Hi,
I broke the screen of my Xperia Go completely. My problem is that I have some very important pictures on my phone, which I would like to back up.
Unfortunately I did not activate usb-debugging before, so pulling the files with adb will not work.
I managed to unlock the bootloader over command-line and booting the phone into fastboot mode.
I read somewhere that you can boot a recovery image(with adb enabled) in fastboot mode and connect to your device this way.
Unfortunately this did not work out for me. After I load clockworkmod recovery into the bootloader I'm not able to connect via adb.
The output is:
Code:
./fastboot boot ~/Downloads/recovery-clockwork-6.0.4.5-u8951-R3.img
downloading 'boot.img'...
(bootloader) USB download speed was 17900kB/s
OKAY [ 0.467s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.022s]
finished. total time: 0.489s
After this
Code:
./adb devices
returns an empty list. I also tried
Code:
./fastboot reboot
and
Code:
./fastboot reboot-bootloader
after that, but both commands get stuck.
Any ideas what I am doing wrong?
are you positive that the screen doesnt work at all? you could try to navigate the menus "blind" and enable debugging?
Hi all
i have asus memo pad fd10, model: me302KL with soft bricked problem ( stuck at fastboot mode and show ERROR: invalid boot image )
i try to flash with fastboot flash recovery from image files but failed..
below are the message:
fastboot flash recovery recovery.img
sending 'recovery' (6002 KB)...
OKAY [ 0.188s]
writing 'recovery'...
FAILED (remote: Invalid input Image. Cannot flash before unlock)
finished. total time: 0.219s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.188s]
booting...
FAILED (remote: Bootloader is locked)
finished. total time: 0.203s
i think bootloader is locked. How to unlock boot loader? i don't have any os to install apk and unlock/root the me302kl.
i try
fastboot oem unlock
FAILED (remote: unknown command)
What should i do now? Please help and provide me any advice.
Many thanks !!
please help
try fastboot oem unlock-go. On fastboot help:
flashing unlock_critical (this enables flashing bootloader-related partitions)
flashing unlock (this enables flashing except bootloader-related partitions)
fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: -0.000s
Any method to unlock the bootloader in fastboot mode?
Any one know how to save my soft bricked pad me302kl??
thanks!
I have the same problem, please help!
push
I have the same issue. Bad flash wiped out the partition table so i cant fastboot flash the oem zip.
push
push
push
no one know how to save my pad T_T
up ...
up ...
Same here
I guess all the unlock info is here:
http://dlcdnet.asus.com/pub/ASUS/Ee...73.649178616.1498070896-1875799990.1498070896
but this is an apk and we need a fastboot method to do it.
Can any1 help!
Thanks!
can you boot your device normally? you need to allow OEM unlocking under developer options before using the code.
Me too, I have the same problem, please help us!
KF HDX only boots into fastboot, I'm trying to install TWRP Recovery, then hopefully after an image
fastboot -i 0x1949 flash recovery thor-twrp-3.0.0-0.img
target reported max download size of 536870912 bytes
sending 'recovery' (9294 KB)...
OKAY [ 0.391s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.442s
fastboot -i 0x1949 oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
./fastboot -i 0x1949 oem idme
...
FAILED (remote: oem idme not allowed for locked hw)
finished. total time: 0.055s
I get ADB for a few seconds before it goes into fastboot
[email protected]:/ $ cat /sys/block/mmcblk0/device/manfid
0x000015
[email protected]:/ $ cat /sys/block/mmcblk0/device/serial
0x8c0f5453
I'v created the unlock file
fastboot -i 0x1949 flash unlock unlock.signed
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.090s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct) **** I've checked this several times
finished. total time: 0.153s
Is it terminal?
Do you follow the steps of this thread correctly?
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
I had the same issue some time ago, in my case the problem was some strange windows 10 compatibility which block /denied flash the code.
I repeat the process on my old windows Vista desktop ,without errors, dont ask why changed between systems, but works for me.
Check the drivers are installed correctly, aboot and twrp files
Remeber first get the unlock code, second use adb to send TWRP and Aboot files to the Kindle, and finally proceed flash unlock code.
RealSlimShady72 said:
KF HDX only boots into fastboot, I'm trying to install TWRP Recovery, then hopefully after an image
fastboot -i 0x1949 flash recovery thor-twrp-3.0.0-0.img
target reported max download size of 536870912 bytes
sending 'recovery' (9294 KB)...
OKAY [ 0.391s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.442s
fastboot -i 0x1949 oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
./fastboot -i 0x1949 oem idme
...
FAILED (remote: oem idme not allowed for locked hw)
finished. total time: 0.055s
I get ADB for a few seconds before it goes into fastboot
[email protected]:/ $ cat /sys/block/mmcblk0/device/manfid
0x000015
[email protected]:/ $ cat /sys/block/mmcblk0/device/serial
0x8c0f5453
I'v created the unlock file
fastboot -i 0x1949 flash unlock unlock.signed
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.090s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct) **** I've checked this several times
finished. total time: 0.153s
Is it terminal?
Click to expand...
Click to collapse
How did the device get into this state?
Did you install the vulnerable aboot before attempting to flash TWRP? If not the installation will fail. Nor can a non-vulnerable bootloader be unlocked.
If you can not establish a stable adb (not fastboot) session you will need to force the device into 'bulk mode' and then attempt to install the vulnerable bootloader.
Yousucks2 said:
Do you follow the steps of this thread correctly?
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
I had the same issue some time ago, in my case the problem was some strange windows 10 compatibility which block /denied flash the code.
I repeat the process on my old windows Vista desktop ,without errors, dont ask why changed between systems, but works for me.
Check the drivers are installed correctly, aboot and twrp files
Remeber first get the unlock code, second use adb to send TWRP and Aboot files to the Kindle, and finally proceed flash unlock code.
Click to expand...
Click to collapse
Davey126 said:
How did the device get into this state?
Did you install the vulnerable aboot before attempting to flash TWRP? If not the installation will fail. Nor can a non-vulnerable bootloader be unlocked.
If you can not establish a stable adb (not fastboot) session you will need to force the device into 'bulk mode' and then attempt to install the vulnerable bootloader.
Click to expand...
Click to collapse
KF was working okay with Nexus 4.4.4 and TWRP I think was 2.7.x, my goal was to install a later Andriod OS. I had an issue with the KF where I only have one USB cable in the house that charges the tablet, the port on the tablet is not the best and if the cable moves slightly I lose the connection. KF was originally unlocked and via fastboot I was flashing TWRP 3.0 to the KF when the cable moved and lost connection, after that I get 'FAILED (remote: flashing not allowed for locked hw)' error when trying to reflash now
adb I get about 20 seconds before the KF continues to fastboot - I don't no how to halt from going to fastboot
From Windows 10 I can use adb but when the KF goes to fastboot I get a triangle on the device file (Windows Device Manager), fastboot does not see the device - I've also installed the KF drivers
OS X I can see the device from both adb and fastboot
Think its terminal now, only going into fastboot.....no more adb
RealSlimShady72 said:
KF was working okay with Nexus 4.4.4 and TWRP I think was 2.7.x, my goal was to install a later Andriod OS. I had an issue with the KF where I only have one USB cable in the house that charges the tablet, the port on the tablet is not the best and if the cable moves slightly I lose the connection. KF was originally unlocked and via fastboot I was flashing TWRP 3.0 to the KF when the cable moved and lost connection, after that I get 'FAILED (remote: flashing not allowed for locked hw)' error when trying to reflash now
adb I get about 20 seconds before the KF continues to fastboot - I don't no how to halt from going to fastboot
From Windows 10 I can use adb but when the KF goes to fastboot I get a triangle on the device file (Windows Device Manager), fastboot does not see the device - I've also installed the KF drivers
OS X I can see the device from both adb and fastboot
Click to expand...
Click to collapse
RealSlimShady72 said:
Think its terminal now, only going into fastboot.....no more adb
Click to expand...
Click to collapse
Too many variables in play (bad port, questionable cable, uncertain damage to bootloader and/or recovery, unreliable operation in current state). You need to address hardware issues before pursuing the sensitive business of attempting to rebuild your device which most likely will involve a trip through 'bulk mode'.
Davey126 said:
Too many variables in play (bad port, questionable cable, uncertain damage to bootloader and/or recovery, unreliable operation in current state). You need to address hardware issues before pursuing the sensitive business of attempting to rebuild your device which most likely will involve a trip through 'bulk mode'.
Click to expand...
Click to collapse
Properly not worth spending much more time now, been a bit of a learning curve though.
Cheeky call to Amazon and asked if they do repairs - NO but have 15% off:cyclops: another Kindle Fire Purchase so I got the $49.99 HD 8- 15%
RealSlimShady72 said:
Properly not worth spending much more time now, been a bit of a learning curve though.
Cheeky call to Amazon and asked if they do repairs - NO but have 15% off:cyclops: another Kindle Fire Purchase so I got the $49.99 HD 8- 15%
Click to expand...
Click to collapse
Nice score
Some real good progress thanks to Draxie ISO :good:. I've now got a recovery TWRP 3.1.1-1
Also now my unlock code worked!!
./fastboot -i 0x1949 flash unlock unlock.signed
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.085s]
writing 'unlock'...
OKAY [ 0.079s]
finished. total time: 0.164s
NO adb though
./adb devices
List of devices attached
D06FA0A0352200A9 unauthorized
EDIT:Tried for a couple of hours now and can't push an image to the KF HDX, there is no OS on the device and even in recovery I've tried to sideload adb but still can't push an image
Also tried to mount data to my Win 10 Pro PC but here now I'm getting a yellow triangle on MTP device.
Is there an system image for KF HDX Thor to installed via fastboot?
We have a fully working KF HDX :cyclops:
Followed the guide here to get MTP device drivers working
https://forum.xda-developers.com/showthread.php?t=2612503&nocache=1
copy over an image and off we go:laugh:
RealSlimShady72 said:
Some real good progress thanks to Draxie ISO :good:. I've now got a recovery TWRP 3.1.1-1
Also now my unlock code worked!!
:
EDIT:Tried for a couple of hours now and can't push an image to the KF HDX, there is no OS on the device and even in recovery I've tried to sideload adb but still can't push an image
Also tried to mount data to my Win 10 Pro PC but here now I'm getting a yellow triangle on MTP device.
Is there an system image for KF HDX Thor to installed via fastboot?
Click to expand...
Click to collapse
RealSlimShady72 said:
We have a fully working KF HDX :cyclops:
Followed the guide here to get MTP device drivers working
https://forum.xda-developers.com/showthread.php?t=2612503&nocache=1
copy over an image and off we go:laugh:
Click to expand...
Click to collapse
Well done - especially notable given the various obstacles that you faced. Demonstrates difficult device recoveries are possible with sufficient time, talent and research (occasionally a dab of luck). Enjoy your rejuvenated HDX!
Davey126 said:
Well done - especially notable given the various obstacles that you faced. Demonstrates difficult device recoveries are possible with sufficient time, talent and research (occasionally a dab of luck). Enjoy your rejuvenated HDX!
Click to expand...
Click to collapse
Lucky for me I had Win 10 and OS X
Windows was good for ADB and mounting the device with MTP but could not get fastboot working with Windows
OSX was good for ADB, fastboot and @draxie 1-click but fastboot was very limited as everything I threw at resulted in a 'FAILED (remote: flashing not allowed for locked hw)'
Be interesting to know which part off 1-click unlocked and pushed over the recovery.
Today I have a Gen 7 HD8 arriving, wonder how long that will take to break
adb sideload
RealSlimShady72 said:
EDIT:Tried for a couple of hours now and can't push an image to the KF HDX, there is no OS on the device and even in recovery I've tried to sideload adb but still can't push an image
Click to expand...
Click to collapse
I know it doesn't really matter anymore,
but I still wonder if it's only me that reads
too much into a hasty comment or were
you actually trying 'adb push' instead of
'adb sideload' to get your ROM over to
TWRP waiting to sideload? The reason
I'm asking is that had used adb sideload
numerous times (I even double-checked
when you were asking) and sideload had
always worked as expected...
draxie said:
I know it doesn't really matter anymore,
but I still wonder if it's only me that reads
too much into a hasty comment or were
you actually trying 'adb push' instead of
'adb sideload' to get your ROM over to
TWRP waiting to sideload? The reason
I'm asking is that had used adb sideload
numerous times (I even double-checked
when you were asking) and sideload had
always worked as expected...
Click to expand...
Click to collapse
Okay you've cleared this one up, I'm not familiar with adb or fastboot.....I tried to take in too much last few days
At no point did I try 'adb sideload' - I didn't even know that was an option but you've cleared that one up for me, I only ever used adb push even when I put the device into adb sideload via TWRP.
So my mistake as I overlooked the sideload option on the CLI
RealSlimShady72 said:
Lucky for me I had Win 10 and OS X
Windows was good for ADB and mounting the device with MTP but could not get fastboot working with Windows
OSX was good for ADB, fastboot and @draxie 1-click but fastboot was very limited as everything I threw at resulted in a 'FAILED (remote: flashing not allowed for locked hw)'
Be interesting to know which part off 1-click unlocked and pushed over the recovery.
Today I have a Gen 7 HD8 arriving, wonder how long that will take to break
Click to expand...
Click to collapse
Thanks for feedback. For others benefit there's a Windows driver package referenced in the another thread (here) that has proven reliable for HDX fastboot access on multiple Windows instances...mine and everyone else who has reported back. Just works despite being targeted for a different device. Call me crazy but I like things that are easy, work and carry no side effects. Kinda radical ...
Good day: I have a similar issue with showing
PS C:\Users\learned\Downloads\KindleFire\unlock> fastboot -i 0x1949 flash unlock unlock.code
target reported max download size of 1073741824 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.078s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.141s
My ADB and fastboot are working well and the Apollo HDX tablet is working fine.
You mentioned flashing aboot before trwp, etc. prior to unlocking. I thought the posts indicated that neither root nor twrp was required to unlock the boot loader?
I created an unlock code for both Thor and Apollo and, both were created successfully. Thor has root and recovery and Apollo has not been altered at all. Trying to run to flash the respective unlock code to both Thor and Apollo fails showing me "FAILED (remote: Unlock code is NOT correct)"
Why would the unlock code be incorrect?
When I created the unlock code for Apollo moments ago, I received two codes at the powershell prompt.
1664 KB/s (506072 bytes in 0.296s)
0x000015 0xfc155609
0 KB/s (256 bytes in 1.000s)
Press any key to continue . .
I presume the two hex codes I received should be correct? Can I manually push the two unlock codes to the tablet aside from the unlock.bat file? I am not sure what is in the unlock.code file created by the get_code.bat file.
galearned said:
You mentioned flashing aboot before trwp, etc. prior to unlocking. I thought the posts indicated that neither root nor twrp was required to unlock the boot loader?
Click to expand...
Click to collapse
A 'vulnerable' aboot must be flashed prior to installing TWRP and/or unlocking the bootloader. You can only flash aboot if: 1) root is available; or 2) the device is placed in 'bulk mode'. Both approaches have their pros/cons.
Please consult the first post in this lengthy thread for an overview of the process then skip to a post near the end by @ReichMann for a nice compilation of files and associated procedures. Note this is only one of several ways to get the job done.
Update to Unlock Code Incorrect
galearned said:
Good day: I have a similar issue with showing
PS C:\Users\learned\Downloads\KindleFire\unlock> fastboot -i 0x1949 flash unlock unlock.code
target reported max download size of 1073741824 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.078s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.141s
My ADB and fastboot are working well and the Apollo HDX tablet is working fine.
You mentioned flashing aboot before trwp, etc. prior to unlocking. I thought the posts indicated that neither root nor twrp was required to unlock the boot loader?
I created an unlock code for both Thor and Apollo and, both were created successfully. Thor has root and recovery and Apollo has not been altered at all. Trying to run to flash the respective unlock code to both Thor and Apollo fails showing me "FAILED (remote: Unlock code is NOT correct)"
Why would the unlock code be incorrect?
When I created the unlock code for Apollo moments ago, I received two codes at the powershell prompt.
1664 KB/s (506072 bytes in 0.296s)
0x000015 0xfc155609
0 KB/s (256 bytes in 1.000s)
Press any key to continue . .
I presume the two hex codes I received should be correct? Can I manually push the two unlock codes to the tablet aside from the unlock.bat file? I am not sure what is in the unlock.code file created by the get_code.bat file.
Click to expand...
Click to collapse
Update: After reading various opinions on whether you need aboot to write the unlock code including one post stating clearly that the OP step 1 and 3 were independent of step 2 (aboot and twrp), I finally installed aboot and cubed twrp. Suddenly, after issuing adb reboot (which booted the tablet into fastboot as predicted), I was then able to issue the unlock command (fastboot flash -i 0x1949 unlock unlock.code) with success so it seems the vulnerable aboot is required to unlock. Now I have a final question about the fact that with the special aboot and twrp, the tablet will boot only into fastboot which is fine for flashing a custom ROM.
While I am going to now find a good stable customer ROM to flash, what does it take to keep the stock OS booting and, maintain the unlocked bootloader? If the user wanted to stay on the stock OS either for a short while or long term, what steps are needed? Flash a more traditional TWRP?
galearned said:
Update: After reading various opinions on whether you need aboot to write the unlock code including one post stating clearly that the OP step 1 and 3 were independent of step 2 (aboot and twrp), I finally installed aboot and cubed twrp. Suddenly, after issuing adb reboot (which booted the tablet into fastboot as predicted), I was then able to issue the unlock command (fastboot flash -i 0x1949 unlock unlock.code) with success so it seems the vulnerable aboot is required to unlock. Now I have a final question about the fact that with the special aboot and twrp, the tablet will boot only into fastboot which is fine for flashing a custom ROM.
While I am going to now find a good stable customer ROM to flash, what does it take to keep the stock OS booting and, maintain the unlocked bootloader? If the user wanted to stay on the stock OS either for a short while or long term, what steps are needed? Flash a more traditional TWRP?
Click to expand...
Click to collapse
This may sound a bit snarky; sometimes brevity is better:
- there are opinions and there are facts; sometimes they align, sometimes they don't
- fact: a vulnerable (ie: exploitable) bootloader (aboot) is required to apply the unlocking methods discussed in this forum
- fact: a stock device running a natively obtained version of FireOS > 3.2.3.2 does not have an aboot with an known vulnerability that can be leveraged by the signature forging exploit (hence the reason it must be replaced with an older vulnerable version)
- fact: steps #1 & #3 are independent of step #2 which can be performed first but is a prerequisite for step #3 if the stock aboot is not vulnerable
For all practice purposes you're done with FireOS after unlocking the bootloader. Enjoy the wide selection of custom ROMs for this device. FireOS can be reinstated with some work; has nothing to do with the version of TWRP.
Amazon Fire 5th generation Need bootloader unlocl
Fire OS 5.3.6.4
Need Bootloader unlock
And
Fastboot mode cmd is " the command you input is restricted on locked hw " problem
Please Replay ?
Hello there,
A newbie here, trying to unlock a TCL 20B (6159K) phone.
Android 11, November 2021 security patch (MTK Easy Su doesn't work with that, reportedly some vulnerability was patched), fastboot accessible but acting weird.
1. Got fastboot from here.
For some reason it doesn't understand the -i option, but connects with the only phone I'm trying to unlock attached anyway.
VID is 0x0e8d, btw.
2. Got adb from don't remember where about a year ago (for my previous Lenovo phone)
3. Unlocked the Developer Options
4. Checked "Allow bootloader unlock" and "Enable USB debugging" options there (not sure how those are named exactly in English, but I 100% guarantee, I've checked the right ones)
5. Sent phone into fastboot with
Code:
adb boot bootloader
6. Checked the unlockability with
Bash:
fastboot flashing get_unlock_ability
(bootloader) unlock_ability = 16777216
OKAY [ 0.005s]
Finished. Total time: 0.006s
7. Tried to unlock the thing, but
Code:
fastboot flashing unlock
FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
and
Code:
fastboot flashing unlock_critical
FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
8. Searching here, on XDA forums revealed there's no TCL 20B sub-form.
9. While there are tons of topics on not allowed in locked state, none of those helps.
fastboot oem unlock is seemingly an old way to do things (TCL 20B is a rather new device released WAY past 2015)
TCL is an Alcatel device, not a Xiaomi or some ZUK one, to require an account (haven't found anthing on "alcatel account")
trying to load some recovery from PC that might work failed as well (for the same reason)
Code:
[/LIST]
./fastboot boot twrp-3.6.1.img
Sending 'boot.img' (8932 KB) OKAY [ 0.212s]
Booting FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
I've read some TCL 10 phones don't even have a fastboot, but TCL 20B clearly does.
Any Ideas how to unlock the bootloader?
P.S. Maybe a new sub forum for 20B? This got placed into the "TCL 20 5G" one, which doesn't seem right.
EDIT:
Ok, have found how to proceed on my own.
Even rooted the thing.
Go here https://github.com/bkerler/mtkclient, grab the ISO, backup, install patched magisk, patch the boot_a, flash patched boot_a and empty vbmeta_a, erase metadata, userdata and md_udc. Reboot, reinstall pathched magisk.
Don't lock the bootloader to avoid red state.
Huge kudos to mtkclient devs
Hello, i been trying to root my tcl 20b (6159a) but i cant figure how, i follow the instructions of mtkclient. Install it in windows, python, mtk repository, all the process, but when i try to replace boot_a.img it doesnt work from the cmd command, but in the python mtk_gui i can replace boot_a.bin and erase vbmeta_a.bin when i do it from there the cellphone keep in bootloop, i can fix the bootloop but cant root it. If u read this, can you plz be more specific with the steps, and made a little tutorial, its not necessary images or video just some more in deep info how you achieve root, thx
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.