Related
Hi everyone,
I can't post in the developers section cos I'm a new user so I hope you guys can point me in the right direction.
Okay to give you a brief summary:
My phone was rooted by using the latest Unrevoked 3.32
Then I did a NADROID Backup of my files.
Then I took S-Off With AlphaRev 1.8 Custom HBOOT.
Everything was successful and it said S-OFF.
Now when I boot up my phone normally all I get is the "Why So Serious?" image by unrevoked.
I restored my backup but still get the same image.
I'm guessing it's to do with the HBOOT version and my Radio version?
Please check attached images.
You do have to change the splash if you want to, thats why the image is how it is because it has changed from the HTC one, to AlphaRev's. Your radio is so old, really old. Try and install a newer one (been tested) or the newest one (get the second radio). See if that does anything for you. Just let things load up, they can take a while to do.
Thanks for the reply.
The thing is, i don't mind the splash, it's kinda cool.
The problem is the fact it just hangs, just stays on the splash screen.
I'll try what you suggested, unless others have another suggestion?
If you wanted S-Off badly, you could just download the correct RUU and then freshly install the stock ROM. It would wipe everything and you would need to run Unrevoked and AlphaRev again. But nontheless, you would have S-Off. Or you could download the stock rooted ROM and then S-Off from that.
Just an update.
The problem has been solved thanks to GoogleJelly's steps in pm.
Why did you sort that out by pm?
Maybe there are other people experiencing the same problem and are interested in the solution too...
just sayin...
lol yeah true, let me ask his permission if I can post the pm
Okay here are the steps I got:
If your able to get into the recovery then you're ok. You can try to install a stock Froyo ROM if you like, pre-rooted. See how that turns out.
If not, then I guess all you can do is install the RUU. You need the correct on that represents your installed radio so you can update. It will reset everything and I mean everything so you will need to root and S-Off again. Hopefully that will of fixed everything. But I don't recommend restoring. I have had some weird stuff happen to me through restoring before but your welcome to try it again.
To Get Into Recovery
1) Turn off your phone
2) Hold down volume down and press the power button
3) Wait for it to check your SD Card then press vol down to highlight recovery and press power button to select it
4) Should take up to 30 seconds to boot into recovery
Whilst in the recovery, you're able to mount USB to transfer the pre-rooted stock ROM across and then you can install it that way.
I hope this helps you out. If you need anymore help, just ask.
Click to expand...
Click to collapse
thanks
10charrrrrrrrrrr
Hi please be gentle...I'm a noob.
So, I receives a pre owned HTC Evo. Went through the forum and figured that it is rooted (bootloader indicates S-OFF at top). I want to unroot so I can take it to Sprint and have the speaker checked.
However, I checked the sd card and it is completely wipe clean with no zip files, no ROMs or any files for that matter. I don't know what was used to root the phone. Although, whenever I bootload it goes to an update which I think is the pc36img and after the process is done all indicate "ok" so not really sure what that is...(BTW-When I got the phone it appeared to have stock OS).
My questions are:
Can I still unroot without any knowledge of how the root was done? If so, how?
Is there a possiblity that the previous owner tried to unroot but did not fully do so, hence the S-OFF?
Do I need to get another rom (like unrevoked-forever) zip firle into the sd card to even proceed with the unrooting?
I am not a techy gal so dumb it down for me please...I would appreciate it. Thanks
http://forum.xda-developers.com/showthread.php?t=780141&highlight=restoring+stock
here is the guide to restoring back to stock.
If you can get into h-boot than its very possible to fix your problem here. Make sure you got a full battery when working with h-boot (you never want your evo to die while these processes are going on)
Just follow the link the previous user supplied, it'll work. If you have any problems just pm me or get back here in the thread.
Edit: Also, the S-OFF [security off] means the phone was fully rooted, allowing you to change the splash screens, and just about everything.
Still confused...
I tried to do all the steps from the link above. Since I wasn't sure if it was rooted with unrevoked forever I first tried to do the first 8 steps and when I did the bootloader and selected "recovery" it took me to a black screen with a red triangle and exclamation mark. The bottom half...also got the same result. So, I pressed vol up and power buttons to get out of that scary page but it just reboots.
What am I doing wrong? Have I "bricked" my phone? I don't think so since I still can use the phone with the stock OS...Help anyone???
uh DUH said:
I tried to do all the steps from the link above. Since I wasn't sure if it was rooted with unrevoked forever I first tried to do the first 8 steps and when I did the bootloader and selected "recovery" it took me to a black screen with a red triangle and exclamation mark. The bottom half...also got the same result. So, I pressed vol up and power buttons to get out of that scary page but it just reboots.
What am I doing wrong? Have I "bricked" my phone? I don't think so since I still can use the phone with the stock OS...Help anyone???
Click to expand...
Click to collapse
That screen you are seeing means you don't have a custom recovery installed. That isn't the main issue.
When you load into H-BOOT. (Volume Down + Power), does it say S-ON or S-OFF at the top? If it says S-ON, flash the stock RUU and it will bring you back to stock. You can find it in my sticky or by going through the forums.
If you are S-OFF and still get the red triangle screen when you hit Recovery, you will have to flash another custom recovery like Amon RA to get back in to flash the Unrevoked S-ON Tool.
Also for future help. Get your H-BOOT Version from the H-BOOT Screen, all the information from Menu > Settings > About Phone > Software Information as well as all the information from Menu > Settings > About Phone > Hardware Information
i have purchased a 2nd hand desire z from someone, i noticed it has clockwork and rom manager installed, i think it also has super user rights. I also noticed that the rom is Virtuous 1.0.1. Thinking this meant that the phone was already rooted, i used rom manager to download and install CM7, however it caused the phone to be semi bricked, then i also realised that the phone was also S-ON.
Fortunately i managed to reboot the phone into CWM and restored the previous image, so now the question is, what is wrong?
PS. new to this whole android thingy..
hmmm... sounds like MAYBE you had a temp root?? Is you had superuser you definitely had some form of root, however, i am not sure you can flash a new rom if you dont have S-off (but i could be TOTALLY wrong here)
I have an Evo (and dont have this temp root issue), but i am helping a friend with a similar problem with his G2.
Can you get into recovery? (while phone is off, hold the volume down and power on the phone) If you can, do you have Clockwork recovery or stock android (says 3e at the top i think)?? If you have CW, just enable USB, download a CM7 through your computer, put it on your SD and flash it. SHould be good to go.
If you have stock recovery and S-on.. WELCOME TO MY BOAT... I am trying to find a solution to this for my friends phone. If i figure it out, i can let you know (please do the same??)
I am having the same problem, with the same rom. I can use all root apps, but it says S is ON? I can't put any other rom on my phone with out it going into boot loop or just staying on, HTC screen. Some one please help us, I know there are many phone guru's on this site. Any help would be over the top. O-yeah and I can not get the wifi to connect either says error or turns it self off after scanning? Please please please help. Thank you in advance.
Sent from my SGH-T959 using XDA App
[email protected] said:
I am having the same problem, with the same rom. I can use all root apps, but it says S is ON? I can't put any other rom on my phone with out it going into boot loop or just staying on, HTC screen. Some one please help us, I know there are many phone guru's on this site. Any help would be over the top. O-yeah and I can not get the wifi to connect either says error or turns it self off after scanning? Please please please help. Thank you in advance.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
If you can boot to an OS, you are WAY ahead lol. Here is description of my problem: http://forum.xda-developers.com/showthread.php?t=1009593
CHeck the links in that post. MAY be able to help if you can boot to OS?
frettfreak said:
Can you get into recovery? (while phone is off, hold the volume down and power on the phone) If you can, do you have Clockwork recovery or stock android (says 3e at the top i think)?? If you have CW, just enable USB, download a CM7 through your computer, put it on your SD and flash it. SHould be good to go.
Click to expand...
Click to collapse
tried using CW to flash CM7 again.. no go.. just stuck at HTC screen after rebooting...
i was also reading thru the goldcard portion of the guides. Should i create one so that i can downgrade my phone back to an earlier ROM? Would appreciate some help to get permaroot.
ok.. i have managed to downgrade to an older rom and did a full root after that.. finally managed to get cm7 working..
was using this guide all the way..
http://forum.xda-developers.com/showthread.php?t=905261
Hey guys,
I tried to root my my evo 4g with the instructions from the sticky and when I started the autoroot file as it said, it would get to found root then establishing something and the cmd would close out and my phone would stay in the bootloader mode. Instructions said to go to recovery if it didn't continue and I did go into recovery and all it gave me was a black screen with the red triangle and nothing was happening so I pulled out the battery to restart the phone. Now my phone boots up normally and it just freezes up after maybe 30 seconds of use everytime and just reboots and it repeats over and over again nonstop. It won't be recognized by my computers and it just says unidentified with the CDMA drivers not working and the phone does not recognize the SD card when its running and booted up. Please help if you guys know what I could do to make it stop restarting. Thanks in advance!
Try re-rooting via unrevoked. Click on unrevoked in my signature and follow the directions, but first, boot into the bootloader screen (after shutting off the device, simultaneously press the DOWN volume button and the power button until the device starts). Look at the top of the screen and see if it displays "S-OFF". If it does, great, you're rooted, bit if it displays "S-ON" then follow the rooting method of unrevoked or retry the method you used. If it does indeed display "S-OFF", I suggest you flash a custom recovery like amon_RA.
posting & replying via the XDA Premium app.
Well I can't do that since it won't recognize the phone through USB or recognize the SD card
Update: I just flashed my evo with the stock 3.70.651.1 rom using a card reader putting the PC36IM something file on the SD card and used bootloader to flash and It's still not recognizing the SD card and it's still freezing up 1 minute after it has booted up and restarts and repeats the loop.
I sorta have a similar problem. I have a rooted evo running CM7 .
trying to use HDMI cable with a 1080p vizio LCD TV. Nothing happens. Does CM7 support the HDMI video out.
Sent from my PC36100 using XDA Premium App
SprintTouchPro2 said:
Hey guys,
I tried to root my my evo 4g with the instructions from the sticky and when I started the autoroot file as it said, it would get to found root then establishing something and the cmd would close out and my phone would stay in the bootloader mode. Instructions said to go to recovery if it didn't continue and I did go into recovery and all it gave me was a black screen with the red triangle and nothing was happening so I pulled out the battery to restart the phone. Now my phone boots up normally and it just freezes up after maybe 30 seconds of use everytime and just reboots and it repeats over and over again nonstop. It won't be recognized by my computers and it just says unidentified with the CDMA drivers not working and the phone does not recognize the SD card when its running and booted up. Please help if you guys know what I could do to make it stop restarting. Thanks in advance!
Click to expand...
Click to collapse
can you send me the autorootlog.txt file? that should show what happened to it. And def don't try rooting it with anything else while the phone is in an inconsistent state, that is just asking to corrupt it.
Use unrevoked 3 my guide has all you need links and so on
I like unrevoked 3 easy to root and unroot . All the other programs that work for rooting can make unrooting a pain in the butt. Do what you want you want .
You don't have a recovery installed that's why you get black screen and triangles . Use amon 2.3
reaper24 said:
Use unrevoked 3 my guide has all you need links and so on
I like unrevoked 3 easy to root and unroot . All the other programs that work for rooting can make unrooting a pain in the butt. Do what you want you want .
Click to expand...
Click to collapse
how is unrooting different?
xHausx said:
how is unrooting different?
Click to expand...
Click to collapse
I'm not going to war with you on that man just saying turn s off flash a stock Ruu the latest and your good to go. Trying to find a auto or one click unrooting program to unroot can be a pain to do if your h boot is to new or old .
I'm sure your way is good I just prefer unrevoked 3 is all. Not dogging your root way. Just familiar with unrevoked 3 use it to root everyone's phone I know.
reaper24 said:
I'm not going to war with you on that man just saying turn s off flash a stock Ruu the latest and your good to go. Trying to find a auto or one click unrooting program to unroot can be a pain to do if your h boot is to new or old .
I'm sure your way is good I just prefer unrevoked 3 is all. Not dogging your root way. Just familiar with unrevoked 3 use it to root everyone's phone I know.
Click to expand...
Click to collapse
Well you're saying there's a difference in how you have to unroot when it's not true. Or at least that I know of, if there is I'm curious as to how.
Autoroot will try to downgrade the hboot to the unlocked engineering leak, if successful it's finished and all you have to do to unroot is run the RUU. If it's unable to downgrade the hboot it will bring up the stock recovery and use unrevoked forever to unlock the nand; when this is used you have to flash the s-on tool (that is left on the sdcard as URFSOn.zip) and then flash the RUU to unroot.
Unrevoked 3 breaks in through the hboot and unlocks the nand through the radio, so you will also have to use the s-on tool and flash the RUU.
You're also telling him to keep trying to root when his phone is obviously in a weird state, that's bad advice unless you want him to end up bricked like a ton of people did when the latest firmware came out.
xHausx said:
Well you're saying there's a difference in how you have to unroot when it's not true. Or at least that I know of, if there is I'm curious as to how.
Autoroot will try to downgrade the hboot to the unlocked engineering leak, if successful it's finished and all you have to do to unroot is run the RUU. If it's unable to downgrade the hboot it will bring up the stock recovery and use unrevoked forever to unlock the nand; when this is used you have to flash the s-on tool (that is left on the sdcard as URFSOn.zip) and then flash the RUU to unroot.
Unrevoked 3 breaks in through the hboot and unlocks the nand through the radio, so you will also have to use the s-on tool and flash the RUU.
You're also telling him to keep trying to root when his phone is obviously in a weird state, that's bad advice unless you want him to end up bricked like a ton of people did when the latest firmware came out.
Click to expand...
Click to collapse
no I'm not telling him to brick his phone. He doesn't have a recovery on his phone that is what he needs . Just saying if he does end up rerooting at some point he can try unrevoked 3 just a suggestion. My advice isn't bad not new to rooting or flashing. Pretty good at trouble shooting .
Well how do I get a recovery? I thought I have one since I have the option to go there? Gives me a red triangle with a phone under it. Once i mash the volume up and down and power button at the same time and hold it in for a bit a menu pops up to update from SD card or to clear storage and some other options. But anyway I reflashed the stock rom from bootloader and it's still doing the freeze after 30 seconds of use and restarts over and over again. So how do I actually get recovery and what do I do after that to make this stupid restarting of my phone to stop.
SprintTouchPro2 said:
Well how do I get a recovery? I thought I have one since I have the option to go there? Gives me a red triangle with a phone under it. Once i mash the volume up and down and power button at the same time and hold it in for a bit a menu pops up to update from SD card or to clear storage and some other options. But anyway I reflashed the stock rom from bootloader and it's still doing the freeze after 30 seconds of use and restarts over and over again. So how do I actually get recovery and what do I do after that to make this stupid restarting of my phone to stop.
Click to expand...
Click to collapse
I'll need to take a look at your autorootlog.txt file in order to find out what's up with your phone. It should be in the autoroot folder and you can post it by using the 'manage attachments' button, if it doesn't want to let you for some reason you can also email it to me.
edit: odds are you're phone is still locked but it won't hurt to try flashing the recovery, all you have to do to flash it is run the FlashZip script that came with AutoRoot and select the one that says Amon RA - hausmod. That's if it's unlocked of course, if it says s-on or that the security is still on then your phone will reject it.
There you go, there is my autorootlog
I'm not too worried about this as I took the phone to sprint and they ordered me a new phone since they didn't know what was wrong with it and I'll get it today or tomorrow but I just want to figure out what went wrong so that I know what to do if I am to root my new phone..cause this autoroot I used on this website messed up and I followed every step perfectly.
Ok guys I would be eternally greatful if someone could please help me on this issue asap...I was in the process of rooting/unlocking/installing CWM on my brother's A100, and I ran into a somewhat serious issue.
Everything was going great - I rooted it, unlocked the bootloader, and started to install CWM. Unfortunately, I totally screwed up and didn't rename /etc/install-recovery.sh. I got all the way through flashing the recovery.img before I realized...I realize this is completely my fault.
After trying to reboot into CWM using the volume down key on power up, it simply shows a picture of an android with a spinning blue orb in it's stomach. After this finishes, it briefly say "Start Updating EBT" then "Finished Updating EBT". It then reboots once more back to the standard android OS. Additionally, during bootup it no longer displays the message about the bootloader being in "UNLOCKMODE".
Is there anything I can do from here? I realize I've totally screwed up, but if anyone could provide step-by-step ideas of what I need to do I would be very thankful. i.e. is the bootloader re-locked, and if so do I need to re-unlock it? and how could I successfully get CWM working? Thanks in advance!
ohlin5 said:
Ok guys I would be eternally greatful if someone could please help me on this issue asap...I was in the process of rooting/unlocking/installing CWM on my brother's A100, and I ran into a somewhat serious issue.
Everything was going great - I rooted it, unlocked the bootloader, and started to install CWM. Unfortunately, I totally screwed up and didn't rename /etc/install-recovery.sh. I got all the way through flashing the recovery.img before I realized...I realize this is completely my fault.
After trying to reboot into CWM using the volume down key on power up, it simply shows a picture of an android with a spinning blue orb in it's stomach. After this finishes, it briefly say "Start Updating EBT" then "Finished Updating EBT". It then reboots once more back to the standard android OS. Additionally, during bootup it no longer displays the message about the bootloader being in "UNLOCKMODE".
Is there anything I can do from here? I realize I've totally screwed up, but if anyone could provide step-by-step ideas of what I need to do I would be very thankful. i.e. is the bootloader re-locked, and if so do I need to re-unlock it? and how could I successfully get CWM working? Thanks in advance!
Click to expand...
Click to collapse
First off, slow down, take a breath, relax, and realize the world didn't just end, everything is fine, it just went awry at one point where alot of people miss the step of install-recovery.sh.
Start from the beginning, check if you have root.
If you have root, then use any root file manager (I use ES File Manager, in settings check "Up to root" then further down, check "Root Explorer", grant it permission, then check "Mount system Writable") and navigate to /system/etc.
Rename or move or delete install-recovery.sh. I would just rename it install-recovery.bak.
Go ahead and reboot, and verify the green acer screen does NOT say (unlocked mode) in the upper right corner. If it does in fact NOT say that (it should still be unlocked) then proceed with the previous steps starting at unlocking the bootloader.
Once the bootloader is again unlocked (remember to be quick on those volume keys) proceed with flashing CWM or TWRP or whatever you choose.
Now when you reboot into android, your custom recovery will remain intact.
Now that you have a custom recovery, boot into it, and first thing, mount either internal or external SD (I use external) and make a full backup. Do it NOW. After that is done, it takes a few minutes, you can either keep the stock ROM, flash a new one, whatever, it's up to you, but you will now have a backup to fall on if anything goes wrong.
In the guide in my sig is a ton of information, I would suggest browsing it to become familiar with some things about these devices.
pio_masaki said:
First off, slow down, take a breath, relax, and realize the world didn't just end, everything is fine, it just went awry at one point where alot of people miss the step of install-recovery.sh.
Start from the beginning, check if you have root.
If you have root, then use any root file manager (I use ES File Manager, in settings check "Up to root" then further down, check "Root Explorer", grant it permission, then check "Mount system Writable") and navigate to /system/etc.
Rename or move or delete install-recovery.sh. I would just rename it install-recovery.bak.
Go ahead and reboot, and verify the green acer screen does NOT say (unlocked mode) in the upper right corner. If it does in fact NOT say that (it should still be unlocked) then proceed with the previous steps starting at unlocking the bootloader.
Once the bootloader is again unlocked (remember to be quick on those volume keys) proceed with flashing CWM or TWRP or whatever you choose.
Now when you reboot into android, your custom recovery will remain intact.
Now that you have a custom recovery, boot into it, and first thing, mount either internal or external SD (I use external) and make a full backup. Do it NOW. After that is done, it takes a few minutes, you can either keep the stock ROM, flash a new one, whatever, it's up to you, but you will now have a backup to fall on if anything goes wrong.
In the guide in my sig is a ton of information, I would suggest browsing it to become familiar with some things about these devices.
Click to expand...
Click to collapse
Thank you very, very much! I went through everything again, and finally got CWM up and a backup taken. I was thinking those steps were what I needed to do, but didn't want to proceed without a confirmation. Thanks again for your great advice!
ohlin5 said:
Thank you very, very much! I went through everything again, and finally got CWM up and a backup taken. I was thinking those steps were what I needed to do, but didn't want to proceed without a confirmation. Thanks again for your great advice!
Click to expand...
Click to collapse
No problem, just be sure to take your time before diving into anything, and make sure everything has been read twice before starting.
pio_masaki said:
No problem, just be sure to take your time before diving into anything, and make sure everything has been read twice before starting.
Click to expand...
Click to collapse
I know lol, that why I felt like such a doofus admitting I did it, because I literally read that part about renaming twice before I even started...I guess it was one of those in-one-ear-out-the-other-cause-I'm-tired type of deals
Anyways thanks again, I'll definitely have to do this when I'm a little more awake next time...wait, here's to hoping there's not a next time :laugh: Thanks!
I used twrp because the instructions sounded so much easier, even though I've worked with cwm for over a year.
sent from my sexy-a$$-iconia tab