Database Users

Bootloop on brand new 4.2.2

I've encountered an unpleasantly unique problem (as far as the internet is concerned) with my Nexus 7.
It started when I wanted to upgrade my Nexus from 4.2.1 to 4.2.2. For whatever reason, the upgrade wouldn't install, gave me an error a quarter of the way through and booted me back into 4.2.1 with no repercussions.
Using WugFresh's Nexus Root Toolkit, I managed to get 4.2.2 onto there by flashing it over everything. It seemed fine, but went into a bootloop on the Google splash screen before it could start up and go through the first time setup.
I have tried everything. I tried flashing again with NRT, and got the image attatched, a hither-to unseen error that could not be fixed with a pc reboot or reinstall of NRT. I tried using the old Nexus Toolkit to boot into CWM recovery, but since USB debugging isn't (and can't be) turned on, that could do nothing. I've tried using the SDK command line to unlock it and flash it, but the device can't be found because it hasn't been booted up for that first time startup configuration. I've tried uninstalling all the drivers and trying all of that again, with nothing.
What's left is a nexus 7 with a brand new 4.2.2 that can't boot, no USB debugging, that is locked and unrooted. I can get into the bootloader, but there's no recovery installed.
I'm sorry if this has happened before. I'm sorry if this isn't new. But good christ almighty I just want my tablet to work.
tl:dr help me gods of the Android

If you can boot into the bootloader, can you use the SDK's fastboot tool to flash the stock recovery?

jfmcbrayer said:
If you can boot into the bootloader, can you use the SDK's fastboot tool to flash the stock recovery?
Click to expand...
Click to collapse
Nope. It just says "<waiting for device>" and stalls indefinitely when trying to flash anything onto the device.

fudgyhoops said:
Nope. It just says "<waiting for device>" and stalls indefinitely when trying to flash anything onto the device.
Click to expand...
Click to collapse
I suppose "fastboot oem unlock" doesn't work, either?

fudgyhoops said:
Nope. It just says "<waiting for device>" and stalls indefinitely when trying to flash anything onto the device.
Click to expand...
Click to collapse
As long as you can get into fastboot, you should be able to use fastboot commands, sounds like you have a driver problem. Did you uninstall all the drivers and install the pdanet drivers? If the pdanet drivers don't work try naked drivers. It doesn't matter if debugging is enabled or not or if your device is unlocked and unrooted, you should still be able to do everything via fastboot commands. I recommend wiping everything via fastboot commands and than flashing the stock image. I recommend avoiding rootkits they are more trouble than they're worth, fast boot is a lot easier, faster and safer. You might want to try a different computer if nothing else works. You might have a defective bootloader though. Make sure you check the device manager on your computer to see if there are any errors with the drivers, it should show a yellow triangle if the driver is not working, if that's the case click on update driver and navigate to the SDK drivers.
http://www.androidegis.com/how-to/how-to-unbrick-the-nexus-7/
---------- Post added at 09:01 AM ---------- Previous post was at 08:54 AM ----------
Once you get the stock image flashed, unlocked and rooted, you can use goo manager to install the twrp recovery.

jfmcbrayer said:
I suppose "fastboot oem unlock" doesn't work, either?
Click to expand...
Click to collapse
I was surprised when it did. I had done a full driver reinstall to prestige777's advice, and fastboot started working again. Ran into an error when trying to flash 4.2.2 and bootloader version 4.18 with mismatched signatures, but tried it on another computer (thank you prestige777 again) and it's booting!
Thank you both so much!

fudgyhoops said:
I was surprised when it did. I had done a full driver reinstall to prestige777's advice, and fastboot started working again. Ran into an error when trying to flash 4.2.2 and bootloader version 4.18 with mismatched signatures, but tried it on another computer (thank you prestige777 again) and it's booting!
Thank you both so much!
Click to expand...
Click to collapse
No problem, I'm glad it worked for you.

Nexus 6p struck in boot loop

Hi,
My Nexus 6p was running the latest OTP update of Android Nougat successfully, Suddenly while using google maps it, restarted and went into a boot loop. All i can see is the unlocked bootloader warning (i had unlocked the bootloader earlier) and then the google logo.
I am able to go into bootloader mode and my system identifies my device as a fastoboot device .
I was able to access my stock recovery but while trying to fix my phone, i tried installing twrp recovery and now whenever I choose the option of recovery mode using my volume keys. it again shows the google logo and nothing happens after that.
I have tried many things, but I am not able to resolve my boot loop. Somebody please help me. Please guide me what should be my approach to this problem
Regards
Ishmeet

ishmeet said:
Hi,
My Nexus 6p was running the latest OTP update of Android Nougat successfully, Suddenly while using google maps it, restarted and went into a boot loop. All i can see is the unlocked bootloader warning (i had unlocked the bootloader earlier) and then the google logo.
I am able to go into bootloader mode and my system identifies my device as a fastoboot device .
I was able to access my stock recovery but while trying to fix my phone, i tried installing twrp recovery and now whenever I choose the option of recovery mode using my volume keys. it again shows the google logo and nothing happens after that.
I have tried many things, but I am not able to resolve my boot loop. Somebody please help me. Please guide me what should be my approach to this problem
Regards
Ishmeet
Click to expand...
Click to collapse
FOLLOW THESE INSTRUCTIONS ONLY IF ANYTHING BETTER DOESNT COME UP BECAUSE I DON'T WANT TO FEEL GUILTY IF YOU "FUBAR" YOUR PHONE. I am not an expert in this stuff.. I can only follow instructions and the two videos helped me get out of crappy situation in the past couple weeks.
Follow the two videos below on how to re-install your drivers properly and flash and root Nougat 7.0
First go delete your driver from your PC via Device Manager. Anything that you can associate with N6P or Google.
Then watch this video on how to install new drivers.
This video on how to install Nougat

If you can access fastboot, I would just follow Heisenbergs guide (look In the stickies) and reflash the N stock images manually via fastboot. Also, make sure that you flash the recommended TWRP version that he has linked in his guide otherwise you will have problems with recovery. His guide has saved me multiple times when I messed up my phone.

Pain-N-Panic said:
If you can access fastboot, I would just follow Heisenbergs guide (look In the stickies) and reflash the N stock images manually via fastboot. Also, make sure that you flash the recommended TWRP version that he has linked in his guide otherwise you will have problems with recovery. His guide has saved me multiple times when I messed up my phone.
Click to expand...
Click to collapse
I am in something similar situation but the thing is computer does not detect any device and phone just shows google. I ended up in this situation after I was trying to flash zip drivers for google assistant. But now I am not able to access recovery mode even.

ranjha94 said:
I am in something similar situation but the thing is computer does not detect any device and phone just shows google. I ended up in this situation after I was trying to flash zip drivers for google assistant. But now I am not able to access recovery mode even.
Click to expand...
Click to collapse
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic

bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
I think I figured out mine problem. I am not sure what you mean by locked bootloader but in my case I was able to reboot to bootloader by pressing all three buttons (Volume up, Volume down and power button) at the same time.
Once you are there and if your bootloader is already unlocked you can flash your own android. Probably this process is called unbrick your phone. I am surprissed and sad as I am not allowed to post link which can help you. Ask admin.
Any related problem while following process. I can try as I am not very expert.
RIP my English.
Thanks
---------- Post added at 05:20 AM ---------- Previous post was at 05:16 AM ----------
bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
https://devs-lab.com/how-to-unbrick-hard-soft-bricked-google-huawei-nexus-6p.html

bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
And that's why it's a good idea if you do ANY tinkering to your phone that you have an unlocked bootloader. I have screwed my phone up a hundred times over but nothing that a fastboot flash of the stock Google images couldn't overcome.
I'm not sure what situation you're in but I would try to get that bootloader unlocked asap. Just know that when you unlock it, every partition on the phone will be completely wiped to include internal storage (sd card).

I wasn't tinkering that's the thing. I was on the Android beta but I have installed those OTA. I would love to be able to unlock the bootloader but none of the commands will work to unlock it because usb debugging was not enabled or the developer options and I can't boot it to change that.

Bootlooping Nexus

My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.

avansledright said:
My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
Click to expand...
Click to collapse
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?

Fe Mike said:
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Click to expand...
Click to collapse
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.

avansledright said:
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
Click to expand...
Click to collapse
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.

Fe Mike said:
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Click to expand...
Click to collapse
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.

avansledright said:
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
Click to expand...
Click to collapse
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images

Fe Mike said:
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.

,
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Do you get the error on all that you try to flash? Maybe just try the recovery img only to see if you can at least get that. If that works you should be able to sideload ota through recovery. With having a locked bootloader you might be at a loss. But on the flip side, having everything locked and not rooted you should be ok for warranty replacement.

avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode

avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Ahh, missed that in your first post. I'm not sure how you can get recovery going if it's bootlooping when you access it.
Sent from my Nexus 5X using Tapatalk

avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6

Fe Mike said:
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Click to expand...
Click to collapse
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:

avansledright said:
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
Click to expand...
Click to collapse
Good to hear about replacement! There are a few people in these forums that have a brick and can't get out of it. I thought you couldn't Hard brick these phones unless that was your goal. And most of these users who have bricks don't even know what causes it. Just a random reboot then loops. Kinda scary.

Bootloop x727

I have successfully unlocked bootloader on 20s and then tried to flash a third-party rom from Cydras, which didn't work out. So in TWRP i chose to restore EUI from backup. After that the phone powers up and everthing works fine until the color-changing EUI logo appears... and that's where it gets stuck, not going beyond this point ever.
I tried to push an image to /sdcard/ but it said the directory is not there? That was when ADB/Fastboot was still able to see the device, it isn't any longer.
This means I can't get to TWRP and/or push a ROM to the device.
I can enter Fastboot Mode by pressing the Vol and Power buttons but this is no help as ADB/Fastboot doesn't see the device in this mode either.
Any ideas would be appreciated. Thanks in advance and good karma to everyone

Anyone?
Would appreciate input! Thanks!

Without ADB or fastboot, I can't think of anything else you can do. If the phone is going into the fastboot mode, you need to figure out why your computer is not connecting to it.

Thank you for your note!
It's going into Fastboot mode by pressing Vol+/Power. It also goes into stock recovery but that one does nothing - it does wipe it seems but the only other option is to install update - which clearly isn't on my phone.
What could be the reasons my computer stopped seeing the device?

Strange: If I put the phone in Fastboot mode, my PC identifies it and starts showing Kedacom USB Device - Android Bootloader Interface in Devices.
Fastboot does actually see it and can perform a few commands. ADB, on the other hand, does NOT see it. What options do I have? I could push TWRP image to the phone. Is there anything else I could do now?
Please help! And thanks!

If you have access to fastboot, either flash or boot TWRP image and see from TWRP if the old backup is still accessible.

Thank you. Did just that but there's nothing there to recover, unfortunately. And I thought about installing system via Fastboot but can't find a system image (.img) anywhere
Please help!
Thanks!

Boot into TWRP and while in TWRP, see if the ADB works.
If ADB works, then push one of the TWRP backup zip file to the data memory and the recover from TWRP.

see guide on leeco . re fourms
crukkh said:
Thank you. Did just that but there's nothing there to recover, unfortunately. And I thought about installing system via Fastboot but can't find a system image (.img) anywhere
Please help!
Thanks!
Click to expand...
Click to collapse
you need to use flashone 2.0 for leeco pro3 google it.

crukkh said:
Thank you. Did just that but there's nothing there to recover, unfortunately. And I thought about installing system via Fastboot but can't find a system image (.img) anywhere
Please help!
Thanks!
Click to expand...
Click to collapse
If you can enter Fastboot mode this will work. You can flash Fastboot rom (stock Eui 5.8.17S China), then you can start all over from there. It will erase everything on the phone so do backup everything. You will need to redo-unlock bootloader and re-install TWRP recovery.
Link for the Fastboot rom with how to flash it here:
https://forum.xda-developers.com/showpost.php?p=73913013&postcount=240
After flash if it show storage free space not correct install TWRP and go to Wipe > Format data, it should fix it.
---------- Post added at 01:26 PM ---------- Previous post was at 01:22 PM ----------
crukkh said:
I have successfully unlocked bootloader on 20s and then tried to flash a third-party rom from Cydras, which didn't work out. So in TWRP i chose to restore EUI from backup. After that the phone powers up and everthing works fine until the color-changing EUI logo appears... and that's where it gets stuck, not going beyond this point ever.
I tried to push an image to /sdcard/ but it said the directory is not there? That was when ADB/Fastboot was still able to see the device, it isn't any longer.
This means I can't get to TWRP and/or push a ROM to the device.
I can enter Fastboot Mode by pressing the Vol and Power buttons but this is no help as ADB/Fastboot doesn't see the device in this mode either.
Any ideas would be appreciated. Thanks in advance and good karma to everyone
Click to expand...
Click to collapse
If you can enter Fastboot mode, you can flash Fastboot rom in the link:
Link for the Fastboot rom with how to flash it here:
https://forum.xda-developers.com/sho...&postcount=240

[GUIDE] Restore to complete stock and relock bootloader. Easiest step by step guide.

Hello friends,
After trying different roms and kernels there always comes a time when we wish to go back to complete stock for a smooth reliable experience. Here's a detailed step by step guide for this process.
This guide assumes that you are on a unlocked bootloader with TWRP recovery installed and want to revert to complete stock
This will erase all data on your phone. Hence first BACKUP!
Note : I am not responsible for any damage do this at your own risk.
Downloads
1) MINIMAL ADB & FASTBOOT : https://goo.gl/UbFXdA
2) STOCK OOS FILE : https://goo.gl/JAfS2F
3) Stock Recovery : https://goo.gl/2kmbB7
Pre Requisites : A windows computer with a decent internet connection
Oneplus 5T with atleast 50% battery charged
USB Cable
Brain:cyclops:
Steps :
1) Download and install minimal ADB & Fastboot.
2) Download OOS Stock Rom And Stock Recovery.
3) Connect your phone to the PC using the USB cable in file transfer mode.
4) Copy the rom zip and stock recovery image to your phone.
5) Go to settings>about>tap build number 7 times.
6) Go to settings>developer options>enable advanced reboot.
7) Press power button for 2 seconds>select reboot>select recovery>tap to reboot.
8) Once the phone boots into TWRP>wipe everything except internal storage.
9) Tap install and select the stock rom zip and then swipe to install.
10) Tap install>select install image>select stock recovery img>tap recovery>swipe to install
11) Tap reboot>select bootloader and reboot to bootloader.
12) Once in bootloader connect the phone to your pc and launch minimal adb & fastboot
13) type fastboot devices and ensure device is connected and serial number shows up
14) type fastboot oem lock in minimal adb and fastboot and hit enter.
15) use the volume keys on your phone to highlight yes and press power button to confirm
16) wait for 2 to 5 minutes and phone will bootup to a complete stock rom with stock recovery and a locked bootloader.
For everyones convinience I have made a step by step video guide please watch and subscribe if you liked it.
Hit thanks if i helped.​

Before this came out I tried the reversal process incorrectly by typing fastboot oem lock as the 1st step (I know it says above you need a brain). Now it seems there is no OS to boot to. I can boot to TWRP and fastboot but my computer doesn't see the storage. Is there a way to push the the rom zip and stock recovery image to your phone via adb? If so what are the commands?

vibrantliker said:
Before this came out I tried the reversal process incorrectly by typing fastboot oem lock as the 1st step (I know it says above you need a brain). Now it seems there is no OS to boot to. I can boot to TWRP and fastboot but my computer doesn't see the storage. Is there a way to push the the rom zip and stock recovery image to your phone via adb? If so what are the commands?
Click to expand...
Click to collapse
I believe you should be able to go into twrp, go to sideload mode. Then the command would be abd sideload filename.zip This should then push the rom to your phone and install it for you. It has been a while since I needed to do it, as now a days I mostly keep my phones stock and locked.

Stephen said:
I believe you should be able to go into twrp, go to sideload mode. Then the command would be abd sideload filename.zip This should then push the rom to your phone and install it for you. It has been a while since I needed to do it, as now a days I mostly keep my phones stock and locked.
Click to expand...
Click to collapse
Thanks but that doesn't seem to work.

Link for Stock Recovery is down. Please help

Nice guide but isn't step 10 unnecessary, since the stock ROM will overwrite TWRP with the stock recovery anyway?

Thanks for the info. My phone's been acting very flaky since I rooted it, so I'm curious to see if returning to stock will make it a little less annoying.

vibrantliker said:
Before this came out I tried the reversal process incorrectly by typing fastboot oem lock as the 1st step (I know it says above you need a brain). Now it seems there is no OS to boot to. I can boot to TWRP and fastboot but my computer doesn't see the storage. Is there a way to push the the rom zip and stock recovery image to your phone via adb? If so what are the commands?
Click to expand...
Click to collapse
unlock the bootloader
flash twrpagain
flash stock rom from twrp
flash stockrecovery image from twrp
reboot to bootloader
relock bootloader
reboot
you are good to go

inxx99 said:
Link for Stock Recovery is down. Please help
Click to expand...
Click to collapse
updated

Sisyphus306 said:
Thanks for the info. My phone's been acting very flaky since I rooted it, so I'm curious to see if returning to stock will make it a little less annoying.
Click to expand...
Click to collapse
definitely worth a shot

rickysidhu_ said:
Nice guide but isn't step 10 unnecessary, since the stock ROM will overwrite TWRP with the stock recovery anyway?
Click to expand...
Click to collapse
sometimes it doesnt and hence before we relock the bootloader its necessary to ensure we have the stock recovery hence the step.

hypergamer1231 said:
sometimes it doesnt and hence before we relock the bootloader its necessary to ensure we have the stock recovery hence the step.
Click to expand...
Click to collapse
Fair enough

hypergamer1231 said:
unlock the bootloader
flash twrpagain
flash stock rom from twrp
flash stockrecovery image from twrp
reboot to bootloader
relock bootloader
reboot
you are good to go
Click to expand...
Click to collapse
My problem is, although I still have TWRP and fast boot, I don't have an os at the moment and need to get one via adb somehow.
I've tried adb push but can't find in TWRP. My computer doesn't see my phones storage either.

vibrantliker said:
My problem is, although I still have TWRP and fast boot, I don't have an os at the moment and need to get one via adb somehow.
I've tried adb push but can't find in TWRP. My computer doesn't see my phones storage either.
Click to expand...
Click to collapse
Can you boot in fastboot

Yes
---------- Post added at 05:54 AM ---------- Previous post was at 05:53 AM ----------
hypergamer1231 said:
Can you boot in fastboot
Click to expand...
Click to collapse
Yes and TWRP

vibrantliker said:
Yes
---------- Post added at 05:54 AM ---------- Previous post was at 05:53 AM ----------
Yes and TWRP
Click to expand...
Click to collapse
Check pm

Thank you for this.
Sent from my LG-H815 using Tapatalk

Thank you so much for this. Is this oos file the most current os for the 5t?

Can someone turn this thread into a sticky?

goran_oh said:
Thank you for this.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Glad it helped
martinez5241 said:
Thank you so much for this. Is this oos file the most current os for the 5t?
Click to expand...
Click to collapse
Yes this is the latest OOS 4.7.2
Co.Tibi said:
Can someone turn this thread into a sticky?
Click to expand...
Click to collapse
Am sure the mods will soon. Thank you.