Unlocking Your Nexus Q
To unlock your device
1. cd to platform-tools
2. Reboot to the bootloader - adb reboot bootloader
3. Unlock your device* (with fastboot tool type): fastboot oem unlock
*You will have to accept and erase all the user data on the tablet.
*You must run this as sudo in Linux
Credits to FadedLite (very similar steps)
Figuring out the rooting next
If you just need "su"....
1. Download su from your busybox installation from say Galaxy Nexus.
2. Download the modified clockworksmod for Nexus Q that this guy put together:
bliny.net/blog/post/How-to-Root-Nexus-Q-%28Temporarily%29.asp
3. Boot into that recovery image will give you write access to /system
4. adb push su into /system/xbin/su
Did you already have your nexus Q in debug mode? I do not have the slider button on my Nexus 7 to put it into debug mode. It's not recognized in "adb devices" or "fastboot devices"
EDIT ***
I found out that the USB Debugging menu in the Nexus Q app shows up when you turn on Developer Options in the Settings > Developer Options menu of Jellybean on the Nexus 7. You might want to test this as well on your variety of devices.
Just me that thinks this thing needs google TV?
nevermind it worked now
Stuck in oem unlock
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
took me a few tries to get it but it needs to be entered within five seconds of the first command
enriquealo said:
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
Click to expand...
Click to collapse
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
silfa718 said:
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
Click to expand...
Click to collapse
the easiest way, assuming you are running windows, is to enter the comands once, and then just use the up arrow key to do it again. also, you may want to be sure its not already unlocked "fastboot getvar unlocked" will return "yes" if unlocked
Related
Hi there,
I'm having a bit of trouble relocking my bootloader. I've tried numerous times
using Hasoons toolkit but always get the following message.
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086000 (0x7FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.975s
C:\Users\Gary\Desktop\Amaze_All-In-One_Kit_V5.1\data>
Thanks,
Gary
It always gives me that message at the command prompt, just make sure the htc drivers are installed properly, which it sounds like they already are. It's relatively easy to do this without hansoons toolkit too, just download a adb_fastboot zip, extract the folder(such as the desktop), then run the following commands in command prompt
cd /path/to/adb/and/fastboot
fastboot oem lock
or for mac users
cd /path/to/adb/and/fastboot
./fastboot-mac oem lock
I really think you already got it all locked up tho, just boot into bootloader and read the the top line
Hello Guys, im fighting with Kiano slimtab 7 3gr for a few days.
First of all i made a root form this solution: http://forum.xda-developers.com/android/development/mod-t3175515 and it worked.
Now i want to unlock bootloader and install TWRP, but there are some problems. I have estabilished ADB and Fastboot connection with no problems. But when i go into fastboot mode and im trying to unlock bootloader via fastboot oem unlock commad it doeasn't work. Could someone help me?
Code:
[email protected]:~# fastboot devices
0123456789012345 fastboot
[email protected]:~# fastboot flash recovery recovery.img
(bootloader) recovery partition type: raw
target reported max download size of 1019215872 bytes
sending 'recovery' (14090 KB)...
(bootloader) Device is locked, cannot perform flash in fastboot
(bootloader) Please use the below command to unlock first:
(bootloader) > fastboot oem unlock
FAILED (remote failure)
finished. total time: 0.026s
[email protected]:~# fastboot oem unlock
...
FAILED (remote: couldn't change state!)
finished. total time: 0.022s
[email protected]:~#
ok I've got it. There was and option to unlock oem in debugging mode settings. So after that fastboot commands suceeded. Botloader is unlocked but i guess i crashed it
I've uploaded recovery.img file and after reboot android doesn't work. I can only send fastboot commands. Could sb help me?
Did you solve your problem? I also crashed my slimtab after I unlocked the bootloader.
Yes, I've solved a problem. I threw it to trash and bought Galaxy Tab A
Did you have green screen in fastboot, or after reboot some lines on black (green, red lines). There is possibly text, but you can't read it squares. Have someone original Kiano Slimtab 7 3GR recovery.img to flash?
Здравствуйте. Дайте оригинальную прошивку или бекап. Прошивка Chuvi не подходит
My One Plus X is stuck in Oneplus logo I haven't rooted my phone, now i can only enter in fastboot mode. unable to enter in recovery mode and system.
when i try to fastboot oem unlock failed it says unable to unlock, device is locked.
how to unlock oem device through fastboot mode. or any way to solve this issue ?
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.008s]
finished. total time: 0.009s
Edit : Sorry, I forgot to answer the question : No...
**********************
Was TWRP installed before ?
Explain what you did just before that !
But seeing what you have, I bet flashing the official recovery won't work.
Flashing stock recovery
1) Download stock Recovery OnePlus (there are one for MM version and one for previous version. Depends on question one I asked !)
2) Copy the recovery in the adb folder
3) Start a new prompt command from the folder adb
4) Put the smartphone in fastboot mode (power off the smartphone , and click volume up + power)
5) Put the command "fastboot device" for be sure computer can see the smartphone
6) Put the command fastboot "flash recovery name-recovery.img"
But you bet shot will be to run the Mega unbrick guide I guess...
aiwin007 said:
My One Plus X is stuck in Oneplus logo I haven't rooted my phone, now i can only enter in fastboot mode. unable to enter in recovery mode and system.
when i try to fastboot oem unlock failed it says unable to unlock, device is locked.
how to unlock oem device through fastboot mode. or any way to solve this issue ?
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
It's softbricked. Happened to me awhile ago, i've resolved it with the unbrick tools.
*Your bootloader is locked and can't do oem unlock, can't boot to twrp/system→ So there's no way to flash anything.
You need to run the unbrick tools. Head to the mega unbrick guide for more details.
Mega Unbrick's Thread
Notes:
Link for the recovery tool in OP is dead, so use this one instead
Recovery Tool
And download "Qualcomm driver" from OP.
Hi
I'm stuck in my Xiaomi MI A3 bootloader, can't boot to recovery and system.
After flashing my stock firmware.
Here is my oem device info
PS C:\platform-tools> ./fastboot oem device-info (bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
Finished. Total time: 0.006s
PS C:\platform-tools> ./fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s
Thank you
bgsebiosjr said:
Hi
PS C:\platform-tools> ./fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s
Thank you
Click to expand...
Click to collapse
Change current-slot to 'a' and reboot.
PS C:\platform-tools> ./fastboot flashing get_unlock_ability (bootloader) get_unlock_ability: 0
OKAY [ 0.002s]
Finished. Total time: 0.005s
PS C:\platform-tools> ./fastboot flashing unlock FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
PS C:\platform-tools> ./fastboot set_active a Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
PS C:\platform-tools>
How can i use EDL?
Sapper Morton said:
Since your bootloader is locked, and there's no proper system.img in slot B, you must change it to slot A; however it's not possible in locked state, first check if it's possible to unlock, by running:
Code:
fastboot flashing get_unlock_ability
If the output is 0, you cannot unlock, and EDL is a must, otherwise, the output will be 1, therefore, unlock is possible, then proceed with the following steps:
Code:
fastboot flashing unlock
Code:
fastboot set_active a
Code:
fastboot flashing lock
As explained above, it's not possible to change slot without unlocking the bootloader.
Click to expand...
Click to collapse
msatyanarayana said:
Change current-slot to 'a' and reboot.
Click to expand...
Click to collapse
PS C:\platform-tools> ./fastboot set_active a Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
PS C:\platform-tools>
Not allowed in Lock State.
Is there any way to oem unlock without going to Debugging Mode -> OEM enable?
I can't boot my system and recovery.
bgsebiosjr said:
Not allowed in Lock State.
Is there any way to oem unlock without going to Debugging Mode -> OEM enable?
I can't boot my system and recovery.
Click to expand...
Click to collapse
EDL mode and authorized Mi account. You should contact your nearest Xiaomi service center or use some online service (you might need to open your phone yourself in such case).
Need advice. My goal is to flash GSI ROM onto this thing. The treble app says it is supported. (type A)
However, the usual commands for unlocking bootloader seem to indicate it is either already unlocked but not telling me or locked and not unlockable..?
This is a unisoc SC9863a
baseband: FM_BASE_18B_W19.08.1_P11 | SC9863a_modem | 04-26-2019 MARLIN2_17A_RLS1_W19.17.7 | sharkl3_cm4 | 04-28-2019
kernel: 4.4.147+ (20190703)
build number: PPR1 180610.011
android: 9 pie
WIKO/W-V800-EEA/W-V800
9/PPR1.180610.011/08018
unrooted > MTK-su and several oneroot options not working (although they might on oreo if I can find the factory rom)
OEM unlocking enabled in developer options
In fastboot you get:
fastboot flashing unlock > FAILED (remote: Not implemet.)
fastboot oem unlock > FAILED (remote: unknown cmd.)
fastboot oem get_unlock_data > FAILED (remote: unknown cmd.)
fastboot flashing unlock_critical > FAILED (remote: Not implement.)
I tried following this process: (from here (Mod Edit: Link removed)
./fastboot oem get_identifier_token
./signidentifier_unlockbootloader.sh XXXXXXXXXXXXXXX rsa4096_vbmeta.pem signature.bin
./fastboot flashing unlock_bootloader signature.bin
last command returns with: "downloading 'unlock_message'...
OKAY [ 0.001s]
unlocking bootloader...
FAILED (remote: Unlock bootloader fail.)
finished. total time: 0.104s"
additional questions:
Can I just flash a certain recovery somehow?
Do I have to try something complicated like this: (Mod Edit: Link removed)
Have you got root on your view 3 lite?
go0 said:
In fastboot you get:
fastboot flashing unlock > FAILED (remote: Not implemet.)
fastboot oem unlock > FAILED (remote: unknown cmd.)
fastboot oem get_unlock_data > FAILED (remote: unknown cmd.)
fastboot flashing unlock_critical > FAILED (remote: Not implement.)
Click to expand...
Click to collapse
Indicates the FastBoot implemented in device's bootloader doesn't support these subcommands. Obviously OEM/Carrier doesn't want that device's bootloader gets unlocked.
anonym6x6 said:
Have you got root on your view 3 lite?
Click to expand...
Click to collapse
If oreo exists for this and you know where to get it, let me know and I'll try.
If I can get root, what would you recommend trying to unlock bootloader?
jwoegerbauer said:
Indicates the FastBoot implemented in device's bootloader doesn't support these subcommands. Obviously OEM/Carrier doesn't want that device's bootloader gets unlocked.
Click to expand...
Click to collapse
OK...