Hello All,
I have a completely stock (Not rooted, and bootloader is locked) Nexus 9 (wifi) that will no longer boot after trying to update to the latest security patch (MOB30G).
I received the notification that there was an update available for my Nexus 9 this weekend. It was functioning just fine, so I chose to download an install the update.
I let it do its thing, and some time during the process something went wrong. I came back to see the little android picture with red "!". There were no words or messages with the error picture.
When I rebooted, There was a momentary message that stated that, "Device is corrupt and cannot be trusted..." and "...press the power button to pause boot".
It then goes back to the little android picture with the red exclamation mark and says "No Command".
I am at a total loss at what to do. It was completely stock, never rooted or anything else and I was applying a factory update?
Please help!
-Jason
@Jsunn Try side-loading the OTA update again from recovery.
Instructions can be found here.
If that doesn't work, try side-loading the Android N OTA instead.
I just had to deal with this after the May OTA. My device was locked and ADB was not enabled but I was able to sideload the dev preview of Android N.
I used the info at this link: Search "Reset your Nexus device to factory settings"
Specifically these steps:
Option 2: Reset device in Recovery mode
If you can't open the Settings app because of device issues, you can use Recovery mode to factory data reset ("format") your device.
Tip: If your device becomes unresponsive at any point, you can restart it by holding down the Power button for several seconds.
After following all the Before you start steps above:
If your device is on, turn it off.
Press & hold the Volume down button. While holding Volume down, press & hold the Power button until the phone turns on. You'll see the word "Start" with an arrow around it.
Press the Volume down button until you highlight "Recovery mode."
Press the Power button to start recovery mode. You'll see an image of an Android robot with a red exclamation mark (you may also see "No command").
Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.
Press the Volume down button until you highlight "Wipe data/factory reset." Then press the Power button.
Press the Volume down button until you highlight "Yes" (or "Yes - delete all user data"). Then press the Power button to select it.
After the reset is complete, press the Power button to select "Reboot system now."
When you're done, restore your data.
My biggest issue was not realizing the second menu was available. After getting "No Command" the power and vol up buttons are what get you to where you can use adb to sideload even if you never unlocked your device. This might work with a normal marshmallow OTA (Search for "Factory Images for Nexus Devices") but I used the N preview 2 which can be found by searching for "volantis-npc91k"
This had me fuming for a few days... No way I was sending a nexus device back and paying shipping for bricking after a stock update.
NOTE: Sorry I had to remove the direct links. My profile doesn't have enough posts yet. Really dumb, but I get it. Hope this helps.
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Had same issu with May update and applied the N preview OTA (that's the only thing you can do on a locked bootloader).
Once booted in N preview, I've enrolled the device in the beta program, then retired. Few seconds after, I've received the downgrade OTA, and no more issue.
Before doing anything else, I've unlocked the bootloader so at least it if occurs again with the MOB30G, I will have some more access !
Jsunn said:
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Click to expand...
Click to collapse
Nobody knows what causes this, maybe a corrupted download of the OTA.
It happens to people's devices nearly every month when an OTA is available.
Try sideloading the failed OTA (linked above) again first before taking the Android N route.
Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Use the latest OTA image from that link, instead of sideloading the patching OTA zips.
I can't seem to sideload the package. My computer doesn't detect that a fastboot device in connected.
I am trying a factory reset now? If that doesn't work, I guess I can try the N preview? Other suggestions?
Thanks,
Jason
@Jsunn Make sure you have the correct drivers on your computer, Nexus Root Toolkit has a driver installation guide.
Check that your in fastboot mode and your device should show up in device manager as
Android Device - Android Bootloader Interface
@corkiejp, Thank you for the tip. That was it and I now am back up and running. I am back on the May 1 Security update. I'd really like to avoid having to do this again in the future. Do you have any suggestions? i.e. should I always sideload the update? Customer ROM etc?
Thanks,
-J
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
corkiejp said:
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
Click to expand...
Click to collapse
It was the drivers, I didn't think to check that the first time. I am going to unlock the book loader, I was thinking the exact same thing! I'm just glad to be back up and running.
-J
Related
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
hiveNzin0 said:
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
Click to expand...
Click to collapse
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, thank you very much. I didn't know I had to press the 3 top buttons again after the dead droid screen, I thought it failed loading the Recovery Mode.
I have to setup my account etc again so I guess it is safe to say it worked.
Additionally, I tried this method after the recovery : http://forum.xda-developers.com/showthread.php?t=2015467
and it worked fine. My device has an unlocked bootloader and is rooted.
hey if someone could help me im stuck myself, after i had the dead android in recovery mode i tried to flash software with the toolkit in fastboot and now when i go to recovery its just a blank screen till i hold the bottom combo again and it takes me back to fastboot
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
maximepull said:
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
Click to expand...
Click to collapse
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
sharksfan7 said:
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
Click to expand...
Click to collapse
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Sorry. I don't know enough about these things to give more in depth troubleshooting advice. I just recently got my N10 & unlocked it and based on your original post, I thought that's where you needed help. But it sounds like you got past that and got it unlocked.
Have you tried downloading a factory image directly from Google and installing that? If it's locking up on a fresh install of any ROM, it very well may be a hardware issue. You may have to file a warranty claim if possible.
maximepull said:
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Click to expand...
Click to collapse
sharksfan7 said:
Have you tried downloading a factory image directly from Google and installing that?
Click to expand...
Click to collapse
^ that's your solution. If you dont know how to just pm me
Sent from my Galaxy Nexus using XDA Premium HD app
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
If I'm not mistaken, you would need to un-root your phone prior to installing any OTA Updates from AT&T. Also, you should only install the OTA Updates while using the stock recovery. So, you should re-flash the stock recovery and then attempt to complete the OTA Update. After that, you could re-install TeamWin, re-root and prosper.
Refer to this link on reverting back to stock... http://forum.xda-developers.com/showthread.php?t=2721435
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
Flash factory recovery, take the update, flash twrp back
or..
Titanium backup to freeze att update
an0ther said:
Flash factory recovery, take the update, flash twrp back
or..
Titanium backup to freeze att update
Click to expand...
Click to collapse
Just downloaded titanium back up. How do I freeze the update?
howyodoing said:
Just downloaded titanium back up. How do I freeze the update?
Click to expand...
Click to collapse
Try searching next time.. I see you are new here so i'll at least give you a link this time
http://forum.xda-developers.com/showthread.php?t=2752718
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
Click to expand...
Click to collapse
Good rule of thumb, do not install OTA updates on any modded Android device, without at a minimum doing thorough research on what will happen.
Depending on the device and the update in question, attempt to install an OTA on a modded device will remove root, possibly plug existing exploits (and render the phone unable to be rooted), or put you in a boot loop (as you have experienced).
In particular, OTAs require stock recovery in order to install. So if you have custom recovery installed, this is why the OTA install is failing (and why it keeps booting into TWRP).
Also, there is little (if anything) contained in the OTAs that doesn't get posted in a safe format (flashed from custom recovery) in the Development section soon after the OTAs start to roll out.
Solution for HTC OneM8 (continous restarting after update)
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
Hi, i have a HTC One M8, and when my first update popped, i was very enthuziast.
I accepted to download the update, installed it, and... the problem appeared. The phone made his restart after update... and continued to do so over and over again. (Vibrate/HTC screen on for 30 secs/screen off and so on)
I checked the HTC website for solutions, i entered live chat with a consultant, and he asked me to start the Hard reset procedure. To do that, while turned off, you have to press both volume keys, and press the power button. The phone will enter in the Bootloader menu where you have some options. But... tell me, how to do that if the phone restarts continously? you have about 1-2 seconds to do that, while the screen is off. It gave me a hardtime to do that... Finnally, i managed to enter the Bootloader menu.
There... you have 2 options: (using volume up/down to select, and power button to select) you can select to poweroff(shutdown) the phone - and the phone will shutdown,
or you can turn off the fastboot, and the phone will restart normally.
The thing is that when you restart your phone normaly, while fastboot on, the phone skips some steps, and go directly to to turn it on and show you the startscreen.
When you make a major update, like system upgrade, when the phone restarts, he needs to load all the boot setting. And here is the problem. If you have fastboot on, and make a major update, the phone will enter in this ****ty cicle of continous restarts.
Remember to deactivate this Fastboot before you update!
sergiu.dragan25 said:
I checked the HTC website for solutions, i entered live chat with a consultant, and he asked me to start the Hard reset procedure. To do that, while turned off, you have to press both volume keys, and press the power button.
Click to expand...
Click to collapse
This is not correct. To force a reboot, you hold power and vol up (not both vol buttons). Then, when its restarting (the moment the screen goes dark and before the white boot screen appears) you let go of both those buttons, and only hold vol down.
sergiu.dragan25 said:
But... tell me, how to do that if the phone restarts continously? you have about 1-2 seconds to do that, while the screen is off.
Click to expand...
Click to collapse
In the case of a bootloop (phone keeps restarting), all you need to do is hold vol down during one of the reboot cycles. The timing doesn't matter in this case. Just sit on the vol down button until the bootloader screen appears.
sergiu.dragan25 said:
There... you have 2 options: (using volume up/down to select, and power button to select) you can select to poweroff(shutdown) the phone - and the phone will shutdown,
or you can turn off the fastboot, and the phone will restart normally.
The thing is that when you restart your phone normaly, while fastboot on, the phone skips some steps, and go directly to to turn it on and show you the startscreen.
When you make a major update, like system upgrade, when the phone restarts, he needs to load all the boot setting. And here is the problem. If you have fastboot on, and make a major update, the phone will enter in this ****ty cicle of continous restarts.
Remember to deactivate this Fastboot before you update!
Click to expand...
Click to collapse
First, the FASTBOOT selection in bootloader is not the same as "Fast boot" in Settings>Power. The latter just makes the phone start faster from power OFF. The former is an adb (Android Debug Bridge) special mode that allows you to flash partitions from a computer.
Second, in bootloader, you should have the following selections:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Of course, its the FACTORY RESET option you want if you want to wipe the phone. Scroll down to (using vol keys) and select with power button.
On the bootloader screen, the active selection is the blue box with white text below the green phone info (hboot number, radio number, etc.). FASTBOOT should only be the default "active" selection if your phone is connected to a computer by USB. Otherwise the default selection in bootloader should be HBOOT.
Third, the "Fast boot" option in Settings>Power does not make a restart "faster" by skipping any steps. It just makes a start from power OFF faster. Its kind of a trick, where power OFF is not really off, but just a deeper sleep mode. A restart is always a restart, regardless of whether "Fast boot" is selected or not in Settings>Power.
Nexus 9 WIFI 16Gb stock android now stuck in endless boot after OTA 5.1.1.
Unfortunately I have a few valuable files on the device that haven't been backed up. Do I have any options to get the files back?
This is what I've tried so far:
1. Wipe cache from recovery menu. Had a warning about low diskspace before OTA that I had fixed by clearing cache for individual apps.
2. adb sideload 5.1.1
None of them worked. The latter fails because it will only upgrade from an older version and claims I already have 5.1.1.
Do I have any options left to pursue other than set this crappy device on fire and forget about it? :crying:
Mine was updated today and it's randomly rebooting. I've cleared the cache and factory reset from stock recovery like 3 times so far. And I'm still dealing with that. Mind you I just bought this thing this morning. It maybe going back soon if no daylight is found.
Have this issue too (assuming it's from the latest update). I've already done a cache wipe and factory reset. It's still on endless boot. It boggles the mind as to how such a thing can happen on a stock device.
Is there anyone outthere that was able to solve this by not sending the device in?
conceptics said:
Have this issue too (assuming it's from the latest update). I've already done a cache wipe and factory reset. It's still on endless boot. It boggles the mind as to how such a thing can happen on a stock device.
Is there anyone outthere that was able to solve this by not sending the device in?
Click to expand...
Click to collapse
Did you ever unlock the bootloader?
madbat99 said:
Did you ever unlock the bootloader?
Click to expand...
Click to collapse
No... never. It's completely stock. Any advice?
conceptics said:
Have this issue too (assuming it's from the latest update). I've already done a cache wipe and factory reset. It's still on endless boot. It boggles the mind as to how such a thing can happen on a stock device.
Is there anyone outthere that was able to solve this by not sending the device in?
Click to expand...
Click to collapse
conceptics said:
No... never. It's completely stock. Any advice?
Click to expand...
Click to collapse
Hi, conceptics...
If you haven't unlocked the bootloader, or enabled the 'OEM unlock' setting in Developer Options...
SETTINGS>> DEVELOPER OPTIONS>>OEM unlocking (allow the bootloader to be unlocked)
...then your options are limited.
-----
With an unlocked bootloader, or at the very least, with the option to unlock the bootloader, (and which requires the above setting to be enabled, and which requires Android to be fully booted in order to enable it), your Nexus 9 would almost certainly be recoverable by simply reflashing it with a Nexus 9 Google factory stock image, or fastboot flashing TWRP Custom Recovery, and then using an ADB 'pull' command to copy your stuff off of the device to your laptop/PC.
But with a locked bootloader, and likely an unlockable bootloader, these options aren't available.
I suspect you're going to have to return your device under warranty .
-----
But before you do...
Have you tried booting the Nexus 9 into Safe Mode?
-----
Safe Mode is ostensibly an Android troubleshooting mode, designed to temporarily suspend all third party (possibly rogue, badly written) user installed apps (those installed via PlayStore or user 'sideloaded' APKs) and just boots the bare essentials of the Android OS.
Now normally, booting into Safe Mode is accomplished by pressing the Power button as normal for shutdown, and then LONG PRESSING on the 'Power Off' dialogue box/option that appears and which you then just normally tap on.
(See second and third attached screenshots.)
Obviously this isn't an option if Android won't boot in the first place, due to it bootlooping.
But like the older Nexus 7, the Nexus 9 can be Safe Mode booted from a complete shutdown state.
Here are the instructions...
bftb0 said:
...
....
[size=+1]Safe Mode Boot[/size]
From a cold start boot (press & release Power button), wait 2 seconds after the B&W Google (bootloader) splash screen appears, then press and hold Vol-Down button until the normal OS boot is fully completed (lock screen or home screen appears)
....
...
Click to expand...
Click to collapse
Full post here: http://forum.xda-developers.com/showthread.php?t=2133986
-----
Precision is required for this button combination...
Power on the device, and RELEASE the power button after the black and white Google logo has displayed for about 2 seconds, then PRESS AND HOLD the Volume Down button ONLY... and KEEP IT HELD DOWN until the device completes booting.
Whilst this Safe Mode boot instruction is written with the Nexus 7(2012) in mind, it also works with the Nexus 9.
I've just tested this procedure on my own Nexus 9. See last attached screenshot
As you can see from the screenshot, all of my user installed apps are 'greyed out' and are temporarily unavailable for use. Notice also the Safe Mode message in the lower left hand corner.
(See attached screenshot four.)
----
If you do successfully boot into Safe Mode, you can then uninstall any or all third party apps that might be problematic, and more importantly go to...
SETTINGS>>ABOUT TABLET>>Build Number ...and then tap 7 times on the Build Number until you become a 'Developer' (...if only it was that easy... )
...and then go to...
SETTINGS>> DEVELOPER OPTIONS>>OEM unlocking (allow the bootloader to be unlocked)
...and enable (checkbox tick it) that infernal setting that has caused so much trouble for Nexus 9 owners!!!
(See first attached screenshot.)
If all of this works, you can then unlock the bootloader, and reflash the device... .
-----
My suggestions here are what in America I think are called a 'Hail Mary Pass', and I am not particularly optimistic it will fix your Nexus 9 .
But it's gotta be worth a shot.
You have nothing to lose by trying it.
Best of luck, and I hope this helps.
Rgrds,
Ged.
I have successfully installed ROMs on Nexus devices, but this one has me stumped. When I issue, "adb reboot bootloader" I get the FASTBOOT and RESCUEMODE screen telling me to use HiSuite to fix it (which didn't help, btw). No options (and I've seen other threads with this issue but no answers). I'm new so can't post a link, but picture is here i.imgsafe.org/d1da047.jpg
- If I try to "adb reboot recovery", It just reboots normally
- If I hold down power and vol down, I get eRecovery, but it will only let me download over wifi (which ultimate fails getting package details) or reboot/shutdown. No options to wipe anything.
- If I hold power and vol up (or both vol up/down) it just constantly restarts with "<vibrate>Honor, for the brave" screen but never boots anything.
My niave hunch is that my normal bootloader got replaced with some kind of OTA upgrade loader and is now stuck. I can otherwise use the phone but I'd like to apply my OEM unlock code I worked so hard to get.
lmatter2 said:
I have successfully installed ROMs on Nexus devices, but this one has me stumped. When I issue, "adb reboot bootloader" I get the FASTBOOT and RESCUEMODE screen telling me to use HiSuite to fix it (which didn't help, btw). No options (and I've seen other threads with this issue but no answers). I'm new so can't post a link, but picture is here i.imgsafe.org/d1da047.jpg
- If I try to "adb reboot recovery", It just reboots normally
- If I hold down power and vol down, I get eRecovery, but it will only let me download over wifi (which ultimate fails getting package details) or reboot/shutdown. No options to wipe anything.
- If I hold power and vol up (or both vol up/down) it just constantly restarts with "<vibrate>Honor, for the brave" screen but never boots anything.
My niave hunch is that my normal bootloader got replaced with some kind of OTA upgrade loader and is now stuck. I can otherwise use the phone but I'd like to apply my OEM unlock code I worked so hard to get.
Click to expand...
Click to collapse
Also (I'm at work so doing this from my crappy memory), I sometimes do get the phone into an OTA update screen which either stays stuck at zero percent (and I have to hold power down to restart) or successfully "installs" and then just boots normally.
Ok so in a nutshell I was trying to FRP unlock my friends phone. Problem is that it kept bringing up an error while loading the setup. I finally got it to where i input the account information (as the owner) and I was able to open settings through bugging out the voice search (I also could open file manager).
I noticed unknown sources was greyed out.
Before consideriing doing a factory reset I went ahead and took my friends advice and stopped setup.apk and google play services.apk
When zi went to clear the data it ended up taking me to the very first start screen, I was just a few steps from completion.
Now after I say setup new device the phone switches between activating network and clicking setup new device. Even clicking emergency call does nothing.'
Meanwhile when talkback is on she informs me how every single play services, gmail, and contact app stop working.
In summary, I want to factory data reset the phone.
Chimeratools. load stock firmware -> reloads firmware but doesn't wipe the current data (refurbish not available for this device, only load)
LGUP -> Load is available, but refurbish is not
Hard Keys -> Apparently the G5 doesnt have hard key capability
TWRP -> thing is not oem unlocked
ADB into stock recovery -> ADB will not work.......not usb debugging.
Please assist
With the phone shutoff hold volume down and power, as soon as you see the lg screen release the power button then quickly repress it. make sure to not let go of the volume down button. it might take a few tries but you should be able to get into factory reset menu
firenemesis7 said:
With the phone shutoff hold volume down and power, as soon as you see the lg screen release the power button then quickly repress it. make sure to not let go of the volume down button. it might take a few tries but you should be able to get into factory reset menu
Click to expand...
Click to collapse
This doesn't work...no matter how many times you try the volume down/power release and reapply procedure ...it never get in to factory reset mode. Any other ideas?