[Q] QSHUSB_DLOAD Brick - Any help? - LG Optimus G Pro

Hi all (sorry for my English)!
I bricked my E986 phone while I was attempting to flash a KDZ file on it. The LG Mobile Support Tool stuck at 95%, leaving my phone in a deep brick status.
The internal partition scheme should be messed up (hence the hard brick), so it can be reflashed only using the QPST tool.
I don't want to use jtag and I'd prefer not to send it to LG... it's my main smartphone and I'd like to fix it in time for my summer holidays.
Has anyone got the necessary files to restore the low-level data that allow the phone to be recognized again by the LG Mobile Support Tool?
I think that I need these files:
- MPRG8064.hex (or the specific similar file for the Snapdragon 600 CPU)
- 8064_msimage.mbn (it should contain the partition scheme)
- g_emmc.img (i found only the F240 version of this file)
I think that there's also a way to get all those files from a working phone... any help will be appreciated.
Thank you!!!

Il Palazzo said:
Hi all (sorry for my English)!
I bricked my E986 phone while I was attempting to flash a KDZ file on it. The LG Mobile Support Tool stuck at 95%, leaving my phone in a deep brick status.
The internal partition scheme should be messed up (hence the hard brick), so it can be reflashed only using the QPST tool.
I don't want to use jtag and I'd prefer not to send it to LG... it's my main smartphone and I'd like to fix it in time for my summer holidays.
Has anyone got the necessary files to restore the low-level data that allow the phone to be recognized again by the LG Mobile Support Tool?
I think that I need these files:
- MPRG8064.hex (or the specific similar file for the Snapdragon 600 CPU)
- 8064_msimage.mbn (it should contain the partition scheme)
- g_emmc.img (i found only the F240 version of this file)
I think that there's also a way to get all those files from a working phone... any help will be appreciated.
Thank you!!!
Click to expand...
Click to collapse
Sorry to say that so far jtag is the only way to fix that kind of brick. I've seen it on the OG forums too and so far nobody has been able to fix it.

luisoman2000 said:
Sorry to say that so far jtag is the only way to fix that kind of brick. I've seen it on the OG forums too and so far nobody has been able to fix it.
Click to expand...
Click to collapse
But I saw a tutorial for the optimus G (not the 'Pro' model) in chinese that should solve the problem, with the right files... Do you mean that there are no files available on the net? Or you're just saying that there isn't a suitable method at all?
Since I don't want to disassemble the phone, I think that I will send it to LG if there is no solution left.

I havent seen anyone manage to revive a phone with that issue without the use of jtag.

I had the same problem and have sent in for repairs to LG. They have repaired the phone without asking a single question.
But that was within 1 year manufacturer's warranty..
PS I have sent it to JTAG (RIFF box) repair service before that and they were NOT able to repair it.

Il Palazzo said:
Hi all (sorry for my English)!
I bricked my E986 phone while I was attempting to flash a KDZ file on it. The LG Mobile Support Tool stuck at 95%, leaving my phone in a deep brick status.
The internal partition scheme should be messed up (hence the hard brick), so it can be reflashed only using the QPST tool.
I don't want to use jtag and I'd prefer not to send it to LG... it's my main smartphone and I'd like to fix it in time for my summer holidays.
Has anyone got the necessary files to restore the low-level data that allow the phone to be recognized again by the LG Mobile Support Tool?
I think that I need these files:
- MPRG8064.hex (or the specific similar file for the Snapdragon 600 CPU)
- 8064_msimage.mbn (it should contain the partition scheme)
- g_emmc.img (i found only the F240 version of this file)
I think that there's also a way to get all those files from a working phone... any help will be appreciated.
Thank you!!!
Click to expand...
Click to collapse
Not sure if you were able to fix your problem. I also had the QSHUSB_DLOAD. My phone (E980) was fully bricked. Would not turn on no matter what I did. After 2 days of no sleep and lots of reading and testing...I was able to get my phone back and it is now fully working. I wrote a tutorial here on xda. Here is the link http://forum.xda-developers.com/optimus-g-pro/help/fix-hard-bricked-e980-t2829684 Hope this helps.

ricanares said:
Not sure if you were able to fix your problem. I also had the QSHUSB_DLOAD. My phone (E980) was fully bricked. Would not turn on no matter what I did. After 2 days of no sleep and lots of reading and testing...I was able to get my phone back and it is now fully working. I wrote a tutorial here on xda. Here is the link http://forum.xda-developers.com/optimus-g-pro/help/fix-hard-bricked-e980-t2829684 Hope this helps.
Click to expand...
Click to collapse
Thank you... I will ask you questions on that thread

Il Palazzo said:
Thank you... I will ask you questions on that thread
Click to expand...
Click to collapse
were you ever able to get it unbricked and if yes how were you able to get it unbricked?

Related

[Q] Help: qualcomm hd-usb qdloader 9008

Today I though let's get cm9 on my nice nitro.
What did I do:
Rooted and installed cwm bytes version
installed custom 0.3 of kernelpanic
Today I installed cmw from the market and installed the new version.
Then I installed the cm9 but it stated that the sd card was not mounted (sdcard pointer wasn't right or something).
I tried all kind of things, but cmw would not work.
So I tried to install cwm bytes version again
[HOW TO]Install ClockworkMod Recovery The easy way
and did: dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 and dd if=/sdcard/_ExternalSD/recovery.img of=/dev/block/mmcblk0p6 bs=4096
Then I did a restart
Nothing happened, nothing at all
No screen no download mode
When I connected it to the pc, it has some usb drivers:
qualcomm hs-usb qdloader 9008
Now what?
I am from holland, so getting it back to the US is not a good option, I also don't have an email address from the seller (ebay). I already send him an ebay message, but I don't know if he is still member or something (2 months ago I bought it).
Does someone has a solution?
The name of the windows driver is Qualcomm HS-USB Qdloader 9008
Oh ****, it looks like you flashed CWM to the wrong partition. Um, I think you're going to have to try to unbrick using a .kdz, possibly the SU640 one. My unbricking guide is out of date (my fault, but real life has kept me busy), but all the information you will need is in this thread somewhere. Please read all the posts, particularly ones toward the end of the thread that will tell you how to edit your hosts file and set up a server so that the kdz update tool will let you flash the .kdz file.
Edit, I forgot to mention this will only work if you are able to get into Download Mode. Please confirm if this is the case.
Malnilion said:
Oh ****, it looks like you flashed CWM to the wrong partition. Um, I think you're going to have to try to unbrick using a .kdz, possibly the SU640 one. My unbricking guide is out of date (my fault, but real life has kept me busy), but all the information you will need is in this thread somewhere. Please read all the posts, particularly ones toward the end of the thread that will tell you how to edit your hosts file and set up a server so that the kdz update tool will let you flash the .kdz file.
Edit, I forgot to mention this will only work if you are able to get into Download Mode. Please confirm if this is the case.
Click to expand...
Click to collapse
I doubt it. p6 is the SBL (secondary bootloader), I think emergency mode depends on it.
I cannot get into download mode, I only see ethe qualcomm driver in windows, nothing else. No screen, no nothing.
Your situation is not good. Your best bet at this point is probably getting it repaired by LG/AT&T unless aremcee or someone more knowledgeable than myself can help you rescue it somehow. Whoever's post you followed that told you to flash to p6 was horribly, horribly misguided. Unfortunately, as you know now, flashing roms the manual way can be really dangerous if you overwrite the incorrect partition. I'm sorry it ended the way it did for you...
Yeah I think I screwed up... I just wanted to get ICS on the phone, anyway.
How can I repair it? My seller does not respond, is there a possibility that someone else can get it to at&t for repairs? or wouldn't that be possible?
maybe ask someone to pull (dd if=) their sbl p6 and you could try to overwrite whatever is on yours now.
worth a shot, I know on samsung phones if this happens you need a .pit files, which will help repartition. I dont know if LG has a similar option.
what software do I have to use to get the new p6 on the phone, for samsung there is ODIN, but for lg?
See, that's the thing, the closest thing we have to Odin is the KDZ update tool and as far as I know they both kind of have a caveat of needing the emergency/download mode intact. I really don't know if there is any way to rescue your device without physically getting in it and reflashing, which most people are not equipped to do.
adb probably is no go as well huh? or you would see android/LG driver...
if this was another device I may have more ideas, but I have no exp. with LG.
{tell them you just hooked it up to Itunes to sync your playlist....an it went all weird.. hahahah}
Not sure how releveant this is but I think one of the Qualcomm Phone tools may have an option for raw memory read & raw memory write.
For example READ_MEM from address 0x0200000 to 0x0250000 (from a device with a working sbl of course) and dump it to a file.
Then WRITE_MEM and cross your fingers. Very dangerous and would take some research to find the sbl memory address.
A long shot more geared towards the technically inclined.
Is there someone who can make my phone work again? I can pay you for it, otherwise I will sell the phone, broken as it is.
My seller won't respond, so I have nowhere to go. If someone want to help me, you are welcome.
search an try a jtag solution
roydejong said:
Is there someone who can make my phone work again? I can pay you for it, otherwise I will sell the phone, broken as it is.
My seller won't respond, so I have nowhere to go. If someone want to help me, you are welcome.
Click to expand...
Click to collapse
You know, you could always ship it off to LG. I sent them mine after having the EXACT same problem, and they fixed it and it's on its way home right now!
Did you have to pay for this? Do you have the contact info? Thanks.
foxdl99 said:
Did you have to pay for this? Do you have the contact info? Thanks.
Click to expand...
Click to collapse
Don't have to pay, they can't turn it on, so how would they know ? Just go to their website and fill out a warranty support form.
rani9990 said:
Don't have to pay, they can't turn it on, so how would they know ? Just go to their website and fill out a warranty support form.
Click to expand...
Click to collapse
Does it have to be within one year of original purchase and do you have to show proof of original purchase?
Sent from my LG-P930 using xda app-developers app
i can help with jtag method
or you can buy the medusa box (like me) but it's not easy to solder the wire
nickmatine said:
i can help with jtag method
or you can buy the medusa box (like me) but it's not easy to solder the wire
Click to expand...
Click to collapse
i have the same issue with my lg connect ms 840.
would you mind to share how to unbrick it.
i only have riff box here
tyvm
For the jtags you first need to check if the cpu is supported. If it is, all you have to do is disassemble the device, locate the pins solder up and go for it. Some other model may have same pinout. Just make sure it is same layout, and check if vref and gnd are in the same place. If successful connection is achieve, you just need converted files from box support. Send them full stock rom for your model. If cpu is not supported, it will take longer and will be harder. Get into the forum support of either, medusa and riff. For the OP, see if you can send it to LG but if you can't, someone at forum that lives nearby you could help you. Only solution afaik is jtag.
Sent from my Abacus

[Q] Unbrick the E980

My phone is bricked, it's in the Qualcomm QDLoader mode (QHSUSB_DLOAD).
I took it to a shop to get it jtaged with the riff box but they could not get it to connect for some reason :crying: so I really need to get it fixed using USB.
It seems they have the solution here:
http://www.zpsjbbs.com/thread-5097-1-1.html
But I cannot figure out how to register and download the .hex and .mbn files. Of course I googled those files and got another ones but they did not work, the specific files for the E980 are needed.
Does anyone have access to those files in that forum?
Thanks in advance,
David
non-english
Daved+ said:
My phone is bricked, it's in the Qualcomm QDLoader mode (QHSUSB_DLOAD).
I took it to a shop to get it jtaged with the riff box but they could not get it to connect for some reason :crying: so I really need to get it fixed using USB.
It seems they have the solution here:
http://www.zpsjbbs.com/thread-5097-1-1.html
But I cannot figure out how to register and download the .hex and .mbn files. Of course I googled those files and got another ones but they did not work, the specific files for the E980 are needed.
Does anyone have access to those files in that forum?
Thanks in advance,
David
Click to expand...
Click to collapse
As it is non-English do not know what the link is...however, if it powers up the return to stock worked for me...
That sounds like something beyond a simple flash back to stock. If you took it for jtag and they could not get it, your only real option is LG service.
Sorry, but that sucks.
donalgodon said:
That sounds like something beyond a simple flash back to stock. If you took it for jtag and they could not get it, your only real option is LG service.
Sorry, but that sucks.
Click to expand...
Click to collapse
LG service was my first option and they did not take my phone because it's an US model and I'm not in the US.
I just want the files from that link and try with QPST and see what happens
I already got the files. They are not good for the E980
Daved+ said:
I already got the files. They are not good for the E980
Click to expand...
Click to collapse
It works fine for e980, of course you need e980's image file to make it work
cgigate said:
It works fine for e980, of course you need e980's image file to make it work
Click to expand...
Click to collapse
Are you willing to help me? Thank you
Daved+ said:
Are you willing to help me? Thank you
Click to expand...
Click to collapse
How could i help you ?
You mentioned link that provided the positive solution for you.
Or you need simple to send LG to get warranty service.
or send to me to get it fixed
cgigate said:
How could i help you ?
You mentioned link that provided the positive solution for you.
Or you need simple to send LG to get warranty service.
or send to me to get it fixed
Click to expand...
Click to collapse
I've said "it seems they have the solution"...
I already posted about the LG service, it's where I took it first.
Closed, per OP request

I totally messed everything up (stuck with brick)

I am an idiot..
Long story short my LG-D852 RGS is showing as an LG-D857 in LG FlashTool and I am unable to flash the correct rom as I keep getting an error message:
"Download fail!! Device model is different"
I somehow flashed my D852 to a D857 while messing around, and now I can not find any way to recover to factory.
Anyone have any solutions that can rescue me from this bricked phone?! PLEASE
If you want some good help to recover your phone go to this thread and ask for help or ask even if it is possible since you flashed the wrong ROM.
http://forum.xda-developers.com/showthread.php?t=2785089
The maintainer of this thread is a really nice guy and has helped thousands of people with these sort of problems.
Hope this helps you somehow.
droidbits said:
If you want some good help to recover your phone go to this thread and ask for help or ask even if it is possible since you flashed the wrong ROM.
http://forum.xda-developers.com/showthread.php?t=2785089
The maintainer of this thread is a really nice guy and has helped thousands of people with these sort of problems.
Hope this helps you somehow.
Click to expand...
Click to collapse
Only way you can fix it is probably kick it into Qualcomm USB Loader 9008 mode
itsbighead said:
Only way you can fix it is probably kick it into Qualcomm USB Loader 9008 mode
Click to expand...
Click to collapse
Yes I actually agree with that.
Here is the link to that thread which is actually closed but the OP of this thread here can have a good read and perhaps Google for the software to download.
http://forum.xda-developers.com/showthread.php?t=3072091
I actually fixed it using a modified .DLL file that bypassed the model mismatch so I used it with the stock bell 5.0.1 and LG flash tool and it finally worked
jetpackjeff said:
I actually fixed it using a modified .DLL file that bypassed the model mismatch so I used it with the stock bell 5.0.1 and LG flash tool and it finally worked
Click to expand...
Click to collapse
Very glad you got it sorted. Another success story!
I am confident this phone is basically unbrickable, much like other LG devices I've had in the past

D851 converted to D850 looking for a way back

Hi guys;
So i bought a second hand unlocked D851 ( TMOBILE) with kitkat (cloudy rom) wanted to upgrade it to lolipop but i hard bricked it then used board diag program to bring it back to life but i extracted a d850 rom TOT since the d851 didnt work so now my lg g3 is at&t and permenantly locked ,been trying for a week now to unlocked it for nothing then I read somewhere in this forum that its easy to unlock the d851 using the tmobile app. so is there any way to change it back to D851.
Anyone has any idea?!!
how u use the board diag cuz im stock in qualcomm hs-usb qdloader 9008 and the threadt is closed now
ipus89 said:
how u use the board diag cuz im stock in qualcomm hs-usb qdloader 9008 and the threadt is closed now
Click to expand...
Click to collapse
Try this thread... it is still open & active: https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
startswithPendswithOOH said:
Try this thread... it is still open & active: https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
how about my problem??!!!
nice8man said:
how about my problem??!!!
Click to expand...
Click to collapse
1)What do you mean permanently locked...carrier/sim, mcafee security, something else? If it's carrier you can order a sim unlock code off of ebay for @$4.00 us, or use any other sim unlock services out there.
2)If you changed a d851 to a d850 using board diag and manually loading the partitions - then why not extract a d851 tot and do the same thing?
startswithPendswithOOH said:
1)What do you mean permanently locked...carrier/sim, mcafee security, something else? If it's carrier you can order a sim unlock code off of ebay for @$4.00 us, or use any other sim unlock services out there.
2)If you changed a d851 to a d850 using board diag and manually loading the partitions - then why not extract a d851 tot and do the same thing?
Click to expand...
Click to collapse
thank you for the reply.
1- its carrier unlock + i have no online wallet and i cant get one
2- thats what im looking for is there a way to manually load d851 partitions i mean when i loaded d850 partitions my phone was in dload mode ( hard bricked) do i have to hard unbrick now again?
by the way i can search for other carriers and i find mine under rat:GSM but i m unable to connect to it .
nice8man said:
thank you for the reply.
1- its carrier unlock + i have no online wallet and i cant get one
2- thats what im looking for is there a way to manually load d851 partitions i mean when i loaded d850 partitions my phone was in dload mode ( hard bricked) do i have to hard unbrick now again?
by the way i can search for other carriers and i find mine under rat:GSM but i m unable to connect to it .
Click to expand...
Click to collapse
1) I don't know of a free way to get an unlock code, so if you can't order one you're probably stuck. Pay a friend who can order one for you?
2) If we're on the same page here and you previously used the board diag tool then that should work again. Hard brick usually shows up in your device manager as qualcomm 9008 instead of an lg device, so to get back to that condition you would have to open the phone up and short a pin -
follow the guide in the link I posted before and you should be good to go. I don't have links for any d851 tot files though...sorry, not my variant.
startswithPendswithOOH said:
1) I don't know of a free way to get an unlock code, so if you can't order one you're probably stuck. Pay a friend who can order one for you?
2) If we're on the same page here and you previously used the board diag tool then that should work again. Hard brick usually shows up in your device manager as qualcomm 9008 instead of an lg device, so to get back to that condition you would have to open the phone up and short a pin -
follow the guide in the link I posted before and you should be good to go. I don't have links for any d851 tot files though...sorry, not my variant.
Click to expand...
Click to collapse
so i need to hard brick my phone again?
nice8man said:
so i need to hard brick my phone again?
Click to expand...
Click to collapse
Unfortunately...I think so. If you were to try and use the lg flash tool and try and tot a d851 file into a d850 it'll probably throw some errors - model check, for ex - and won't flash. You can try and see for yourself if you'd like...here's a link for a couple tools; the 1st is kdz method, second is tot: https://forum.xda-developers.com/showthread.php?t=2785089
To brick it again follow guide I linked( https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359), short that 2nd jtag pin in the pic for @5 seconds, plug in the usb, and it should go to qualcomm 9008. You already know how to do the rest as far as loading partitions and such, and if you don't the guide will tell you what to do.
Good luck :good:
startswithPendswithOOH said:
Unfortunately...I think so. If you were to try and use the lg flash tool and try and tot a d851 file into a d850 it'll probably throw some errors - model check, for ex - and won't flash. You can try and see for yourself if you'd like...here's a link for a couple tools; the 1st is kdz method, second is tot: https://forum.xda-developers.com/showthread.php?t=2785089
To brick it again follow guide I linked( https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359), short that 2nd jtag pin in the pic for @5 seconds, plug in the usb, and it should go to qualcomm 9008. You already know how to do the rest as far as loading partitions and such, and if you don't the guide will tell you what to do.
Good luck :good:
Click to expand...
Click to collapse
the link you attached is for mobiles that are already hard bricked mine is not
nice8man said:
the link you attached is for mobiles that are already hard bricked mine is not
Click to expand...
Click to collapse
Yeah....and?
Re-read your previous post where you asked if you'll have to brick it again.
I said yes, and gave you a link on how to do it. Did you read the link? My guess would be no, since the 1st 4 steps tell you how to brick it and enter qualcomm9008 mode.
You're on your own now. Good luck. And you're welcome for the time I spent trying to help you.
startswithPendswithOOH said:
Yeah....and?
Re-read your previous post where you asked if you'll have to brick it again.
I said yes, and gave you a link on how to do it. Did you read the link? My guess would be no, since the 1st 4 steps tell you how to brick it and enter qualcomm9008 mode.
You're on your own now. Good luck. And you're welcome for the time I spent trying to help you.
Click to expand...
Click to collapse
Thank you for your replies man i really appriciate it...i have read that topic like 5 times; maybe i dont understand english very well but when i read the title LG G3 Hard Brick Recovery+ Required Materials:Bricked LG G3 i thought he meant that this topic is for people that has thier phone bricked and need to recover them.
nice8man said:
Thank you for your replies man i really appriciate it...i have read that topic like 5 times; maybe i dont understand english very well but when i read the title LG G3 Hard Brick Recovery+ Required Materials:Bricked LG G3 i thought he meant that this topic is for people that has thier phone bricked and need to recover them.
Click to expand...
Click to collapse
It's cool. Yes the guide is for already bricked phones, but what I was trying to say is since you have a functional phone rt now you're gonna have to brick it, and by brick it I mean qualcomm9008 mode, and that's what the 1st part of the guide shows you how to do by shorting out the pin. Once you get to Qualcomm mode you can then use the board diag tool and load your partitions that you extracted from the tot and hopefully get back to your original d851 phone and get back up and running. Does that make more sense?
Again...good luck
startswithPendswithOOH said:
It's cool. Yes the guide is for already bricked phones, but what I was trying to say is since you have a functional phone rt now you're gonna have to brick it, and by brick it I mean qualcomm9008 mode, and that's what the 1st part of the guide shows you how to do by shorting out the pin. Once you get to Qualcomm mode you can then use the board diag tool and load your partitions that you extracted from the tot and hopefully get back to your original d851 phone and get back up and running. Does that make more sense?
Again...good luck
Click to expand...
Click to collapse
I did not know that you can hard brick the phone by shorting the pins; thank you.
startswithPendswithOOH said:
It's cool. Yes the guide is for already bricked phones, but what I was trying to say is since you have a functional phone rt now you're gonna have to brick it, and by brick it I mean qualcomm9008 mode, and that's what the 1st part of the guide shows you how to do by shorting out the pin. Once you get to Qualcomm mode you can then use the board diag tool and load your partitions that you extracted from the tot and hopefully get back to your original d851 phone and get back up and running. Does that make more sense?
Again...good luck
Click to expand...
Click to collapse
I hard bricked it again and then extracted another D851 tot and then loaded all the necessary partitions but the phone still on qload mode i copied the sbl1.mbm of the D850 and tried them with D851 partitions the phone revived but not in download mode.
I managed tp recover all partitions and the phone is on dowloading mode but still detected as d850 so i have the dll cross error everytime i try to flash a rom even with using the custon dll file.

Question Oneplus 9 Pro T-MO (LE-2127) Revert to stock and fix modem. Will donate.

I flashed my device using the Indian MSM Tool and I am unable to revert back the stock T-Mobile flash using the T-Mo MSM Tool. Now my mobile radio will not enable. I tried flashing multiple T-Mobile modems that are posted on here and that did not fix the issue. So let me summerize.
Can someone guide me to 1) Flashing back to the T-Mobile stock firmware from the IN version, and or 2) Help me get my radios working again. I'd be willing to donate to whoever can help me resolve this issue!
Thanks!
Thanks, unfortunately it didn't work for me. My IMEI, MAC Addresses, and fingerprint functionality is still working. Now it's not recognizing my SIM card at all.
@FizzyAps @craznazn Do yall have any suggestions? Seems yall are the all stars here!
ripclap said:
Thanks, unfortunately it didn't work for me. My IMEI, MAC Addresses, and fingerprint functionality is still working. Now it's not recognizing my SIM card at all.
@FizzyAps @craznazn Do yall have any suggestions? Seems yall are the all stars here!
Click to expand...
Click to collapse
India MSM is known to screw things up and make devices think they are LE2120 instead of whatever it originally was, but at the same time, that's what makes it able to also flash ColorOS over to Oxygen easily...
I remember people solving something like issue on this forum, might need to search extensively.... I haven't had my OP9P for over 6 months now probably, so I can't help much... best of luck!
bencozzy said:
Is it possible to pop a different sim in to see if it recognizes it? Could be the sim.
Click to expand...
Click to collapse
I tried 2 others but no luck.
craznazn said:
India MSM is known to screw things up and make devices think they are LE2120 instead of whatever it originally was, but at the same time, that's what makes it able to also flash ColorOS over to Oxygen easily...
I remember people solving something like issue on this forum, might need to search extensively.... I haven't had my OP9P for over 6 months now probably, so I can't help much... best of luck!
Click to expand...
Click to collapse
[]
I really hate to say this. But I don't think there's no coming back from India os. I did the same thing not once but twice. I called T-Mobile and used my insurance. Only way. Read the topic in this forum bout the India msm tool. Idk if u noticed how much different the India os is from the eu and global os. But if there's away I wanna know also. Cause now the only msm tool your going to be able to use is the India one. But you can update to the a12 one of the color or oxygen I can't remember but ur modem will come on everything will be fine for a few days then it will start messing up again.
ripclap said:
I flashed my device using the Indian MSM Tool and I am unable to revert back the stock T-Mobile flash using the T-Mo MSM Tool. Now my mobile radio will not enable. I tried flashing multiple T-Mobile modems that are posted on here and that did not fix the issue. So let me summerize.
Can someone guide me to 1) Flashing back to the T-Mobile stock firmware from the IN version, and or 2) Help me get my radios working again. I'd be willing to donate to whoever can help me resolve this issue!
Thanks!
Click to expand...
Click to collapse
have you read this thread yet?
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com
amaroney55 said:
I really hate to say this. But I don't think there's no coming back from India os. I did the same thing not once but twice. I called T-Mobile and used my insurance. Only way. Read the topic in this forum bout the India msm tool. Idk if u noticed how much different the India os is from the eu and global os. But if there's away I wanna know also. Cause now the only msm tool your going to be able to use is the India one. But you can update to the a12 one of the color or oxygen I can't remember but ur modem will come on everything will be fine for a few days then it will start messing up again.
Click to expand...
Click to collapse
I think you're right. I'm going to RMA it with Oneplus.
I thought with my persist, modest1, and modemst2 I could SMT flash it and restore those files but I get a OnePlus write protection using edl and the OEM Unlocking option will not enable in the OS now. Hopefully they warranty repair it. That's my only concern. It's fairly new lol
Sorry I am just going on what that one thread was saying. And my experience I had to make TMobile believe that it was the phone breaking. Be sure to switch it back to the TMobile os. If the msmtool doesn't work fastboot flash it back before u take it back. The 2nd time they went through my phone saw I had the xda app they really started questioning me. I grabbed my phone back and said umm why u looking in my phone privacy dude. You're concern is only with network and data not my apps files and folders. But just save ya some trouble
amaroney55 said:
Sorry I am just going on what that one thread was saying. And my experience I had to make TMobile believe that it was the phone breaking. Be sure to switch it back to the TMobile os. If the msmtool doesn't work fastboot flash it back before u take it back. The 2nd time they went through my phone saw I had the xda app they really started questioning me. I grabbed my phone back and said umm why u looking in my phone privacy dude. You're concern is only with network and data not my apps files and folders. But just save ya some trouble
Click to expand...
Click to collapse
I'll just flash it clean to where it doesn't even boot lol
Maybe its a bit off topic... but what do we learn about it? NEVER buy a carrier branded device if you want play with root. The lower price is not worth. I learned that over 10yrs ago xD
RheinPirat said:
Maybe its a bit off topic... but what do we learn about it? NEVER buy a carrier branded device if you want play with root. The lower price is not worth. I learned that over 10yrs ago xD
Click to expand...
Click to collapse
Yea I learned my lesson
What sucks is I have the modemst1, modemst2, and persist image backups but I cannot unlock it to upload. I am trying to modify the MSM Tool settings.xml to patch the modemst and persist images and I almost had success using the SMT Downloader but I think I don't have the offset bytes set properly to match the partition table.
Try this, worked for me from In back to TMO....
File on MEGA
mega.nz
TheGhost1951 said:
Try this, worked for me from In back to TMO....
File on MEGA
mega.nz
Click to expand...
Click to collapse
Internet explorer user spotted. xD
ekin_strops said:
Internet explorer user spotted. xD
Click to expand...
Click to collapse
Beg your pardon, I used the Indian MSM to unbrick before I was aware of it changing my TargetID to IN. Now I have to use a modded MSM tool to flash TMO firmware. I use Python3 to extract the .ops file, then open settings.xml, remove the "Target" line at the bottom encrypt back to a .ops file with the name out.ops and then flash that with the MSM tool. Then it will flash the TMO firmware and you are good to go.......
- op6 user - its destroyed now
but as i see that u cant use any other msm but the indian one? right?
i destroyed my op6 system and partations before,
OnePlus Agency, tried to fix it but no luck, i fixed it by msm but not the normal one
if 9pro msm is the same as op6 so you should do this
first, take twrp backup of EFS and MODEM partations and VENDOR ( idk if vendor is important but for precaution )
take another backup of EFC and MODEM by any root apps for precaution too
use the t-mobile msm flashtool and press on verify
the SMT mode should be able to use now
go to options, turn on the COM box or whatever
start flashing with SMT, but i think its high risk bc idk what error you get by normal flashing
keep in mind that SMT Mode will reFlash all known partations and hidden, hidden like MODEM, EFS, etc
my story with this is long, but funny for me, and big lesson..
thx for allah
@ripclap
edit: forget to tell that u have to restore the EFS backup, u should root t-mobile version or idk if u can restore it with some apps without root i dont remember
with op6 old firmware there is something called nvBackupUI it allow us to backup EFS and Restore it by one file
i know this maybe too old now but it may help
edit2:
some links about backup and restore EFS
1- https://community.oneplus.com/thread?id=278167
2- https://www.getdroidtips.com/how-to-backup-or-restore-qcn-efs-on-qualcomm-devices/
3- https://www.droidthunder.com/how-to-backup-efs-imei-on-android-phones/
ALL of this is for SMT Mode, because it may clear the EFS partation and Root is needed to restore it, idk if there is non root method, do ur own search

Categories

Resources