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.
Related
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???
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
I have a htc legend(BellMobility - Build number: 3.20.666.1 CL291292 release-keys) with hboot 1.01 and adroind 2.2. I try and update hboot via ruu file but it says that i have not downlaoded the right ruu file for my phone. Even tho i have. Any idea on how to fix this. Why do I want to update via ruu is i need to update hboot so I can execute the command "fastboot oem get_identifier_token"
IIRC Bell released Android 2.2 for Legend, and that was the last update they ever did. There wouldn't be anything newer for you to have.
Asovse1 said:
IIRC Bell released Android 2.2 for Legend, and that was the last update they ever did. There wouldn't be anything newer for you to have.
Click to expand...
Click to collapse
ya i know but i have hboot 1.01 and i need to update it via ruu file to hboot 1.02 to flash CWM. fyi i have s-off but i still cant flash the recovery. so i am trying to unlock boot-loader but in order to do that i need to update hboot.
iphone4life4 said:
ya i know but i have hboot 1.01 and i need to update it via ruu file to hboot 1.02 to flash CWM. fyi i have s-off but i still cant flash the recovery. so i am trying to unlock boot-loader but in order to do that i need to update hboot.
Click to expand...
Click to collapse
Use BlaY0's method , look at post #62 and yo will have no problems !
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?
I have an HTC one that has been bootloader unlocked and running CM for some time. The bootloader version is currently 1.55 and S-ON. I'm hoping to revert to a rom that will work with rumrunner and allow S-OFF to happen.
Can anyone point me in the right direction? I've been looking for about an hour and can only find a leaked dev build of a rom for this phone that is flashable via recovery, the rest are all RUU files and I'm not familiar enough with RUU to know whether or not I'll take an permanent step in the wrong direction if I use one to upgrade.
Edit: please move to the right forum, I just realized I should have put this in another section instead of dev.
bruor said:
I have an HTC one that has been bootloader unlocked and running CM for some time. The bootloader version is currently 1.55 and S-ON. I'm hoping to revert to a rom that will work with rumrunner and allow S-OFF to happen.
Can anyone point me in the right direction? I've been looking for about an hour and can only find a leaked dev build of a rom for this phone that is flashable via recovery, the rest are all RUU files and I'm not familiar enough with RUU to know whether or not I'll take an permanent step in the wrong direction if I use one to upgrade.
Edit: please move to the right forum, I just realized I should have put this in another section instead of dev.
Click to expand...
Click to collapse
Since you are S-ON you will need to do the following:
Relock your bootloader
Leave your phone in FASTBOOT USB
Run this RUU 3.24.531.3 in Windows and follow the prompts
Follow rumrunner's OP instructions
The RUU will reset your phone back to stock and since your hboot is 1.55 this is the RUU which corresponds to that hboot.
majmoz said:
Since you are S-ON you will need to do the following:
Relock your bootloader
Leave your phone in FASTBOOT USB
Run this RUU 3.24.531.3 in Windows and follow the prompts
Follow rumrunner's OP instructions
The RUU will reset your phone back to stock and since your hboot is 1.55 this is the RUU which corresponds to that hboot.
Click to expand...
Click to collapse
Thank you for the quick reply, it worked beautifully. Now that I am S-OFF, if I am to run an RUU, will they set the device back to S-ON? Or do they leave that flag alone?
bruor said:
Thank you for the quick reply, it worked beautifully. Now that I am S-OFF, if I am to run an RUU, will they set the device back to S-ON? Or do they leave that flag alone?
Click to expand...
Click to collapse
No, RUU will not set the flag to S-ON.
I keep getting error 155 during the RUU process. I have been researching and trying a bunch of different things but I cannot update the RUU
I'm running SkyDragon GPE 7.2 Android 5.1.1 hboot 1.61 with S-ON. I error saying RRU is older and errors.