Database Info

[Q] Root + CWM without unlocking bootloader?

Hello, is there any possible way how to root Nexus S GSM ICS 4.0.4 without unlocking my bootloader.
I made it once when I wanted to update from 4.0.3 to 4.0.4 by using UnlockRoot and then instaling CWM via RomManager, but after update my recovery/CWM doesn't work, I am just getting a "dead" android with red triangle above him. It a bit wierd because I still have superuser app,but RomManager is not able to install CWM.

For as far as I know it's not possible.
I updated my NS to 4.0.4 from 4.0.3 by unlocking the Bootloader and flash CWM on it, from CWM I flashed the update to 4.0.4 and it works like a charm.
The "dead" android you see is for as I know another bug of 4.0.3, the recovery mode simply does not work.
If you are going to unlock the bootloader, please create a backup of everything, also your internal memory (photo's, videos, music etc.) Since the whole phone will be whiped.

Ok, i might be wrong but does lock on booting screen mean that my bootloader is locked? Someone told me that it says that my bootloader is unlocked...I lil'bit confused and lost
And maybe last question: Is it possible to flash CWM via Odin like other samsung devices?

Lock on the Google screen means it is unlocked. And AFAIK you can root and flash ROMs without unlocking.

ok, thanks for providing info.
Now i have to solve my not working recovery, is there any stock CWM kernel?

If you see the dead android with the red triangle above it, just hold the power button and press the vol.+ button and you'll see your recovery

Note that the padlock is actually open, hence "unlocked". Locked bootloaders show no padlock at all.
I believe there is -currently- no "official" way to root 4.0.4 without unlocking the bootloader, so i wouldn't count on it considering we have a relockable bootloader (and hence don't need exploits).

Still having prob with recovery, i flashed it via adb fastboot, but after restart is my CWM lost (really not there) again

Rename /system/etc/install-recovery.sh to something else.

problem with recovery
I also see a dead android but in my case backlight also dies out and when I press vol up + power button, phone just reboots

The official 4.0.3 has the recovery broken.
As the recovery mode cannot be used, I think unlocking bootloader then flash CWM recovery become a must.

Harbb said:
Rename /system/etc/install-recovery.sh to something else.
Click to expand...
Click to collapse
Ok, i will try but right now i have to fix my superuser app, it's gone mad, it is not asking about permission, some apps gets it, but my root explorer not...i tried to reinstall root expl. but it didn't help, tried to delete SU data and nothing, still not getting permission for r.exp.

There is an exploit that you could use you to get root without unlocking BL or wiping phone. I used it myself and it was super easy. Unfortunately, the exploit was closed in 4.0.4(so I've heard).
If you can find a way to revert to an earlier ICS or GB check out the link below:
http://forum.xda-developers.com/showthread.php?t=1479831
Sent from my Nexus S using xda premium

if your bootloader is unlocked it should say : “LOCK STATE – UNLOCKED”.
If you have a dead android and exclamation mark, it is the stock recovery. Press volume down + power button + volume up, in order. This will give you the stock recovery.
For some reason the new ICS update still has the 2.3.6 security.
use this http://nexusshacks.com/nexus-s-hacks/how-to-force-your-nexus-s-into-clockworkmod-recovery/
to flash CWM Recovery

About this thread topic, is there any way to root without unlocking?
When I was in 2.3.6 I had my phone rooted without unlock, but lost root after the ICS update althought I still have the Superuser app in my apps even after a factory reset, so I assume it was installed as a system app.
Can I do anything to regain root now that I have Superuser already installed?

Ok, i might be wrong but does lock on booting screen mean that my bootloader is locked? Someone told me that it says that my bootloader is unlocked...I lil'bit confused and lost <br />
<br />
And maybe last question: Is it possible to flash CWM via Odin like other samsung devices?
Click to expand...
Click to collapse
Lock on boot screen = unlocked
I think you can flash cwm via odin or you can try flash the cwm 5.0.1.0 via rom manager, it works for me...
Here's CWM 5.0.2.8
http://dl.xda-developers.com/attach...1/2/4/CWM.Touch.Recovery.5.0.8.2.Carebear.zip
sent from my nexus s - xda

thanks guys i will try it i hope it will work

naveen bailey said:
I also see a dead android but in my case backlight also dies out and when I press vol up + power button, phone just reboots
Click to expand...
Click to collapse
First press volume down + power + volume up. This gets you into STOCK recovery.
Since ICS has a problem with the CWM recovery loading up. You can force it to go into recovery.
Heres how
type this in cmd prompt (Make sure your command prompt search is in the correct folder. Press shift and right click on your folder you have your img in. Than click run command prompt in the list): fastboot flash recovery <RECOVERY IMG>
download my IMG uploated below for the latest recovery

[Q] Where did I go wrong (installing CWM)?

I'm new to the Verizon GS3. I rooted with SuperSu_GS3_Debugfs_r2a, then unlocked with EZ-Unlock12.apk. I then installed CWM V6 using VZWGS3_EZ-Recovery2.2.apk. My phone is rooted and unlocked, but when I boot into recovery mode (vol+,home and power) I get a blue text with the header "Android System Recovery (3e)". Below are a few options in blue, but no bakup option. Below that there are red error messages which state :E:Failed to mount/data(invalid argument), and E:Can't mount /data/fota/ipth-muc.prop. These are repeated three times. Finally below that in yellow is a message regarding using manual mode and appling Multi-CSC.
I tried reinstalling the EZ-Recovery and get the same result. I know I'm probably overlooking something simple, but I've searched for another user with this issue and can't find a solution. Can anyone help? Thanks!

dl ez reccovery from market

ddurandSGS3 said:
dl ez reccovery from market
Click to expand...
Click to collapse
That's what I used. I got the results I posted above. Any other suggestions? Thanks!

STraver said:
That's what I used. I got the results I posted above. Any other suggestions? Thanks!
Click to expand...
Click to collapse
the way you descirbed it it sounded like you sideloaded it through an installer.
i always flash recovery through the app. try that instead of holding buttons down.

ddurandSGS3 said:
the way you descirbed it it sounded like you sideloaded it through an installer.
i always flash recovery through the app. try that instead of holding buttons down.
Click to expand...
Click to collapse
Just tried reboot into recovery from the app itself instead of the 3 button method. Unfortunately I got the same recovery error I reported in the original post. Any other ideas? I wondered if my bootloader was really unlocked, and that perhaps that was the issue. But a search found an unlock check-if the Samsung logo is only on the screen for a second when the phone boots, than my bootloader is unlocked. If that's true than my phone is unlocked. It's got to be something simple since I'm not finding others with this issue.

STraver said:
Just tried reboot into recovery from the app itself instead of the 3 button method. Unfortunately I got the same recovery error I reported in the original post. Any other ideas? I wondered if my bootloader was really unlocked, and that perhaps that was the issue. But a search found an unlock check-if the Samsung logo is only on the screen for a second when the phone boots, than my bootloader is unlocked. If that's true than my phone is unlocked. It's got to be something simple since I'm not finding others with this issue.
Click to expand...
Click to collapse
did you select custom - 6.0.1.0 (or something close to it? my phones not next to me)

STraver said:
I'm new to the Verizon GS3. I rooted with SuperSu_GS3_Debugfs_r2a, then unlocked with EZ-Unlock12.apk. I then installed CWM V6 using VZWGS3_EZ-Recovery2.2.apk. My phone is rooted and unlocked, but when I boot into recovery mode (vol+,home and power) I get a blue text with the header "Android System Recovery (3e)". Below are a few options in blue, but no bakup option. Below that there are red error messages which state :E:Failed to mount/data(invalid argument), and E:Can't mount /data/fota/ipth-muc.prop. These are repeated three times. Finally below that in yellow is a message regarding using manual mode and appling Multi-CSC.
I tried reinstalling the EZ-Recovery and get the same result. I know I'm probably overlooking something simple, but I've searched for another user with this issue and can't find a solution. Can anyone help? Thanks!
Click to expand...
Click to collapse
I had the same issue when I first flashed CWM. If I flashed CWM then rebooted into recovery, it would work properly. Then reboot, and the next time I would reboot it would be back to the android recovery. So this was I how I fixed it (I was missing a very simple selection myself)
1 - From ez recovery flash CWM
2 - Reboot into recovery using ez recovery
3 - You should boot into CWM this time, select Reboot
4 - When you select reboot you will get a warning message asking if you want to disable the stock recovery. Select YES.
5 - Phone reboots and prevents the phone the "re-flashing" stock recovery on reboot
6 - Let it boot up
7 - Power off the phone (not reboot)
8 - Boot into recovery from power off. (Vol +, home, Power)
You should boot into CWM. Without selecting that disable stock recovery option, its switching back to stock everytime. This is how I fixed my problem a few weeks ago. Hopefully that helps. Ive also heard of people having to flash a custom ROM before CWM would stick.

travis.bridges10 said:
I had the same issue when I first flashed CWM. If I flashed CWM then rebooted into recovery, it would work properly. Then reboot, and the next time I would reboot it would be back to the android recovery. So this was I how I fixed it (I was missing a very simple selection myself)
1 - From ez recovery flash CWM
2 - Reboot into recovery using ez recovery
3 - You should boot into CWM this time, select Reboot
4 - When you select reboot you will get a warning message asking if you want to disable the stock recovery. Select YES.
5 - Phone reboots and prevents the phone the "re-flashing" stock recovery on reboot
6 - Let it boot up
7 - Power off the phone (not reboot)
8 - Boot into recovery from power off. (Vol +, home, Power)
You should boot into CWM. Without selecting that disable stock recovery option, its switching back to stock everytime. This is how I fixed my problem a few weeks ago. Hopefully that helps. Ive also heard of people having to flash a custom ROM before CWM would stick.
Click to expand...
Click to collapse
That did it! Thanks!

No problem
Sent from my SCH-I535 using xda app-developers app

[Q] Boot into Clockwork Recovery mod

Hi,
I am trying to flash my LG P500 to Cyanogen Mod 9 and the manual I found stated, that I should partition my SD card using Clockwork mod.
So I found ROM Recovery app in Google Play and installed it. Afterwords I downloaded Clockwork Flash using ROM Mangager app and everything seems OK.
But when I try to boot to clockwork mod, my phone is always being flashed into factory default.
I power off the phone, press vol down, home and power on buttons - the phone starts up, an animation of white box and android logo beside shows (with a progressbar at the bottom) - I think this is because of installed clockwork - then I release those 3 buttons I was holding, but the phone simply resets itself into factory default.
I also tried to hold those buttons all the way, until some "DOS-like" screen shows up, but the phone keeps rebooting itself.
The next thing I tried was to boot into recovery using ROM manager app, but it also did not work - I don't know, if it should boot into recovery by itself or I should press those 3buttons (vol down, home, power on/off)
Could you help me, what am I doing wrong?
thanks

It sounds like your phone is not rooted. Follow the sticky topics in this section for how to root your phone. Start with this one:
http://forum.xda-developers.com/showthread.php?t=2047589
Once you have root, install clockworkmod again. Then, you'll have success.

mrcorey said:
It sounds like your phone is not rooted. Follow the sticky topics in this section for how to root your phone. Start with this one:
http://forum.xda-developers.com/showthread.php?t=2047589
Once you have root, install clockworkmod again. Then, you'll have success.
Click to expand...
Click to collapse
no, my phone is already rooted

That's the stock recovery, that means ClockworkMod Recovery did not flash properly. See if you granted SuperUser rights to ROM manager, and check the SuperUser app if you had mistakenly checked 'Remember Choice'.
Sent from my LG-P500 using Tapatalk 2

Dont use Rom Manager.
You dont have recovery installed.
Find some other way to flash recovery.. there are many in this forum.

I suggest you use Rom Manager to download CWM and then boot into cwm .

I suggest http://forum.xda-developers.com/showthread.php?t=1827723
This is safe for installing custom recovery.
Thanks to Shinobisoft.
Use AmonRA recovery. Works flawlessly for all roms in this forum.

bleritaezo said:
I suggest you use Rom Manager to download CWM and then boot into cwm .
Click to expand...
Click to collapse
Your suggesting something that might make your phone unusable,This is not the way to get your 10 posts! Please do some research before suggesting something.

[Q] Can't boot into recovery

Trying to install CyanogenMod for my razr maxx HD. Recently used RSDlite to install 183.46.10 after OTA KK update kept failing. Then used towelroot to root and motopocalype to unlock bootloader. Fastboot screen shows bootloader is unlocked with status code: 3.
I then followed the instructions on the CyanogenMod site to flash CWM 6.0.4.4 recovery using fastboot, and all appeared to work fine.
However, when I try to reboot into recovery, nothing happens. I get hung up on the motorola dual core flashscreen for about a minute or two, then the screen goes black, then the phone reboots normally.
I tried flashing a different copy of CWM, tried TRWP, and tried several third party apps from Google Play store to boot directly into recovery using software reboot instead of hardware keys - all with the same results. I even tried flashing custom CWM recovery using ROM Manager and Rashr, same result.
Do I have a corrupt recovery partition? Any suggestions for how to fix?

You need to install a recovery for that phone specifically.
http://androidhosting.org/Devs/Dhacker29/
Use the recovery files found here.
Edit: on the site I posted, browse to the msm8690 folder. There you will find the recovery files.

to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader

billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Thanks, guys, total noob mistake. I knew the recovery needed to be specific for the phone, but didn't realize it varied depending on the bootloader. Will try again with the right recovery!

billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk

TheGman125 said:
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".

iBolski said:
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".
Click to expand...
Click to collapse
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.

TheGman125 said:
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.
Click to expand...
Click to collapse
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.

iBolski said:
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. Have code 3 on the devices.

try and unplug from USB when you reboot

Can't Boot Recovery Philz Touch - Root Lost

I was running Alliance rom and decided I wanted to try a couple different roms. I had previously installed Philz touch recovery 6.48.4 and had no issues with it. So I went into recovery and did the 'clean to install new rom' option and then I installed the Beanstalk 4.4.285 rom and checked it out and then was going to wipe it and try out Paranoid Android 4.45 so I rebooted to recovery again using the script in Rom Toolbox which is how I had been rebooting in to recovery since having installed Philz Touch because it's just simpler than holding the hardware keys. I had never tried booting in to Philz recovery using hardware keys. So anyways once in recovery again I once again do the 'clean to install new rom' option and then I went to flash Paranoid Android and I get a message about (can't remember exactly what it said) root being lost and was asked If I want to (again not sure exactly what it said) push su back to system/xbin and I said yes at which point the phone rebooted and now I can not reenter Philz recovery. I have tried numerous key combos including V+,home, power ; V+,power : V-,Power : V-,home,power ; V-,V+,power, V-,V+,home,power and nothing. It just boots to the Samsung Galaxy SIII screen and sits there. When I tried the V-,Home,power combo I get a screen that reads something like "Warning a custom os can cause critical problems in phone and installed applications. If you want to download a custom OS press the volume up key...." I think that is download mode but not sure. How can I get back in to Philz and or regain root if lost and reflash back to Alliance? Hope I didn't brick it.

DuhCiphered said:
I was running Alliance rom and decided I wanted to try a couple different roms. I had previously installed Philz touch recovery 6.48.4 and had no issues with it. So I went into recovery and did the 'clean to install new rom' option and then I installed the Beanstalk 4.4.285 rom and checked it out and then was going to wipe it and try out Paranoid Android 4.45 so I rebooted to recovery again using the script in Rom Toolbox which is how I had been rebooting in to recovery since having installed Philz Touch because it's just simpler than holding the hardware keys. I had never tried booting in to Philz recovery using hardware keys. So anyways once in recovery again I once again do the 'clean to install new rom' option and then I went to flash Paranoid Android and I get a message about (can't remember exactly what it said) root being lost and was asked If I want to (again not sure exactly what it said) push su back to system/xbin and I said yes at which point the phone rebooted and now I can not reenter Philz recovery. I have tried numerous key combos including V+,home, power ; V+,power : V-,Power : V-,home,power ; V-,V+,power, V-,V+,home,power and nothing. It just boots to the Samsung Galaxy SIII screen and sits there. When I tried the V-,Home,power combo I get a screen that reads something like "Warning a custom os can cause critical problems in phone and installed applications. If you want to download a custom OS press the volume up key...." I think that is download mode but not sure. How can I get back in to Philz and or regain root if lost and reflash back to Alliance? Hope I didn't brick it.
Click to expand...
Click to collapse
I've used philz but only on my tablet. I prefer using terminal emulator to reboot if I need to. And the last part yes that is download mode. You can always try Odin
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

ShapesBlue said:
I've used philz but only on my tablet. I prefer using terminal emulator to reboot if I need to. And the last part yes that is download mode. You can always try Odin
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I figured it out. I feel stupid though. I was really freaking out hoping I didn't brick my phone, couldn't you just hear the panic in my post. The first key combo I used to boot recovery was correct I just wasn't doing it right. I was pressing V+,home,power and waiting for the samsung logo before letting go and that's why it wasn't working. But I found out the correct method is to hold down V+ and home then hold down power also and wait for the phone to vibarate then let go of the power button but continue to hold down V+ and home until recovery boots.
I was about ready to try reflashing recovery via odin but I was a bit concerned about a few things when it comes to that. If I do need to use odin in the future is there a specific version I should use for the S3. I downloaded Odin3 v3.07 and also have 1.85. I know your phone needs to be in download mode to use it, so now I know how to boot to download mode at least. My bootloader is unlocked and I was wondering if using odin would lock it or affect that in anyway or have any other type of ill effect on my phone?

DuhCiphered said:
I figured it out. I feel stupid though. I was really freaking out hoping I didn't brick my phone, couldn't you just hear the panic in my post. The first key combo I used to boot recovery was correct I just wasn't doing it right. I was pressing V+,home,power and waiting for the samsung logo before letting go and that's why it wasn't working. But I found out the correct method is to hold down V+ and home then hold down power also and wait for the phone to vibarate then let go of the power button but continue to hold down V+ and home until recovery boots.
I was about ready to try reflashing recovery via odin but I was a bit concerned about a few things when it comes to that. If I do need to use odin in the future is there a specific version I should use for the S3. I downloaded Odin3 v3.07 and also have 1.85. I know your phone needs to be in download mode to use it, so now I know how to boot to download mode at least. My bootloader is unlocked and I was wondering if using odin would lock it or affect that in anyway or have any other type of ill effect on my phone?
Click to expand...
Click to collapse
No Odin has nothing to do with the bootloader.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2