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.
Hey XDA,
So I need your help with something. This morning I woke up to my LG G3 D855 v10i stuck in a bootloop, for no apparent reason. I'd set an alarm to go off, and it did but only for a second and not the full 10 seconds it should have, and then it shutdown and went into a boot loop with the LG Boot Animation and the notification light was flashing yellow. I pulled the battery out, put it back in, and then restarted it. I got the same boot-loop except the notification light was alternating between blue and green as it should have been, but it was still stuck. So I pulled it out, tried again twice more, until the phone finally decided to boot. Then the phone boots, and I see my customized lockscreen with my lockscreen image and lock code, and then it goes to the screen to setup the phone completely again; Like it's a brand new phone with nothing on it, except that some of my apps were opening/running and I could see them doing things while on the setup screen. At this point I knew something was up, and I suspect a corrupted file or something on the phone, and then I started getting a whole bunch of errors on the phone itself, such as "Gmail has stopped working", "com.google.gapps has stopped working" "YouTube has stopped working" and basically all the Google apps had stopped working, but mine were still running fine.
So, after a whole day of trying to flash a new KDZ in Normal Flash mode to the phone using the LG Flash Tool 2014 here on the forums, and failing over and over (Yes, the phone was in download mode, COM port on the PC was set to 40 and I tried port 41 as well, I even put the .kdz file itself in the LG Flash Tool 2014 folder as it says to do, but nothing worked and I kept getting all this http://gyazo.com/158044ffe14287157a4388a2a42680c0 ) So I just decided to do a hard factory reset on the phone itself. I've now updated it and everything's fine, it's just a vanilla LG G3 with none of my apps on it.
Now I'm onto my current predicament. I've installed LG PC Suite when I first got the phone and since then I've done 2 full backups of the phone using it, as seen here ( http://gyazo.com/cebada2d6b06cd116afce22d8caad8bc ) but LG PC Suite recognizes NONE of them as seen here ( http://gyazo.com/3359f520739ab229334d9fa9d4e1edd2 ). In the area down the bottom where it should list the backups I've done, it doesn't list anything, even though the backups are in the correct folders themselves. Since factory resetting the phone wiped the internal memory, I lost all 32GB of my Apps, Photo's, Videos, and all my App Data. I NEED a way to get LG PC Suite or something else (Even ADB?) to push the backup/backup files to the phone and restore it. As you can see here, when LG PC Suite backs up the phone, it creates all of this data ( http://gyazo.com/a62ad1efa0e127c1b5830562965ed50a ) but in LG PC Suite's Backup/Restore device area when my device is plugged in, it shows no backups. I've even tried changing the directory the backups are in, re-installing PC Suite, everything.
I just really need a way for the PC, ADB or LG PC Suite to push all the files onto the phone and restore them, copying the files to the phone and using the G3's built-in restore app doesn't work either; All backups done by the phone were on the internal storage which was wiped with the factory reset
If someone could come up with a solution to this, I would be eternally grateful; You would save me an immense amount of time having to re-download my 32GB on my internet (Which is slow here in AUS) and I'd be eternally grateful. I'm not sure if it's the LG Software just being crap like their Android App Code, or if it's just an error or if the backups need to be in a specific place, I'm not sure. I just need a way to push them onto my phone and restore it. Thank you SO much to anyone that comes up with ideas or a solution!
TL;DR: I need a way to get LG PC Suite to recognize my backups I've done so I can push them to the phone.
iDefalt said:
the op
Click to expand...
Click to collapse
try This, I am sorry to say but you will have to redownload the 1gb file if this doesn't work esspecially since imei is motherboard depended'(imei error that you get) I guess you have a faulty motherboard you will have to bring your phone in for repairs
I have created boot recovery files based on Samsung's pdf titled "[14-96]_Boot_Recovery_Guide_Qualcomm_APQ8084_[includes_SM-N910F]__Rev_3.0"
These were done on a 32gb clas 10 microSD, they are imaged to a file via Norton Ghost portable (GHO file.
If your note doesn't boot, that might help. (No charging light, PC detects as QHUSB 9008 mode etc)
Download these GHO files and norton ghost portable.
Insert an empty microSD, Open norton ghost > Local>Image>to Disk the choose your microSD.
Your disk capacity might show up less, but don't worry, you can restore later on with Minitools (Check online on how to use).
I have also created an eMMC backup image of n910p running MM (PE2 build version)
It's a 2gb file, on unzipping with 7zip, around 4gb. (While creating, the output from adb shell is shown in the pick. Not sure if it's an error... is it supposed to be bigger? it was on a clean stock but rooted.. no user content)
Follow this guide http://www.droidsavvy.com/unbrick-qualcomm-mobiles/ to check it's in new 9008 mode.
Then my file might work for you.
All files are at https://mega.nz/#F!qRAGBZDY!_k24QWYaA0We2IQoAgE2Ng
Hi,
and Thanks
Well I have tried these Gho files but no joy. Ghost says file sizes are 19. After writing to the mirco SDCard there is no spaced used and 3 folders that are blank.
I am looking for these files below to recover to use QPST (QFIL) / MiFlash , maybe you can extract them from your device but I have no idea how to do it.
MPRG8084.hex
-8084_msimage.mbn
-rawprogram_32GB.xml
-patch0.xml
-Settings.xml
Thanks
dray_xclusive said:
Hi,
and Thanks
Well I have tried these Gho files but no joy. Ghost says file sizes are 19. After writing to the mirco SDCard there is no spaced used and 3 folders that are blank.
I am looking for these files below to recover to use QPST (QFIL) / MiFlash , maybe you can extract them from your device but I have no idea how to do it.
MPRG8084.hex
-8084_msimage.mbn
-rawprogram_32GB.xml
-patch0.xml
-Settings.xml
Thanks
Click to expand...
Click to collapse
And my phone its same
I hope to find way to solve it
i have also same issue does any one solve ?
an interesting read... curious, under what circumstances would this be more convenient / more practical than a simple odin flash?
is this supposed to recover hard bricks / bad bootloaders?
Took N910P back to Sprint.
I experienced my problem when I was using my secondary (not activated, clean esn) Sprint N910P as an MP3/MP4 player. After the last update which i don't know... it would not boot into the OS after the Sprint splash screen, so it would continue to do this constantly after removing the battery and rebooting even after optimizing apps screen. I researched and found XDAs forums with a lot of How tos, troubleshooting and workarounds. Long story short the Reactivation Lock was not disabled and even using the techniques supplied here I did not have any success.
I took it to the Sprint store and they deactivated my Primary LGV20 and activated the Note 4 so they could service it and then flash it to the current OS. They couldn't flash it and were going to have to send if off to replace the motherboard or replace the phone. The tech told me that this has been happening to Sprint Note 4 phones after an update and since it was a update error there will be not charge to me. Now I had insurance on the Note 4 for six years prior to upgrading to the LGV20, so they had to activate it to be able to service it. I will update their findings when i receive my phone in 7 to 10 days.
I pray this helps someone in my situation, as for me it is bittersweet. I didn't fix my phone but I found a new forum and I can tell everyone here is as passionate about what they do as I am!
- Jacob
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.
I need help with my pixel (taimen), and I don't know what to do. In attempt of resizing partitions with help of parted, I somehow deleted all the partitions (even though it showed they were recreated successfully), and now the phone won't even boot to fastboot. Is there any way how to repair it? I've had it for long time and I don't feel like loosing it today.
There are a couple of other threads where a user posted firebase files that could be used with existing firmware. Those files and a copy of MiFlash on the PC may be able to restore the device, but only if it shows up as a Qualcomm USB loader in Windows. The only other alternatives are to pay Google to fix the problem or sell the unit for parts.