Hey Everyone,
Im sorry in advance if I'm about to ask the dumbest questions of the day/week, but I'm brand new to this, and I haven't found any answers in any of these threads, so go easy...
Up until now I customized the heck out of my mt4g. Tonight however, I followed HTC's instructions and unlock the boot loader -- as I thought based on what their site said, that I'd be able to flash custom roms to the phone once unlocked.
I was successful in unlocking the Bootloader, but (S=on) still exists. I'm kinda stuck now because I don't know what to do next? Is it possible to go from here to Root, if so, how? I've tried the HTC Super Tool for over an hour and it's not working... not giving me perm S=off. Maybe I'm doing something wrong?
If the phone isn't rooted, then how am I supposed to be able to flash a rom??... Do I do it from the HBOOT menu? Because I can't seem to do that either. If I opt for "recovery" while in HBOOT, I come to a red triangle, and have to do a battery pull.
The stock rom that's loaded now has GB 2.3.4 running.
My goal is simply to get CyanogenMod running on this phone. I just don't know what the next step is. I've already factory reset the phone so all my customizations and apps are gone therefore I don't really care what I have to do to get where I want to go. If it's possible to root from here, what's the next step? If root isn't possible, then how do I flash a new rom, like HTC claims I can do now that the BL is unlocked??
If someone could offer some help, I would be super appreciative!!
T40
Follow this link . Very well written guideit worked for me http://forum.xda-developers.com/showthread.php?t=1178912
headcreepz said:
Follow this link . Very well written guideit worked for me http://forum.xda-developers.com/showthread.php?t=1178912
Click to expand...
Click to collapse
Follow that guide and get off the official HTC unlock. You should have read the thread on this forum about it.
Sent from my mytouch 4g using xda premium
okay... I followed the guide and I achieved "perm-root", I believe.
If I go into terminal emulator, and type SU, I get a # returned. I do notice however that when I boot into HBOOT, it still says s=on. Not sure what the difference is between 'perm root' and 's=on' but...
I have rom manager downloaded. I also have titanium backup downloaded and did a full backup.
PROBLEM:
In rom manager, I Flashed ClockworkMod Recovery, and then downloaded the nightly CyanogenMod, no problem, but every time the phone reboots (into recovery mode), I stop at the red triangle?!?!?!
What's going wrong?
Open rom manager and art the top is an option to install recovery-install it, then you should be good to go
I did install recovery. Everytime it reboots into recovery i get the red triangle.
After I get the red triangle, and I hold the Vol Up button and hit power, I come to a BLUE recovery menu (3e) with 4 options:
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
in the middle of the screen, in yellow text it says "E:Can't open /cache/recovery/command"
track40 said:
I did install recovery. Everytime it reboots into recovery i get the red triangle.
After I get the red triangle, and I hold the Vol Up button and hit power, I come to a BLUE recovery menu (3e) with 4 options:
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
in the middle of the screen, in yellow text it says "E:Can't open /cache/recovery/command"
Click to expand...
Click to collapse
That's the stock android recovery.
Sent from my Infernalized Glacier!
-Team Inferno
If you had your device s-off and rooted, why HTC unlock? You just went backwards.
i started with HTC Unlock, then achieved perm-root, but (s=on)
Recovery
Hello,
I had the same issue, I had to flash the recovery with adb
1) If you dont already have it download flash_image and place it in your adb tools folder
2) Download the recovery you need and unzip, then rename to recovery.img and place in the root of your sdcard
3) open terminal and use the following commands
adb push flash_image /system/bin
adb shell
su
cd /system/bin
chmod 777 flash_image*
flash_image recovery /sdcard/recovery.img
4)wait for it to finish
5) type exit
adb reboot recovery
this should solve the issue
You can find the recovery here...including the new touchscreen version
http://clockworkmod.com/rommanager
You can download flash_image here
http://forum.xda-developers.com/showthread.php?t=902493
Thanks to Raichison for all the above
okay #furydude39, im all ready to run through your steps... when i issued the first command "adb push flash_image /system/bin", the handset responded with
"failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system"
Any idea where to go now? This is obviously why every time i boot into recovery that the processes initiated by RomManager isn't sticking.
an hour later...
I was able to execute the commands correctly that 'furydude39' recommended, and still nothing.
Here's a video I shot of the phone [still] giving me a headache
http://youtu.be/2Hr-7CosDQc
Someone's gotta have an idea on how to get past this?
Have you turned off fastboot?
Sent from my HTC Glacier using xda premium
yes, just checked... fastboot is off
We need to find out why it is not flashing the cw recovery. Are you able to to mount /system partition and copy files to it? I'm thinking a downgrade might be necessary so you can do gfree and eng bootloader.
Sent from my HTC Glacier using xda premium
okay guys...
I got past the last problem, of getting clockwork mod recovery to work. So, that's all set.
NOW, I use rom manager and i downloaded cyanogenmod 7.1 (stable) + google apps. Once the downloads were complete, I checked all three boxes... backup, clear caches, clear dalvik cache. The phone reboots, goes right into clockwork mod recovery.
the backup goes fine... the cyanogen flash goes without error, and then the google apps flashes without error.
NOW, the phone reboots, and the thing just hangs on the White t-mobile boot screen. Is this supposed to take a while before it goes into Cyanogen's screen? It's been sitting on this white screen for at least 5 minutes.
track40 said:
okay guys...
I got past the last problem, of getting clockwork mod recovery to work. So, that's all set.
NOW, I use rom manager and i downloaded cyanogenmod 7.1 (stable) + google apps. Once the downloads were complete, I checked all three boxes... backup, clear caches, clear dalvik cache. The phone reboots, goes right into clockwork mod recovery.
the backup goes fine... the cyanogen flash goes without error, and then the google apps flashes without error.
NOW, the phone reboots, and the thing just hangs on the White t-mobile boot screen. Is this supposed to take a while before it goes into Cyanogen's screen? It's been sitting on this white screen for at least 5 minutes.
Click to expand...
Click to collapse
You should manually wipe and flash. Doing it from the app seems to screw up some of the time. Make sure you wipe system data cache and dalvik before flash. It even helps to reboot recovery after doing wipe before you flash a rom.
Sent from my HTC Glacier using xda premium
i hate to ask another [stupid] question... but how do i manually do that?
track40 said:
i hate to ask another [stupid] question... but how do i manually do that?
Click to expand...
Click to collapse
In recovery, using the volume rockers, look for factory data reset/wipe. I'm not to positive on the exact names, since I have touch recovery. When you find it select wipe data an wipe cache. after those are wiped, go back then find advance, wipe dalvik cache. When that finished, go back. Select install from sdcard, find your files an install them. Everything should work then.
If I helped, give thanks, if you please.
........Death before dishonor........
Team inferno
Leader
Thanks all for your suggestions. I finally was able to get Cyanogen to stick. Had to wind up flashing the boot.img manually using fastboot via Windows while in HBOOT screen.
Related
Since the Evo just got NAND protection removed, I figured I'd share the persistent version of ClockworkMod recovery
Currently ROM Manager is using a recovery hot replace to give you a custom recovery. But I'll eventually be packaging this into ROM Manager's flashing process like the other phones it supports. I'll wait a week or so to switch, while everyone switches over to the new root.
For those that want to make ClockworkMod their default recovery on recovery boot, use this image:
These step assume you have already unlocked your NAND using the "Part 2" thread in the forums.
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-supersonic.img
http://www.droidaftermarket.com/koush//recoveries/flash_image
Place these files on the root of your SD card.
Then run this from a root Android shell.
cd /data/local
cat /sdcard/flash_image > flash_image
chmod 755 flash_image
./flash_image recovery /sdcard/recovery-clockwork-supersonic.img
Done!
For insurance stuff, will we need to flash stock recovery img to get rid of everything?
<3
Will we be able to update this with ROM Manager?
Re: Permanently replacing your recovery with ClockworkMod Recovery Image
You are a God!
-------------------------------------
Sent via the XDA Tapatalk App
TheBiles said:
<3
Will we be able to update this with ROM Manager?
Click to expand...
Click to collapse
Yes, in a week, when everyone has done their NAND unlock, ROM Manager will start flashing and replacing your recovery for you, so you don't need to do this manually. I do not want to switch right now, because that will leave people who haven't unlocked out in the cold.
Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?
HTC6800 said:
Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?
Click to expand...
Click to collapse
No, that will still work.
This is just an option for people that want to boot into recovery via the power key combination. Or those that don't want to apply the update.zip on the root of their SD card to switch to ClockworkMod. It's just a convenience/safety net people wanting to replace their recovery now.
HTC6800 said:
Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?
Click to expand...
Click to collapse
no, it means when you choose reboot to recovery in any application, ROM manager, quickboot or thru adb it will reboot to the phone's recovery partition but instead of loading the stock recovery, it will load this custom recovery!
this is basically a permanent or "sticky" recovery where as before we had to load the custom recovery every time as a temporary or "non-sticky" recovery. the days of temporary or non sticky recoveries are OVER ... at least until the next update from HTC/Sprint!
Koush, I m still a completely rookie on root part, EVO4G is my first androind phone, and 0 experience on root. Besides, i haven't done anything about rooting evo4g yet (still kinda struggle here, worrying to brick such a$$kicking phone, anyway). So please forgive if my question sounds ridiculous and stupid.
lets say if i decide do root like next months, so i should follow the 1st part root my phone by "PC36IMG.zip", then what's next step? should I use adb shell complete flash recovery, and 2nd part to remove NAND protection, at last run ROM Manager flash recovery permanently? or I can just directly use ROM Manager after root'd phone, like the instruction "[TUTORIAL] IDIOT-PROOF Root Guide! No ADB, no fuss!" by theBiles, to flash recovery permanently?
Koush said:
No, that will still work.
This is just an option for people that want to boot into recovery via the power key combination. Or those that don't want to apply the update.zip on the root of their SD card to switch to ClockworkMod. It's just a convenience/safety net people wanting to replace their recovery now.
Click to expand...
Click to collapse
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0
phinnaeus said:
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0
Click to expand...
Click to collapse
Hrm, let me double check on mine
phinnaeus said:
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0
Click to expand...
Click to collapse
I get the android with the white triangle as well when using reboot into recovery from rom manager. However the normal recovery is now clockwork great job and thx K!
Confirming this as well.
Booting to recovery via adb or hboot works as expected, reboot from Rom Manager doesn't.
jeremydk said:
Confirming this as well.
Booting to recovery via adb or hboot works as expected, reboot from Rom Manager doesn't.
Click to expand...
Click to collapse
Found the problem Fix is being uploaded!
Flash this:
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-1.8.2.2-supersonic.img
Koush said:
Flash this:
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-1.8.2.2-supersonic.img
Click to expand...
Click to collapse
Just did this, works perfectly. Thanks for the fast response, Koush. Sending some beer your way.
Edit: When I boot into recovery manually (hold down voldown, select recovery) I get into version 1.8.2.2.
When I boot into recovery from ROM Manager I get into version 1.8.1.9. Does this mean there are two different recoveries on my phone and it is booting into them distinctly based on which method I use? Or is it just a error in reporting version numbers?
So what exactly does this do or look like? I'm a bit confused on that one.
phinnaeus said:
Just did this, works perfectly. Thanks for the fast response, Koush. Sending some beer your way.
Edit: When I boot into recovery manually (hold down voldown, select recovery) I get into version 1.8.2.2.
When I boot into recovery from ROM Manager I get into version 1.8.1.9. Does this mean there are two different recoveries on my phone and it is booting into them distinctly based on which method I use? Or is it just a error in reporting version numbers?
Click to expand...
Click to collapse
Booting via ROM Manager still uses the recovery hot replace, which is using a recovery with a different version number. They're exactly the same, no worries
Koush said:
Booting via ROM Manager still uses the recovery hot replace, which is using a recovery with a different version number. They're exactly the same, no worries
Click to expand...
Click to collapse
Oh gotcha. So thats what that progress bar is before it loads up? And this won't happen with the updated ROM Manager coming in a week. I guess thats not really a question, but if I'm wrong feel free to correct me
Koush said:
./flash_image recovery /sdcard/recovery-clockwork-supersonic.img
Click to expand...
Click to collapse
Worked great but it might help to change that to
./flash_image recovery /sdcard/recovery-clockwork-1.8.2.2-supersonic.img
Took me a second to figure out why it said directory or file doesn't exist
Thank You for all your work
Attempted to flash update to current CM 7 Nightly build, from Nightly10. When doing so, Bootloader>Recovery(System hangs on Google load screen), Battery is then pulled. Attempts are made without SIM card. Also initiated with ROM Manager v3.0.0.7 +Fix Permissions, with same results.
No luck with returning to previous ROM, or cleaning Cache and Dalvic-cache for same reason.
All other ROM flashing attempts have been flashed on my Nexus S, great success.
Side Note: CM 7 Nightly10 is running great! Boots/Loads with no issue.
Red Fox said:
Attempted to flash update to current CM 7 Nightly build, from Nightly10. When doing so, Bootloader>Recovery(System hangs on Google load screen), Battery is then pulled. Attempts are made without SIM card. Also initiated with ROM Manager v3.0.0.7 +Fix Permissions, with same results.
No luck with returning to previous ROM, or cleaning Cache and Dalvic-cache for same reason.
All other ROM flashing attempts have been flashed on my Nexus S, great success.
Side Note: CM 7 Nightly10 is running great! Boots/Loads with no issue.
Click to expand...
Click to collapse
dont use rom manager, rom could be corrupted while downloading. download it manually then flash from recovery.
simms22 said:
dont use rom manager, rom could be corrupted while downloading. download it manually then flash from recovery.
Click to expand...
Click to collapse
What could cause, or any suggestion on how to fix/pass the system freeze on: Power+VolumeUP>Recovery= Google ... .. ... (snooze, thinking, snooze)
Much help is greatly appreciated, updating to the latest and greatest is inspiring.
Sent from my Nexus S
Red Fox said:
What could cause, or any suggestion on how to fix/pass the system freeze on: Power+VolumeUP>Recovery= Google ... .. ... (snooze, thinking, snooze)
Much help is greatly appreciated, updating to the latest and greatest is inspiring.
Sent from my Nexus S
Click to expand...
Click to collapse
ahhh, i misunderstood you first. try flashing the recovery again.
simms22 said:
ahhh, i misunderstood you first. try flashing the recovery again.
Click to expand...
Click to collapse
I just tried the recovery OS ROM, no progress, still freezing the same. Could you please explain this recovery, that you suggest?
If the system doesn't make it to the next stage/screen, w/the android. I feel like something is missing to pass go, and collect $100 big one's, LOL!
Sent from my Nexus S
Note: I also attempting this through, ROM Manager. As Bootloader triggers same results. ROM's are all DL'ed from http://mirror.teamdouche.net/?device=crespo (Blank Stare)
Sent from my Nexus S
adb update:
cmd
cd c:\androidsdk\tools
fastboot flash recovery recovery.img
ENTER
Figured it out through trial, and error.
Hope this helps fellow XDA members.
Thanks for your efforts, and taking the time to help with this issue.
Sent from my Nexus S
Red Fox said:
adb update:
cmd
cd c:\androidsdk\tools
fastboot flash recovery recovery.img
ENTER
Figured it out through trial, and error.
Hope this helps fellow XDA members.
Thanks for your efforts, and taking the time to help with this issue.
Sent from my Nexus S
Click to expand...
Click to collapse
I do have exactly the same problem.
Which recovery.img did you flash?
stiefa00 said:
I do have exactly the same problem.
Which recovery.img did you flash?
Click to expand...
Click to collapse
Here is the recovery.img that I flashed:
http://www.megaupload.com/?d=C933QJOO
Same recovery.img used when rooting, here is the source:
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
Sent from my Nexus S
Another alternative, Terminal Emulator:
- install recovery to sd-card(no folders)
- Terminal:
su
flash_image recovery /sdcard/name-of-recovery.img
-=Edit=-
Phone should pause for a second and then show you a new blank line. Turn it off and back on. Holding down VolumeUp and Power to ensure it flashed correctly. Done.
Sent from my Nexus S
thx, got it!
Dunno if mine is the same problem.
My recovery seems to "reset" itself after every reboot. I have done it from ROM manager also also fastboot.
1. I flash the recovery
2. reboot
3. recovery comes up fine
4. reboot again, it show me this triangle sign with a exclamation mark inside.
So i need to fastboot/ROM manager everytime I want to go into the clockwork recovery.
ykphuah said:
Dunno if mine is the same problem.
My recovery seems to "reset" itself after every reboot. I have done it from ROM manager also also fastboot.
1. I flash the recovery
2. reboot
3. recovery comes up fine
4. reboot again, it show me this triangle sign with a exclamation mark inside.
So i need to fastboot/ROM manager everytime I want to go into the clockwork recovery.
Click to expand...
Click to collapse
Dude, this is discussed in multiple threads already.
The OTA 2.3.1 and 2.3.2 updates place a new script in the /etc folder that checks the crc on your recovery image at every bootup. If it fails, a backup copy of stock replaces it.
If you want to stay on Clockwork, you need to rename the file /etc/install-recovery.sh to something like /etc/install-recovery.sh.bak
Ah ok thanks! I din know where or what term to search for this.
After successfully flashing ClockWork RecoveryMod, I placed SU on the root of my SNS, powered it off, went into fastboot, but when I went into Recovery, it just went to Stock Recovery, the Exclamation Mark inside the Triangle with the Android next to it appeared, but no text or anything else is on the screen. I've let it sit for about 15 minutes, and nothing. I also can't do anything by clicking the volume buttons, or the power buttons. I've also unplugged the Phone, held the power button to try to reboot it, held volume-up and power to try to go back into fastboot, but nothing. Should I pull the battery? Why didn't it go into ClockWork RecoveryMod? Command Prompt gave me the whole " sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s" thing...
What do I do? I can't just leave it sitting like this forever.
Edit: I unplugged and replugged it a few times, and it rebooted. But I've tried going back to fastboot and going into Recovery, and I get the same screen, over and over. I've even tried flashing CWRM again, and nothing. I'm using 3.0.2.4. Should I just use 3.0.0.5?
When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.
If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Hawky_ said:
When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.
Click to expand...
Click to collapse
I tried it again with 3.0.2.5 from http://forum.xda-developers.com/showthread.php?t=988686. Did not work. Went again into Stock Recovery.
jerrycycle said:
If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Click to expand...
Click to collapse
I'm a bit confused with your post.
I am still using the Stock Rom, but I don't have root access.
I've tried, after unlocking the Bootloader, going into Rom Manager and Flashing ClockWork, but it tells me first:
"You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin.su". (...)"
Then, when I still attempt to flash ClockworkMod, it tells me:
"An error occurred while attempting to run priviliged commands!"
I should have told the full story first.
I was once rooted, but it was through ROM Manager and flashing Clockwork from there. But then I had a few issues with my Wifi, and I decided to flash back Stock Rom. I still had an unlocked Bootloader though, so I thought that just redownloading Rom Manager and flashing CWRM and having Superuser installed would work. It didn't. So I attempted to root all over again, this time, manually.
But, I always go back to square one, it seems, when I try to get into Recovery.
What up with that?
After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App
matt2053 said:
After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
No problem.
There is a script located in the /etc folder called install-recovery.sh. it runs every time you boot and installs stock recovery. You have two choices: always use rom manager to flash CWM every time you need to access recovery, or use root explorer to rename install-recovery.sh to install-recovery.sh.bak so that it will not run and will leave CWM installed.
Glad you got it figured out!
Sent from my Nexus S using XDA App
Or a third choice of course would be to install a custom ROM because they tend to not include that script
Sent from my Nexus S using XDA App
EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up
buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
That's partly my fault, I never went down to the 2nd Post and saw those Notes, but what's the point of not including that already in the steps in the main Post? He could have just told to go straight from Recovery after flashing CWRM, but decided not to.
matt2053 said:
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up
Click to expand...
Click to collapse
I think he should just have instructed to place the SU zip on the root of the SD card before flashing CWRM. That way, there wouldn't be a need to reboot to mount the SD to place SU, that way potentially losing the CWRM.
Hi All,
I've looked all around for the answer to this and am thoroughly lost. I have the Verizon Galaxy S3 with VRALHE. I rooted it, then used EZ-Unlock 1.2 to unlock the phone, then installed Rom manager and flashed CWR. It says it installed 6.0.1.2 but when I try and go into recovery it only goes into Android Recovery. If I flash CWR and right away click the boot into CWR button it seems to go but after that it will only go into Android Recover both via Rom manager and holding Volume Up, Power and Home. Anyone know whats going on?
Thanks for your help!
If it does go into cwm the first time then after that stock there are two files you need to erase that basically reinstall the stock recovery on reboot. I can't recall them, but you could probably search here and find them. Or the easier way is busy flash a custom ROM n that first boot into cwm. By the way ez recovery is better for installing our recoveries, give it a shot.... It may sick without the extra stuff I just told you.
Sent from my SCH-I535 using xda app-developers app
Anyone know where to look into about the files that need to be deleted? I'm not finding much. EZ recovery worked the first reboot but returned to Android recovery after a reboot.
Boss428man said:
Anyone know where to look into about the files that need to be deleted? I'm not finding much. EZ recovery worked the first reboot but returned to Android recovery after a reboot.
Click to expand...
Click to collapse
I would recommend re-flashing Clockworkmod Recovery from EZ recovery, then using EZ recovery to boot into Clockworkmod Recovery, after your are in Clockworkmod Recovery select the "Reboot system" option, you should then be asked if you want to erase two files to make Clockworkmod Recovery stick permanently (At least until you flash a different recovery) select the "Yes" option, then after it has completed that task the phone should reboot, while it is rebooting boot into recovery and you should find that Clockworkmod Recovery is still installed.
I like to help, but Google stuff. This is what you would have found as the second result
/system/recovery-from-boot.p*
/system/etc/install-recovery.sh
Sent from my SCH-I535 using xda app-developers app
So to confirm to everyone, Deleting the 2 files above does work! So delete the files then re-flash CWR and restart that's it!
I wanted to thank everyone for the help!
Same problem but a little different
shimp208 said:
I would recommend re-flashing Clockworkmod Recovery from EZ recovery, then using EZ recovery to boot into Clockworkmod Recovery, after your are in Clockworkmod Recovery select the "Reboot system" option, you should then be asked if you want to erase two files to make Clockworkmod Recovery stick permanently (At least until you flash a different recovery) select the "Yes" option, then after it has completed that task the phone should reboot, while it is rebooting boot into recovery and you should find that Clockworkmod Recovery is still installed.
Click to expand...
Click to collapse
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.
Wizardtech-101 said:
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.
Click to expand...
Click to collapse
What rooting guide did you follow? Did you flash Clockworkmod Recovery yet? If you can provide me with this information I can try help you further. If you haven't flashed Clockworkmod Recovery yet then you will be presented with the normal stock Android recovery system that you described.
Wizardtech-101 said:
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.
Click to expand...
Click to collapse
Ummm... You do not necessarily go into recovery to root it. Have you installed and used Odin through your PC? You say you are trying to root your phone, so before you get ahead of yourself trying to flash recoveries I recommend reading up a little bit, it is very important you follow directions specifically or you will brick your device....
http://forum.xda-developers.com/showthread.php?t=2046439
There is even a video watch it while you root your phone, and pause along with it.
If you have already done some of this, and done any of it wrong there are steps to recover through Odin.
Hello, I've recently completed the Bootloader unlocking method with Easy Ace Root Tool. Bootloader is unlocked and SHIP S-ON, I need to flash a rom. These roms require S-OFF and have no method to flash them with only an unlocked bootloader and S-ON.
So let me get this straight, us 'low level' and unexperienced users are left without any method to gain S-OFF privileges without following the vague guide provided at tau(dot)shadowchild(dot)nl/attn1/?p=411 Yeah... I can't.
Trying to find alternate methods I have only gone in circles and keep running into old how-to guides. The more I read the more confused I become. I hope someone can point me in the right direction, I would really appreciate it!
Thanks,
Ninjewbag
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
bananagranola said:
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
Click to expand...
Click to collapse
Good deal, thanks for the reply!
I put the ROM Android Revolution HD 9.0 on the root of my SD card, booted in recovery mode and chose the recovery option, I got the red exclamation mark icon so I pressed VOL up + power button which didn't work so I pulled the battery. I tried all above steps again but this time I was able to successfully get into "Android system recovery <3e> with VOL up + power button. With 4 options:
Reboot system now
Apply update from sdcard
wipe data/factory reset
wipe cache partition
I chose the option to wipe all data, said it could not find Efolder name)'s and "data wipe completed successfully".
Then I wiped cache, then chose the option to apply update from sdcard, it said "Invalid operation" then "success rebooting by reason 00" and proceeded to reboot by itself.
Phone factory reset, I rebooted into recovery again with the same red exclamation mark error. Pressed Vol up + power and back into "Android system recovery". At the bottom in yellow text it says "E: Can't open /cache/recovery/command". I tried another "update from SD card" and recieved error: "success rebooting by reason 00" and reboots.
I don't have a nandroid backup as I read I needed Root to make one, but the phone still works fine as far as I can tell. I don't have a working simcard in it though.
Also from what I've read my eMMC chip may be fried so it looks like I'm retiring early. I'll keep an eye on this thread among others with the same problems.
Cheers,
Ninjewbag
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
RadRacer said:
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
Click to expand...
Click to collapse
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
http://forum.xda-developers.com/showthread.php?p=31211732
ninjewbag said:
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
Click to expand...
Click to collapse
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
turboyoshi said:
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
Click to expand...
Click to collapse
Thanks for the reply but as for installing the 4ext free updater version, it wasn't on the market so I used android injector to place and install that APK. None of the options worked as they all give the same error "it seems your phone is not rooted, this option will not function" etc.
RadRacer said:
http://forum.xda-developers.com/showthread.php?p=31211732
Click to expand...
Click to collapse
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
ninjewbag said:
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
Click to expand...
Click to collapse
Glad to help. Wanna hit thanks?