Related
The eMMC module "crashed" in my Nexus 7, and it got into write-locked mode as much as I can tell.
Actually I get -110 on init, I can't reach the block devices in adb, as it says it's busy.
What I can do:
Get into bootloader mode
Get into recovery mode (The screen stays at TWRP logo, but I can adb shell in it, but I can't read or write the mmc blocks)
Now this is not much help in write locked mode of course, but then I ran into this thread.
I could try the same with my Nexus 7, but I need some help:
Reset command (if there is any) for H26M64003DQR (I guess that's what is inside the 32GB version)
A dump from the boot and some other neccesary partitions.
As an alternative if someone knows the pinouts of eMMC chip I can use to solder to an sd card reader, it would help a lot.
As a second alternative, if anyone knows a way to boot right from usb, it would help too.
If anyone could help me with this, I would be really grateful.
Having the same issue and need help
I'm also having the exact same issue. No access to the eMMC at all -- all attempts to mount or read from it results in I/O error (-110 error when checking via dmesg).
It all happened randomly and I thought it was just a random restart. But after it was stuck for 30 minutes on the Google logo, I found out something was not right.
Does someone have any ideas? I would be **very** interested and grateful if I can get this fixed. The warranty just expired two months ago... :crying:
leoetlino said:
I'm also having the exact same issue. No access to the eMMC at all -- all attempts to mount or read from it results in I/O error (-110 error when checking via dmesg).
It all happened randomly and I thought it was just a random restart. But after it was stuck for 30 minutes on the Google logo, I found out something was not right.
Does someone have any ideas? I would be **very** interested and grateful if I can get this fixed. The warranty just expired two months ago... :crying:
Click to expand...
Click to collapse
I've tried everything, and as far as I can tell, you have 2 options:
Solder a microsd card to the proper pins on the motherboard. (When I looked, nobody knew those pins, maybe there is some development since then)
Buy a new motherboard. - That's what I did, it was about 75$ from eBay. It's working beautifully since.
Xmister said:
I've tried everything, and as far as I can tell, you have 2 options:
Solder a microsd card to the proper pins on the motherboard. (When I looked, nobody knew those pins, maybe there is some development since then)
Buy a new motherboard. - That's what I did, it was about 75$ from eBay. It's working beautifully since.
Click to expand...
Click to collapse
I think I'll buy a new motherboard: is this one [1] okay?
Also, would you mind writing up a quick guide as to how to change the motherboard? I've found a video on YouTube for disassembling but unsure on how to change the motherboard safely. Thanks!
L i n k s (sorry, but there's a restriction; you know what to do with the l i n k s):
[1] www-ebay-fr_itm/ASUS-Google-Nexus-7-tablet-Gen-2-2013-16gb-motherboard-logic-board-100-working-/271623781886
[2] www-youtube-com_watch?v=uv3u78YNUHk
Yes, it's okay.
I've done the disassembling from a youtube video too. Just be careful, the case can be easily cracked on the corners. Memorize(or take photo from) every cable's place. There is a few hidden screws holding parts of the MB you should be aware of, but you'll find them if you search.
It's not that hard, just be patient and gentle.
Good luck!
Thank you! I'll try this and hope I can revive my Nexus 7.
Did you also try booting from a USB flash driver through an OTG cable before replacing the motherboard? I'm just curious what you did end up trying when you say you tried everything.
I'm not the OP, but as I've had the same issue, I can definitely say it wouldn't have helped, since it was a hardware failure.
Hello all, I have been a lurker for quite a while here. I own an Xperia M (Rooted, Unlocked BL running CM11). I was feeling adventurous and started messing with the partition table hoping to resize the system and data partitions using parted. I was unaware that the bootloader detects such modifications and ended up with a brick.
Just to clarify, this is a hard brick, since the Flashtool and fastboot modes do not work. I do not see the blue LED while trying to start the device in the fastboot mode using the volume rockers. My PC only detects a "QHSUSB_DLOAD" device for which I've installed the drivers and it is now "Qualcomm HS-UDB QDLoader 9008".
However, before I started to work with the partition table, I took a raw backup of the emmc i.e. mmcblk0. This should include the correct partition table and all the partitions (TA, userdata, system etc.). Theoretically (I believe so), if this is reflashed onto the device, an unbrick could be possible. However, so far, I haven't been able to figure out a way to push this image back to the device. I came across QPST and some linux bash scripts but haven't been able to use them successfully.
Has anyone come across such a scenario before? I looked for solutions in other threads but didn't find anything conclusive for Xperia devices. Can someone help me with this? thanks.
randallstevens said:
I was feeling adventurous and started messing with the partition table
Click to expand...
Click to collapse
Hi,
On other forum one user followed suggested by me same theory of remapping paritions as described here to shrink so large /system and increase /userdata
He gotta same brick because deleted 3 partitions and then they was cannot created by any commands, so seems this method not applicable to our phone.
Next he very early quited from recovery without restoring partition table from backup.
Surprisingly, in un-offical service center phone was quickly fixed, seems with JTAG-device.
QHSUSB_DLOAD – this is fall-back low-level mode of CPU that allow access to all partitions just like fastboot
Needed to repair / writing stock ROM at factory.
Can be enabled manually by connecting to PC with holding both volume buttons. How to exit – don't know.
QPST utility not useful because we not have dump in it's proper format. So only Linux our hope.
That user tried to manage with Ubuntu but phone was not recognized. Very likely he went into something wrong.
That's very great that you created backup of whole NAND.
Maybe will be enough restore GPT (partition table), I have one and own per-partitions dump too.
So plan very easy: connecting phone to PC with Ubuntu and restore dump via dd utility.
Partially follow this instruction with modifications because you have full dump.
Connect phone, find where it "attached" (whole nand, not partitions), restore file there.
Be careful with disk naming, you can damage data on HDD.
Bonoboo said:
So plan very easy: connecting phone to PC with Ubuntu and restore dump via dd utility.
Partially follow this instruction with modifications because you have full dump.
Connect phone, find where it "attached" (whole nand, not partitions), restore file there.
Be careful with disk naming, you can damage data on HDD.
Click to expand...
Click to collapse
Hi Bonoboo, thank you for replying.
Unfortunately, Ubuntu isn't able to detect the emmc and therefore, I'm unable to find the "/dev/sdX" node for the device. The phone is being detected only as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)".
I've seen some threads wherein QPST is first used to enable the partitions detection of emmc. However, as you mentioned, we do not have the necessary MSM8227 HEX file for this.
A windows app called "s1tool.exe" can be used to flash the bootloader files from the FTF, Link to thread. However, a testpoint combination is needed to access the emergency mode. I was unable to find a testpoint for Xperia M.
Is JTAG the only way forward here? Thanks again for the help.
EDIT: Looks like the s1tool I mentioned is device specific, may not work with XM.
randallstevens said:
I'm unable to find the "/dev/sdX" node for the device.
The phone is being detected only as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)".
Click to expand...
Click to collapse
Yeah, this is not good, same as was with that guy. 1, 2
But here under spoiler I found Perl-script that may open access to eMMC.
Here more info.
Maybe it device-specific too, but anyway try.
UPD: post
just connect your phone to PC (at this time your /var/log/kern.log should update and ttyUSB0 should be added), in terminal, cd to your download folder and run './qd.pl --check', or run 'perl ./qd.pl --check'.
Click to expand...
Click to collapse
Bonoboo said:
Yeah, this is not good, same as was with that guy. 1, 2
But here under spoiler I found Perl-script that may open access to eMMC.
Here more info.
Maybe it device-specific too, but anyway try.
UPD: post
Click to expand...
Click to collapse
Hello Bonoboo,
I've tried using the qd.pl script but I'm not sure which file needs to be sent to the device when using the "qd.pl --pfile X" and the other parameters. The script detects the Qualcomm modem. I've tried uploading the first 256 kilobytes of the dump which should include the partition table but this results in an "Invalid Response" error from the script. Tried uploading the TA and some other partitions, but received the same error. No eMMC access yet. What file do you think the script requires?
randallstevens said:
What file do you think the script requires?
Click to expand...
Click to collapse
Was mentioned some *.hex, that maybe relates with same from QPST.
In threads more info.
Very likely script just not compatible with M.
UPD: it's sounds weird, but try to connect phone in fastboot / flashmode with long holding volume key.
In some cases this really helpful due second "bootloader" (alt_s1sbl2 partition and other).
Bonoboo said:
UPD: it's sounds weird, but try to connect phone in fastboot / flashmode with long holding volume key.
In some cases this really helpful due second "bootloader" (alt_s1sbl2 partition and other).
Click to expand...
Click to collapse
Hi, I tried long-pressing the volume key, it does not seem to work. Thanks for the confirmation about the hex file. It looks like I'll need the right files for the handset, as using hex files of similar chipsets did not help. I'll keep working on it and write back with an update if I'm able to fix it.
I've got the same problem., but unfortunately I didn't make a dump of mmcblk0. There is a way I can get yours? Or a part of it with the interesting data with which I can try figuring out how the qdload.pl script works (maybe leave out userdata cause of its size and the private data).
fakier said:
I've got the same problem., but unfortunately I didn't make a dump of mmcblk0. There is a way I can get yours? Or a part of it with the interesting data with which I can try figuring out how the qdload.pl script works (maybe leave out userdata cause of its size and the private data).
Click to expand...
Click to collapse
Hi fakier, sorry to know you have the same problem. I've sent you a PM with a link to a compressed copy of the first 140 MBs of the raw eMMC dump I made earlier. This should contain all the important partitions besides system and userdata. Note that this also includes my TA partition which probably shouldn't be written to your device.
randallstevens said:
Hi fakier, sorry to know you have the same problem. I've sent you a PM with a link to a compressed copy of the first 140 MBs of the raw eMMC dump I made earlier. This should contain all the important partitions besides system and userdata. Note that this also includes my TA partition which probably shouldn't be written to your device.
Click to expand...
Click to collapse
Thanks, a backup of my TA partition I do have...
Update
Hello folks, after spending a lot of time trying to fix my device with qdloader and QPST, I gave up. Before getting it JTAGed, I wanted to try my luck (again) and approached Sony to claim warranty, since there was a month remaining before its expiry.
My warranty claim was accepted and they replaced the mainboard, though the bootloader was unlocked!! My Xperia is alive and kicking again! Will unlock it soon.
Trying to fix the phone was not a pleasant experience, but I think I learned much along the way. Hope nobody else screws-up the way I did.
Thanks XDA, see ya around! :good:
randallstevens said:
Hello folks, after spending a lot of time trying to fix my device with qdloader and QPST, I gave up. Before getting it JTAGed, I wanted to try my luck (again) and approached Sony to claim warranty, since there was a month remaining before its expiry.
My warranty claim was accepted and they replaced the mainboard, though the bootloader was unlocked!! My Xperia is alive and kicking again! Will unlock it soon.
Trying to fix the phone was not a pleasant experience, but I think I learned much along the way. Hope nobody else screws-up the way I did.
Thanks XDA, see ya around! :good:
Click to expand...
Click to collapse
Dude what was the point of this thread and when you tried to fix your phone did you re flash stock ROM?
Reply to Piravinthb's comment
Piravinthb said:
Dude what was the point of this thread..
Click to expand...
Click to collapse
The point of this thread, dude, was to see if the device could somehow be taken out of the "Qualcomm HS-USB QDLoader 9008" mode, a (very) low-level interface meant for vendors to flash bootloaders and system images on their devices.
..and when you tried to fix your phone did you re flash stock ROM?
Click to expand...
Click to collapse
Had you googled this, you'd know that this mode isn't the same as the Flashtool flash mode or fastboot. No rom, stock or CM, can be flashed before fixing the bootloader itself, which is needed to start the device.
Not much progress could be made here since the bootloader hex files for Qualcomm's OEM tools (QPST) would be needed to fix such a hard brick. Also, the QDloader scripts mentioned earlier were written for a different chipset from the one used in Xperia M.
Cheers, RS.
randallstevens said:
Hello all, I have been a lurker for quite a while here. I own an Xperia M (Rooted, Unlocked BL running CM11). I was feeling adventurous and started messing with the partition table hoping to resize the system and data partitions using parted. I was unaware that the bootloader detects such modifications and ended up with a brick.
Just to clarify, this is a hard brick, since the Flashtool and fastboot modes do not work. I do not see the blue LED while trying to start the device in the fastboot mode using the volume rockers. My PC only detects a "QHSUSB_DLOAD" device for which I've installed the drivers and it is now "Qualcomm HS-UDB QDLoader 9008".
However, before I started to work with the partition table, I took a raw backup of the emmc i.e. mmcblk0. This should include the correct partition table and all the partitions (TA, userdata, system etc.). Theoretically (I believe so), if this is reflashed onto the device, an unbrick could be possible. However, so far, I haven't been able to figure out a way to push this image back to the device. I came across QPST and some linux bash scripts but haven't been able to use them successfully.
Has anyone come across such a scenario before? I looked for solutions in other threads but didn't find anything conclusive for Xperia devices. Can someone help me with this? thanks.
Click to expand...
Click to collapse
hi i have same problem with same adventure , but i was using stock rom with customized kernel with cwm.
i think the solutions are 2
repair hard brick with JTAG or test point and s1tool what is not implemented for xperia m
see http://forum.xda-developers.com/showthread.php?t=2646405 for Z1
my handset will be in trash no free or paid solution or sony service . i'll buy another one
thx
rafik23 said:
my handset will be in trash no free or paid solution or sony service . i'll buy another one
thx
Click to expand...
Click to collapse
Buy a nexus 4 off amazon for 140€
It only takes 2 taps to thank somebody here.
I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.
still no results
To no avail I have tried everything! I have seen some changes but nothing that tells me that its fixed! I have tried qpst, but either I don't know how to run it or it wont connect properly, as a matter of fact I dont think it connects properly to any of the programs I run on it. It doesn't help that the only way the computer recognizes it is when it is on demigod mode.has anyone out there in android land had some experience or any idea of how to format the internal sd and start over from scratch?
shiftykidd said:
I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.
Click to expand...
Click to collapse
You managed to fix it?
am facing the same issue.
Not yet i am thinking about just sending it back to lg. It's mixed up partitions, due to power surge from unauthorized power cords.
Do you have your phone rooted and with a custom recovery?
If yes,
Give this a try:
1.Enter recovery
2.Wipe data
3.Wipe cache
4.Wipe dalvic cache
5.Reboot
I've had the same problem with an LG L9 ii and this one fixed it.
So i really hope this will help. Inform me after doing this.
Greetings.
About five months ago I was able to access recovery but nothing was functional, now I cant even turn it on, if you left it on a different charger, kernal crash handler popped up half the time. Before it quit turning on the lg boot logo started going fuzzy, logic leads me to believe its a messed up Q C mother and the partitions are scrambled due to me using a non-oem charging cord and block, I also suspect the power button mounted to the back, on top of mother might have caused some hw problems. But those are just theories, it could simply be a bad battery!
Greetings Everyone,
I need help regarding my hardbricked LG F460L. As of right now it is in DEADBOOT (The screen won't turn on even if I plug it in) So, I can't boot into RECOVERY, DOWNLOAD MODE, or FASTBOOT. However, when I connect my phone to my Win 7 64-bit PC, it is detected as QHSUSB_BULK.
This nightmare happened because I flashed a D855 modem.iso to my F460L, I accidentally flashed the incorrect modem.iso in TWRP and i've been screwed since then.
After reading and scouring through every LG F460L/K/S Cat 6 Unbricking threads in XDA, I have found three methods:
https://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853
- I have installed the QUALCOMM driver, my phone is now detected as Qualcomm QDLoader 9008. This is in accordance to the BoardDiag method. Using willcracker's boarddiag program, I connected my phone to my pc and clicked start HOWEVER I always get the device not found in dload trying flash programmer error after 2 minutes. The AP Chipset I chose is B2 since there is no MSM8084 or APQ8084 chipset for the Cat 6 in the program
If anyone has a working BoardDiag program that supports the Cat 6, please do post a link in the comments or PM me if you so prefer.
= ~FAILED~
https://forum.xda-developers.com/lg-g3/general/unbrick-debrick-f460-boot-security-t3352382
- I tried to boot through an external Micro SD card by flashing a "debrick.img" to the SD card. There were 5 debrick images listed in the guide, however, all of its download links are down (220, 200, 180, 160, and 140 are all down)
Thanks to the efforts of other users, I was able to download a debrick image file for the F460. Upon mounting the flashed Micro SD card, my screen turns on and I can enter download mode BUT it was of no use since I was stuck in an eternal "Secure Booting Error!" bootloop.
If anyone has a working link to the 5 debrick images for the F460, please share.
= ~FAILED~
https://forum.xda-developers.com/verizon-lg-g3/general/fix-unbrick-hard-bricked-lg-g3-vs985-t3467067
-Finally, there is the Wire Trick (Test Point/Shorting Points) method, this method carries a risk of DAMAGING HARDWARE since you can fry your mobo if you're careless.
Since my phone was already detected as Quallcomm QDLoader 9008, I skipped this method, but beacuse the first method is not working for me, I wanted to get back to this.
I was actually desperate enough to attempt this, however, upon reading the warnings and disclaimers, I had to think twice about it. The trick was to short a point near/beside the processor and short it to ground. It is relatively simple and easy (For the International versions) but since I have an F460 Cat 6, my board is SIGNIFICANTLY different from the mobos of the International/European versions.. Images and diagrams online, looks different to an F460L mobo. Can't risk frying my phone!
Since there is no information/images/guides regarding how to short an F460 Cat 6, I put out this method for later study.
If anyone can point me where to short these pins or help me find the correct pins, I would appreciate it.
= ~FAILED~
http://cafe.naver.com/develoid/562849
:crying: I am desperate because support for the Cat 6 seems to be very poor, and the Develoid Cat 6 forum in Cafe.Naver is apparently region-locked, only allowing Koreans. I can't seem to register an account since it requires an I-PIN or a Korean phone number.
Please Help Me!!!!!!!!!!!!!!!!!!!!!!
If anyone can provide me with other methods (except paying for overpriced JTAG repairs ) I will really appreciate it!
and Thanks everyone!
If you have a working link to the 5 debrick images for the F460, please share.
Thanks you so much
Boot verification fail!cause : mismatch_sig_len please help me asap pleaseee
Hi everyone,
I am trying to revive a Samsung A5 2017. Few months ago I had a software problem with it and went to a local shop to fix it, but no luck. The repair man told me he doesn't know what's wrong with the phone. To be short, the phone was completely dead. On a second shop and opinion, the phone was erased, I mean no partitions at all .... nothing. The phone wasn't even recognized by the pc at the beginning of this story. Don't have any backups. I've succeeded to make phone visible to Odin by flashing the correct PIT file. Now any attempt with Odin ends the same way .... efs, preload failed to mount. I want to remake the partition table with Odin multi downloader, but for this I need the ops file for this type of phone or the partitions name and order (to create one) and EFS file (which I have). Maybe it's a waste of time but I like tinkering with this. Any suggestions are very welcome on how to solve this.
Thanks
Hey, I have the same problem phone doesnt respond at all and isnt recognized by my Pc. How did you get it to be regocnized at least on your Pc.