Related
I had followed this video ht tp://w ww.youtub e.com /watch?v=hQtUxEL8pd8 and did everything correctly. When I go to boot my phone up it shows the blue android boot animation then the green HTC animation then restarts.
Hboot 1.57
Somehow my recovery got deleted.
Clockworkmod recovery is installed.
I just don't know what to do
Is there a way I can just undo everything and go back to the stock rom?
Edit: Tried ViperROM and it's doing the exact same thing.
Make sure you are wiping everything except sdcard and then flash the rom. Maybe even try changing recoveries to 4ext.
Sent from my PG86100 using Tapatalk 2
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Jsparta26 said:
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Click to expand...
Click to collapse
I'm S-on, will it matter? And also I do mean 1.57. And one more thing. Does it matter if I boot up into a recovery using the command prompt? Also I'm not sure what kernel it is. I guess the one that's in the zip folder? Also sorry for slow responses I've been working days. Any chance you'll be on tomorrow around 7pm central?
Update: I reformatted everything and tried reinstalling Viperrom through CWM but no dice still boots up and resets. Got 4ext installed. Working from there.
Update: 4EXT is the best recovery I've ever seen and I'm never using CWM again.
Update: I installed VIperROM through 4ext and it's still restarting itself.
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Jsparta26 said:
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Click to expand...
Click to collapse
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I? Also i youtubed bootloop to see if it is really what's wrong and I came up with this video. ht tp ://www .y outube.co m/watch?v=OKXTD1-fqbc and my phones doing more than that. It's booting up all the way then once the screen and dock begins to load it restarts.
IAnb3rlin said:
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I?
Click to expand...
Click to collapse
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Jsparta26 said:
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Click to expand...
Click to collapse
How do I flash a kernel? I'm not really sure what one is, I just know it's really important.
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Jsparta26 said:
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Click to expand...
Click to collapse
I formatted everything using 4ext and installed a rom i also flashed the boot img just incase and it still restarted.
Here's the steps I took.
1. Format everything.
2. Download the.zip file and copy to SD card.
3. Load the recovery and enable smartflash.
4. Installed the rom.
5. Flashed the boot.img
6. Also tried without flashing the boot img.
And just to clarify. I'm installing ViperROM. And I only need the .zip file, correct?
I ended up using RUU to fix it and go back to the stock rom/ect, Then locked the bootloader unlocked it and flashed superuser and rooted it then got s-off using the wire trick. But after I rebooted it keeps taking me back to the jbear bootup logo and when I try to flash a recovery it doesn't load I just get the htc logo then jbear logo then it restarts. I followed this guide.htt p://w ww.yo utube.co m/ watch?v =tRj47iFQvbE I found here on the xda forums.
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Jsparta26 said:
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Click to expand...
Click to collapse
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
IAnb3rlin said:
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
Click to expand...
Click to collapse
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Jsparta26 said:
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Edit: just realized your using virgin mobile correct? I believe the reason your phone kept bootlooping with viper ROM was because of hboot. Try flashing a different hboot with the same method as the ruu and recovery.
Click to expand...
Click to collapse
I downloaded root checker and apparently I'm not root anymore. Yes I'm VM. I'm trying to rename the recovery and update it using the SD card now.
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
IAnb3rlin said:
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
Click to expand...
Click to collapse
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Jsparta26 said:
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Click to expand...
Click to collapse
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
IAnb3rlin said:
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
Click to expand...
Click to collapse
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Jsparta26 said:
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Click to expand...
Click to collapse
I just ended up unlocking the boot loader again and installing the recovery that way. Then saw this.. oh well lol. I really do appreciate the help. . I'm going to try to install viperrom again, and double backup this time! I'll let you know how it goes.
Hey all, just received a replacement rezound under warranty due to the charge port being all muffed up, and of coarse the first thing was unlock via htcdev which worked fine.
Here is the issue.. when trying to flash amonra via fastboot or PH98IMG.zip in bootloader it won't flash. For fastboot it says "unknown error" and as a PH file in bootloader it says "parsing..." for a few seconds then disappears without flashing anything. I've re-downloaded and checked md5's and still get the same errors.
My last rezound was s-off and that whole process was quick and painless and I don't understand why the same procedure I used on my last rezound isn't working now.
Any help would be greatly appreciated.
zac41189 said:
Hey all, just received a replacement rezound under warranty due to the charge port being all muffed up, and of coarse the first thing was unlock via htcdev which worked fine.
Here is the issue.. when trying to flash amonra via fastboot or PH98IMG.zip in bootloader it won't flash. For fastboot it says "unknown error" and as a PH file in bootloader it says "parsing..." for a few seconds then disappears without flashing anything. I've re-downloaded and checked md5's and still get the same errors.
My last rezound was s-off and that whole process was quick and painless and I don't understand why the same procedure I used on my last rezound isn't working now.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
What firmware is on the device?
hgoldner said:
what firmware is on the device?
Click to expand...
Click to collapse
ota 3.14.605.12 710rd.
Can you flash in fastboot usb? (And, to be perfectly clear to avoid a dumb question, does hboot reflect that you are unlocked?)
hgoldner said:
Can you flash in fastboot usb? (And, to be perfectly clear to avoid a dumb question, does hboot reflect that you are unlocked?)
Click to expand...
Click to collapse
indeed *** unlocked *** is displayed at the top on hboot. and ive tried "fastboot flash recovery (nameofrecovery.img) with nameofrecovery changed to what i have it saved as and no luck. even tried relocking and ruuing too just to make sure it wasnt the software messing everything up.
Can't remember but can you try to S-OFF first? (It's been so long, but I can't remember whether you have a custom recovery already on).
Ah, one other stupid thing.... have you tried a different sdcard?
hgoldner said:
Can't remember but can you try to S-OFF first? (It's been so long, but I can't remember whether you have a custom recovery already on).
Ah, one other stupid thing.... have you tried a different sdcard?
Click to expand...
Click to collapse
I was thinking about the sd card being the issue but it installed an ruu via ph98img.zip perfectly fine bit its worth a shot. And on unlimited.io's site they say you need to be completely stock with root and as far as I know amonra is the only way to root on a stock ruu. I managed to s-off tho after using hasoon's tool to flash amonra. I'm now completely stock again after ruuing back to gb then accepting ota
so I'll try flashing amonra again and report back. Thank you for your help!
Sent from my ADR6425LVW using xda premium
You can install any custom recovery and use it to flash SuperUser. The root option in Amon Ra doesn't usually work by itself anyway.
shrike1978 said:
You can install any custom recovery and use it to flash SuperUser. The root option in Amon Ra doesn't usually work by itself anyway.
Click to expand...
Click to collapse
Oh ok thats good to know actually. just cant seem to install any custom recoveries lol. i chose to install amon ra 3.15 with hasoons tool and for some reason i have 3.06 installed.. dont know how or why but i do. tried to install 3.15 with his toolkit again and got the stupid error again. i dont know what to do at this point lol. never had this problem with the last rezound. i am s-off now but do not have the recovery i want installed.
should i try ruu'ing again and start fresh?
and for what its worth i do have the jb hboot installed just to see if that was the issue. had to use fastboot commands to install it so i dont think thats the issue. i think its the download for amonra 3.15 i have. if anyone has a personal copy of 3.15 that is confirmed working and is willing to share it itd be greatly appreciated.
To use the fastboot commands you must be unlocked. With the parsing error. That will sometimes happen if you have a file called "update.zip" on your sdcard. Try seeing if you have one of those files. If your HBOOT does say s-off. Flash the GB RUU. Just so you can verify everything has changed. and then restart with the ICS RUU then flash a recovery. This time not with that tool.
Flyhalf205 said:
To use the fastboot commands you must be unlocked. With the parsing error. That will sometimes happen if you have a file called "update.zip" on your sdcard. Try seeing if you have one of those files. If your HBOOT does say s-off. Flash the GB RUU. Just so you can verify everything has changed. and then restart with the ICS RUU then flash a recovery. This time not with that tool.
Click to expand...
Click to collapse
Thank you for the response. i tested to see if i really did have s-off by doing just that. ruu'd back to gb without a hitch. then accepted the ota. so im thinking ill just ruu the ota (3.14.605.12) and see what happens. and im with you on not using the tool again. ive heard really good things about it but never used it personally until today. my old method worked well i just didn't know what else to do at that point lol
zac41189 said:
Thank you for the response. i tested to see if i really did have s-off by doing just that. ruu'd back to gb without a hitch. then accepted the ota. so im thinking ill just ruu the ota (3.14.605.12) and see what happens. and im with you on not using the tool again. ive heard really good things about it but never used it personally until today. my old method worked well i just didn't know what else to do at that point lol
Click to expand...
Click to collapse
To s-off you got to do the wire trick. But RUU then don't use the tool. lol Lets us now if it works out.
Flyhalf205 said:
To s-off you got to do the wire trick. But RUU then don't use the tool. lol Lets us now if it works out.
Click to expand...
Click to collapse
Yupp s-off'd with no issues. Just want amonra lol. Ruu'd to OTA and am waiting for my battery to charge up enough to flash via hboot. The amonra thread has a PH98IMG.zip but I think that one was the 3.06 version. Dunno. Will report back.
Sent from my ADR6425LVW using xda premium
zac41189 said:
Yupp s-off'd with no issues. Just want amonra lol. Ruu'd to OTA and am waiting for my battery to charge up enough to flash via hboot. The amonra thread has a PH98IMG.zip but I think that one was the 3.06 version. Dunno. Will report back.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I'm not trying to be a jerk or whatever but have you read the bottom of the AmonRA OP? It has a link to 3.15 I am pretty sure.
Curious. Why you want AR so bad? We have 2 other fully functional recoveries. lol
Flyhalf205 said:
I'm not trying to be a jerk or whatever but have you read the bottom of the AmonRA OP? It has a link to 3.15 I am pretty sure.
Curious. Why you want AR so bad? We have 2 other fully functional recoveries. lol
Click to expand...
Click to collapse
The ph98img.zip in that post is 3.06. I just got really used to it lol. I have twrp 2.3.2.3 downloaded for a couple weeks now.. might as well try it out lol.
Sent from my ADR6425LVW using xda premium
zac41189 said:
The ph98img.zip in that post is 3.06. I just got really used to it lol. I have twrp 2.3.2.3 downloaded for a couple weeks now.. might as well try it out lol.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Since you're on the OTA ICS firmware, you should definitely NOT be running Amon Ra 3.06. You need to be on 3.15. If the md5's match what's on your sdcard and what's on the OP at that thread, it shouldn't be a bad download, but just in case, I loaded it up on my Dropbox and you can try the one here.
As far as alternate recoveries, while I was very impressed with TWRP, it is incapable of wiping boot, so that's a nonstarter. Admittedly, if Flyhalf solved that issue, I'd switch to it. As far as CWM Touch, that has issues with reading sdcard2, as of the last time I checked, or at least with respect to its interaction with various ROMs and their features. For me at least, having tried all of the Rezound recoveries, Amon Ra is my preferred choice.
just push AR manually instead of using the tool:
Unzip the file from the link listed below onto the root of the C drive on your PC, and it should create a folder called Android on the root of C.
1) open a cmd prompt and type " cd c:\Android " without quotes
2) boot to fastboot and make sure your USB is plugged into the pc and phone
3) type " fastboot flash recovery recovery.img " without the quotes
This should push the AR 3.15 to your device. I included AR 3.15 in the Android folder below.
the folder contains a txt file of a few other handy commands that i use. that txt file is for reference only
https://www.dropbox.com/s/aycfqc37tvkhbdl/Android12-14-2012_22+21+19.rar
I ended up flashing twrp and it worked great. Like a previous poster said if it could wipe boot it would be perfect. But it got the job done and am up and running again. Thank you all for your help!
Sent from my Rezound using xda premium
Glad everything worked out for ya. Wiping boot can cause a lot of problems just sayin. So I debating on putting it back into TWRP. Just ask snuzzo in his kernel thread
Hey guys I am looking for a little help. I had an IDIOT error.
I have a rezound that I put a custom recovery and unlocked via hosoons tool. Then I flashed a custom Rom (newts hybrid).
Well I started reading about how its easier to flash etc if you are s-off. So I tried restoring my stock unrooted backup. While restoring it failed and I came to find out its because I needed to also restore the boot.IMG. so I went to try and find it and my backup was gone! I have went thru internal and external its no where.
So I reflashed the Rom and boot IMG the correct way and am now running that. So my basic question is am I sol? Am I stuck on this Rom?
Thank for any help.
Sorry for the crappy type out I am at work and just got time to write this up. I will update what I get home.
P.s I did a lot of searching and couldnt find anything.
Sent from my ADR6425LVW using xda premium
S On you say...
It's as easy as extracting the boot.img file and using fastboot to install the boot.img file.
Open up the ROM you downloaded and extract the boot.img file.
Place the boot.img in the folder where you have fastboot, ex:
d:\phones\rezound\bootloader\andriod\
Boot into recovery; flash your ROM; boot into the bootloader; then run fastboot from the command prompt:
fastboot flash boot boot.img
Good luck and have fun.
Thanks for your reply! But how would I go about getting back to stock? I understand the boot.IMG flashing procedure I just didn't realize it was necessary to restore a backup and now my stock back up is not available and I have no idea where it went so I am running the Rom I stated above with no way to go back to stock.
Sent from my ADR6425LVW using xda premium
Schnider said:
Thanks for your reply! But how would I go about getting back to stock? I understand the boot.IMG flashing procedure I just didn't realize it was necessary to restore a backup and now my stock back up is not available and I have no idea where it went so I am running the Rom I stated above with no way to go back to stock.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
You don't have to go back to stock to change ROMs. You can just wipe and flash another ROM (including whatever kernel comes with it).
But yeah, if you want to s-off you should be stock. Although now it seems even if you are s-on flashing the kernels is automated. I just flashed EclipticRez and it had me select s-off or s-on, I picked s-on and it made the PH98IMG of the kernel and went to hboot. I just had to say yes and delete the file afterwards.
But you can get back to stock by running the RUU found here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
You need to put this on your external sd card, rename it to PH98IMG.zip, relock (fastboot oem lock) and reboot. Hboot will find the file and start running it. Let it run through several times so it gets all the files. It will reboot you once it's done. Then you'll need to unlock again and flash a custom recovery and then you can make a new nand of stock to make it easier to get back to it.
Also, there's an OTA that just rolled out so if you don't want to be bothered by it just don't put the back door on so you won't connect. There's a thread about it in General, seems to be new radios and who knows what else.
But don't you have to be s-off to flash an RUU? Also can you put amon ra recovery on your phone with s-on?
Sent from my ADR6425LVW using xda premium
Schnider said:
But don't you have to be s-off to flash an RUU? Also can you put amon ra recovery on your phone with s-on?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
No, you just have to be locked to run the RUU. I'm still s-on and I just did it last night. Then I flashed Amon Ra and then a ROM.
s-off was a later discovery so RUUs and custom recoveries were being flashed by everyone when they were s-on until someone figured out how to s-off.
So while I'm on my Rom I can relock and flash the ruu? Do I need to put the recovery back to stock or will the ruu do that?
Sent from my ADR6425LVW using xda premium
The RUU will do that. All you need to do is put it on your sd card if it's a zip file, rename it to PH98IMG.zip, relock and reboot.
I am sorry for my ignorance but I need to relock first correct?
Sent from my ADR6425LVW using xda premium
Yes.
Save anything you need off both cards. Pictures, music, etc... any files at all.
Make a nandroid of what you have now in case anything goes wrong. (I'm sure it won't)
Relock the phone in fastboot:
fastboot oem lock
Put the RUU file on the sd card and rename it to PH98IMG.zip
Reboot the phone into bootloader (hold vol down then press and hold power until you are in hboot)
Phone will find the PH file and run the RUU. It goes through it a few times. The screen will go dark a few times during the process and it will go through updating after each of those times again. Just let it run it's course and it will reboot your phone when it's done. Delete the PH file if it's still there. (I used my orig 16gb card and popped in my 64gb back in as soon as I did it so I didn't check if it was still on the 16gb card or not, but if it is it will run again so make sure it isn't.)
After that you will need to unlock again using your unlock token. If you don't have it still you can get a new one. I just keep mine in my flashing folder on the pc so it's always there if I need it.
Use this command to unlock:
fastboot flash unlocktoken Unlock_code.bin
Then flash your recovery:
fastboot flash recovery nameofrecovery
Root
Make a nandroid for going back to stock whenever you need to
Flash ROM of choice.
Good luck!
Hey thank you so much for your help! For some reason my phone eouldnt read the PH98img file. So I had to use hasoons tool again and flashed the file that way. Ran it twice and bam back to relocked stock! I really appreciate all of of your guys help!
I do have one more question. Do you have to be s-off to flash amonra recovery? I have read where you don't and where you do...
Sent from my ADR6425LVW using xda premium
No, you can flash Amon Ra while s-on. Everyone did before s-off happened. I'm still s-on and I just did the whole RUU thing, Amon Ra, new ROM a couple days ago.
Don't forget to make a nandroid of stock right after you flash Amon Ra.
Thanks again! What Rom do you recommend?
Sent from my ADR6425LVW using xda premium
I'm glad I saw this thread, because I'm in trouble.
I've been running an ICS rom with the gingerbread patch. But tethering never worked.
In an effort to get tethering working, I flashed the new CM10.1 JB rom. Phone stuck at HTC screen. Did some reading, realized I needed to yank the boot.img out of the zip and fastboot it in. Did that, didn't help. I spent 4 hours last night trying every conceivable order of events. rom first, then img. img first, then rom. img via fastboot. img via PH98update file. Nothing works.
I put amon ra on and started all over again. Ugh. My old Sprint Evo was a tank for stuff like this, I swear you could put anything you wanted on it and it would run fine.
Anyway, I was going to come on here and ask if it's possible to go S-OFF with a stuck phone because it's all I could think of.
But now I will try this relock, ruu, unlock, amon ra, root method.
Here goes another 8 hours.
wakekiller said:
I'm glad I saw this thread, because I'm in trouble.
I've been running an ICS rom with the gingerbread patch. But tethering never worked.
In an effort to get tethering working, I flashed the new CM10.1 JB rom. Phone stuck at HTC screen. Did some reading, realized I needed to yank the boot.img out of the zip and fastboot it in. Did that, didn't help. I spent 4 hours last night trying every conceivable order of events. rom first, then img. img first, then rom. img via fastboot. img via PH98update file. Nothing works.
I put amon ra on and started all over again. Ugh. My old Sprint Evo was a tank for stuff like this, I swear you could put anything you wanted on it and it would run fine.
Anyway, I was going to come on here and ask if it's possible to go S-OFF with a stuck phone because it's all I could think of.
But now I will try this relock, ruu, unlock, amon ra, root method.
Here goes another 8 hours.
Click to expand...
Click to collapse
Good luck! Post back if you have any issues. The RUU took me about 10-20 minutes.
After you flash Amon Ra and root make a nandroid so you can easily revert to stock if needed.
Back up and running. The instructions were well written and easy to understand.
Thanks for all the help!
However I think this time I just want to go straight to S-OFF. I did the htc dev unlock last time, I have no idea where my token is.
I guess I'd rather go all the way and s-off so I can try that JB rom again without worrying about seperating the boot.img file.
So is it possible to s-off my phone with the RUU listed on this thread? And phone currently locked?
Another question. I don't think I've flashed any firmware which means my phone is still running GB firmware. Does that mean I need to always run the GB patch when running IC or JB roms?
Good to hear!
The RUU will have gotten you to the latest firmware if you used the global one at android police.
As to any s-off questions, I'm still s-on so I would get that info from someone else. I don't want to say the wrong thing and get you in a bad spot. There's a long s-ff thread in the general section and I'm sure if you just search you should find the info you need. Or else there's a help thread also in the general section where you can post questions or actually, probably find the answers you need.
Keep this handy for next time:
http://forum.xda-developers.com/showthread.php?t=1547496
It works similar to dumlock.
Hi guys.
It's 2 days already I am trying to do s-off for my evo 3d. Maybe anyone got "up to date" thread where I can do this? My hboot is 1.49.0018, and GSM phone.
Because thread using hex and revolutionary method is out of date, and the main file PG86IMG.zip is no longer uploaded there.
Juopunutbear method requires stock RUU, but when I download from http://www.androidfiles.org/ruu/?developer=Shooter this version: RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.zip I get wrong zip file when flashing. Name was too big for 4ext, but when I shorten name it's gives error.
Any ideas? :crying: Thanks..
EDIT: Got S-off, but have no root now..
You can't flash that through 4ext. You need to rename to PG86IMG.zip and put it on the root of your SD card. Then reboot into the bootloader and when it asks to update, hit volume up to say yes.
Make sure when you boot back up to delete the file from the sd card.
I believe your bootloader needs to be relocked before running the ruu as well.
fastboot oem lock
Personally I have seen many evo V users get s-off just by being on a stock based rom. Because there was no ruu available to them they went as close to stock as possible. Probably best to just follow the instructions though if you have that option.
Thanks Brian. Actually I did just like you said, but apparently that RUU version had 1.53.0007 hboot, so now I am on stock RUU with 1.53.0007 hboot.
Gonna try juopunutbear method first if I manage to install linux first haha.
Good luck! It's not too hard to make the live dvd/usb. There is a program you can download that will set it all up for you if you go to the ubuntu website. They have all the instructions for a live ubuntu dvd/usb.
So I finally made S-off using wire trick But got new problem so gonna ask here..
I am still on stock RUU, and I installed 4ext using Play store, but it's not working cause it says I need root. I installed busybox and SuperSu, but SuperSu won't work, it says: "There is no SU binary installed, and SuperSU can not install it, This is a problem!
I had root before I know for sure.. Also I can't go into recovery from bootloader because recovery does not exist. Can I flash 4ext through the bootloader renaming it PG86IMG.zip or it's not how it works?
Just downloaded several "root checker" apps, and all of them says I have no root access.
Thanks!
Edit: my hboot is 1.53.7777 now if that matters.
Edit2. I am on stock ROM, maybe that's why it does not work..?
EDIT: I've fixed everything, thanks.
Sorry, was asleep but glad to see you got it! I'm assuming you had to flash Super user to get the binaries installed? The app is just an interface.
Brian706 said:
Sorry, was asleep but glad to see you got it! I'm assuming you had to flash Super user to get the binaries installed? The app is just an interface.
Click to expand...
Click to collapse
Yes I flashed recovery using adb and then SuperSU using recovery And my root access came back.
Got an old phone from a friend which I'm using since wife broke her phone and I'm trying to decide what to replace it with.
Anyhow, I have an Aria with hboot 1.03, I have unlocked it via the HTC site and managed to get Cyano 10 on it. It is still s-on and I've tried multiple times to redownload Cyano 11 and always get an error of "Error in <name>.zip (Status 0) Installation Aborted". I'm making an assumption based on research that it is due to a combination of s-on and hboot 1.03 so I need to kick it down to 1.02 and s-off it. However, I have been unable to find a valid link for the Official HTC Froyo link to downgrade so I can run Revolutionary to s-off and move ahead.
Thanks in advance.
Hmm, can't find a link either... I can reupload it for you
But before you do that, try updating your recovery to this: http://forum.xda-developers.com/showthread.php?t=2474662
HTCdev unlock shouldn't have any problems with CM11, so it's probably your recovery...
Anyway, here's the RUU
http://goo.gl/OBVJL7
md5sum: 66d703b8a92fc382c38ceec4992a379c
And the rom.zip extracted from it if you just want to run it directly from the phone:
http://goo.gl/WF3RhW
md5sum: 49e737569d1d99e11e652ddcfc15bf84
Edit: Here's a list of them instead of just the AT&T one: http://www.androidruu.com/?developer=Liberty
Thank you Win, that did it. I had to fastboot the CMW as it wouldn't upgrade through recovery, after that I just flashed CM11.
CollinsJ said:
Thank you Win, that did it. I had to fastboot the CMW as it wouldn't upgrade through recovery, after that I just flashed CM11.
Click to expand...
Click to collapse
Problem is that due to S-On it is not possible to write to recovery partition from recovery. You also can't write to boot partition, but you can install ROMs without problems if you flash boot image separately through fastboot.
dansou901 said:
Problem is that due to S-On it is not possible to write to recovery partition from recovery. You also can't write to boot partition, but you can install ROMs without problems if you flash boot image separately through fastboot.
Click to expand...
Click to collapse
Boot images can be flashed from recovery just fine with S-ON... maybe you're thinking of newer (but not newest) HTC devices? I've heard they did that
WinSuk said:
Boot images can be flashed from recovery just fine with S-ON... maybe you're thinking of newer (but not newest) HTC devices? I've heard they did that
Click to expand...
Click to collapse
Possible. I own one of them (points at signature) and it's been that way for me then. When I rooted my Gratia way back, I also directly did the S-OFF so I never checked the procedure with S-ON. Have been a newbie at that time.
So I'm in a similar boat. I have an old aria, and seeing a cm11, id like to try it (though a nexus is my dd). Anyway, i had cm7 on it, went through some old nandroids, and finally got back to 2.1 just after i used unrevoked on it. I've tried to flash the posted rom.zip (2.2.2, so i can then s-off and /or upgrade hboot [which i also tried to do via htcdev with no success]), it fails a sig check on my cwm 2.5.0.1, telling me bad, even though i verified the md5. Figured it could be the recovery, but i cannot flash the newer version on here via ./fastboot flash recovery recovery.img. i also tried ./fastboot boot recovery.img to no avail. I also couldnt flash the recovery through the old cwm. Im baffled a bit here... Any suggestions are welcomed.
Im thinking of trying to put my sim in it and see if the old att update would go through, any thoughts on that?