Hello
I have a problem when I want to unlock my nexus 9.
First I have a problem because my tablet freezed.
I have made a factory reset, then google said me : used the first account to use your tablet" but I lost this account
So I want to flash my tablet.
to do that, I use the tutorial on HTC site. on step 5 they say:
type adb oem unlock
but the CMD windows just say:
<waiting for device>
then I try to show devices with adb device but my window don't show device.
to do those step my tablet was in recovery more "fastboot usb"
can you help me?
thanks
Jack
@jackvig Looks like you encountered Factory Reset Protection!
You can not use adb commands while in fastboot mode! "fastboot devices" should list your device.
And the command to unlock is "fastboot oem unlock" not adb!
Plus you won't be able to unlock the bootloader unless you have selected the option to do so in developer options, since you have factory reset that option may have been turned off even if you set it previously.
Your going to have to try and remember your account password to make the device usable.
Depending on what version/patch of the rom your device is on it maybe possible to Bypass FRP, google it.
If your device was on a very recent patch level, no bypass trick will work.
corkiejp said:
@jackvig Looks like you encountered Factory Reset Protection!
You can not use adb commands while in fastboot mode! "fastboot devices" should list your device.
And the command to unlock is "fastboot oem unlock" not adb!
Plus you won't be able to unlock the bootloader unless you have selected the option to do so in developer options, since you have factory reset that option may have been turned off even if you set it previously.
Your going to have to try and remember your account password to make the device usable.
Depending on what version/patch of the rom your device is on it maybe possible to Bypass FRP, google it.
If your device was on a very recent patch level, no bypass trick will work.
Click to expand...
Click to collapse
thanks @corkiejp for your reply
I agree with you for fastboot instead of adb but the result is the same.
I cannot go inside the tablet to change parameters
Some forum said that I can Unlock in recovery mode
Is it true?
when my tablet is in recovery mode (On/off + Vol Up)
the tablet show me device state : locked
I am in state HBOOT
the on my computer I do that
C:\Users\maison>fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.015s]
finished. total time: 0.018s
after I go in FASTBOOT mode then :
C:\Users\maison>fastboot oem unlock
< waiting for device >
what can I do to have the Key to unlock
No you need fastboot mode to unlock the bootloader!
Is the command "fastboot devices" listing your device. If not check your drivers for your device.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HT4B6JT00881 fastboot
after that i try :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload volantis-ota-n9f27m-ad1aee0f.zip
loading: 'volantis-ota-n9f27m-ad1aee0f.zip'adb server is out of date. killing...
* daemon started successfully *
serving: 'volantis-ota-n9f27m-ad1aee0f.zip' (~0%) * failed to read command: Invalid argument
i think tablet i now connected to computer
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.011s]
finished. total time: 0.014s
As suspected the option to unlock is not selected in developer options.
If your successful in sideloading an OTA image in recovery mode (not fastboot mode), you will still encounter FRP on booting the device.
Edit: - As said before ADB commands do not work in fastboot mode. And fastboot commands do not work in Recovery mode!
As said before your only hope is to remember your account and password used (or the very last account you used on the device might work).
If you haven't updated the rom in the last year, you maybe able to use FRP Bypass trick.
jackvig said:
Hello
I have a problem when I want to unlock my nexus 9.
First I have a problem because my tablet freezed.
I have made a factory reset, then google said me : used the first account to use your tablet" but I lost this account
So I want to flash my tablet.
to do that, I use the tutorial on HTC site. on step 5 they say:
type adb oem unlock
but the CMD windows just say:
<waiting for device>
then I try to show devices with adb device but my window don't show device.
to do those step my tablet was in recovery more "fastboot usb"
can you help me?
thanks
Jack
Click to expand...
Click to collapse
You should not have factory reset if you do not know the account password. It is protected by "factory reset protection". To prevent it from being used if it is stolen. You are most likely going to need the password for the account that was logged in when you reset.
Flashing is not going to help. And as mentioned previously, you cannot unlock the bootloader now since you cannot go into developer options and turn on oem unlocking.
Related
Dear all,
I have made numerous attempts to unlock the bootloader of my Wiko U Feel Prime, but to no avail.
(My goal is to flash TWRP, root with Magisk and install LineageOS.)
USB debugging and OEM unlocking are enabled in the developer settings.
ADB recognises the device. When I execute adb reboot bootloader, the device reboots, and doesn't get past the "powered by Android" screen – but is nonetheless found by fastboot when I run fastboot devices. Seems like the USB drivers are functioning properly, correct?
Now, when I run fastboot oem unlock, I get the following response:
Code:
...
FAILED (remote: unknown command)
finished. total time: -0.000s
The command fastboot flashing unlock gives the same result.
Moreover, fastboot getvar all displays no unlocked variable. The command fastboot getvar unlocked yields
Code:
unlocked:
By the way, this phone was shipped SIM unlocked.
I've spent hours looking around the web for solutions, but everyone (including guides specifically written for Wiko U Feel Prime) simply says "unlock the bootloader" as if it's a trivial task. And I've run out of ideas. Could anyone help?
Thank you very much.
Hi all,
How can I wipe the cache partition on a Poco F1 with 10.3.6.0 Global stable (stock, so not rooted)? Booting in recovery mode gives me a custom recovery with only the option to wipe all data. Can Mi Assistant help here? Or are there other options?
Google would have helped you... Reboot to recovery and try 'fastboot erase cache'. Sometimes you need a 'sudo su' before that.
guhvanoh said:
Google would have helped you... Reboot to recovery and try 'fastboot erase cache'. Sometimes you need a 'sudo su' before that.
Click to expand...
Click to collapse
Well, as I said: I have stock ROM. As far as I see I do not have any option to erase system cache in the default recovery.
As I said as well: I have stock firmware, perhaps should have added locked bootloader. So no possibility to use fastboot (again, correct me if I'm wrong).
If the only option is to unlock the bootloader I can just replace recovery with TWRP, but I'd like to avoid having to unlock...
Hi there,
First enable USB debugging in the developer options. To enable developer options, you have to tap five times on the miui version in the about phone. Connect your PC and accept the pop up in your phone to register the pc in your phone. Power off your phone first and press power button and volume down simultaneously to take you to fastboot mode. If it goes to bootloader mode, then select the option to go to fastboot mode. If the bootloader mode is in Chinese then search some forums to select the fastboot mode appropriately.
Before all these. Install minimum ADB tools in your PC. Execute fastboot commands once connected to your phone in fastboot mode.
This is very simple once you are familiar with the process. Until then these seems a nightmare'.
Cheers
sssyraj
Hit thanks if it helps you.
And just to add to the above instructions, you don't need an unlocked bootloader, just have USB debugging enabled, to use fastboot.
You use fastboot to unlock the bootloader and it would be a mite hard (and redundant) if you needed the bootloader unlocked to unlock the bootloader...
Also, just to confirm the phone is being detected in fastboot mode use the command "fastboot devices" to see if the phone is recognised.. It should show a number otherwise if it is just a blank space fastboot hasn't recognised your phone...
ultramag69 said:
And just to add to the above instructions, you don't need an unlocked bootloader, just have USB debugging enabled, to use fastboot.
You use fastboot to unlock the bootloader and it would be a mite hard (and redundant) if you needed the bootloader unlocked to unlock the bootloader...
Also, just to confirm the phone is being detected in fastboot mode use the command "fastboot devices" to see if the phone is recognised.. It should show a number otherwise if it is just a blank space fastboot hasn't recognised your phone...
Click to expand...
Click to collapse
Got it into fastboot, but now it throws an error. Google search did not give a real solution.
Error shown:
Code:
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.007s
jvdv360 said:
Got it into fastboot, but now it throws an error. Google search did not give a real solution.
Error shown:
Click to expand...
Click to collapse
With that error shown I'm not sure what formatting will do. If the current type is ext4, then you should be fine. But it is looking like you're a candidate for unlocking your bootloader...
Hi, just got a brand new Armour x5, bought unlocked. It has Android 10 on it. First, I would like to back up entire phone without installing any apps at all, adb or fastboot commands to do so would be appreciated.
I tapped developer options 7 times, enabled adb, and OEM unlocking. I then adb reboot fastboot after allowing pc to connect, and in fastboot I try:
fastboot oem unlock
and
fastboot flashing unlock
C:\adb>adb devices
List of devices attached
3082SH1001004262 device
C:\adb>adb reboot recovery
C:\adb>fastboot devices
3082SH1001004262 fastboot
C:\adb>fastboot oem unlock
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.010s
C:\adb>fastboot flashing unlock
...
FAILED (remote: Unrecognized command flashing unlock)
finished. total time: 0.010s
to no avail, fastboot just looks blackscreen and the tiniest of fonts lol... yes drivers are installed.
So I reboot, and try the Armour 6 tut, but Magisk manager has no option to patch the boot.img I extracted from stock firmware, it also has a distinct lack of advanced settings, most likely due to my not yet having flashed a twrp or magisk-20.4 due to still unable to find out about dm-verity, (is dm-verity different between android 9 + 10?) meaning I wont flash anything that will brick the fone before i even put a sim into it.
Any help appreciated. Google sux.
Edit: Well after 12 or so hours I can honestly say that rooting is all gone downhill, does anyone actually know what they are doing nowadays?
I read all 5 copies of the rooting procedure for this phone, none of which is anywhere near complete, and so very wrong. What might have worked years ago does not work now.
In the Armour x5, when rebooting into fastboot using adb reboot fastboot, we are taken to a black screen with the smallest of txt saying fastboot. This fastboot does not ****in work ('scuse the swearing) so dont tell people to do this, it wont work. Nothing works in this fastboot mode. What you have to do is go into ANOTHER fastboot, by going into what we call recovery, by pressing power and volume up button, then choosing fastboot, ONLY then will fastboot commands kind of work. I say kind of, because most of the fastboot commands do nothing anyway, but at least show some output proving that booting into fastboot from adb is useless now.
For instance, in the pure black screen fastboot, nothing is found in adb or fastboot shell, no 'null' (needing activation), no waiting, just black nothingness. But in the recovery version of fastboot, we see fastbootd at the top of the screen, this is the fastboot that recognises at least partial commands. But none I have actually tried re finding bootloader lock status etc, nada.
I also noticed, I do have shell access when in adb, but not recovery, so if anyone knows how to flash a twrp for android 10 using shell with no root, I'll try it on my not so shiney brand spankin blank fastbootin fone
Getting super frustrated!
Using ADB Debuging. Here are my steps.
1. adb devices
2. adb reboot bootloader
3.fastboot devices.
4. fastboot oem unlock
Then I get this...
FAILED (remote: unknown command)
finished. total time: 0.005s
after so many attempts I finally check adb devices and nothing shows up! It's like it automatically disconnects with adb debugging but it does not. Because I am able to to put fastboot reboot.
Can someone please help me with this! Thank you!
Use the fast boot command
Fastboot flashing unlock
Only this works on A12 devices
fastboot flashing unlock
oem unlock has been deprecated for awhile, manufacturers were just slow to implement changes.
I'm at a total loss here...
phone has unlocking and USB debugging toggled on.
phone is not a US phone and unlocking is allowed.
phone goes into fastboot mode (by turning on while holding volume)
"fastboot devices" command returns my phone is in fastboot and connected
"fastboot oem unlock 0xPASSWORD" returns FAILED (remote: 'Command not supported in default implementation')
and fastboot: error: Command failed
I have no idea what to do or try from here.
If I try to flash an image i get:
FAILED (remote: 'Download is not allowed on locked devices')
so, defiantly still locked out of the bootloader
Try below steps
1. Ensure you have platform tools 33.x , 34 has issues.
2. Try to reboot to bootloader from pc.
adb reboot bootloader
3. Try running
fastboot flashing unlock unlockcode
Try it :
fastboot oem unlock
or
fastboot flashing unlock
SOLVED I am so happy. I'm on day 3 of trying to get the phone to bootload.
there is definitely a difference between going into fastboot through the phone itself and through adb commands on PC.
fastboot through the phone shows the drop down menu and no blue light illuminated on phone.
fastboot through adb phone is black screen with a blue light on right corner on the phone.
the windows drivers behave differently between the two. I am running windows 10. phone model XQ-CT72
steps that solved the issue. For anyone in the future.
I downloaded and used platform tools version 33.0.3 NOT version 34.
"adb reboot bootloader" used from windows PC
opened windows device manager found my "discovered device" and forced it to use the SONY driver downloaded from sonys website. It would not detect it on its own, or even use the SONY driver without me telling it to specifically. device manager> "andorid" > properties > update driver > browse computer for driver > installed sony driver
everything worked following these instructions here https://www.droidwin.com/unlock-bootloader-and-root-sony-xperia-1-iv/
alexriethmeier said:
There is definitely a difference between going into ...
Click to expand...
Click to collapse
fastboot, part of the android bootloader, abl
fastbootd, part of recovery
I had same issue and same solution fixed it what you showed and did. I was terrified, after investing so much money on this phone and not getting it unlocked.
You won't need to go through such hassle if you just use Linux VM (a Ubuntu distro will do). The driver works out of the box.