Database Info

[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] RAZR HD XT 925 Boots into recovery by default

So, today I trade my HTC One for a RAZR XT925, $350, and a water proof 32GB Sandisk ultra sd card on Kijiji. I thought it was kinda weird to get all of this stuff, but it seemed fine at the time. Afterwards however, I found out that every time you turn off or reboot the phone, it tried to go into recovery mode or something with the android guy and a bar at the bottom in a loop and always factory reset the phone, so no matter what, every time you turned it off, it'd reset it. After hours and hours of work, I have the bootloader unlocked, rooted, CWM installed, and Cynogenmod also installed. It no longer factory resets it (I think, but i sent a text to a random number and when I rebooted it was still there), however, everytime i power off and power on, it goes into recovery mode. This is very annoying and will make it very hard to sell again, but if I can fix this last thing, I'll have a solid phone until the waterproof S4 comes out as well as having made like $100.
So basically, I need to know what to do to make it boot into the rom by default and not the recovery. Also, I searched it up and someone else had a problem where they kept booting into AP fastboot mode I think, I tried that line, it said successful, but it didnt work. For me, it's booting into the recovery by default.

Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium

recovery
jmcdonald58 said:
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.

roguezz said:
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
Click to expand...
Click to collapse
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck

recovery
jmcdonald58 said:
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
Click to expand...
Click to collapse
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.

roguezz said:
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
Click to expand...
Click to collapse
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)

coldtech said:
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
Click to expand...
Click to collapse
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4

mentose457 said:
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.

coldtech said:
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
Click to expand...
Click to collapse
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.

mentose457 said:
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
Click to expand...
Click to collapse
is there an alternative to flash the stock ROM on a locked device?

coldtech said:
is there an alternative to flash the stock ROM on a locked device?
Click to expand...
Click to collapse
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.

mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
Thanks for the hint, will give it a try. RSDLite just completed flashing, but the odd behaviour of the phone is still the same. Guess I might just have a broken phone... :/

mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.

coldtech said:
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
Click to expand...
Click to collapse
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear

mentose457 said:
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
Click to expand...
Click to collapse
the fb_mode_clear was the culprit, thanks a lot!
and the error says: "downgraded security version. update gpt_main version failed. preflash validation failed for GPT" - which is still keeping me from flashing stuff via fastboot.
since I can't fastboot flash at the moment: do you happen to know where I can get the german modem image so that I can flash it using CWM? I think through all the flashing and trying I have a corrupt or wrong modem file (probably the US version). I can not log into the carrier network right now. it asks me for my SIM PIN and unlocks the SIM, but that's it. so I can't make phone calls or anything right now.

Stuck in startup animation loop

I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.

stuck on animation loop
slap_shot_12 said:
I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.
Click to expand...
Click to collapse
this gonna sound odd but i had exact same prob when i rooted and flashed chromix rom. it went. what i did was flash it once with the rom with secure wipe, then i flashed again. and it got stuck at optimizing apps,then i tried reflashing couldnt get it to boot, what i ended up doing was using clockwork mod to factory reset my tablet, then had to restart, and reflash, this time it actually got to main screen. dont let it discharge/reboot for awhile as im bout to post a issue im having with it. but thats what i did to make it work for me.

shadowarez said:
this gonna sound odd but i had exact same prob when i rooted and flashed chromix rom. it went. what i did was flash it once with the rom with secure wipe, then i flashed again. and it got stuck at optimizing apps,then i tried reflashing couldnt get it to boot, what i ended up doing was using clockwork mod to factory reset my tablet, then had to restart, and reflash, this time it actually got to main screen. dont let it discharge/reboot for awhile as im bout to post a issue im having with it. but thats what i did to make it work for me.
Click to expand...
Click to collapse
I'm not sure I understand --- how do I get to the clockwork mod if i can't get past the startup animation? And I've tried a bunch of roms with secure wipe and i get an error from every one of them.

didnt you install clockwork mod first?
slap_shot_12 said:
I'm not sure I understand --- how do I get to the clockwork mod if i can't get past the startup animation? And I've tried a bunch of roms with secure wipe and i get an error from every one of them.
Click to expand...
Click to collapse
the thing i found showed me to installed the clockwork mod first before i did any flashing, i rooted device then i flashed once clockwork mod was installed, i had to root, then install rom manager and goo manager, from within there i installed the clockwork recovery script/mod then i proceeded to flash chromi-X DEODEX.

Did you flash the correct bootloader? I had the same problem, look for my posts in the last few pages of ChromiX.
Here: http://forum.xda-developers.com/showpost.php?p=41658701&postcount=2716

slap_shot_12 said:
I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.
Click to expand...
Click to collapse
Seems to me you installed Asus factory stock rom JB 4.2.1 (10.6.1.14.4), which means you have the latest bootloader, then you unlocked and rooted your device, however, you never installed any custom recovery like TWRP or CWM (clockmod). Now your device is boot looping. You need to boot into stock recovery by turn off your device, hold volume down and power button until you see white text on the screen, now release both buttons, you should see 3 icons (RCK, Android and wipe data). NOW you are in fastboot mode. Let me know at least you can get that far, before we continue....

buhohitr said:
Seems to me you installed Asus factory stock rom JB 4.2.1 (10.6.1.14.4), which means you have the latest bootloader, then you unlocked and rooted your device, however, you never installed any custom recovery like TWRP or CWM (clockmod). Now your device is boot looping. You need to boot into stock recovery by turn off your device, hold volume down and power button until you see white text on the screen, now release both buttons, you should see 3 icons (RCK, Android and wipe data). NOW you are in fastboot mode. Let me know at least you can get that far, before we continue....
Click to expand...
Click to collapse
buhohitr -- You're exactly right. I can boot into stock recovery. When I select Android or wipe data it goes back to the animation screen and hangs up. When I select RCK it goes to the Android guy and says installing update but then it show him fallen over and the word Error. I've tried RCK with a memory card that has a number of different ROMs on it but the same thing keeps happening.

slap_shot_12 said:
buhohitr -- You're exactly right. I can boot into stock recovery. When I select Android or wipe data it goes back to the animation screen and hangs up. When I select RCK it goes to the Android guy and says installing update but then it show him fallen over and the word Error. I've tried RCK with a memory card that has a number of different ROMs on it but the same thing keeps happening.
Click to expand...
Click to collapse
Give this a try, the factory Asus firmware zip file that you downloaded, unzip the file, you should see another zip file, rename this new zip file to "EP201_768_SDUPDATE.zip" (without quotation), then copy it to the root of your sdcard then boot into stock recovery and execute the RCK again. Make sure you don't have any other zips laying around in the root of your sdcard.

You are truly a god among men.
buhohitr said:
Give this a try, the factory Asus firmware zip file that you downloaded, unzip the file, you should see another zip file, rename this new zip file to "EP201_768_SDUPDATE.zip" (without quotation), then copy it to the root of your sdcard then boot into stock recovery and execute the RCK again. Make sure you don't have any other zips laying around in the root of your sdcard.
Click to expand...
Click to collapse
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.

slap_shot_12 said:
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.
Click to expand...
Click to collapse
Somehow the stock recovery was reinstalled on your tablet, thus letting this method work. It however does not on CWM or TWRP. All you did was manually reinstall a stock rom back onto your tablet. How it got the stock recovery is beyond me unless you flashed a stock ROM from CWM and didnt realize what you were installing.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

slap_shot_12 said:
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.
Click to expand...
Click to collapse
Since the JB 4.2.1 upgrade, this is the most reliable method to install Asus full stock firmware. Also, since you're unlocked, let root the device by go here http://forum.xda-developers.com/showthread.php?t=2230763 download the tool and root it. Once rooted, I suggest that you should install TWRP custom recovery, by download Goomanager from the market, open the app and tab on the 3 little boxes on the top right hand corner, select "install recovery scripts" , this will shutdown your device and install custom TWRP recovery script, once this installed, you can download "rebooter" from the market and this app has many options, one of them is allowed you easily boot into custom recovery.

[Q] I might have hard bricked my nexus

I have a nexus 5.
16GB model.
5.1.1
Rooted.
TWRP 2.8.6.1
I was about to flash CM 12.1 .
I pressed wipe but it froze, I left it that way for about an hour and decided to research about what is happening. A lot of comments on some thread I read said that turning it off and then on worked for them and I did the same. Now all I get is a flashing Teamwin logo. The only accessible feature of the phone is the Power off/Start/Bootloader/Restart Bootloader thing-y. Whichever of them I press I get the flashing Teamwin logo.

Just wait it takes awhile

@bigglongruler

bigglongruler said:
I have a nexus 5.
16GB model.
5.1.1
Rooted.
TWRP 2.8.6.1
I was about to flash CM 12.1 .
I pressed wipe but it froze, I left it that way for about an hour and decided to research about what is happening. A lot of comments on some thread I read said that turning it off and then on worked for them and I did the same. Now all I get is a flashing Teamwin logo. The only accessible feature of the phone is the Power off/Start/Bootloader/Restart Bootloader thing-y. Whichever of them I press I get the flashing Teamwin logo.
Click to expand...
Click to collapse
Well you still have access to the bootloader luckily. Best part about a Nexus is that they're difficult to actually brick. Boot your phone into the bootloader and either fastboot flash recovery to reinstall twrp or use fastboot to reflash the stock system images.

davehasninjas said:
Well you still have access to the bootloader luckily. Best part about a Nexus is that they're difficult to actually brick. Boot your phone into the bootloader and either fastboot flash recovery to reinstall twrp or use fastboot to reflash the stock system images.
Click to expand...
Click to collapse
Thanks man, that's exactly what I needed. I tried to re-flash TWRP but had the same problem but when I flashed the stock system images everything went back to normal.

bigglongruler said:
Thanks man, that's exactly what I needed. I tried to re-flash TWRP but had the same problem but when I flashed the stock system images everything went back to normal.
Click to expand...
Click to collapse
Glad I could help, and that your phone is up and running again.
Take care.

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: