Develop Bugs

Galaxy Nexus stuck on Google logo boot loop help [GSM]

I am running the stock rom without root and unlock and I got the 4.0.2 OTA update 3 days ago. Today when I do the pattern unlock my phone froze and reboot. Now I cannot get pass the Google logo boot screen.
I am able to get into the recovery mode but I don't want to do a factory restore as I don't have anything backup yet.
Is there any solution to this boot loop problem? I am surprise that I am getting this problem as I am running the stock rom without any root / mod.
If there is no solution to this, is there any way I can backup my phone before doing the factory restore?
Many thanks!

You can back up via adb. Try searching in the General threads, since there's a long topic on this...
Good luck!

Thanks, I do find information about backup, but I can't find anything regarding the bootloop...

When i got stuck at the Google screen with a bootloop i booted into the bootloader/fastboot screen with vol up+down power and i redid the one click all process and it basically rewiped my device and put it back to working again with unlocked bootloader rooted etc....
All you have to remember is what build number you have and let the toolkit work its magic.

tigersgt said:
Thanks, I do find information about backup, but I can't find anything regarding the bootloop...
Click to expand...
Click to collapse
Sorry, forgot to mention. You're probably gonna have to wipe via recovery - which is why I pointed you to a back up...

danger-rat said:
Sorry, forgot to mention. You're probably gonna have to wipe via recovery - which is why I pointed you to a back up...
Click to expand...
Click to collapse
I can't find a way to backup without going into Android. I can only go to Fastboot Mode.
Anyone know how to backup the file using abd without getting into android?

Why did make 2 threads about this. Unlock the boot loader and use adb to flash your stock. Image files. You will loose all data unfortunately but I think that's the only way to fix it.
Sent from my Galaxy Nexus using xda premium

Ok I'm stuck with the same problem now. I wanted to flash a ROM, so I downloaded AOKP, flashed it and rebooted and the phone refuses to boot past the Google logo and keeps rebooting again and again. I am able to get into the recovery. I have flashed the ROM several times and its still the same. I have done a complete wipe as well. Still no go.
Fastboot command doesnt work in the bootloader either. I have made sure the drivers are installed, still there is nothing when I type fastboot devices. If I type any fastboot command it just says <waiting for device> or something like that.
Any other suggestions? :-s

Softbrick'd. No idea what to do.

I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?

I had same problem. Follow the steps. Unlock it again and reboot to the system.
There enable developer option, enable debugging, enable unlock bootloader option.
Rebooted to fastboot mode
Install stock recovery
Adb sideload 3.2 full firmware.
After that reboot your phone to fastboot mode.
Unlock bootloader.
This should do it.
Sent from my ONEPLUS A3003 using Tapatalk

It's like you didn't even read what I wrote...
I said it doesn't boot to system, OnePlus logo appears for a split second and phone turns off.
Bootloader is locked and I cannot flash anything.
ADB Sideload won't read files. Gives the 'cannot read' error.

You know that you can load to bootloader by pressing volume up and power button right?
Sent from my ONEPLUS A3003 using Tapatalk

Monskiller said:
I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?
Click to expand...
Click to collapse
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!

ajaysoranam said:
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!
Click to expand...
Click to collapse
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?

I relocked the bootloader. Which wiped to factory reset.
That wipe deactivated the ability to unlock bootloader until reactivated from the system, which I cannot get to because the phone turns off/bootlops before loading it.

This happened quite a few times on this forum, there is really no reason to relock the bootloader on the op3, it is covered through warranty, but u will have to contact oneplus and they should walk u through and send u files to unbrick it if u r lucky

ovidiu1982 said:
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?
Click to expand...
Click to collapse
then you better get in touch with the op customer service. they will, from what i know, fix it thru a remote connection sitting.

I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.

karthikrr said:
I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.
Click to expand...
Click to collapse
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.

Bro don't worry now.
I am gonna guide you out of this.
First install an adb package like this.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Now get a toolkit like this.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Try to connect to fastboot and check for your device in the toolkit.
If failed then kill process adb in your task manager.
Now once connected.
Check OEM status and bootloader status.
Unlock if required.
Now.
Push twrp to your phone .
Then boot into it through the toolkit.
Now load a full ROM.
http://forum.xda-developers.com/oneplus-3/development/rom-op3lite-debloated-tweaked-fast-t3404996
Just copy paste it using your file manager on PC.
Them flash first make it boot and then root.
Hope this helped.

Monskiller said:
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.
Click to expand...
Click to collapse
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out

karthikrr said:
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out
Click to expand...
Click to collapse
Don't test it. I've already done it by mistake.
It replaced recovery with TWRP by allowing the modification of system and even after reflashing stock it'll bootloop on relocking recovery.
So I found something useful then.

Hey, i think i found a solution for you. I don't know if i can post here xda thread links, so search "EDL Mode xda" on Google and the first link it is. Hope i helped

Really need help

So i have searched all over the internet and havent found ant help. My phone is in a bootloop and i can't get out of it, i have tried with Nexus root tool kit to factory reset but just bootloop have tried it twice. Also tried to install factory with TWRP but still bootloop. I have an unlocked bootloader, I also tried to lock it and start with a new factory image but didnät work either . So please help me if you can i'm willing to try anything can't afford a new phone right now.
BIG UPDATE
So now after some work with trying to fx this i have found the problem with it. It's that my phone dosen't install the files that i install with either adb or TWRP. I found this by putting pure nexus rom on the phone and installing it with TWRP and then remove it from the storage. That was when the storage on the phone said it was still zero even when i had choose to install a new rom on the phone. but it still bootloop with the google logo and the four dots that pulse and then reboots.
Another Update
So i tried with installing the pixel rom from the xda forum and it all went well and all with the insallation no errors what so ever but my boot animation changed to pixels but still continue to bootloop still don't know whats happening.

I'm not sure what state your device is in right now. Is the bootloader locked or unlocked? When you tried to lock it, don't try that again, did it lock or did it remain unlocked when you re-booted into the bootloader? Were you able to successfully flash the factory image?
I'd suggest you carefully read thru this and pay particular attention to how to flash a factory image, http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Sent from my Nexus 9 using XDA-Developers mobile app

Not really
jd1639 said:
I'm not sure what state your device is in right now. Is the bootloader locked or unlocked? When you tried to lock it, don't try that again, did it lock or did it remain unlocked when you re-booted into the bootloader? Were you able to successfully flash the factory image?
I'd suggest you carefully read thru this and pay particular attention to how to flash a factory image, http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Sent from my Nexus 9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Whell when i locked the bootloader it got locked but then when it bootlooped for one to two hours i opened it again and went to ask the pros at xda. I also read through the guide you linked me and did as said in the tutorial but my phone is still bootlooping right now.

Did you successfully manually flash each of the image files in the latest factory image? Bootloader, radio, system, boot, etc.

jd1639 said:
Did you successfully manually flash each of the image files in the latest factory image? Bootloader, radio, system, boot, etc.
Click to expand...
Click to collapse
Yes i succesfully flashed everyone that was said in the guide.

Pixel 2 xl brick after lock bootloader

HELP. (SOLVED)
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..

zetareticuli said:
HELP.
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..
Click to expand...
Click to collapse
You probably should look into this.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

With a locked bootloader, you cannot flash system images. You need to be unlocked to do so.
But it seems that you did something wrong when re-locking the bootloader: It is normal that a factory reset is performed, but the OS should stay on the phone.
So I would first unlock the bootloader again - both fastboot flashing unlock and fastboot flashing unlock_critical, like described here: https://developers.google.com/android/images
Also note that you always need to update the Android SDK Platform-Tools, like descibed in the link. As always: Those who can read do have an advantage
Then you should be able to flash the latest factory image again and are ready to go.

Badger50 said:
You probably should look into this.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
I couldn't dig myself out of a soft brick the other day too. That saved me as well. Worked like a charm the first time.

zetareticuli said:
HELP.
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..
Click to expand...
Click to collapse
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.

exist2resist said:
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.
Click to expand...
Click to collapse
SOLVED WITH [TOOL] Deuces Bootloop-Recovery & Flashing Script v4.4/v4.5
Thanks alot guys

mikelikesbikes said:
I couldn't dig myself out of a soft brick the other day too. That saved me as well. Worked like a charm the first time.
Click to expand...
Click to collapse
Thanks my friend works like a charm..

exist2resist said:
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.
Click to expand...
Click to collapse
Solved with [TOOL] Deuces Bootloop-Recovery & Flashing Script v4.4/v4.5..

Simple question about relocking my bootloader

I unlocked the bootloader on my phone because I was planning on flashing a different ROM on the phone and I never got around to it. Now I need to send it back because of a screen issue and I want to relock it so I don't get any grief from Google about it. So can I just run the lock command or do I need to flash a factory image first and then do the lock?

loki993 said:
I unlocked the bootloader on my phone because I was planning on flashing a different ROM on the phone and I never got around to it. Now I need to send it back because of a screen issue and I want to relock it so I don't get any grief from Google about it. So can I just run the lock command or do I need to flash a factory image first and then do the lock?
Click to expand...
Click to collapse
Be darn sure you are full stock!! No magisk or modules or custom kernels. I just did this for a trade in for my P4XL as well. After I uninstalled magisk and custom kernel, I factory reset, let it boot up, then went back and clean flashed the factory image. In essence, wiping the phone twice. Also, be sure and leave OEM unlocking and USB debugging turned on. Then just go to fastboot and run...fastboot flashing lock. And there ya go :good:

Badger50 said:
Be darn sure you are full stock!! No magisk or modules or custom kernels. I just did this for a trade in for my P4XL as well. After I uninstalled magisk and custom kernel, I factory reset, let it boot up, then went back and clean flashed the factory image. In essence, wiping the phone twice. Also, be sure and leave OEM unlocking and USB debugging turned on. Then just go to fastboot and run...fastboot flashing lock. And there ya go :good:
Click to expand...
Click to collapse
I was in the process of rooting it and somehow soft bricked the phone..so I has to reflash the stock image once. After that I didn't mess with uit again but I left it unlocked because I figured id try again at some point. So yeah Ill just reflash a factory image just to be extra sure and then relock it.

loki993 said:
I was in the process of rooting it and somehow soft bricked the phone..so I has to reflash the stock image once. After that I didn't mess with uit again but I left it unlocked because I figured id try again at some point. So yeah Ill just reflash a factory image just to be extra sure and then relock it.
Click to expand...
Click to collapse
This thread might help you :
https://forum.xda-developers.com/pixel-2-xl/help/lock-bootloader-steps-p2xl-t3968185

Yep I did that last night..worked fine, its all ready to go back now.