Hi, I literally opened the nexus 9 out of the box, powered it on & after choosing a wifi network it began updating, the device crashed during this update and now it won't boot! I've tried & searched for everything, anyone have any ideas?
Booting to recovery with HW buttons, wiping cache/userdata/factory reset - Nada!
Can boot into fastboot, no permission to flash as oem unlock is disabled!
I cant get into the tablet to unlock fastboot oem unlock within devOpitons or usb debugging etc, (com.android.phone has stopped on boot) black screen indefinitely.
I can't flash any images while it is locked
surely there must be a simple method?
desperate here
Return it
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
VermontKindBud said:
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
Click to expand...
Click to collapse
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
syko9 said:
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
Click to expand...
Click to collapse
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
cam30era said:
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
Click to expand...
Click to collapse
Alright thanks for the info, guess it shall be replaced thanks.
syko9 said:
Alright thanks for the info, guess it shall be replaced thanks.
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that.
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Ripx88 said:
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Click to expand...
Click to collapse
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
cam30era said:
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
Click to expand...
Click to collapse
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Ripx88 said:
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Click to expand...
Click to collapse
No problem. That's how we learn.
cam30era said:
No problem. That's how we learn.
Click to expand...
Click to collapse
Indeed I'm still new to nexus devices. I've been flashing on Samsung devices for years so I'm still stuck in my Odin ways. Just got the N9 less then a week ago. The whole fastboot thing was foreign at first but I'm getting there lol. Thank you again.
Related
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
tekmeister98 said:
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
Click to expand...
Click to collapse
Oh I forgot to mention I was on fire os 4.5.2 before this happened.
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
EncryptedCurse said:
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
Click to expand...
Click to collapse
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
tekmeister98 said:
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
Click to expand...
Click to collapse
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
tekmeister98 said:
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
Click to expand...
Click to collapse
And I can't get to adb shell... so I need help.
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
lekofraggle said:
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
Click to expand...
Click to collapse
I've tried that but I'm stuck in a bootloop.
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
lekofraggle said:
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
Click to expand...
Click to collapse
Yeah that doesn't work. Is there any fix for a corrupted system?
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
lekofraggle said:
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
Click to expand...
Click to collapse
hmmm.. okay. Are you able to give me a cat /sys/block/mmcblk0/device/manfid and a cat /sys/block/mmcblk0/device/serial on a device of yours so I can try and unlock it?
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
lekofraggle said:
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
Click to expand...
Click to collapse
dang. Okay. Thanks for the help though. I'll just have to keep at it.
did you ever get your bootloader unlocked?
bowman1966 said:
did you ever get your bootloader unlocked?
Click to expand...
Click to collapse
Nope. I tried a bunch of stuff but it didn't work.
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Cl4ncy said:
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Click to expand...
Click to collapse
Thats just par for my coarce lol.
Ill let it sit awhile and play another day....
Resurrecting this thread... Any new fixes out yet? I've seen workarounds for starting with stock os but other than that I don't know.
Hello,
situation ist this:
Cyanogen Recovery is installed and there is no rom on the phone. But it won't install a new one through apply update. So I tried installing twrp through fast boot. But it failed with:
FAILED (remote: Device not unlocked cannot flash or erase)
So i tried to unlock it which gave me:
FAILED (remote: oem unlock is disabled)
oem devices gave me tampered = false and unlocked = false
What can I do.
Would appreciate help
Morishno
Flash stock recovery and try unlock again.
Dumb Question but how exactly do I do that?
Just flash it via fast boot? And where do i get it?
Morishno said:
Dumb Question but how exactly do I do that?
Just flash it via fast boot? And where do i get it?
Click to expand...
Click to collapse
You can get it from oneplus downloads section, if you cant find it ask me... Yes you have to flash official stock recovery through fastboot
Exodusche said:
Flash stock recovery and try unlock again.
Click to expand...
Click to collapse
cva_kabil said:
You can get it from oneplus downloads section, if you cant find it ask me... Yes you have to flash official stock recovery through fastboot
Click to expand...
Click to collapse
Not really, OP reports that the unlock command gave him FAILED (remote: oem unlock is disabled)
Hey OP, did you enable OEM Unlocking from Developer options ?
Joshwin Aranha said:
Not really, OP reports that the unlock command gave him FAILED (remote: oem unlock is disabled)
Hey OP, did you enable OEM Unlocking from Developer options ?
Click to expand...
Click to collapse
If not is there any other way?
cva_kabil said:
If not is there any other way?
Click to expand...
Click to collapse
I'm sorry but i do not know any other method that works without flipping that switch in Developer Options.
Joshwin Aranha said:
I'm sorry but i do not know any other method that works without flipping that switch in Developer Options.
Click to expand...
Click to collapse
You dont need to be sorry, thats okay i jus asked... Maybe OP didnt enable oem unlocking.
I didnt enable oem unlocking because it wasnt necessary. The device was unlocked and twrp and cyanogenmod were installed. But somehow cyanogen recovery was installed. Super user was away and I tried to reinstall it. Not knowing the recovery had changed I chose twrp/cwm to install it what resulted in a boot loop. No problem I thought just flash a ROM which didn't worked. No problem just flash a proper recovery it didn't worked. And somehow the device is locked again..
Sorry I was little brief when I said flash stock recovery. I believe if you revert back completely stock you can start the process from the beginning again. That would mean fastboot flash stock recovery then any firmware of OnePlus X. I'm not sure how a bootloader can relock itself.
Exodusche said:
Sorry I was little brief when I said flash stock recovery. I believe if you revert back completely stock you can start the process from the beginning again. That would mean fastboot flash stock recovery then any firmware of OnePlus X. I'm not sure how a bootloader can relock itself.
Click to expand...
Click to collapse
But I couldn't flash twrp.. Is it possible to flash the stock recovery with a locked boot loader? I don't have access to the phone at the moment and i want to gather as much information possible thats why i'm asking
Morishno said:
But I couldn't flash twrp.. Is it possible to flash the stock recovery with a locked boot loader? I don't have access to the phone at the moment and i want to gather as much information possible thats why i'm asking
Click to expand...
Click to collapse
I'm not sure but this has been addressed many times. Comb the threads you will find the information you need.
Exodusche said:
I'm not sure but this has been addressed many times. Comb the threads you will find the information you need.
Click to expand...
Click to collapse
Found a hard brick guide. You mean that?
So I just remembered something was able to help someone else with a similar issue. If you can boot Into something and your rooted download the app Rashr. With it you can flash stock recovery and be back in business.
The problem is i dont have anything to Boot
//UPDATE: So I tried booting with fastboot boot but it said cannot boot device isn't unlocked.
Edited
So i managed to save the Phone using the Hard Brick Guide. Thanks everyone!
Thank goodness for the hard brick guide. ?
Exodusche said:
I think your gonna have to go through the hard bricked guide.
Click to expand...
Click to collapse
Yeah i did that and it worked thank you
So, long story short, I recently bought a Nexus 9 from ebay which arrived with factory reset protection.
I have spoken to both Google and HTC about the situation and both were of no real help except for saying a few things outright between them to give me good enough reason to believe one of two things.
That 1 - it is possible to flash factory images over a device with a locked bootloader
or 2 - it is possible to unlock the bootloader without having access to developer settings
Anyone have any experience with either of these possibilities?
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
enriquejones666 said:
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Click to expand...
Click to collapse
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Those are full ota images, same as factory image. Meaning full package.
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
enriquejones666 said:
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
Click to expand...
Click to collapse
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
BigDomTheFirst said:
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
Click to expand...
Click to collapse
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
Never found out how they do this.... are you able to boot in to recovery? if you can do that you may be able to flash a recovery OTA through 'apply update from ADB'. Worth a shot
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Bryanx86 said:
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Click to expand...
Click to collapse
definitely don't lock your bootloader. That is a horrible move and serves no purpose
madbat99 said:
definitely don't lock your bootloader. That is a horrible move and serves no purpose
Click to expand...
Click to collapse
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Bryanx86 said:
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Click to expand...
Click to collapse
it's only a bad move if you make a mistake and can't repair it because your bootloader is now locked. But if it goes well then you're all set.
anybody seen this error? I was trying to revert back to stock. Once it rebooted, this happen. I found an old thread but only resolution was to warranty it. Of course this device is old so no more warranty. wanted to see if theres other solutions before i dump it on ebay for parts..
thanks
NJ_RAMS_FAN said:
anybody seen this error? I was trying to revert back to stock. Once it rebooted, this happen. I found an old thread but only resolution was to warranty it. Of course this device is old so no more warranty. wanted to see if theres other solutions before i dump it on ebay for parts..
thanks
Click to expand...
Click to collapse
You tried to relock the bootloader didn't you? Usually not a good idea. Is it not booting anymore? If it boots go in developer options and tick the allow OEM unlocking back to on. And then see if unlocking the bootloader changes it.
madbat99 said:
You tried to relock the bootloader didn't you? Usually not a good idea. Is it not booting anymore? If it boots go in developer options and tick the allow OEM unlocking back to on. And then see if unlocking the bootloader changes it.
Click to expand...
Click to collapse
yea.. smh... i actually got it out of that bootloop but i can't unlock bootloader. ill let it be. its running lineageos... i tried these steps and it actually worked if anybody has this issue...
https://forum.xda-developers.com/showpost.php?p=77355001&postcount=6
to get to the point i used the ota updater for a lineage and it wiped twrp and replaced it with lineage recovery. then i decided to perform a factory reset in sed recovery. that led to boot loop that landed me back in recovery. so i started up lgup and went back to stock oreo and bootloader remained unlocked. now that i'm back on stock oem unlock is greyed out. when in fastboot it says to enable oem unlock. so what do you guys think i should do? unable to flash or fastboot boot twrp at all.
heres the pics
https://imgur.com/a/WiDIqfm
For anyone that happens to run into this issue. Run fastboot OEM lock and it'll fail on the command line but reboot your device and it'll relock the bootloader. Then follow the Frankenstein guide to unlock the bootloader again.
Was able to immediately toggle OEM unlock after this
What error do you get when you try to flash?
Sent from my LG-US998 using Tapatalk
kenbo111 said:
What error do you get when you try to flash?
Click to expand...
Click to collapse
Any fastboot commands fail minus fastboot reboot
Also I have a ls998u that's been converted to us998
R800x_user said:
Any fastboot commands fail minus fastboot reboot
Also I have a ls998u that's been converted to us998
Click to expand...
Click to collapse
It's possible the greyed out button may turn active in a few days. This also happens immediately after bootloader unlock -- it's greyed out, then days later it can be toggled.
ChazzMatt said:
It's possible the greyed out button may turn active in a few days. This also happens immediately after bootloader unlock -- it's greyed out, then days later it can be toggled.
Click to expand...
Click to collapse
I want aware of the wait time. Thanks for the info
R800x_user said:
I want aware of the wait time. Thanks for the info
Click to expand...
Click to collapse
It's mentioned in the WTF instructions. See attached screenshot.
Hopefully this will happen to you, even though slightly different circumstances.
ChazzMatt said:
It's mentioned in the WTF instructions. See attached screenshot.
Hopefully this will happen to you, even though slightly different circumstances.
Click to expand...
Click to collapse
How long would one have to wait? Still grayed out.
Just an update to this.
R800x_user said:
How long would one have to wait? Still grayed out.
Just an update to this.
Click to expand...
Click to collapse
I never measured, but less than a week I think.
ChazzMatt said:
I never measured, but less than a week I think.
Click to expand...
Click to collapse
[email protected] okay, I'll need to try to OEM lock. I'm unsure if it'll even work. At least I have a functional v30. I was thinking using LGup would've relocked the bootloader if I downgraded.