Database Develop

Urgent no recovery sticks after s-off

I S-offed my HTC one then I RUUed it to remove tampered then tried to flash back a recovery and that wouldn't work even erased cache. If i erase cache to many times it seems to remove system. So I read I have to get a tampered flag back up. Right now it just says
*Unlocked*
M7_UL PVT SHIP S-OFF RH
CID-CWS_001
**
**
OS-3.17.502.3
Any ideas on getting any recovery to stick?

Irish Enigma said:
I S-offed my HTC one then I RUUed it to remove tampered then tried to flash back a recovery and that wouldn't work even erased cache. If i erase cache to many times it seems to remove system. So I read I have to get a tampered flag back up. Right now it just says
*Unlocked*
M7_UL PVT SHIP S-OFF RH
CID-CWS_001
**
**
OS-3.17.502.3
Any ideas on getting any recovery to stick?
Click to expand...
Click to collapse
sounds strange are you using the correct commands? download latest recovery (CWM or TWRP) from the xda threads, place it in your adb folder, then
abd reboot bootloader
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
and enter RECOVERY, should be no problem. if it still fails, copy/paste your command prompt here

nkk71 said:
sounds strange are you using the correct commands? download latest recovery (CWM or TWRP) from the xda threads, place it in your adb folder, then
abd reboot bootloader
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
and enter RECOVERY, should be no problem. if it still fails, copy/paste your command prompt here
Click to expand...
Click to collapse
UPDATE it worked with CWM. All the Twrp flashes were "successful" but they wouldn't stick. Now the latest clockwork sticks no problem. There's something wrong with twrp 2.6.3.0 for GSM. It doesn't work at all.
Yes i downloaded the file many times.
Any ideas i want twrp...

Irish Enigma said:
UPDATE it worked with CWM. All the Twrp flashes were "successful" but they wouldn't stick. Now the latest clockwork sticks no problem. There's something wrong with twrp 2.6.3.0 for GSM. It doesn't work at all.
Yes i downloaded the file many times.
Any ideas i want twrp...
Click to expand...
Click to collapse
Can you post the link from where you downloaded it. I'll give it a shot an let you know if it works on my phone
Hit the thanks button if i helped

nkk71 said:
Can you post the link from where you downloaded it. I'll give it a shot an let you know if it works on my phone
Hit the thanks button if i helped
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2173870

Irish Enigma said:
http://forum.xda-developers.com/showthread.php?t=2173870
Click to expand...
Click to collapse
Worked just fine; download was a bit tough, kept stopping and restarting (i use a download manager)
1- verified MD5: 216d3f836264fc568fe8054263fa26ba
2:
Code:
C:\ADB2>[B]adb reboot bootloader[/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\ADB2>[B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\ADB2>[B]fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img[/B]
sending 'recovery' (10570 KB)...
OKAY [ 1.856s]
writing 'recovery'...
OKAY [ 0.780s]
finished. total time: 2.636s
C:\ADB2>[B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB2>[B]fastboot reboot-bootloader[/B]
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
entered recovery, and screenshot attached:

nkk71 said:
Worked just fine; download was a bit tough, kept stopping and restarting (i use a download manager)
1- verified MD5: 216d3f836264fc568fe8054263fa26ba
2:
Code:
C:\ADB2>[B]adb reboot bootloader[/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\ADB2>[B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\ADB2>[B]fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img[/B]
sending 'recovery' (10570 KB)...
OKAY [ 1.856s]
writing 'recovery'...
OKAY [ 0.780s]
finished. total time: 2.636s
C:\ADB2>[B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB2>[B]fastboot reboot-bootloader[/B]
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
entered recovery, and screenshot attached:
Click to expand...
Click to collapse
....wtf is wrong with my phone....

Irish Enigma said:
....wtf is wrong with my phone....
Click to expand...
Click to collapse
did you verify MD5?
EDIT: I'll upload it for you, hold on...
---------- Post added at 04:20 PM ---------- Previous post was at 04:15 PM ----------
Irish Enigma said:
....wtf is wrong with my phone....
Click to expand...
Click to collapse
OK, here you go:
openrecovery-twrp-2.6.3.0-m7.img 10.3 MB
https://mega.co.nz/#!KRN3WJjZ!DmbbAR4ZVgbWQTVyv0kOkj3vAF0bTzMg5epyGMZJLk0
verify MD5 is: 216d3f836264fc568fe8054263fa26ba
then
adb reboot bootloader
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
enter RECOVERY
copy/paste your command prompt like I did, to see if we can spot anything wrong.
Hit the thanks button if I helped

nkk71 said:
did you verify MD5?
EDIT: I'll upload it for you, hold on...
---------- Post added at 04:20 PM ---------- Previous post was at 04:15 PM ----------
OK, here you go:
openrecovery-twrp-2.6.3.0-m7.img 10.3 MB
https://mega.co.nz/#!KRN3WJjZ!DmbbAR4ZVgbWQTVyv0kOkj3vAF0bTzMg5epyGMZJLk0
verify MD5 is: 216d3f836264fc568fe8054263fa26ba
then
adb reboot bootloader
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
enter RECOVERY
copy/paste your command prompt like I did, to see if we can spot anything wrong.
Hit the thanks button if I helped
Click to expand...
Click to collapse
i gotta get back to you on that. my phone is encrypting @ %72

Irish Enigma said:
i gotta get back to you on that. my phone is encrypting @ %72
Click to expand...
Click to collapse
encrypting you won't be able to access it from custom recovery anymore. or is that something that is now supported?

nkk71 said:
encrypting you won't be able to access it from custom recovery anymore. or is that something that is now supported?
Click to expand...
Click to collapse
it's not actually. I flashed everything I needed. I have to RUU it to decrypt it.I have recovery issues. I can flash and access recovery I just have to ADB sideload everything now.

Irish Enigma said:
it's not actually. I flashed everything I needed. I have to RUU it to decrypt it.I have recovery issues. I can flash and access recovery I just have to ADB sideload everything now.
Click to expand...
Click to collapse
uh i need someone to analyse my partition tables they seem screwed up.

Irish Enigma said:
uh i need someone to analyse my partition tables they seem screwed up.
Click to expand...
Click to collapse
what do you mean? start reading here: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
before formatting anything, what do you think is corrupt?
first thing is to do this "cat /proc/emmc"
read here: http://forum.xda-developers.com/showthread.php?t=2504542&page=8

[HELP!] I need rom ship HTC ONE M7 Australia ( CID-VODAP021)

I can't find official rom of my HTC One M7 from Vodafone, i search google and I know my CID is VODAP021, can anybody give me an official rom for my HTC One M7. Thank you a lot !
:crying::crying::crying::crying::crying:

No Ruu. Only guru reset file http://www.htc1guru.com/dld/guru_reset_m7_2-24-980-2-zip/
What's the issue?
sent from my mobile device

mikadoofvn said:
I can't find official rom of my HTC One M7 from Vodafone, i search google and I know my CID is VODAP021, can anybody give me an official rom for my HTC One M7. Thank you a lot !
:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/guru_reset_m7_2-24-980-2-zip/
Sent from my HTC One using xda app-developers app

I have downloaded, but run by ADB command error "Fail", I've tried a lot of times, and are in need of an exe file, not the zip file

mikadoofvn said:
I have downloaded, but run by ADB command error "Fail", I've tried a lot of times, and are in need of an exe file, not the zip file
Click to expand...
Click to collapse
There is no ruu.exe for your phone.
Sent from my HTC One using xda app-developers app
---------- Post added at 04:55 AM ---------- Previous post was at 04:53 AM ----------
SaHiLzZ said:
No Ruu. Only guru reset file http://www.htc1guru.com/dld/guru_reset_m7_2-24-980-2-zip/
Click to expand...
Click to collapse
Almost at same time
Sent from my HTC One using xda app-developers app

HTML:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rauvang>cd \Android
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.049s]
finished. total time: 0.049s
C:\Android>fastboot flash zip guru.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1045181 KB)...
OKAY [ 39.588s]
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: 55.879s
C:\Android>

mikadoofvn said:
HTML:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rauvang>cd \Android
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.049s]
finished. total time: 0.049s
C:\Android>fastboot flash zip guru.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1045181 KB)...
OKAY [ 39.588s]
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: 55.879s
C:\Android>
Click to expand...
Click to collapse
This is a guru reset, you have to adb push the zip to /sdcard/ and then install the zip from recovery
Sent from my HTC One using xda app-developers app
---------- Post added at 05:00 AM ---------- Previous post was at 04:59 AM ----------
Go see the video guide on htc1guru.com
Sent from my HTC One using xda app-developers app

alray said:
This is a guru reset, you have to adb push the zip to /sdcard/ and then install the zip from recovery
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Stuck at Bootloader, cannot connect to storage.... how can I put adb file to /sdcard/ :crying:

@alray .. What else can anyone ask for! Multiple people helping out.
@ OP. Unlock bootloader. Flash custom recovery, push file via adb and FLASH!!
sent from my mobile device

SaHiLzZ said:
@alray .. What else can anyone ask for! Multiple people helping out.
@ OP. Unlock bootloader. Flash custom recovery, push file via adb and FLASH!!
sent from my mobile device
Click to expand...
Click to collapse
I have TWRP
How to flash file in TWRP
File zip

SaHiLzZ said:
@alray .. What else can anyone ask for! Multiple people helping out.
@ OP. Unlock bootloader. Flash custom recovery, push file via adb and FLASH!!
sent from my mobile device
Click to expand...
Click to collapse
If OP wants to be completely stock, why unlock bootloader? Let him just use the standard factory reset from the stock recovery right?
Sent from my iPod touch using Tapatalk

mikadoofvn said:
Stuck at Bootloader, cannot connect to storage.... how can I put adb file to /sdcard/ :crying:
Click to expand...
Click to collapse
Yeah, as SaHiLzZ said, you will be able to use adb when booted in cuatom recovery. I recomemd you go with trwp if you havent one installed yet
Sent from my HTC One using xda app-developers app
---------- Post added at 05:11 AM ---------- Previous post was at 05:07 AM ----------
n1234d said:
If OP wants to be completely stock, why unlock bootloader? Let him just use the standard factory reset from the stock recovery right?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I thought he tried before asking how to return stock... Did he?
Sent from my HTC One using xda app-developers app

mikadoofvn said:
I have TWRP
How to flash file in TWRP
File zip
Click to expand...
Click to collapse
Search how to adb push
sent from my mobile device
---------- Post added at 11:15 PM ---------- Previous post was at 11:12 PM ----------
Also. Do NOT FLASH if you have a 1.54+ hboot.
sent from my mobile device

mikadoofvn said:
I have TWRP
How to flash file in TWRP
File zip
Click to expand...
Click to collapse
open a cmd prompt from you adb/fastboot folder of your computer
connect phone to pc and boot in twrp
Code:
adb push name_of_file.zip /sdcard/
then in twrp select install then chose the zip.
and make sure your hboot version is compatible before as sahillz said.
you can see hboot version in bootloader
and btw did you first tried to factory reset ?

alray said:
open a cmd prompt from you adb/fastboot folder of your computer
connect phone to pc and boot in twrp
Code:
adb push name_of_file.zip /sdcard/
then in twrp select install then chose the zip.
and make sure your hboot version is compatible before as sahillz said.
you can see hboot version in bootloader
and btw did you first tried to factory reset ?
Click to expand...
Click to collapse
HTML:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rauvang>cd \Android
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.3-m7.img'
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.073s]
writing 'recovery'...
OKAY [ 0.705s]
finished. total time: 1.779s
C:\Android>adb push Guru_Reset_M7_2.24.980.2 /sdcard/
error: more than one device and emulator
C:\Android>adb push Guru_Reset_M7_2.24.980.2.zip /sdcard/
error: more than one device and emulator
C:\Android>adb push Guru_Reset_M7_2.24.980.2.zip /sdcard/
error: device offline
C:\Android>
I try..... in TWRP and Bootloader

mikadoofvn said:
HTML:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rauvang>cd \Android
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.3-m7.img'
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.073s]
writing 'recovery'...
OKAY [ 0.705s]
finished. total time: 1.779s
C:\Android>adb push Guru_Reset_M7_2.24.980.2 /sdcard/
error: more than one device and emulator
C:\Android>adb push Guru_Reset_M7_2.24.980.2.zip /sdcard/
error: more than one device and emulator
C:\Android>adb push Guru_Reset_M7_2.24.980.2.zip /sdcard/
error: device offline
C:\Android>
I try..... in TWRP and Bootloader
Click to expand...
Click to collapse
what is the output of
Code:
adb devices
when in twrp?
make sure you don't have any other devices connected to your pc and that you don't have an android emulator like ''bluestacks'' or ''windows android'' installed on your computer.
---------- Post added at 05:55 AM ---------- Previous post was at 05:37 AM ----------
if you have multiple devices (or emulator) connected to your computer then use this command:
Code:
adb -s YOUR_PHONE_SERIAL_NUMBER push NAME_OF_FILE.zip /sdcard/

alray said:
what is the output of
Code:
adb devices
when in twrp?
Click to expand...
Click to collapse
HTC is one of my TWRP mode, I've tried adb command to copy the zip file but not, I only connect one device in recovery mode
HTML:

alray said:
what is the output of
Code:
adb devices
when in twrp?
make sure you don't have any other devices connected to your pc and that you don't have an android emulator like ''bluestacks'' or ''windows android'' installed on your computer.
---------- Post added at 05:55 AM ---------- Previous post was at 05:37 AM ----------
if you have multiple devices (or emulator) connected to your computer then use this command:
Code:
adb -s YOUR_PHONE_SERIAL_NUMBER push NAME_OF_FILE.zip /sdcard/
Click to expand...
Click to collapse
HTML:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rauvang>cd \Android
C:\Android>adb devices
List of devices attached
HT34WW904065 offline
HT34WW904065 recovery
C:\Android>adb -s HT34WW904065 push Guru_Reset_M7_2.24.980.2.zip /sdcard/
error: more than one device
C:\Android>

@nkk71.. How goes it! Does 1.54 works with 2.260.x firmware? Any insight for OP?
sent from my mobile device

SaHiLzZ said:
@nkk71.. How goes it! Does 1.54 works with 2.260.x firmware? Any insight for OP?
sent from my mobile device
Click to expand...
Click to collapse
good & yourself, all well i trust.
you mean hboot 1.54 with 2.24.xxx.x firmware? haven't seen any 2.26 firmware. but guru reset should work fine as you guys mentioned to him.
OP, can you post a "fastboot getvar all" (removing IMEI and s/n), and confirm bootloader is unlocked.

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?

[Q] A Unique Problem...:confused:

Hello fellow One users,
I have browsed threw most if not all the HTC One problems on the site and google to try and figure this thing out as i KNOW how people hate Duplicated Threads... Anyways i hope someone can help me with this situation.. Thanks
I received this phone from a friend, ive attached pic showing the state he gave it t me in... According to him he was able to get the phone into Bootmode .. when he gives it to me AFTER TRYING TO RUN A RUU without S-OFF ...
Heres my problem... Basically the phone will not power on, into anything... I try to power on i get this... either a red flashing LED inside the top speaker... or a solid RED led when plugged into the power outlet .... Then ill try to boot into Bootmode and i get this ... Home and Back buttons flashing with no LED on, after the Home and Back buttons flash 10 times i then get a solid red LED , plugged in or not... ive even trying to just charge the device ( I had it charging for a week CONSTANTLY ) no results .. i even try to run a RUU ( for luck i guess ) but no cigar... all i get is an error saying the device has less then 30% battery .. i don't know how it can tell that even tho my PC actually doesn't even see the phone EVER connect.
If anyone can give me ideas and solutions on how to go about fixing this please do as i have tried almost everything. I am very familiar with android and electronics so please don't noob me.
Thank you and i do apologize if i do respond with Noobish questions and the HTC One is a newer device to me.
Thanks
**UPDATE**
Got it to boot into bootloader and it also boots to the HTC screen as shown below.... now i try to run adb commands but the PHONE IS NOT AUTHORIZED...What do i do now??

RED light solid = Not enough battery - at least 30% is required other the security measures will prevent you from flashing RUUs.
Device unauthorized? Try to check and uncheck the USB Debugging option in the device, if possible. If not, you can plug in and out the USB and the device should show up a messagebox to ask you if you authorize the computer, but for that Debugging must be checked AFAIK.
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
Click to expand...
Click to collapse
If ADB does not work, you can still use fastboot commands.

davebugyi said:
Try to check and uncheck the USB Debugging option in the device, if possible.
If ADB does not work, you can still use fastboot commands.
Click to expand...
Click to collapse
I can't access the device itself as there is no OS on the device, so I also don't know if I can even get the device authorized...
If Fastboot commands still work, I should be able to flash a rom to the device correct??
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
I can't access the device itself as there is no OS on the device, so I also don't know if I can even get the device authorized...
If Fastboot commands still work, I should be able to flash a rom to the device correct??
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
1- RUU will not work with S-On and UNLOCKED bootloader, with S-On you need to relock bootloader for RUU to work -> but don't do that yet!!
2- for future reference: Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
3- what adb version are you running and what OS do you have
4- start by posting a "fastboot getvar all" (excluding IMEI and s/n) and what do you ultimately want to achieve?

nkk71 said:
3- what adb version are you running and what OS do you have
4- start by posting a "fastboot getvar all" (excluding IMEI and s/n) and what do you ultimately want to achieve?
Click to expand...
Click to collapse
I am running Windows 8 64bit with the latest adb version. also all i have are USB 3.0 ports
and ive tried to run the command "fastboot getvar all" but it just says waiting for device when the device is in fastboot usb mode...

Ok guys, so because i had windows 8.1 and only USB 3.0 Ports i followed this guide to fix the fastboot issue... http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers...
it now connects to fast boot, after running the fastboot command "fastboot getvar all" i get this in return... (refer to pic)
so any ideas how to RETURN THE PHONE TO STOCK
thanks

Shotgun4 said:
Ok guys, so because i had windows 8.1 and only USB 3.0 Ports i followed this guide to fix the fastboot issue... http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers...
it now connects to fast boot, after running the fastboot command "fastboot getvar all" i get this in return... (refer to pic)
so any ideas how to RETURN THE PHONE TO STOCK
thanks
Click to expand...
Click to collapse
1- Win8.1 doesn't play nice with hboot 1.44, so recommend you use a Win7 or Ubuntu Live USB.
2- why don't you just flash a custom recovery and install a custom ROM? because with S-On, you can only get your bootloader to say RELOCKED, not the original LOCKED
And I'll leave this here just in case:
There is a newer RUU for your version here
but I personally would not use it, because you can still achieve S-Off on hboot 1.44

nkk71 said:
1- Win8.1 doesn't play nice with hboot 1.44, so recommend you use a Win7 or Ubuntu Live USB.
2- why don't you just flash a custom recovery and install a custom ROM? because with S-On, you can only get your bootloader to say RELOCKED, not the original LOCKED
And I'll leave this here just in case:
There is a newer RUU for your version here
but I personally would not use it, because you can still achieve S-Off on hboot 1.44
Click to expand...
Click to collapse
Ok, I'll look for a Custom Rom and I'll flash that threw Fastboot.
Thanks
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
Ok, I'll look for a Custom Rom and I'll flash that threw Fastboot.
Thanks
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
1- ROMs are installed using custom recovery. (TWRP 2.6.3.3 or 2.6.3.4 recommended at the moment)
2- do you intend on trying to S-Off your phone?

nkk71 said:
1- ROMs are installed using custom recovery. (TWRP 2.6.3.3 or 2.6.3.4 recommended at the moment)
2- do you intend on trying to S-Off your phone?
Click to expand...
Click to collapse
I have TWRP 2.6.3.4 installed already as the recovery... And I do intend to gain S-Off
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
I have TWRP 2.6.3.4 installed already as the recovery... And I do intend to gain S-Off
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
then install the ROM mentioned here: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone to get S-Off: http://forum.xda-developers.com/showthread.php?t=2314582

nkk71 said:
then install the ROM mentioned here: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone to get S-Off: http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
Ok thanks, I'll let you know how things go
Sent from my LG-D801 using XDA Free mobile app

nkk71 said:
then install the ROM mentioned here: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone to get S-Off: http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
ok sorry for the delay but here are some snaps of the issues im having. Every time try to push something to the device, it gives me "FAILED <remote:not allowed>
then it even says that the bootloader is not unlocked ..how is that if it clearly states in the bootloader menu *** UNLOCKED ***??
Any ideas on how to fix this? if the HTC One only had an SD Card Slot this could be so much easier ...

Shotgun4 said:
ok sorry for the delay but here are some snaps of the issues im having. Every time try to push something to the device, it gives me "FAILED <remote:not allowed>
then it even says that the bootloader is not unlocked ..how is that if it clearly states in the bootloader menu *** UNLOCKED ***??
Any ideas on how to fix this? if the HTC One only had an SD Card Slot this could be so much easier ...
Click to expand...
Click to collapse
hmm , and you want to s-off your device?
are you trying to brick your device in the 20 commands or so you ran (with the exception of fastboot devices), none of them are correct... either mistyped or completely inappropriate.
fastboot commands are not a joke, don't treat them as such, or you will end up bricking your phone. randomly typing fastboot commands is not a good habit.
Now please do some reading and research, but here's some quick info: Your phone has three states
1- bootloader (this is where you use fastboot.exe to flash things appropriate for bootloader mode flashing, such as a custom recovery)
2- recovery (with custom recovery you can use adb.exe commands, and install ROMs)
3- ROM (if you have USB debugging enabled you can also use adb.exe commands here)

nkk71 said:
hmm , and you want to s-off your device?
are you trying to brick your device in the 20 commands or so you ran (with the exception of fastboot devices), none of them are correct... either mistyped or completely inappropriate.
fastboot commands are not a joke, don't treat them as such, or you will end up bricking your phone. randomly typing fastboot commands is not a good habit.
Now please do some reading and research, but here's some quick info: Your phone has three states
1- bootloader (this is where you use fastboot.exe to flash things appropriate for bootloader mode flashing, such as a custom recovery)
2- recovery (with custom recovery you can use adb.exe commands, and install ROMs)
3- ROM (if you have USB debugging enabled you can also use adb.exe commands here)
Click to expand...
Click to collapse
Ok but even if the Command codes are wrong ( I did them at 2am I was so tired) the program Squabbi Toolkit should have worked... Right?
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
Ok but even if the Command codes are wrong ( I did them at 2am I was so tired) the program Squabbi Toolkit should have worked... Right?
Click to expand...
Click to collapse
Wrong.
you use fastboot to flash
* recoveries
* erase cache
* ruu.zip packages
* firmware.zip packages
you use a custom recovery (such as TWRP 2.6.3.3), to install a <name of ROM>.zip
you cannot "fastboot flash ..." a custom ROM.ZIP.
PS: I seriously recommend you don't do these commands at 2am when you're tired, that could end badly

nkk71 said:
Wrong.
you use fastboot to flash
* recoveries
* erase cache
* ruu.zip packages
* firmware.zip packages
you use a custom recovery (such as TWRP 2.6.3.3), to install a .zip
you cannot "fastboot flash ..." a custom ROM.ZIP.
PS: I seriously recommend you don't do these commands at 2am when you're tired, that could end badly
Click to expand...
Click to collapse
Ok so what I want to do is...
1. Upload the ROM you previously posted to my device via Fastboot
2. Gain S-Off using revon
My issue is what proper command I use to load the rom to my device for flashing threw the recovery??
I can access the Bootloader, Fastboot and Recovery.
ADB will not work, not sure why...
In Recovery I can not mount the storage, as I would on my LG to load the zip file to storage and flash threw recovery...
Sent from my LG-D801 using XDA Free mobile app
**Update**
So I found this in a guide...
""Alternatively you can flash through Fastboot. Download the ROM and place it in the platform-tools folder.
To start flashing, type fastboot update [romfile.zip].
This will take a few minutes to complete, so do not touch the device while it is working. ""

Shotgun4 said:
Ok so what I want to do is...
1. Upload the ROM you previously posted to my device via Fastboot
2. Gain S-Off using revon
My issue is what proper command I use to load the rom to my device for flashing threw the recovery??
I can access the Bootloader, Fastboot and Recovery.
ADB will not work, not sure why...
In Recovery I can not mount the storage, as I would on my LG to load the zip file to storage and flash threw recovery...
Sent from my LG-D801 using XDA Free mobile app
**Update**
So I found this in a guide...
""Alternatively you can flash through Fastboot. Download the ROM and place it in the platform-tools folder.
To start flashing, type fastboot update [romfile.zip].
This will take a few minutes to complete, so do not touch the device while it is working. ""
Click to expand...
Click to collapse
Search more next time.
If I had a nickel for every time I post this
adb/fastboot files for Windows: http://www.androidfilehost.com/?fid=23329332407585867
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
then you can either:
1- OTG cable
2- adb push <name of rom>.zip /sdcard/
3- initiate sideload in custom recovery, then adb sideload <name of rom>.zip
adb push example:
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
.
if you're having problems with PC seeing your phone, check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
Search more next time.
If I had a nickel for every time I post this
adb/fastboot files for Windows: http://www.androidfilehost.com/?fid=23329332407585867
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
then you can either:
1- OTG cable
2- adb push <name of rom>.zip /sdcard/
3- initiate sideload in custom recovery, then adb sideload <name of rom>.zip
adb push example:
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
.
if you're having problems with PC seeing your phone, check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
Finally after 6 hours of sitting at my laptop, browsing the internet for answers ... it was so simple ...
1. adb wasnt working because when the device was connected in recover mode, Windows 8 had installed the "My HTC" drive ... To fix it all i did was uninstall that driver "My HTC".. refresh Device Manager and look under "unknown Devices" ... and install the Samasung OEM adb device driver in its place ...BOOM working adb!?
Next i followed your steps to push the rom via adb and it finished successful.
C:\Users\Peter\Android>adb devices
List of devices attached
FAXXXXXXXXXX recovery
C:\Users\Peter\Android>adb push rom.zip /sdcard/
4739 KB/s (1017950778 bytes in 209.742s)
C:\Users\Peter\Android>adb shell md5sum /sdcard/rom.zip
06c863ce41b0d5001290737a31e198a1 /sdcard/rom.zip
C:\Users\Peter\Android>
3. i check the "md5sum" and got "06c863ce41b0d5001290737a31e198a1" ... File i pushed was Android_Revolution_HD-One_9.4...
4. Flashed and device is now working perfectly :victory:
Thank You so much and for being so patient with me aha ... you deserve a thanks and a donation for all your help :highfive:
Also gained S-Off using Revon

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