Related
Hello, before I call Samsung in hopes they might give me a RMA, I need help.
I had unlocked the bootloader in the past and had recently installed the IMM26D official stock rom that was not rooted. This worked fine for a month or so then yesterday the phone would not boot up anymore, just sitting at "GOOGLE' across the screen with the unlocked padlock on the bottom. So here is what I have tried ;
I was able to load CWM on it, but once in there, I could not do anything that pointed to the sdcard (mount, mount usb, format, wipe and erase). The minute I tried this, the log would show "Error mounting \sdcard\".
I then tried ODIN to see if I could reload the IMM26D, It would start and get only about 5% of the way and just stop for eternity. I tried the same cable I used before when this worked, and a different one.
And at the last step (Stupidly), I tried doing a fastboot oem lock and it locked it. Now when I go back in and do a fastboot oem unlock, the options come up on the screen and when choosing Yes to unlock, the phone just locks up.
Could this be a corrupted or damaged SDcard in the phone (now I wish it wasn't internal and rather a external one) ?
Is there ANYTHING I can do at this point? Is there a .PIT file specific for this phone that I can try loading with ODIN ?
I would love to somehow load the "stock" recovery back on it but since I can't unlock the bootloader, seems that idea is toast. It would be a lot easier to take to Sprint or send to Samsung if it didn't have CMW on it.
Sorry for the long post, but thanks in advance ..
what happened with this issue? Was it resolved, did you have it swapped with another phone?
Sent from my Nexus S 4G using Tapatalk 2
Ended up calling Samsung and sending it in, luckily it was still under warranty. Looks like they fixed it and waiting for it to return. There was nothing I could do on my end at the time, it was a corrupted internal SD card.
Hello all, I entered into recovery mode and got this warning today. http://i.imgur.com/CHya85E.jpg
For more info, I updated the other day to 4.1.2 and it removed my root access. Now, I was simply trying to remove the SuperSU app by going into recovery mode (don't know if it can be done there or not). Any help is extremely appreciated.
bootloader is locked. search around for an answer or someone will post it for you. I'm not the best at describing how to do it.
bobAbooE said:
bootloader is locked. search around for an answer or someone will post it for you. I'm not the best at describing how to do it.
Click to expand...
Click to collapse
Okay, thanks. Whenever I reboot my phone, there is text that comes up and says "custom" with an unlocked lock symbol. Could you point me in the right direction with this? Am I not able to go into recovery mode without the bootloader being unlocked?
I have the exact same issue. It came right after I upgraded Recovery to the latest Touch version. I am also on 4.1.2, but have been there a couple of weeks and have had no other problems. I don't believe I lost root with the upgrade.
If the boot loader has been relocked somehow, how can we fix it without being able to boot the phone? All attempts to boot including volume up/home/power, volume down/home/power, and home power just end up with the Verison message. It appears impossible to boot to recovery or even start the phone. I am lost.
See my thread called: “System software not authorized by Verizon Wireless has been found on your phone.” I also could not reboot the phone to fix it.
Some great info was posted there that enabled me to escape from the Verizon prison
Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin
Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?
If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.
[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS
Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.
So here is a string of steps I've already been through in trying to save my bricked Nexus 6: [Can't post outside link yet...]
Basically I got the 'your phone is corrupt' message from google and it kept forcibly shutting down. It would not boot up so someone suggested I side load a rescue OTA. At this point recovery existed and I went through all the steps and had it installing, only to fail mid-way through (~52%) and give me a 'read error' on my command prompt. I started the whole process over again just fine and it got to 73% before 'read error' failing again. I thought no big deal, I'll just keep doing this until it gets to 100%. Nope, recovery is gone. I cannot get there anymore. I start into Fastboot mode and scroll to recovery and hit power and it just goes to a new Fastboot screen and keeps flashing every time I try to select it. The Bootloader logs give me a 'failed to validate boot image: ret=-1' message and says 'Boot up failed.'
I can't find a single guide online that doesn't require recovery mode to work. At this point I don't care about my data and just want to get this phone working again before I throw in the towel and pay Motorola $175 for a refurb. I'm just barely over a year too. The Nexus 'expert' gave up and blamed the memory and maybe he is right but I wanted to run this by you guys first. This phone was completely stock and unrooted.
The only reason why I feel there is still a chance is because when I connect USB my computer reads it as an Android Device in Device Manager with 'Android Bootloader Interface' as a sub device. If the computer can read it, isn't there a chance that some kind of software exists that can forcibly load a new bootloader onto this phone without recovery? I'm 'competent' with computers and android phones but I haven't rooted or done any custom stuff in years so I'm at a loss for what's out there.
Thanks in advance for any help you can give me, even if it's to tell me I'm SOL.
Ok so far I have tried to load a custom recovery but that requires an unlocked bootloader. Then I tried using a toolkit to flash stock as a soft-bricked device but that also requires an unlocked bootloader and I can't unlock the damn bootloader. You know, I thought I was just playing it safe by leaving this phone as-is instead of playing around with it but it looks like I screwed myself by doing so.
Is this the wrong forum for this question?
JQ3 said:
Is this the wrong forum for this question?
Click to expand...
Click to collapse
Sorry for the delay
We have a dedicated help section for your device here
http://forum.xda-developers.com/nexus-6/help
Ask there to receive help
Good luck
As per title, it just happened while I was using the phone while charging. Trying my luck as I'm not in the country(Australia) that I bought my Pixel from. Grateful for any suggestion that the sub can provide. Non rooted stock rom
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Yes only bootloader. What you have mentioned do not require recovery mode right ? Cos I can't boot into it. Thanks for your reply
k.s.deviate said:
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Click to expand...
Click to collapse
The bootloader would have needed to have been unlocked already.
indifferent1 said:
The bootloader would have needed to have been unlocked already.
Click to expand...
Click to collapse
no it doesnt, I suggested unlocking the bootloader first, that way it factory resets. this might fix the problem, if not its unlocked so he can flash the factory image.
Bump? I'm having this problem as well.
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
graymoment said:
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
Click to expand...
Click to collapse
I'm having the same issue. My wife's Pixel entered a continuous boot loop today. It only loads the white screen that says "Google." I can enter the bootloader, but when I select "recover," it goes back to the bootloop. As far as I know, she is on Android 8.1, debugging mode is off and the phone is 100% factory.
If anyone has solved this issue, it would be greatly appreciated!
Thanks
has anyone figured this out?? this happened to me today, i was using the phone, the poof it restarted itself and stayed in a boot loop. i can get into the recovery, i tried wipe/factory reset. any suggestions? google told me i need to send it to whatever company to get it fixed or get a new phone. verizon told me to go through insurance. insurance told me to go through verizon because i may be able to use the extended warranty. went back to verizon but they wont take it because the screen cracked a year ago. its not a deep crack and it didnt affect the phone at all, never had an issue. so now i go back to assurion and now they need an affidavit about my screen being cracked. im at a loss.... i havent rooted a phone since my droid x, then s3 days. so im essentially new again!
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
thedosbox said:
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
Click to expand...
Click to collapse
I had the same thing happen yesterday (not long after the Android 10 update). I was finally able to get it to boot after multiple tries and it stayed up long enough for me to enable "OEM unlocking" in Developer options. Now at least I have the option of unlocking the bootloader and re-flashing the OS with an image directly from Google.
Has anyone been able to get past this problem by reflashing the image? I suspect the underlying problem is some kind of hardware fault with eMMC, DDR, or the SOC itself.
One other interesting behavior I noticed is that the only way to shut it down and stop the bootloop is to select the "Power off" option in the bootloader menu. However, if I plug it in to charge when it is fully powered "off", it will start up the bootloop again.
Same sitution here. A couple of days after installaing it suddenly went inte a G-bootloop frenzy.
Erratic though, sometimes I could boot up (2-3/40 boots) but then it froze and started again.
Also Recovery and Safemode is very hard to get into.
Got in once or twice out of 100 boots, Bootloader Fastboot is generally reachable though.
It exhausted the battery and now I'm holding off trying to interfere, until I get more info off the net.