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
This AM I was:
S-ON
HBOOT: 1.19
Running a version of Fresh
11PM I am:
S-OFF w/ DirtyRacun
HBOOT 1.15.2222
Radio 1.05.11.0606
I have access to Bootloader & I have TWRP 2.4.1.0
I have reformatted internal SDcrd, and I've reformatted internal memory
The phone is blank besides Bootloader and TWRP
Any ROM's I attempt to flash "FAILS"
My attempts at flashing a kernal has been dubious.. I don't know what I'm doing on the kernal front.
Is there a plain Jane Rom out there that will load every time? I'm just not sure where to go from here.
2/20/13 Comment - I forgot to mention, after achieving S-Off with Racun, the phone was basically stock, so I re-rooted with 1.22_RUU_PLUS_ROOT which seemed to flash with no problems and install TWRP. It was at this point I tried to flash (over confidently, I did not make a backup) fresh-evo-lte-5.3.1. The Flash never made it through the process, and restarted. There's where it sits. Now all Rom's very quickly start to flash then, "Fail."
Ffej4ord said:
This AM I was:
S-ON
HBOOT: 1.19
Running a version of Fresh
11PM I am:
S-OFF w/ DirtyRacun
HBOOT 1.15.2222
Radio 1.05.11.0606
I have access to Bootloader & I have TWRP 2.4.1.0
I have reformatted internal SDcrd, and I've reformatted internal memory
The phone is blank besides Bootloader and TWRP
Any ROM's I attempt to flash "FAILS"
My attempts at flashing a kernal has been dubious.. I don't know what I'm doing on the kernal front.
Is there a plain Jane Rom out there that will load every time? I'm just not sure where to go from here.
2/20/13 Comment - I forgot to mention, after achieving S-Off with Racun, the phone was basically stock, so I re-rooted with 1.22_RUU_PLUS_ROOT which seemed to flash with no problems and install TWRP. It was at this point I tried to flash (over confidently, I did not make a backup) fresh-evo-lte-5.3.1. The Flash never made it through the process, and restarted. There's where it sits. Now all Rom's very quickly start to flash then, "Fail."
Click to expand...
Click to collapse
try downgrading TWRP. Some ROMs aren't compatible with the latest release. The Dev has to bake something in the ROM. Version 2.3.1.0 seems to be the "sweet spot". Get it here. Since you're s-off just use the "Download - Bootloader Method:" make sure you rename it to PJ75IMG.zip and place it on the root of your EXTERNAL sdcard.
Similar Issues
I have a similar issue as the OP. I've looked around, and to avoid created a new thread, I'm going to pseudo-bump this into a new topic.
S-ON
HBOOT: 2.09
Running TWRP 2.6
Radio 1.13.11.0830
When stock, I was on 3.17 baseband. I saw that DirtyRacun was had the capability to unlock it, and they (If I read correctly) completely abandoned windows. MeanBean is on 3.16. I'm not adverse to Linux, but I have no idea how to use it past the GUI, and I don't want to install another OS to do something that should be accomplish able on the regular PC.
I have tried DirtyRacun, FacePalm, and Moonshine to get S-Off, no avail on any front unless I'm doing it wrong, which is completely possible.
I have access to Bootloader & I have TWRP 2.6.3.0
I have reformatted internal SDcrd, and I've reformatted internal memory
I am running Mean Bean due to its interesting method of installation, separating the Rom from kernel.
Any other ROM's I attempt to flash "FAILS"
I have flashed a kernel but no ROM I try will install regardless of my attempts. I have used Flash Image GUI from the Play store, but it doesn't seem to help any.
The only reason I am still trying to get a different ROM, MeanBean has no audio. Granted, it plays Pandora, but it has no ringtones, cannot install Amazon MP3, Cannot use Zedge (Crashes every time, not even FC), and cannot see my SD card to use manually loaded music. So I have no music or notification capabilities. No alarm, no text, nothing but the stock ringtone and I think a default e-mail that works about half the time. It also has no loaded sounds, so I cant even set any of the stock ones, which I could suffer until I get the Nexus 5. My Phone, like most people, is my alarm and my life line, so... I really wanna get it back in shape. I appreciate any and all help! I already got help getting out of Limbo once, now I just need one more little piece of info to get comfy again.
Part of your issue is that you're S-on, and you really need to be S-off (fairly simple using the newest Rumrunner method, which is Windows friendly).
As far as MeanBean, I'm not quite sure why you're having those issues with audio, as I and countless others have used that same ROM and have not encountered those issues. What other ROM's have you tried to flash?
Take a look at the top link in my sig. It has some useful info which hopefully you'll find helpful.
If you continue to have issues after exhausting all efforts, shoot me a PM.
Sent from my HTC EVO 4G LTE
Let me start off by saying that I'm a complete idiot and wasn't being very careful.
I have several problems with my Rezound right now and I'll try to be clear and concise. My internal SD card won't mount in the recovery menu, nor HBOOT, therefore I cannot flash PH98img.zip in HBOOT. My external SD will mount, but I'm not sure if the PH98img.zip will work from the external SD because it doesn't show up in HBOOT. My HBOOT reads as follows:
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.10.00000
eMMC-boot
OCT 5 2011,21:18:48
And also, here's a weird thing: My phone will show up in adb devices only when the phone is off or when I'm in the Recovery menu. My phone won't appear in adb devices when I'm in HBOOT menu. I'm running ClockworkMod Recovery v6.0.2.3.
I have tried using a few different ROMs to no avail. I think my main problem as of now is that I cannot access my internal SD card. Before I install a ROM I wipe everything I can think to wipe, cache, dalvik cache, factory reset. Some of the ROMs have the Aroma installer where it asks if I want to wipe on those and I say yes every time. I cannot start my phone because I'm stuck on HTC white screen whenever I try to boot the phone. I've tried using the Old_Firmware_Patch.zip and the GB Firmware Patch.zip. I have had no luck so far. Again, I'm sorry that I'm not exactly sure what I'm doing and I need a bit of help. Thank you and I appreciate any help that you can give.
Additional Information
Prior to this complete failure in my phone I was using an early leak of ICS, one of Newts ROMs. His ROM didn't support 4G and had trouble with a few other things including stock wifi settings. Every time I tried to go to wifi settings the "com.settings.htc" or some such process would crash. So I wanted to update to a newer ICS ROM that hopefully supported 4G and didn't have problems with wifi settings. I thought it would be as simple as loading a ROM onto the external SD and loading it from recovery, but it wasn't that easy. Because I'm S-ON I apparently missed a few steps and forgot that I have to flash PH98img.zip. But now that I cannot access my internal SD card, I cannot flash PH98img.zip as far as I know.
First thing you want to do is get off of Clockwork Mod recovery. It doesn't play well with the Rezound. Go grab Amon Ra and flash v3.16.
Secondly, you can flash a PH98IMG file off the external sd, providing you can read it of course.
I think you are still on GB firmware based on your hboot, not completely sure about that. But it's def an old hboot.
So actually, I would run the RUU and update all your firmware, don't bother flashing Amon Ra first, do that after the RUU. Find it here:
http://androidfiles.org/ruu/?dir=Vigor
Top one, 3.14.605.12. Then after you run that, you can check for and accept the latest OTA that came out a couple weeks ago and then you'll be up to date with the official updates.
You'll need to relock the phone before running the RUU
fastboot oem lock
And save everything you need from the phone first since this will wipe everything and get you back to factory stock.
Then to run the RUU attach the phone to your pc and double click on the exe RUU file. It will do it's thing. Or you can use the following commands in fastboot to get it going:
fastboot oem rebootRUU
fastboot flash zip NameOfZip.zip
Make sure you let it go all the way through. I ran the global RUU and the screen went black for a while then it goes back to finishing up, so if that happens just let it keep going. I think you end up in bootloader when it's done, and it'll ask you if you want to reboot. You should go ahead and boot up and make sure it's working okay.
After you run the RUU you will need to unlock again. Then flash Amon Ra, flash superSU for root (though I think you can just get root via Amon Ra again now) and make a nandroid of stock so you can always go back to this when you run into trouble, then flash a custom ROM if you choose.
That should sort everything out since like I said, it'll be a clean start and you'll get everything updated.
Oh, and the PH98IMG.zip file you have to flash because of being s-on is the kernel for the ROM you are flashing. So know that each PH98IMG.zip file is not the same as the other, the ROM makes the one you need using the kernel that is specifically for that ROM. So you'll either need to pull it out of the ROM and flash via fastboot, download the separate PH98IMG file if there is one in the ROM's thread, or the ROM may make one during the flash and leave the PH98IMG file on your SD card in which case you go to bootloader and accept the update, which will be the kernel.
If you don't flash the kernel then the phone won't boot, it'll just get stuck.
One last thing, I would grab CleanWipe from the Dev section and use that for wiping whenever you change ROMs. It'll really get the job done.
Back to stock now
You, feralicious, are a beautiful person for replying so detailed lol. I got my phone to start up gladly. I just now read your post. Earlier I got it working by following a thread which basically said exactly what you said: relock using fastboot oem lock and then do the lastest RUU. It was a thing of beauty. I as so lost prior to that.
It's good to know that each PH98IMG.zip is different per rom. I had no idea. I'm going to stay stock for a while. It's just nice to finally see that 4g up on the top of my phone after having dealt with 3g only for like 6 months. I'll definitely come back to this site if I have an trouble while attempting to re-root the phone. Thanks so much for your excellent reply.
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 ?
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 !