Related
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
First off I am sorry for posting this, however I DID use the search tool. I recently got a USA spec Wifi only Xoom. It came with 4.1.1 preinstalled. I have sucessfully unlocked the bootloader.
My problem is this. I cannot gain root or even get CWM installed. I have tried oneclick, i have tried cmd prompt. I have followed every guide I can find to a "T". Is there something missing, is it an issue with Jellybean being preinstalled?
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
airesch said:
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
Click to expand...
Click to collapse
Thanks for the reply, however this is one of the utilities I have tried,..
Here is a bit more info.
I am running windows 7 64bit if it makes a difference. Whenever I get the device into fastboot and try to flash anything, it just hangs at the original fastboot screen. I have let it sit there from 3 hours and eventually I have to reboot it. The Lord AIO Tool you linked just gives me and error message that the device is not a 2.2/2.3 device. If I were at home I would take a screenshot.
Could my bootloader be corrupt? The device still boots up and runs jellybean fine, but I am not loving the stock experience thus far...
Thanks again for the links!
Actually sounds like your drivers aren't right. I will look them up and link them when I get home
Try installing the driver from http://developer.motorola.com/tools/usb_drivers/, rebooting your pc, and try fastboot again. If that still doesn't work, then there may be something wrong with your pc setup OR your Xoom, not sure at that point.
Sent from my SPH-D710 using xda premium
Thanks a million, I am going to try it fresh on my pc at work. Thanks!
That did the trick THANKS A BUNCH!!!!!
I accepted the latest over the air update and I need to know if that messed up my chances of obtaining root. I tried photon torpedo and could not get it to work. My device says it is unlocked but I can not boot into recovery. I have flashed several recoveries using sdk-tools but I cannot erase any recoveries. I receive an error. I have tried several things and am at a loss to as what is the most recent way if there is one. Looking for someone with more experience then I to guide me. I previously rooted my EVO 4g and EVO 3d and was away from internet for about 9 months so I mistook the old Motorola Photon for the Photon Q. Didn't realize till way later that I was trying some rooting techniques intended for the old photon on my photon q. Anyways I feel a bit lost. Any help would be greatly appreciated. I can provide any information requested. Will be monitoring this thread all day today and will provide quick responses. Cheers!
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
arrrghhh said:
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
Click to expand...
Click to collapse
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
sent17inel said:
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
Click to expand...
Click to collapse
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
arrrghhh said:
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
Click to expand...
Click to collapse
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break. Honestly "you should always be careful with anything you do" . . did that really need to be said?
sent17inel said:
Honestly "you should always be careful with anything you do" . . did that really need to be said?
Click to expand...
Click to collapse
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
sent17inel said:
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break.
Click to expand...
Click to collapse
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
arrrghhh said:
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
Click to expand...
Click to collapse
I did try again about 5 minutes ago. It says that it won't unlock because it's already unlocked.
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
sent17inel said:
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
Click to expand...
Click to collapse
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
arrrghhh said:
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
Click to expand...
Click to collapse
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
sent17inel said:
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
Click to expand...
Click to collapse
Ok... Good luck.
Thread moved. Please post in the correct forum sections in future. All questions belong here in Q&A.
Thanks
AvRS
unlocking nd rooting visuals
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
1300 said:
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
Click to expand...
Click to collapse
Well, I was going to ask you where you are stuck in the process, but it sounds like you haven't even purchased the device yet...
I wouldn't worry about unlocking and rooting until the device is in your hands. We can help out a lot easier when you actually have the thing, hahaha.
To answer your question, I don't think there's any visuals because it's not a very visual thing. fastboot is anything but visually-appealing, and the process is rather dry. Just follow the steps carefully and you'll be fine. It's very straightforward.
Plus you must decide if you prefer to keep the bootloader LOCKED or UNLOCKED and still have root access. Research the differences in the two.
The only thing simple is the belief in simplicity.
Similar problem
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
D.Eternity said:
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
Click to expand...
Click to collapse
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
arrrghhh said:
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
Click to expand...
Click to collapse
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
D.Eternity said:
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
Click to expand...
Click to collapse
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
arrrghhh said:
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
Click to expand...
Click to collapse
I know fastboot and adb are separate things, this is why I assumed cwm recovery image was flashed succesfully (despite it took only a few seconds). Now I`m trying to get into CWM, but when my phone is plugged (standard mode), adb reboot recovery returns Device not found. I haven`t the original cable here, but in the office (where I have motorola cable) it was the same. Truth is both my computers are Win7 64bit. Is it possible adb has problem with 64bit system?
Thank you for helping me
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 have a rooted, locked TF300T. I tried to flash TWRP via ADB back in ICS with locked bootloader but that apparently just broke my recovery (does it check signature before launching it?). I then OTA upgraded to latest JB (10.4.2.18) but I still cannot enter recovery (red triangle). Even if of little use, how can I get the right blob to flash on /dev/block/mmcblk0p4 to restore it?
I'd like to stay locked for a while since I just got this pad, if everything's smooth I may then consider unlocking and wild-flashing averything.
Download stock ROM from ASUS webside and flash the huge blob file to staging partition.
Sent from my GALAXY Cooper
100% sure it will not mess with root, installed system and so on once I try to boot recovery?
Sent from my Galaxy Nexus
poochie2 said:
Hello,
I have a rooted, locked TF300T. I tried to flash TWRP via ADB back in ICS with locked bootloader but that apparently just broke my recovery (does it check signature before launching it?). I then OTA upgraded to latest JB (10.4.2.18) but I still cannot enter recovery (red triangle). Even if of little use, how can I get the right blob to flash on /dev/block/mmcblk0p4 to restore it?
I'd like to stay locked for a while since I just got this pad, if everything's smooth I may then consider unlocking and wild-flashing averything.
Click to expand...
Click to collapse
When you took the ota you had stock recovery. Stock recovery is what installs otas and also updates you place on your tab to encourage updates or downgrades. Stock recovery is what is giving you the red triangle. It is telling you there is no update seen on your tab. I have never seen any type of menu on stock recovery either the red triangle or the fact that is is updating.
You can't flash twrp or cwm while locked! If you could there would be no reason to unlock.
There is much confusion about stock recovery. I have even seen posts saying there is no stock recovery. I think this is because the stock recovery does not present you with a menu and if it does not find a stock file to flash it presents the red triangle.
I hope this helps!
Place Asus stock 10.4.2.18 on your sdcard reboot the same as when you see the red triangle and accept the update. If no help there reboot normally with stock update still on sdcard. You should get a triangle notification of an update, accept the update.
adb shell
su
dd if=/sdcard/stock-recovery.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
Thanks for clearing this one out, I think I'm already good then!
Sent from my Galaxy Nexus
poochie2 said:
Thanks for clearing this one out, I think I'm already good then!
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
You're welcome!
I also think you are already good.