We bought a used / refurbished tablet, but got 2 of them. The seller said it's okay and doesn't want it back. One tablet works, one tablet is factory resetted and locked with a PIN.
Alternatively I can unlock it with the last used google account. I neither have PIN nor google account.
Is it still possible to use the tablet or is it just an high tech paperweight?
I can boot into FFBM mode (Power + Volume Up)
pretty empty here
I can boot into fastboot mode (Power + Volume Down)
The tablet gets recognized by my laptop.
I tried "fastboot erase data", but got the error "remote: device is locked. Cannot erase."
I tried "fastboot oem unlock", but got the error "remote: unknown command"
I can boot into Android recovery (Power + Volume Up + Volume Down)
I selected "Wipe data/factory reset" and "Wipe cache partition".
After reboot it's still asking for the last used PIN or the last used google account.
The tablet is a Lenovo M10. Seems like I can't get a connection over "adb shell" at all "no devices/emulators found".
Maybe anyone of you has an idea.
@arv_
Your problem is that tablet is FRP locked. This lock can't get sinply removed by means of any method selectable in Android's recovery or ADB and/or Fastboot.
Try Lenovo FRP Remove Tool.
FYI:
I tried "fastboot erase data", but got the error "remote: device is locked. Cannot erase."
Click to expand...
Click to collapse
Indicates that tablet's bootloader is locked.
I tried "fastboot oem unlock", but got the error "remote: unknown command"
Click to expand...
Click to collapse
Says the "oem unlock" subcommand isn't a valid one. Try "fastboot flashing unlock" instead.
I can't get a connection over "adb shell" at all "no devices/emulators found".
Click to expand...
Click to collapse
Tells you that you haven't established an ADB connection yet. Try "adb devices" instead.
jwoegerbauer said:
Try Lenovo FRP Remove Tool.
Click to expand...
Click to collapse
This does not work.
jwoegerbauer said:
Says the "oem unlock" subcommand isn't a valid one. Try "fastboot flashing unlock" instead.
Click to expand...
Click to collapse
This works, but says "remote: oem unlock is not allowed"
But FRP Remove seems like what I am looking for. And seems like Lenovo / Android are trying to prevent this.
Related
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.
Its not broken as it works to boot up into recovery. I am trying to unlock the bootloader on my blu studio one S0110UU. "Fastboot devices" shows my device so its connected properly Any help would be greatly appreciated. "Fastboot oem unlock" shows the confirmation screen but only the volume down button seems to work and get a response.
Also when trying to sideload in adb or flash in fastboot I consistently come across the error "Could not find "META-INF/com/google/andriod/update-binary in the zip file" Am i not using the correct file or something?
stickyfingers88 said:
Its not broken as it works to boot up into recovery. I am trying to unlock the bootloader on my blu studio one S0110UU. "Fastboot devices" shows my device so its connected properly Any help would be greatly appreciated. "Fastboot oem unlock" shows the confirmation screen but only the volume down button seems to work and get a response.
Also when trying to sideload in adb or flash in fastboot I consistently come across the error "Could not find "META-INF/com/google/andriod/update-binary in the zip file" Am i not using the correct file or something?
Click to expand...
Click to collapse
I have the same problem with Lenovo C2 phone. R u find the resolv alredy?
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
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
salmanvai said:
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
Click to expand...
Click to collapse
Edit. Okay, ignore most of what i said down there as after re-reading your post you seem to have a grasp on fastboot, the no command bit still applies though i think
"No Command" mode
If your talking about the recovery with the android image in the background, then there might still be hope, for some reason, the recovery starts up in this mode, showing the "no cammand" message, its fiddly, but you have to press the power button and either volume up or volume down repeatedly, in the end i was button spamming all the buttons and eventually the recovery menu showed up. Carefull to stop pushing buttons when the menu shows up as the buttons are how you navigate(v+,v-) and choose options(power button)
Whether that gives you any options i dont know, you could try a factory reset from the recovery menu, i suppose, or try the posted ota in the other thread if nokia has`nt released official firmware, although im not sure if you can use stock recovery to flash unofficial firmware, best bet is to try and boot into fastboot and use adb on another computer to flash the firmware that way, assuming the firmware files are available.
Most android devices have a way to boot into recovery or fastboot/bootloader using hardware keys
Quick google found this (works?)
Power off
Connect Micro USB to computer.
"In the next step hold down Volume Down + Power key for a short while"
Let go of the buttons when fastboot comes up
Using the computer with adb installed, go to a command terminal and type "fastboot devices" without quotes, you`ll know everythings working if your the device is listed in terminal after typing that command. From there look up fastboot flashing firmware or something to that extent, this is assuming you managed to find the correct firmware for your device and have it stored in your computer
I`d be real carefull here with fastboot, flashing wrong image file could make things much worse, at least it seems you can boot to recovery, so hopefully a factory reset fixes things, use fastboot as last resort i.e if its new job is a paperweight, as i dont think theres any particular guide on doing this specifically for the nokia 1, but i havent checked thouroughly so i could be wrong, take a look and see..............
And let us know if/how you managed to get it working
Goodluck
hi all,
i am having problems flashing twrp, at first i had my device showing up after typing "fastboot devices" (as a string of numbers and letters) then i tried "fastboot flash recovery" but i got an error sending it "failed to write to device"
now my device shows up only as questionmarks (i guess no device found)... what can i do?
bad1080 said:
hi all,
i am having problems flashing twrp, at first i had my device showing up after typing "fastboot devices" (as a string of numbers and letters) then i tried "fastboot flash recovery" but i got an error sending it "failed to write to device"
now my device shows up only as questionmarks (i guess no device found)... what can i do?
Click to expand...
Click to collapse
You can reboot the PC and phone and then check. How does it show up when booted (if you type "adb devices")? If it shows up again like this, then reinstall the drivers and try. Also check your Device Manager to see how the phone shows up.
tnsmani said:
You can reboot the PC and phone and then check. How does it show up when booted (if you type "adb devices")? If it shows up again like this, then reinstall the drivers and try. Also check your Device Manager to see how the phone shows up.
Click to expand...
Click to collapse
thanks, i could reach my device again with "fastboot devices" after reboots were made but after "adb reboot bootloader" it shows only question marks again... is this an amd/ryzen related issue too?
edit: the answer is: yes, it very much seems ryzen related as it worked on another pc (with an amd a6 apu)