Changing hboot without a pc - Android Q&A, Help & Troubleshooting

Hi, I recently tried to downgrade my hboot on my Droid DNA from version 1.57 to 1.54 because I was going to unroot it. Long story short I decided not to. Anyway, I accidentally went down to hboot 1.33. Because of this fastboot won't recognize my phone and I can't find any drivers that will work which means I can't upgrade my hboot back up to 1.57. Is there anyway you can change your hboot version without using a computer? I have tried renaming the zip to PC86IMG.zip and booting into the bootloader but it doesn't check for the file so it won't change the hboot version. Any suggestions?

Anybody?

Related

[Q] Hboot Downgrade/RUU Downgrade Help

Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
IXKastling said:
Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
Click to expand...
Click to collapse
You need to be relocked/have 2.17 firmware on your phone.
Once you press (UP) to update does your device turn off right away?
I am relocked and have 2.17 firmware. When I press (UP) for the update it updates with a series of purple and black updating sequences. But I am trying to brick it and I can't seem to do so cause I am pulling out the power cord with no battery but I see no dim red light on the top of the phone. Like I said, everything boots as normal and I even can run the 2.17 RUU EXE and boot up that. I saw that the "HBoot downgrade tutorial" said...
If you're already S-OFF, but on 1.50, you can do one of two things... I have attached the PG86IMG.zip with the 1.40 bootloader on it, download it copy to sd card and flash via bootloader.
The other option is to simply re-run 1.13 RUU, this will downgrade it as well, but this will also erase all data in the process.
Now I assume that means if I am 2.17 and S-ON, which I am, I need to downgrade to 1.13 to have the 2.17 PG86IMG.zip update properly so I can pull the plug and brick it. Do I need to do that or am I just needing to repeat the bricking process until it works?
IXKastling said:
Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
Click to expand...
Click to collapse
I downgraded yesterday. This is what I did. I downloaded this hbootdowngrade217.zip along with another download zip file that contained the 1.13 ruu and I downloaded a 2.08.zip file as well. I relocked my phone and ran the 2.17 ruu thats in that hbootdowngrade217.zip file. Then I rename the 2.08.zip file to PG86IMG.zip onto the root on my sd card. Booted into bootloader let it read the file. Once it read n I had to update. I plugged in the charger from the laptop to the phone then took the battery out. let it sit for a min then hit up on sp it can begin the update n right after it said UNZIPPING n said Updating I counted to 5 n took the charger out on 5. If u did this before it went to the next step you have bricked your device correctly. You can check this by going into the control panel>view devices<manage devices n u put the battery back in hold down the down volume button then plug your phone back up n u will see something saying: Qualcomm MMC Storage but it should change to QSUSB_ (something) that means have bricked it correctly. If u didnt then its gone read unknown device. Just continue trying to brick it. Hope this works for you.

Confused. No root but soff hboot 1.5

Hey guys. A while back my phone got screwed up I had to flash the ruu to get it going again. Originally I was on hboot 1.4 rooted/s off via revoked. After I updated with the ruu for the newer radio it now has hboot 1.5 but still says s off. I wasn't able to flash a Rom via clockwork or twrp. So I have a stock Rom without root and I can't figure out where to go from here.
Any ideas?
Bowdowntozoltan said:
Hey guys. A while back my phone got screwed up I had to flash the ruu to get it going again. Originally I was on hboot 1.4 rooted/s off via revoked. After I updated with the ruu for the newer radio it now has hboot 1.5 but still says s off. I wasn't able to flash a Rom via clockwork or twrp. So I have a stock Rom without root and I can't figure out where to go from here.
Any ideas?
Click to expand...
Click to collapse
don't know for sure but IMO you will have to unlock via HTC dev.com, then you will be able to flash anything like you did before . And to root your ROM, just flash a zip file containing superuser apk and binary after doing the above steps.
Also you can revert back to hboot 1.4 ( don't know how exactly ) but don't follow the downgrade thread by unknownforce as you are already s-off
S-Off supercedes being locked. You should still be able to flash roms and have superuser. I was on unlocked on 1.4 with s-off and went to 1.5 showing locked but with s-off and everything still flashes and superuser works fine.
s-off should allow you to do as you please with your phone.. you should still be able to flash w/e recovery you want and w/e rom you want w/o fastboot into recovery..
having s-on in 1.5 is a pain.. but if you already have s-off.. you can just as easily flash back down to 1.4 or even to 1.04 the eng hboot..
but once you're s-off, which you already are, you can do as you please with your device.. you don't need htc dev for it..
EDIT: you might just have to reflash your recovery.. use fastboot flash recovery recovery.img and then boot into it... recovery.img has to be in the same folder as your adb and fastboot files..

RUU not working AT&T

I have to ship my hox+ back soon and for some reason the ruu doesn't work I get bootloader version error. This is the ruu that I have been using RUU_EVITARE_UL_JB_45_Cingular_US_1.15.502.9_Radio_1.09.55.17_18.20.95.55L_release_290329_signed.exe. Any help would be much appreciated I need to get this thing back to stock.
Has your phone already booted into hboot when you get that error? I had a similar error (maybe the same one) when I was flashing the 1.15 stock 2 weeks ago because the phone didn't boot into hboot on its own. I put the phone into hboot after relocking the bootloader. Then ran the RUU and it worked perfectly.
are you on Hboot 1.40? If so, you'll probably want to use the 1.19 RUU.
Where is the 1.19? I've only found the one I'm using.
EDIT:I am running HBOOT 1.40 I will try running the ruu again and see if it works this time.
Found it http://forum.xda-developers.com/showthread.php?t=2238839
Sent from my HTC One X using Tapatalk 2
You can also get the 1.19 RUU from HTC's website.

Unbrick my phone

I bricked my Thunderbolt trying to return it from rooted ICS 4.0.4 with the new radios to stock. Now i downloaded the .19 RUU however it does not want to install. It says that the MAIN VERSION IS OLDER. Of course since the installed version is 7.02.605.10 the hboot does not allow the PG05IMG to install because it is the .19 RUU.
So my phone is stuck in the HTC white screen and boot-loops. When I go to bootloader I can only use fastboot usb and nothing else. Not even recovery. On top of that the hboot is version 1.05 with s-on with latest radios
I think the solution would be updating with the latest OTA zip file from botloader. Do you have the zip file OTA 7.02.605.10???
Or how did you unbrick ur phone???

[Q] Error 131 on RUU Flash after HBOOT Downgrade

I recently bought my new Evo 3D from eBay. As far as I can tell, it is in perfect shape. I was hoping to flash it to Page Plus and was dismayed when I realized how impossible the rooting process looked. I began with downgrading my 1.58 HBOOT to 1.40. Now I am attempting to flash the 1.13 RUU so I can finally move on in this process, but every time I attempt to flash it (or any other RUU), I get the error, "Error [131]: CUSTOMER ID ERROR." Now most fastboot commands do not work, and my phone bootloops with the stock ROM. Any idea how to fix it?
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Brian706 said:
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Click to expand...
Click to collapse
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Macadamia Daze said:
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
Click to expand...
Click to collapse
Oh, I see now!
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Brian706 said:
Oh, I see now!
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Click to expand...
Click to collapse
So far, I have yet to have any success despite flashing many RUUs. I took a break for quite a while, but decided I may try again. I am downloading now the 2.08 RUU, which one thread suggested.
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
If I remember correctly, the HTCDev unlock doesnt work for the earlier bootloaders. It says so on the very first page when its walking you through the steps. I could be wrong but you may wanna keep that in mind

Categories

Resources