Complete and utter noob here, recently did the OTA update and noticed my battery life went downhill (using extended battery), also my phone would barely charge while it was powered on. So I went ahead and flashed my phone to CLEANROM 2.2 ICS, and the battery life was even worse.
So now I just want to go back to stock (or as close as possible), but, I was a big dummy and forgot to make a backup of my phone, besides I want to go to where I was before the OTA.
I am downloading Stock Rooted WWE 1.02.605.6 from scottsroms, will I need to take any special steps to get this done?
Thanks in advance and try not to be too hard on me
EDIT: It should be noted that I did try the official HTC exe file but it failed.
update: tried flashing the ROM I mentioned above. I get the HTC screen, then just a blank screen. Tried flashing several kernels from Nils, but I keep getting main ver error. Not really sure where to go from here. Flashed back to CleanROM ICS for now until I can figure this out.
Since you did the OTA you will be on a later mainver than that ROM. I don't know that it matters, but really, the easiest way to get back to stock is to run the RUU.
RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00 .1123r_3161E_9K_QMR_release_233635_signed.exe
Link and info in this thread:
http://forum.xda-developers.com/showthread.php?t=1338916
Alternate download link in this post from pg.6:
http://forum.xda-developers.com/showpost.php?p=22045045&postcount=58
You need to relock the phone and I think you need HTC Sync installed on your computer. Once this runs you will be stock unrooted. Then if you want to root just unlock the phone again - you can use the same unlock code bin you got before - flash Amon Ra and then install su from the Amon Ra developer menu.
EDIT: I didn't notice you flashed an ICS ROM. You may be at a 3.xx.xxx.xx mainver in which case you might not be able to run this RUU. I've seen a couple threads about reverting to stock from ICS, try searching in the thread title for "ICS Stock".
You can check what your mainver is in fastboot using this command:
fastboot getvar all
And you can edit things to trick your phone regarding the mainver... search mainver to find info on that. And if you flash in fastboot it doesn't matter what your mainver is it will flash fine.
feralicious said:
Since you did the OTA you will be on a later mainver than that ROM. I don't know that it matters, but really, the easiest way to get back to stock is to run the RUU.
RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00 .1123r_3161E_9K_QMR_release_233635_signed.exe
Link and info in this thread:
http://forum.xda-developers.com/showthread.php?t=1338916
Alternate download link in this post from pg.6:
http://forum.xda-developers.com/showpost.php?p=22045045&postcount=58
You need to relock the phone and I think you need HTC Sync installed on your computer. Once this runs you will be stock unrooted. Then if you want to root just unlock the phone again - you can use the same unlock code bin you got before - flash Amon Ra and then install su from the Amon Ra developer menu.
EDIT: I didn't notice you flashed an ICS ROM. You may be at a 3.xx.xxx.xx mainver in which case you might not be able to run this RUU. I've seen a couple threads about reverting to stock from ICS, try searching in the thread title for "ICS Stock".
You can check what your mainver is in fastboot using this command:
fastboot getvar all
And you can edit things to trick your phone regarding the mainver... search mainver to find info on that. And if you flash in fastboot it doesn't matter what your mainver is it will flash fine.
Click to expand...
Click to collapse
The ICS roms that are out there now, don't change your mainver. Just the version under software, but your mainver is still the updated OTA one. So flashing that RUU should be fine.
Hey feralicious,
I haven't found that to be completely true about using fastboot and it not mattering what your mainver is.
I have all all kinds of headache in the last two days with mainver errors and they all occurred while trying to flash from fastboot.
All this started after I relocked and ran the ruu/OTA starting from the setup listed in my sig.
Since your mainver were updated during the OTA. I suggest going with cleanrom 1.6.5 based on the OTA. I get decent battery life on the standard battery.
thanks for the help so far guys, will give it another shot today. I was really hoping to revert to the firmware before the OTA since I was having major headaches with charging my battery after the OTA.
If anything this has taught me the true importance of BACKING UP YOUR DATA
also in case it matters, my mainver is 3.10.605.7
finally got cleanrom 1.6 to flash, but was getting mainver error when it was flashing boot.img, but i got it to go through using the android.txt file found in the cleanrom 2.2 ics thread.
jmorton10 said:
Hey feralicious,
I haven't found that to be completely true about using fastboot and it not mattering what your mainver is.
I have all all kinds of headache in the last two days with mainver errors and they all occurred while trying to flash from fastboot.
All this started after I relocked and ran the ruu/OTA starting from the setup listed in my sig.
Click to expand...
Click to collapse
Hm... I heard it's not supposed to care and that's how I got a kernel that was giving me mainver error when flashing via Amon Ra to work. Flashed without issue in fastboot. I guess when that doesn't work I won't panic and I'll try the android-info.txt edit.
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
I need to return a rezound to stock. I purchased it @ retail but have since gotten one via craigs list for nearly half price.
I was running an ICS rom.
First attempts with using RUU in windows resulted in ruu not seeing the phone via USB. The phone was locked @ the time and in fastboot usb mode.
I have tried many of the threads doing things like setting mainversion low etc.. still wont detect the phone . Tried pulling the zip and doing it from hboot but it says hboot mainversion is older.
Im sort of lost and on my last day here. I am currently on cleanrom so it looks kinda like stock, I realize it will still says relocked but i dont want anything else out of place if possible...
Flash the newest ICS CleanRom, Scott has it in his rom to get you back to mainver 1.00.000.00. This will allow you to pull the zip and do it from hboot. But make sure you using the right RUU. If you have hboot 2.11 you have to run RUU 2.01.xxx.xx.
Ok flashed to the latest, now as far as the ruu zip.. im in linux so i cant just grab them from the windows temp folder i have been dl them..
if using the downloads from scotts do i need to do both the smaller 3.xmb one and the larger472.xmb one? do this after re-locking correct?
UPDATE SOLVED
This issue was the ruu file there was the older one once i searched out the new one by name and found it all is well.
Thanks for the clear concise answer EmerikL
Full disclaimer - I am pretty much a noob at rooting devices. I got my first android phone which was a Rezound in december and I only just rooted it in May using the All in 1 tool. I read up on all the steps for unlocking, rooting and flashing ROMs, but I took the easy way out and used to AIO tool. I am S-OFF as well
Having said that, I've been running a few Sense 3.6 ROMs without issues for the last 2 months. I saw that Nils has his Sense 4.0 ROM out and decided to take the plunge at v2.2
Now I decided that I wanted to update to the 3.14.605.10 leak before just in case. I followed the instructions on Nils ROM page. Or at least I thought I did. I screwed up at step 1
I factory reset from bootloader when Nils had clearly mentioned that I needed to reboot into recovery and factory reset, wipe from there. I then went ahead and flashed the 3.14.605.10 leak. It took a while but finally went through.
I didn't realize something was wrong until I tried to reboot into recovery. I couldn't find Amon Ra. I tried to push it more than a few times and it just wasnt working. I kept on getting an error - error: cannot load 'recovery-ra-vigor-3.15-gnm.img'.
Now I tried to install Amon Ra using the All in One tool and got an error there too. Something like 'Remote access denied'.
Finally I installed Quick boot to just check for the heck of it and that's when I got the error that I don't have root access.
So from what I can tell, I have one or possibly both the problems listed below:
> I lost root access when I did the factory reset from bootloader and/or flashed the leaked RUU
> I'm screwing up in my efforts to flash Amon Ra
Since I'm a noob, I could be completely off base and it could be something else, but this is what I could guess. I need help. I need someone to tell me where I messed up. And I guess I really need someone to help me figure out how I get from where I am now, to where I was before i.e. being able to flash ROMs using Amon Ra
I do see that I'm still S-OFF on the bootloader screen, but it used to say 'Tampered' there, but doesnt now.
I hope I've provided all the information for someone to help me. I tried searching the forums but unless I missed it, I didn't find a thread addressing the scenario that I face.
sniles1 said:
Full disclaimer - I am pretty much a noob at rooting devices. I got my first android phone which was a Rezound in december and I only just rooted it in May using the All in 1 tool. I read up on all the steps for unlocking, rooting and flashing ROMs, but I took the easy way out and used to AIO tool. I am S-OFF as well
Having said that, I've been running a few Sense 3.6 ROMs without issues for the last 2 months. I saw that Nils has his Sense 4.0 ROM out and decided to take the plunge at v2.2
Now I decided that I wanted to update to the 3.14.605.10 leak before just in case. I followed the instructions on Nils ROM page. Or at least I thought I did. I screwed up at step 1
I factory reset from bootloader when Nils had clearly mentioned that I needed to reboot into recovery and factory reset, wipe from there. I then went ahead and flashed the 3.14.605.10 leak. It took a while but finally went through.
I didn't realize something was wrong until I tried to reboot into recovery. I couldn't find Amon Ra. I tried to push it more than a few times and it just wasnt working. I kept on getting an error - error: cannot load 'recovery-ra-vigor-3.15-gnm.img'.
Now I tried to install Amon Ra using the All in One tool and got an error there too. Something like 'Remote access denied'.
Finally I installed Quick boot to just check for the heck of it and that's when I got the error that I don't have root access.
So from what I can tell, I have one or possibly both the problems listed below:
> I lost root access when I did the factory reset from bootloader and/or flashed the leaked RUU
> I'm screwing up in my efforts to flash Amon Ra
Since I'm a noob, I could be completely off base and it could be something else, but this is what I could guess. I need help. I need someone to tell me where I messed up. And I guess I really need someone to help me figure out how I get from where I am now, to where I was before i.e. being able to flash ROMs using Amon Ra
I do see that I'm still S-OFF on the bootloader screen, but it used to say 'Tampered' there, but doesnt now.
I hope I've provided all the information for someone to help me. I tried searching the forums but unless I missed it, I didn't find a thread addressing the scenario that I face.
Click to expand...
Click to collapse
Ok, here is the deal. When you ran the RUU it reinstalls the stock recovery. It also leaves you with the stock hboot which will not allow you to use most fastboot commands! bummer. You can find the ICS jounuponut bear hboot (J hboot) and flash that, and then flash the recovery via fastboot. you can find it
http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/
I think it is the 4th one down.
OR.. flash this ph98img which contains the recovery file here:
https://docs.google.com/open?id=0B28uLCcMCyfRZDZVOWNXbE90eWc
ctrl-s to download.
From there flash a custom rom and that should also give you root.
Thanks!
Thank you so much for your reply. I tried out both the things you mentioned but it didn't quite seem to work, mostly because I couldnt get the JHBoot to flash properly. I wasn't sure what I was doing wrong but decided to put in some effort to research this before bothering you with more questions. I think I found the solution.
I went the Unlimited.io site directly and downloaded the Vifor JHBoot for ICS_3.14.605.5 from there
I then followed the instructions they had listed to flash JuopunutBear hboots
'Put the phone in fastboot mode, connected to the pc and enter the following commands
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip '
I then rebooted into bootloader using 'fastboot reboot-bootloader'
And flashed the Amon Ra 3.15 img file you had linked to earlier. That finally seemed to work. Ijust validated it. I managed to flash Amon Ra finally properly. I think I have root back. Flashing Nils Sense 4.0 v.2.2 ROM as I speak.
Thanks so much for the advice. I was really stuck without it. I hope this information helps anyone else if they get stuck the way I did.
topgun1953 said:
Ok, here is the deal. When you ran the RUU it reinstalls the stock recovery. It also leaves you with the stock hboot which will not allow you to use most fastboot commands! bummer. You can find the ICS jounuponut bear hboot (J hboot) and flash that, and then flash the recovery via fastboot. you can find it
I think it is the 4th one down.
OR.. flash this ph98img which contains the recovery file here:
ctrl-s to download.
From there flash a custom rom and that should also give you root.
Click to expand...
Click to collapse
Glad you were able to get things corrected
Sent from my ADR6425LVW using Tapatalk 2
Ok, so long story short, I got fed up with the latest update (4.05.605.14) downloading onto my phone and then failing every time it tried to install itself. Deferring didn't work and it would do it about 5 times a day. So I decided to try and manually install it. That was a mistake, as I think I used a method that was for S-Off instead. I ended up with a phone that wouldn't boot past the 4G LTE screen. I have searched the forums all day and tried everything I could, including trying to install the 3.14.605.12 RUU to take me back to stock. Even locked I can't get it to flash. It checks the PH98IMG.zip but when it installs it fails and says that the "Main Version is older!" So at this point I'm lost. If any of you have any ideas and can help me get my phone back it would be so great.
Thanks in advance.
S-On
Locked
HBOOT: 2.28.0000
Radio: 2.2310.0123r/2.23.10.0124r
Recovery Amon Ra 3.14
You might just need to flash the proper kernel. Pull the boot.img from the ROM based on the OTA (linked below) and flash it and see if that does it. s-off phones don't need to flash kernel separately.
fastboot flash boot boot.img
http://forum.xda-developers.com/showpost.php?p=40949419&postcount=11
no boot
Here on xda is Hassoon's Rezound All-In-One kit #3.2.
It has a tool to set main version for you. And more.
Do it in Fastboot.
michaelbsheldon said:
Here on xda is Hassoon's Rezound All-In-One kit #3.2.
It has a tool to set main version for you. And more.
Do it in Fastboot.
Click to expand...
Click to collapse
Is that going to work for an RUU? The RUU will want to actually change the hboot version to an older one.
I think I saw an RUU feature in Hassoon's Rezound Toolkit as well.
You can always flash just a radio or hboot later if you want.
It does have a Mainver Error Fix listed so it would be worth a try. Also downloading the kernel to try and flash that. Thank you both for the suggestions. Hopefully they keep coming in because I've tried about everything I've seen in the forums to date...
well neither of those worked. The all in one couldn't even find the phone. Guess I severely borked it... :crying:
borkness
Gonna be a lot of work, but you may have to re-educate your phone with
RUU 3.14.xxxx.xx.
After that, install AmonRa recovery. Then mebbe a custom rom or your old nandroid backup.
That's all assuming you can get into fastboot-usb.
I have no problem getting into fastboot usb. It's about the only thing I don't have a problem with. How does one reducate a phone?
There's no RUU that you can run since you have a newer hboot than all of them.
Try flashing the ROM linked in my post #2 above. It's stock based on the OTA. That worked for someone else who was having issues with other methods. Flash the boot.img after you flash the ROM.
Yep
What Feralicious said...
This might help
kirkman81 said:
Ok, so long story short, I got fed up with the latest update (4.05.605.14) downloading onto my phone and then failing every time it tried to install itself. Deferring didn't work and it would do it about 5 times a day. So I decided to try and manually install it. That was a mistake, as I think I used a method that was for S-Off instead. I ended up with a phone that wouldn't boot past the 4G LTE screen. I have searched the forums all day and tried everything I could, including trying to install the 3.14.605.12 RUU to take me back to stock. Even locked I can't get it to flash. It checks the PH98IMG.zip but when it installs it fails and says that the "Main Version is older!" So at this point I'm lost. If any of you have any ideas and can help me get my phone back it would be so great.
Thanks in advance.
S-On
Locked
HBOOT: 2.28.0000
Radio: 2.2310.0123r/2.23.10.0124r
Recovery Amon Ra 3.14
Click to expand...
Click to collapse
Hi, I had similar issues. ROM and Kernel weren't matching. See this thread where I got some great help. Hopefully it gets you on your way too.
http://forum.xda-developers.com/showthread.php?p=41261391&posted=1#post41261391
Thanks for the suggestions, all. I had to switch phones finally because nothing was working but I'll give the last two suggestions a try when I have some time. I'll let you know if anything worked.
Sent from my DROID BIONIC using xda app-developers app
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
brownsfan said:
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
Click to expand...
Click to collapse
So I think I found out what I did. 2.28 is the Global version. I must of rooted that version and flashed roms. I wanted to unroot and get back to stock software version.
Where should I go from here? Is there an RUU for the ICS Global? I can not seem to find one.
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Thingula said:
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I can unlock again and that does get me unstock from the boot screen but still cant get where I want. Hmm.
I wonder if you can fastboot-flash the older kernels, using a computer, then flash the old stock ROM, lock the bootloader, then run an RUU.. Can anyone confirm this? Sounds too simple to work on an HTC phone.
Edit: No, of course that doesn't work. Sorry, I can't really offer any more help.. I'll have to just hope that someone more knowledgeable can take over.
Sent from my ADR6425LVW using xda app-developers app
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Very much so! Thank you. If I could hit the thanks button 10x I would.
Im sure im not the only only to have the Hboot 2.28 issue.
hey man you still around ? i need some help with a situation like this
dust906 said:
hey man you still around ? i need some help with a situation like this
Click to expand...
Click to collapse
I replied to you in your thread.
S-On Locked stock !
mikeyk101 said:
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Click to expand...
Click to collapse
This guide was FREAKING AWESOME. It led me to finally after 2 years go S-Off (wire trick) to do RUU, etc. Have to return phone and have already got replacement. Crossed my fingers and everything looks stock stock stock !