Hi all,
My G3 seems to have bricked itself somehow when i wasn't even messing with it.
Anyway, looks like a hard brick, getting failed to open eMMC partition in boarddiag software. Does this mean its flash storage is knackered?
Phone still under warranty, so i guess its worth a try getting it replaced. If eMMC is knackered, does that mean they wont be able to see anything that was on the device or get anything back off it? Is eMMC the onboard storage?
Cheers all
MMM
Mistermoleymole said:
Hi all,
My G3 seems to have bricked itself somehow when i wasn't even messing with it.
Anyway, looks like a hard brick, getting failed to open eMMC partition in boarddiag software. Does this mean its flash storage is knackered?
Phone still under warranty, so i guess its worth a try getting it replaced. If eMMC is knackered, does that mean they wont be able to see anything that was on the device or get anything back off it? Is eMMC the onboard storage?
Cheers all
MMM
Click to expand...
Click to collapse
If your phone doesn't charge, doesn't vibrate, doesn't power on, doesn't get into download mode (Battery out, back in, hold VOLUME UP and plug usb cable in) it is a hard-brick.
If you can't use QCOM 9008 to reflash using board diag then it could be an EMMC failure.
If EMMC is fried or it is destroyed they can't see anything. They won't even invest time in this. You will get a replace since they don't waste time with this kind of stuff they change the phone or the motherboard.
For your knowledge:
eMMC comes from embedded Multi-Media Controller. This means the chip is a combination of non volatile memory (your storage space) and a micro controller encapsulated in the chip (the controller handles the storage etc; won't get into this too much). Yes the eMMC is the onboard storage but it also contains a lot of partitions. Think of the eMMC like a hard-disk it has a lot of partitions including /data (the internal storage) /system (where the os lies), Primary GPT. Modem, Secure boot chain (SBL1, Aboot (Android bootloader), etc).
Hope this clarifies the stuff for you.
Peace out,
neutrondev
neutrondev said:
If your phone doesn't charge, doesn't vibrate, doesn't power on, doesn't get into download mode (Battery out, back in, hold VOLUME UP and plug usb cable in) it is a hard-brick.
If you can't use QCOM 9008 to reflash using board diag then it could be an EMMC failure.
If EMMC is fried or it is destroyed they can't see anything. They won't even invest time in this. You will get a replace since they don't waste time with this kind of stuff they change the phone or the motherboard.
For your knowledge:
eMMC comes from embedded Multi-Media Controller. This means the chip is a combination of non volatile memory (your storage space) and a micro controller encapsulated in the chip (the controller handles the storage etc; won't get into this too much). Yes the eMMC is the onboard storage but it also contains a lot of partitions. Think of the eMMC like a hard-disk it has a lot of partitions including /data (the internal storage) /system (where the os lies), Primary GPT. Modem, Secure boot chain (SBL1, Aboot (Android bootloader), etc).
Hope this clarifies the stuff for you.
Peace out,
neutrondev
Click to expand...
Click to collapse
I am trying to fix the very same issue as this guy and BoardDiag will not pass the EMMC test at all.
======== EMMC TEST START Failed to open partition from EMMC TEST aborted!! Elapsed time: 2 seconds
No matter what I do it won't get past this part. Is there something I am not doing right possibly or a way to verify my EMMC is actually busted?
AndyVanAndy said:
I am trying to fix the very same issue as this guy and BoardDiag will not pass the EMMC test at all.
======== EMMC TEST START Failed to open partition from EMMC TEST aborted!! Elapsed time: 2 seconds
No matter what I do it won't get past this part. Is there something I am not doing right possibly or a way to verify my EMMC is actually busted?
Click to expand...
Click to collapse
I don't know really. I just searched the web and telling you from my previous experience. I didn't hard brick my G3. It depends how you bricked it. If you did nothing that could brick it then it's likely you have a broken EMMC. Nothing you can do to see if it's damaged or not.
Mine was busted..... Sent back to Amazon to fix under warranty.
Sent from my LG-D855 using Tapatalk
i got yesterday a d850 with emmc test fail.
the set in 9008 qusb mode... ap test pass but emmc test fail....
I m thinking of doing emmc repair through emmc pinout method using medusa pro.... I suggest u to consult some jtag expert... this may work... but on qusb mode this emmc not so much supporting through such softwares..
I got d851 previous days... that got in 9008 mode during flashing marswalow file.... but that not repaired thfrough boardiag although that pass emmc test also... and flash through diag also...
then I come to point ... now a time this set boot loader is not softwarely accessible. or some manufacturing hardware issue... if any possible solution I get .. I will update u dears..
im late but if anyone else has this problem it means ur emmc is corrupted or has some issues on capacitors in motherboard or it could be in emmc. happened to me too i just overheated the emmc manually with hot glue guns body then emmc got pass somehow but after like using phone 1-2 hours i wanted to install lineage os and im flashed twrp then i was not able to install lineage from twrp because of some problems of port or twrp and i stuck at bootloop and i booted to download mode and started flashing but flash tool gave me LAF_READ_GPT_FAILED or something like this and it was stuck at %0 when i closed phone and tried to reboot it doesnt opened and i attached it to computer and qualcomm qdloader 9008 appeared i tried with boarddiag again but now heat trick doesnt work or its an motherboard issue so dont mess it just replace motherboard or buy new phone and please note almost every LG phone having issues like touchscreen, emmc and more because its poorly designed and sometimes your phone has wrong motherboard in it.
Related
My phone is bricked,when i connect it to pc its show in device manager Qualcomm 9008 mode.How to unbrick it!
Best regards! :crying::crying:
Dzeki064 said:
My phone is bricked,when i connect it to pc its show in device manager Qualcomm 9008 mode.How to unbrick it!
Best regards! :crying::crying:
Click to expand...
Click to collapse
same here
try if you have warranty.. or try jtag box.. there isnt a way to fix this yet.. funnt thing on G2 shortening a circuit brings back to life..
there's no way to fix it? really o,O
I wrote a guide a few months ago for the Lg G3, isn't it possible to use it with the right DLlL and TOT/KDZ file?
https://open-freax.fr/guide-unbrick-your-lg-g3/
emmc chip is faulty or corrupt.
I fixed mine by heating up with hot air soldering gun until solder reflow.
cloud1250000 said:
there's no way to fix it? really o,O
Click to expand...
Click to collapse
Same here on my h811. I followed instruction almost exactly but missed 1 thing. It looks like there is no way to fix it by reflashing. Having soft bricked Samsung,Moto and LG g2 and finding ways to recover all of them,it was a shock that this happened to my g4. Androidbrick.com also mentions that we are out of luck.
Other people have sent it back and got it fixed. You can go to LG website to apply for repair. Did the same today and will update the outcome.
When I tried to reverse the sbl1 image, I saw some instruction about booting from mmc1 (I have no clue if it's from a usb stick or the sdcard)...
(since I have really ****ty skill, I had no success in reversing anything related to the bootchain, but I can still read clear string...)
I guess it should be possible to write a copy of the g4 system on it and then boot from it. Unless lg kept the code in their bootloader but patched it out.. (would be stupid tho...)
cloud1250000 said:
When I tried to reverse the sbl1 image, I saw some instruction about booting from mmc1 (I have no clue if it's from a usb stick or the sdcard)...
(since I have really ****ty skill, I had no success in reversing anything related to the bootchain, but I can still read clear string...)
I guess it should be possible to write a copy of the g4 system on it and then boot from it. Unless lg kept the code in their bootloader but patched it out.. (would be stupid tho...)
Click to expand...
Click to collapse
That's pretty much exactly how to fix the problem from what I seen from the people who are withholding information. I was able to get as far as make the phone turn on and Secure Boot Error 1006. I also at one point got it to detect as LGE Android NET device, unfortunately I didn't make a backup of the SD card before flashing another partition to try and go further. I also got the recovery to popup and attempt to restore default settings, but it just reboots into the 1006. I also created the entire G4 system partition table and everything from a US991 KDZ file and got the same SBE 1006 as I did with the LS991 dump.
I think perhaps LG is working with a universal unlocked boot loader on the SD card to bring up download mode and flash whatever stock firmware. They are for sure plugging into the SD card and then flashing via USB
Noksucow1 said:
That's pretty much exactly how to fix the problem from what I seen from the people who are withholding information. I was able to get as far as make the phone turn on and Secure Boot Error 1006. I also at one point got it to detect as LGE Android NET device, unfortunately I didn't make a backup of the SD card before flashing another partition to try and go further. I also got the recovery to popup and attempt to restore default settings, but it just reboots into the 1006. I also created the entire G4 system partition table and everything from a US991 KDZ file and got the same SBE 1006 as I did with the LS991 dump.
I think perhaps LG is working with a universal unlocked boot loader on the SD card to bring up download mode and flash whatever stock firmware. They are for sure plugging into the SD card and then flashing via USB
Click to expand...
Click to collapse
If it can help I had the 9008 problem on my LG G4 H811. First there was no dump to do jtag , I found mmcblk0 files somewhere on xda , so I took a 32 gb SD card, flashed it with PrimaryGPT ( taken from extracted 10N H811 firmware) using win32diskimager and then I flashed each of the 50 first mmcblk0 to the SD card using dd command of Ubuntu, put the SD card into the phone and bam, phone is alive and it can entre download mode. I tried to flash a 10N firmware but the firmware goes to the SD card, I finally flashed a custom recovery, custom rom, the phone internal memory became the SD card, listing /dev/block folder does not show any trace of the emmc, so I think that my emmc is dead
bottom line, like you, I think that the solution is with the SD card method, the inspiration came from the optimus g pro boot repair with some creativity, but I think that something is missing .
leptdre said:
If it can help I had the 9008 problem on my LG G4 H811. First there was no dump to do jtag , I found mmcblk0 files somewhere on xda , so I took a 32 gb SD card, flashed it with PrimaryGPT ( taken from extracted 10N H811 firmware) using win32diskimager and then I flashed each of the 50 first mmcblk0 to the SD card using dd command of Ubuntu, put the SD card into the phone and bam, phone is alive and it can entre download mode. I tried to flash a 10N firmware but the firmware goes to the SD card, I finally flashed a custom recovery, custom rom, the phone internal memory became the SD card, listing /dev/block folder does not show any trace of the emmc, so I think that my emmc is dead
bottom line, like you, I think that the solution is with the SD card method, the inspiration came from the optimus g pro boot repair with some creativity, but I think that something is missing .
Click to expand...
Click to collapse
YES! This is exactly what I wanted to test, even if the emmc is dead, your phone is still "fine." Use the sd slot and it will rise from the dead.
cloud1250000 said:
YES! This is exactly what I wanted to test, even if the emmc is dead, your phone is still "fine." Use the sd slot and it will rise from the dead.
Click to expand...
Click to collapse
to do such thing, we need a database of phone dumps for now i need H815 partitions (mmcblk0)
yeah maybe we'll have more chance if we make a thread in the dev place.
it could help alot of people with bootloop problem..
I can fix these phones talk me on WhatsApp +918989874040
Sent from my LS-4004 using Tapatalk
https://mega.nz/#F!yZ9iERoa!q9eoP4uQoPLRqyiabBIHaA
I have got a H818P bricked
Anyone can provide a solution on how to unbrick it? as this thread just provides H815 unbrick solution:crying:
:crying:
I had no luck at all with mine. Theres no indication the card is being read, phone just gets to boot screen then turns off again after 15-20 seconds then does nothing till the battery is taken out and left for a while. Then the same thing again.
mickrick said:
I had no luck at all with mine. Theres no indication the card is being read, phone just gets to boot screen then turns off again after 15-20 seconds then does nothing till the battery is taken out and left for a while. Then the same thing again.
Click to expand...
Click to collapse
Have you tried starting your phone in download mode?
hiker123 said:
Have you tried starting your phone in download mode?
Click to expand...
Click to collapse
Better still, I got it repaired under warranty.
sup all was screwing with some crap i shouldnt have and have bricked my phone. the pwr+vol does nothing
plug in to charger gives no led light
plugin to computer does not give emmc access
phone is prob trash but i like tinkering neway
i have a dd copy of all partitions 1-65 befor crash
phone is s-off and rooted
so my thought is how to push the dd imgs to the phone
i messed with partition 1 and 54 so is there a way to unbrick
thx in advanced
I cannot make any promises that it will work but we can try something.
I discovered that if you flash a sd card with the dragonboard 410c -->> DB-Boot-Tools
And use the partitions backups you have as files.
It is possible to make a sd card that will boot.
some qualcomm devices will boot the sdcard if the emmc is dead.
What partition did you trash?
Aboot ??
---------- Post added at 10:25 PM ---------- Previous post was at 10:16 PM ----------
bow2evil said:
sup all was screwing with some crap i shouldnt have and have bricked my phone. the pwr+vol does nothing
plug in to charger gives no led light
plugin to computer does not give emmc access
phone is prob trash but i like tinkering neway
i have a dd copy of all partitions 1-65 befor crash
phone is s-off and rooted
so my thought is how to push the dd imgs to the phone
i messed with partition 1 and 54 so is there a way to unbrick
thx in advanced
Click to expand...
Click to collapse
I forgot to mention.
If you are in 900E mode !!!
Then you need to short the data positive usb line to the ground of the usb cable.
Press power button 3 to 5 seconds
New device will show in windows dev manager.
After new device shows you need to install qualcomm drivers.
After all is done windows will show hs usb qdl9008
Unfortunatly I believe the firehose to flash in emergency dl mode has to be signed.
I have a couple ideas but i nedd to know what partition you fried.
must be
aboot
hosd
tz
radio
Which one did you fry?
mmcblk0p1
i was pissed off at the phone and started self destruction mode lol
sorry it took so long to get back
i got a xt1254 been hacking it lately
i still have a dd dump of each partition one with s-off and one with s-on all 58 something partitions
didnt know where the s-off bit was stored so a backed everything
figured that htc would want the users to feel better then haha you got a brick?
but the lack of a firehose proves it
BTW removing phones battery while connected to computer results in 9008 mode as well i believe
woke up to this green screen of death, pulled out the battery, and phone is dead since then.
no combination of buttons does anything.
The only picture i get the phone to display is when i plug it into the pc without a battery i see the yellow triangle next to the empty battery.
Whenever i put the battery in its solid black, not even the leds light up.
Anyone know of any way to get it into download mode? or is it dead?
Necromancer3 said:
woke up to this green screen of death, pulled out the battery, and phone is dead since then.
no combination of buttons does anything.
The only picture i get the phone to display is when i plug it into the pc without a battery i see the yellow triangle next to the empty battery.
Whenever i put the battery in its solid black, not even the leds light up.
Anyone know of any way to get it into download mode? or is it dead?
Click to expand...
Click to collapse
You can try shorting a pin on the motherboard, getting into qualcomm 9008 mode, and then manually loading the proper partitions via the board diag tool listed in the instructions here... https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
To be honest though...it may be time for a new phone. If it randomly crashed on you and went to the Demigod most likely one of the chips is dead/dying or the solder has opened up(common g3/lg problem). You can test if it is a solder issue by putting light pressure on the board near the SoC, memory, and/or PMIC chips and powering it up; if it shows any signs of life then you have bad solder connection and need a new board.
startswithPendswithOOH said:
You can try shorting a pin on the motherboard, getting into qualcomm 9008 mode, and then manually loading the proper partitions via the board diag tool listed in the instructions here... https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
To be honest though...it may be time for a new phone. If it randomly crashed on you and went to the Demigod most likely one of the chips is dead/dying or the solder has opened up(common g3/lg problem). You can test if it is a solder issue by putting light pressure on the board near the SoC, memory, and/or PMIC chips and powering it up; if it shows any signs of life then you have bad solder connection and need a new board.
Click to expand...
Click to collapse
So there is no way i can make adb work from download mode? The device is recognized but in the list of driver installed does not appers "adb". I have some importants file on it and really need to recover it
marsio95 said:
So there is no way i can make adb work from download mode? The device is recognized but in the list of driver installed does not appers "adb". I have some importants file on it and really need to recover it
Click to expand...
Click to collapse
What is the device recognized as? If it is listed as a qualcomm device you are probably stuck and need to follow the tutorial I linked previously. If you see androidnet, LGE, or something that looks like your device then you may get lucky and just need the right driver(s) for your PC.
If you can find a way to get download mode working again(shorting the pin and loading the proper partitions should work) you should be able to recover your files by flashing a kdz and choosing the "normal flash"
option with the LG flash tool(CSE option &/or TOT flash will erase everything)... https://forum.xda-developers.com/showthread.php?t=2797190
*Just try to flash the same version of the software you were running at the time so you can avoid any conflicts; if you can't remember the exact SW version at least flash the correct android version (kit kat, lollipop, marshmallow, nougat).
startswithPendswithOOH said:
What is the device recognized as? If it is listed as a qualcomm device you are probably stuck and need to follow the tutorial I linked previously. If you see androidnet, LGE, or something that looks like your device then you may get lucky and just need the right driver(s) for your PC.
If you can find a way to get download mode working again(shorting the pin and loading the proper partitions should work) you should be able to recover your files by flashing a kdz and choosing the "normal flash"
option with the LG flash tool(CSE option &/or TOT flash will erase everything)... https://forum.xda-developers.com/showthread.php?t=2797190
*Just try to flash the same version of the software you were running at the time so you can avoid any conflicts; if you can't remember the exact SW version at least flash the correct android version (kit kat, lollipop, marshmallow, nougat).
Click to expand...
Click to collapse
maybe you give me the solution !!! Yes i can get in the download mode anytime i want ; the device is recognized as Lge driver . O i try to flash the right kdz file and hope it will good
Hey all, I was wondering if some one wanted to be very kind and provide a backup of emmcblk0 for me. I bricked my Z2F by some silly means. I am hoping to not have to have motorola replace it for money because it is in the dreaded Qualcomm USB Loader 9008 mode and thus fixable, technically. Ive read some success with moto Z and moto X for writing a backup of the emmc to an img file and writing that to an SD card.
I really want to contribute to the Z2F, but I cant really do that with a dead device.
You may ask, how did I brick my phone if I followed the rules. Turns out you cant switch to slot b in TWRP, otherwise you get a boot loop, and then try to use adb to switch back to slot a. You must flash a ROM again for it to not enter the 9008 mode. I found out the hard way, and I would hate to spend money on a replacement device if the current one is still salvageable.
Thanks for helping me through my momentary stupidity.
How do you make a emmcblk0 back up?
You must be rooted and then run something like:
"adb shell
su
dd if=/dev/block/mmcblk0 of=/some/file/directory bs=1m"
gbuscrizist said:
Hey all, I was wondering if some one wanted to be very kind and provide a backup of emmcblk0 for me. I bricked my Z2F by some silly means. I am hoping to not have to have motorola replace it for money because it is in the dreaded Qualcomm USB Loader 9008 mode and thus fixable, technically. Ive read some success with moto Z and moto X for writing a backup of the emmc to an img file and writing that to an SD card.
I really want to contribute to the Z2F, but I cant really do that with a dead device.
You may ask, how did I brick my phone if I followed the rules. Turns out you cant switch to slot b in TWRP, otherwise you get a boot loop, and then try to use adb to switch back to slot a. You must flash a ROM again for it to not enter the 9008 mode. I found out the hard way, and I would hate to spend money on a replacement device if the current one is still salvageable.
Thanks for helping me through my momentary stupidity.
Click to expand...
Click to collapse
So do u have emmc bulk img backup now. if yes i'm in dire need please provide, Thanks!
Hello!
I have flashed a firmware for my HTC 10 extracted from a ruu.zip, but the format of these zip should be incorrect and now the phone doesnt boot ** ultrafacepalm **. No boot, no screen on, no charge led on...
From my experience with other phone (s4 mini) I think maybe put a dump emmc from an equal mobile on my sdcard maybe can get it started and run a ruu.exe or ruu.zip to restore it.
Could someone make a dump of an HTC 10 32G international unlocked emmc please? I would like to try this, the next thing would be to send it to HTC SAT.
I tried to recreate the partition table of the HTC10 with fdisk by sectors and load the content of the different firmware files using dd, I dont know if it is possible... Maybe I need to modify the RAMDISK to indicate that I want to start reading the SD partitions and not the EMMC...
https://forum.xda-developers.com/htc-10/how-to/htc-10-partition-table-t3374048
Thank you!!
Are you able to access download mode? Volume Down+Power button until you see small gray HTC logo, then release both buttons. If you can please let me know as its possible you can execute the command fastboot getvar all in cmd
Hel10s said:
Hello!
I have flashed a firmware for my HTC 10 extracted from a ruu.zip, but the format of these zip should be incorrect and now the phone doesnt boot ** ultrafacepalm **. No boot, no screen on, no charge led on...
From my experience with other phone (s4 mini) I think maybe put a dump emmc from an equal mobile on my sdcard maybe can get it started and run a ruu.exe or ruu.zip to restore it.
Could someone make a dump of an HTC 10 32G international unlocked emmc please? I would like to try this, the next thing would be to send it to HTC SAT.
I tried to recreate the partition table of the HTC10 with fdisk by sectors and load the content of the different firmware files using dd, I dont know if it is possible... Maybe I need to modify the RAMDISK to indicate that I want to start reading the SD partitions and not the EMMC...
https://forum.xda-developers.com/htc-10/how-to/htc-10-partition-table-t3374048
Thank you!!
Click to expand...
Click to collapse
Nope, that's the problem, smartphone it's completely dead, no fastboot, no screen on, no led on...
It sound like a I need to send to HTC for repairmen, maybe motherboard replacement. Daaamn, I did this thousand of times, but now I just fu** it
I recreate the partition table inside the SD card, cause with a s4 mini I was able to boot up in similar situation, Qualcomm soc, now I don't know if this it's possible with the HTC 10.
ayyu3m said:
Are you able to access download mode? Volume Down+Power button until you see small gray HTC logo, then release both buttons. If you can please let me know as its possible you can execute the command fastboot getvar all in cmd
Click to expand...
Click to collapse
Hel10s said:
Nope, that's the problem, smartphone it's completely dead, no fastboot, no screen on, no led on...
It sound like a I need to send to HTC for repairmen, maybe motherboard replacement. Daaamn, I did this thousand of times, but now I just fu** it
I recreate the partition table inside the SD card, cause with a s4 mini I was able to boot up in similar situation, Qualcomm soc, now I don't know if this it's possible with the HTC 10.
Click to expand...
Click to collapse
Personally i think you might bricked it messing with the partition tables and not by flashing the wrong firmware. A wrong firmware doesn't pass through if the CID and MID doesn't match, even when it has a different region code it won't flash.
Bricking a htc with an incorrect firmware is nearly impossible......
Hel10s said:
Nope, that's the problem, smartphone it's completely dead, no fastboot, no screen on, no led on...
It sound like a I need to send to HTC for repairmen, maybe motherboard replacement. Daaamn, I did this thousand of times, but now I just fu** it
I recreate the partition table inside the SD card, cause with a s4 mini I was able to boot up in similar situation, Qualcomm soc, now I don't know if this it's possible with the HTC 10.
Click to expand...
Click to collapse
Hi,
I have had the same result (No Boot, No Charging Led, Device recognised as Qualcomm device instead of HTC Phone, etc...)
I have tried several method and for our HTC model, it does not exist yet a method/tool to reflash motherboard.
I have had to pass via HTC Support and they changed my motherboard... fortunately under warranty
Does your device is recognised when plugged on PC ?
Check : https://forum.xda-developers.com/showpost.php?p=75038281&postcount=6
chrisftlse said:
Hi,
I have had the same result (No Boot, No Charging Led, Device recognised as Qualcomm device instead of HTC Phone, etc...)
I have tried several method and for our HTC model, it does not exist yet a method/tool to reflash motherboard.
I have had to pass via HTC Support and they changed my motherboard... fortunately under warranty
Does your device is recognised when plugged on PC ?
Check : https://forum.xda-developers.com/showpost.php?p=75038281&postcount=6
Click to expand...
Click to collapse
Yes! That's the result, no boot, no led and it's recognized as 'Qualcomm HSUSB 9008' or similar name.
Yeah, maybe that's the solution, send to HTC and wait for a motherboard replacement (under warranty :fingers-crossed
On LG devices, I was able to restore to stock from QHS_USB 9008 mode several times. I have no idea if the same special Windows program, along with the files from the stock RUU can do the job. Google QHS_USB 9008 HTC and see if you find anything.