Database Users

Stuck on google logo!

Hello,
I need a bit of help with my nexus s. I was trying to install ICS on it the other day and something went wrong so it is now stuck at the google logo with the unlocked padlock underneath. I would just go into recovery mode but the power button is broken, now i can get into fastboot mode but for some reason i cant do anything in it for example the volume buttons dont move the selection up or down and obviously i cant select anything because the power button doesn't work. If anyone could help me out with this I would greatly appreciate it!
Thanks,
Alex

Well you cant get into recovery except from the boot loader I think
If you can somehow manage to get the power button working even once, you should be able to fix your phone by flashing a new ROM, for ICS I first installed GB 2.3.6 and then went into the stock recovery mode, held power + volume up and selected the ICS update zip file, which I had renamed to update.zip
I hope that will help you if you manage to get into recovery, maybe send it to the company, or try pressing the button somehow I dunno, sorry :S
Sent from my Nexus S using XDA App

You can also try flashing a ICS compatible kernel using fastboot, that is if the kernel is responsible for you being stuck...
Sent from my Nexus S using XDA App

I havn't had much personal experience, though you might be able to find some information searching around for flashing a rom via adb, or something of the sort.

been there before
what i did is, flash a Custom ROM like MIUI 2.3.7 then flash stock 2.3.6 and then flash ICS stock 4.0.3

I think this app will help you:
http://www.mediafire.com/?2jx8xtx2602hi23
extract it and click bat.run
if your phone is at the 'google' kernel splash screen, it should auto-boot the phone into bootloader, if I remember correctly, and if you use command line adb to boot into recovery you should be able to use the capacitive buttons to navigate & select so you can get a rom installed. back=back, home=up, menu=down, search=select

Booting into Revocery

Ok so I just got my Nexus 7 unlocked and rooted no problem, I have done this on a few Galaxy Nexus phone without issue.
Now here is the strange part, if I adb into bootloader then select boot into recovery it works (CWM Touch) however if I manually go into the bootloader, hold volume keys and select reboot into recover it will just hang at the google screen.
I can get out of that bu holding power until the deivce reboots back to the OS.
I can do this as much as I want, from using adb into bootloader and get into recovery, but not manually. What can i try?
I have already tried flashing stock recovery, and other CWM non touch and all act the same way, what am I missing?

I had the same issue completely stock. No idea what causes it, and I've still not fixed it either.

Good to know I am not alone.

same here! even with 6.0.1.0
Sent from my Nexus 7 using xda premium

I rooted a week ago and this problem drove me nuts. I was paranoid enuff not to wanna flash anything. Within the last few days it was found that you can do the 3 button thing, get into the bootloader and select recovery ONLY if the N7 is plugged into something with a powered usb port. It seems any computer will work, and I read where one guy tried assorted ports like tvs, direct tv box, xbox, etc. These also allowed the buttons to activate bootloader & select recovery. There must be something within the port which requires power in order to get past that Google screen? It doesn't matter whether your on cwm 6.0+ or TWRP. It seems to be a hardware issue as far as I know at this point.
I read where a guy said that during a bootloop, hold power + volume down and wait, sometimes as long as 50 seconds. Eventually it has always worked for him. I've had one bootloop and didn't try that method. I just connected usb cable to the laptop, held the buttons and was in. That is a summary of what I know as of now.
Sent from my Galaxy Nexus using Tapatalk 2

I can confirm that it only works if you have USB plugged in.
Anyone able to get past the red triangle? It seems to just hang there for me

Its a bug with the early CWM Official Port i think, try TWRP Recovery

The only way I was able to get into CWM was to use ROM Toolbox or ROM Manager to boot into recovery. :\ Hangs for me while holding down volume and power.

[Q] Nexus 10 Bricked :/

Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.

Hyflex said:
Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.
Click to expand...
Click to collapse
Reboot holding Power and both volume buttons and you should be able to get to recovery

brees75 said:
Reboot holding Power and both volume buttons and you should be able to get to recovery
Click to expand...
Click to collapse
I'm on the xda-devs irc at the moment and we've got so far... but still its messed up.
- Recovery is dead (can't get into it atm, orange triangle guy every time)
- Flashed stock via fastboot and unrooted, but on reboot I get the triangle guy.
- I can boot into unsecure roms (temporary)
- I can boot into temporary recoverys, clearing cache works but davlik cache and factory reset doesn't work both say "failed"
I'm currently awaiting the guy whos been helping me get back from the shops.

From what I remember you need to either install something or run a command after "oem unlock" for security reasons. Android wont let you boot back into the OS until you have wiped all the data after the unlock.

The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD

Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!

altimax98 said:
The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
The pressing 3 buttons at once; cycling to recovery... method wasnt working because there was no recovery accessable what so ever and temporary recoveries weren't working.
That's what a few guys in IRC said too about the toolkits haha
Thankfully some guy by the name of YellowGTO spent some time helping me out and we finally got there in the end, he's awesome and extremely patient
jlvlawrence said:
Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!
Click to expand...
Click to collapse
Okay, updates for everyone just incase someone else gets the problem.
- Factory Images via fastboot flashed fine but never stuck, just kept returning me to triangle dude.
- Fix permissions, did nothing
- Restoring stock recovery did nothing, I still couldn't get to a recovery.
- Temporary recoveries only had limited functionality.
I decided to unlock an already unlocked phone again
I flashed stock, Ran file permissions
Used the temporary recovery to clear the cache/davlik (previously didn't work)
I re-rooted, Installed TWRP 2.4.4.0, this finally stuck.
I double checked that it had stuck by booting the system, rebooting into recovery, powering device of and powering it on to Android. It was all working perfectly.
I then made my backup and put a custom rom and kernel on, it's working lovely now.
It seems that somewhere during the oem unlock it messed up some partitions or something resulting in recoveries and flashing not to work/stick.

Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD

altimax98 said:
Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That's the thing, the recovery wasn't available in any way shape or form and temporary recoveries wouldn't wipe the cache... the oem unlock went wrong somehow even though it had full power, wasn't interrupted or anything.
I'm glad it's all working now, I thought the device was completely dead at one stage.

I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well

anazei said:
I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well
Click to expand...
Click to collapse
I think you are right and that was his problem..... The toolkit actually told him how to handle this ... but who reads all the that text anyway

[Q] Can't boot after flashing Cyanogenmod

Just got a brand new LG G2. I've already rooted and flashed TWRP, but after I flashed CM 10.2 RC1, I couldn't boot. I got stuck on a screen that says:
Code:
fastboot mode started
udc_start()
After messing around with it a bit, I was able to get back to recovery. I double checked the MD5's of the ROM and Gapps but they were both correct, so I tried flashing again and got the same problem. I tried looking for a solution online, but I wasn't able to find anything.
I'm new to TWRP, and somewhat new to custom ROMs in general, so I'm really not sure what to do.
Has anybody encountered the same problem? Am I doing anything wrong?

gollum999 said:
Just got a brand new LG G2. I've already rooted and flashed TWRP, but after I flashed CM 10.2 RC1, I couldn't boot. I got stuck on a screen that says:
Code:
fastboot mode started
udc_start()
After messing around with it a bit, I was able to get back to recovery. I double checked the MD5's of the ROM and Gapps but they were both correct, so I tried flashing again and got the same problem. I tried looking for a solution online, but I wasn't able to find anything.
I'm new to TWRP, and somewhat new to custom ROMs in general, so I'm really not sure what to do.
Has anybody encountered the same problem? Am I doing anything wrong?
Click to expand...
Click to collapse
Never mind, turns out I am just a dumbass. The Cyanogenmod wiki gives you the download for d802 by default. I have the d800, so I was trying to flash the wrong ROM. :silly: That really should not have taken me that long to figure out.
In case anyone encounters the same problem in the future: If you are stuck on the screen I mentioned above, you should still be able to get back to recovery the normal way. (Hold down the power button until the phone turns off, then hold power + volume down until the LG logo appears. Release the buttons and hold them again until a screen appears asking you if you want to reset. Hit power twice to boot to recovery. From there you should be able to restore and/or fix your mistakes.) Make sure you downloaded the right ROM.

Did u download the correct Rom for your model, d800,d801 etc?
Sent from my LG-D800 using Xparent BlueTapatalk 2

[***RESOLVED***][HELP] Did I brick it?

Ok, friend of mine has the LS980 (Sprint G2). Got my SGS3 today and got CM11 on it, he decided he wanted CM goodness. So, I rooted with IO method, no issues. Couldn't find anything about a bootloader needing unlocked, but found a CWM installer using FreeGee (because I had the VBA[?] OTA upgrade, needed a different aboot, and FreeGee does this automagically) in these forums. Cool, so I did that. Rebooted to recovery, performed nandroid, wipe data/cache/dalvik, flashed CM11, rebooted. Got a boot loop, stuck at the LG logo, rebooting indefinitely. Wiped data and cache a few more times, still doing it, so I restored, and rebooted. Now, it wont boot. Holding power does nothing. Holding VOL-UP or VOL-DOWN and power, does nothing. If I plug it into USB, theres a red flashing led next to the top speaker, but it wont charge past 0%, and still, nothing.
Have I bricked it? How would I go about doing this?
I should have known this would be a pain. Tried to do my brother's G1 a while back, and it was the biggest pain in the arse

if u can boot into download mode find thread about flashing back to stock and install only d80010d version
Sent from my LG-D800 using xda app-developers app

lingarajug said:
if u can boot into download mode find thread about flashing back to stock and install only d80010d version
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
He has sprint not att

Ok, so I was able to get booted back. It went right to the restored stock/rooted, but it's still boot looping when I flash CM11. I re-downloaded CM11 and gapps, re-flashed CWM. Maybe I'll try the manual aboot flash and flash recovery with flashy, or whatever tool it was, see if that helps.

When the device is powered off, hold volume up and plug the device into the usb cable that is connected to the computer. If download mode comes up then you can return to stock by using this.

uToTMeH8 said:
When the device is powered off, hold volume up and plug the device into the usb cable that is connected to the computer. If download mode comes up then you can return to stock by using this.
Click to expand...
Click to collapse
That's how I was able to get back to stock I'll start another thread for the CM Boot Loop issue.

Fixed
Ok, I fixed the CM bootloop. Apparently, the modem from the ZVA OTA breaks AOSP ROMs, so I flashed the Furnace kernel, and the issues are completely resolved. I knew it had to be something simple, and I had a hunch that it was because of the ZVA update, and I was right. Thanks for the help, G2 bros and broettes. I'm going back to my Samsung world