-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Yeah, so I bricked my phone
- Thread starter ou7shined
- Start date
-
- Tags
- htc desire
I did, but I made sure I could exactly replicate a couple of the alpharev hboots first (identical to the last bit).
It still took a bit of nerve to flash it though!
ou7shined
Well-Known Member
Don't think it's not appreciated guys.
If it wasn't for pioneering explorers like yourselves conquering the Mount Everests of phone surgery on our behalves we'd all be left in the dark.... with our bricks. (too many mixed metaphors ???
)
Also there must be a beneficial knock on effect to the entire industry as it forces the big companies to be less complacent about the products they are putting out and develop better tech quicker in order to keep up with the standards set by the open communities... maybe?
If it wasn't for pioneering explorers like yourselves conquering the Mount Everests of phone surgery on our behalves we'd all be left in the dark.... with our bricks. (too many mixed metaphors ???
)Also there must be a beneficial knock on effect to the entire industry as it forces the big companies to be less complacent about the products they are putting out and develop better tech quicker in order to keep up with the standards set by the open communities... maybe?
Tyseyh
Android Expert
davoid
Android Expert
You can use this utility:
_thalamus Hacking: Custom HBOOTS…update…
Yes, it's scary. I tried to replicate a couple of alpharev tables, checking the MD5 checksum like Hadron did, and then went ahead. It worked.
_thalamus wrote the tool for editing them - we just used it
saltire
Android Expert
+1
Oh yes, spent a long time comparing the hex of the tools' output against an AlphaRev table. Procrastinated for a few more hours, then went for it, waited a few agonising secs, and phew phone ok.
I was more direct - I chose the "title" string to match that of the alpharev table as well as the partition sizes, then just did a linux "diff" to check the files were identical. Comparing md5sums would also work.
But you do need to get the titles to match too for this to work, otherwise it will just tell you that the files differ, not why.
But you do need to get the titles to match too for this to work, otherwise it will just tell you that the files differ, not why.
Rastaman-FB
Extreme Android User
all i want to say is this
you made your first mistake using android flasher, its a gui and therefore gives you a problem at times and could potentially cause you a real brick if it messes up big time on hboot
always use the fastboot method in cmd
then once done do fastboot reboot-bootloader
job done
you made your first mistake using android flasher, its a gui and therefore gives you a problem at times and could potentially cause you a real brick if it messes up big time on hboot
always use the fastboot method in cmd
then once done do fastboot reboot-bootloader
job done
ou7shined
Well-Known Member
Yep I know that now. I was just following the FAQ which was slightly ambiguous (to noobs) about which method to use and when.
In the end I actually found it easier to use the command line than the GUI version.
Rastaman-FB
Extreme Android User
I'm sure I used Android flasher :-\
was a while ago though. think I had to put it in
fast boot and then run the app on PC
is it deemed bad practice now days?
cm7r2 went on no worries
well ive never recommended it, its why we wrote a fastboot guide as all the flasher gui does is scripted fastboot commands.
we try and minimalise issues by removing any unneeded 3rd party interference especially in mission critical scenarios
if you can use flasher then the drivers are already there to use fastboot from the sdk.
