[Q] Bricked ? - Nexus S - Nexus S Q&A, Help & Troubleshooting

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.

Related

[Q] Nexus S stuck on google boot logo

Hey everyone,
I got a Nexus S that gets stuck on the Google logo when it starts up. I can get the phone into the bootloader and I can also clear the data from the phone but that hasn't fixed it. If you have any suggestions, please respond to the thread. Thank you!
I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??
brenix said:
I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??
Click to expand...
Click to collapse
Yah, i just did it and it didnt solve my problem but thanks for the suggestions
Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?
lostgoatX7 said:
Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?
Click to expand...
Click to collapse
No but the person I purchased it from might have. Does anyone know how to load stock android becuase I'm not experienced with rooting.
Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom
any solution?
hi guys.i have the same issue.does anyone have a solution for this?
i had the same problem.....what i did was cleared everything on recovery and flashed cyanogenmod and now is all good (this was of course after changing my underwear lol )
Smokexz said:
Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom
Click to expand...
Click to collapse
how can I do it?
I got the same problem.
Nexus S stuck at Google lOgo
I have the same Issue
Here is the Boot Loader Details.
Boot Loader version is : I9020XXKA3
baseband : I9020XXKB1
Locked sTate : LOCKEd
I have downloaded the stock nandroid , but not able to put it on the phone memory.
then tried to unlock the BOOT Loader in order to install Clock..Recovery , but there also after selecting Yes while Running Fastboot oem unlock , phone does not do anything.
then tried to load the file using ADB mode, but when i run adb devices , it doesnt show any device. or when i run adb remount it says "Error device not found"
Please help me get out of it.....
Similar problem
Ahoy!
I have a similar problem. Bought the phone in the States so I'm not in a position to go into psychological warfare with some poor high school kid working in Best Buy. Plus, all this is totally my fault...
I dropped my phone down the can (if it was a Blackberry I would have flushed) and manged to rescue it through handy desiccant (open shoe box gel packets) and rediscovering religion *cough* until this is sorted *cough*.
When I eventually fired her back up (the battery had flatlined btw) I'm stuck on the Google screen. So battle commenced...
The phone was stock 2.3.4, never rooted, no CW Recovery.
T-Mobile I9020T.
I sorted the Win 7 USB device issue
Can see it with fastboot but not adb.
Can access the bootloader screen so tried the Recovery option but it just goes into Google splash screen each time.
Flashed various versions of CW recovery (herring, mecha) to it but hitting the Recovery menu on the bootloader screen just keeps going to the Google splash screen.
This is where I complicated things because I'm a complete and utter noob to the rooting game.
I'm fairly sure I was careless early on with the appropriate versions of the full stock and singular recovery images I was trying to flash, so this might be useful information.
I downloaded ODIN and tried it briefly but it didn't seem to recognise my phone (I keep reading the ODIN needs to be tricked into recognising the phone). I also keep reading the ODIN is unnecessary if you have fastboot access so let this line of inquiry slide.
I downloaded a full Clockwork Mod Stock Nandroid (Stock-GRH78-Nandroid) and attempted to flash it all. The boot img failed due to a "FAILED exceed blocks" problem, so I tried this (classic noob try anything):
"Got a failure when trying to flash back a 8Mb boot.img?
From example above I started from a boot.img smaller than the full boot partition but if you create a new boot.img or start from an image of the full partition taken manually or with clockworkmod, boot.img will be 8Mb-large (8388608) and fastboot fails with "FAILED exceed blocks 0x00000020 > 0x0000001e".
I'm not really sure about what size the file should be but as it's filled with zeroes till reaching 8Mb, I decided to cut it:
0x00000020 => 0x0000001e means for me 8388608 / 0x20 * 0x1e = 7864320, so I did:
dd if=boot.img of=boot2.img bs=262144 count=30
fastboot flash boot boot2.img"
Click to expand...
Click to collapse
This worked! noob W1NNAR!!!11one111!!
I got the same thing with the recovery and the same "trick" worked. When it got around to the system img it eventually failed with a "Magic number" problem. Checking this problem out made me realise I can't keep messing around and should "get help".
As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.
Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
hand_of_henry said:
As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.
Click to expand...
Click to collapse
Do "fastboot erase recovery" then flash a different ClockworkMod build. Try 3.0.2.4
Sent from my Nexus S using XDA App
Thanks Matt.
Just tried erasing (hadn't before) and flashing 3.0.2.4 - no dice. Tried erasing and 3.0.2.5 and no luck either.
twitch153 said:
Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
Click to expand...
Click to collapse
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.
hand_of_henry said:
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.
Click to expand...
Click to collapse
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App
How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App
asafru said:
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thanks asafru,
I tried booting into recovery but again, no luck. I did it with one of the recovery builds you suggested (the cyan recovery but having trawled that thread I'm not sure what the difference is between the colours).
matt2053 said:
How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's a fair point - I had expected to see the recovery screen fairly sharpish.
I've waited 15 minutes now on the splash screen for flashings of cw 3.0.2.4, 3.0.2.5 and the mysterious cyan build of 4.0.0.2.
I imagine this is an appropriate amount of time for the recovery to kick in?
I've tried all these recoveries using the Recovery menu item and also using the booting directly recovery method that asafru suggests above.

[Q] Only have Hboot...

Hi, im new to rooting and stuff and i could use some help. after i flashed twrp and did a backup followed by a reboot i lost access to to everything except hboot. No i cant use my phone or twrp but i still have hboot unlocked. can anyone lead in me in the right direction? thanks
shadyboy039 said:
Hi, im new to rooting and stuff and i could use some help. after i flashed twrp and did a backup followed by a reboot i lost access to to everything except hboot. No i cant use my phone or twrp but i still have hboot unlocked. can anyone lead in me in the right direction? thanks
Click to expand...
Click to collapse
Reboot the phone holding power and volume down until you're into the bootloader screen and then select recovery. Try restoring the backup you made. If that doesn't work go back into recovery, put a rom on the sdcard, and flash it. Then reboot.
i cant get to my sdcard because i cant get to twrp anymore. everytime i have it reboot from bootloader it just goes the htc screen and turns off. :crying:
Reinstall twrp from fast boot.
Sent from my HTC One XL using xda premium
Yea, try that. After that select reboot recovery from the bootloader not reboot.
omg i got twrp back. wow that scared me thanks.

Rooting and recovery

I have a problem when I reboot into recovery. The recovery that I am using on my HTC One S is TWRP. When I go into the bootloader and go to recovery, it will boot up to the HTC screen with red text on it. Then the phone will restart and boot normally. Then I would have to go to bootloader again and go into recovery and then it goes into TWRP. I don't know why I have to do this twice. I am not sure what I have done wrong and I can't find a way to fix this. Also I've been trying to flash CM10 and on the first boot, it stays on the animation for a long time. And one last thing. Root checker says I am rooted but when I use Apex Launcher and use a stock HTC widget, it says that it doesn't have root permissions. So can anyone help me with this? This is also my first time on XDA. Another problem. When I restore from a backup, it boots up fine. But then it stays on the lockscreen for couple of seconds and it restarts again. And when I rooted my phone by flashing SuperUser, It didn't say upgrading android. Was it suppose to?
Bump. I too have this problem with booting twice to get into recovery and can't find any answers. Thanks.
I have the exact same issue. I experienced it with both CWM and TWRP. Also when I reboot from recovery, the device seems to reboot twice, and it gets back to normal with a dialog asking if I want to send an error report to HTC. I was beginning to wonder what I have done wrong.
PJMAN2952 said:
I have a problem when I reboot into recovery. The recovery that I am using on my HTC One S is TWRP. When I go into the bootloader and go to recovery, it will boot up to the HTC screen with red text on it. Then the phone will restart and boot normally. Then I would have to go to bootloader again and go into recovery and then it goes into TWRP. I don't know why I have to do this twice. I am not sure what I have done wrong and I can't find a way to fix this. Also I've been trying to flash CM10 and on the first boot, it stays on the animation for a long time. And one last thing. Root checker says I am rooted but when I use Apex Launcher and use a stock HTC widget, it says that it doesn't have root permissions. So can anyone help me with this? This is also my first time on XDA. Another problem. When I restore from a backup, it boots up fine. But then it stays on the lockscreen for couple of seconds and it restarts again. And when I rooted my phone by flashing SuperUser, It didn't say upgrading android. Was it suppose to?
Click to expand...
Click to collapse
I would suggest downloading the newest twrp recovery IMG and flashing it with fastboot.. As far as flashing cm 10 make sure you flash the boot.IMG through fastboot before you flash the ROM..and wipe both caches after installation.. If you get stuck at boot animation go back to recovery and wipe both caches again...are you guys all using the all in one tool... Or flashimggui..?
Sent from my HTC One S using xda premium

Nexus soft-Bricked :(

Hey, xda people.
I have a consult here:
I have a hammerhead bright red (if that is useful to know) and I install the AOKP in the latest version, with root and super su. I install the ROM toolbox app from the play store and in there there is a feature in which you can install ROMs and ROM utilities. One of them is the Franco kernel so I went ahead and installed, thought TWRP, but because I didn't knew there were going to be any problems I didn't do any kind of wipe. My phone then boot into the Google loading screen but stuck there indefinitely. I tried getting into the bootloader/recovery and repowering my phone but it made no difference.
Hope you can help me up, cheers!
(All ideas are thanked)
Flash the stock rom using fastboot.
Lokke9191 said:
Flash the stock rom using fastboot.
Click to expand...
Click to collapse
Dude, it's impossible for me to get into the fastboot, it just won't load to me
Hold power about 10 sec(hard reboot)until device powers off to reboot and then hold volume down. This will get you into the bootloader using volume keys toggle to and select recovery using power. In twrp reflash rom. Wipe cache and dalvik and reboot. If that doesn't work you can do the same except wipe for clean flash flag ROM gapps reboot. If all else fails go to boot loader and flash factory images via fastboot.
Edit... You say it won't load meaning you can't get there?
If you will be flashing images it will wipe your device so that's a last option.
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 5 using Tapatalk

stuck in loop, possibly a different kind of loop

I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
atomkrieg said:
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
Click to expand...
Click to collapse
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
soupysoup said:
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
atomkrieg said:
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
Click to expand...
Click to collapse
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
soupysoup said:
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
in the end fastboot, since i coulndt see how i could copy the img over to install via twrp
im pretty sure the button is fine, since it was cycling from the ota update install, then was working fine unlocking the bootloader, but after the flash, it crapped the bed.
Different problem
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
siddhu007 said:
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
Click to expand...
Click to collapse
ok, took it into a shop, got the power button fixed. It must have been on the way out because literally one minute it worked and the second it didnt. now i think ive got it narrowed down. it's saying it's unable to mount /persist. ive tried the various fixes:
e2fsck/dev/block/platform/msm_sdcc.1/by-name/persist
and
make_ext4fs/dev/block/platform/msm_sdcc.1/by-name/persist
but all i get is a not found error. not sure what to do from here on.
success!! i ended up stumbling on a bit how to restore the persist partition i didnt try. got a custom rom installs and everything works. thanks to everyone who tried to help!!
stuck in bootloop while flashing cataclysm rom
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
When it was stuck in the loop, I had to hold vol up and down with the power button (wait a few secs until it was completely off) then reboot holding down + power till it opened the bootloader. if that doesnt work, try reflashing the bootloader via fastboot. I only found out i couldnt mount the persist partition by looking at the terminal window in twrp after trying to install a rom which kept it in the boot loop. I then used the cmd: make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist to rebuild it.
jpau11 said:
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
Click to expand...
Click to collapse
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
audit13 said:
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
Click to expand...
Click to collapse
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
jpau11 said:
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
Click to expand...
Click to collapse
Great to hear it. Congratulations:good:

Categories

Resources