Help nexus 9 boots into recovery by default - Nexus 9 Q&A, Help & Troubleshooting

I am in a messed up situation, I live outside US, asked a friend to bring me a nexus 9 from US. Tablet was ordered from Amazon, and when I received it its box was open. Anyway long story short when I turned on the tablet it showed me google logo then directly went to recovery screen (android logo with exclamation sign and text no command). This is all I get no matter how many times I restart the tablet.
I don't know how it got into this state, but I tried resetting it from recovery and fast boot, but it shows me same screen.
Boot loader is locked and I can not unlock it with unlock boot loader command, it tells me I don't have permission to run this command, now I know in nexus 9 you have to check a box in developer settings to run that command but the irony is I never reach the OS screen.
So I have locked boot loader, I am in a boot loop where my tablet boots into recovery by default, I can not unlock boot loader with simple unlock command, but I have access to boot loader and recovery and also ADB.
What option if any I have, is there any way to unlock boat loader without first checking that box in developer options, I really need help here other wise my money is going down the drain.

sahirsani said:
I am in a messed up situation, I live outside US, asked a friend to bring me a nexus 9 from US. Tablet was ordered from Amazon, and when I received it its box was open. Anyway long story short when I turned on the tablet it showed me google logo then directly went to recovery screen (android logo with exclamation sign and text no command). This is all I get no matter how many times I restart the tablet.
I don't know how it got into this state, but I tried resetting it from recovery and fast boot, but it shows me same screen.
Boot loader is locked and I can not unlock it with unlock boot loader command, it tells me I don't have permission to run this command, now I know in nexus 9 you have to check a box in developer settings to run that command but the irony is I never reach the OS screen.
So I have locked boot loader, I am in a boot loop where my tablet boots into recovery by default, I can not unlock boot loader with simple unlock command, but I have access to boot loader and recovery and also ADB.
What option if any I have, is there any way to unlock boat loader without first checking that box in developer options, I really need help here other wise my money is going down the drain.
Click to expand...
Click to collapse
Can you get into recovery, when you get the exclamation mark use power + vol up? If you can do a factory reset in that
Sent from my Nexus 9 using XDA Free mobile app

Yap, already tried that, but it did not fix any thing
Sent from my SM-N910C using XDA Free mobile app

Did you try a factory reset from the bootloader?

Yap, did that
Sent from my SM-N910C using XDA Free mobile app

Related

[Q] bootloader unlocking even though it says locked in the service menu

Only asking because now that fire droid has stopped being developed their is now their is no cyanogen mod for locked boot loader and as my phone is a t mobile one i cannot unlock the boot loader because i cannot get into the fast boot because nothing happens (continues to charging animation) even though i have all the drivers installed and i have even tried on two different computers. I think it could be that in the service menu it says it cannot be unlocked even though i can get the unlock code from Sony.
If in service menu its says it cant be unlocked then there is no way to unlock it i guess......
bobthecooldad said:
Only asking because now that fire droid has stopped being developed their is now their is no cyanogen mod for locked boot loader and as my phone is a t mobile one i cannot unlock the boot loader because i cannot get into the fast boot because nothing happens (continues to charging animation) even though i have all the drivers installed and i have even tried on two different computers. I think it could be that in the service menu it says it cannot be unlocked even though i can get the unlock code from Sony.
Click to expand...
Click to collapse
No means no unfortunately
Regards
Dr. Sanket

[Q] HTC one bricked. Please help.

Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
xeas said:
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
Click to expand...
Click to collapse
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
clsA said:
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
Click to expand...
Click to collapse
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
xeas said:
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
Click to expand...
Click to collapse
very good
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
qibz said:
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
Click to expand...
Click to collapse
Welcome to XDA
posting your problem with all the needed information in a new thread would help.
when making your post be sure and include
whats on the bootloader screen
and a copy/paste of the results from fastboot getvar all
most likely your not s-off or your not on the correct version of TWRP
also in your new post add @clsA so i get the notification that you posted

[Q] Did a lot of research, no help. Little help with white screen of death??

Stock DNA, never rooted, never s-off. Fell asleep and woke back up with phone in quietly brilliant bootloop. Went into boot loader, cannot access recovery(just bootloops), can't do factory reset(just freezes and have to reboot) . Downloaded and followed all necessary steps to use adb and reboot recovery, when typing adb devices it shows up blank, but when I do fast boot devices my serial number comes up. When in fast boot on the phone it says fast boot USB how it should. As of lately the bottom 3 buttons are starting to flash when holding down power button, before they didn't. Also when I plug it into the wall it never showed the battery icon actually charging, but now it does, when it gets to a certain % it turns itself on and bootloops. What to do what to do??
I can always run the latest ruu file, but won't that pretty much wipe everything?
Yes, ruu will wipe everything. If your pho e isn't accepting any commands, I don't see how it would accept an ruu anyway. You could try it.
Sent from my HTC6500LVW using XDA Free mobile app
Upon further investigation, I'm pretty sure it's the boot loader that's the problem, it can reboot when I do fast boot reboot, but when I do reboot boot loader it just shuts off and doesn't turn back on. Same with trying to run the ruu, connects and everything, but as soon as it reboots back in the boot loader, it doesn't and says there's a USB connection error. So thats where I'm at, any help at all?
What OS is your PC?
Sent from my HTC6500LVW using XDA Free mobile app
Still running windows vista!
It might be a driver issue. can you try to load up a Linux live CD and see if it recognizes the phone? Vista hasn't had any updates or support from Microsoft since 2011 iirc.
Sent from my HTC6500LVW using XDA Free mobile app
Not alot of experience with Linux, anyway you could get me a link to what I need. I also tried the SD option from bootloader and it said Initialization failed.... So not sure if its an SD card issue.
Well, not sure what happened, but I did Fastboot oem task 28 and it accepted and turned right back on! Hell yes.

Infinite boot animation screen Nexus 5

***
SO I AM RENDERING THIS NEXUS 5 DEAD (BRICKED FOREVER)
***
My daughter was using this Nexus 5 device and the power button started causing her problems.
Well I removed the power button and ordered a new one. So now the power button is not an issue.
But I guess during the time that the phone constantly kept rebooting due to the bad power button, something got corrupt.
Now the device gets to the boot animation and never goes any further.
There are no options in recovery for me to use.
I have working ADB and Fastboot on my PC. I can see the device with Fastboot but not ADB because I can't get the device to boot into the OS for me to enable USB debug.
But I know ADB works because I used it just the other day on a Galaxy S5.
I have tried to run fastboot oem unlock, it unlocks the device then once you reboot the boot loader, it says locked again.
I have tried using Nexus Root Toolkit and hit unlock and it unlocks then says the phone will reset itself and just be patient. It may appear to bootloop but just wait.
I waited for an hour and still just sits at the boot animation.
What are my options without being able to enable USB debug since the device will not boot to the OS?
I am able to Temporarily boot to a custom recovery, but I can't mount data!!!
With Temporary TWRP, I am able to use ADB and I get a success message when I push a new system image to it, and when I push twrp recovery to it, but when the phone reboots, I find out that neither the system image or recovery were actually installed.
I looked into bad partitions, tried some fixes, and nothing works. I am so far beyond frustrated with this thing. I guess I will wait one more day to see if anyone else has any other ideas for me to try, then I am just going to put it in the trash.
- Bootloop
- Bootloader doesn't stay unlocked
- Unable to mount storage
- USB Debugging is not enabled and can't be enabled
- Can't install OS image
- Can't install Recovery
- Can run TWRP temporary
- Can use ADB when TWRP Temporary is running, still can't mount anything

My phone is not booting

I don’t know what happened to my phone, but I booted up the phone and I get the error in the picture below. The boot loader is locked and I can’t unlock it, it says “flashing unlock is not allowed “ and I can’t access download mode or any mode except boot loader.
So is there anyway to revive my phone again? Maybe force unlock boot loader or flashing stock bios using fastboot?
Thank you for your time.
moomlufi said:
I don’t know what happened to my phone, but I booted up the phone and I get the error in the picture below. The boot loader is locked and I can’t unlock it, it says “flashing unlock is not allowed “ and I can’t access download mode or any mode except boot loader.
So is there anyway to revive my phone again? Maybe force unlock boot loader or flashing stock bios using fastboot?
Thank you for your time.
Click to expand...
Click to collapse
Press and hold power key to continue
You probably pressed power button which paused it from going further
That's the ugly Red safety warning, not the benign yellow one. As I understand, this is what happens if the bootloader is locked and one of the partitions fails its security check. All partitions must be completely stock when the bootloader is locked.
@runningnak3d described this somewhere, and I seem to recall it's a hard brick, or at least pretty hard. But I hope I'm wrong

Categories

Resources