Related
I bought a g4 near a week ago and it says on the back sticker that its H811 but when i entered download mode it was korean and i found something mentioning f500 any way i flashed 20r kdz for h811 and phone bricked(9008 mode)then i used ls991 mbn file to use in QFIL and revive my phone now when i flash any kdz for h811 phone bricks and i have to flash mbn files again however the phone boots up but no camera no imei no baseband im very confused can anyone help?
Any chance that flashing f500l tot file revive the phone?
Thanks.
shamescool said:
I bought a g4 near a week ago and it says on the back sticker that its H811 but when i entered download mode it was korean and i found something mentioning f500 any way i flashed 20r kdz for h811 and phone bricked(9008 mode)then i used ls991 mbn file to use in QFIL and revive my phone now when i flash any kdz for h811 phone bricks and i have to flash mbn files again however the phone boots up but no camera no imei no baseband im very confused can anyone help?
Any chance that flashing f500l tot file revive the phone?
Thanks.
Click to expand...
Click to collapse
may have to dissassmble the device and find out what motherboards on it weve seen cases like this before and its not easy i would return it and say wtf
TheMadScientist420 said:
may have to dissassmble the device and find out what motherboards on it weve seen cases like this before and its not easy i would return it and say wtf
Click to expand...
Click to collapse
you would say there is a chance to recover it or not?does it worth it?
Thanks for reply
shamescool said:
you would say there is a chance to recover it or not?does it worth it?
Thanks for reply
Click to expand...
Click to collapse
In my opinion no its not worth the hassle but ot only takes 5 mine to check ot 2. Unless its got the bootloop issue or hard bricked its fixable. But how determined are you.
TheMadScientist420 said:
In my opinion no its not worth the hassle but ot only takes 5 mine to check ot 2. Unless its got the bootloop issue or hard bricked its fixable. But how determined are you.
Click to expand...
Click to collapse
my phone boots up completely but no baseband no imei or anything and that infamous 9008 brick is fixable with ls991 laf.img and 8992.mbn and etc... files and here is my next approaches please if you have enough aknowledge guide me with these options i have or add any if something came on your mind:
1.Flashing a ls991 model kdz and see what comes out(probably not doable,lgup may not let me flash it)
2.while surfing through the forums and threads i found the exact H811 10N Laf.img and i will replace it with ls991's and will use QFIL to correct the partitions and then my phone would be fixed(im too scared for this one...maybe my phone is a refurbished F500...who knows? :fingers-crossed: )
3.Maybe finding and flashing F500 laf.img fix the phone but a HUGE problem i am facing:where to find that file?
Note:All i am trying to do is to fix this phone by software approaches and disassembling the phone is out of my options for now(only will do if none of above fix it properly)
So with all of that what would you do if you be in my shoes?:cyclops:
Always hated LG and admired Sony but i started to hate xperia x series because of weak development so i bought this one for around 100$ in your currency.:laugh:
Id send it back.
TheMadScientist420 said:
Id send it back.
Click to expand...
Click to collapse
My curiousity will kill me someday
I believe i can fix it and beside that learning new things about lg devices is interesting since i bought it for only 100 bucks from an old pal who does nt know what actually smart phone is:laugh:
Anyway i learnt how to extract laf from kdz files and im going to test both f500l and h811 and pray:cyclops:
if i fix it properly i would make a thread to share my experience with this refurbished(dont know actually if it is)
phone and help people who brick their refurbished phone and dont know how to fix it
shamescool said:
My curiousity will kill me someday
I believe i can fix it and beside that learning new things about lg devices is interesting since i bought it for only 100 bucks from an old pal who does nt know what actually smart phone is:laugh:
Anyway i learnt how to extract laf from kdz files and im going to test both f500l and h811 and pray:cyclops:
if i fix it properly i would make a thread to share my experience with this refurbished(dont know actually if it is)
phone and help people who brick their refurbished phone and dont know how to fix it
Click to expand...
Click to collapse
i use the old wilcracks diag toot and lg firware extractor to extract any bins u need
TheMadScientist420 said:
i use the old wilcracks diag toot and lg firware extractor to extract any bins u need
Click to expand...
Click to collapse
then i will use them to crack open kdz from both H811 and F500L firmwares to flash laf and other messed up files with fastboot
but im wondering which one should i try first because im concerned if i flash wrong files then there will be even no 9008 mode to use QFIL and get back to very first step...
What is going to happen exactly when i flash another varient's laf? will it kill the phone completely or will there be any 9008?
Thanks for those apps you mentioned btw:good:
shamescool said:
then i will use them to crack open kdz from both H811 and F500L firmwares to flash laf and other messed up files with fastboot
but im wondering which one should i try first because im concerned if i flash wrong files then there will be even no 9008 mode to use QFIL and get back to very first step...
What is going to happen exactly when i flash another varient's laf? will it kill the phone completely or will there be any 9008?
Thanks for those apps you mentioned btw:good:
Click to expand...
Click to collapse
yea ive been using em since g2.and i use em on all lgs . diag tool is for flashing but at the bottom u can extract
i get my own .dlls for lgg2 flash tool and i flash orig g4 firmware with it still.
if i could find the tot would for g5.
now if u break 9008 jtag i think is the only fix i dont know the pin outs or if the g4 even supports that like the g3 and 2. thats why i say take device apart its fricken easy there should be a sticker on the mother board or stamps that say the mbs model and go from there
TheMadScientist420 said:
yea ive been using em since g2.and i use em on all lgs . diag tool is for flashing but at the bottom u can extract
i get my own .dlls for lgg2 flash tool and i flash orig g4 firmware with it still.
if i could find the tot would for g5.
now if u break 9008 jtag i think is the only fix i dont know the pin outs or if the g4 even supports that like the g3 and 2. thats why i say take device apart its fricken easy there should be a sticker on the mother board or stamps that say the mbs model and go from there
Click to expand...
Click to collapse
dissembled the phone and it was f500l as expected so i decided to go with f500 laf.img and then my phone got fixed up completely ive even replaced modem and other h811 things except for system now my phone is working perfect again and im going to flash a stock based rom's system.img (10N) with fastboot
Thanks for your precious info once again:cyclops:
shamescool said:
dissembled the phone and it was f500l as expected so i decided to go with f500 laf.img and then my phone got fixed up completely ive even replaced modem and other h811 things except for system now my phone is working perfect again and im going to flash a stock based rom's system.img (10N) with fastboot
Thanks for your precious info once again:cyclops:
Click to expand...
Click to collapse
These guys will piece these things together and mislabel crap. Just to make a dollar. Im glad to see ure good to go.
TheMadScientist420 said:
These guys will piece these things together and mislabel crap. Just to make a dollar. Im glad to see ure good to go.
Click to expand...
Click to collapse
Actually LG devices are very easy to disassemble so people like them wont put so much effort to refurbish LG phones and earn themselves some easy money.
And believe me Iran is the heaven of refurbished and chinese phones
Mostly because many cant afford to buy their phones and other stuff from trusted sellers and they buy them with no warranty(or guarranty)from third party sellers.
Actually they have a place for themselves in downtown(Aladdin building).
But i wanted a flagship LG device to learn more about it and i got it for a couple of bucks so it really didnt matter if my G4 didnt work as expected.
But its always a pleasure to make some mystery and try to crack the case by yourself :laugh:
shamescool said:
Actually LG devices are very easy to disassemble so people like them wont put so much effort to refurbish LG phones and earn themselves some easy money.
And believe me Iran is the heaven of refurbished and chinese phones
Mostly because many cant afford to buy their phones and other stuff from trusted sellers and they buy them with no warranty(or guarranty)from third party sellers.
Actually they have a place for themselves in downtown(Aladdin building).
But i wanted a flagship LG device to learn more about it and i got it for a couple of bucks so it really didnt matter if my G4 didnt work as expected.
But its always a pleasure to make some mystery and try to crack the case by yourself :laugh:
Click to expand...
Click to collapse
the whole lg g series is a wonderful device for do it your self i have owned a g2 g3 g4 and now g5 even thought i said i would never by lg again after g4 i got a stylo3 and my wife sports a stylo 2
im working on a us cellular s5 now as we speak and i sometimes run my gs6 edge nut not much since i got g5.
TheMadScientist420 said:
the whole lg g series is a wonderful device for do it your self i have owned a g2 g3 g4 and now g5 even thought i said i would never by lg again after g4 i got a stylo3 and my wife sports a stylo 2
im working on a us cellular s5 now as we speak and i sometimes run my gs6 edge nut not much since i got g5.
Click to expand...
Click to collapse
of course they are great but hardware faults are pretty big deal but for me sony z series were better right until z3+ .for now im happy with my htc u11 and im not going to unlock it or anything.
maybe i use g4 as my secondary device instead of xperia z2.
its a shame that sony is not in its golden age (2011-2013) anymore...
will make a thread to help people like me to unbrick their refurbished device
Thanks for everything
first of all - great job steadfasterX and cWks! with unlocking LG G4
probably I bought (in China) "Frankenstein" LG G4 phone, because it should be H810, but on mainboard is written VS986. I have unlocked it by SALT and instaled TWRP, but I have not find any ROM which would work
based on the information from the vendor it should have V10o ATT firmawe, but in the LG software it shows that is model H815 with firmware V29a.
subsequently I brick it and unbrick it a try to fash .tot files using LG software, but unsuccessful. Because the LGUp shows, that it is model LS991 finally I flash the LS991ZVD.tot file. during booting, the android will stop, when "configuring your phone", probably LS991 files have wrong modem...
now works the download mode and recovery mode only for this phone (no fastboot) and in SALT shows that is ARB4 which is not possible to unlock
Is there any possibility to:
1. to flash correct modem (possibly for VS986?) - 1.a) how is possible to modify the modem in tot file?
2. erase eMMC or go back to ARB2?
I have the backup prepared in TWRP with ARB2, but how us it to recover the phone?
Many, many, many thanks for help!
Or it is easier to buy in Chine the new motherboard? and which?
Thank you very much for answers!!!
Dedulo said:
first of all - great job steadfasterX and cWks! with unlocking LG G4
probably I bought (in China) "Frankenstein" LG G4 phone, because it should be H810, but on mainboard is written VS986. I have unlocked it by SALT and instaled TWRP, but I have not find any ROM which would work
based on the information from the vendor it should have V10o ATT firmawe, but in the LG software it shows that is model H815 with firmware V29a.
subsequently I brick it and unbrick it a try to fash .tot files using LG software, but unsuccessful. Because the LGUp shows, that it is model LS991 finally I flash the LS991ZVD.tot file. during booting, the android will stop, when "configuring your phone", probably LS991 files have wrong modem...
now works the download mode and recovery mode only for this phone (no fastboot) and in SALT shows that is ARB4 which is not possible to unlock
Is there any possibility to:
1. to flash correct modem (possibly for VS986?) - 1.a) how is possible to modify the modem in tot file?
2. erase eMMC or go back to ARB2?
I have the backup prepared in TWRP with ARB2, but how us it to recover the phone?
Many, many, many thanks for help!
Or it is easier to buy in Chine the new motherboard? and which?
Thank you very much for answers!!!
Click to expand...
Click to collapse
Ok well first of all read my signature about the anti roll back details. It is absolutely impossible to flash lower ARB . That's for what it is made for obviously .
Next is that you have flashed stupid files and besides they're with an arb higher than 2 so you cannot unlock it anymore.
we all know that Frankenstein devices are special in many terms .
one example is nobody knows what they do or flash in the primary boot loader which we cannot read out. That means we don't know which RAM is compatible and we do not know if they make any modifications in the signed boot loader stack which ensure they can load Frankenstein devices.
So even if you flash for example h810 files with an arb of 4 it may not load or working properly the same goes for vs 986 of course .
yeah and I have to repeat myself but flashing that arb of 4 was bad in another way,too. Having that arb you have no way to use qfil anymore as that works only up to arb 3. So you have no way to use it to flash for example other models image files or even more important to unbrick your device if it ever hard bricks.
You can of course use a text editor to modify any kdz file and flash whatever you like .. The other option is to use the SD card unbrick method linked in my signature but it requires to hard brick your device first. I can tell you how but in your situation it is very risky if you can't get the SD card unbrick working . so I would recommend to go the Hex editor way just search XDA for how to use it and flash vs986 files with an ARB of 4
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
Ok well first of all read my signature about the anti roll back details. It is absolutely impossible to flash lower ARB . That's for what it is made for obviously .
Next is that you have flashed stupid files and besides they're with an arb higher than 2 so you cannot unlock it anymore.
we all know that Frankenstein devices are special in many terms .
one example is nobody knows what they do or flash in the primary boot loader which we cannot read out. That means we don't know which RAM is compatible and we do not know if they make any modifications in the signed boot loader stack which ensure they can load Frankenstein devices.
So even if you flash for example h810 files with an arb of 4 it may not load or working properly the same goes for vs 986 of course .
yeah and I have to repeat myself but flashing that arb of 4 was bad in another way,too. Having that arb you have no way to use qfil anymore as that works only up to arb 3. So you have no way to use it to flash for example other models image files or even more important to unbrick your device if it ever hard bricks.
You can of course use a text editor to modify any kdz file and flash whatever you like .. The other option is to use the SD card unbrick method linked in my signature but it requires to hard brick your device first. I can tell you how but in your situation it is very risky if you can't get the SD card unbrick working . so I would recommend to go the Hex editor way just search XDA for how to use it and flash vs986 files with an ARB of 4
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
You are right. I have done some stupid steps, because the method for unlocking my "Frankenstein" phone did not work. I read about the anti roll back, but I hoped that something had changed (also the unlocking process has gradually developed )
I had to take apart the phone first and find out what was written on the motherboard This was a big mistake!
Today I have bricked (hard?) my phone by flashing LS991 ZVB ARB3 tot file, because I don't know, how to work with Hex editor.
Which KDZ file I need to download for SD card unbrick? I suppose that VS986 with ARB4, right?
Thanks for a help and reply!
Dedulo said:
You are right. I have done some stupid steps, because the method for unlocking my "Frankenstein" phone did not work. I read about the anti roll back, but I hoped that something had changed (also the unlocking process has gradually developed )
I had to take apart the phone first and find out what was written on the motherboard This was a big mistake!
Today I have bricked (hard?) my phone by flashing LS991 ZVB ARB3 tot file, because I don't know, how to work with Hex editor.
Which KDZ file I need to download for SD card unbrick? I suppose that VS986 with ARB4, right?
Thanks for a help and reply!
Click to expand...
Click to collapse
well I see. the ARB is (as written in the linked guide) a (extreme likely) physical blown fuse, so a process which can not be reverted..
yes you hard-bricked the phone by flashing a lower ARB then the current one. once you flashed ARB 4 you can't flash ARB lower then 4.
the good is as you have hard-bricked it you may be able to use the sdcard unbrick but that requires the 9008 qdl mode:
connect the device to your PC and view the device manager. does it add something like QHUSB BULK? If yes use the vs986 files + UsU files as written the sdcard thread.
You can also use FWUL from booting on USB and just type: lsusb in a terminal after connecting the phone. paste the output here then. It should show something like "QDL 9008" or "QualComm...". If thats the case use the vs986 files + UsU files as written in the sdcard thread.
If both of the above does not show up the QDL 9008 mode.. well try it without battery in again. If it still failing it is likely gone. sorry. The QFIL files available do not work with ARB >3 so.
You can still read on in the sdcard unbrick thread in the second post to find out how to force the sdcard unbrick mode (that differs from the the QDL mode and so need to disassembling the whole mainboard and doing tricky stuff without a guarantee of that it work at the end.)
.-
steadfasterX said:
well I see. the ARB is (as written in the linked guide) a (extreme likely) physical blown fuse, so a process which can not be reverted..
yes you hard-bricked the phone by flashing a lower ARB then the current one. once you flashed ARB 4 you can't flash ARB lower then 4.
the good is as you have hard-bricked it you may be able to use the sdcard unbrick but that requires the 9008 qdl mode:
connect the device to your PC and view the device manager. does it add something like QHUSB BULK? If yes use the vs986 files + UsU files as written the sdcard thread.
You can also use FWUL from booting on USB and just type: lsusb in a terminal after connecting the phone. paste the output here then. It should show something like "QDL 9008" or "QualComm...". If thats the case use the vs986 files + UsU files as written in the sdcard thread.
If both of the above does not show up the QDL 9008 mode.. well try it without battery in again. If it still failing it is likely gone. sorry. The QFIL files available do not work with ARB >3 so.
You can still read on in the sdcard unbrick thread in the second post to find out how to force the sdcard unbrick mode (that differs from the the QDL mode and so need to disassembling the whole mainboard and doing tricky stuff without a guarantee of that it work at the end.)
.-
Click to expand...
Click to collapse
Yes, Q HS-USB QDLoader 9008 is in the Ports (in DevMan), but now I need to prepare SD card, because the old files (which I have used for unbricking last time) do not work .
Dedulo said:
Yes, Q HS-USB QDLoader 9008 is in the Ports (in DevMan), but now I need to prepare SD card, because the old files (which I have used for unbricking last time) do not work .
Click to expand...
Click to collapse
sure. you need ARB 4 files.
.-
Dedulo said:
Yes, Q HS-USB QDLoader 9008 is in the Ports (in DevMan), but now I need to prepare SD card, because the old files (which I have used for unbricking last time) do not work .
Click to expand...
Click to collapse
I don´t find the right kdz for VS986 with ARB4. Can I use yours? (these two with ARB2: http://leech.binbash.it:8008/stock/LG/vs986/2BA/)
Dedulo said:
I don´t find the right kdz for VS986 with ARB4. Can I use yours? (these two with ARB2: http://leech.binbash.it:8008/stock/LG/vs986/2BA/)
Click to expand...
Click to collapse
well you still do not read my linked guide or understand what ARB is, right? Its IMPOSSIBLE to use an ARB lower then 4 in your case. so NO you can NOT use these.
Well I assumed there would be firmware with ARB 4 for the vs986 but it seems the highest is ARB 2..
keep in mind: everything you do now is extremely risky with maybe no point of return! If it bricks and is not switching to the 9008 mode.. you are lost!
After looking around a bit including in my ARB thread (which I mentioned) the LS991 seems to be the only one with ARB higher then 3 (so 4).
you are stuck with LS991 now. that means even when you may be able to unbrick with the sdcard unbrick it means you may never get cell service.
so try a LS991 kdz with ARB 4 (ZVD as you flashed that one should be fine) for the unbrick files to bring it at least back to life.
.-
steadfasterX said:
well you still do not read my linked guide or understand what ARB is, right? Its IMPOSSIBLE to use an ARB lower then 4 in your case. so NO you can NOT use these.
Well I assumed there would be firmware with ARB 4 for the vs986 but it seems the highest is ARB 2..
keep in mind: everything you do now is extremely risky with maybe no point of return! If it bricks and is not switching to the 9008 mode.. you are lost!
After looking around a bit including in my ARB thread (which I mentioned) the LS991 seems to be the only one with ARB higher then 3 (so 4).
you are stuck with LS991 now. that means even when you may be able to unbrick with the sdcard unbrick it means you may never get cell service.
so try a LS991 kdz with ARB 4 (ZVD as you flashed that one should be fine) for the unbrick files to bring it at least back to life.
.-
Click to expand...
Click to collapse
OK, so we understood each other. Because I flashed wrong file LS991 ZVD, I can't go back - only to the same firmware (because of ARB etc.). There is no way to change it (to VS986) or flash anything else
and, if I will be lucky, then the phone comes back to point during booting, when it stops in "configuring your phone". Never use him anymore for call services? How to go through this (configuration)?
There is only one way - to buy in Chine the new motherboard, but which (H815)?
Dedulo said:
OK, so we understood each other. Because I flashed wrong file LS991 ZVD, I can't go back - only to the same firmware (because of ARB etc.). There is no way to change it (to VS986) or flash anything else
and, if I will be lucky, then the phone comes back to point during booting, when it stops in "configuring your phone". Never use him anymore for call services? How to go through this (configuration)?
There is only one way - to buy in Chine the new motherboard, but which (H815)?
Click to expand...
Click to collapse
buy a h811 one as you can unlock h811 within just fastboot.
if you can't get one: the h815 international (so no h815p, h815tr etc) as it can be unlocked officially by the LG website.
if you can't get one: any h815 model should be fine as you can unlock by UsU and I haven't heard any big issues here.
good luck
.-
steadfasterX said:
buy a h811 one as you can unlock h811 within just fastboot.
if you can't get one: the h815 international (so no h815p, h815tr etc) as it can be unlocked officially by the LG website.
if you can't get one: any h815 model should be fine as you can unlock by UsU and I haven't heard any big issues here.
good luck
.-
Click to expand...
Click to collapse
I will try to unbrict it first and we will see... maybee I will wait for motherboard. this will be ok?
https://www.aliexpress.com/item/For...pm=a2g0s.13010208.99999999.259.88b93c00XlwucM
or is there any issue?
thank you very much for your time and help!
Dedulo said:
I will try to unbrict it first and we will see... maybee I will wait for motherboard. this will be ok?
https://www.aliexpress.com/item/For...pm=a2g0s.13010208.99999999.259.88b93c00XlwucM
or is there any issue?
thank you very much for your time and help!
Click to expand...
Click to collapse
I cannot guide you in where to buy or if that one is valid sorry.
.-
steadfasterX said:
I cannot guide you in where to buy or if that one is valid sorry.
.-
Click to expand...
Click to collapse
OK, I understand.
Could you be so kind and send me a link for kdz file? I don't find it. I have only LS991 ZVD tot file. It is possible to convert it to kdz?
Thank you!
I have prepared the SD card from tot file (not bin but img files) except PrimaryGPT.gpt (I don't fin it in tot file, only the PrimaryGPT_0.bin from another KDZ).
The proper KDZ for LS991 ZVD I could not download from LG support site, because my FR phone has IMEI VS986.
Until now the SD card unbricking method doesn't work for me.
I will try LS991 ZVB, which I used for bricking the phone.
Any idea what to do?
Good afternoon friends. I still have a problem on my phone "your device has failed a routine safety ..." after I locked the bootloader. I gave it unofficial for repair, they could not do anything there. But now, for some reason, my phone does not load in edl9008 mode, but there is dowmload mode as on other lg devices (in theory, it should not be). So the question is, how to flash the phone via download mode to any other firmware? The main thing for me is that it starts and I can return twrp to restore my native firmware. Yesterday I tried it through uppercut, lgup didn't work. Does anyone have any knowledge of how to download kdz to this phone?
i wish someone would leak at least one sprint KDZ firmware
blaze2051 said:
i wish someone would leak at least one sprint KDZ firmware
Click to expand...
Click to collapse
Don't think you'll ever see, in your lifetime, a sprint kdz. Nor will you see an at&t one.
It's very important to do some research, initially, before messing with your phone. It's common knowledge that these kdz don't exist, and, that is why we always want to do a full backup of our device, especially when the kdz isn't (nor will ever be) available.
So where are u now? what's the situation? I ask because there are sprint backups around (from individual personal devices), that, if done carefully, can be used to fix a device without messing up the imei and s/n.
AsItLies said:
Don't think you'll ever see, in your lifetime, a sprint kdz. Nor will you see an at&t one.
It's very important to do some research, initially, before messing with your phone. It's common knowledge that these kdz don't exist, and, that is why we always want to do a full backup of our device, especially when the kdz isn't (nor will ever be) available.
So where are u now? what's the situation? I ask because there are sprint backups around (from individual personal devices), that, if done carefully, can be used to fix a device without messing up the imei and s/n.
Click to expand...
Click to collapse
phone is good i made more than one backup just it would be nice just to throw LGup and flash instead of using Qfil or other means of backup
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
Hey all,
My phone has an issue where it's stuck on target IN, but I discovered with the help of retryfail that the target ID is in the param.bin partition. Does anyone have a param.bin they can dump from their phone using EDL or something? This would help me get back to stock.
Thank you,
razercortex
razercortex said:
Hey all,
My phone has an issue where it's stuck on target IN, but I discovered with the help of retryfail that the target ID is in the param.bin partition. Does anyone have a param.bin they can dump from their phone using EDL or something? This would help me get back to stock.
Thank you,
razercortex
Click to expand...
Click to collapse
I'd like the as well if anyone has it for LE2127 TMO c.22 firmware. But if you use a modded msm tool to accommodate the IN TargetID wouldn't the param img get written over and get you back to stock?
If I borrow my wife's phone long enough, I can get it. She has the same LE2127 9 Pro....
Here you go....
if it works, let me know and include the steps you took....please!
Hi all,
In order to use the file, unlock bootloader, then reboot to fastbootd. From fastbootd, run "fastboot flash param param.bin". You will be able to run stock TMO MSM after this. It doesn't really matter what FW version you are on, you can flash it anyway as long as it's a TMO device.
razercortex said:
Hi all,
In order to use the file, unlock bootloader, then reboot to fastbootd. From fastbootd, run "fastboot flash param param.bin". You will be able to run stock TMO MSM after this. It doesn't really matter what FW version you are on, you can flash it anyway as long as it's a TMO device.
Click to expand...
Click to collapse
You successfully got rid of Target is IN with this? How do you check it?
Yaaaaaaa....!!!!!!
TheGhost1951 said:
if it works, let me know and include the steps you took....please!
Click to expand...
Click to collapse
You'll need to generate new unlock token after you flash this, otherwise you won't be able to unlock bootloader.
TheGhost1951 said:
You successfully got rid of Target is IN with this? How do you check it?
Click to expand...
Click to collapse
Try to flash regular TMO MSM.
TheGhost1951 said:
Yaaaaaaa....!!!!!!
Click to expand...
Click to collapse
I'm so happy for you bro!!
TheGhost1951 said:
Yaaaaaaa....!!!!!!
Click to expand...
Click to collapse
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
Oh my god. I've been dealing with this stupid indian thing for months, I gave up on trying anymore. No matter what I did , I could never get a normal UNMODDED TMobile msm to run for me.
But I got it now.
Followed the steps above. Unlocked bootloader, went into fastbootd and flashed the param.bin from above, and immediately after that I shut the phone off right from fastbootd mode. Started my TMobile msm tool , plugged it in and we are good!
I'm shocked at how easy of a solution this was, I was trying so many other long drawn out trial and errors and it was truly this easy
razercortex said:
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
Click to expand...
Click to collapse
hold on...
razercortex said:
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
Click to expand...
Click to collapse
razercortex said:
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
Click to expand...
Click to collapse
I encourage you to make a new How-To thread in this forum with instructions on how to fix the target IN problem. There are a quite a few people who are stuck on IN after using the Indian MSM tool. I saw it being asked a bit in the OnePlus telegram group a few months back too. Good work.
It's one more thing off the list for us to have complete control of our device. Since we have the last "real" OnePlus phone with msm tool, the development on this device may go on for a long, long time
Sorry guys, I pulled my param.bin file because deep inside some settings my wife's name was on my phone. I used her param.bin because it was pure TMO... Personal reasons and security reasons as well... hope y'all understand. and as it is I have now gone with flashing my phone to global...... i actually like it better. Got away from a branded phone!
Appreciative said:
I encourage you to make a new How-To thread in this forum with instructions on how to fix the target IN problem. There are a quite a few people who are stuck on IN after using the Indian MSM tool. I saw it being asked a bit in the OnePlus telegram group a few months back too. Good work.
It's one more thing off the list for us to have complete control of our device. Since we have the last "real" OnePlus phone with msm tool, the development on this device may go on for a long, long time
Click to expand...
Click to collapse
I'm going to refrain from doing so because it can potentially cause side effects, but if anyone wants to do so, by all means.
TheGhost1951 said:
Sorry guys, I pulled my param.bin file because deep inside some settings my wife's name was on my phone. I used her param.bin because it was pure TMO... Personal reasons and security reasons as well... hope y'all understand. and as it is I have now gone with flashing my phone to global...... i actually like it better. Got away from a branded phone!
Click to expand...
Click to collapse
At least we know it's possible now. Do you think we need a pure virgin new in box param or do you think there are specifics to the device and that's why he ( @razercortex ) needed persist also? (I was under the impression that persist was device specific)
I also understand your reservations @razercortex, I suppose we can point people here when it comes up, they can read the thread and understand the risks. I'm not stuck on IN but I knew it was possible to undo something the msm package did and I'm glad to see @TheGhost1951 was finally able to undo it. I knew he felt the same way about undoing whatever was done by the IN msm. Maybe someone can piece together a custom repair msm using a virgin param...but maybe I'm getting ahead of myself