• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root HELP.Problem updating to jelly bean

Ok, bad news. I tried the factory reset from the recover and received the same error after the update.

I have a question about the 3.16 OTA update. How do I accept the
3.16 upgrade after locking the phone. Does it automatically prompt you??

Another question: Do I have to use baby racun if the phone is on 3.16?

thanks!
 
I locked the phone. It says RELOCKED at the top in the bootloader.
Now I can't get into Recovery. The phone just reboots and goes into bootloader. How can I update to 3.16?

thank you.
 
Ok, bad news. I tried the factory reset from the recover and received the same error after the update.

I have a question about the 3.16 OTA update. How do I accept the
3.16 upgrade after locking the phone. Does it automatically prompt you??

Another question: Do I have to use baby racun if the phone is on 3.16?

thanks!

I locked the phone. It says RELOCKED at the top in the bootloader.
Now I can't get into Recovery. The phone just reboots and goes into bootloader. How can I update to 3.16?

thank you.

to get to the update go to your settings>about phone>software>check software update. or it is somewhere around there in settings. there should be a check software update. once you do that the phone will check for an update and it should start to download after that.
 
I can't get to the settings. The phone just reboots and goes into the bootloader.

I locked the phone. It says RELOCKED at the top in the bootloader.
Now I can't get into Recovery. The phone just reboots and goes into bootloader. How can I update to 3.16?
 
I can't get to the settings. The phone just reboots and goes into the bootloader.

I locked the phone. It says RELOCKED at the top in the bootloader.
Now I can't get into Recovery. The phone just reboots and goes into bootloader. How can I update to 3.16?

hmmmmmm that is weird. did you do anything else after re-locking it?

can you get into fastboot? if so then try unlocking it again and see if you can get access to recovery. if not then we can still get recovery by either fastboot command or by flashing it through the bootloader.
 
Yes, I can unlock it and access the recovery. After that I restore the backup. This is how I always do it.
If I unlock it, can I still accept the OTA update or it is not possible?

thanks for all the help. I am getting better at this but still a lot of question.
 
Yes, I can unlock it and access the recovery. After that I restore the backup. This is how I always do it.
If I unlock it, can I still accept the OTA update or it is not possible?

thanks for all the help. I am getting better at this but still a lot of question.

no worries first of all. keep the questions coming. its the best way you will learn all of this stuff. well you can't accept an ota unless you re-lock the bootloader. so it is not possible which is a good thing as you can't by accident accept the ota as you will not be able to. the other way to do it is the ruu, but you are having issues with ruu's.

question.......have you tried using another computer when running the ruu?
 
No, I am using one computer. I have tried in Linux and Windows. Both
environments show the same error. I can try on a different computer.
 
No, I am using one computer. I have tried in Linux and Windows. Both
environments show the same error. I can try on a different computer.

yeah that is just weird with the error you are getting. i'm still checking though, but i can't seem to find an answer yet. i might try and see if i can get some big guns to come in and see if they can come up with an answer.

in the meantime try it on another computer.

also can you post what your radio is as well as your hboot again.
 
E:\Android\sdk-tools\RabiesShotWindows>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.15.0000
INFOversion-baseband: 1.05.11.0606
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.15.651.16
INFOversion-misc: PVT SHIP S-ON
INFOserialno: HT
INFOimei:
INFOproduct: jewel
INFOplatform: HBOOT-8960
INFOmodelid: PJ7510000
INFOcidnum: SPCS_001
INFObattery-status: good
INFObattery-voltage: 4113mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: dirty-1b5ebf26
INFOhbootpreupdate: 11
INFOgencheckpt: 0
 
I can't get any help on the IRC channel for the error I am getting.
They don't support the RUU updates.

getting the error FAILED (remote: 12 signature verify fail).
RUU version on my phone: 3.15.
I have downloaded the 3.15 file and checked the MD5SUM.

I run the following commands:

chmod 755 RabiesShot adb fastboot

fastboot oem lock

phone shows: Tempered, Relocked, Security Warning on top

fastboot erase cache - success
fastboot oem rebootRUU - success
fastboot flash zip RUU.zip - error FAILED (remote: 12 signature verify fail).

I have spent 4 hours yesterday trying to update.
Downloaded the file one more time just to make sure.

I would appreciate any other suggestions.

thanks.

just to clarify,you are on a stock rom now,correct? if you go to settings/about phone/ your software build number is 3.15.651.16,correct?

RUU.zip is just a stock ruu. i cant say why they have you run it,but it is 100% stock,signed by htc,and must be corrupt somehow,thus failing the signiture verification. could be a firewall or antivirus is somehow corrupting the download,or they possible have the wrong file/md5sum posted. you could try downloading the stock 3.15 ruu from here and then extract rom.zip from the .exe file in this manner:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be renamed to PxxxIMG and flashed in hboot,from a FAT32 sd card

compare the md5 of rom.zip to unlimiteds ruu.zip and see if they are the same. if not,you could try the process using your rom.zip(renamed ruu.zip to keep the commands the same)


This is just an idea I had, not sure if it will work or not. You will also have to do extra steps to root the phone. But if you are game, then I would re-lock the phone and accept the ota to get you to 3.16. I would then root the phone from there. Again, it is just a thought.
id prolly avoid that,if the phone is on 3.15 now,if for no other reason than the baby raccun steps are increasing the margin for error. i venture to guess that this minor update is using the same hboot,and baby raccun is just changing the main version so the 3.15 ruu will flash. i dont think being onthe newer software will increase your changes,i think you just have a bad,corrupt,or incorrect ruu.

if you happen to have more than one RUU.zip in your dirty raccun folder,make sure you delete all but the one that is 3.15

hope that helps :)
 
E:\Android\sdk-tools\RabiesShotWindows>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.15.0000
INFOversion-baseband: 1.05.11.0606
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.15.651.16
INFOversion-misc: PVT SHIP S-ON
INFOserialno: HTxxxxxxxxxx
INFOimei: xxxxxxxxxxxxx
INFOproduct: jewel
INFOplatform: HBOOT-8960
INFOmodelid: PJ7510000
INFOcidnum: SPCS_001
INFObattery-status: good
INFObattery-voltage: 4113mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: dirty-1b5ebf26
INFOhbootpreupdate: 11
INFOgencheckpt: 0

ninja post! :D

something is not right here... you have 1.15 hboot,but are you actually on software build 3.15.651.16? check in settings/about phone like i suggested above. you are on a stock rom,correct?

also,may want to x out your serial number and imie :eek:
 
ninja post! :D

something is not right here... you have 1.15 hboot,but are you actually on software build 3.15.651.16? check in settings/about phone like i suggested above. you are on a stock rom,correct?

also,may want to x out your serial number and imie :eek:

i believe he was unlocked with recovery and flashed a 3.15 rom, but i could be wrong.
 
hmm after a couple minutes of thot i think we need a slightly different approach. i think the main version/hboot mismatch is screwing us up,so try this:

-download the set main version low zip from this post: http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4 and flash it in recovery

-do fastboot getvar all again

-if your main version is now 1.00.000.0,then try dirty racuun again,using the unlimited ruu.zip file for RUU 1.22.651.3 - HBOOT 1.15.

hold off on flashing the 2.13 ruu for now. i dont think we want to elevate the hboot any higher than neccessary at this point.
 
sending 'zip' (596240 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)


E:\Android\sdk-tools\RabiesShotWindows>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.15.0000
INFOversion-baseband: 1.05.11.0606
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.00.000.06
INFOversion-misc: PVT SHIP S-ON
INFOserialno: HT
INFOimei:
INFOproduct: jewel
INFOplatform: HBOOT-8960
INFOmodelid: PJ7510000
INFOcidnum: SPCS_001
INFObattery-status: good
INFObattery-voltage: 4105mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: dirty-1b5ebf26
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
 
E:\Android\sdk-tools\RabiesShotWindows>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.15.0000
INFOversion-baseband: 1.05.11.0606
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.22.651.3
INFOversion-misc: PVT SHIP S-ON
INFOserialno: HT
INFOimei:
INFOproduct: jewel
INFOplatform: HBOOT-8960
INFOmodelid: PJ7510000
INFOcidnum: SPCS_001
INFObattery-status: good
INFObattery-voltage: 4110mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-1b5ebf26
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!

I will try to run the RabiesShot.exe
 
Back
Top Bottom