Hi, i'm trying to flash by using fastboot with command prompt. I can't flash anything by useing the recovery option in hboot because it keeps taking me back to the hboot menu.
Right. I extracted the rom.zip from the RUU Rom "testruu" which went okay, it has all the images, includeing the recovery image to get it working again. but when i type in "fastboot -p (serial number) update rom.zip" which the rom.zip is located in the sdk tools folder. it comes up with the error
"Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in "MS-DOS symbols.........."
Any ideas? i tried flashing other rom's but they don't contain the "android-info.txt" within the image zip package.....
Please help because my phone is 100% dead with no recovery working and stuck at the htc logo screen.
so no one knows how to flash in fastboot? well great.
Enter fastboot then plug Desire to your computer and run official RRU (*.exe file)
That should help
Cheers
Hey guys,
I am trying to s-off my girlfriends Wildfire S.
MARVEL PVT SHIP S-ON RL
HBOOT-1.009.0099
MICROP-041
RADIO-7.57.39.10M
FEB 9 2012 18:29:31
I am following the directions from htcdev.com/bootloader
I got to the point where I am supposed to "get_identifier_token"
Now my phone is connected as it should be, I am in "fastoot usb".
Still, the only thing happens is that I get the following message in command prompt: "waiting for device". Nothing happens. I tried to restart PC and phone again: same problem.
Does anyone have an idea about what I'm doing wrong? I'm stuck.
Okay. Now I unlocked bootloader. I think the problem was USB-debugging was not turned on.
Trying to run clockworkmod, but keep getting error messages:
"you must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or "system/xbin/su".
When I try to flash clockworkmod recovery I get the following error:
"An error occured while attempting to run privileged commands".
My deviced is with unlocked bootloader, buy of course still S-ON. I understood from the threads around that that's not a problem.
http://forum.xda-developers.com/showthread.php?t=1927757&highlight=root
How can I install a custom ROM?
How can I install data2sd?
Can someone help? Thanks a lot.
szaboagoston said:
Okay. Now I unlocked bootloader. I think the problem was USB-debugging was not turned on.
Trying to run clockworkmod, but keep getting error messages:
"you must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or "system/xbin/su".
When I try to flash clockworkmod recovery I get the following error:
"An error occured while attempting to run privileged commands".
My deviced is with unlocked bootloader, buy of course still S-ON. I understood from the threads around that that's not a problem.
http://forum.xda-developers.com/showthread.php?t=1927757&highlight=root
How can I install a custom ROM?
How can I install data2sd?
Can someone help? Thanks a lot.
Click to expand...
Click to collapse
-------------------------------------------------------------
Hi, what you need to do is go into your bootloader as you usually do, Volume - and Power Button, plug your USB and go into fastboot USB. Then you need to create a file on you C: drive called "fastboot" and put the following files in there "adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe" and your recovery image, I suggest you use the offical clock work mod recovery which is available here,
if you do not have these files you can download them from here,
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
http://forum.xda-developers.com/showthread.php?t=1474956
once you do this then open a command dos window by typing cmd in the start search box of windows.... once the command window opens go to the right folder of C:\fastboot> where you saved the files.
Then as your phone is in fastboot USB and you are in the command window C:\fastboot>, type in the command window the following,
fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
Then press enter, what you should see is the below,
c:\fastboot>fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
sending 'recovery' (2224 KB)... OKAY
writing 'recovery'... OKAY
If you follow the above then you should have clockworkmod recovery, you can then take the USB out and go back to the hboot in you bootloader and choose recovery under hboot by navigating with the volume button and power button.
I do need to inform you though that if you are one of the unlucky WFS owners that get the "Black Screen Recovery" issue where you go into recovery and you only get a black screen and you tactile buttons are on then you need to follow the bellow method to be able to see you recovery on you PC screen than on your phone.
http://forum.xda-developers.com/showthread.php?t=1781105
Also here is a youtube video of what I mean
http://www.youtube.com/watch?v=HgrPctWKW8E
I know all this as I had the same issue and this helped me. Now I feel that I need to inform you about other issues... When you unlock the bootloader you can't flash a ROM and then just switch your phone on and it boots into the new ROM, there is a process you need to follow.
When you choose your ROM, and not all ROMs work with the Wildfire S new batch of phone as I had to find out the hard way, you need to flash your ROM and then open the .zip file of your phone copy the boot.img of the ROM paste it in the c:\fastboot> directory and again in the command window type,
fastboot flash boot boot.img
You will see the below,
c:\fastboot>fastboot flash boot boot.img
sending 'boot' (2224 KB)... OKAY
writing 'boot'... OKAY
Then type,
c:\fastboot>fastboot reboot
And your phone will reboot into the new ROM allow 10 to 15 minutes... BE PATIENT.
I hpe the above helps you.
I am currently having the below problems just for your info if you have the same...
http://forum.xda-developers.com/showthread.php?t=1948038
success
Karavasileiadis said:
-------------------------------------------------------------
Hi, what you need to do is go into your bootloader as you usually do, Volume - and Power Button, plug your USB and go into fastboot USB. Then you need to create a file on you C: drive called "fastboot" and put the following files in there "adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe" and your recovery image, I suggest you use the offical clock work mod recovery which is available here,
if you do not have these files you can download them from here,
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
http://forum.xda-developers.com/showthread.php?t=1474956
once you do this then open a command dos window by typing cmd in the start search box of windows.... once the command window opens go to the right folder of C:\fastboot> where you saved the files.
Then as your phone is in fastboot USB and you are in the command window C:\fastboot>, type in the command window the following,
fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
Then press enter, what you should see is the below,
c:\fastboot>fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
sending 'recovery' (2224 KB)... OKAY
writing 'recovery'... OKAY
If you follow the above then you should have clockworkmod recovery, you can then take the USB out and go back to the hboot in you bootloader and choose recovery under hboot by navigating with the volume button and power button.
I do need to inform you though that if you are one of the unlucky WFS owners that get the "Black Screen Recovery" issue where you go into recovery and you only get a black screen and you tactile buttons are on then you need to follow the bellow method to be able to see you recovery on you PC screen than on your phone.
http://forum.xda-developers.com/showthread.php?t=1781105
Also here is a youtube video of what I mean
http://www.youtube.com/watch?v=HgrPctWKW8E
I know all this as I had the same issue and this helped me. Now I feel that I need to inform you about other issues... When you unlock the bootloader you can't flash a ROM and then just switch your phone on and it boots into the new ROM, there is a process you need to follow.
When you choose your ROM, and not all ROMs work with the Wildfire S new batch of phone as I had to find out the hard way, you need to flash your ROM and then open the .zip file of your phone copy the boot.img of the ROM paste it in the c:\fastboot> directory and again in the command window type,
fastboot flash boot boot.img
You will see the below,
c:\fastboot>fastboot flash boot boot.img
sending 'boot' (2224 KB)... OKAY
writing 'boot'... OKAY
Then type,
c:\fastboot>fastboot reboot
And your phone will reboot into the new ROM allow 10 to 15 minutes... BE PATIENT.
I hpe the above helps you.
I am currently having the below problems just for your info if you have the same...
http://forum.xda-developers.com/showthread.php?t=1948038
Click to expand...
Click to collapse
Thanks a lot for the quick and professional answer. By the time I read it, I managed to root.
I used rezo609's all-in-one utility, which I found in at this location:
http://forum.xda-developers.com/showthread.php?t=1697985
I got the advice from this thread:
http://forum.xda-developers.com/showthread.php?t=1927757
I installed the Speeddroid ROM and data2SD as described here:
http://forum.xda-developers.com/showthread.php?t=1932534&highlight=data2sd+install
The result: so far everything working. It looks like a new phone!
stuck to root
Hi,
I have the same situation here.
But Which tool do you run of the [UTILITY]rezo609's All-In-One Utility ? (http://forum.xda-developers.com/showthread.php?t=1697985&page=3)
In the whole topic there is no how to.
I managed to unlock the bootloader, and clockwork recovery is also on there.
I just want to root the phone (not to put an other rom)
Thanks in advance,
I'm confused.... I'm following all the instructions using the toolkit v10.
I was able to unlock the bootloader without an issue, but when it comes to rooting, I'm having problems.
I use option 16 for the build, then option 4 to root. In the fastboot screen, the bottom Fastboot status says FAILInvalid Command as soon as it pulls up, then it goes to "reboot" after the 30 second wait.
It doesn't reboot automatically, so I press the power button to reboot it myself. then it reboots and then goes back into fastboot with the fail invalid command. Then this comes up:
downloading 'boot.img'
FAILED (remote: Invalid Command)
finished. total time: 0.006s
Waiting for device.
I'm at a loss. I feel like last time did this, I had to get the factory image and the boot.img file from somewhere and place them in the folders within the c:/galaxy nexus toolkit folder.
Any help would be greatly appreciated!
Thanks,
Nick
put on your big boy pants and root your phone this way:
http://forum.xda-developers.com/showthread.php?t=1529058
I have tried that... i get a similar message:
sending 'recovery' (5990 KB)
FAILED (remote: Invalid Argument)
finished. total time: 0.006s
then the fastboot status on the phone changes to "download 005d9800"
not sure what to make of that either.
is the cwm/twrp image actually named recovery? and is it in the fastboot.exe directory?
are you typing the command correctly? ( fastboot flash recovery nameofrecovery.img
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
waldo22 said:
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
Click to expand...
Click to collapse
Yep that's it
Sent from my Galaxy Nexus using Tapatalk 2
I'm guessing you mean that that's the correct way to do it and not, "yep that's you're problem." Any ideas where to go from there?
crazy... I switched to a different computer, and used the most up to date pdanet drivers, and it's going like a champ.
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...
Hello,
Many many many moons ago i decided to try install LineageOS on my old pixel c, then the world when weird and the tablet has lived in a drawer, today it came out and i can't remember where i got up to so looking for guidance before i kill it.
This is what i do know:-
1. Doesn't have an OS as it won't boot properly
2. Get to a recovery menu but trying to boot to "Android recovery" doesn't work (just reboots)
3. Message in the recovery menu states "OS on your tablet is damaged. Needs Recovery" this is along side the Product name, Hardware Version, Bootloader Version and Lock State.
And advice on where to start very much appreciated.
I took another punt at this, tablet is "waiting for fastboot command...." from my mac when attempting to write the recovery image using the following: ./fastboot flash recovery twrp-3.7.0_9-1-dragon.img from my Mac i hit the following error:-
Sending 'recovery' OKAY
Writing 'recovery' FAILED (remote: 'unsupported command')
fastboot: error: command failed
./fastboot oem unlock says it is unlocked already