Related
Hello,
i've just bricked my Desire i think
I think it got wrong in recovery mode. I chose usb mount from the recovery menu with a fat and ext3 partition (aps2sd).
Now my Desire hangs on the white screen with the green HTC letters. When i enter the recovery menu from holding volume down and the power button i can choose for the update zip to install, but then i get the error can't mount /dev/block/mmcblk0p1
Please help, this is so annoying.
Try the command in fastboot to reenable USB.
Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
Follow the USB un-bricking guide here:
http://forum.xda-developers.com/showthread.php?t=691639
Dont worry mate, i know it can be scary,
Its happened to us all, and if it hasnt, it will
Good luck with unbricking, every unbrick is a victory for XDA over HTC
JD
thnx for the replies.
I've just enabled the sdcard function so lets see how far i will come
Well it's working again This was really not cool
peewster said:
thnx for the replies.
I've just enabled the sdcard function so lets see how far i will come
Well it's working again This was really not cool
Click to expand...
Click to collapse
Great stuff, as you can see, it's not so much of a worry when there are fixes available
I haven't been bricked yet... but as JD said, there's still that chance... then i will be literally bricking it!
well the only thing i can't get to work is the actual fix.
my phone boots normally, but when i try to execute:
/data/flash_image misc /data/mtd0.img i get the following error:
mtd: rad all-zero block at 0x00000000; skipping
error reading mtd0.img
peewster said:
well the only thing i can't get to work is the actual fix.
my phone boots normally, but when i try to execute:
/data/flash_image misc /data/mtd0.img i get the following error:
mtd: rad all-zero block at 0x00000000; skipping
error reading mtd0.img
Click to expand...
Click to collapse
Are you sure you USB bricked and it's not just a bad flash that will be solved by a wipe/clear and reflash? That is, if you are able to get into recovery. As I understand it USB brickeds are still able to boot, while hanging on "quietly brilliant" is a typical bad flash/sd-card issue (had it a couple times meself). I might very, very, very well be wrong though
Mac
No this was a real usb brick. I could nog flash anything anymore, and mu usb wasn't working anymore.
I replaced the mtd0.img with a new one, and this time the script executed correctly.
I'm rebooting it now.
Just rebooted, and everything is working normal again
Great! Nothing is like the feeling of relief when things work again!
Mac
M4cr0s said:
Great! Nothing is like the feeling of relief when things work again!
Mac
Click to expand...
Click to collapse
You can say that again
No success after 1st step
MasDroid said:
Try the command in fastboot to reenable USB.
Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
Follow the USB un-bricking guide here:
http://forum.xda-developers.com/showthread.php?t=691639
Click to expand...
Click to collapse
I got this.
D:\Softwares\htc\android-sdk-windows\tools>fastboot oem enableqxdm 0
... OKAY [ 0.096s]
finished. total time: 0.096s
But, still now I'm getting
"Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
I'm trying to follow second step at the thread 691639. I have posted more info there. Please help.
Hey guys!
My SD card won't mount in Recovery mode... When I try to flash zips or partition the SD card I get the following error:
Code:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
Upon further reading, I've tried going into Fastboot (which does work thankfully) but every command I use, including:
Code:
fastboot oem enableqxdm 0
Chucks me the following error:
Code:
... FAILED (status malformed (1 bytes))
I'm totally at a loss here guys, and I'm way out of my depth with this one. Any help would be appreciated!
first try fastboot devices
to see if ur phone is detected
It does list the device in Fastboot, but not in adb shell devices :S
now re type fastboot oem enableqxdm 0
FAILED (status malformed (1 bytes))
type fastboot oem boot
then take a print screen of the writing
ur phone will reboot
Same error.
let me look for a fix
is ur desire s-off
Yup. It's running AlphaRev's 1.8 HBoot with S-OFF
HBoot version is 0.93.0001
what does fastboot devices show
dont post ur full serial number
dont post ur full serial number
dont post ur full serial number
dont post ur full serial number
dont post ur full serial number
just post the first two letters or numbers
HT*********421
Blanked of course
good ok do u have a sd card reader i.e sd to usb
do u have windows 7 or xp and are the hboot and fastboot drivers installed propery
I have all of the above. I've been installing ROMs for some time now, its only just happened after I installed AlphaRev's Hboot.
the only thing i can say is do u have a ruu for ur phone if not i can find 1 for u
I've downloaded the RUU.exe for my phone, but it requires a working ROM in order to work, of which I don't have. :-/
not true i used my ruu from fastboot usb plug
run the ruu
It's an .exe... you saying just to Run that? I've ran it and it tries to find the phone, but it can't as it searches for USB debugging, but since theres no running ROM it fails.
what os are u on win 7 or xp
Long story here. My desire has decided to become sd bricked
Hboot version is 0.93
Software is 2.29.405.5
Phone is not routed and is s-on.
I can use adb and fastboot but I cant do anything that requires the sd card. Can someone please help me in getting the sd card working again please.
John
did you already triy the "fastboot oem enableqxdm 0" command in fastboot mode?
Yes it comes back with
fastboot oem enableqxdm 0
...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
You need to have s off to use that command. Follow the root and s off guides in the development forum then try again.
Sent from my Motorola Startac running Atari 2600 software!
I've ran unrevoked and it says I am rooted and titanium backup runs.
I tried alpharev to get s off and it doesn't appear to work, it cant find my phone.
John
no you don't need s-off.
i think you are in the wrong directory. The fastboot.exe is in the folder tools,
so you have to change the directory in cmd and then "fastboot oem enableqxdm 0".
(also fastboot mode on your desire)
You tried reformatting the SD using "SD Formatter"?
Also, which ROM were you running? Some roms dont seem to boot (stuck on HTC logo screen) if theres probs with the SD card format - especially if your sd-ext is ext 4.
Can you boot into recovery? If so and you arent bothered about losing phone data, format your SD (using SDFormatter), stick something like LeeDroid 2.3d on and flash it (with full wipe).
Maybe this'll help:
http://forum.xda-developers.com/archive/index.php/t-1070863.html
Hi All,
Via a particularly stupid series of steps I've ended up with:
1) stock boot 0.93 (S-ON)
2) RA-desire-v2.0.0 recovery image which won't mount the sd card.
(Can't mount /dev/block/mmcblk0p1 etc.
3) Result of half way through alpha rev process:
AlpahRev SPLBOOT version 2.0
New NAND detected. Possibly Bravo PVT4.
Dumping old HBOOT.
Flashing AlphaRev HBOOT:
Flashing AlphaRev HBOOT: Verifying HBOOT: Old HBOOT matches.
Procedure soft-failed. We were unable to flash HBOOT, but the old BHOOT is still in place.
Reminder: your phone is not bricked. Restart the procedure and try again. You may need to restore your most recent nandroid backup from recovery.
Snag is with out sd working in recovery I can't do that.
I don't have a gold card.
Anyone know of a way out of this mess?
At least partly out of the mess via:
fastboot oem enableqxdm 0
found in a post on [email protected] forums.
Thanks due to ZiCon and sorry for the noise to everyone else.
as posted above, in fastboot, type:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Should get your SD card back up and running.
i had a similar issue with mine.. cm7 hboot, recovery and looping os.. try connecting your SD car to your computer and see if you can get the files off, then format it all as a FAT32 partition and try to repartition on the device.. it worked for me after a few tries, plus various other fiddling..
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...