Related
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.
Hello
This is the process that I used to unbrick the LG G Pad 8.3 tablet.
Note 1: The operating system on my PC is Windows XP SP3 x86
Note 2: The same process should also work on LG G Pad 10.1 (With a different .tot file)
1. First of all you should make sure that the G Pad is detected when connected to the PC.
The device should be seen as QHSUSB_DLOAD in Other Devices section in Device Manager.
hxxp://i.imgur.com/IawJZq0.jpg
2. Install the QHSUSB Driver for your operating system.
The driver can be found here:
hxxp://mega.nz/#!HlpViaTJ!NPACjSQtTjGWdYIj3kHO3bGfmAotaSSQindmgRY9VJ4
I have used the driver from the "checked" folder.
Reconnect the tablet and you should now see the device as Qualcomm HS-USB QDLoader 9008 (COMxx) under the Ports section in Device Manager.
Take a note of the COM port number.
hxxp://i.imgur.com/IR7uUCB.png
3. Download the .tot image file for you tablet model.
I have used the one from here (LG G Pad 8.3 V500 4.4.2):
hxxp://androidfilehost.com/?fid=23329332407581518
4. Now you need the LG BoardDiag tool.
Download this one from here:
hxxp://mega.nz/#!XwgkXTAR!JnAAXKBQoezT7CcxRSVkSQlPFr4AXcvfm6oJbw4bht4
Please use only this one even if you have another BoardDiag. I have tried other versions and this was the only one that worked. For the other versions I always got some error:
failed during loading flash programmer
or
device not found in dload trying flash programmer
With this tool we will extract the .tot rom image first.
Unrar the archive and open BoardDiag3.99c application.
Click on the ... button next to BIN from the Image Extraction section on the bottom of the BoardDiag application and browse to the .tot file you downloaded at step 3.
Then click on the ... button next to DIR and browse to a folder to extract the files in.
Click on the Extract button and wait for the files to be extracted.
After the extraction is complete, close the BoardDiag application.
hxxp://i.imgur.com/Kw0ZhUv.jpg
5. Now we will perform some cheks on the tablet.
Open the BoardDiag application again.
Now select the AP check and EMMC TEST checkboxes from the Board Diag Test section on the top-left.
Also choose the G-pro (APQ8064) on the AP Chipset dropdown selection box. Choose the Com Port that you took a note of at step 2. Select as the Target Dir the folder where you extracted the .tot image file at step 4. These settings are in the top-right side of the BoardDiag application. Make no other changes to the settings.
Now Click on the big START button and wait for the checks to be made.
If everything is OK you should see under the Test Results section the green text PASS both under the AP and EMMC. Leave the BoardDiag application open. Now you can proceed to step 6.
6. Now we will Flash the files to the tablet.
Now you will also check the SDRAM TEST checkbox on the left top side of the BoardDiag application. The other settings were already made in step 5. Click the START button again.
After performing the checks you should see that the files from the image (aboot.mbn, boot.mbn, etc.) are written to the tablet.
After that, the BoardDiag tried to reset the tablet, but it failed and it ended with FAIL for SDRAM under the Test Results section. But the files were already written on the tablet.
7. After that I disconnected and reconnected the tablet to the PC. Nothing was detected, or so I thought, because I could see that in Device Manager something was happening. It was like refreshing itself every 5 seconds or so. I disconnected the tablet from the PC and I plugged in the wall charger. It turns out that the battery had no power.
After a few minutes the LG logo appeared on the screen. Nothing else was happening but I could see the LG logo. I left the tablet to charge the battery for at LEAST 3 hours. If your tablet battery is also discharged you should plug your tablet to the charger for at LEAST 3 hours.
After that I reconnected the tablet to the PC and it was detected as G Pad but it couldn't find the driver.
8. Install the LG Mobile Drivers.
You can get them from here:
hxxp://mega.nz/#!j8xikSYC!Njz3E1_PSJanzQEeZCbbEoWfxUz9TfrTVgusqBCJ2qY
After the driver installation reconnect the tablet to the PC.
It should now be connected properly.
9. Download LG Mobile Support Tool. You can use the launcher from here:
hxxp://mega.nz/#!bp5jgBQJ!xqiMyQU7z-ATlYz__0ybz2kM7boeLFNgqsu5XoPPSzo
Open LG Mobile Support Tool. You should now see the tablet is connected correctly and you should see the tablet model on the left side of the LG Mobile Support Tool. You will now go to Options and choose Upgrade Recovery. Wait for the image to be downloaded and flashed to the tablet.
After the process is completed the tablet will boot to life again.
Please write your comments bellow if you succeeded or failed. I will provide further assistance if required.
PS: I think you need to remove the battery and reinsert it after step 6. Or it could also work if you let the battery discharge completely.
Good luck!
I could not post the images and the links.
I will add them later (after I get to 10 posts).
Contact me on skype (cyadron) for the files and for other help.
nice finding.
it can be handy if we try to flash the v510 bootloader on the v500 to see if it fits and "unlocks" the pad
ckret said:
nice finding.
it can be handy if we try to flash the v510 bootloader on the v500 to see if it fits and "unlocks" the pad
Click to expand...
Click to collapse
Actually it was the only way I found that worked to unbrick this tablet.
Bricked LG G Pad
Need your help man with those files. I bricked my device after flashing wrong file. I have tried LG G2 Pro Board Diag tool and everything passes except SDRAM.
Thanks in advance for your assistance.
Links for files
Hi, I bricked my GPad and would be very interested in getting the proper files or links. How can I get them?
I will update this thread as soon as I can post links. Hopefully no more than a few days.
cyadron said:
I will update this thread as soon as I can post links. Hopefully no more than a few days.
Click to expand...
Click to collapse
Can you post links ?
This sounds very promising @cyadron, hopefully you'll be able to edit the links in soon.
@muiriddin this sounds like you should be able to revive your tablet from your science experiment.
@fefifofum posting here instead of the other thread as that would be way off topic for it.
This sounds like we'll be able to do some proper experimenting and still be able to recover if it doesn't work!
Hopefully I will be able to post the links soon. Does anyone know the minimum number of posts required to post links?
cyadron said:
Hopefully I will be able to post the links soon. Does anyone know the minimum number of posts required to post links?
Click to expand...
Click to collapse
Just put hxxp instead of h t t p.
roirraW "edor" ehT said:
Just put hxxp instead of h t t p.
Click to expand...
Click to collapse
Thank you. That worked.
Links have been added.
cyadron said:
Thank you. That worked.
Links have been added.
Click to expand...
Click to collapse
This thread should probably be pinned. You can request the moderators to do so by "reporting" your first post and ask them there. Too bad, as far as I know, there aren't any TOTs available for the VK810, although I haven't needed one yet.
I used the tutorial, but accuses ero Emmec test fails
Any solution?
edsmat said:
I used the tutorial, but accuses ero Emmec test fails
Any solution?
Click to expand...
Click to collapse
Unless there is a hardware problem with the emmc, it should work.
Try and remove the battery and put it back again.
Please also make sure you follow the steps as described.
Cluey said:
This sounds very promising @cyadron, hopefully you'll be able to edit the links in soon.
@muiriddin this sounds like you should be able to revive your tablet from your science experiment.
@fefifofum posting here instead of the other thread as that would be way off topic for it.
This sounds like we'll be able to do some proper experimenting and still be able to recover if it doesn't work!
Click to expand...
Click to collapse
It would be nice to get my science experiment working again... I hopefully will have some time to follow this process this weekend...
hi, i have hardbrack v410 no have screen at all only qualcomm hs_usb 9008 please help me (
lgv410 said:
hi, i have hardbrack v410 no have screen at all only qualcomm hs_usb 9008 please help me (
Click to expand...
Click to collapse
Read everything you can and follow instructions.
I think you'll need to search further than just this thread though. I read about someone recovering an LG device from this state but I think it was a phone.
But you'll need to find it and follow the instructions, I don't remember where I read it.
Cluey said:
Read everything you can and follow instructions.
I think you'll need to search further than just this thread though. I read about someone recovering an LG device from this state but I think it was a phone.
But you'll need to find it and follow the instructions, I don't remember where I read it.
Click to expand...
Click to collapse
thank you for you answer, can you show me where i can found this instructions to fix this problem? :/
lgv410 said:
thank you for you answer, can you show me where i can found this instructions to fix this problem? :/
Click to expand...
Click to collapse
No, I'm not here to do searches for you.
okay let start, my friend gave me his LG G4 with BOOT LOOP issue.
so i did like in the video
https://www.youtube.com/watch?v=TM9umec5aeo
the phone worked for 5 hours and back to boot loop issue. so in this time i made backup.
after it i follow this guide
https://forum.xda-developers.com/g4/development/ilapo-infinite-loop-auto-power-off-fix-t3404421
but the friend phone has marshmallow android and i need lollipop android so i have flashed wrong ktz by mistake and phone gone to Brick mode.
so i search a lot in the internet MBN file for G4 and i found so i want to share it with you
just download the files from next linkaccording to your model
http://bit.ly/2maK3uL
or
Code:
http://forum.gsmdevelopers.com/showthread.php?t=24303
the password for H815 is "Moyal Software H815",for other just PM to dev.
after i downgraded to android 5.5 i continue with
https://forum.xda-developers.com/g4/development/ilapo-infinite-loop-auto-power-off-fix-t3404421
and after it i reactive the reset cores with kernel adiutor.
right now the phone works well already 4 days.
Enjoy.
These are the exact same files as already given in another thread. They don't work for me.
Depending on QFIL version I have "Device not in firehose mode" or "too long to open COM port" error.
I have H815. Bricked the exact same way as yours.
Do you have any ideas what I can change/try?
Dear,
I have the same problem with a H818P.
Someone can help me!?
I`ve attached a screenshot with my problem!
https://ibb.co/hVthyv
I`m stuck in "COM Port number 5"
in device manager, is not possible to find "Qualcomm MMC Storage USB Device" under disk drivers.
thanks!
rfsaidel said:
Dear,
I have the same problem with a H818P.
Someone can help me!?
I`ve attached a screenshot with my problem!
https://ibb.co/hVthyv
I`m stuck in "COM Port number 5"
in device manager, is not possible to find "Qualcomm MMC Storage USB Device" under disk drivers.
thanks!
Click to expand...
Click to collapse
Hey, I have struggled long time with this but finally I got it to work
I used this guide:
http://gsmmarhaba.com/threads/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box.612/
But instead files for H815 i used ones for LS991 and QPST 2.7.425. Files were flashed successfully and now I have download mode
So try with other versions of mbn files as well as with other versions of QPST/QFIL. Good luck.
washoq said:
Hey, I have struggled long time with this but finally I got it to work
I used this guide:
http://gsmmarhaba.com/threads/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box.612/
But instead files for H815 i used ones for LS991 and QPST 2.7.425. Files were flashed successfully and now I have download mode
So try with other versions of mbn files as well as with other versions of QPST/QFIL. Good luck.
Click to expand...
Click to collapse
Thank you ! I'll try this and will send a message with final result.
I can Help
washoq said:
These are the exact same files as already given in another thread. They don't work for me.
Depending on QFIL version I have "Device not in firehose mode" or "too long to open COM port" error.
I have H815. Bricked the exact same way as yours.
Do you have any ideas what I can change/try?
Click to expand...
Click to collapse
I have a solution, BTW have you solved your issue
washoq said:
Hey, I have struggled long time with this but finally I got it to work
I used this guide:
http://gsmmarhaba.com/threads/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box.612/
But instead files for H815 i used ones for LS991 and QPST 2.7.425. Files were flashed successfully and now I have download mode
So try with other versions of mbn files as well as with other versions of QPST/QFIL. Good luck.
Click to expand...
Click to collapse
Dear Washoq!
The mega.nz link (provided on the page you shared) is expired. Can you please upload the files yourself and share them here?
For fusing devices h815, to get download mode
https://mega.nz/#F!GJ9WlCYA!IT57novfFmId67gUt7_QPQ
Pleas bro all links are broken pleas update
In my position I'm having bricked HTC M9 which need to recover user data (Photos of new born kid which don't have backups)
Symptoms :-
NO power LED (Even charger connected)
NO HTC Logo
NO boot menu
NO vibrations
Power On button do nothing
Power + Volume down nothing
But when it connected to PC it shows Qualcomm service port "Qualcomm HS-USB QDLoader 9008 (COM8)"
After spending long time on reading I figure out If I'm able to fix the partition table & connect Qualcomm HS-USB QDLoader 9006 interface,
Then the eMMC can be mounted to local PC via USB. then I can recover my data,
So I'm planing to use Qfil to flash required data to mobile
So I downloaded Qfil from here
Downloaded stock firmware from here or here
My problem is it required following 3 files
prog_emmc_firehose_8994_lite.mbn
[*]rawprogram0.xml
[*]patch0.xml
prog_emmc_firehose_8994_lite.mbn file found & attaching
I'm still unable to find above three files any where from internet,
Please can some one help me to find this files (or extract the from some where)
I'm attaching some Images of device manage view, Qfile & stock ROM I have respectively
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you read this thread https://forum.xda-developers.com/windows-10-mobile/create-rawprogram0-xml-ffu-file-extract-t3385201 ?.
Beamed in by telepathy.
shivadow said:
Have you read this thread https://forum.xda-developers.com/windows-10-mobile/create-rawprogram0-xml-ffu-file-extract-t3385201 ?.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi My Friend, thanx for take your time,
Yep I read it, but the problem is
1. to use this tool we need "prog_emmc_firehose_8994_lite.mbn" file
2. we can only get "rawprogram0.xml" file from this, still need "patch0.xml"
Any one could help me with this will be a great help.
Thanx Mate
Good news , I have found the programmer for MSM8994 "prog_emmc_firehose_8994_lite.mbn"
I'm attaching it above for any one who is in the same boat as me.
Please some one help me to find "rawprogram0.xml and patch0.xml" files for HTC M9
https://drive.google.com/file/d/0BzypAwIfVp1gV1Vjc2FSQlhlaHM/view?usp=sharing
Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.
Sneakyghost said:
Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.
Click to expand...
Click to collapse
hello Sir,
Thanx for your time taken,
Actually I don't need recover the phone, I just need to restore partition table & put the phone in to "Qualcomm HS-USB QDLoader 9006 " mode. ( now it is on Qualcomm HS-USB QDLoader 9008 mode)
then I can mount the eMMC to Windows OS & recover what I need from the memeory.
So please any one can direct me to that way ??
thanx again
BR
war357 said:
hello Sir,
Thanx for your time taken,
Actually I don't need recover the phone, I just need to restore partition table & put the phone in to "Qualcomm HS-USB QDLoader 9006 " mode. ( now it is on Qualcomm HS-USB QDLoader 9008 mode)
then I can mount the eMMC to Windows OS & recover what I need from the memeory.
So please any one can direct me to that way ??
thanx again
BR
Click to expand...
Click to collapse
As far as my experience went five years ago, mounting the storage chip was not possible. A reflash was, although pretty complicated, just so possible.
I wish you good luck with your adventure.
Sneakyghost said:
As far as my experience went five years ago, mounting the storage chip was not possible. A reflash was, although pretty complicated, just so possible.
I wish you good luck with your adventure.
Click to expand...
Click to collapse
Ok Mate, Thanx
one other thing,
Do you know a way to just flash only boot partition (from USB cable)
Forgot to answer, I live far from German, Sri Lanka (Southeast Asia) so unable to access most of the resources.
thanx
br
Sneakyghost said:
Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.
Click to expand...
Click to collapse
Actually these phones are pain to me ? taking them apart and reassembling them isn't easy at all. Sadly. And the new HTC U isn't much better
---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------
war357 said:
Ok Mate, Thanx
one other thing,
Do you know a way to just flash only boot partition (from USB cable)
Forgot to answer, I live far from German, Sri Lanka (Southeast Asia) so unable to access most of the resources.
thanx
br
Click to expand...
Click to collapse
It's m possible Right now. Or I don't know any way. We don't have the resources for that. I could be wrong, but it gets harder getting these Files
Rawprogram0.xml is supposed to be creatable from the dragonboard tools.
Isn't it "fastboot flash boot.img"?
Beamed in by telepathy.
war357 said:
My problem is it required following 3 files
prog_emmc_firehose_8994_lite.mbn
[*]rawprogram0.xml
[*]patch0.xml
Click to expand...
Click to collapse
rawprogram0.xml for M9 here.
This from my gpt.bin
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=8 count=2176
and converted to rawprogram0.xml
shivadow said:
Rawprogram0.xml is supposed to be creatable from the dragonboard tools.
Isn't it "fastboot flash boot.img"?
Beamed in by telepathy.
Click to expand...
Click to collapse
hi Sir,
Fastboot is not working,
only software download mode working, whole partition table has messed up,
so no other option than finding above files & flash via QFil.
Thanx
BR
For info: https://forum.xda-developers.com/showpost.php?p=68390222&postcount=11
Bro, that was a great help,
That was a huge favor.
That was a huge favor.....
Thanx bro, thanx a lot
One more file & I'm goor to go
See you mate!
Golv said:
rawprogram0.xml for M9 here.
This from my gpt.bin
and converted to rawprogram0.xml
Click to expand...
Click to collapse
war357 said:
hi Sir,
Fastboot is not working,
only software download mode working, whole partition table has messed up,
so no other option than finding above files & flash via QFil.
Thanx
BR
Click to expand...
Click to collapse
Thanx a lot bro, taking your time for me is much appreciated,
If possible please help me to get patch0.xml also
Thanx again
Golv said:
rawprogram0.xml for M9 here.
This from my gpt.bin
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=8 count=2176
and converted to rawprogram0.xml
Click to expand...
Click to collapse
Hello,
Thanx for your great help,
but I have one more favor , can you extract patch0.xml from your M9 please,
I can't find anyone who has M9 around me to extract the patch0.
it would be a great help.
Thanx
BR
war357 said:
Hello,
Thanx for your great help,
but I have one more favor , can you extract patch0.xml from your M9 please,
I can't find anyone who has M9 around me to extract the patch0.
it would be a great help.
Thanx
BR
Click to expand...
Click to collapse
Try to use the zeroed file (empty content)
Golv said:
Try to use the zeroed file (empty content)
Click to expand...
Click to collapse
did you get this working?
i have a working m9 and qfil set up if you know how to read from the working m9?
G
gda_scooby said:
did you get this working?
i have a working m9 and qfil set up if you know how to read from the working m9?
G
Click to expand...
Click to collapse
Hi,
No Bro, Still no luck,
I don't know exact way to extract patch0.xml,
Normally it should come with firmware file,
But no sign of that on internet,
Seems really bad luck,
Any way Bro, thanx for your support,:good:
Hey everybody. I am looking for mbn or firehose files so i can try to revive my hard bricked Nokia XL. I dont know the history of the device, because i have bought it online in hope of fixing it. My best guess is that somebody flashed V2 files on this device. The device shows as QDLoader 9008. I have read some tutorials and the problem is, dont have money, nor do i know where to buy a jtag box in order to flash boot files that way. QPST is my only hope but as you can guess from the title, i cannot find proper boot files for my device that will work on QPST. Thank you in advance for help