Database Info

[Q] Bricked ? - Nexus S

I have tried to unlock and root my Nexus S. I achieved unlock, but I am having problems with ClockworkMod Recovery v4.0.0.2 When I reboot, all I get is "Google" in the middle of the screen, with an "unlocked" lock image at the bottom of the screen. I am a new to this, and may have done something wrong.
Paul
Nexus S (Rogers)

Barlaw604 said:
I have tried to unlock and root my Nexus S. I achieved unlock, but I am having problems with ClockworkMod Recovery v4.0.0.2 When I reboot, all I get is "Google" in the middle of the screen, with an "unlocked" lock image at the bottom of the screen. I am a new to this, and may have done something wrong.
Paul
Nexus S (Rogers)
Click to expand...
Click to collapse
You have to be more specific on what you did.
Did you flash a ROM?
.. What did you do?
The "unlocked" image is supposed to be there.
Hold Volume up + Power then go into recovery. Upon there, you should be able to do something. Perform a nandroid restore, flash a ROM, etc.
Remember when you flash a ROM you must wipe: factory settings, cache, dalvik
I'm here thinking you flashed a ROM and didn't wipe so it's not loading the ROM.
If this is the case, just wipe the 3 things I said above and reflash the ROM and then reboot and you'll be on your way.
And please stop using the term 'brick' it is not bricked.
Brick doesn't mean your phone doesn't start and it seems like its broken. Brick means to the state where you CANT turn on the phone AT ALL.

You need to flash the recovery image correctly.
Fastboot flash recovery cwmfilename.img
Then turn off phone and boot. Up by volume up and power to get to bootloader then select recovery.
Sent from my HTC Sensation 4G using XDA Premium App

Thanks for your help. You were right. I have everything working now. Thanks.

[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

Restore Stock Recovery via ADB?

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.

[Q] Factory Reset using TWRP now it asks for encypted password upon boot

I just got my new S5, so it was time to nuke my S3 to get it ready for sale. My S3 is running 4.1.2 rooted with an unlocked bootloader and TWRP 2.5.0.0. To ensure a better wipe I encrypted the device and then did a factory reset. Now upon booting back up, I get a screen that reads: Enter password to access encrypted device storage. So I entered my password and it won't accept it. I cancel out of it, nothing works - I'm stuck.
I'm trying to reset the phone back to 4.1.2 and have no idea what I need to do next. Any help appreciated.

If no one knows how to fix this is there a way using TWRP or something other method to flash my S3 back to stock 4.1.2?

I looked at your thread earlier and I was wondering how to do it myself. Since your on an unlocked bootloader you can flash it back to another version, however I'm not sure if because having encryption enable it will let you
From my CM11 S3

SOLVED!
This Wonderful Guide from droidstyle helped me out.
1. I already had the USB drivers installed so I skipped to Section 5: How to Odin back to Stock from any rom/recover from a soft brick/flash a stock radio.
2. Downloaded the appropriate stock firmware, in my case it was VRALG1 4.0 ICS since I was on 4.1.2 and was not unfortunate enough to use any OTAs (4.3 and up) which permanently locked the bootloader.
3. Power on phone to Download mode (Hold Power on, Volume down and Home key at the same time). Make sure Binary Flash Counter is set to NO. Press Volume Up to select download mode.
4. Connect phone to computer and follow the steps on using ODIN to flash the stock image.
Phone reboots, wait and then viola - it booted just fine and asked me to set up the phone. Just to play it safe I rebooted to stock recovery, wiped cache and did a hard reset.
Now I will unlock and root the phone and then it's ready for sale. :good:
BTW I tried to find a stock 4.1.2 rooted and unlocked image but couldn't. If I find it I will flash it.

[Q] [HELP!] Bootloop unlike any other

So here is the deal. I was running CM 12 with TWRP on my Nexus 5 for the past few weeks. After the 12.1 OTAs rolled out, with their issues in Google Play Services compatibility, I decided to go back to stock. For that I used the Nexus Root Toolkit option flash stock/ unroot. The process finished said that the bootloader needed to be unlocked, silly me for forgetting that step. I unlocked the bootloader, again using the Nexus Root Toolkit and the stock recovery. After it finished erasing data, it started this weird bootloop where it goes to the google logo, with the unlocked bootloader symbol, then immediately goes to the TWRP splashscreen, where it will stay for approximately 20 seconds before the screen goes black and the splashcreen comes back again.
I've tried shutting it off and on again, even tried accesing it via ADB, all with no luck. Any suggestions?

Toolkit f'd you up pretty bad. Why would you need to unlock your bootloader if you were already rooted and running a custom rom?
Try downloading the factory images and flashing them..
Sent from my Nexus 5 using Tapatalk

Go ask the toolkit dev. All you can tell us is which button you pushed. Without knowing what script was run and what it did, we can't tell you what happened.
And I second the above; why would the bootloader need to be unlocked when you already successfully flashed? Because the toolkit told you that you needed to?

axstcz said:
So here is the deal. I was running CM 12 with TWRP on my Nexus 5 for the past few weeks. After the 12.1 OTAs rolled out, with their issues in Google Play Services compatibility, I decided to go back to stock. For that I used the Nexus Root Toolkit option flash stock/ unroot. The process finished said that the bootloader needed to be unlocked, silly me for forgetting that step. I unlocked the bootloader, again using the Nexus Root Toolkit and the stock recovery. After it finished erasing data, it started this weird bootloop where it goes to the google logo, with the unlocked bootloader symbol, then immediately goes to the TWRP splashscreen, where it will stay for approximately 20 seconds before the screen goes black and the splashcreen comes back again.
I've tried shutting it off and on again, even tried accesing it via ADB, all with no luck. Any suggestions?
Click to expand...
Click to collapse
You should put it in fastboot mode and flash a stock android image. will wipe your device but your sanity and phone will be back to normal. if you need help finding fastboot commands and such let me know.