Evening!!
I'm hoping you all might be able to help me out here. I have been running the OTA GB ROM for months now. Tonight I rebooted my phone by just holding the power button and hitting reboot. Its now however stuck on the HTC screen and won't boot past it.
I can get into the FASTBOOT menu and such, however when I try to go into the RECOVERY the phone just shuts off, or it will just reboot back into the HTC screen. I've tried download the Rezound_All-In-One_Kit_v2.0 and was able to flash the recovery again however I'm getting the same results, phone just shuts off.
Any idea on how to get my phone back? I really don't care about the data on the phone, just want to get it backup and working. lol I'm really confused as to why all the sudden its getting stuck on the HTC screen.
Did you try removing the battery and putting it back in?
are you rooted? which recovery?
I'm using Amon Ra style vigor and I am unlocked/rooted.
I'm trying to get ADB to detect my phone, but not having luck in that realm either. Was just going to try to push a ROM over to the phone. However it does not appear that it will detect my phone when in the FASTBOOT USB mode. I do a adb devices and it just comes back as none being found...
Kabish said:
I'm using Amon Ra style vigor and I am unlocked/rooted.
Click to expand...
Click to collapse
Download the RUU. Relock your phone ("fastboot oem lock" from command prompt), and run the ruu from your PC while connected to USB. After that you can unlock your phone again and start from scratch.
link to the RUU:
http://forum.xda-developers.com/showpost.php?p=22045045&postcount=58
Will do downloading now, and thank you for the link. I so want to bang my head on the table.
Kabish said:
I'm trying to get ADB to detect my phone, but not having luck in that realm either. Was just going to try to push a ROM over to the phone. However it does not appear that it will detect my phone when in the FASTBOOT USB mode. I do a adb devices and it just comes back as none being found...
Click to expand...
Click to collapse
disconnect your phone
close command prompt
ctrl+alt+del and kill any adb process
take out your battery, then put your battery back and connect your phone to your PC and boot to fastboot.
open up CMD again and you should be able to detect your phone.
Ugh...
"ERROR [140]: BOOTLOADER VERSION ERROR"
"The ROM Update Utility cannot update your Android Phone.
Please get the correct ROM Update Utility and try again"
Kabish said:
Ugh...
"ERROR [140]: BOOTLOADER VERSION ERROR"
"The ROM Update Utility cannot update your Android Phone.
Please get the correct ROM Update Utility and try again"
Click to expand...
Click to collapse
you're on the latest gb update?
Yes I should be on the latest OTA. I had my phone rooted when I first got it, then Verizion did an OTA update which was messing with my phone. So I did an RUU and then re-rooted with the OTA Pre Root ROM.
Trying to follow this thread now.. Corsses Fingers...
http://forum.xda-developers.com/showthread.php?t=1338916&page=6
Kabish said:
Yes I should be on the latest OTA. I had my phone rooted when I first got it, then Verizion did an OTA update which was messing with my phone. So I did an RUU and then re-rooted with the OTA Pre Root ROM.
Trying to follow this thread now.. Corsses Fingers...
http://forum.xda-developers.com/showthread.php?t=1338916&page=6
Click to expand...
Click to collapse
gl. let me know how it goes.
Looks like that is not going to work.. I pulled the "firmware" file from that post and renamed it to the PH98IMG.ZIP.
It goes to "Loading...PH98IMG.ZIP
Then
Parsing...PH98IMG.ZIP
Then it just goes back to the main HBOOT menu.
I did unlock my phone again since I had locked it to run the RUU. Any suggestions on how to get the RUU to run?
Ran the RUU again from the link that you sent me. Getting this info when running it:
FROM IMAGE VERSION: 3.10.605.7
TO IMAGE VERSION: 2.01.605.11
Guessing it going from 3.10 to 2.01 is the issue???
Kabish said:
Ran the RUU again from the link that you sent me. Getting this info when running it:
FROM IMAGE VERSION: 3.10.605.7
TO IMAGE VERSION: 2.01.605.11
Guessing it going from 3.10 to 2.01 is the issue???
Click to expand...
Click to collapse
so you are on the leaked ruu?
Apparently so...
I was sure I was on the OTA Stock one though, but apparently not, or I jacked things up trying to fix everything and flashed the wrong one.
I'm trying to go through post to downgrade my Mainver file. Thing is since I can't get into Recovery for whatever reason, and stupid ADB won't list my phone its making this difficult. I can run commands, example locking/unlocking but it won't let me shell in.
Kabish said:
Apparently so...
I was sure I was on the OTA Stock one though, but apparently not, or I jacked things up trying to fix everything and flashed the wrong one.
I'm trying to go through post to downgrade my Mainver file. Thing is since I can't get into Recovery for whatever reason, and stupid ADB won't list my phone its making this difficult. I can run commands, example locking/unlocking but it won't let me shell in.
Click to expand...
Click to collapse
try to run the leak again.relock, put the ph file on the root of your sd card, then run the file in hboot once. after that finishes, run it again.
http://androidcommunity.com/htc-rezound-android-4-0-ics-leaked-with-sense-3-6-get-it-now-20120316/
download the stock version. you need to be relocked to do this.
after that, unlock, flash a recovery, then proceed to install an ics rom, like clean rom or the many others out there.
after you flash the leak twice, and boot to the OS for the first time, it can take up to 10 minutes to boot up in some cases. be patient.
Ok, i'll give that a go...
If I'm reading that post right though it saying that is ICS?? I was not running ICS, I had tried ICS but it was too buggy for my taste so I flashed back my restore and kernel. I'm wondering if I accidently flashed the ICS PH98IMG file.
I'm willing to give it a go though... Its going to take for EVER to download that file though as its on Rapidshare and I'm getting an eta of 6hrs lol.
What really just gets me is that I've not touched my phone as far as rooting/updating since February. And out of the blue it decides to take a dump on me...
Kabish said:
Ok, i'll give that a go...
If I'm reading that post right though it saying that is ICS?? I was not running ICS, I had tried ICS but it was too buggy for my taste so I flashed back my restore and kernel.
I'm willing to give it a go though... Its going to take for EVER to download that file though as its on Rapidshare and I'm getting an eta of 6hrs lol.
Click to expand...
Click to collapse
ICS isn't that buggy especially after flashing a good rom. I actually have no bugs at all. Clean ROM is as stable as they come.
When you flashed the leak before, you lost the ability to fully revert back to pre leak status. you can however install a gb rom, but your radios ad such stay upgraded to the leak versions.
---------- Post added at 01:51 AM ---------- Previous post was at 01:48 AM ----------
Kabish said:
What really just gets me is that I've not touched my phone as far as rooting/updating since February. And out of the blue it decides to take a dump on me...
Click to expand...
Click to collapse
If its February, then you aren't on the leak. you just need to reset your main version I believe.
If I remember correctly my phone kept crashing on me. Granted this is when ICS first came out. I don't remember running an RUU though for ICS, however I did run one to get the OTA update.
I have a A500 tablet as well, which it is running ICS so I kind of get the two all mixed up when I think what I've done lol I've changed ROMS on my A500 so many times that my volume rocker is almost warn out
Found another host for the ICS Stock, it will be done in about 10 minutes.
Kabish said:
If I remember correctly my phone kept crashing on me. Granted this is when ICS first came out. I don't remember running an RUU though for ICS, however I did run one to get the OTA update.
I have a A500 tablet as well, which it is running ICS so I kind of get the two all mixed up when I think what I've done lol I've changed ROMS on my A500 so many times that my volume rocker is almost warn out
Found another host for the ICS Stock, it will be done in about 10 minutes.
Click to expand...
Click to collapse
ICS leak isnt in ruu format. perhaps thats why you dont remember it.
INSTALL:
- rename the downloaded leak file to “PH98IMG.zip” (no quotes)
– Place the renamed file onto the root of the SD Card
- relock your device
– Power down your device
– Reboot into the bootloader by holding VOL DOWN + Power
– The flashing process should begin automatically
- once complete, go back to bootloader and flash a second time.
Related
Hey Guys, fairly new to posting here, but was hoping this could help some of you.
#####################################################################
# If you are running a stock ROM you can ignore this, there are better threads for you out there.
#####################################################################
When the OTA came out I knew I wanted the new radios, but have had nothing but problems putting them on.
I have spent the last couple of hours reading and generally just being frustrated. I eventually got to the conclusion I wanted and I thought having all of this OTA update junk in one place might be helpful for others.
History:
- I was running Ineffabilis 12/29. (great ROM)
- Went to Senseless ICS (great ROM, bluetooth problems, persistent with all current ICS's, was insurmountable for me)
- Went to Team BAMF Rezound Cubed ROM, used this ROM to get out of the ICS trap because it flashes a kernel after it flashes the ROM.
Coming From ICS, Team BAMF Cubed or the New clean GB rom:
If you have installed a ROM that updated the Main Ver (all ICS roms or Team BAMF rom, or the new clean GB rom, then you will need to reset the main ver to 1.00.000.00 to run the RUU.
To do that go to this thread: http://forum.xda-developers.com/showpost.php?p=21875151&postcount=1
Next:
Once you have your main ver set to 1.00.000.00. You will need to follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1466474 (summary below)
1) You will need to reflash the stock recovery (a great way to do that is using Cleanflash, get it here: http://www.scottsroms.com/downloads.php?do=file&id=57) -- You can find the stock flash recovery image in the thread above.
2) Reboot to Fastboot and run "fastboot oem lock" from your DOS command line. This will reboot your phone back into fastboot/hboot.
3) Run the RUU.exe from Windows using the download from scottsroms here: http://www.scottsroms.com/downloads.php?do=cat&id=11
4) Go through and install the OTA updates. Go to settings, and software update.
5) Go back to HTCDev.com and unlock the bootloader as you have in the past.
6) Flash a new recovery.img, such as amonRa, (fastboot flash recovery nameofrecovery.img)
7) The world is now yours! Install ICS if you would like or any other ROM or install su if you prefer.
Credits:
!! mrbracht for the mainver fixed (saved my bacon)
!! FlyHalf205 for the rest of this
!! scrosler for generally being awesome and all the great tool's, roms, ruu, etc.
I've downloaded the recovery and unziped it. Then I moved it to fastboot but when I type fastboot flash recovery recovery_sign.img I get a error cannot load.
FlagAZ said:
I've downloaded the recovery and unziped it. Then I moved it to fastboot but when I type fastboot flash recovery recovery_sign.img I get a error cannot load.
Click to expand...
Click to collapse
The stock recovery? What mainversion are you?
I checked today it was something like 1.0.6. I know that it was not updated.
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
I've been trying all day with no like...... I'm lost with all the post about how to do this (flash this, unload this, do it this way)......
okay so what is the text of the error?
i keep getting hung up in the RUU... my MainVer is the same version as the RUU, or was, but now i can't reboot my phone, just tuck in bootloader/fastboot, and with the stock recovery lol...
my ADB won't open either
---------- Post added at 09:26 PM ---------- Previous post was at 08:39 PM ----------
platinumrims said:
i keep getting hung up in the RUU... my MainVer is the same version as the RUU, or was, but now i can't reboot my phone, just tuck in bootloader/fastboot, and with the stock recovery lol...
my ADB won't open either
Click to expand...
Click to collapse
pah, gave up. unlocked reflashed amon ra, and restored my nandroid... :'(
Maybe this reply is too late. Sorry...
But, was it locked and having the stock recovery when you were trying the RUU? Also you run the RUU from windows while the phone is in hboot mode.
pngwyn said:
Also you run the RUU from windows while the phone is in hboot mode.
Click to expand...
Click to collapse
Yes, that is how I always do it.
Wow. I'm impressed with the details you provided. I was debating flashing ICS and had questions about going back. You answered all my questions. Thanks for posting your findings. I really appreciate it.
Updated
So by resetting the mainver, will I be able to flash ICS then say Ineffabilis 12/29 without worrying about updating any kernels? Also, just to confirm, once I flash ICS, I'd have to reset the mainver before going back to Ineffabilis 12/29.
Sent from my ADR6425LVW using xda premium
I go back and forth between ics and gb roms without any issues, never got a mainver error.
Sent from my HTC Rezound using XDA Premium
raider3bravo said:
Wow. I'm impressed with the details you provided. I was debating flashing ICS and had questions about going back. You answered all my questions. Thanks for posting your findings. I really appreciate it.
Updated
So by resetting the mainver, will I be able to flash ICS then say Ineffabilis 12/29 without worrying about updating any kernels? Also, just to confirm, once I flash ICS, I'd have to reset the mainver before going back to Ineffabilis 12/29.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Glad you found the post useful.
As far as I understand, you won't have any issues switching between GB and ICS and back to GB (other than needing to make sure you are running a compatible kernel). If you go back to ineffabilis after ICS you will need to find a way to get the kernel on the system (probably through fastboot or adb) and then flash ineffabilis, for me it was easiest to go back to GB using team bamf because it included the kernel and then you could flash ineffabilis and all should have been well.
The real reason to worry about main ver (as far as I know) is so that you can flash the ruu and return to stock. I guess there are also some other problems with kernels and them checking what mainver you have before flashing, but I am not familiar with those issues.
The nice thing is with the mainver hack above you won't ever have to worry by resetting the mainver, pushing the stock recovery, relocking and then flashing using the RUU utility it is possible to get completely back to factory condition.
Best Regards!
pngwyn said:
Maybe this reply is too late. Sorry...
But, was it locked and having the stock recovery when you were trying the RUU? Also you run the RUU from windows while the phone is in hboot mode.
Click to expand...
Click to collapse
I was using the ruu on Windows and had my phone in Hboot.
I relocked it, via an app someone made here on the forums because I couldn't get ADB to run at all. It would flash up in a window and close immediately. And I re installed SDK 10 Times and couldn't ever get adb to re instal or update.
Also had the stock recovery flashed...
When I used the app to relock the phone I had a "security warning" message under the relock status in fastboot, dunno if that's normal.
Then when trying to run the ruu I got a 155 error, but it wasn't the same one as listed in the report, or it didn't say the same thing at least. Then I kept getting battery lower than 30% errors so it wouldn't let me redo it after the 3rd try. Even though my phone was at like 85% when I got frustrated and decided booted it back up...
I'd like to try it again some other time but idk what else to do to get my ADB functioning ATM so I can check or change my MainVer (which was the same version as the ruu, also dunno if that mattered, I just though as long as it wasn't higher the ruu would work)
Any info would be mucho appreciated lol. :banghead:
platinumrims said:
I was using the ruu on Windows and had my phone in Hboot.
I relocked it, via an app someone made here on the forums because I couldn't get ADB to run at all. It would flash up in a window and close immediately. And I re installed SDK 10 Times and couldn't ever get adb to re instal or update.
Also had the stock recovery flashed...
When I used the app to relock the phone I had a "security warning" message under the relock status in fastboot, dunno if that's normal.
Then when trying to run the ruu I got a 155 error, but it wasn't the same one as listed in the report, or it didn't say the same thing at least. Then I kept getting battery lower than 30% errors so it wouldn't let me redo it after the 3rd try. Even though my phone was at like 85% when I got frustrated and decided booted it back up...
I'd like to try it again some other time but idk what else to do to get my ADB functioning ATM so I can check or change my MainVer (which was the same version as the ruu, also dunno if that mattered, I just though as long as it wasn't higher the ruu would work)
Any info would be mucho appreciated lol. :banghead:
Click to expand...
Click to collapse
I am not familiar with anything you experienced.
You shouldn't need adb for anything you are trying to do. It doesn't sound like you are getting the mainver error (if you were you would be getting the error after trying to go through the RUU wizard and it actually tells you your mainver is 2.00.###.## for whatever it is. If you are sure you haven't done anything to update your main ver than chances are your mainver is not the problem.
I am just guessing but this is what I am imagining could be solutions.
- Use 'fastboot oem lock' from the hboot prompt when in fastboot usb mode (ie your usb cable is plugged in.
- Make sure you are using the .exe version of the RUU. If you are not using the .exe version then that definitely could be the problem, if you are using the .exe version then perhaps the file got corrupted when you downloaded it. Try deleting and redownloading.
- You have said that you are running the stock recovery which sounds correct. But make sure you aren't using the stock recovery from one of your own backups use the one that is provided in the thread from my link above.
... In conclusion you shouldn't need ADB if your main version is the stock mainver. Flash the stock recovery first of all, then use the command 'fastboot oem lock' it will tell you it is locked it will reboot the phone (I think it even gives you an error in the dos prompt.) But then when it reboots it reboots to hboot and will say relocked at the top in the bright purple. Then be sure to run the RUU version .exe. If the RUU you have still isn't working download another (this is the one that worked for me: http://www.scottsroms.com/downloads.php?do=file&id=37)
Sorry wish I could be more helpful but I don't have relevant experience for what is happening for you but I do know what worked for me and I do believe it will work for you.
Good luck!
I doubt seriously that its my mainver. I'm wondering if it had something to do with that,weird security thing I had showing up in my fastboot. I will try it again maybe tomorrow night or something. Thank for your help
THANKS
I had to do the main ver fix and everything, great guide made everything super easy
Wind Mobile released ICS today so I want to go back to stock from the custom ROM I'm using.
First I downloaded the RUU.exe in a thread I found here for Wind Mobile. I tried running it on my PC with my phone plugged in and it failed. So I thought perhaps I need to relock the boot loader (my phone is S-ON btw). So I downloaded the All in One Tool Kit, booted into the bootloader and chose relock option. First thing said success, second thing said failed too many failed attempts. After that my phone rebooted and went into the bootloader. It says **RELOCKED** and then *** Security Warning***. I'm assuming that meant it worked?
After this I could not reboot my ROM and I could not get into clock work mod recovery. So I attempted to install another recovery EXT4 included in the toolkit, it said success and rebooted. But when I choose recovery it just goes reboots into bootloader from the beginning again.
Did I fubar my phone?
mapleleafs89 said:
Wind Mobile released ICS today so I want to go back to stock from the custom ROM I'm using.
First I downloaded the RUU.exe in a thread I found here for Wind Mobile. I tried running it on my PC with my phone plugged in and it failed. So I thought perhaps I need to relock the boot loader (my phone is S-ON btw). So I downloaded the All in One Tool Kit, booted into the bootloader and chose relock option. First thing said success, second thing said failed too many failed attempts. After that my phone rebooted and went into the bootloader. It says **RELOCKED** and then *** Security Warning***. I'm assuming that meant it worked?
After this I could not reboot my ROM and I could not get into clock work mod recovery. So I attempted to install another recovery EXT4 included in the toolkit, it said success and rebooted. But when I choose recovery it just goes reboots into bootloader from the beginning again.
Did I fubar my phone?
Click to expand...
Click to collapse
Boot your phone into bootloader, choose fastboot, then run the RUU.exe file, follow the instructions to get it back to complete stock.
Mind telling me what ROM you were running? If it was ICS or something based on GB.
Edit: Wrong forum by the way
Thanks, it worked like that. I was on GB energy rom btw.
Back to stock, looks like Wind didn't even push the update out fully yet because no ones been able to update OTA yet.
Thanks again.
mapleleafs89 said:
Thanks, it worked like that. I was on GB energy rom btw.
Back to stock, looks like Wind didn't even push the update out fully yet because no ones been able to update OTA yet.
Thanks again.
Click to expand...
Click to collapse
Welcome, I was just checking the software version to make sure it would work correctly. Try checking for the update in settings, usually comes through faster that way.
ruu.exe being something like ruu_ruby_globalive_wwe_1.45.1500.2_r_radio_1.09.550L.11V2DC........etc etc etc.. ?
is that the right version to revert back to?
seems to be the only one i can find on the forums here.. via a really slow download link.
Ashcunak said:
ruu.exe being something like ruu_ruby_globalive_wwe_1.45.1500.2_r_radio_1.09.550L.11V2DC........etc etc etc.. ?
is that the right version to revert back to?
seems to be the only one i can find on the forums here.. via a really slow download link.
Click to expand...
Click to collapse
Well that's the only link we have here, you can always google for it, hopefully you can find a link on HTC's site, since that's probably the only link I'd trust.
forgot about this guy, everyone seems to trust him so ill go with the crowd...
http://forum.xda-developers.com/showthread.php?t=1335368
Ashcunak said:
forgot about this guy, everyone seems to trust him so ill go with the crowd...
http://forum.xda-developers.com/showthread.php?t=1335368
Click to expand...
Click to collapse
Fair enough, peace.
Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
I've heard of several people being successful on 4.03.605.2 with the 3.14.605.5 ControlBear version.
Only other advice I can offer is don't give up, try different wires if you're having trouble, and pay attention to the troubleshooting page if you decide you want back out and try again later. I've S-OFF'ed three Rezounds. The first took 3 days, the second 2 minutes, and the third 30 minutes.
dplane said:
Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
Click to expand...
Click to collapse
i did s-off with viper's rom and the .5. i was on global too, don't let it scare you or you will not get it. i couldn't get the timing for the life of me. first two hours was a hassle, then i had to get my other battery(thought i bricked my phone) then i relized that they had a metrnome with the correct timing and it worked the first time. but use a different memory card. all of these things can be found under the s-off instructions.:good:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Thanks for the responses and moral support folks!
Collin, I may have to hit you up for that assistance soon, I'd rather be safe then sorry so I might feel better if I have someone to "hold my hand"
May not get around to it til Sat afternoon or Sunday though.
famouscollin said:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Click to expand...
Click to collapse
I'm working with the same situation as the OP. You posted a link to a second recovery to flash after Amon Ra, I've tried that link and it forces me to request access. Which recovery is it and is there another link or are you able to give me access to that one?
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Sax1031 said:
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Click to expand...
Click to collapse
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
neowisdom1031 said:
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
Click to expand...
Click to collapse
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Sax1031 said:
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Click to expand...
Click to collapse
If you're able to flash back to stock that would be the best place to start for S-OFF
neowisdom1031 said:
If you're able to flash back to stock that would be the best place to start for S-OFF
Click to expand...
Click to collapse
I flashed back to the first ICS RUU.
I think I know why it said permission denied. Because I didn't have actual root access.
At the point of trying the wire trick.
Edit: Achieved S-OFF. Thanks so much guys. Going from 3 days ago of flashing my first rom. To having to relock the device, run the first ICS Ruu, then doing the wire trick. Hell of a learning curve on these things. Thanks everyone for all the help.
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
neowisdom1031 said:
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
Click to expand...
Click to collapse
Fwiw I also was able to go s-off using this ruu and flashing supersu from a temporary amon ra. Not as tough as it thought.
Sent from my ADR6425LVW using xda app-developers app
.
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
michaelbsheldon said:
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
Click to expand...
Click to collapse
It shouldn't matter. ControlBear has its own versions of everything it needs.
Sent from my HTC Rezound using Tapatalk 2
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Izeltokatl said:
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Click to expand...
Click to collapse
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
famouscollin said:
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
Click to expand...
Click to collapse
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Izeltokatl said:
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Click to expand...
Click to collapse
you can try backing up your sd cards and partition them before you start the control bear process, and your sure you have root access correct? via rootchecker, tatanium backup or somethin gand usb degugging checked? if your still having issues look for apophis' thread named "so you need assistance, WE ARE HERE TO HELP" post in that thread im sure he can help you walk thru it..
When I bought my rezound used it had a constant boot loop issue. That's why I got it fairly cheap. I immediayly ran the global ruu hoping it would boot. It still boot looped. I was able to unlock, flash recovery and install newts xxx. I have tried to boot other romsand they give me issues too. Is there any way I can s off in my current configuration because I am pretty confident another ruu from my sd card just won't boot. Has anyone had success being on a custom Rom w global firmware hboot 2.27?
I'm trying to help a buddy of mine. He has a Thunderbolt, issued through work. It is stock, unrooted, locked, never modded. He recently got the ICS OTA update. Phone was functional, but laggy and a bit unstable. He did a factory reset, and initially the phone was fine for a few hours, then it was acting buggy. After a reboot it was fine for a bit, then froze. Usable time kept diminishing with subsequent reboots. He tried another factory reset, and the phone won't boot now. If you power it up, you get the white screen with the HTC logo, then a black screen, and nothing ever happens. I can get to Hboot. I can get to fastboot. Not sure if recovery does anything. I get the recovery screen, then a reboot, and then nothing.
I've been trying to read up on how to fix this, and I'm not sure how to go about it since the phone is currently locked, and won't boot. I looked at the Thunderbolt All In One tool, but it looks like it needs the phone to be booted to start the process.
My end goal is to get back to stock, unrooted, (Gingerbread, then OTA update I suppose), and S-on. But to do that, I need to obtain s-off first. Any info would be greatly appreciated.
I've attached a couple of pics.
Thank you.
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
cujo6801 said:
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
Click to expand...
Click to collapse
Good to know. Thank you. I think because it was employer issued, he's going to try to get a newer device if we can't get it running. But I just had to make some attempt to get it running.
Pm disconnecktie as you should be able to flash via abd beings you can get in to fastboot. He knows a lot about the workings of these phones.
Sent from my ADR6425LVW using Tapatalk 2
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Fastboot does work. I was able to do the "fastboot devices" command before, and saw the phone. I was also able to "fastboot flash zip" the file from post 12 from this tread (link below), BUT even though the file transferred from the computer to the phone, the actual flash failed... I'm assuming because the phone is locked.
http://forum.xda-developers.com/showthread.php?t=2120985&page=2
Try downloading the official ota zip over at the developer section. Put it on the root of your sd card and rename it to PG05IMG. Then run the update through fastboot. I seriously doubt this will solve the problem long term but it may work. I have doubts. I am beginning to think htc released the ota purely for development purposes. More and more people are popping in here with problems similar to this.
Sent from my ADR6400L using Tapatalk 2
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
SoundTech said:
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
Click to expand...
Click to collapse
You need to be rooted to use a rom
Sent from my Nexus 7 using Tapatalk 2
Yeah, that wasn't too swift of me, was it now?
I grabbed the zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2144326
Tried Hboot with the file renamed, same results as previous post. Tried fastboot flash zip, same results as above. No joy.
Going to try to see if HTCDev will get the bootloader unlocked in the current phone state.
Well since the ota isn't a downgrade I thought it may work. If HTC dev is able to unlock his bootloader maybe he can get further.
Sent from my personally built from source CM10.1 N7.
Bootloader is unlocked now, since it was all through fastboot. Still S-on. Tried with the OTA zip still on the SD card as "PG05IMG.zip." It loaded, started to check, started to parse for a moment, then went back to the Hboot screen, reboot got me nowhere. I need to go deal with the rest of life now. I'll try again tomorrow. I appreciate everyone's help today. Thank you.
At this point just s off and install a recovery then you can flash that ROM.
Sent from my Nexus 7 using Tapatalk 2
Use this guide here. Make sure you have plenty of time before hand and FOLLOW THE DIRECTIONS IN ORDER TO A T. It is very important that you don't skip over stuff. This is the only current method to get s off with ics.
Sent from my ADR6400L using Tapatalk 2
Long day at work, but back to it. Making sure the battery is charged up, and downloading files.
I'm looking at a post on ThunderboltForums. Making absolutely sure here: Is THAT the one I should be following?
Follow-up: At the end of step 28, after flashing the .19 ROM, is says to use the All-In-One tool. IF I plan to be stock, unrooted, locked, S-on, it seems I'm there at this point, and I can let the OTA update run. Is that correct?
Thanks again.
Looks like I'm on stock Gingerbread, S-off, re-locked, stock recovery. Heck, it finally boots! I'll see about trying OTA update tomorrow.
Thanks again.
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Huh. I never did use the tool. I went through the steps on the ThunderboltForums post all the way through flashing the .19 ROM. Unless I missed something or did something wrong, before the flash it said I would be re-locked and S-on. After the flash it said the phone should be "back to normal". The next step was the All-In-One tool. But the device actually booted into android with the .19 ROM. That was the first time I saw it boot since I got my hands on it. Perhaps the process in that thread helped repair whatever part of the system was buggered up to begin with?
Regardless, I tried the OTA update, and the phone took the ICS update through Verizon. It seems to be running better now than it did before. It's back in my buddy's possession, and he's in the process of getting his apps and data reinstalled.
He thanked me profusely for getting it running again. So I, in turn, pass his thanks on to everyone here that helped me out, the people that worked to get the Thunderbolt resources to where they are now, and to the forum in general for existing and doing what it does. Thank you all.
I have a rooted Rezound running the OTA ICS. I also have Amon Ra recovery. The newest Firmware update keeps downloading. Once it does the phone shuts off and goes straight to Amon Ra which does not install new firmware. So I reboot the phone and the download process starts all over again. Is there any way to get this new firmware with having to factory reset? Thanks in advance!
xCOOLHWIPx said:
I have a rooted Rezound running the OTA ICS. I also have Amon Ra recovery. The newest Firmware update keeps downloading. Once it does the phone shuts off and goes straight to Amon Ra which does not install new firmware. So I reboot the phone and the download process starts all over again. Is there any way to get this new firmware with having to factory reset? Thanks in advance!
Click to expand...
Click to collapse
If you want the OTA to go you need to flash stock recovery.
- "Is it dark in there?"
drynyks said:
If you want the OTA to go you need to flash stock recovery.
- "Is it dark in there?"
Click to expand...
Click to collapse
Thanks. I was hoping that wouldn't be the case. Do you know of anyway of getting rid of the update? I would rather not have the update than flash back to stock. But my phone shutting off every few hours is pretty annoying. Thanks again.
xCOOLHWIPx said:
Thanks. I was hoping that wouldn't be the case. Do you know of anyway of getting rid of the update? I would rather not have the update than flash back to stock. But my phone shutting off every few hours is pretty annoying. Thanks again.
Click to expand...
Click to collapse
Remove otacerts... Don't remember the exact location and I'm on my phone, a search on that should turn it up.
Sent from my ADR6425LVW using Tapatalk 2
mjones73 said:
Remove otacerts... Don't remember the exact location and I'm on my phone, a search on that should turn it up.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
\etc\security\otacerts.zip
same problem here
hgoldner said:
\etc\security\otacerts.zip
Click to expand...
Click to collapse
I cant seem to find the otacert on my htc resound. I have tried every way to update the new radios and nothing works. I have tried everything but a hard reset and relocking the bootloader. I would rather shut the stupid auto update off. My phone resets at 12:30 am and again at 4am. considering I need the alarm clock on my phone it renders it useless. Any help is appreciated. I am Rooted running stock OTA ICS with Amon Ra.
xander5680 said:
I cant seem to find the otacert on my htc resound. I have tried every way to update the new radios and nothing works. I have tried everything but a hard reset and relocking the bootloader. I would rather shut the stupid auto update off. My phone resets at 12:30 am and again at 4am. considering I need the alarm clock on my phone it renders it useless. Any help is appreciated. I am Rooted running stock OTA ICS with Amon Ra.
Click to expand...
Click to collapse
In confused why don't you just flash stock recovery and let the OTA go? Problem solved. Oh you'd have to relock also.
drynyks said:
In confused why don't you just flash stock recovery and let the OTA go? Problem solved. Oh you'd have to relock also.
Click to expand...
Click to collapse
I have relocked the bootloaderb and gone back to stock 605.12 now it won't download the ota updates. I'm a little stuck on this one
xander5680 said:
I have relocked the bootloaderb and gone back to stock 605.12 now it won't download the ota updates. I'm a little stuck on this one
Click to expand...
Click to collapse
Are you going to settings> software update> check new?
From 605.12 you should get a small OTA first then the big one after that one is done. I just did same procedure in the last week on my wife's phone.
Btw might want to be on WiFi if you aren't already for the download.
Having the same issue here as OP and been searching forums for days looking for help...
First, I'm on 605.13 already, stock ROM, rooted with Amon ra. I realize the steps I need to take but can't find any specifics.
Could someone please spell out the specifics of how to flash the stock recovery, and if I can use the 605.12 RUU to do this being on .13 already. I keep seeing others posting about just renaming a file to recovery.img and pushing using fastboot, but I'm not sure how to obtain the correct file.
Do you relock bootloader first or flash stock recovery first and the relock? BTW I'm s-on stil. Thanks in advance
drynyks said:
Are you going to settings> software update> check new?
From 605.12 you should get a small OTA first then the big one after that one is done. I just did same procedure in the last week on my wife's phone.
Btw might want to be on WiFi if you aren't already for the download.
Click to expand...
Click to collapse
I have tried your suggestions. It goes to download the small update and never downloads it. It says unable to download after about 3minutes.
fixed
xander5680 said:
I have tried your suggestions. It goes to download the small update and never downloads it. It says unable to download after about 3minutes.
Click to expand...
Click to collapse
For some apparent reason the 605.13 update downloaded this afternoon and the 605.14 updated. Its all set after a frustrating 2 weeks of digital torture. thanks to all that helped. I had to scour all these resources and forums to get this done but this is what worked for me. I relocked the bootloader then I used the 605.12 RRU.exe program. After about a day I checked for the updates and they downloaded and installed successfully.
Xander, since you just got this working, can you please confirm the process - I'm about to do this myself and want to verify the steps...
1) Reboot into hboot > fastboot and relock bootloader via fastboot oem lock
2) download 3.14.605.12 RUU.exe (I'm currently on 3.14.605.13)
3) Reboot phone into hboot > fastboot usb
4) run RUU.exe from PC
Is that it? Anything I'm missing here or am I on the right path?
mattman37 said:
Xander, since you just got this working, can you please confirm the process - I'm about to do this myself and want to verify the steps...
1) Reboot into hboot > fastboot and relock bootloader via fastboot oem lock
2) download 3.14.605.12 RUU.exe (I'm currently on 3.14.605.13)
3) Reboot phone into hboot > fastboot usb
4) run RUU.exe from PC
Is that it? Anything I'm missing here or am I on the right path?
Click to expand...
Click to collapse
U have step 1 and step 2 correct. Step 3 would be to connect the phone to the computer and run the 605.12 ruu.exe tool. After that u are now back to a stock phone. After the initial setup of adding your gmail account and contacts you can now go into system settings and check for update. As I stated before my phone would not download the update for some odd reason. I tried it a couple more times without success. Today on a whim I went to check for the update again and it started to download. After the small 6mb file was complete the next update for 605.14 downloaded without anny issues. Make sure you delete any zip files off your external SD card labeled ph98img.zip if u tried that method.
Step1 relock boot loader
Step2 run 3.14.605.12 ruu.exe
Step3 check for updates
Step4 unlock phone if you want to
I hope this helps anyone. Let me know if you have any questions.
Thanks.. Got it! And I got both the 13 and 14 updates almost immediately afterwards. I appreciate the confirmation about the process...
Sent from my ADR6425LVW using Tapatalk 2
xander5680 said:
U have step 1 and step 2 correct. Step 3 would be to connect the phone to the computer and run the 605.12 ruu.exe tool. After that u are now back to a stock phone. After the initial setup of adding your gmail account and contacts you can now go into system settings and check for update. As I stated before my phone would not download the update for some odd reason. I tried it a couple more times without success. Today on a whim I went to check for the update again and it started to download. After the small 6mb file was complete the next update for 605.14 downloaded without anny issues. Make sure you delete any zip files off your external SD card labeled ph98img.zip if u tried that method.
Step1 relock boot loader
Step2 run 3.14.605.12 ruu.exe
Step3 check for updates
Step4 unlock phone if you want to
I hope this helps anyone. Let me know if you have any questions.
Click to expand...
Click to collapse
Can anyone point me to where to find the 3.14.605.12 ruu.exe? I didn't want to spend all day flashing my phone, but ok, I guess I can to get rid of this annoying update.
digitalmofo said:
Can anyone point me to where to find the 3.14.605.12 ruu.exe? I didn't want to spend all day flashing my phone, but ok, I guess I can to get rid of this annoying update.
Click to expand...
Click to collapse
Check the march 10 2013 thread titled rezound in trouble please help. The download link is there. Its under the vigor section.
Here is the RUU I used without issues:
shipped-roms.com/index.php?category=android&model=Vigor
(http removed from link due to forum limitations)
3rd from the bottom...