Develop Bugs

Trying to use ADB to flash_image on Desire Z

Hey, I've been following Cyanogen mods guide about flash_image to flash PSFmod onto my phone. I can use ADB to push files to my SD card and stuff, but when I follow this:
Code:
Temporarily allow app to run from the sdcard (use mount to find the correct device for your sdcard, ie: the /dev/block/BLAH part)
mount -o remount,exec /dev/block//vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
But I get this error:
Code:
error scanning partitions
Does anyone know how to fix it?

You get that error from which of those commands ?

From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?

Beegee7730 said:
From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?
Click to expand...
Click to collapse
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?

Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App

I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?

steviewevie said:
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?
Click to expand...
Click to collapse
I got it from the Cyanogen Mod Wiki, should I look for a different version?
theXeffect said:
Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I would but the recovery I'm flashing isn't supported by Rom Manager.
steviewevie said:
I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?
Click to expand...
Click to collapse
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.

Beegee7730 said:
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.
Click to expand...
Click to collapse
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.

steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Wait a sec.

steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Tried few days ago with a kernel,but don`t works too.
You mean I need the eng hboot,then it should work,right?
Otherwise fastboot don`t work.

C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>

Beegee7730 said:
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
You haven't got S-OFF. You need S-OFF to flash a custom recovery.

I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.

Beegee7730 said:
I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.
Click to expand...
Click to collapse
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.

steviewevie said:
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.
Click to expand...
Click to collapse
SHIP.
I assume I need to reflash it with the engineering one?

Beegee7730 said:
SHIP.
I assume I need to reflash it with the engineering one?
Click to expand...
Click to collapse
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.

steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?

Beegee7730 said:
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?
Click to expand...
Click to collapse
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.

steviewevie said:
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.
Click to expand...
Click to collapse
Ah, managed to flash it.
Will test and report back when done.
EDIT:
It works!
Thanks alot!

steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
I think too,the same with my HTC Hero.
Fastboot wont work without engineering bootloader/hboot!
So the same at Desire Z.

[Q] Desire is in Stalemate condition

It all started when i tried to flash Insertcoin's Sense 2.1+ GB ROM. That involve messing about with partitions. I have re-formatted several times and erased all partitions, but still no help. the phone doesn't boot up, When SD card is in the phone, only the most basic android splash screen comes up and stays there. If my SD card is not on the phone. it is able to boot to the ROM, but nothing can be accessed, there is no keyboard, i can't answer calls, because the screen is just blank (apart from background image). also in Recovery mode i can't "choose zip from sdcard" because of the "E: can't mount /dev/block/mmcblk0
(or /dev/block/mmcblk0)" error.
edit: I tried un-rooting from http://forum.xda-developers.com/showthread.php?t=696189 thread. and in the beginning of the un-rooting it gave me the ERROR [140] BOOTLOADER VERSION ERROR. Now when SDcard is in, the boot process stops at HTC's own splash screen and when it's out of the phone, i can still access the obviously misinstalled ROM. At this point i'm very confused about what to do next. Can anyone help me?

Can you access and use fastboot??? If you can -
fastboot oem enableqxdm 0
and then
fastboot oem eraseconfig
That should fix your sd card mounting again....

i'm not really familiar with that command. In fastboot menu i can see Bootloader, Reboot, Reboot Bootloader and Power Down menu items
edit: okay, i understand you mean using that with cmd. Well, adb devices command shows no devices attached,

Amphor said:
i'm not really familiar with that command. In fastboot menu i can see Bootloader, Reboot, Reboot Bootloader and Power Down menu items
edit: okay, i understand you mean using that with cmd. Well, adb devices command shows no devices attached,
Click to expand...
Click to collapse
Not adb -
Boot to bootloader (vol down + power )
plug in usb - bootloader will change to say usb is plugged in
Boot fastboot - scroll down to and press power - bootloader will again change to show fastboot mode
open CMD then type -
fastboot devices
- if nothing happens make sure you have changed your directory to where fastboot.exe is stored
e.g. (is how my hard drive is set up but yours will prob be different
cd C:/android/tools
When fastboot devices command shows your phone -
fastboot oem enableqxdm 0
fastboot oem eraseconfig
That will re-eastblish your usb again
What set up do you have?? S-off?? Sd card partitioned etc... Hboot (all info from bootloader)
Oh and do you actually want to unroot or are you just trying to fix it?

i am just trying to fix it, any means necessary, whether it's unrooting or not
s-on, in the recovery menu there is format sdcard and format sd-ext. so, i would think that there is a partition, but not sure.
oh, and
C:\Users\Amphor>fastboot oem enableqxdm0
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.019s]
finished. total time: 0.020s
C:\Users\Amphor>
normal behaviour? Still can't choose zip from sdcard

http://forum.xda-developers.com/showthread.php?t=691639
Should get you going unless someone else has an easier way?

Not really sure what it did, but definitely not did it fix my problem. The solution was for some kind of USB connectivity issue which i have luckily. Wasn't it?

Amphor said:
Not really sure what it did, but definitely not did it fix my problem. The solution was for some kind of USB connectivity issue which i have luckily. Wasn't it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/archive/index.php/t-1077985.html Read that one .... I believe it is pretty much the problem you have?

C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem enableqxdm 0
...
OKAY [ 0.024s]
finished. total time: 0.024s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem eraseconfig
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
was my error, as was his. Strrangely, this time the first command didn't give me an error. But yeah, this is the problem pretty much yes. And there were no other solutions given, apart from the two lines in fastboot. Also, the last post stated that i have to be S-OFF to use fastboot (properly), but i am S-ON. Also, i couldn't find a way to format the card to fat, not fat32

Amphor said:
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem enableqxdm 0
...
OKAY [ 0.024s]
finished. total time: 0.024s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem eraseconfig
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
was my error, as was his. Strrangely, this time the first command didn't give me an error. But yeah, this is the problem pretty much yes. And there were no other solutions given, apart from the two lines in fastboot. Also, the last post stated that i have to be S-OFF to use fastboot (properly), but i am S-ON. Also, i couldn't find a way to format the card to fat, not fat32
Click to expand...
Click to collapse
Is your sd card partitioned correctly??? How is is set up exactly??? Make sure that your partitions are EXT 3 /4 NOT LOGICAL
You still can't access SD card in recovery?

would you define "correctly"?
Finally got a chance to test with another card and i can access sd card from recovery. And i think the dog is buried under the issue that the testcard is FAT, but mine is FAT32. though my 8GB card couldn't be FAT. So what was it?
And again, what is correctly. If i look with Gparted, then my card has 7.40 gb and 512 mb partitions (dev/sda and sdb) and i can't delete that 512 mb one

Amphor said:
would you define "correctly"?
Finally got a chance to test with another card and i can access sd card from recovery. And i think the dog is buried under the issue that the testcard is FAT, but mine is FAT32. though my 8GB card couldn't be FAT. So what was it?
And again, what is correctly. If i look with Gparted, then my card has 7.40 gb and 512 mb partitions (dev/sda and sdb) and i can't delete that 512 mb one
Click to expand...
Click to collapse
Ah.... Insert coin states requirements - A2SD+ STOCK HBOOT - stock hboot - the one with 250 mB for /system
- 1 gB ext2/3/4 partition
So your correct sd card setup is FAT 32 7GB and 1GB EXT 3/4
If I were you I would backup ALL files from Sd card to computer...
Format your sd card with gparted..
New partition - Fat 32 - 7gb
New partition - Ext 3 or 4 - 1 gb
Apply
Transfer all files back to your sd card
Put in phone and see if it's fixed?
Make sure you are using the Stock HBOOT version of insert coin... I'm surprised nothing has got you up and running so far ?!

My problem is the mounting, not the "not booting" issue, still
but yes, thats why i started mazking partitions in the first place

Amphor said:
My problem is the mounting, not the "not booting" issue, still
but yes, thats why i started mazking partitions in the first place
Click to expand...
Click to collapse
I know I didn't mention not booting....

either way, it didnt solve my problem

Well if none of the 3 suggested fixes work... I'm out though
Good luck

[Q] I need some serious help here

Guys I think I'm in deep trouble...
I updated my rom today and then rebooted my phone (I did a backup before) and then the rom didn't work. I went back to CWM and then got the message "unable to write to ums lunfile" and "cant mount /sdcard". WTH am I supposed to do?
Please answer as fast as possible, I am panicking...
Ok fixed this here: http://forum.xda-developers.com/showthread.php?t=1275632

fastboot oem enableqxdm 0
fastboot oem eraseconfig
provide some more info...
info from fastboot screen, rom etc...

[Q] Totally bricked(probably overheated)

Device is doesn't react anything. Do not light button. Nothing. Totally bricked. And seems to be totally erased. No data. No bootloader.
Tryed http://forum.xda-developers.com/showthread.php?t=1430038.
Device power up with usb_fix_parts_and_install_fff_twrp and Boot Shorting Trick. Loads TWRP. But what's next?
Tryed to put some firmwares to sdcard and install it - got lots of errors. And nothing.
Kindle Fire utility says:
ADB Status: Online
ADB Rooted: Yes
Boot Status: Unknown
P.S. If i press "reboot" or power down device - going to the beginning(Device is doesn't react anything.)
P.P.S. MB it's not brick, but hardware problem(flash memory died...)?How to check?

If you successfully did usb_fix_parts_and_install_fff_twrp, then either it should leave it with a working bootloader & recovery or your flash is somehow bad.

pokey9000 said:
If you successfully did usb_fix_parts_and_install_fff_twrp, then either it should leave it with a working bootloader & recovery or your flash is somehow bad.
Click to expand...
Click to collapse
It boots into twrp up after usb_fix_parts_and_install_fff_twrp(usb load).
but in terminal window i can see lots of messages: unable to mount /system /data /cache /sdcard.....
Flash is bad?
What can i do with it? Mainboard replacement only?

UPD: /usbboot aboot.bin u-boot.bin; ./fastboot flash boot 6_2_1rootboot.img
fails with:
writing 'boot'...
FAILED (remote: image too large for partition)
UPD2. Strange thing that flashing(fastboot flash...) different file sizes takes almost the same time(256kb sending 0.035s writing 1.231s, 16mb sending 4.111s writing 1.230s).
Does replacing flash memory chip unbrick it?

Stuck in Fastboot/No Download Mode

Hey guys !
So since i messed up with the recovery mode, i'm stucked in the fastboot with no Download mode (recovery doesnt work neither).
So after searching 3 days in the internet i found the acces to fast through adb by puting a new laf.img in order to restore the download mode and flash a stock firmware !
My problem is that when i try to enter the command on the cmd, i get severals errors, take a look :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (18432 KB)...
OKAY [ 0.581s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.615s
Also command : "fastboot boot laf.img" result to "Failed(remote: dtb not found) instead of flash write failure..
Of course i have my G3 855 32GB in download mode (but it goes into fastmode), so when i try a command, lines are added in the screen etc..
Does that mean that my laf.img don't work? I assumed that so i try several, but does it have to be the exact same one as the one who was in my phone before( v20a if i record correctly ) or could it be from any 855 32GB version ?
I also thought it could be a recognition problem as when i type "adb devices" or "adb shell" nothing is found..
If someone has any clue or a link to some guide i'll be more than joyful, thanks in advance !

Try adb fastboot when writing command hope it helps

Anik49 said:
Try adb fastboot when writing command hope it helps
Click to expand...
Click to collapse
Hey thank you so much for answering !
What do you mean by that, i already download the adb/fastboot driver and launch a cmd in the directory they are at, writing "adb fastboot" has no result neither, can you be more specific please ?

cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/

BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again:
Click to expand...
Click to collapse
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?

I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly http://forum.xda-developers.com/lg-g...-9008-t3072091

BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
Click to expand...
Click to collapse
Like @BigsyBiggins said, this is the guide which could fix your phone. HW Part is not too hard!

Anik49 said:
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly
Click to expand...
Click to collapse
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?

SisGG said:
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
Click to expand...
Click to collapse
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.

Ernesto0023 said:
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Click to expand...
Click to collapse
Well I think i'm still under warranty, so i dont wanna touch to much on the hardware.
So do you think, if i send it back without touching anything, saying i put it on charge one night and the next morning it was like this, the warranty could work?

If they found it's rooted or they understand you did something with your software your warrenty is void ?

SisGG said:
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
Click to expand...
Click to collapse
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart

miguexneox said:
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
Click to expand...
Click to collapse
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(

SisGG said:
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
Click to expand...
Click to collapse
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done

datrmon said:
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
Click to expand...
Click to collapse
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)

Ghikya said:
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Click to expand...
Click to collapse
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>

datrmon said:
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
Click to expand...
Click to collapse
It seems that your phone's bootloader is locked, you can try to execute this command: "fastboot oem unlock", and then check state with "fastboot oem device-info". But some people says that it does nothing, so you can try and check for yourself.
You can also try to boot directly an image from fastboot for eaxmple:
Code:
fastboot boot laf.img
or
Code:
fastboot boot twrp.img
So if you could successfully boot a laf image you would be able to access download mode, and if you could boot a custom recowery then you could access ADB and to try to flash other partitions, or even flash a custom rom...