Database Develop

HELP! stuck in fastboot

Hello everyone,
I was trying to return my htc one, s-on, custom recovery and rom installed...back to complete stock. I have a mac. I tried using the following guide:
http://forum.xda-developers.com/showthread.php?t=2251800
I was able to re-lock the bootloader, but I was unable to flash the RUU as instructed in the post. Kept getting an error in terminal
htconeroot Josh$ ./fastboot-mac flash zip Rom.zip
sending 'zip' (1029700 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Joshuas-MacBook-Pro:htconeroot Josh$ ./fastboot-mac flash zip Rom.zip
ERROR: could not clear input pipe; result -536870163< waiting for device >
./fastboot-mac flash zip Rom.zip
I am now stuck at the fastboot screen. It say tampered, relocked, security warning. I can't get into recovery or anything. It just returns me to this screen.
How can I fix this?
Thanks,
Blue

I was able to re-unlock the bootloader using htc dev...so I have access to my phone again. Still trying to figure out how to return it to stock using a mac, but at least its usable again.
Sorry for the post,
Blue

Help please
BlueGoldAce said:
I was able to re-unlock the bootloader using htc dev...so I have access to my phone again. Still trying to figure out how to return it to stock using a mac, but at least its usable again.
Sorry for the post,
Blue
Click to expand...
Click to collapse
How did you get your phone working again? This is what I've been getting:
./fastboot flash zip RUU2.zip
sending 'zip' (101972 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
Do you know what to do about this?

cowkong said:
How did you get your phone working again? This is what I've been getting:
./fastboot flash zip RUU2.zip
sending 'zip' (101972 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
Do you know what to do about this?
Click to expand...
Click to collapse
I'm guessing your trying to use the 1.29 RUU with 1.31....
Follow this http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app

cowkong said:
How did you get your phone working again? This is what I've been getting:
./fastboot flash zip RUU2.zip
sending 'zip' (101972 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
Do you know what to do about this?
Click to expand...
Click to collapse
Are you running version 1.32? or whatever it is...
The ruu you are trying to push is for version 1.29. As indirect states in the post, you need to the do following:
"fastboot boot recovery and then do this:
adb shell
echo 1.29.00 | dd if=/dev/block/mmcblk0p19 bs=1 skip=160
and then just fastboot oem lock and run the RUU"
Again, I can't take credit for this, its indirect's work, but it works.
You just need to get into recovery, and type in the echo portion of the message while in abd shell. Then get into fastboot and you can push the ruu.
Does that help?
-Blue

BlueGoldAce said:
Are you running version 1.32? or whatever it is...
The ruu you are trying to push is for version 1.29. As indirect states in the post, you need to the do following:
"fastboot boot recovery and then do this:
adb shell
echo 1.29.00 | dd if=/dev/block/mmcblk0p19 bs=1 skip=160
and then just fastboot oem lock and run the RUU"
Again, I can't take credit for this, its indirect's work, but it works.
You just need to get into recovery, and type in the echo portion of the message while in abd shell. Then get into fastboot and you can push the ruu.
Does that help?
-Blue
Click to expand...
Click to collapse
Thanks for the in depth reply. I've tried the flashing the latest RUU.zip file even with the adb commands. I'm still getting this error:
./fastboot flash zip RUUnew.zip
sending 'zip' (1032712 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
I'm having trouble accessing the internal memory. In twrp and cwm recovery, they state that the internal memory is 0MB.

I would pm indirect. He will be of more help than I can.

BlueGoldAce said:
I would pm indirect. He will be of more help than I can.
Click to expand...
Click to collapse
So my question is ...u were able to run the RUU on a mac from indirects thread.. ??
Sent from my HTCONE using xda app-developers app

Actually I did all the adb and fast boot commands with my Mac, and then I ran an ruu using an old windows.
I believe you should be able to do it all via abd and fast boot with you Mac.

BlueGoldAce said:
Actually I did all the adb and fast boot commands with my Mac, and then I ran an ruu using an old windows.
I believe you should be able to do it all via abd and fast boot with you Mac.
Click to expand...
Click to collapse
Not sure I've read that RUU'S are for pc only...but I saw JUS the ONE video available...with a guy running a RUU on mac...??
Sent from my HTCONE using xda app-developers app

I would think pushing the ruu via fastboot, as directed in that thread, should work.,,, but maybe not.
Running an ruu on a Mac requires using wine... Or running windows through parallel desktops.

BlueGoldAce said:
I would think pushing the ruu via fastboot, as directed in that thread, should work.,,, but maybe not.
Running an ruu on a Mac requires using wine... Or running windows through parallel desktops.
Click to expand...
Click to collapse
Yup that's what I thought ... To run a RUU wine would be needed and spoke good timing...lol I'll wait to borrow a pc.:thumbup:
Sent from my HTCONE using xda app-developers app

[SOLVED] Rooting, Custom Recovery on HBOOT 1.55

I just received a new warranty phone from AT&T - I had my old phone S-OFF, unlocked, etc running my ROM of choice. However, the new phone I received today is on HBOOT 1.55. Now, I unlocked the bootloader and have been trying for hours to get root, custom recovery, and S-OFF. I know that Rumrunner can get SOFF for 1.55, but it apparently doesn't work without root. Which I can't figure out how to get without being able to flash a custom recovery. Normally, I could just do that with fastboot, but when I try, I just get a "failed to load" error, which apparently is due to the fact that HBOOT 1.55 doesn't allow the fastboot flash recovery command (and I'm positive file name and command was entered correctly). I've tried toolkit by Hasoon (sp?), and I get an error with that, which I think is just running fastboot commands. Anyway, if you've read this far, I appreciate it, and you probably see my dilemma. Can anyone help, please? So I need to get either root or custom recovery and I can seem to figure out a way to do it.
Thanks

gsxrfl1k6 said:
I just received a new warranty phone from AT&T - I had my old phone S-OFF, unlocked, etc running my ROM of choice. However, the new phone I received today is on HBOOT 1.55. Now, I unlocked the bootloader and have been trying for hours to get root and S-OFF. I know that Rumrunner can get SOFF for 1.55, but it apparently doesn't work without root. Which I can't figure out how to get without being able to flash a custom recovery. Normally, I could just do that with fastboot, but when I try, I just get a "failed to load" error, which apparently is due to the fact that HBOOT 1.55 doesn't allow the fastboot flash recovery command (and I'm positive file name and command was entered correctly). I've tried toolkit by Hasoon (sp?), and I get an error with that, which I think is just running fastboot commands. Anyway, if you've read this far, I appreciate it, and you probably see my dilemma. Can anyone help, please?
Thanks
Click to expand...
Click to collapse
There is a root info guide on the XDA HTC One homepage.

Ktan188 said:
There is a root info guide on the XDA HTC One homepage.
Click to expand...
Click to collapse
I appreciate the reply, but rooting that way requires a custom recovery. Which as I stated above, I'm not able to install so far due to having HBOOT 1.55 and no SOFF to downgrade it. So the more pressing issue is not so much root but installing the custom recovery. I can't use GOO Manager or any of the others because I don't have root and I can't use fastboot because I have HBOOT 1.55

Are you on windows 8.1?

SaHiLzZ said:
Are you on windows 8.1?
Click to expand...
Click to collapse
no,7

Never had such an issue with fastboot

SaHiLzZ said:
Never had such an issue with fastboot
Click to expand...
Click to collapse
Did you try with HBOOT 1.55? I read that the commands for boot and flash recovery don't work

Yes I have. Check your fastboot drivers.

SaHiLzZ said:
Yes I have. Check your fastboot drivers.
Click to expand...
Click to collapse
Gave that a try, updated fastboot and adb, still getting - "target reported max download size of 1526722560 bytes
error: cannot load 'recovery.img': No error"

Try a diffferent computer, usb cable or usb port.

SaHiLzZ said:
Try a diffferent computer, usb cable or usb port.
Click to expand...
Click to collapse
Same result on the ports and cable, haven't tried the different computer yet, though. Although, the bootloader unlock process used fastboot and it worked ok....

flash works but not boot?
Hi guys, I'm a complete noob at his stuff but i managed to get fastboot to flash twrp but it wouldn't boot twrp first so i could do a stock recovery. I think this might be the problem with hboot 1.55 which I'm not stuck with after returning to stock for an OTA update. My lesson learn't. I also had drama flashing anything with twrp 2.6.3.3, but downngrading it to 2.6.3.0 then worked a treat. Good luck :good:

gsxrfl1k6 said:
Gave that a try, updated fastboot and adb, still getting - "target reported max download size of 1526722560 bytes
error: cannot load 'recovery.img': No error"
Click to expand...
Click to collapse
1- to flash custom recovery, you only need an unlocked bootloader, S-off not required
in bootloader/FASTBOOT USB:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
2- "error: cannot load 'recovery.img': No error" -> that just means the filename is wrong, use the correct one, do a "dir" in command prompt and see what it's really called.
EDIT: next time copy/paste the command prompt output, would have saved you some time, when we can see the actual output

nkk71 said:
1- to flash custom recovery, you only need an unlocked bootloader, S-off not required
in bootloader/FASTBOOT USB:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
2- "error: cannot load 'recovery.img': No error" -> that just means the filename is wrong, use the correct one, do a "dir" in command prompt and see what it's really called.
EDIT: next time copy/paste the command prompt output, would have saved you some time, when we can see the actual output
Click to expand...
Click to collapse
If you refer to my op, you'll see that I said fastboot is not working for me - the FIRST thing I did long before I posted my plea for help was to try the commands you wrote. And, as i also stated in the op, the command and file name was entered correctly. Lastly, I did copy and paste the console output, hence the stuff in the quotes. Thanks though.

gsxrfl1k6 said:
If you refer to my op, you'll see that I said fastboot is not working for me - the FIRST thing I did long before I posted my plea for help was to try the commands you wrote. And, as i also stated in the op, the command and file name was entered correctly. Lastly, I did copy and paste the console output, hence the stuff in the quotes. Thanks though.
Click to expand...
Click to collapse
no need to get snappy, anyway here you go, check my command prompt:
Code:
C:\ADB2>dir
Volume in drive C has no label.
Volume Serial Number is 0622-9D4A
Directory of C:\ADB2
25/11/2013 16:57 <DIR> .
25/11/2013 16:57 <DIR> ..
19/08/2012 00:00 846,848 aapt.exe
19/08/2012 00:00 191,488 adb.exe
19/08/2012 00:00 96,256 AdbWinApi.dll
19/08/2012 00:00 60,928 AdbWinUsbApi.dll
20/05/2013 03:03 1,151,546 APKBIT.exe
20/11/2010 21:23 345,088 cmd.exe
19/08/2012 00:00 140,800 fastboot.exe
05/07/2013 21:50 27,446,092 fw_2.24.401.1_custom.zip
03/10/2013 06:56 1,102,709,591 Guru_Reset_M7_2.24.707.1.zip
12/11/2013 16:37 1,252,513 logcat_log.txt
31/03/2012 23:53 186 mainver_fix.bat
19/02/2012 00:24 656,708 misctool
19/02/2012 07:41 4,526 misctool.c
04/10/2013 17:35 0 nandroid.md5
27/10/2013 20:38 10,823,680 openrecovery-twrp-2.6.3.0-m7.img
09/06/2013 13:21 498,167 orig_hboot_1.44.0000_M7_RUUmode.zip
[B][B]14/06/2013 19:01 7,600,128 recovery-clockwork-touch-6.0.3.2-m7--v2.img[/B][/B]
30/09/2013 02:08 8,427,520 recovery-clockwork-touch-6.0.3.8-m7ul.img
05/11/2013 02:29 9,052,160 recovery-clockwork-touch-6.0.4.4-m7ul.img
14/11/2013 07:12 8,955,904 recovery-clockwork-touch-6.0.4.5-m7ul.img
09/06/2013 15:02 648,208 revone
03/11/2013 20:56 249,028 Screenshot_2013-11-03-20-51-36.png
29/02/2008 03:33 5,925,120 stock_boot_img_2.24.401.8.img
05/05/2013 15:04 9,820,416 stock_recovery_1.29.666.17.img
22/08/2013 12:17 8,964,352 stock_recovery_2.24.401.1.img
29/09/2013 21:31 10,584,320 stock_recovery_2.24.401.8.img
24/06/2013 09:09 8,964,352 stock_recovery_2.24.707.1.img
27 File(s) 1,225,415,925 bytes
4 Dir(s) 11,100,098,560 bytes free
C:\ADB2>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[B][COLOR="Blue"]C:\ADB2>fastboot flash recovery recovery.img[/COLOR][/B]
[COLOR="Red"]error: cannot load 'recovery.img'[/COLOR]
C:\ADB2>[B]fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img[/B]
sending 'recovery' (7422 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.841s
C:\ADB2>[B][B]fastboot erase cache[/B][/B]
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\ADB2>[B]fastboot reboot-bootloader[/B]
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB2>

nkk71 said:
no need to get snappy, anyway here you go, check my command prompt:
Code:
C:\ADB2>dir
Volume in drive C has no label.
Volume Serial Number is 0622-9D4A
Directory of C:\ADB2
25/11/2013 16:57 <DIR> .
25/11/2013 16:57 <DIR> ..
19/08/2012 00:00 846,848 aapt.exe
19/08/2012 00:00 191,488 adb.exe
19/08/2012 00:00 96,256 AdbWinApi.dll
19/08/2012 00:00 60,928 AdbWinUsbApi.dll
20/05/2013 03:03 1,151,546 APKBIT.exe
20/11/2010 21:23 345,088 cmd.exe
19/08/2012 00:00 140,800 fastboot.exe
05/07/2013 21:50 27,446,092 fw_2.24.401.1_custom.zip
03/10/2013 06:56 1,102,709,591 Guru_Reset_M7_2.24.707.1.zip
12/11/2013 16:37 1,252,513 logcat_log.txt
31/03/2012 23:53 186 mainver_fix.bat
19/02/2012 00:24 656,708 misctool
19/02/2012 07:41 4,526 misctool.c
04/10/2013 17:35 0 nandroid.md5
27/10/2013 20:38 10,823,680 openrecovery-twrp-2.6.3.0-m7.img
09/06/2013 13:21 498,167 orig_hboot_1.44.0000_M7_RUUmode.zip
[B][B]14/06/2013 19:01 7,600,128 recovery-clockwork-touch-6.0.3.2-m7--v2.img[/B][/B]
30/09/2013 02:08 8,427,520 recovery-clockwork-touch-6.0.3.8-m7ul.img
05/11/2013 02:29 9,052,160 recovery-clockwork-touch-6.0.4.4-m7ul.img
14/11/2013 07:12 8,955,904 recovery-clockwork-touch-6.0.4.5-m7ul.img
09/06/2013 15:02 648,208 revone
03/11/2013 20:56 249,028 Screenshot_2013-11-03-20-51-36.png
29/02/2008 03:33 5,925,120 stock_boot_img_2.24.401.8.img
05/05/2013 15:04 9,820,416 stock_recovery_1.29.666.17.img
22/08/2013 12:17 8,964,352 stock_recovery_2.24.401.1.img
29/09/2013 21:31 10,584,320 stock_recovery_2.24.401.8.img
24/06/2013 09:09 8,964,352 stock_recovery_2.24.707.1.img
27 File(s) 1,225,415,925 bytes
4 Dir(s) 11,100,098,560 bytes free
C:\ADB2>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[B][COLOR="Blue"]C:\ADB2>fastboot flash recovery recovery.img[/COLOR][/B]
[COLOR="Red"]error: cannot load 'recovery.img'[/COLOR]
C:\ADB2>[B]fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img[/B]
sending 'recovery' (7422 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.841s
C:\ADB2>[B][B]fastboot erase cache[/B][/B]
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\ADB2>[B]fastboot reboot-bootloader[/B]
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB2>
Click to expand...
Click to collapse
Didn't mean to sound snappy.
I just realized that since I reformatted my laptop a couple of weeks ago, file extensions were hidden so the file name was wrong due to .img.img. So thanks for suggesting I pull a dir, I'm an idiot...

gsxrfl1k6 said:
Didn't mean to sound snappy.
I just realized that since I reformatted my laptop a couple of weeks ago, file extensions were hidden so the file name was wrong due to .img.img. So thanks for suggesting I pull a dir, I'm an idiot...
Click to expand...
Click to collapse
no worries. the .img.img issue is happening a lot!
BTW, if fastboot doesn't recognize your device it usually just sits there waiting:
Code:
C:\ADB2>fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
< waiting for device >

nkk71 said:
no worries. the .img.img issue is happening a lot!
BTW, if fastboot doesn't recognize your device it usually just sits there waiting:
Code:
C:\ADB2>fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
< waiting for device >
Click to expand...
Click to collapse
Good to know, thanks again.

Recovery Help

I've done some searches and am at a loss. I am on Insertcoin 2.8. I upgraded TWRP to 2.7 and now it won't enter into recovery. It gets to the screen that has "Entering recovery" at the top, but it just stalls there and I have to press the power button until it restarts. I've tried using Flashify and Goomanager to re-install, but it just hangs up at the entering recovery page. Any help or links would be aprreciated.

A quick fix try installing a 2.6 version of twrp.

Try and boot into the bootloader, do a fastboot erase cache and then reboot into recovery and see if it works.
Sent from my HTC One using Tapatalk

Egrier said:
Try and boot into the bootloader, do a fastboot erase cache and then reboot into recovery and see if it works.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I've never done that before. Can you suggest where I might find a link or a video? Thanks!

You have to have adb/fastboot on your computer. Boot your phone into bootloader. Hook it up to the computer and make sure the phone says 'fastboot usb'. Browse to where you have adb installed on the computer and open up a command prompt there. At the prompt, type in 'fastboot erase cache'. Then type in 'fastboot reboot-bootloader'. When your phone comes back up, try and get into recovery again.
Sent from my HTC One using Tapatalk

Egrier said:
You have to have adb/fastboot on your computer. Boot your phone into bootloader. Hook it up to the computer and make sure the phone says 'fastboot usb'. Browse to where you have adb installed on the computer and open up a command prompt there. At the prompt, type in 'fastboot erase cache'. Then type in 'fastboot reboot-bootloader'. When your phone comes back up, try and get into recovery again.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thank you very much! I'll give it a try.

gpo1956 said:
Thank you very much! I'll give it a try.
Click to expand...
Click to collapse
I tried this and it says "fastboot is not recognized as an internal or external command, operable program or batch file". What am I doing wrong?

Do you have adb installed on your computer?
Sent from my HTC One using Tapatalk

Egrier said:
Do you have adb installed on your computer?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
yes

Did you get it to work?
Sent from my HTC One using Tapatalk
---------- Post added at 05:26 PM ---------- Previous post was at 05:22 PM ----------
Did you go to the folder with you adb files, shift+right click the folder that contains the adb files and select 'open command prompt here' then try the fastboot erase cache command?
Sent from my HTC One using Tapatalk

Egrier said:
Did you get it to work?
Sent from my HTC One using Tapatalk
---------- Post added at 05:26 PM ---------- Previous post was at 05:22 PM ----------
Did you go to the folder with you adb files, shift+right click the folder that contains the adb files and select 'open command prompt here' then try the fastboot erase cache command?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Nope.

I was able to erase cache and reboot, but it didn't fix it. Any other ideas to try? I cant seem to install a different veersion of twrp using the adb method.

You can only flash recovery by fastboot. Fastboot flash recovery....... I would flash twrp 2.6.3.3 seems to be the most stable and have the least amount of issues
Sent from my HTC One using XDA Premium 4 mobile app

nateboi81 said:
You can only flash recovery by fastboot. Fastboot flash recovery....... I would flash twrp 2.6.3.3 seems to be the most stable and have the least amount of issues
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK, I'm making progress. I'm in fastboot and try to flash recovery, but it says "error-cannot open twrp.img", What am I doing wrong?

gpo1956 said:
OK, I'm making progress. I'm in fastboot and try to flash recovery, but it says "error-cannot open twrp.img", What am I doing wrong?
Click to expand...
Click to collapse
cannot load = MyFileNameIsWrong.img.img
and copy/paste is so useful (so the below is an example ):
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.

nkk71 said:
cannot load = MyFileNameIsWrong.img.img
and copy/paste is so useful (so the below is an example ):
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
Click to expand...
Click to collapse
now it just sits on "waiting for device".

gpo1956 said:
now it just sits on "waiting for device".
Click to expand...
Click to collapse
are you in bootloader with the red "FASTBOOT USB" showing?
and what does windows device manager show, check FAQ #2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
are you in bootloader with the red "FASTBOOT USB" showing?
and what does windows device manager show, check FAQ #2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
Yes I'm in bootloader with the red fastboot USB showing. I'll try and reinstall the drivers and try again.
Thanks very much for your continued help.

gpo1956 said:
Yes I'm in bootloader with the red fastboot USB showing. I'll try and reinstall the drivers and try again.
Thanks very much for your continued help.
Click to expand...
Click to collapse
You'll also need to check Windows Device Manager, if it's listed as unknown or such, then you need to manually select the drivers as mentioned in FAQ#2.
and just in case you have an older version of adb/fastboot, here is 1.0.31: http://www.androidfilehost.com/?fid=23329332407585867
you can find out by typing "adb version"

nkk71 said:
You'll also need to check Windows Device Manager, if it's listed as unknown or such, then you need to manually select the drivers as mentioned in FAQ#2.
and just in case you have an older version of adb/fastboot, here is 1.0.31: http://www.androidfilehost.com/?fid=23329332407585867
you can find out by typing "adb version"
Click to expand...
Click to collapse
I'm at my wits end! It still says cannot open openrecovery..... Where should I put the recovery file? Maybe its not on the right place?

HELP - BRICKED One!

I was flashing a new rom onto my HTC One today and my daughter got hold of it (Age 3) whilst my back was turned and has wiped the ROM completely!
I have TWRP v2.7.1.1 touch bootloader but I cant get a ROM installed - fastboot won't recognise that there is a device attached even though I get the 'connected sound' when I connect to my windows 8 laptop. I have searched for all the fastboot and adb solutions but have come to a dead end!
I think its dead! :crying:
Fastboot usb shows on the phone screen when connected though
the OS - on the fastboot screen shows blank too!
*** TAMPERED ***
*** RELOCKED ***
M7_ PVT SHIP S_ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 21 2013,22:50:54.0
Can anyone help?

lol if you have a working recovery then your device is not bricked. Even if your recovery is broken if you can access the bootloader your device is still fine.
It sounds to me like you are having some trouble with the windows drivers.. if you have a pc with linux I would try it there as it is easier. or if you only have win8 then you have to install these drivers http://forum.xda-developers.com/showthread.php?t=2544146
btw what problem do you have when installing the rom via recovery?

cuyo11 said:
lol if you have a working recovery then your device is not bricked. Even if your recovery is broken if you can access the bootloader your device is still fine.
It sounds to me like you are having some trouble with the windows drivers.. if you have a pc with linux I would try it there as it is easier. or if you only have win8 then you have to install these drivers http://forum.xda-developers.com/showthread.php?t=2544146
btw what problem do you have when installing the rom via recovery?
Click to expand...
Click to collapse
"C:\android-tools>fastboot devices
HT34PW913345 fastboot"​
CID = HTC__001
I can attempt to flash a .zip rom (same recovery number = stock 5.11.401.10) but it fails!
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 43.432s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 179.412s​
I cant flash a different recovery anymore I presume as my bootloader is "RELOCKED" and I can't work out how to unlock it. HTCDev can't unlock it.
C:\android-tools>fastboot flash recovery recovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.187s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.141s​
What is "bootloader signature checking"? How do I resolve that problem of FAILED?
I can access the RUU screen successfully
[INDENTC:\android-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.187s]
finished. total time: 0.234s][/INDENT]
but when I try to flash a .zip it doesn't work still
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 44.000s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 159.127s​
Anyone have any ideas of how to get the signature checking to work?

I have managed to unlock again using my Unlock_code.bin file but it still fails to load the .zip ROM
C:\android-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.172s
C:\android-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.172s
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 43.874s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.203s​

I have now managed to load ClockworkMod Recovery v6.0.4.6
I have found I can't mount the /sdcard
I guess that's where my problem lies? If my phone has forgotten how to find /sdcard then how can it flash to it?

targett said:
I have now managed to load ClockworkMod Recovery v6.0.4.6
I have found I can't mount the /sdcard
I guess that's where my problem lies? If my phone has forgotten how to find /sdcard then how can it flash to it?
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showthread.php?t=2228274&page=3
then let me know if you have any questions.

nkk71 said:
Check this http://forum.xda-developers.com/showthread.php?t=2228274&page=3
then let me know if you have any questions.
Click to expand...
Click to collapse
I have wiped the system and cache just in case and am attempting the sideload but when i do the "adb devices" it doesn't sow my device number, where it does if in fastboot.
G:\adb>adb devices
List of devices attached
​
And when I attempt at adb sideload I get this
G:\adb>adb sideload One_5.11.401.10_odexed.zip
error: device not found​Stuck again :crying:
Oh - How important is the USB OTG in the adb sideload

targett said:
I have wiped the system and cache just in case and am attempting the sideload but when i do the "adb devices" it doesn't sow my device number, where it does if in fastboot.
Stuck again:crying:
Click to expand...
Click to collapse
it is mentioned in the post, but here again: FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
it is mentioned in the post, but here again: FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
Sorry for being so stupid! I feel like a noob on this device (not flashed or rooted in about 3 years!)
Reading it all again I see I need S-Off. My Security is ON. and I can't turn it off as I can't install SuperSU or Superuser or anything at all.
Any thoughts?

targett said:
Sorry for being so stupid! I feel like a noob on this device (not flashed or rooted in about 3 years!)
Reading it all again I see I need S-Off. My Security is ON. and I can't turn it off as I can't install SuperSU or Superuser or anything at all.
Any thoughts?
Click to expand...
Click to collapse
sorry, i don't follow. it has nothing to do with s-on or s-off.
you say your device isn't being seen while in custom recovery, but it has to show somewhere in device manager, no? if yes, then you may need to manually select the correct drivers, that's it

nkk71 said:
sorry, i don't follow. it has nothing to do with s-on or s-off.
you say your device isn't being seen while in custom recovery, but it has to show somewhere in device manager, no? if yes, then you may need to manually select the correct drivers, that's it
Click to expand...
Click to collapse
Sorry!
I have sorted the Win8 driver issue - Hadn't spotted that one.
I have now managed to adb push the .zip file and adb sideload it too.
I'm now installing the 'sideload.zip' Wish me luck!
Wordked! It F#*king WORKED!!!!!
Thank you, thank you, thank you!

targett said:
Sorry!
I have sorted the Win8 driver issue - Hadn't spotted that one.
I have now managed to adb push the .zip file and adb sideload it too.
I'm now installing the 'sideload.zip' Wish me luck!
Wordked! It F#*king WORKED!!!!!
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Good Luck :good: :good:

fastboot error lg optimus l90 D415

So I have an LG D415 and I don't know if it's bricked, softbricked, hardbricked or whatever, i'm really a noob and would really appreciate some help, I've included a picture, that shows what pops up when I try entering "Download mode" but I've already tried flashing the KDZ files, I've tried factory resetting the phone, nothing seems to work, phone always shows 0% battery even after charging for over an hour, and so I tried getting into the fastboot commands and stuff, I extracted the laf dz from the kdz files, renamed it to laf.img, put it in the same folder as my fastboot drivers (not even sure if I have the correct drivers) I open up command prompt inside the folder, type in "Fastboot flash laf laf.img" and the following appears in cmd:
target reported max download size of 536870912 bytes
sending 'laf' (13312 KB)...
OKAY [ 0.586s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.739s
I feel like I am missing something or missing some steps, I've got the laf partition, the fastboot drivers(I think) phones in fastboot mode even though at the top it says download mode, no idea as to what to do or try next, if anybody could help it would be very much appreciated...
https://drive.google.com/file/d/0B0shRlbnxbQpTFhYTnpnX3RhVUE/view?usp=sharing

SMOKYxPANDA said:
So I have an LG D415 and I don't know if it's bricked, softbricked, hardbricked or whatever, i'm really a noob and would really appreciate some help, I've included a picture, that shows what pops up when I try entering "Download mode" but I've already tried flashing the KDZ files, I've tried factory resetting the phone, nothing seems to work, phone always shows 0% battery even after charging for over an hour, and so I tried getting into the fastboot commands and stuff, I extracted the laf dz from the kdz files, renamed it to laf.img, put it in the same folder as my fastboot drivers (not even sure if I have the correct drivers) I open up command prompt inside the folder, type in "Fastboot flash laf laf.img" and the following appears in cmd:
target reported max download size of 536870912 bytes
sending 'laf' (13312 KB)...
OKAY [ 0.586s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.739s
I feel like I am missing something or missing some steps, I've got the laf partition, the fastboot drivers(I think) phones in fastboot mode even though at the top it says download mode, no idea as to what to do or try next, if anybody could help it would be very much appreciated...
https://drive.google.com/file/d/0B0shRlbnxbQpTFhYTnpnX3RhVUE/view?usp=sharing
Click to expand...
Click to collapse
What ROM are you using? I think you should try flashing the bootstack with recovery from here >> https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632. When you flash the bootstack, recovery gets rewritten with an old version of twrp so you probably want to have an IMG of twrp to update to the latest version.

0000.0000.00 said:
What ROM are you using? I think you should try flashing the bootstack with recovery from here >> https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632. When you flash the bootstack, recovery gets rewritten with an old version of twrp so you probably want to have an IMG of twrp to update to the latest version.
Click to expand...
Click to collapse
I'm not aware of what ROM the phone is using, and I don't even know if the bootloader is unlocked, or if the phone has TWRP or root, and I don't want to mess the phone up even more (if that's even possible) phone was a friends and he gave it to me, said I could keep it if I could fix it, and i don't currently have a working phone, so it would be really nice to fix this one, i'm really a noob when it comes to this stuff, but I'm willing to learn if that's what it takes to fix the phone, I also included a link that shows a picture of the information that appears when i type in "fastboot getvar all" in command, not sure if that could help you
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view?usp=sharing

SMOKYxPANDA said:
I'm not aware of what ROM the phone is using, and I don't even know if the bootloader is unlocked, or if the phone has TWRP or root, and I don't want to mess the phone up even more (if that's even possible) phone was a friends and he gave it to me, said I could keep it if I could fix it, and i don't currently have a working phone, so it would be really nice to fix this one, i'm really a noob when it comes to this stuff, but I'm willing to learn if that's what it takes to fix the phone, I also included a link that shows a picture of the information that appears when i type in "fastboot getvar all" in command, not sure if that could help you
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view?usp=sharing
Click to expand...
Click to collapse
So the first to do is run the command fastboot oem unlock with the phone connected to your computer with fastboot. Then download the latest twrp from https://dl.twrp.me/w7/twrp-3.1.1-0-w7.img and flash it with fastboot flash recovery twrp-3.1.1-0-w7.img making sure that you move the twrp IMG to the directory where fastboot is unless fastboot is on your path where you can just flash it from cmd in the downloads folder. After that, try to factory reset the phone and it should boot into twrp where I would flash the lollipop bootstack linked above with adb sideload "zip name here" where you put the full filename of the zip in zip name here and remove the quotes, boot into the download mode thing which is fastboot and reflash recovery with the instructions above.
---------- Post added at 11:07 AM ---------- Previous post was at 11:02 AM ----------
Also, are you trying to save any data?

0000.0000.00 said:
So the first to do is run the command fastboot oem unlock with the phone connected to your computer with fastboot. Then download the latest twrp from https://dl.twrp.me/w7/twrp-3.1.1-0-w7.img and flash it with fastboot flash recovery twrp-3.1.1-0-w7.img making sure that you move the twrp IMG to the directory where fastboot is unless fastboot is on your path where you can just flash it from cmd in the downloads folder. After that, try to factory reset the phone and it should boot into twrp where I would flash the lollipop bootstack linked above with adb sideload "zip name here" where you put the full filename of the zip in zip name here and remove the quotes, boot into the download mode thing which is fastboot and reflash recovery with the instructions above.
---------- Post added at 11:07 AM ---------- Previous post was at 11:02 AM ----------
Also, are you trying to save any data?
Click to expand...
Click to collapse
No, i'm not trying to save any data, I want a fresh start, the problem when trying the "fastboot oem unlock" command is that it gives me an error, again i put a link below to show you what appears when trying that command..
https://drive.google.com/file/d/0B0shRlbnxbQpeFlxcWxjS0l1eE0/view?usp=sharing

This is what appears on the phone, yet nothing happens
https://drive.google.com/file/d/0B0shRlbnxbQpQzVXMjZ4d3E5S3M/view?usp=sharing

SMOKYxPANDA said:
This is what appears on the phone, yet nothing happens
https://drive.google.com/file/d/0B0shRlbnxbQpQzVXMjZ4d3E5S3M/view?usp=sharing
Click to expand...
Click to collapse
Something probably happened..
Can you please send the results of fastboot getvar all so I can check.

I had already sent it, but here it is again:
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view

SMOKYxPANDA said:
I had already sent it, but here it is again:
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view
Click to expand...
Click to collapse
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.

0000.0000.00 said:
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
Click to expand...
Click to collapse
This is the only response I get:
...
FAILED (remote: unkown command)
finished. total time: 0.002s

SMOKYxPANDA said:
This is the only response I get:
...
FAILED (remote: unkown command)
finished. total time: 0.002s
Click to expand...
Click to collapse
Then try flashing twrp and the bootstack and Tell me how it goes from there.

0000.0000.00 said:
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
Click to expand...
Click to collapse
0000.0000.00 said:
Then try flashing twrp and the bootstack and Tell me how it goes from there.
Click to expand...
Click to collapse
How can I flash TWRP?
I've got a TWRP file named "TWRP_2.8.0.0_26.09.14_L90.img"
Tell me where to go from there, and also, the phone isn't even detected using the command "adb devices" it says list of devices and does'nt ever show anything...

SMOKYxPANDA said:
How can I flash TWRP?
I've got a TWRP file named "TWRP_2.8.0.0_26.09.14_L90.img" Tell me where to go from there, and also, the phone isn't even detected using the command "adb devices" it says list of devices and does'nt ever show anything...
Click to expand...
Click to collapse
Flash twrp by first moving the twrp IMG to where fastboot is and running fastboot flash recovery TWRP_2.8.0.0_26.09.14_L90.img with the phone in the download mode thing and connected to the computer.
Also, could you please re-run fastboot getvar all even if you have already run it because its output probably changed and send me an image of what it shows.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
0000.0000.00 said:
Flash twrp by first moving the twrp IMG to where fastboot is and running fastboot flash recovery TWRP_2.8.0.0_26.09.14_L90.img with the phone in the download mode thing and connected to the computer.
Also, could you please re-run fastboot getvar all even if you have already run it because its output probably changed and send me an image of what it shows.
Click to expand...
Click to collapse
After that, run fastboot reboot recovery to reboot into recovery. Press the advanced button and then press the button that says adb sideload with the touchscreen and start it. Then to install the zip run adb sideload zipname where zipname is the name of the zip you want to flash.
After that boot back into the download mode thing to reflash recovery and then reboot into recovery with fastboot reboot recovery. After that I would flash the zips for a ROM and optionally gapps with adb sideload.

This is what I get:
https://drive.google.com/file/d/0B0shRlbnxbQpN3ZrendPbkI4R1k/view?usp=sharing

SMOKYxPANDA said:
This is what I get:
https://drive.google.com/file/d/0B0shRlbnxbQpN3ZrendPbkI4R1k/view?usp=sharing
Click to expand...
Click to collapse
Were you able to flash recovery and boot into it?

0000.0000.00 said:
Were you able to flash recovery and boot into it?
Click to expand...
Click to collapse
No, you can observe in the picture where it gives me the same error message, unknown command

SMOKYxPANDA said:
No, you can observe in the picture where it gives me the same error message, unknown command
Click to expand...
Click to collapse
Could you please send me a picture of the output of fastboot devices.
---------- Post added at 08:52 PM ---------- Previous post was at 08:48 PM ----------
I think the fastboot on the phone has issues because it seems to not flash anything. I think you should try this >>> https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429

guys, i am in the exact same situation..phone stuck on lg logo, no recovery possible, no download mode available, only fastboot
i have downloaded and extracted the img files from the original firmware, but i cannot do anything with flashboot commands..pls see below
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
c369bc71 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 5.029s]
finished. total time: 5.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 536870912 bytes
sending 'laf' (15872 KB)...
OKAY [ 0.501s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (13824 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>

asahi7 said:
guys, i am in the exact same situation..phone stuck on lg logo, no recovery possible, no download mode available, only fastboot
i have downloaded and extracted the img files from the original firmware, but i cannot do anything with flashboot commands..pls see below
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
c369bc71 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 5.029s]
finished. total time: 5.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 536870912 bytes
sending 'laf' (15872 KB)...
OKAY [ 0.501s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (13824 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429

thanks, already did, unfortunately seems like there is a problem with the rom. i flash each file but when i test again i always get slb1 corrupt. no recovery, no download mode. it was worth the try