Database Users

Nexus 7 wont start up or go into recovery mode..

Was having issues with my Nexus 7(2013) this morning, rebooted the device and now it gets stuck at the "Google" loading screen.
I can get into the Fastboot loader. I was able to unlock the bootloader.. I have LOCK STATE - unlocked and the unlocked lock showing up on the "Google" boot screen.
I am UNABLE to get into Recovery mode.. either by selecting "Recovery mode" in Fastboot or holding the power and vol up buttons. It just sits on the "Google" boot screen.
I have downloaded and installed the SkipSoft Android Toolkit(mskip).. very nice toolkit BTW. But no matter what I do I'm unable to start the tablet up normally or get into a Recovery mode of any kind.
I have tried to flash TWRP. I have tried to flash the stock ROM. Nothing, still sits at the Google boot screen. Since flashing the stock ROM its been 30 min and still just says "Google".
I'm open to any ideas or anything that you can think of.

Still have TWRP and fastboot access? If so, use the command line fastboot the img using
"fastboot boot <filename>.img"
Reply back; do you get to recovery?

Snuzzo said:
Still have TWRP and fastboot access? If so, use the command line fastboot the img using
"fastboot boot <filename>.img"
Reply back; do you get to recovery?
Click to expand...
Click to collapse
No.. I do not get into recovery of any kind. Stock or TWRP after loading it.. just sits at the Google screen.

Quick question; what were your partition setups like? F2fs? Ext4?

Snuzzo said:
Quick question; what were your partition setups like? F2fs? Ext4?
Click to expand...
Click to collapse
No idea.. it should be whatever it is stock. Before today I never rooted, flashed or did anything to this device.

FDokinawa said:
No idea.. it should be whatever it is stock. Before today I never rooted, flashed or did anything to this device.
Click to expand...
Click to collapse
Answers all of my questions. I know myself I won't be able to help. All I can say is to try relocking and then unlocking again.

Snuzzo said:
Answers all of my questions. I know myself I won't be able to help. All I can say is to try relocking and then unlocking again.
Click to expand...
Click to collapse
Thanks for the help.. will give it a shot.

FDokinawa said:
Thanks for the help.. will give it a shot.
Click to expand...
Click to collapse
What that should do is wipe internal, could have some corruption there. Try doing the command line fastboot of the recovery.img again. Those are the only few things I can think of short from exercising your warranty.

Snuzzo said:
What that should do is wipe internal, could have some corruption there. Try doing the command line fastboot of the recovery.img again. Those are the only few things I can think of short from exercising your warranty.
Click to expand...
Click to collapse
Dont think I can use the warranty.. bought it used(1 hour old) from a friend for $100.. he got it and then decided he didnt like the aspect ratio. His loss, my gain. Until now.. lol
I'll keep hacking at it.. thanks again.

Anytime! You're welcome!

So the original issue I was having was that the screen was not responding to touches. Was unable to slide the unlock button on the screen.
I was able to "Boot to Custom/Stock Recovery without Permanently Flashing it" via SkipSoft Toolkit.. and had TWRP load up. But like before it was not responding to touches.
Starting to think this thing is totally borked.. =/

I'm able to get into TWRP now.. but sits on boot animation screen now. one step forward. Going to try and reload the stock ROM again and see if that helps.

That seemed to work.. at the Welcome screen.
So if anyone else runs into something like this..
Issues:
Flakey touch screen
Stuck on Google bootup screen
Eventually stuck boot loop animation
Get SkipSoft Android Toolkit, donate a couple bucks and keep flashing anything and everything you can. Sorry I can't give you a specific order that works. I would say try the 'ALLINONE'(#8) option first and then download and flash the stock ROM. I did several things in the toolkit a few times over and over. Hopefully I'm good now, if not I will update.

Have you tried reflashing recovery via fastboot?

Exact thing happend to my n4.
Sent from my N⁴ using Android Lollipop by @Sykopompus running Unleased kernel by @DeFcOni

[Q] Stock Phone after random crash in bootloop

Hi Guys,
i hope you can help me. My lovely Nexus 4 is stucked in a bootloop (green, red, yellow and blue dots are flying in circles).
I was using my phone and then some google tasks crashed and then the phone completly restarted.
It is completly on the stock rom with the newst updates.
I already tried to wipe all cashes and did a factory reset. Unfortunately it is still stucked at the loadings Screen.
Does anyone has an idea how to bring it back to life?
Regards Mrdeli

Try flashing the factor image with fastboot.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Try flashing the factor image with fastboot.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hey, thank you for your help.
I installed the adb, the drivers and downloaded the factory image.
Then i booted into the bootloader to get fastboot mode. After that i used the "fastboot oem unlock" command to unlock the bootloader and "LOCK STATE - locked" changed to "LOCK STATE - unlocked".
But when i am trying to flash the factory image with "flash-all" my nexus 4 restarts and tries to install the image, but the LOCK STATE changes back to "locked" and so the flash fails.
:/
Even if just restart the phone after unlocking the Bootloader, it is locked again when i enter the bootloader again.
So what can i do? My warranty is until the end of May.
Regards Mrdeli

mrdeli said:
Hey, thank you for your help.
I installed the adb, the drivers and downloaded the factory image.
Then i booted into the bootloader to get fastboot mode. After that i used the "fastboot oem unlock" command to unlock the bootloader and "LOCK STATE - locked" changed to "LOCK STATE - unlocked".
But when i am trying to flash the factory image with "flash-all" my nexus 4 restarts and tries to install the image, but the LOCK STATE changes back to "locked" and so the flash fails.
:/
Even if just restart the phone after unlocking the Bootloader, it is locked again when i enter the bootloader again.
So what can i do? My warranty is until the end of May.
Regards Mrdeli
Click to expand...
Click to collapse
That's not good. If you unlock the phone and then reboot it and it remains locked it usually means the emmc has gone bad. The good news is you're still under warranty. I think you'll have to warranty it.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
That's not good. If you unlock the phone and then reboot it and it remains locked it usually means the emmc has gone bad. The good news is you're still under warranty. I think you'll have to warranty it.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for your fast answer. I had been concerned that. I had some weird usses the last weeks with my phone:
it randomly restarts
when i had a call, noone was able to hear the other, so i had to restart
sometimes it did some weird sounds, like a cracking
I will send it to LG and let them try to repair it i guess.
Thank you for your support.
Regards Mrdeli

Bootloop and cannot boot into recovery

Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.

Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode

met911 said:
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
Click to expand...
Click to collapse
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.

met911 said:
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
Click to expand...
Click to collapse
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.

met911 said:
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
Click to expand...
Click to collapse
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. i left it as you mentioned and it went into bootloop. Even the one time i managed to get it in recovery mode and made factory reset and wipe cache partition. I did not get it to be detected by ADB as debugging was not enabled in the setting menu.
This recovery mode is really useless if you cannot start the phone. Its supposed to be RECOVERY mode but its completely useless.
Previously, you could just unlock the bootloader and flash new image. Now it must be enabled in the setting in a phone that does not even work.

The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
You are asking the same questions again. YES, download mode is disabled.
after the first command, it tells me "locked device to enable ramdump"
I tried adb sideload but did not work because its not enabled in the phone settings as i already mentioned before.

I apologize for asking the same questions. I got confused on which thread I was posting in. I have been trying to help someone else with the same issue.
Sent from my Nexus 6 using XDA-Developers mobile app

Adb sideload won't work in bootloader mode, only in recovery. The only thing that will work in bootloader mode is fastboot but seeing as the bootloader is locked (with no way to unlock it) you can't use fastboot. If you can't get into recovery there's nothing you can do except send the phone for repair.

But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.

met911 said:
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
Click to expand...
Click to collapse
I'm not sure what you mean by new security, this has been standard fare for some time now. I'm sure if your phone was stolen you'd be thanking this security feature because it'd mean that the thief couldn't possibly access your data.
People in the know usually go into the settings menu and tick the "allow oem unlocking" box even if they don't plan on unlocking the bootloader at that time, there's a slight security risk but it's insurance against situations like this.
And what you're saying isn't entirely true; even if the OS fails the phone can usually still boot into recovery which would mean being able to revive it via adb sideload. What you're experiencing is relatively unusual, not being able to boot into the recovery as well as the OS means you're basically screwed.
If there's anything to take away from this it's that electronic devices fail sometimes. If you can handle the security risk it's worth ticking that box in the settings menu, or even completely unlocking the bootloader, to give yourself some insurance against these rare situations.

Same problem
met911 said:
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Click to expand...
Click to collapse
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me

ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.

ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
uodii said:
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
Click to expand...
Click to collapse
You both might want to take a read of http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921 - it has many people who have experienced the issue you both have. tl;dr - you'll probably need to contact goog/huwaei for a replacement.

Had the exactly same issue the day before yesterday, tried every possible way to flash different versions of images, none worked. My warranty expired 2 weeks ago, so both google and huawei told me that I am on my own for this.

Wow.. I feel for you all. I've had the exact same thing happen some weeks ago, phone freezing, then reboot, then couple of days later bootloop, then able to flash and reinstall, then after one final bootloop with the phone unable to 'take' the flashing through recovery, etc, etc. I've been playing with xda since the days of Froyo and that was the first time I had to send a phone back under warranty.
I was just about to try to manually rebuild the whole partition system at the block level but I'm glad I could send it for repairs. You might have a chance if you go as low as that. Good luck
* edit * I got the TWRP to stick by flashing it in Fastboot a couple of times in a row at that time, then I was adapting a Linux guide on reformatting and repairing drives partitions and all that through an adb shell.I did not get it to work yet before sending it, though.

Nexus 6P Bootloop, fastboot devices works, but no other fastboot commands work

Hello,
My wife's 6P is stuck in a bootloop. Here's what I've tried so far:
adb devices -> no result
fastboot devices -> device info is displayed
Any other fastboot command -> "FAILED (command write failed(No error))"
I unlocked her bootloader when we got the phone, but I can't flash anything. I just keep getting that error.
Any ideas? Thanks in advance for your help.

Did you update ADB and fastboot ?
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/

coremania said:
Did you update ADB and fastboot ?
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Click to expand...
Click to collapse
Yep, I'm able to see my 6P and N7 2012 via ADB, just my wife's 6P that I can't seem to get to work.

Not sure what happened, but I am now able to execute fastboot commands without getting that error. So now I'm waiting for the battery to die down enough to be able to boot recovery per this post. Hopefully this will fix it.

FlyOnTheWall43 said:
Yep, I'm able to see my 6P and N7 2012 via ADB, just my wife's 6P that I can't seem to get to work.
Click to expand...
Click to collapse
You're not able to boot to stock recovery ?
---------- Post added at 14:40 ---------- Previous post was at 14:21 ----------
What happens if you put a working twrp.img into your fastboot folder and try to boot it without flashing.
fastboot boot twrp.img
or
fastboot boot recovery twrp.img

coremania said:
You're not able to boot to stock recovery ?
---------- Post added at 14:40 ---------- Previous post was at 14:21 ----------
What happens if you put a working twrp.img into your fastboot folder and try to boot it without flashing.
fastboot boot twrp.img
or
fastboot boot recovery twrp.img
Click to expand...
Click to collapse
correct, I cannot boot to stock recovery, flash a custom recovery, or boot to a custom recovery directly (without flashing).

FlyOnTheWall43 said:
correct, I cannot boot to stock recovery, flash a custom recovery, or boot to a custom recovery directly (without flashing).
Click to expand...
Click to collapse
Just read the thread you linked, did you try the freezer, like the guy from the last post ???

coremania said:
Just read the thread you linked, did you try the freezer, like the guy from the last post ???
Click to expand...
Click to collapse
no, I just found that thread and I'm at work... going to try the freezer trick tonight.

coremania said:
Just read the thread you linked, did you try the freezer, like the guy from the last post ???
Click to expand...
Click to collapse
FlyOnTheWall43 said:
no, I just found that thread and I'm at work... going to try the freezer trick tonight.
Click to expand...
Click to collapse
Shoot, didn't help. Still continued to bootloop.

FlyOnTheWall43 said:
Shoot, didn't help. Still continued to bootloop.
Click to expand...
Click to collapse
Yes, actually the thing with the freezer i never heard that before, but if i remember right someone uses heat to make the phone bootable for a short time. May you carefully try this
with a hairdryer ??? And then try the 4 core modified boot.img

coremania said:
Yes, actually the thing with the freezer i never heard that before, but if i remember right someone uses heat to make the phone bootable for a short time. May you carefully try this
with a hairdryer ??? And then try the 4 core modified boot.img
Click to expand...
Click to collapse
ok, I can give this a try today after work and report back... thanks

The freezer trick did not work. But what helped me was to let the phones battery run out then plug it into the charger and let it boot loop for about 20 mins or so. The phone should boot at that point. I'm thinking the phone has to at least have a minimal charge to boot. Once the phone boots take it off the charger and make sure that "usb debugging" is on as well as allow "oem unlock" option. Once those settings are set go back to fast boot and attempt to flash the four core fix. It really works ????. If you leave the charger on it will go back to boot looping after it reaches 10 percent or so. Hope this helps.

pacoe said:
The freezer trick did not work. But what helped me was to let the phones battery run out then plug it into the charger and let it boot loop for about 20 mins or so. The phone should boot at that point. I'm thinking the phone has to at least have a minimal charge to boot. Once the phone boots take it off the charger and make sure that "usb debugging" is on as well as allow "oem unlock" option. Once those settings are set go back to fast boot and attempt to flash the four core fix. It really works . If you leave the charger on it will go back to boot looping after it reaches 10 percent or so. Hope this helps.
Click to expand...
Click to collapse
My bootloader is already unlocked, but I can't flash or boot the four core fix.

I know this question sounds redundant, but does your phone show your bootloader to be unlocked? Seems quite strange that it would not run the fastboot commands. What is the command that you are typing in to install the four core fix.

pacoe said:
I know this question sounds redundant, but does your phone show your bootloader to be unlocked? Seems quite strange that it would not run the fastboot commands. What is the command that you are typing in to install the four core fix.
Click to expand...
Click to collapse
no worries, I appreciate the attention/suggestions this thread is getting.... yeah, the bootloader is showing as unlocked. Also as of post #4, I am able to execute all fastboot commands now... I'm not 100% sure why it started working.

Always glad to help. Have you been able to fix the phone?

Sorry to disturb you, after I unlocked my device, I tried to flash both normal fix and 4 -core fix img > flash TWRP recovery, but I still cannot get into recovery mode, is my procedure wrong?
1) Flash 4 core fix boot img.
2) Flash TWRP recovery.
3) Boot to recovery.
4) Bootloop.
Thank you.

pacoe said:
Always glad to help. Have you been able to fix the phone?
Click to expand...
Click to collapse
No, but our Pixel 2's just showed up, so this isn't as urgent for me as it originally was. I'm hoping I can still get her old Nexus 6P and use it as our home phone with Google Voice. But, first I have to get this fix to work...
I'm able to flash the modified boot images without any errors, but I still can't get it to boot... I'm thinking it might be because my wife had to keep her phone 3-6 months behind the most current factory image (due to a poorly supported app she HAS to have for work) so I'm thinking the boot images on this thread won't work for her phone because he's on an older factory image. Am I correct in thinking this might be the problem?
I've requested that the OP of that thread either created modified boot images for the older versions of the factory images or explain how he made them so I can try to make them myself. Hopefully he's able to help me out.

Cant leave fastboot after unlocking bootloader....

So just got the axon 7 mini yesterday and was so excited I decided to try to root it with my laptop while my girl was driving us home from Las Vegas..... Ell I got as far as unlocking the boot loader.... now i get this odd screen after i try to exit fastboot. (pic-1) and no matter what option I pick the only thing that will come up is this screen. The only time its different is if I try to chose start from this screen then I get (pic-2) The best thing about this is that I can still go back to fastboot anytime. And it shows up in fastboot devices. Do I need to reflash stock thru fastboot? If so How and Where can i find it. Can I just flash nougat? I'm new to ADB/Fastboot.... Thank you for your time and consideration ahead of time for any help.

Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.

Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.

William Guo said:
Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.
Click to expand...
Click to collapse
I tried the thing were saying over and over

MrWhite0429 said:
Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.
Click to expand...
Click to collapse
so I was stuck all day yesterday trying anything and everything. BY THE WAY...Im very knowledgable but im pretty much a newb in rooting dept. especially fastboot. Well it seems I erased everything including the bootloader then battery died and no I have NOTHING on screen, no vibrations. Pretty much looks bricked. But when I try to put it in my computer to charge it it still shows up in my devices. BUT its not being found in adb/fastboot. I've tried every key combo/and length of holding them which doesnt do nothing

Can you place the device in edl? It will not display any lights or images when it is in edl.