Develop Bugs

Fire TV v1 stuck on white logo

Hi,
I was following the guide to install Rbox's boot menu from aftvnews. I had done it on my other aftv fine. The bootloader on the aftv was unlocked, but when I rebooted the aftv just sat at the white Amazon screen. The last few commands are below.
255|[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/syste
m/boot/boot.img
_sdcc.1/by-name/boot of=/system/boot/boot.img <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.884 secs (11861719 bytes/sec)
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ # dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by
-name/boot
dev/block/platform/msm_sdcc.1/by-name/boot <
13164+0 records in
13164+0 records out
6739968 bytes transferred in 1.289 secs (5228834 bytes/sec)
[email protected]:/ # reboot
I tried hooking up a keyboard, but the alt i prtscn doesn't seem to work. I tried fastboot, but it doesn't look good. I haven't come across what tampered true, unlocked false means. As you can see from above though I had root, so that should have meant the bootloader was unlocked. Any help would be appreciated. I have done a fair bit of looking and it seems unless I want to take up soldering I am probably out of luck.
Thanks in advance!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
OKAY [ -0.000s]
finished. total time: -0.000s

Sox35 said:
Hi,
I was following the guide to install Rbox's boot menu from aftvnews. I had done it on my other aftv fine. The bootloader on the aftv was unlocked, but when I rebooted the aftv just sat at the white Amazon screen. The last few commands are below.
255|[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/syste
m/boot/boot.img
_sdcc.1/by-name/boot of=/system/boot/boot.img <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.884 secs (11861719 bytes/sec)
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ # dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by
-name/boot
dev/block/platform/msm_sdcc.1/by-name/boot <
13164+0 records in
13164+0 records out
6739968 bytes transferred in 1.289 secs (5228834 bytes/sec)
[email protected]:/ # reboot
I tried hooking up a keyboard, but the alt i prtscn doesn't seem to work. I tried fastboot, but it doesn't look good. I haven't come across what tampered true, unlocked false means. As you can see from above though I had root, so that should have meant the bootloader was unlocked. Any help would be appreciated. I have done a fair bit of looking and it seems unless I want to take up soldering I am probably out of luck.
Thanks in advance!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
OKAY [ -0.000s]
finished. total time: -0.000s
Click to expand...
Click to collapse
Having root does not mean the bootloader is unlocked. Can you run:
Code:
fastboot boot recovery.img

rbox said:
Having root does not mean the bootloader is unlocked. Can you run:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Sorry, I was going by the guide of aftvnews that says if you have root it is unlocked. I ran the command, but I am guessing it is not good news.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
FAILED (remote: boot not allowed for locked hw)
finished. total time: 0.296s

Sox35 said:
Sorry, I was going by the guide of aftvnews that says if you have root it is unlocked. I ran the command, but I am guessing it is not good news.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
FAILED (remote: boot not allowed for locked hw)
finished. total time: 0.296s
Click to expand...
Click to collapse
You didn't follow all the instructions properly, and it is bricked now. I wrote instructions in a post somewhere on how to unlock with fastboot. I don't know where it is though. You could try searching my posts. @AFTVnews.com might know where it is.

rbox said:
You didn't follow all the instructions properly, and it is bricked now. I wrote instructions in a post somewhere on how to unlock with fastboot. I don't know where it is though. You could try searching my posts. @AFTVnews.com might know where it is.
Click to expand...
Click to collapse
Do I need to generate an unlock file using the output from the commands below? I am not able to find it again right now, but I believe you mentioned something about not using the 1949 part of the command. I don't have a Linux machine. Is there anyone that has the script installed already? If not I can hopefully find someone at work that has one. I just want to make sure I am using the correct commands. I am not sure if I can make the AFTV worse that it is now, but you never know!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem emmc-info
(bootloader) 0x154f04bad7
7090030242070BNB fastboot
//github.com/dpeddi/Cuber
./cuber_unlockbl --sign ./unlock.img ./unlock.signed
connect the hdx to a linux box and do following command:
./fastboot -i 0x1949 devices
./fastboot -i 0x1949 flash unlock unlock.signed
./fastboot -i 0x1949 reboot

Sox35 said:
Do I need to generate an unlock file using the output from the commands below? I am not able to find it again right now, but I believe you mentioned something about not using the 1949 part of the command. I don't have a Linux machine. Is there anyone that has the script installed already? If not I can hopefully find someone at work that has one. I just want to make sure I am using the correct commands. I am not sure if I can make the AFTV worse that it is now, but you never know!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem emmc-info
(bootloader) 0x154f04bad7
7090030242070BNB fastboot
//github.com/dpeddi/Cuber
./cuber_unlockbl --sign ./unlock.img ./unlock.signed
connect the hdx to a linux box and do following command:
./fastboot -i 0x1949 devices
./fastboot -i 0x1949 flash unlock unlock.signed
./fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Yeah, Cuber. That's it. And yes, you dont need the -i. http://forum.xda-developers.com/showpost.php?p=61812290&postcount=213 That has some instructions for doing it on Windows.

rbox said:
Yeah, Cuber. That's it. And yes, you dont need the -i. http://forum.xda-developers.com/showpost.php?p=61812290&postcount=213 That has some instructions for doing it on Windows.
Click to expand...
Click to collapse
Thank so much for the Windows link. The instructions on the couple different posts all mention the argument being 0xmmsssssss, but I am getting the following. I have to assume that isn't going to work without using the emmc-info.
C:\Python27>python.exe cuberHDX.py 0xd77090030242070BNB
Usage: cuberHDX.py [boot.img|serial]

Sox35 said:
Thank so much for the Windows link. The instructions on the couple different posts all mention the argument being 0xmmsssssss, but I am getting the following. I have to assume that isn't going to work without using the emmc-info.
C:\Python27>python.exe cuberHDX.py 0xd77090030242070BNB
Usage: cuberHDX.py [boot.img|serial]
Click to expand...
Click to collapse
Your ID is from the previous line:
(bootloader) 0x154f04bad7

help me to flash twrp

this is happening i did all step by steps but whole day i tried many drivers and ways to make it flash but nothing.Please help
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
adb server version (22) doesn't match this client (35); killing...
* daemon started successfully *
LGH815ba365ed2 device
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
< waiting for any device >

iko84 said:
this is happening i did all step by steps but whole day i tried many drivers and ways to make it flash but nothing.Please help
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
adb server version (22) doesn't match this client (35); killing...
* daemon started successfully *
LGH815ba365ed2 device
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
< waiting for any device >
Click to expand...
Click to collapse
Again a windows driver problem? You should better switch to Linux.
For the moment:
Download Ubuntu install it on a stick and boot it.
Install adb tools and fastboot there and no driver issues anymore!
There are many guides how to make that. Search by google to find them.
And you said you read everything: but you missed the official guide. Read the installation steps from the official twrp thread (see my sig) --> fastboot flash will not work!
.

Zenfone 2 ze550kl only fastboot mode

hi all ,
i have a zenfone 2 laser exactly ze550kl , i don't know how was done on it .
everything i done it appear only fastboot mode...fastboot device find the device and adb device not find it
I've tryied a lot of guide but nothing..so i want to start again
If someone can and want follow me to resolve please answer
(fastboot getvar all is empty)
sorry for my bad english , i'm italian :angel:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
G1AZCY06E666 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.859s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.859s

No valid OS and can not connect to adb, briked??

So I was stupidly trying to relock bootloader, and somehow I ended up hardly bricked
Please tell me If I can do anything...The problem is:
Cant find valid operating system
The device will not start
Click to expand...
Click to collapse
I can get into fastboot, but when connect to PC, it recognizes some device, but is not working properly, adb is not finding the device
Not problem of the drivers or the cable, because I have managed to connect to adb before, and also trying right now with other phone. Adb recognizes as soon as I enable USB debugging
Thank you

When you say 'adb', do you mean you're trying to use the command 'adb' when you're in fastboot? At the risk of stating the obvious, you need to use 'fastboot' command when you're in fastboot mode. 'adb' is only used when you're in recovery or in the actual android system. Otherwise you may wish to try a different fastboot version (sometimes that matters).

Javi22 said:
So I was stupidly trying to relock bootloader, and somehow I ended up hardly bricked
Please tell me If I can do anything...The problem is:
I can get into fastboot, but when connect to PC, it recognizes some device, but is not working properly, adb is not finding the device
Not problem of the drivers or the cable, because I have managed to connect to adb before, and also trying right now with other phone. Adb recognizes as soon as I enable USB debugging
Thank you
Click to expand...
Click to collapse
TOOL_ALL_IN_ONE_1.1.1.3.zip it's the solution,Block again from here and you can start over

Ok thank you for the answers. I missconfused about adb and fastboot. So yes, fastboot is working. But If I try to unlock bootloader in order to flash the image, it is not working. I tried these 2 commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
711KPDT0682490 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.013s
So my problem now is to unlock the bootloader

Javi22 said:
Ok thank you for the answers. I missconfused about adb and fastboot. So yes, fastboot is working. But If I try to unlock bootloader in order to flash the image, it is not working. I tried these 2 commands:
So my problem now is to unlock the bootloader
Click to expand...
Click to collapse
Get rid of minimal adb, and use the most recent platform-tools version 28.0.3 :good:

Badger50 said:
Get rid of minimal adb, and use the most recent platform-tools version 28.0.3 :good:
Click to expand...
Click to collapse
Thank you! But still the same...:
Code:
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot devices
711KPDT0682490 fastboot
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot flashing unlock_critical
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>

Javi22 said:
Thank you! But still the same...:
Click to expand...
Click to collapse
Then either you have a Verizon variant phone, and/or USB debugging and OEM unlocking is not enabled in developer options.

Badger50 said:
Then either you have a Verizon variant phone, and/or USB debugging and OEM unlocking is not enabled in developer options.
Click to expand...
Click to collapse
But there is no system installed, I erased by accident...:S
Any clue what I can try?
Gesendet von meinem Pixel 3 mit Tapatalk

Javi22 said:
But there is no system installed, I erased by accident...:S
Any clue what I can try?
Gesendet von meinem Pixel 3 mit Tapatalk
Click to expand...
Click to collapse
Try side loading the OTA through stock recovery.
https://developers.google.com/android/ota

Badger50 said:
Try side loading the OTA through stock recovery.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
Thanks but I can not get into recovery, the same screen:

Javi22 said:
Thanks but I can not get into recovery, the same screen:
Click to expand...
Click to collapse
Can you get into fastboot mode? If so you can then run deuces bootloop tool.
https://www.google.com/url?sa=t&sou...AxAB&usg=AOvVaw02czE3zeVK5sKbCe6V9L2v&ampcf=1

Moto Z2 Force: Can´t boot into TWRP from fastboot mode

Hey, I wanted to install TWRP recovery on my Moto Z2 Force. I wanted to boot into twrp.img which I have in the Minimal ADB & Fastboot. But always if I run the "fastboot boot twrp.img" it fails and I don´t know why. On my friends PC it always works (when I installed Custom ROMS or rooted my phone and stuff like this) but on mine it doesn´t. Can someone tell me, why I can´t use fastboot commands with my cmputer? I´ve reinstalled all the USB drivers, the Minimal ADB & Fastboot app or whatever it´s called.
Btw, this is, how my CMD looks like after I´ve put in the command:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY224ZCKZN fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I´ve spent hours to find out what the problem is but I just cant figure it out. Does anyone have some ideas, what I should do?
Aaron

Off the top I'd say that unless you've renamed your twrp.img to "twrp.img" and it resides in your Minimal ADB folder then it just doesn't have the correct path or filename.
Try
PHP:
fastboot boot 'Drag n Drop twrp.img here'