How's it goin'. Not my first time rooting, as I had the Hero and rooted a few other phones back in the day..
Just got the EVO in today, and decided to use the Auto-Root method found here:
http://forum.xda-developers.com/showthread.php?t=838448
Everything was going well, the program was going through all the motions, and then my dog jumped up and knocked over the laptop, I guess killing the connection to the AutoRoot.bat. I can repeatedly get it to go back through the motions of flashing the PC36IMG file, (Step 7) but after it tries and boot in to Recovery, it just hangs at the triangle screen. I can still get bootloader to show up, but I'm all out of ideas here. I'd GREATLY appreciate if someone could throw a few ideas out this way. Thanks.
I'm pretty sure youdidnt get the recovery to get installed are you rooted? If yes you can download superuser and download manager and get the recovery from there, if your not complete rooted get zroot to perm root and try it
Sent from my PC36100 using Tapatalk
Related
My phone has been rooted pretty much since the first week of release. I used Toastcf's method (step 1) of rooting my wife's phone, but never did the NAND unlock root, and she was fine with that for a while.
Recently, she's been having short batter time issues and problems with the phone restarting for no reason, so she asked me to root it and put a new ROM on.
I did some searching and it looked like Unleash the Beast was the best tool for rooting her phone in the shortest time possible, so I downloaded the zip file and loaded Amon's recovery to install it.
Unfortunately, when I went into Recovery mode, the phone restarted and now all I get is the little phone icon with the triangle/! and even when I restart the phone, this is all I get! I've pulled the battery, tried starting it up in recovery, etc. but nothing seems to work.
Did I just brick my wife's Evo?
Update 1: I played around with the volume buttons and somehow the recovery listing came up. I selected install update from sdcard, but it errored out and wouldn't install the Unleash the Beast update.zip.
I rebooted the phone instead and now I'm back up and running, but still not sure what the best way to root this thing completely would be. Any help would be very much appreciated!
http://forum.xda-developers.com/showthread.php?t=776477
Euphoricsoul said:
Update 1: I played around with the volume buttons and somehow the recovery listing came up. I selected install update from sdcard, but it errored out and wouldn't install the Unleash the Beast update.zip.
I rebooted the phone instead and now I'm back up and running, but still not sure what the best way to root this thing completely would be. Any help would be very much appreciated!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=776477
unrEVOked
Hey all. Running CM6.1 172 nightly. Launch day evo rooted with toasts 2 part.
Flashed zendroid last night. Booted and ran great, good scores on quadrant etc. Smooth as butta.
Rebooted to do a backup of the new setup. Boot loop, about 1 seconds on the splash screen each time. Not sure if its of relevance but its the fastest boot loop I've seen (day one g1 owner). Went to recovery to restore, and....boot loop after selecting recovery.
So I figure recovery image went bad somehow. Fastboot flash AmonRa1.8. Attempted to reboot into recovery. Aaaannddd....boot loops.
Does anyone have any ideas on where I should go next? I can get into bootloader. Had to do plenty of "repair" with the G1, but this is the first issue I've ran into with my Evo since launch day.
Cliffs: CM6.1. Flash zendroid. Runs fine. I reboot. Boot loops. Attempt to enter recovery. Boot loops. Fastboot flash recovery. Loop loop loop. No recovery, cant get into the operating system so no ADB.
Any help would be GREATLY appreciated. Thanks in advance.
Edit: Just tried flashing PC36IMG.zip from toasts part 2. Still cant get past splash screen. Grrrr. It did however change my splash screen so I would guess it flashed fine. But it still looped after rebooting.
That sucks. Hopefully someone else will chime in. I've never had anything like that happen, but from reading through xda, I've seen this happen to other people. Now I've never had to do it, so don't know the steps. But I think you can take your sd card out, and mount it in your pc. Load a stock RUU onto your sd card, then put the card back in the phone, and flash it from hboot. Then you'll be totally stock and have to start over, but I think that's what you should search about doing. I wish you luck, and hope someone who knows more than I can help more, or inform you of another way.
Sent from my PC36100 using XDA App
k2buckley said:
That sucks. Hopefully someone else will chime in. I've never had anything like that happen, but from reading through xda, I've seen this happen to other people. Now I've never had to do it, so don't know the steps. But I think you can take your sd card out, and mount it in your pc. Load a stock RUU onto your sd card, then put the card back in the phone, and flash it from hboot. Then you'll be totally stock and have to start over, but I think that's what you should search about doing. I wish you luck, and hope someone who knows more than I can help more, or inform you of another way.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Hey thanks for lookin man. Yeah my next move is gonna be flashing a stock unrooted img see if I can get into Android. I already tried reflashing toasts 2nd pc36img.zip (launch day evo rooted with toast 2 part). Thanks for your input tho.
i would say unroot is your best option
I picked up the Galaxy Nexus from Verizon yesterday and attempted the unlocking and rooting procedure on droid-life.com. It looked like it was working, but now I can not get into recovery. When I try, I end up stuck on the screen with Andy and a red yield sign. I can get into the bootloader and run fastboot from my computer. The phone does still boot up completely.
I've seen posts about using Terminal Emulator and flash_image to restore the recovery, but Terminal Emulator says it can't find su. So something must have failed with the rooting.
Is there any information I can gather to help with this? Any help would be greatly appreciated. I'm out of ideas. My only other rooting experience was on my OG nearly two years ago and it went flawlessly.
Download the image in this thread and flash via fastboot. Make sure to delete /system/reboot-from-recovery.p afterwards.
Android screen with red exclamation point is the stock recovery image. Press power and either up or down volume to get into the recovery.
But yes, you'd want to flash clockwork mod like the guy above me said. Also rename or delete that file he wrote, otherwise on every boot, your recovery will go back to stock recovery.
Sent from my Galaxy Nexus
Oh. I hadn't found any documentation on the stock recovery so when I saw Andy open with a red yield and exclamation sign, I assumed it was bad. Thanks for the help!
EDIT: Got it thanks.
Hi all
This is the first time I tried to root my phone and install ICS on it. The phone was on 2.3.4 and then I tried to root it using unrevoked tool. Initially it was the latest version of the unrevoked and hence it did not allow me to root it. I went for one lower version and the phone was rooted successfully.
After that I followed the instructions from the androidlookout website.
All the steps went fine. When installed zip files, it did say that file was installed successfully. Now when I am trying to reboot after that, all I get is the first screen with "htc Incredible" written and it does not go ahead. I waited for hours but it did not move. Then I pulled out the battery and tried using the hard reset using Power and Volume Down. I selected option to reboot now and again stuck at the same screen.
I believe the phone is not bricked as it is still allowing me to go to the recovery menu. Any help would be truly appreciated. I am sure I might have messed up somewhere.
Regards
Gajendra
moondoo said:
Hi all
This is the first time I tried to root my phone and install ICS on it. The phone was on 2.3.4 and then I tried to root it using unrevoked tool. Initially it was the latest version of the unrevoked and hence it did not allow me to root it. I went for one lower version and the phone was rooted successfully.
After that I followed the instructions from the androidlookout website.
All the steps went fine. When installed zip files, it did say that file was installed successfully. Now when I am trying to reboot after that, all I get is the first screen with "htc Incredible" written and it does not go ahead. I waited for hours but it did not move. Then I pulled out the battery and tried using the hard reset using Power and Volume Down. I selected option to reboot now and again stuck at the same screen.
I believe the phone is not bricked as it is still allowing me to go to the recovery menu. Any help would be truly appreciated. I am sure I might have messed up somewhere.
Regards
Gajendra
Click to expand...
Click to collapse
You don't say anything about the ICS version you attempted to flash. I suggest you try flashing another rom such as the reliable Nil's 2.1. Then if that is up running save a nandroid copy of that and try flashing the IC-dinc AOKP or Kang roms.
Pull the battery, press volume down and power button. You should be at the bootloader screen and it should say S-off if you are rooted. On the menu, go to recovery and press the power button, it should then reboot to the CWM recovery menu. You can then go to mounts and select USB mount to get the nil's (or other rom) that you downloaded to your computer and transfer it to the root of the sd card; then go back to the main menu and do a factory reset; go back to mounts, and format system and boot; then flash your rom and reboot. It should work.
Wrong section. This should be in Q&A, per site rules. Thought there was a 10 post rule, mabey they did away with it.
That being said, wipe the phone from recovery, and reflash a rom.
It sounds like you might have gone ahead with flashing before achieving S-OFF. Here is a good guide on how to downgrade to 2.2 and use unrevoked to get S-OFF. As always be sure to make a nandroid backup before you downgrade. I followed the steps in the guide to a T and am now rooted, S-OFF, with ICS running
You said that can get into the recovery menu, go in wipe your stuff and reflash.
Sent from my Galaxy Nexus using XDA App
Thanks!
cmlusco said:
Wrong section. This should be in Q&A, per site rules. Thought there was a 10 post rule, mabey they did away with it.
That being said, wipe the phone from recovery, and reflash a rom.
Click to expand...
Click to collapse
Thank you sir!! I apologize for posting in the wrong manner but I did as you suggested. I wiped off the user data and reflashed it and voila, it worked this time.
Thank you so much!
Regards
Gajendra
Anyone knows how to close the thread?? My issue has been resolved. If only moderators are allowed to so, then you guys can close it on my behalf. Thanks for all your support.
Regards
Gajendra
you could add resolved to the title...
Sent from my Galaxy Nexus using Tapatalk
I have an S3 from sprint. it has a faild root at this point (TrevE). My guess is that an update locked up my root.. I am tring to flash back to stock so I can reroot but SU blocks everything i do. I have tried to reroot but CW wont come up, just android recovery. Everything I have found on removeing SU requires you to be rooted first.... I even tried Root Browser and Uninstall master but SU just denies permission.... All i want to do is start from scratch. Please help...
christivson said:
I have an S3 from sprint. it has a faild root at this point (TrevE). My guess is that an update locked up my root.. I am tring to flash back to stock so I can reroot but SU blocks everything i do. I have tried to reroot but CW wont come up, just android recovery. Everything I have found on removeing SU requires you to be rooted first.... I even tried Root Browser and Uninstall master but SU just denies permission.... All i want to do is start from scratch. Please help...
Click to expand...
Click to collapse
Do you are able to get to download mode?
kevinrus123 said:
Do you are able to get to download mode?
Click to expand...
Click to collapse
The problem was that i watched too many videos and went through too many how to guids. I kept working at it and finaly got it to work. i finaly found a video that told me not to let it reboot after odin was done. I turned "off" the auto reboot on Odin, which is the exact oposite of what every other video said to do, and manualy shut it down and put it straight into Recovery Mode. All of the videos I had seen said to leave Auto Reboot on so i had been doing that. after it would reboot I would shut it back down and try to go to recvery mode but got the android recvery insted of CWRecovery. I guess the reboot after Odin was enough to through it all out of wac. Manually shutting it down after Odin and then going into recovery right away got it. Unfortunatly thats the problem when there are 5,000 answers to the same question. Thanks
christivson said:
The problem was that i watched too many videos and went through too many how to guids. I kept working at it and finaly got it to work. i finaly found a video that told me not to let it reboot after odin was done. I turned "off" the auto reboot on Odin, which is the exact oposite of what every other video said to do, and manualy shut it down and put it straight into Recovery Mode. All of the videos I had seen said to leave Auto Reboot on so i had been doing that. after it would reboot I would shut it back down and try to go to recvery mode but got the android recvery insted of CWRecovery. I guess the reboot after Odin was enough to through it all out of wac. Manually shutting it down after Odin and then going into recovery right away got it. Unfortunatly thats the problem when there are 5,000 answers to the same question. Thanks
Click to expand...
Click to collapse
You may have watched some videos from before the last two official stock updates that were released several months ago - I don't recall which one, but one of those updates added a function that reinstalls the stock recovery every time the phone boots up. And since the custom recovery is the only way to flash a custom rom that doesn't revert your recovery to stock, you have to do that while the custom recovery is still installed, which means before the stock rom ever gets a chance to boot
In other words, nothing was thrown out of whack - it was all operating the way it was designed to, by developers who don't want us to be able to mess with their programming - we sure showed them, though, lol
Sent from my SPH-L710 using xda app-developers app