Related
Hi all,
not long ago the update to 10.0.8.0 seriously bricked my Mi A2 Lite.
I still do not really know why, but I have managed to get it alive again - mostly. The only thing no longer working is - the mobile phone part
When inserting a SIM, the IMEI gets shown as 00 (on both slots).
Reading the qcn via Qualcomm-Tools crashes the tool after 16kb - so I guess that part is corrupted also? (And no, I got no idea how a "normal" EDL-flash could do this).
And as I only learned about all this AFTER having the trouble - of course I have no valid qcn-Backup of my own
So, could anybody send me a backup of their qcn-File (of course, set your IMEIs to 000000000000)? I still have my IMEIs (as numbers), so this would probably enable me to revive my phone.
The only MiA2Lite qcn file I could find on the internet seems to be for another hardware revision ...
Hmm, as nobody answered, ca at least somebody provide me with images of modemst1 and modemst2?
dd if=/dev/block/bootdevice/by-name/modemst1 of=/storage/emulated/0/Download/modemst1.img
dd if=/dev/block/bootdevice/by-name/modemst2 of=/storage/emulated/0/Download/modemst2.img
Afterwards, there should be modemst1.img and modemst2.img in the "Download" directory of your internal Storage
Of course, needs root to do it - or twrp ...
Many thanks!
This guide seems to indicate you don't need modemst?
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-to-fix-efs-corruption-sim-card-t3928910
Thanks for the link.
I flashed via EDL "from the beginning" (i.e. the first version), but I did not erase modem before ...
So, I'll definitely try that - it's not that I could "destroy" much more
So - no luck
Even after following the instructions in the thread to the letter, my IMEI still shows as 0
But if that thread really worked for other people that means that it's probably NOT the modemst1/modemst2 partitions that got corrupted on my phone.
Of course, there are a LOT of other partitions that do NOT get flashed during a fastboot-Recovery (fsc, fsg, ssd, ...).
After learning all this, I made a backup of all of them for my other phone(s), but the Mi A2 Lite is still dead.
Ah, I guess if no one has a qcn-File it's time to re-lock the bootloader and send it in for repairs ... luckily I have a BQ X2 Pro that still works great ...
merlinwv said:
Hi all,
not long ago the update to 10.0.8.0 seriously bricked my Mi A2 Lite.
I still do not really know why, but I have managed to get it alive again - mostly. The only thing no longer working is - the mobile phone part
When inserting a SIM, the IMEI gets shown as 00 (on both slots).
Reading the qcn via Qualcomm-Tools crashes the tool after 16kb - so I guess that part is corrupted also? (And no, I got no idea how a "normal" EDL-flash could do this).
And as I only learned about all this AFTER having the trouble - of course I have no valid qcn-Backup of my own
So, could anybody send me a backup of their qcn-File (of course, set your IMEIs to 000000000000)? I still have my IMEIs (as numbers), so this would probably enable me to revive my phone.
The only MiA2Lite qcn file I could find on the internet seems to be for another hardware revision ...
Click to expand...
Click to collapse
You just need MiFlash.exe and "daisy_global_images_V10.0.3.0.PDLMIXM_9.0" thats it, when you flash the device, you can unlock the bootloader again or update via OTA if you want, i brick my device 3 times, and i had no problem with that, if you need a tutorial send PM and i give you instructions
Links
MiFlash: https://en.miui.com/thread-2197836-1-1.html (portable)
V10.0.3.0.PDLMIXM ROM: https://en.miui.com/download-354.html
Jaie55 said:
You just need MiFlash.exe and "daisy_global_images_V10.0.3.0.PDLMIXM_9.0" thats it, when you flash the device, you can unlock the bootloader again or update via OTA if you want, i brick my device 3 times, and i had no problem with that, if you need a tutorial send PM and i give you instructions
Click to expand...
Click to collapse
I think you misunderstood my post. My phone boots again and everything - It's just the mobile network part that's no longer working.
I do not think that flashing 10.0.3.0 will change something with that?
merlinwv said:
I think you misunderstood my post. My phone boots again and everything - It's just the mobile network part that's no longer working.
I do not think that flashing 10.0.3.0 will change something with that?
Click to expand...
Click to collapse
I understand, but, when you flash again, you fix all problems
https://drive.google.com/open?id=189zN6FrXniO8KTq7lhNXkk6_56-GQnkp
Hi, I'm begging you all for help.
Please, even if you don't know the answer, share any sort of advice.
I'm not a newbie (25+ years story of Unix/Reversing), but I know nothing about radio.
Here's a list of symptoms:
1) Sometimes the WIFI MAC Address comes up as 02:00:00:00:00:00 and IMEI isn't available, then they both magically come up (without rebooting, after the SIM Is read - see n. 2)
2) It keeps powering ON & OFF the SIM and switching between Connected , No Signal , Emergency. Sometimes taking the SIM out & back in helps. Selecting the Preferred Network Type from the modem debug screen keeps it connected for long periods.
3) It won't search for alternative networks to Register Manually
3) IMS Registration is showing as Not Registered always, even while it's connected: Voice + Data (?!?)
4) From the Debug Info only 1 cell appears as SRV = R+N and has a CELL ID, so it seems it connects only to 1 cell at a time.
I can't post screenshots as I lost my old username here, so I signed-up again.
Nothing works, it was a new phone. I wanna die.
Thank you all for your help.
Thanks.
I have problems with modem and camera wgen updating ta android 9.
I would recomend you to rollback to 10.2.1.0
I would use this method
1. Backup your media files to your computer
2. Unlock bootloader
3. Download fastboot china version of 10.2.1.0 and Flash it with mi flash (choose wipe but dont lock!)
4. Flash orange fox twrp with fastboot
5 wipe all partitions exvept internal storage with orangefox
6. Download 10.2.1.0 from xiaomi.eu and flash it with orangefox
Tell me is you want direct links to all files that you need.
If you still have problems after downgrading I can prove my persist and modem files
Good luck
eliaztheone said:
I would recomend you to rollback to 10.2.1.0
Click to expand...
Click to collapse
@eliaztheone thank you for your reply and your offer about the files, I'll take it if necessary.
Just one question: won't that trigger Anti-Rollback ?
(I don't need to stay on MIUI: do I have other options?)
DoYouWantFriesWithThat said:
@eliaztheone thank you for your reply and your offer about the files, I'll take it if necessary.
Just one question: won't that trigger Anti-Rollback ?
(I don't need to stay on MIUI: do I have other options?)
Click to expand...
Click to collapse
Your anti rollback is already triggered on 4. Thats the arb value on 10.2 too. As long as you dont flash older miui 9 firmware you should be ok...
eliaztheone said:
Your anti rollback is already triggered on 4. Thats the arb value on 10.2 too. As long as you dont flash older miui 9 firmware you should be ok...
Click to expand...
Click to collapse
The roll-back went well but the phone is still unstable.
I'm not sure why: did the Persist get corrupted? Or the EFS partition? I have some backups but I'm not sure what to do.
Can you provide the files that you mentioned, or maybe some pointers?
What could be wrong with the phone?
Thanks a lot @eliaztheone
DoYouWantFriesWithThat said:
The roll-back went well but the phone is still unstable.
I'm not sure why: did the Persist get corrupted? Or the EFS partition? I have some backups but I'm not sure what to do.
Can you provide the files that you mentioned, or maybe some pointers?
What could be wrong with the phone?
Thanks a lot @eliaztheone
Click to expand...
Click to collapse
I can give you my efs and persist backup if you want? Then you can use partitions backup and restorev from playstore.
You need to be rooted with magisk to restore
Are you on the xiaomi.eu version of 10.2.1.0 and is it the 8.1 version or 9.0?
eliaztheone said:
I can give you my efs and persist backup if you want? Then you can use partitions backup and restorev from playstore.
You need to be rooted with magisk to restore
Are you on the xiaomi.eu version of 10.2.1.0 and is it the 8.1 version or 9.0?
Click to expand...
Click to collapse
I am on Xiaomi.eu 10.2 with Android 9 now, as you suggested. Rooted & with Magisk.
I have backups of my old PERSIST from the China 9.x ROM. Should I flash that (or do I risk bricking) ?
I was reading on persist.img and I don't understand one thing: if it's different for every phone, why there's a persist.img in every Fastboot ROM ?
EDIT: I flashed my old Persists (tried various ones), and the problem.....persists! :') lol
So I'm back to my most recent Persist and still in need for help.
PS: if it helps for a diagnosis, any time the modem resets the SIM it dumps a lot of logs in /ramdump
DoYouWantFriesWithThat said:
I am on Xiaomi.eu 10.2 with Android 9 now, as you suggested. Rooted & with Magisk.
I have backups of my old PERSIST from the China 9.x ROM. Should I flash that (or do I risk bricking) ?
I was reading on persist.img and I don't understand one thing: if it's different for every phone, why there's a persist.img in every Fastboot ROM ?
EDIT: I flashed my old Persists (tried various ones), and the problem.....persists! :') lol
So I'm back to my most recent Persist and still in need for help.
PS: if it helps for a diagnosis, any time the modem resets the SIM it dumps a lot of logs in /ramdump
Click to expand...
Click to collapse
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
eliaztheone said:
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
Click to expand...
Click to collapse
I tried it following this guide to restore the Persist partition (https://forum.xda-developers.com/xi...guide-restoring-persist-partition-to-t3906424 - via Fastboot, not EDL) , and right after flashing the SIM was working fine on 4G/LTE and the phone didn't present any problems.
Then I opened up Google-Maps and gave it permission to read the GPS and it went crazy: not reading the SIM anymore, rebooting, etc. And turning GPS off now won't help. So I guess the problem is with the Modem and the fact that it connects to only 1 Cell - no idea why.
@eliaztheone
eliaztheone said:
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
Click to expand...
Click to collapse
I am on 10.2.1.0 - Android 8.1 now. In addition to what you suggested I restored the persist.img via Fastboot (not EDL) following this guide on XDA .
Right after flashing the phone didn't present any problems (SIM/4G was working without hiccups). As I opened up Google-Maps and gave it permission to read the GPS it went crazy: not reading the SIM anymore, rebooting, etc. Turning GPS off now won't help, it constantly reboots - I have to use Airplane Mode.
So I guess the problem is still in the Modem. Maybe it's the fact that it connects to only 1 Cell, apparently.
@eliaztheone if you can provide the files I'll try one last time. Thank you.
I will upload them tonight hopefully. You need to be on 10.2.1.0 oreo xiaomi.eu version.
You also need to be rooted with magisk so you can restore them with partition backup and restore
---------- Post added at 07:33 PM ---------- Previous post was at 07:28 PM ----------
Did you try to flash modem_fix_ysl.zip? It resets the modem.img and modemst1.img and modemst2.img
Take your time, thank you.
While inspecting the ramdump I noticed the following:
[ 21.864464] [c:1] [p:<003975, android.vending>] Fatal error on the modem.
[ 21.864522] [c:1] [p:<003975, android.vending>] modem subsystem failure reason: rflm_diag_error.cc:361:[email protected]_qlnk.cpp:1090 [9,3] RF stuck in QLINK start s.
[ 21.864530] [c:1] [p:<003975, android.vending>] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.​
There's many SELinux odd log entries too, not sure if that's normal. When I disabled SELinux from the terminal the 4G immediately picked up...totally weird
eliaztheone said:
[/COLOR]Did you try to flash modem_fix_ysl.zip? It resets the modem.img and modemst1.img and modemst2.img
Click to expand...
Click to collapse
I'll try to flash it, thank you.
I am on 10.2.1.0 oreo xiaomi.eu. Do you think it makes sense to try a custom ROM ?
Thank you.
EDIT:
- I flashed modem_fix_ysl.zip but it didn't have any effect.
- I find the ramdumps from the china ROM much cleaner and errorless than the Xiaomi.eu ROM, just saying
I have sent you a pm
Have you guys found a solution? I have the exactly same problem on Mi Max 3 4/64Gb version. I'm on MIUI Global Stable 10.3.5.0. I was on China stable and had issues,so i flashed Global Stable fastboot rom using Mi Flash Tool(flash all option),and It doesn't solve the problem.I have unlocked bootloader,and no previous system backup.
Also i tried flashing NON-HLOS.bin file from Global Stable fastboot ROM using command : fastboot flash modem NON-HLOS.bin
Also i tried something that worked on my old redmi 4,after NON-HLOS.bin flash,executed fastboot commands :
fastboot erase modemst1 and modemst2,but no luck because of "partition is write protected" error.
Have you found what's the cause of this problem?Is it hardware?Is it corrupted modem files?Will custom rom solve it? Please, any help,any suggestion will be appreciated. I'll try everything to fix it. Thank you in advance.
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
DoYouWantFriesWithThat said:
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
Click to expand...
Click to collapse
Thank you man, I'll try everything you said tommorow. The device hardware is awesome,and i really want to support xiaomi,only if they had solution for this problem. Also i think keeping ARB on unlocked bootloader is a bad decision,it really makes this whole process harder.
I'm hoping you get you phone fixed and looking forward to see how this will end.
Thanks for helping me man.
(Sorry for bad English)
---------- Post added at 10:35 PM ---------- Previous post was at 10:33 PM ----------
Maybe someone's QCN file can help us?
DoYouWantFriesWithThat said:
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
Click to expand...
Click to collapse
Maybe someone's QCN file can help us?[/QUOTE]
All authorizations has been locked down for a while now, learned that the hard way during in the early days of ARB4 and i tried to flash a stable rom with a lower ARB number and my phone bricked. IThen i found someone to flash a beta rom by remote with authroization; costed me 15 USD. EDL flash was the only way if you still have fastboot. I worked with the service guy because he also wants to figure out the problem also. After bricking my device 4 times, I got the right recovery to use and then TWRP Recovery worked for the 4GB version. I got the 6GB version also and the people who sold me the phone had already unlocked the bootloader, I had to double check to see using command prompt. The i flashed the Recovery i was given to by a user on the AOSiP thread, thinks its Page 7, its a TWRP CN Recovery.. and it worked in both devices.
@Wmateria can you give me the contact of this person who gave you the remote Auth ?
I just phoned Xiaomi and they told me that Xiaomi's warranty is only valid at national level (read: each european country collects phones sold on its territory, and sends them to specific labs).
Wmateria said:
Maybe someone's QCN file can help us?
Click to expand...
Click to collapse
The QCN won't help cause we can't access EDL anyway even via QFIL.
If anyone has a contact for remote Auth, I'd appreciate if he/she could share it.
Thanks.
DoYouWantFriesWithThat said:
@Wmateria can you give me the contact of this person who gave you the remote Auth ?
I just phoned Xiaomi and they told me that Xiaomi's warranty is only valid at national level (read: each european country collects phones sold on its territory, and sends them to specific labs).
The QCN won't help cause we can't access EDL anyway even via QFIL.
If anyone has a contact for remote Auth, I'd appreciate if he/she could share it.
Thanks.
Click to expand...
Click to collapse
I found some article that shows how to flash QCN file form DIAG mode,and how to enter that mode. I'll try and keep you updated.
Wmateria said:
Maybe someone's QCN file can help us?
Click to expand...
Click to collapse
All authorizations has been locked down for a while now, learned that the hard way during in the early days of ARB4 and i tried to flash a stable rom with a lower ARB number and my phone bricked. IThen i found someone to flash a beta rom by remote with authroization; costed me 15 USD. EDL flash was the only way if you still have fastboot. I worked with the service guy because he also wants to figure out the problem also. After bricking my device 4 times, I got the right recovery to use and then TWRP Recovery worked for the 4GB version. I got the 6GB version also and the people who sold me the phone had already unlocked the bootloader, I had to double check to see using command prompt. The i flashed the Recovery i was given to by a user on the AOSiP thread, thinks its Page 7, its a TWRP CN Recovery.. and it worked in both devices.[/QUOTE]
Did EDL flash solved the problem?
Hi guys,
I f*xked up
Blindly follow the advice from my friend, I flashed the Indo version of MIUI with his guarantee of stable performance. Flashed my persist.img in process. Now my L1 is lost.
How can I recover from this? Please send help Can I just flash persist.img from stock ROM downloaded from Mi? I dont have any backup yet.
Roast me as good as you can, but please, send help
Sadly I don't know how to recover the persist.img L1 Widevine rating without sending your device to a Xiaomi repair centre. I'm pretty sure its unique for every device sold. Sorry to be the bearer of bad news
jamescarter117 said:
Hi guys,
I f*xked up
Blindly follow the advice from my friend, I flashed the Indo version of MIUI with his guarantee of stable performance. Flashed my persist.img in process. Now my L1 is lost.
How can I recover from this? Please send help Can I just flash persist.img from stock ROM downloaded from Mi? I dont have any backup yet.
Roast me as good as you can, but please, send help
Click to expand...
Click to collapse
Honestly if flashing indi made it l3 why would flashing your country firmware not make l1 again? Probably would. It most be safe you already did it once I don't own the device but if your looking for someone who did it also they never come around
Maybe flashing original region's fastboot ROM might help.
I used MiFlash to flash different region's fastboot ROM without losing L1 (I didn't flash persist.img)
Robert314 said:
Sadly I don't know how to recover the persist.img L1 Widevine rating without sending your device to a Xiaomi repair centre. I'm pretty sure its unique for every device sold. Sorry to be the bearer of bad news
Click to expand...
Click to collapse
Techguy777 said:
Honestly if flashing indi made it l3 why would flashing your country firmware not make l1 again? Probably would. It most be safe you already did it once I don't own the device but if your looking for someone who did it also they never come around
Click to expand...
Click to collapse
j4smith said:
Maybe flashing original region's fastboot ROM might help.
I used MiFlash to flash different region's fastboot ROM without losing L1 (I didn't flash persist.img)
Click to expand...
Click to collapse
Hi guys, thanks for commenting.
The good news: all is false alarm. My dumb ass though that Netflix failed because of loosing L1. But it is actually not. Checking by app show L1 is intact. Downloading Netflix from mirror and good to go.
A valueable lesson learnt
jamescarter117 said:
Hi guys, thanks for commenting.
The good news: all is false alarm. My dumb ass though that Netflix failed because of loosing L1. But it is actually not. Checking by app show L1 is intact. Downloading Netflix from mirror and good to go.
A valueable lesson learnt
Click to expand...
Click to collapse
Also on Samsung devices using a permissive kernel gets l1 back for Netflix but if you got it good for you.
I have OnePlus 9 pro t mobile, I was using eu rom normally, when eu network problem gave, I returned to tmo via msm in hopes that the network problem would be solved. but i keep getting this error t mobile team They said that there is no problem, the network can be unlocked, please try again. , please help someone , i checked the imei on the back of the device and the same inside . If anyone has encountered this problem before, can you tell me the solution? Whatever the solution is, I'm ready to do it, I couldn't solve the problem no matter what I did, eu network didn't work, I tried custom rom, but the result is that I can't get the same network and I don't have a t mobile sim card. Please someone help with this. Is there any file that I can remove this lock on the computer? My English is a bit bad, sorry about that. I'm ready to give 50 euros to the person who can solve this problem, please help.
Under settings/about phone/status what do you see?
TheGhost1951 said:
Under settings/about phone/status what do you see?
Click to expand...
Click to collapse
selimo21 said:
View attachment 5814737
Click to expand...
Click to collapse
Have you tried going into settings/system and resetting network settings?
TheGhost1951 said:
Have you tried going into settings/system and resetting network settings?
Click to expand...
Click to collapse
yes i tried and no result
Something happened to the phone, now I'm getting this error, what happened? can someone help?
Search in threads for TMO non-halos.img and flash it in fastboot mode. It flashes the modem and radio for TMO
TheGhost1951 said:
Search in threads for TMO non-halos.img and flash it in fastboot mode. It flashes the modem and radio for TMO
Click to expand...
Click to collapse
I couldn't find the file you mentioned, can you help me? can you link the file
[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
Quick Google search
TheGhost1951 said:
[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
Quick Google search
Click to expand...
Click to collapse
I flashed it and the result is wrong, I still get the error you see above.
selimo21 said:
I flashed it and the result is wrong, I still get the error you see above.
Click to expand...
Click to collapse
Time to MSM to your original model number....
TheGhost1951 said:
Time to MSM to your original model number....
Click to expand...
Click to collapse
i did the result did not change , if i flash custom rom can i fix network eg pixel experience rom ?
How long was it working on Eu rom before it gave you a problem? Maybe you temporarily sim unlocked the phone for 30 days and that ran out?
OnePlus says you must go through tmobile to get it unlocked. Tmobile does need it on their network for a day or so to be able to unlock it. (They tried to do mine manually but there was no data for my phone and there is an exchange that takes place on their server so it has to be online).
Looks like the efs may be somewhat corrupt. Hope you backed up modemst1/modemst2 partitions like the conversion thread suggested you do. You'll want to flash these both back on and then problems should be resolved. You cannot use someone else's partitions, has to be yours.
MSM'ing will not help this situation. Need to unlock permanently using t-mobile's unlock in original ROM after you've restored those partitions. It blows an efuse when it does this, no custom rom can be used as a workaround.
I also had the same problem on OP9. It happened after playing with modemst partition.
joecool1029 said:
Looks like the efs may be somewhat corrupt. Hope you backed up modemst1/modemst2 partitions like the conversion thread suggested you do. You'll want to flash these both back on and then problems should be resolved. You cannot use someone else's partitions, has to be yours.
MSM'ing will not help this situation. Need to unlock permanently using t-mobile's unlock in original ROM after you've restored those partitions. It blows an efuse when it does this, no custom rom can be used as a workaround.
Click to expand...
Click to collapse
Unfortunately I don't have my own modem backups. but someone else has a backup, what can i do? please help me
ElitePotato said:
I also had the same problem on OP9. It happened after playing with modemst partition.
Click to expand...
Click to collapse
did you solve the problem? I have someone else's backup, do I have a chance to use it, please help
I have all the modem related imgs for A12 TMO if needed OP9P
TheGhost1951 said:
I have all the modem related imgs for A12 TMO if needed OP9P
Click to expand...
Click to collapse
Thank you very much for this. Finally, I'm thinking of taking a twrp backup and installing it. I've tried everything with modem backups and the result is unsuccessful I hope someone can fix this problem.
selimo21 said:
Something happened to the phone, now I'm getting this error, what happened? can someone help?
View attachment 5814789
Click to expand...
Click to collapse
Take ur SIM out then restart and connect to a US VPN and try again
L0ND0NB0Y said:
Take ur SIM out then restart and connect to a US VPN and try again
Click to expand...
Click to collapse
unfortunately i tried that too. this problem happened because i deleted modemst1 and modemst2 file in eu rom. I guess the tmo unlock application cannot read the phone's information so the unlock is refusing to bind.
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