Maybe my mistake was taking part of the moonshine s-off thread when it didn't really apply to me since I was already s-off.
I was on 1.15.604 from December 2012, unlocked bootloader, s-off from first exploit (January?), with Verrine5.9 kernel.
I decided out of curiosity to flash the 2.0.6 fw in the moonshine thread, using adb in Ubuntu.
The terminal showed the zip flashing successfully. I chose to shut down the phone from the bootloader menu.
My DNA rebooted with all my apps, etc, but the firmware was still showing as 1.15.604. When I rebooted a second ti. E
via adb to recovery, now my phone internal sd, and twrp was wiped, I lost my nandroid, and all personal files. I know I should
have backed up the nandroid off pbone.
The end result was a factory fresh phone still running 1.15.604, with a new kernel from the 2.0.6 fw I got from moonshine thread, wi_fi not
working.
I'm not quite sure where you're at, but just use the RUU and get back to stock, then upgrade the firmware to 2.06, use moonshine to get s-off and root.
androidgg81 said:
Maybe my mistake was taking part of the moonshine s-off thread when it didn't really apply to me since I was already s-off.
I was on 1.15.604 from December 2012, unlocked bootloader, s-off from first exploit (January?), with Verrine5.9 kernel.
I decided out of curiosity to flash the 2.0.6 fw in the moonshine thread, using adb in Ubuntu.
The terminal showed the zip flashing successfully. I chose to shut down the phone from the bootloader menu.
My DNA rebooted with all my apps, etc, but the firmware was still showing as 1.15.604. When I rebooted a second ti. E
via adb to recovery, now my phone internal sd, and twrp was wiped, I lost my nandroid, and all personal files. I know I should
have backed up the nandroid off pbone.
The end result was a factory fresh phone still running 1.15.604, with a new kernel from the 2.0.6 fw I got from moonshine thread, wi_fi not
working.
Click to expand...
Click to collapse
use the facepalm method to get back to stock, then take the update to 2.06 then moonshine
re-flash a kernel... if you can
.torrented said:
re-flash a kernel... if you can
Click to expand...
Click to collapse
Thanks, I just used this as an excuse to run 10.2 with your sweep2wake, looks pretty fast right now.
as you did
how to deleted this post?
androidgg81 said:
Maybe my mistake was taking part of the moonshine s-off thread when it didn't really apply to me since I was already s-off.
I was on 1.15.604 from December 2012, unlocked bootloader, s-off from first exploit (January?), with Verrine5.9 kernel.
I decided out of curiosity to flash the 2.0.6 fw in the moonshine thread, using adb in Ubuntu.
The terminal showed the zip flashing successfully. I chose to shut down the phone from the bootloader menu.
My DNA rebooted with all my apps, etc, but the firmware was still showing as 1.15.604. When I rebooted a second ti. E
via adb to recovery, now my phone internal sd, and twrp was wiped, I lost my nandroid, and all personal files. I know I should
have backed up the nandroid off pbone.
The end result was a factory fresh phone still running 1.15.604, with a new kernel from the 2.0.6 fw I got from moonshine thread, wi_fi not
working.
Click to expand...
Click to collapse
how to fix this problem ?
Related
Alright, so I've got an S-On rooted Rezound and I'm stuck in the boot loop. YES I've read all the posts about logging in and dialing *#etc and also to go into Mobile Network and switch to LTE/CDMA, but I can't dial anything because the phone cuts off before I get a chance, and the LTE switch does nothing. I've tried flashing several different kernels, using the adb method and the PH98IMG methods, I've tried installing several different ROMS, I've done at least 10 different wipes/factory resets, I boot my phone without the cover, SIM card and without the SD card..and I'm still stuck in this boot loop. Someone please help a noob
---- EDIT WITH SOLUTION ----
Here's my "solution" to this issue. I'm sure it's located somewhere in these forums, but I couldn't find it so I imagine others can't either. Essentially, you're going to have to S-Off. Here's the solution:
I believe my recovery started acting funny after I failed to S-Off properly the first time. Amon Ra was all gimmicky and said stuff like "E: can't find cache" and reinstalling the recovery/wiping everything (and I mean everything: external SD, internal SD, cache, partioning SD card etc..) wasn't working. I tried re-installing Amon Ra through command prompt with the adb, I tried reinstalling my ROMS but my phone wasn't having it.
It got to the point all I could boot into was a white HTC screen, so I then tried out Twrp's 2.1 Touchscreen (I wasn't S-Off yet) recovery (I don't have enough posts to post a link yet ) which INITIALLY reported the same "E: can't find cache" errors as Amon Ra, BUT when I wiped my files in Twrp it seemed to actually fix them...I'm not sure exactly what I wiped or formatted that fixed the "E: can't find mount/cache" issues, so try everything.
So my ROM installed but I was still stuck on the white HTC logo. This is where I INSTALLED A NEW KERNEL THROUGH ADB. I wish I knew which kernel I installed, but I have like 10 and I just picked a random one. The point is if you're still stuck at a white HTC screen, install a new kernel.
So I got a recovery on the phone, and then I tried to S-Off again but I didn't have a good ROM installation so that was hanging at the HTC white screen. I then installed CleanROM DE 1.4 and I was able to boot into it, but ran into my initial problem of it crashing after dialing a number and entering infinite reboot. However, it would stay on just long enough for me to run ControlBear's program to S-Off.
So I S-Offed, I downloaded the Gingerbread RUU (the .exe version for Windows), I installed it, and now I can dial numbers and I'm all goodie again. Unfortunately, I honestly think the only way I was escaping my trouble was doing an S-Off, unless they leak a Ice Cream Sanwhich executable for Windows.
TL;DR Install Twerp 2.1 through adb, wipe everything, install CleanROM DE 1.4, install kernel S-Off, run Gingerbread RUU .exe
autotuneuser said:
Alright, so I've got an S-On rooted Rezound and I'm stuck in the boot loop. YES I've read all the posts about logging in and dialing *#etc and also to go into Mobile Network and switch to LTE/CDMA, but I can't dial anything because the phone cuts off before I get a chance, and the LTE switch does nothing. I've tried flashing several different kernels, using the adb method and the P87etc methods, I've tried installing several different ROMS, I've done at least 10 different wipes/factory resets, I boot my phone without the cover, SIM card and without the SD card..and I'm still stuck in this boot loop. Someone please help a noob
Click to expand...
Click to collapse
Have you tried running a RUU to put it back to factory like you just bought it?
I can't tell you how many times I've had to do that to fix stuff.
Magestic12 said:
Have you tried running a RUU to put it back to factory like you just bought it?
I can't tell you how many times I've had to do that to fix stuff.
Click to expand...
Click to collapse
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
autotuneuser said:
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
Click to expand...
Click to collapse
It is if you're s-on. Also, what did you mean by "P87etc," are you flashing the files properly?
autotuneuser said:
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
Click to expand...
Click to collapse
People say a lot of things are impossible, most have the virtue of never being tried.
This is the one I used to fix mine when I screwed up the partitions on my phone. I will warn you, the link in the thread takes you to another site & you have to sign up to download it. Its completely free & legit, but it won't let you download unless you register which is STUPID!
http://forum.xda-developers.com/showthread.php?p=25664508
Let me know if that helps
Oh & BTW I was & still am on the ICS leaks when I did this, so you'll be fine. You will lose everything on your phone though, because it wipes everything. But if you can't use it, that's not really an issue I guess.
tekhna said:
It is if you're s-on. Also, what did you mean by "P87etc," are you flashing the files properly?
Click to expand...
Click to collapse
The PH98IMG file. And I believe I'm flashing the properly..I do it twice; flashboot in adb, it tells me success, I then flash again right there, and then I reboot back to the bootloader and flash again so I do it 3 times in total.
I'm downloading the Vigor executable now. It's going to take a while but I'll report back with my results.
autotuneuser said:
The PH98IMG file. And I believe I'm flashing the properly..I do it twice; flashboot in adb, it tells me success, I then flash again right there, and then I reboot back to the bootloader and flash again so I do it 3 times in total.
I'm downloading the Vigor executable now. It's going to take a while but I'll report back with my results.
Click to expand...
Click to collapse
PH98IMG is not going to help you in this situation. You are going to have to download & run the RUU that I linked in the previous post. Trust me on this, not only have I already tried that before, I've blown my phone up enough times to know.
Magestic12 said:
PH98IMG is not going to help you in this situation. You are going to have to download & run the RUU that I linked in the previous post. Trust me on this, not only have I already tried that before, I've blown my phone up enough times to know.
Click to expand...
Click to collapse
Ok, I went to use the RUU and at first I got error 150, so I read somewhere I should lock my bootloader, so I relocked and now I get error 140, whcih is bootloader verision error. I think that's because I'm on ICS with S-On right? Is there any ICS RUU I can use to restore my phone? I downloaded Vigor_Stock_Doedexed_3.14.605.5 before but it still wasn't working for me.
autotuneuser said:
Ok, I went to use the RUU and at first I got error 150, so I read somewhere I should lock my bootloader, so I relocked and now I get error 140, whcih is bootloader verision error. I think that's because I'm on ICS with S-On right? Is there any ICS RUU I can use to restore my phone? I downloaded Vigor_Stock_Doedexed_3.14.605.5 before but it still wasn't working for me.
Click to expand...
Click to collapse
And as far as this goes yeah you can't use the .exe if your on ICS firmware with s-on and there are no available .exe's for ICS
Sent from my ADR6425LVW using Tapatalk 2
Unless you are already on the gingerbread build, and it sounds like your not, if you are s-on, it simply will not work. My suggestion is to download the latest leak and that should get you going. If it were me, and I aleady did it, download the latest leak here: http://android.thesmallprint.org/ICS.LEAK.3.14.605.5_PH98IMG.zip. Rename it PH98IMG.zip and put it on your external sd card. Should take less than 10 mins to download. Reboot into bootloader and let hboot install it. Make sure you are locked or relocked. After that is installed either delete or change the name of that file. Reboot into bootloader, unlock, and install either amon ra or tpwr and you can reinstall that rooted rom.
what he said
mikey's comments just previous are totally right, but after install, i would recommend
a factory reset, maybe even twice.
your bootloop problem should be cured then...
I was on the latest ICS firmware running an ICS ROM when I had to run the RUU I gave the link for & it worked fine for me.
Here's my suggestion & you can take it for what its worth.
I would download the latest HBoot & Radios & flash them.
Then if you can get into recovery, wipe everything, manually wipe the system, boot, etc. Then after that try running the RUU.
I just did this earlier in the week & it worked fine & my phone was all screwed up because the partitions were mounting to the wrong places & just all messed up.
I am by no means a dev or an expert, I'm just telling you what I did.
WHATEVER YOU CHOSE, YOU DO AT YOUR OWN RISK, but I don't see where you really have a choice.
Let me know if I can be of anymore help as I know what its like to have a phone that's freaking out on you. You can PM me or post here which ever you prefer. If after that we still can't get it fixed, we'll go find a dev to help us.
mikeyk101 said:
Unless you are already on the gingerbread build, and it sounds like your not, if you are s-on, it simply will not work. My suggestion is to download the latest leak and that should get you going. If it were me, and I aleady did it, download the latest leak here: . Rename it PH98IMG.zip and put it on your external sd card. Should take less than 10 mins to download. Reboot into bootloader and let hboot install it. Make sure you are locked or relocked. After that is installed either delete or change the name of that file. Reboot into bootloader, unlock, and install either amon ra or tpwr and you can reinstall that rooted rom.
Click to expand...
Click to collapse
Well now my recovery is saying it can't mount various things like "E: can't mount b dev/block/ blah blah"
And I tried flashing my ROM through Amon recovery but it's saying it can't open the file because it's (bad). I formatted the SD card and I'm still getting the issue. Any ideas?
Did you download the one from the link? You don't flash that PH98IMG.zip in recovery, you boot up into bootloader and let hboot find it. If when you get to your bootloader and it is fastboot, use your volume key and select on bootloader option. Then hboot will find it and ask you if you want to install it. Install it. After that, you will then need to reinstall either amon ra or the other but stay away from clockworkmod. But to reinstall the recovery, you will have to unlock again.
mikeyk101 said:
Did you download the one from the link? You don't flash that PH98IMG.zip in recovery, you boot up into bootloader and let hboot find it. If when you get to your bootloader and it is fastboot, use your volume key and select on bootloader option. Then hboot will find it and ask you if you want to install it. Install it. After that, you will then need to reinstall either amon ra or the other but stay away from clockworkmod. But to reinstall the recovery, you will have to unlock again.
Click to expand...
Click to collapse
I did install in hboot. I then installed Amon so I could flash the ROM and that's what's giving me all those errors.
If all you are after is stock and rooted, try looking at this one: http://forum.xda-developers.com/showthread.php?t=1642217
Since you ran the PH98IMG that I directed you to, you are now on ICS. So follow the directions in that thread for "S-On and ICS".
Installation for S-ON Devices on ICS firmware
•Copy ROM to SD Card AND PH98IMG.zip to ROOT of SD Card
•Reboot to recovery
•wipe data / Factory Reset
•Flash ROM
•Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
•Reboot
•Profit!
Edit: The only change I would recommend is to hold off putting that PH98IMG file from that thread on the sd card right away. You will have a hard time getting to recovery if you have that on the card. I would suggest following all the instructions up to and including "Flash ROM". Then I would "return" back to the main Amon Ra screen, make sure you have the data cable connecting your phone to the computer, select "USB-MS Toggle", then select the SD Card, and that will allow you to copy the PH98IMG file to the SD card. Then continue with the rest of the directions. If you do this right, you should be ok.
mikeyk101 said:
If all you are after is stock and rooted, try looking at this one: http://forum.xda-developers.com/showthread.php?t=1642217
Since you ran the PH98IMG that I directed you to, you are now on ICS. So follow the directions in that thread for "S-On and ICS".
Installation for S-ON Devices on ICS firmware
•Copy ROM to SD Card AND PH98IMG.zip to ROOT of SD Card
•Reboot to recovery
•wipe data / Factory Reset
•Flash ROM
•Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
•Reboot
•Profit!
Edit: The only change I would recommend is to hold off putting that PH98IMG file from that thread on the sd card right away. You will have a hard time getting to recovery if you have that on the card. I would suggest following all the instructions up to and including "Flash ROM". Then I would "return" back to the main Amon Ra screen, make sure you have the data cable connecting your phone to the computer, select "USB-MS Toggle", then select the Internal_sd, and that will allow you to copy the PH98IMG file to the SD card. Then continue with the rest of the directions. If you do this right, you should be ok.
Click to expand...
Click to collapse
It's the actual recover I believe to be giving me the errors, but I'll try what you said in about 2 days (I need to study for finals). It might be because I tried to S-Off and I installed all of that guys software and it might be making the phone act funny. I'll be much more descriptive about my errors when I post back in 2 days.
I fixed it!!
Ok, so I finally got it working, I'll try to detail my steps for anyone else who ran into similar issues:
I believe my recovery started acting funny after I failed to S-Off properly the first time. Amon Ra was all gimmicky and said stuff like "E: can't find cache" and reinstalling the recovery/wiping everything (and I mean everything: external SD, internal SD, cache, partioning SD card etc..) wasn't working. I tried re-installing Amon Ra through command prompt with the adb, I tried reinstalling my ROMS but my phone wasn't having it.
It got to the point all I could boot into was a white HTC screen, so I then tried out Twrp's 2.1 Touchscreen (I wasn't S-Off yet) recovery (I don't have enough posts to post a link yet ) which INITIALLY reported the same "E: can't find cache" errors as Amon Ra, BUT when I wiped my files in Twrp it seemed to actually fix them...I'm not sure exactly what I wiped or formatted that fixed the "E: can't find mount/cache" issues, so try everything.
So my ROM installed but I was still stuck on the white HTC logo. This is where I INSTALLED A NEW KERNEL THROUGH ADB. I wish I knew which kernel I installed, but I have like 10 and I just picked a random one. The point is if you're still stuck at a white HTC screen, install a new kernel.
So I got a recovery on the phone, and then I tried to S-Off again but I didn't have a good ROM installation so that was hanging at the HTC white screen. I then installed CleanROM DE 1.4 and I was able to boot into it, but ran into my initial problem of it crashing after dialing a number and entering infinite reboot. However, it would stay on just long enough for me to run ControlBear's program to S-Off.
So I S-Offed, I downloaded the Gingerbread RUU (the .exe version for Windows), I installed it, and now I can dial numbers and I'm all goodie again. Unfortunately, I honestly think the only way I was escaping my trouble was doing an S-Off, unless they leak a Ice Cream Sanwhich executable for Windows.
TL;DR Install Twerp 2.1 through adb, wipe everything, install CleanROM DE 1.4, install kernel S-Off, run Gingerbread RUU .exe
Hi, everyone. I am sure someone is going to shaking their heads at my idiocy after reading this post but I hope someone can save me. So I went to all that trouble to update my phone to ICS from Gingerbread and retain S-off and rooted. After playing with it a little, I decided I like my previous state better. Before I updated my phone, I backed up my phone using the clockworkmod recovery that was installed using revolutionary's tool. That was also the recovery that I flashed after I updated to ICS. So I figure all I have to do was restore the backup. I boot into recovery and all I did was select "backup\recovery" and then the date that I did the backup. The restore finished and I rebooted my system. Everything should be fine now, right? Wrong! As the phone bootup, it would read HTC then Sprint before rebooting again and again. I never reach the lockscreen. Right now I can still reach recovery through the bootloader but that is it.
So how can I recover? Was I supposed to wipe something before restoring? If so, which options am i supposed to use (wipe all data?) because specific details will prevent me from making another bonehead move. If not, what do I do?
Problem is, I got impatient to downgrade from ICS and never bothered to backup after the update to ICS. Just a reminder to all that "backup, backup and backup). So I am stucked right now and need help. HELPPPPPPP......
Tommy
I can see from my bootloader that it is still HBoot 1.58 instead of HBoot 1.4 before the ICS update. Would flashing the boot.img from the clockworkmod backup work?
xionchen4628 said:
Hi, everyone. I am sure someone is going to shaking their heads at my idiocy after reading this post but I hope someone can save me. So I went to all that trouble to update my phone to ICS from Gingerbread and retain S-off and rooted. After playing with it a little, I decided I like my previous state better. Before I updated my phone, I backed up my phone using the clockworkmod recovery that was installed using revolutionary's tool. That was also the recovery that I flashed after I updated to ICS. So I figure all I have to do was restore the backup. I boot into recovery and all I did was select "backup\recovery" and then the date that I did the backup. The restore finished and I rebooted my system. Everything should be fine now, right? Wrong! As the phone bootup, it would read HTC then Sprint before rebooting again and again. I never reach the lockscreen. Right now I can still reach recovery through the bootloader but that is it.
So how can I recover? Was I supposed to wipe something before restoring? If so, which options am i supposed to use (wipe all data?) because specific details will prevent me from making another bonehead move. If not, what do I do?
Problem is, I got impatient to downgrade from ICS and never bothered to backup after the update to ICS. Just a reminder to all that "backup, backup and backup). So I am stucked right now and need help. HELPPPPPPP......
Tommy
Click to expand...
Click to collapse
xionchen4628 said:
I can see from my bootloader that it is still HBoot 1.58 instead of HBoot 1.4 before the ICS update. Would flashing the boot.img from the clockworkmod backup work?
Click to expand...
Click to collapse
You need to downgrade your bootloader to something lower than 1.58 if you want to run ROM's based on GB or AOSP. You can go back to 1.4 if you want, or the Jbear GB (1.50.5050) version. You should leave the rest of your firmware at the ICS level.
The bootloaders can be found in this post. Download the one you want, put it in the root of your SD card, rename it to PG86IMG.zip and flash it from the current bootloader. You should then be able to boot your CWM backup, and don't forget to delete the PG86IMG.zip file from the root of your SD card after you flash it.
ramjet73
Thanks, ramjet. My phone is back to the state that it was in before my ICS update. Sorry for all the work that you put in to help me upgrade in the first place. Since I restore from my GB backup, all I did was flash the bootloader and everything went to normal. If somewhere done the line, I decided to update to ICS again, I know all the steps that need to be done (thanks to you and all the users who provided the various files). Thanks again. I love this community!
ramjet73 said:
You need to downgrade your bootloader to something lower than 1.58 if you want to run ROM's based on GB or AOSP. You can go back to 1.4 if you want, or the Jbear GB (1.50.5050) version. You should leave the rest of your firmware at the ICS level.
The bootloaders can be found in this post. Download the one you want, put it in the root of your SD card, rename it to PG86IMG.zip and flash it from the current bootloader. You should then be able to boot your CWM backup, and don't forget to delete the PG86IMG.zip file from the root of your SD card after you flash it.
ramjet73
Click to expand...
Click to collapse
xionchen4628 said:
Thanks, ramjet. My phone is back to the state that it was in before my ICS update. Sorry for all the work that you put in to help me upgrade in the first place. Since I restore from my GB backup, all I did was flash the bootloader and everything went to normal. If somewhere done the line, I decided to update to ICS again, I know all the steps that need to be done (thanks to you and all the users who provided the various files). Thanks again. I love this community!
Click to expand...
Click to collapse
Well the rest of firmware (other than the hboot) is now updated to the Sprint ICS 2.89.651.2 level, so you should be able to run the ICS ROM's that don't require the 1.58 bootloader and there are quite a few of those. So it wasn't a waste of time and effort.
ramjet73
I've been at this for about 8 hours now and finally decided that I need help:
Background: I rooted, unlocked, and installed TWRP using RegawMOD. Began reading up on meanROM, read that I should have the latest firmware installed, didn't realize that what I had 1.13.651.1 would have been sufficient (if I had realized this was sufficient enough of firmware version I probably wouldn't be writing this post). I followed the S-On directions because I never performed S-Off. I followed the link, http://forum.xda-developers.com/showpost.php?p=31520093&postcount=11730, followed instructions. I made the backup, but I'm not entirely sure where it got saved to.
I re-locked the phone, and unrooted as well. (Did this happen to get rid of that backup??) Looking back, I don't know why I unrooted when the steps don't call for it. I continued on and installed the 2.13 RUU. Upon completion I was thinking I could just use RegawMOD to unlock, root, and install TWRP again. It didn't work as planned. I could never get RegawMOD to work like it had before so it never unlocked, rooted, or installed TWRP.
I eventually was able to use HTCdev to unlock the phone and followed the instructions from here: http://htcevohacks.com/htc-evo-4g-lte-root/how-to-root-htc-evo-4g-lte-unlock-bootloadertwrp-recovery/. I got to step 29 and I couldn't ever "see" or find the .zip file.
.
Question: Where do I go from here? I realized I shouldn't have updated to 2.13 and it seems from what I've read is that trying to downgrade back to my original 1.13.651.1 would instantly brick my phone. I would really like to be able to root my phone and flash meanROM. Any help in being able to achieve that would be more than welcomed!
Currently:
firmware is 2.13.651.1
Unlocked
I don't believe I am rooted since I don't have SU, but on bootloader it does state that my phone is tampered, typically meaning it's rooted I believe.
I have TWRP v2.1.8 installed, from following the htcevohacks instructions, but cannot find .zip files that I've put onto my SD card.
Many thanks!
I was able to figure it out!
I don't know why or how, but all of a sudden I was able to see everything on my SD card including the zip files. I then rooted by installing CWM-SuperSU-v0.87.zip. Downloaded goomanager, upgraded TRWP to 2.3.1, rebooted into recovery, backed up, factory reset, cleared cache, cleared dalvik cache, rebooted system. Rebooted back into recovery, and installed meanrom v5.8 without issue.
The question that remains is why I couldn't originally see full contents of my SD card?
Zips get saved to internal sd by default, you were probably looking on external sd
LtEVO
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 !
Hi. I attempted to root my device. I'm S-ON with Hboot 3.19
I was successful in unlocking the bootloader and installing a custom recovery. I then flashed SuperSU 2.02.
I rebooted and clicked SuperSU. It tells me there is no SU binary installed, if i upgraded to Android 4.3 i need to manually re-root it.
I thought fixing permissions in recovery would do the trick. Most of my apps are gone now, and i still don't have root.
Any suggestions?
I installed a newer version of SuperSU and was able to obtain root.
Most of my apps are still gone, since i changed the permissions.
Does anyone have a twrp stock rom backup or a stock rom i can flash?
I don't want to RUU because of fears of bricking my device. But if doing that is the only way to go back to stock, i might as well. I don't mind redoing the root process, as long as i have a working phone.
I went ahead and relocked the bootloader but didn't flash the stock recovery (oops), and i'm attempting to RUU, but it's stuck at 14% and my phone just says htc, no green bar. I hope i didn't just brick my phone.
jackzilla241 said:
I went ahead and relocked the bootloader but didn't flash the stock recovery (oops), and i'm attempting to RUU, but it's stuck at 14% and my phone just says htc, no green bar. I hope i didn't just brick my phone.
Click to expand...
Click to collapse
with exe ruu, be sure other programs in windows isn't talking to the phone of the ruu utility will hang. This means uninstalling things like Eclipse, HTC Sync, etc.
jackzilla241 said:
I went ahead and relocked the bootloader but didn't flash the stock recovery (oops), and i'm attempting to RUU, but it's stuck at 14% and my phone just says htc, no green bar. I hope i didn't just brick my phone.
Click to expand...
Click to collapse
You don't need stock recovery to RUU, typically (only for OTA, a different animal altogether).
RUU just gets stuck sometimes. Disconnect the phone, and start again (as scary as that sounds).
Use Win7 and USB 2.0 for the best results.