I have 32GB WIFI, Nexus 9 bought from Amazon which unfortunately has got stuck in boot loop after updating to 5.0.2 (LRX22L) released on air . My device is locked and it doesn't give permission to use "fastboot oem unlock" command thus I can't flash factory image because it says device is locked. I've tried Factory reset from fastboot mode and also from Recovery menu (wipe cache partition and wipe data/factory reset) and it still has the problem. That's worthy to note that PC recognizes device with "fastboot devices" command but it doesn't recognize using command "adb devices".
my PC's OS is 64bit windows 8.1
Then I tried using "Apply update from ADB" in recovery menu and sideload which gave me E: footer is wrong and signature is unspecified but in this mode command window in platform-tools path recognizes device as "adb device" command used.
The other thing I tried was unlocking the device using adb shell (and so on) and it says :closed
I'd be grateful if you folks, helped me with your solutions.
npa2194 said:
I have 32GB WIFI, Nexus 9 bought from Amazon which unfortunately has got stuck in boot loop after updating to 5.0.2 (LRX22L) released on air . My device is locked and it doesn't give permission to use "fastboot oem unlock" command thus I can't flash factory image because it says device is locked. I've tried Factory reset from fastboot mode and also from Recovery menu (wipe cache partition and wipe data/factory reset) and it still has the problem. That's worthy to note that PC recognizes device with "fastboot devices" command but it doesn't recognize using command "adb devices".
my PC's OS is 64bit windows 8.1
Then I tried using "Apply update from ADB" in recovery menu and sideload which gave me E: footer is wrong and signature is unspecified but in this mode command window in platform-tools path recognizes device as "adb device" command used.
The other thing I tried was unlocking the device using adb shell (and so on) and it says :closed
I'd be grateful if you folks, helped me with your solutions.
Click to expand...
Click to collapse
You only have one solution: return it to Amazon for replacement.
cam30era said:
You only have one solution: return it to Amazon for replacement.
Click to expand...
Click to collapse
You mean there is no other way for rooting or unlocking Nexus9 ? any program, application , command etc?
npa2194 said:
You mean there is no other way for rooting or unlocking Nexus9 ? any program, application , command etc?
Click to expand...
Click to collapse
Correct. No way if your bootloader is locked.
Related
Hello, everyone
I rooted my phone 2 weeks ago and 2 days ago I got an update notification which I did and then something occurred and the phone started to reboot itself.
I tried to recover from the backup that I did when I rooted the phone and now there is a new problem. When starts, a message "com.android.phone has stopped working" pops up and I can't use the phone.
I tried starting on Recovery Mode multiple times with no results, the phone just starts normally. I also tried to connect the phone to the PC (Running linux) but the command 'adb devices' shows nothing.
Any help is appreciated.
Thanks!
P.D: Srry for my bad English
Enable usb debugging on developer options and plug the phone to your pc and run the comand "adb reboot recovery" and it should reboot to recovery
Sorry for my english
hetor99 said:
Enable usb debugging on developer options and plug the phone to your pc and run the comand "adb reboot recovery" and it should reboot to recovery
Sorry for my english
Click to expand...
Click to collapse
Hi!
Developer Options were already enabled. But the the computer doesn't recognize the phone. When running 'adb reboot recovery' it says "error: no devices found" (on windows) and error: device'(null)' not found (on linux)
stephs1515 said:
Hi!
Developer Options were already enabled. But the the computer doesn't recognize the phone. When running 'adb reboot recovery' it says "error: no devices found" (on windows) and error: device'(null)' not found (on linux)
Click to expand...
Click to collapse
On windows, you have installed the drivers??? And if you want view the devices that are plugged run these "adb devices" if the problem continues, try with an different pc or port usb
You can't boot into recovery? but why?
When you select "Recovery" option in fastboot mode what does it shows?
Its kernel error I guess....vest option would be to flash recovery using flashify or ad again
Sent from my Moto E using Tapatalk
After 2-3 hours of work I finally managed to unlock my Honor5x, but my phone seems to **** up on these few steps of the xda guide:
Step 9
Boot back into the bootloader by typing the following
"adb reboot bootloader"
Step 10
Flash the recovery with the following command:
"fastboot flash recovery twrp_kiwi.img"
Step 11
Once it finishes type the following
"fastboot reboot"
My phone gets recognized by adb generally, but whenever I use the command adb reboot bootloader, immediately after my phone doesn't get recognized by fastboot, so the following steps don't work. The phone is in bootloader mode however, and it DOES say that it's unlocked.
Things I've tried:
Using different USB ports
Using different USB s
Unplugging and replugging while my phone is in fastboot
Installing TWRP from the TWRP manager app (It gives me an error with every single version that's available. The error message is "Something went wrong. Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occured. Would you like to attempt rebooting to recovery now?" Pressing the button reboot now doesn't do anything.
Re-enabled developer mode and made sure that usb debug and oem unlock are both enabled.
Computer is: Win 10 64 bit
Wtf do I do?
Araschon said:
After 2-3 hours of work I finally managed to unlock my Honor5x, but my phone seems to **** up on these few steps of the xda guide:
Step 9
Boot back into the bootloader by typing the following
"adb reboot bootloader"
Step 10
Flash the recovery with the following command:
"fastboot flash recovery twrp_kiwi.img"
Step 11
Once it finishes type the following
"fastboot reboot"
My phone gets recognized by adb generally, but whenever I use the command adb reboot bootloader, immediately after my phone doesn't get recognized by adb anymore, so the following steps don't work. The phone is in bootloader mode however, and it DOES say that it's unlocked.
Things I've tried:
Using different USB ports
Using different USB s
Unplugging and replugging while my phone is in fastboot
Installing TWRP from the TWRP manager app (It gives me an error with every single version that's available. The error message is "Something went wrong. Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occured. Would you like to attempt rebooting to recovery now?" Pressing the button reboot now doesn't do anything.
Re-enabled developer mode and made sure that usb debug and oem unlock are both enabled.
Computer is: Win 10 64 bit
Wtf do I do?
Click to expand...
Click to collapse
Install the Huawei fastboot drivers
Sent from my SM-N920T using Tapatalk
I have HiSuite, which seems to be the USB drivers for huawei, but are you talking about the ones from team android? I can't post the link because this is a new account.
Okay, now I know the topic is a bit vague but I couldn't come up with any other name.
I just got a phone (QMobile s2) and I want to factory reset it because I don't know the pin code, simple enough right?
But here's the problem, when I boot into recovery it says "No command". So I tried the following:
1. I connected it to a pc and tried doing a reset from adb (adb shell wipe data) I get " Error opendir'ing /data 'Permission denied' " (same happens with root)
2. I get into fastboot and use "fastboot -w", "fastboot format cache", "fastboot format userdata" all give the error " FAILED (remote: unknown command) "
3. Then i read that I have to use "fastboot oem unlock" before the above commands, I get a prompt on the phone but the volume keys don't work and I get " FAILED (remote:Unlock operation is not allowed)"
And now I got nothing... any help would be appreciated.
I too Got That When I boot To recovery on my Old note 3.
Good for me Holding power Button for 2s Solved That.
Sent from my Nexus 6P using Tapatalk
Does enabling OEM Unlock from developer options (Android 5.1.1) unlocks the bootloader?
If yes then can I directly flash a custom recovery after enabling OEM Unlock?
ayu321 said:
Does enabling OEM Unlock from developer options (Android 5.1.1) unlocks the bootloader?
If yes then can I directly flash a custom recovery after enabling OEM Unlock?
Click to expand...
Click to collapse
No, it only gives you permission to unlock bootloader.
You will need to unlock bootloader using adb.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and your phone will reboot normally.
Augustoandro said:
No, it only gives you permission to unlock bootloader.
You will need to unlock bootloader using adb.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and your phone will reboot normally.
Click to expand...
Click to collapse
thnx for the reply augustonandro ! but i think im doing something wrong , whenever i type the command adb reboot bootloader my device(Galaxy J200G) restarts instead of rebooting to bootloader . So I just went to my stock recovery and chose option "reboot to bootloader" but still it restarted instead of rebooting to bootloader.
Am I doing something wrong?
ayu321 said:
thnx for the reply augustonandro ! but i think im doing something wrong , whenever i type the command adb reboot bootloader my device(Galaxy J200G) restarts instead of rebooting to bootloader . So I just went to my stock recovery and chose option "reboot to bootloader" but still it restarted instead of rebooting to bootloader.
Am I doing something wrong?
Click to expand...
Click to collapse
Try "adb reboot download" command
If u try
Setting>Developer Option>
Now search
OEM Unlock and enable
Ashwinrg said:
Try "adb reboot download" command
Click to expand...
Click to collapse
this command reboots to download mode not bootloader
guys i just found out this thread:https://forum.xda-developers.com/galaxy-j2/development/dev-samsung-galaxy-j2-lte-t3258147 and it says that just enable OEM Unlock and your bootloader will be unlocked. Is it true?
No, as explained above. That just allows the bootloader to be unlocked via ADB/fastboot (unless the bootloader is locked down like many ZTE phones).
Have you tried "adb reboot-bootloader"?
HI...I know after so many years....But i am having some problem considering my nokia 5 phone....In developer option the OEM unlock is greyed out and i cannot unlock it at all(i cannot toggle it on)....Any possible way i can turn it on....Let me know....Thanks in advance
Thebisboss said:
HI...I know after so many years....But i am having some problem considering my nokia 5 phone....In developer option the OEM unlock is greyed out and i cannot unlock it at all(i cannot toggle it on)....Any possible way i can turn it on....Let me know....Thanks in advance
Click to expand...
Click to collapse
It might already be unlocked
I am trying to put a custom Rom on my phone but can't at the moment.
I have used adb-setup-1.4.3 for adb and fastboot.
Whenever in using "adb devices" command, it shows my device name and when I boot into bootloader it does show my device name as well when I use "fastboot devices". It lets me flash recovery but whenever I try to use adb push I get error: device '(null)' not found.
I have tried to enter recovery and to use MTP or adb sideload but my phone is not recognized there i.e. no device shown when I use "adb devices".
After many tries and and installing/ reinstalling drivers, I did a clean install on my laptop (Win 10).
Installed adb 1.4.3 <Only adb and fastboot>
Installed Xiaomi drivers using Mi Flash Tool.
Still facing the same issue.
Strangely I have Mi Mix 2 as well and it shows up in recovery under adb devices.
What am I doing wrong?
Have you tried with another cable or diffrent USB port?
I did but same result. Any other advice I can follow?
TSKXDA said:
I am trying to put a custom Rom on my phone but can't at the moment.
I have used adb-setup-1.4.3 for adb and fastboot.
Whenever in using "adb devices" command, it shows my device name and when I boot into bootloader it does show my device name as well when I use "fastboot devices". It lets me flash recovery but whenever I try to use adb push I get error: device '(null)' not found.
I have tried to enter recovery and to use MTP or adb sideload but my phone is not recognized there i.e. no device shown when I use "adb devices".
After many tries and and installing/ reinstalling drivers, I did a clean install on my laptop (Win 10).
Installed adb 1.4.3 <Only adb and fastboot>
Installed Xiaomi drivers using Mi Flash Tool.
Still facing the same issue.
Strangely I have Mi Mix 2 as well and it shows up in recovery under adb devices.
What am I doing wrong?
Click to expand...
Click to collapse
You don't need to use asb push
After u flash the recovery
Boot Into the recovery using "fastboot boot "recovery file"" and then flash the zip file from the recovery
You can flash from internal storage or sd card so it's best to put the files in the SD card and flash from there
MobyDuhFreak said:
You don't need to use asb push
After u flash the recovery
Boot Into the recovery using "fastboot boot "recovery file"" and then flash the zip file from the recovery
You can flash from internal storage or sd card so it's best to put the files in the SD card and flash from there
Click to expand...
Click to collapse
If I try to fastboot into recovery I still get the same error.
TSKXDA said:
If I try to fastboot into recovery I still get the same error.
Click to expand...
Click to collapse
Is your phone a redmi 5(codename Rosy) or a redmi 5 plus or a redmi note 5 in India (codename Vince)?