Request for Nokia XL RM-1030 v1 mbn files - Nokia X

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

Related

Possible solution to unbrick xperia s with RED LED

Hello this is maybe solution to repair xperia with only red led with QPST but we need some files MPRG8260.hex and 8260_ms image.mbn to upload and boot into sdcard mode and need copies of the devices boot loaders and partition table from the actual working device. Please help, a search on web but cant find anything
check this tool
http://forum.xda-developers.com/showthread.php?t=2173363
desperately need files.. please help
MPRG8260.hex and 8260_ms image.mbn
lukasz8504 said:
Hello this is maybe solution to repair xperia with only red led with QPST but we need some files MPRG8260.hex and 8260_ms image.mbn to upload and boot into sdcard mode and need copies of the devices boot loaders and partition table from the actual working device. Please help, a search on web but cant find anything
Click to expand...
Click to collapse
I need these files too but for me for another device ( Asus padfone A66 ( qualcomm MSM8260 )).
I searched these files for a month everywhere, but I find just died links.
Anybody have got these files?

Need help for recovery damp bootloader

Hello! I am sorry for my translation. I'm just out of Russia. I have a problem - I beg your Oppo FIND 7а wrong firmware and it does not react to the power button. When connected to a computer is determined by the device - Qualcomm HS-USB QDLoader 9008, and the flash drive is not seen. Esteemed the on the forums that it is possible restore through the program - GPST, but at me there are no files necessary for programm required for programming via this program. Necessary files from the same machine - mprg8974.hex 8974_msimage.mbn sahara.xml, maybe someone you have these files?
vovan0983 said:
Hello! I am sorry for my translation. I'm just out of Russia. I have a problem - I beg your Oppo FIND 7а wrong firmware and it does not react to the power button. When connected to a computer is determined by the device - Qualcomm HS-USB QDLoader 9008, and the flash drive is not seen. Esteemed the on the forums that it is possible restore through the program - GPST, but at me there are no files necessary for programm required for programming via this program. Maybe someone you have these files?
Click to expand...
Click to collapse
Contact Oppo. Their support staff have given people QPST recovery files in the past... The only OEM I'm aware of to ever have done this.
Entropy512 said:
Contact Oppo. Their support staff have given people QPST recovery files in the past... The only OEM I'm aware of to ever have done this.
Click to expand...
Click to collapse
Official forum written request, but so far received no response. Can anyone here downloaded these files?
up
vovan0983 said:
Official forum written request, but so far received no response. Can anyone here downloaded these files?
Click to expand...
Click to collapse
up
Found A Solution ?
vovan0983 said:
Hello! I am sorry for my translation. I'm just out of Russia. I have a problem - I beg your Oppo FIND 7а wrong firmware and it does not react to the power button. When connected to a computer is determined by the device - Qualcomm HS-USB QDLoader 9008, and the flash drive is not seen. Esteemed the on the forums that it is possible restore through the program - GPST, but at me there are no files necessary for programm required for programming via this program. Necessary files from the same machine - mprg8974.hex 8974_msimage.mbn sahara.xml, maybe someone you have these files?
Click to expand...
Click to collapse
Hi Guy !
Did you find a solution ?
Thanks
Leny
I have the same problem... if you have the files, can you send them to me ? (I'm using google translate so my English could be wrong...)

[GUIDE] LG G3 D851 Unbrick Qualcomm 9008 Fully Working... Unbrickable D851!

NOTE: Before we begin, let me tell you that from my experience the D851 does not require shorting at all. it will be identified as Qualcomm HS-USB in a brick state without any opening up, check your device manager!
Hello guys, I spent 2 weeks analyzing hex files in order to revive a D851 that I got my hands on. It was not an easy journey but I would like to share this with the devs or people who are looking at bring their bricks to life.
What I did was actually hack the Sahara programmer files that WillCracker (BoardDiag) programs use. This comes in the attached files. Seems like there was no site on the Internet sharing this unique files and thus not allowing us to unrbick the D851.
For a more detailed view of how I got these modified files created please look at this post
But with this uniquely created files we now have unbrickable D851's , I have revived one D851 phone that I had dead. Right now it already booted into download mode and it is loading the *.tot.
Instructions
Connect your D851 phone without battery via USB to a Windows Box.
Make sure you have installed the HS USB 9008 Drivers installed. If so you will find something called "Qualcomm HS-USB QDLoader 9008 (COMxx)" under device manager, make sure you check the COM Port number, as you will need this later on the next step.
Open up BoardDiag.exe (from the downloaded files here, as it includes modified files specific for D851) and select: B2 (MSM8974AC), and pick up your COM Port.
Under 'Image Extraction' select your bin which should be the *.tot file (I used LG_D851.10C_TOT&DLL.7z).
Hit the 'extract' button into a directory of your choice.
Pick under 'COM Port' the 'Target Dir' and select where you have extracted the *.tot. This will allow us to start flashing the partition files.
{
"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"
}
Select on the checkbox "AP check".
Check the box called "RESTORE BOOT IMG", in here start picking up the partitions, write each one of them (not system, userdata or cache -- those are worthless for now), and ONLY in the end flash LAF and then finally SBL*. After this you will see the phone boot up with the battery icon since you do not have a battery connected. This is when you can tell you have now the bootloader reflashed.
Unplug the USB cable, insert the battery into the phone and hold UP while hooking up the USB cable again. After doing this your phone will boot up in download mode and now you can go ahead and flash the correct firmware using a tool such as LGFlashTool.
Below you can see a screenshot of the dmesg showing that it is already in download mode (after being in QC HS USB 9008 mode)... I am so !"#$ happy
I flashed the partitions like in this other guide but please use the attached file or else it won't work.
NOTE: Do download the attached Willcracker Version I attached specific for the D851, this is a modified one and is the only type of program I managed to use to revive my phone. I cannot stop insisting that any other set of files will not work on our D851, which is what most people reported on the forums for some time.
EXTRA: Disable Windows driver update, updating the Qualcomm HS-USB driver can cause conflicts and problems on the process.
<< If you like my work here is my hat, please donate! >>​
​
hello please i ask for your help
thank you for the great work man
can you please help me in my phone has same problem now it is a month
the problem is that my phone is lg f460s
i have the tot file but because it is a different chip-set Apq8084 this app BoardDiag doesn't support it
can you please modify the app
i searched in so many Korean forums nothing there and Russian forums too
please i donate for you man if you could find .hex singleimage.bin
i gave my phone to some people here but all of them doesn't know how to solve this boot loader problem i knew it can be fixed only by medusa box or octubos box which no body have it here
i found some files which it can revive some other phones having the same processor qualcomm snapdragon 805 like Motorola turbo and nexus 6
like these images
these unbrick files can communicate with lg f460s but because it need a right singleimage and .hex files it cant fix it
please bro try to look for this model i tried for so many weeks now
and thank you again
it fully work
thank u so much
i found your port last night
and it isnt have instruction
so i do by my self with your tool
you are my hero , you saved me thank you sooo much bro , my phone booted in fastboot mode after this , i ll try to flash frimeware now , biiig thnaks to you man
Jyed said:
you are my hero , you saved me thank you sooo much bro , my phone booted in fastboot mode after this , i ll try to flash frimeware now , biiig thnaks to you man
Click to expand...
Click to collapse
No problem man. I am also so glad to have unrbicked that phone as I can now give it to my dad as his phone (a really old Samsung Galaxy S3 was dying of slowness). I hated to have a ~$200.00 brick :cyclops: not being used! And I am a big fan of this LG G3 phone.
Btw, what I did after unrbciking first after fastboot started was that I shutted down my phone by removing the battery, and disconnected the USB cable. Then I reinsrted the battery and put it in download mode by using the: 'Keep pressing up and insert the USB cable'... and after that re-flashed the *.tot using downloaded mode as it is way faster with LGFlashTool.
Amazing work man… my D851 is working now. Earlier it failed to boot in all other methods. Thank u so much
@Omar-Avelar , Man, today i've seen my pm box and checked your message and looked here, nothing to say just.
THANKS, YOU SAVED ME! THANKS A LOT.
I've set the phone in download mode now, but when it begin the d851 firmware flash says cross DL SWversion, thats because i have a frankenstain phone, thats what've caused me a brick, what i need to do to set the d851 firmware?
Look at the images
ERROR:
My phone in dload mode says that:
and my motherboard:
I suposse that it can be fixed, but what i need to do?.
THANKS AGAIN MASTER! IM SO HAPPY
Where can i donate to you? Sorry for my english haha.
Edit: i've saw your firm now i'll donate you.
adrianbravom said:
@Omar-Avelar , Man, today i've seen my pm box and checked your message and looked here, nothing to say just.
THANKS, YOU SAVED ME! THANKS A LOT.
I've set the phone in download mode now, but when it begin the d851 firmware flash says cross DL SWversion, thats because i have a frankenstain phone, thats what've caused me a brick, what i need to do to set the d851 firmware?
I suposse that it can be fixed, but what i need to do?.
THANKS AGAIN MASTER! IM SO HAPPY
Where can i donate to you? Sorry for my english haha.
Edit: i've saw your firm now i'll donate you.
Click to expand...
Click to collapse
I've faced the same fate as you because I flashed a D855 on a Phone that was a refurbished D851. Took me like a month to figure out how to unbrick it.
By the looks of it it seems that your phone still has the LAF partition of the D855 but you recovered the other bootloder partition files allowing you to boot into the download mode 'thinking' it is a D855.
I suggest you use the LGUP_8974.dll instead of the 'supposed' D851 *.dll in the *.tot files... I think that will flash the partitions regardless if it is a D855 or 851 and force enter the files.
Omar-Avelar said:
I've faced the same fate as you because I flashed a D855 on a Phone that was a refurbished D851. Took me like a month to figure out how to unbrick it.
By the looks of it it seems that your phone still has the LAF partition of the D855 but you recovered the other bootloder partition files allowing you to boot into the download mode 'thinking' it is a D855.
I suggest you use the LGUP_8974.dll instead of the 'supposed' D851 *.dll in the *.tot files... I think that will flash the partitions regardless if it is a D855 or 851 and force enter the files.
Click to expand...
Click to collapse
Well, that images posted before whas with lgup_8974.dll and gives me the errors, I think I need to modify the hex file to put it as a "d855" and makes the program recognizes it, me fear is that if I flash the d851 firmware maybe I can loose the imei a mobile information ( before the brick the phone has d855 software ) or it will not erase my efs partition ? What u recommend me ? Flash d855 or d851 tot?
adrianbravom said:
Well, that images posted before whas with lgup_8974.dll and gives me the errors, I think I need to modify the hex file to put it as a "d855" and makes the program recognizes it, me fear is that if I flash the d851 firmware maybe I can loose the imei a mobile information ( before the brick the phone has d855 software ) or it will not erase my efs partition ? What u recommend me ? Flash d855 or d851 tot?
Click to expand...
Click to collapse
If it is a D851 motherboard but seen as a D855 via firmware I would try using the *.dll of D855 and the *.tot file of D851.
Seems like while being in HS-USB 9008 mode one of the partitions was not flashed correctly and the downloader mode still sees it as D855. The other option would be to brick it again with D855 *.dll and *.tot if the first try does not work. And while being in HS-USB 9008 mode please make sure you do flash most of the partitions there (not system, nor userdata, not cache) but the rest and end up with LAF > SBL* partition. That will flash the correct *.tot files for D851 and hopefully you will see the D851 now as D851 in the downloader mode.
I believe IIRC that the LAF partition has the downloader, and that's the one I believe is still written from when you overwrote it as a D855. If you wrote SBL* before LAF it might have booted with the LAF partition of the D855.
All done! Phone works and is alive!, @Omar-Avelar i've did what i told you, i've used a hex editor in a linux distro and modified the first "D851" mention to "D855" and goodbye CrossDL error, flashed sucessly, now my phone it's a real D851 and its hardunbricked! thanks all to you, you are great!.
Thank you, sir. You are live saver.
I have bricked my phone (d851) and I had been looking for days and nothing works.
Fortunately, I went to this thread and had successfully unbrick my phone.
God bless you.
D851 unbrickable
Omar-Avelar said:
I've faced the same fate as you because I flashed a D855 on a Phone that was a refurbished D851. Took me like a month to figure out how to unbrick it.
By the looks of it it seems that your phone still has the LAF partition of the D855 but you recovered the other bootloder partition files allowing you to boot into the download mode 'thinking' it is a D855.
I suggest you use the LGUP_8974.dll instead of the 'supposed' D851 *.dll in the *.tot files... I think that will flash the partitions regardless if it is a D855 or 851 and force enter the files.
Click to expand...
Click to collapse
My case is almost similar. As per software info it was d855 before bricking. So I flashed mm kdz for d855 and bricked.then I opened the cover and found this has a d851 board. So ,as per this tutorial I flashed everything for d851.phone booted but booting into fastboot mode only no download mode. Then I followed some other tutorial and again flashed laf. Img .now it can enter in download mode. But have a big problem .As it was a real d851 rom it cant connect to 3g net work here in india(2g ok). Now I am so disappointed because such a good phone with 2g only.....
But how initially d855 rom was flashed on d851 board???? There may be a way..
Ofcourse only beacuse of thread my g3 is live now. Please help me to get full out put from that.
There are threads to manually add bands to qualcomm device.Can I go for that?
[Update; Duplicated post]
justinmartin111 said:
My case is almost similar. As per software info it was d855 before bricking. So I flashed mm kdz for d855 and bricked.then I opened the cover and found this has a d851 board. So ,as per this tutorial I flashed everything for d851.phone booted but booting into fastboot mode only no download mode. Then I followed some other tutorial and again flashed laf. Img .now it can enter in download mode. But have a big problem .As it was a real d851 rom it cant connect to 3g net work here in india(2g ok). Now I am so disappointed because such a good phone with 2g only.....
But how initially d855 rom was flashed on d851 board???? There may be a way..
Ofcourse only beacuse of thread my g3 is live now. Please help me to get full out put from that.
There are threads to manually add bands to qualcomm device.Can I go for that?
Click to expand...
Click to collapse
Yes, it is such a great feeling to be able to bring the phone back from the death.
BTW, I do believe also the phone bands can be changed using QPST since I have seen Argentinian D855 phones changed to D855P (Adding another LTE band).
You might need another phone reference (LG G3 that worka on the band you want) and using QPST might let you modify some specifics.
Go ahead and Google translate this post for analysis: http://www.grupoandroid.com/topic/112493-guia-habilitar-bandas-lte-para-argentina-en-d855-int/
Another success in reviving the dead lg g3
Omar-Avelar said:
NOTE: Do download the attached Willcracker Version I attached specific for the D851, this is a modified one and is the only type of program I managed to use to revive my phone. I cannot stop insisting that any other set of files will not work on our D851, which is what most people reported on the forums for some time.
Click to expand...
Click to collapse
Thank your thread was really helpful in getting somewhere, You are the champion :good::victory:
---------- Post added at 07:53 AM ---------- Previous post was at 07:52 AM ----------
adrianbravom said:
All done! Phone works and is alive!, @Omar-Avelar i've did what i told you, i've used a hex editor in a linux distro and modified the first "D851" mention to "D855" and goodbye CrossDL error, flashed sucessly, now my phone it's a real D851 and its hardunbricked! thanks all to you, you are great!.
Click to expand...
Click to collapse
Can you please direct me somewhere or guide by yourself on how to do this.
Hey , could anyone help me? i have a lg l40 d175f, and i have boarddiag ,the kdz files but i do not have the partition.txt, what do I have to do??? please save me, this is not a monster phone but i don't have money to buy another one
Omar-Avelar said:
[*]Open up BoardDiag.exe (from the downloaded files here, as it includes modified files specific for D851) and select: B2 (MSM8974AC), and pick up your COM Port.
Click to expand...
Click to collapse
Modified Files huh??
The miracle file is a file that has been around all along. It can be found in the Smartboot Diag Tool. Its called LGD851_ATMO_TMUS.mbn.
All you have to do is rename this file to 2nd_loader.hex and put it inside the Board DIag Tool > Model > B2(MSM8974AC) Folder. Replace this file with the old one.
Now start Board Diag tool and load and decompress your tot file, and flash away.
For other models, you could try renaming your devices mbn from the Smartboot Diag tool to 2nd_loader.hex
wow
mickeyasamoah said:
Modified Files huh??
The miracle file is a file that has been around all along. It can be found in the Smartboot Diag Tool. Its called LGD851_ATMO_TMUS.mbn.
All you have to do is rename this file to 2nd_loader.hex and put it inside the Board DIag Tool > Model > B2(MSM8974AC) Folder. Replace this file with the old one.
Now start Board Diag tool and load and decompress your tot file, and flash away.
For other models, you could try renaming your devices mbn from the Smartboot Diag tool to 2nd_loader.hex
Click to expand...
Click to collapse
can you provide same file for lg g3 f460s ? it has chipset apq8084 . thank you i advance
ExtraDemo said:
can you provide same file for lg g3 f460s ? it has chipset apq8084 . thank you i advance
Click to expand...
Click to collapse
I am currently in class. Will check when I get home.

Unbrick LG G4 9008 Qualcomm MBN files

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

HTC M9 Qfil flash help needed (Qualcomm MSM8994) {Images Attached}

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:

Categories

Resources