Hi guys
I really need your help!
Just unlocked my new z4 tablet and flushed a new kernel.
The short version, I've flushed androplus kernel v10 and rebooted the tab and completed the android wizard.
And the stupid thing is, I've forgot to activate usb debugging and rebooted the tab.
And now I have a black screen. The tablet doesn't show anything on the display.
After turn on it just vibrates shortly, but the screen is black.
The only thing I can do ist start fastboot, but since I did not enabled usb debugging I can't do anything, like reflush:
HTML:
C:\adb>fastboot flash boot boot.img
sending 'boot' (31948 KB)...
OKAY [ 1.239s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 1.256s
I'm pretty sure it is this stupid sony my xperia protection, I was so stupid to turn on "locate my device" or whatever.
(Before the fastboot oem unlock, I had to disable this thing in the android settings. If it was activated I got command not allowed from fastboot)
I have a black screen, usb debugging disabled and this stupid xperia protection is enabled, what can I do?
Please help
Thanks a lot!
Awesome, was able to fix it myself. With great help from this forum (Other older posts).
If anyone got the same problem, don't worry if fastboot doesn't work anymore.
You would be able to flush a new firmware (stock.)
1. Get latest version of flashtool
2. Download a firmware for your Device (Xperifirm)
3. Flush firmware in flashmode (Connect your device in flashmode, not fastboot)
4. Finish, your device will boot again!:laugh::laugh::laugh::laugh::
A couple of days ago, I got an error on my phone (Motorola XT1033) saying that it cannot load the home screen. So, I restarted it in order to resolve the issue. However, it didn't reboot and since then it has been stuck in the Motorola logo.
I tried to do recovery or factory reset, but all the options lead to the same Motorola logo with no luck.
The only option that is working is AP Fastboot. I managed to unlock the bootloader by getting an unlock code from Motorola's website and using the mfastboot command. So I assume that the fastboot command is working since it detects the devices; however, I couldn't make ADB command to work since it give the error: 'device not found'.
Anyway, the second step is to flash the phone. According to this question, I should be able to do that. However, when I am running the command fastboot flash partition gpt.bin, I am getting the following result:
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.154s
I have been searching for days to solve this problem, but nothing yet! I don't know which part I am doing wrong.
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 ?
Hey guys,
I have an European LG G5 H850 with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP once, but I didn't want to install it, but instead keep the stock recovery untouched. So I booted into the bootloader, entered "fastboot boot twrp.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.462s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.482s
I have absolutely no idea what I'm doing wrong. I made sure twrp.img is referring to the correct file, and I tried both the Android SDK platform tools and the 15 seconds ADB installer, but none of them worked. When I try flashing the recovery with "fastboot flash recovery twrp.img", it seems to work because this appears:
target reported max download size of 536870912 bytes
sending 'recovery' (20900 KB)...
OKAY [ 0.471s]
writing 'recovery'...
OKAY [ 0.198s]
finished. total time: 0.670s
But when I try to boot into the bootloader again, it just gives me the option to do a factory reset, nothing else. So I assume that something went wrong. I have absolutely no idea what it could be, so please help me. I also asked on reddit, but didn't get any answers so far. Any help would be greatly appreciated!
Thanks in advance!
JonSchnee777 said:
Hey guys,
I have an European LG G5 H850 with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP once, but I didn't want to install it, but instead keep the stock recovery untouched. So I booted into the bootloader, entered "fastboot boot twrp.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.462s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.482s
I have absolutely no idea what I'm doing wrong. I made sure twrp.img is referring to the correct file, and I tried both the Android SDK platform tools and the 15 seconds ADB installer, but none of them worked. When I try flashing the recovery with "fastboot flash recovery twrp.img", it seems to work because this appears:
target reported max download size of 536870912 bytes
sending 'recovery' (20900 KB)...
OKAY [ 0.471s]
writing 'recovery'...
OKAY [ 0.198s]
finished. total time: 0.670s
But when I try to boot into the bootloader again, it just gives me the option to do a factory reset, nothing else. So I assume that something went wrong. I have absolutely no idea what it could be, so please help me. I also asked on reddit, but didn't get any answers so far. Any help would be greatly appreciated!
Thanks in advance!
Click to expand...
Click to collapse
The "fastboot boot twrp.img" command didn't work for me either, but the keystroke to do a "factory reset" -- which is really a keystroke to enter recovery -- did work. Specifically, I
powered down the LG G5 completely (nothing attached to the USB-C port, or battery pull)
with the power off (preferably via battery pulled), held down the Volume Down and Power/Fingerprint buttons
As soon as the LG logo appeared, released and re-pressed the Power/Fingerprint button, all the while continuing to hold down Volume Down
Held down both while the LG logo showed, releasing them after the white screen appeared asking whether you want to do a full erase. Answer yes (Press and release Volume Down until the Yes is grey, then press Power/Fingerprint button)
It prompts you once again. Answer yes again the same way.
At this point after a few seconds, TWRP starts. It hasn't actually done an erase.
This is important: after fastboot flash recovery twrp.img, you need to pull the battery to power down, and then follow the instructions above to enter TWRP. Do not boot into system with the stock ROM after fastboot. It will replace TWRP with the stock recovery at boot time, and in that scenario, the full erase mentioned above actually does erase data and internal storage.
TWRP will on first start change the system image (once you "allow modification") so that the stock ROM stops replacing it at boot time.
If you did boot up the stock ROM after fastboot, you will need to re-enter fastboot and flash TWRP again (power down with USB-C port clear, hold down Volume Up, insert USB-C cable, fastboot flash recovery twrp.img). Then pull the battery with fastboot still running, then boot into TWRP as above.
Unfortunately most writeups aren't crystal clear about the correct sequence of steps. Most cover some steps and gloss over others.
You aren't doing anything wrong.
LG did not put the typical Fastboot commands into the bootloader.
Fastboot flash does not work either.
You need to follow the other methods available on xda to get TWRP on your device.
Edit: woops. That's only with H830. Follow the instructions in the H850 TWRP thread.
Sent from my LG-H830 using Tapatalk