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?
Related
Dear Community,
I just searched the past 2 days for a solution but I've not been lucky
Therefore I'd like to ask for help in this forum and hope there is some additional hint or hack I could try...:
So here's the situation:
OnePlus 5T (8/128) with a non booting or not "useful" OS (see last point what I've tried)
No TWRP or CWM
Stock Recovery present
Bootloader Locked
Allow Bootloader to be unlocked = FALSE
What I've already tried yet:
Flashing TWRP --> Not possible Bootloader Locked
Flashing regarding any other kinds like "update" or "flash all" as provided with TOOL_ALL_IN_ONE
ADB Sideload any available ROMS (Original "full" OP5T / FreedomOS / Omni8) --> ADB stops at 47% in Stock Recovery regardless of size of the ZIP file
Tried different versions of ADB (32 & 64 Bit / older & new / also with the LargeAddressAware approach / and on multiple PC's) --> Always same error (47%)
Stumbled upon the possibility to EmergencyDownload a factory flash due to Qualcomm chipset using the MSM-Download-Tool --> Only OnePlus 5 ROM available (no "T")
Mentioned EDL procedure works and OS is booting BUT neither Touchscreen nor USB OTG (for external mouse support) is working --> So I can't navigate and allow Bootloader to be unlocked again
Unfortunately I'm now stuck and have no more idea how to unbrick my phone again
What would help:
Any source to MSM-Download-Tool packed with a correct ROM for the OnePlus 5T
A Workaround to just flash TWRP via MSM-Download-Tool or Qualcomm's QFIL application in EDL mode
Some "hack" to bypass the locked Bootloader situation
Every appreciated Input you might have that I'm currently not aware of...
So PLEASE let me know of any approach that I could try or if you might have found a link or something else to a solution that might help me out of this disaster...
Many thanks in advance!
Tryouts due to your feedback:
@dreinulldrei - "fastboot boot recovery.img" tried with the original 5T Recovery.img also with blu_spark TWRP --> no luck...
SOLVED SOLUTION:
As the EDL factory flash ROM is currently not (or will never officially be) available public getting in contact with the OnePlus support team is required.
They have such a recovery tool (MSM-Download-Tool) with an appropriate ROM and are able to flash the device during a remote support session conducted via chat.
So by starting a chat on the OnePlus Support page and describing your situation will lead to scheduled time slot where a Level-2 technician will do all required steps remotely.
(All files are password protected and the technician ensures they are deleted at the end of the session so I'm unfortunately not able to provide the sources for DIY purposes...)
Following. I would think there would be some way to flash some sort of signed image via fastboot...
U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u
Bradl79 said:
U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u
Click to expand...
Click to collapse
Thanks for your input - I'm really not aware of how to generate such *.ops ROM files as this is what the MSM Tool expects...
But if there is a way and you are able to extract and produce a MSM flashable file I would be very happy to try!
I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.
crakerjac said:
Following. I would think there would be some way to flash some sort of signed image via fastboot...
Click to expand...
Click to collapse
Thanks for the input - I forgot to mention I also tried the 2 original available OP5T "full" ZIP ROM's (think they should be signed...)
Will add this to the initial Post but I assume also no chance here...
dreinulldrei said:
I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.
Click to expand...
Click to collapse
Ohhh good point - I also think there is the "wrong" recovery (from 5) currently on my phone (because also there the touchscreen behaves unexpectedly...)
But unfortunately with your command I get the "Your device is corrupted. It can't be trusted and will not boot" message.
Tried this with the original 5T Recovery.img I managed to obtain and also with the blu_spark TWRP - no luck...
Edit: Ignore, misread previous post.
U may have to make a call to oneplus so they can restore for u
Submit a ticket to One Plus
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
One important this you didn't mention is how this happened.
OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."
blackknightavalon said:
OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."
Click to expand...
Click to collapse
Bradl79 said:
U may have to make a call to oneplus so they can restore for u
Click to expand...
Click to collapse
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again
CodeXter said:
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again
Click to expand...
Click to collapse
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Awwww I wish we could get them, do they use the msmtool too?
How I bricked a 5t
I got the phone and I had installed twrp, that went fine. I was looking at magick systemless rooter when the phone then kicked in with a OTA update, I chose to ignore it the first time. It occurred again a few minutes and in my haste I let it do it's job but it did not complete correctly. I rebooted and the phone complained about corruption to the OS, I got in again but made the dumb mistake of re enabling the OEM lock and because I thought that might be causing the problem. I rebooted again but now I could not boot any more into the OS, it complained I was corrupted and go to google to see what to do.
So I was left with a bricked phone.
I could do bootloader but not recovery and I could not unlock the bootloader.
I could not get in via adb usb debug, So after much research I download the OnePlus 5 unbricking pack and learned a whole lot about qualicom and EDL mode, plus I learned a lot about the QFIL tools and restoring a phone. I did the 5 unbrick but my screen ended up upside down but the touch was right side up, which resulted in a very hard to use phone.
I tried the QFIL method but I was missing a mdb file to be able to talk to the phone.
So I gave up submitted a ticket and after much bad co-ordination on their part got a level 2 tech to debrick the phone remotely.
They do a reverse VPN and connect to your computer, they tell you to have 2 files archive ready in a folder on your desktop (they supply the links). They install the EDL driver and unpack the debrick archive. The archives are password protected, they run the tool and restore the phone
back to factory.
They erase the unpacked archives after they are done.
jerrywmilton said:
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.
Click to expand...
Click to collapse
Oh yes I've learned my lesson on this :angel: --> Never ever set OEM to be unlocked to NO again
Obviously I do not exactly know what wrong procedure made me stuck in this situation but I just wanted to revert every single step back one by one to see which element brings me back to a valid SafetyNet situation...
I've been with the OnePlus "family" since the OP1 but never needed any direct support from the vendor - so every time there's a first time and so for me now...
Thus I really didn't know OP staff is actively doing remote support for their devices - but thumbs up for that! :good:
(BTW: I'm not the guy from the OP forum)
Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
Yes basically it's the same archive as the 5 unbrick pack but it's for 5t, OnePlus 5T OxygenOS 4.7.2-171116.zip is the archive and you can look in it and you see the ops file is for dumpling not cheesburger, which is the code name for 5t. I saw the MsmDownloadTool is 4.0.8
Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
I just had a chat with them before and got mailed a link to the MSMTool incl. ROM for the OP5T (dumpling)
But unfortunatley support files from OnePlus are password protected Nevertheless here the original vendor link:
https://onepluscn-my.sharepoint.com/personal/sheva_liu_oneplus_net/_layouts/15/guestaccess.aspx?docid=0fde9596c72744b4fb9c073ca5d87edbe&authkey=AQPXKRi7pdIzZX-5WH_pwWg&e=1030aa0046da4d1aa9189020027d9c93
So I have to wait for my remote support schedule on Saturday to have the L2 technician entering the password and do the rest.
Would be able to do this myself but OnePlus obviously wants to protect their sources what I have to accept, respect and be patient for...
So, never turn off the OEM Unlocking?
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
I have lost IMEI number after flashing Pie. On my Sprint Moto Z2 Force. Signal bar has turned grey and IMEI is showing as zero.
Wifi is working
Bluetooth is working
Barcodes in bootloader mode is showing some different IMEI no.
Downgrade to Stock Oreo or Naugat
If I downgrade to stock Oreo then I lost all wifi, sim and Bluetooth. Also no baseband found in bootloader.
Will appreciate if someone can help.
Thanks in advance.
If you have already flashed Pie Rom (including bl、 baseband), you will not be able to return to Oreo
Hello.
I am trying to research the imei bricks on Sprint models after Verizon pie update. In short, everything we understand says this should not be happening, and yet it is.
Can you, for research purposes, describe the state of your device when you applied the update? Was it running full verizon firmware down to the bl, modem, and gpt? I may have an experimental fix but I need to gather more info about the bricks.
Also, it is impetative that you don't flash any further modems for my fix to have a good chance to work. Thanks.
Thanks for the message,
The device working fine, very super smooth and I can feel the difference.
The only think which is not working is cell phone and it's because of 0 IMEI number, currently I am on pie retail version (NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml) downloaded from mirrors lolinet com / firmware / Moto / Nash / retail
Pls let me know if you want more info.
Thanks in advance.
hqureshi said:
Thanks for the message,
The device working fine, very super smooth and I can feel the difference.
The only think which is not working is cell phone and it's because of 0 IMEI number, currently I am on pie retail version (NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml) downloaded from mirrors lolinet com / firmware / Moto / Nash / retail
Pls let me know if you want more info.
Thanks in advance.
Click to expand...
Click to collapse
What firmware did you flash from? Stock? Do you have an unlocked bootloader?
If yes to all the above, I can give you some experimental things to try.
Yes to all and bootloader is unlocked.
btw i have flashed firmware in this order
1. i flashed NASH_PPX29.159_19_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
then
2. XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and now on
3. NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml
That's not ideal (the additional flashes) but what I have is still worth a try and you have nothing to lose.
The first thing we need is to boot twrp on the device using fastboot (get the latest .img here and fastboot boot twrp.img it). Once in twrp, immediately reboot to "EDL."
https://dl.twrp.me/nash/
Get drivers for qualcomm 9008 mode device if needed (should show in Windows device manager under "ports"):
https://androidfilehost.com/?fid=11410963190603862036
Then get the nougat blankflash here:
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/blankflash_from_NDX26.183-15_17.zip
Extract and run the cmd inside. You may need to try a few times, on different usb ports. I heard usb 2.0 works best.
If it succeeeds, try flashing your stock firmware and see if imei is back.
Good luck. This is a real stretch but it just might work...
PS: This does have potential to completely brick your device. Please keep that in mind and weigh your options.
I have tried as per instruction but still getting the "baseband not found" status on all stock oreo & nougat firmwares. So when I flash Pie retail I get wifi and Bluetooth back with 0 IMEI status. so the situation is the same.
BTW I have read somewhere the 0 IMEI issue is related persist file/folder/. I may be able to share reference link of that discussion in a while. (Link of discussion)
Let me know if you want me to test anything else. Thanks again for your time. best
hqureshi said:
I have tried as per instruction but still getting the "baseband not found" status on all stock oreo & nougat firmwares. So when I flash Pie retail I get wifi and Bluetooth back with 0 IMEI status. so the situation is the same.
BTW I have read somewhere the 0 IMEI issue is related persist file/folder/. I may be able to share reference link of that discussion in a while. (Link of discussion)
Let me know if you want me to test anything else. Thanks again for your time. best
Click to expand...
Click to collapse
That's really odd. Sorry, I have nothing right now for you but will look into this as best I can.
Thanks, btw whenever i flash stock nougat i am getting verification failed error during flashing of bootloader.img
EDL
R-T-B said:
That's not ideal (the additional flashes) but what I have is still worth a try and you have nothing to lose.
The first thing we need is to boot twrp on the device using fastboot (get the latest .img here and fastboot boot twrp.img it). Once in twrp, immediately reboot to "EDL."
https://dl.twrp.me/nash/
Get drivers for qualcomm 9008 mode device if needed (should show in Windows device manager under "ports"):
https://androidfilehost.com/?fid=11410963190603862036
Then get the nougat blankflash here:
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/blankflash_from_NDX26.183-15_17.zip
Extract and run the cmd inside. You may need to try a few times, on different usb ports. I heard usb 2.0 works best.
If it succeeeds, try flashing your stock firmware and see if imei is back.
Good luck. This is a real stretch but it just might work...
PS: This does have potential to completely brick your device. Please keep that in mind and weigh your options.
Click to expand...
Click to collapse
I can see the qualcomm device in twrp on my device manager. how to i get to edl mode. there is no reboot edl option in twrp. do i command fastboot reboot edl when device in twrp screen? when i run the qboot blank-flash it says wating for device
Please use latest TWRP from here https://dl.twrp.me/nash/ load it using fastboot and the in TWRP click reboot and select EDL.
Let me know if you face any issue.
i'm on the same boat
no celluler, no IMEI
wifi and bluetooth working
Everyone keeps trying to flash pie firmware that isn't for their variant and this is the result, no baseband. Plus once you upgrade to a pie modem, you can't go back to an oreo modem. Maybe something will come along and remedy that, that's a big maybe too. The devs are trying to find a solution, but there just might not be one. You can't blankflash your way out of it, and if you're not careful you can brick your phone for real. Not 9008 brick, paperweight. Not trying to be an ass, just trying to warn others. If it isn't pie for your phone, don't flash it.
Blankflash doesn't work anyways.
Stand by we are working on another fix.
R-T-B said:
Blankflash doesn't work anyways.
Stand by we are working on another fix.
Click to expand...
Click to collapse
Let me know if you need this fastboot_nash_verizon_oem_vzw_user_9_PCX29.159-21_10d9a_release-keys-cid2_vzw.tar.gz. I have got it from @oslov a member of discord.
I have tried this in this sequence but still zero IMEI.
1. Nougat Blank flash
2. Flashed Stock Verizon Oreo and then staying in bootloader mode I flashed above Pie Update using Flash-All batch file.
Phone successfully booted with Verizon sim activation warning but IMEI was 0.
I thought I should update you guys.
Thanks
Oslov is my discord nick.
Confusing I know, lol.
Be careful with that file, we don't fully understand it yet. I gave it to you because, how much worse off can you be really?
R-T-B said:
Oslov is my discord nick.
Confusing I know, lol.
Be careful with that file, we don't fully understand it yet. I gave it to you because, how much worse off can you be really?
Click to expand...
Click to collapse
Lol. Wow!
Thanks again for doing this. Best
un1ocked said:
i'm on the same boat
no celluler, no IMEI
wifi and bluetooth working
Click to expand...
Click to collapse
Have restored IMEI # with the help of @oslov, We will share the solution in a while.
hqureshi said:
I have lost IMEI number after flashing Pie. On my Sprint Moto Z2 Force. Signal bar has turned grey and IMEI is showing as zero.
Wifi is working
Bluetooth is working
Barcodes in bootloader mode is showing some different IMEI no.
Downgrade to Stock Oreo or Naugat
If I downgrade to stock Oreo then I lost all wifi, sim and Bluetooth. Also no baseband found in bootloader.
Will appreciate if someone can help.
Thanks in advance.
Click to expand...
Click to collapse
I have resolved the 0 IMEI issue with the help of R-T-B, by doing undo Sim/network Unlock. changing CHMOD of id_00 to 0770
so now I am facing sim/network locked,
So whenever i unlock the sim/network lock i get 0 IMEI issue.
I will appreciate if someone now can help me to unlock SIM/network lock while keeping IMEI
I am currently on Retail pie with Sim/Network Locked. Phone Model is Sprint XT1789-03, dual sim enabled
IMPORTANT NOTE TO USERS UPGRADING TO AN ANDROID 10 ROM:
Please BACKUP YOUR PERSIST PARTITION IN RECOVERY BEFORE FLASHING AN ANDROID 10 ROM, otherwise your device may be messed up seriously. Please read this post before upgrading to A10.
Update on this issue:
https://forum.xda-developers.com/ma...n-fixing-persist-issues-t4024247/post81656725
Apparently, due to the changes made by Google, some hacks needed to be done to make Q work with our device. Due to this, when installing an Android 10 ROM and other things like Magisk on it, some modifications are made to the persist partition. These changes might break some important stuff like Camera, Wifi, Torch etc for users who go back to Pie ROMs. Even when switching between TEN Roms, similar problems have come to some users.
*******************************************
****** WAYS TO BACKUP PERSIST ******
*******************************************
1) Using persist backup option in recovery
-> This option is present in recent versions of TWRP and other TWRP based recoveries. Its a good practice to always backup all the important partitions like Persist, EFS and Modem. These contain the most important stuff like IMEI, Wifi Mac address etc. which are unique to your device.
2) Making an Image backup of persist via recovery terminal
-> If the persist backup option isn't available, you can use the dd command from a terminal app (needs root rights) or from the recovery terminal.
Usage:
To create a backup and place it at /sdcard/persist.img:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
To restore a backup which is placed at /sdcard/persist.img:
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
Thanks to @NZedPred, due to which I came across these commands. These appear to work universally and work on our device as well. Please be careful while typing the commands, especially while restoring the persist.img. Even a small mistake could be fatal for the device.
*************************************
********* FIXING PERSIST *********
*************************************
There is no guaranteed way to fix your broken ORIGINAL persist, but currently the only way to fix the broken stuff on your device is using someone else's persist. We need to obtain a twrp backup of the persist or persist.img from some other user who has not upgraded to Android 10.
Before fixing your persist, make a BACKUP of your ORIGINAL PERSIST even if it is broken. It contains important stuff UNIQUE to your device. It might be very helpful, in case someone discovers a fix to it in the future.
Please BEWARE, there are RISKS associated with using someone else's persist. Historically in other devices, it has been used to store IMEI and other important things.
But the following things are CONFIRMED TO BREAK if using someone else's persist.
1) WIDEVINE WILL BE PERMANENTLY STUCK AT L3, since the drm certificates unique to your device will be lost forever.
2) Persist stores your serial number as well, so your ORIGINAL SERIAL number may get lost when switching to stock.
***************************************
****** FIXING SERIAL NUMBER ******
***************************************
Fortunately there is a way to fix your serial number. In the root of your persist, there is a hidden file ".sn.bin". Opening it in a text editor, we can see the last 15 digits of the serial number of the other person's device, whose persist you have used. Copy and keep this number somewhere. Then follow below steps:
1) Backup the current persist.img using the above dd commands.
2) Open the persist.img using a hex editor. You can use any hex editor software for windows/linux or Hex Editor app from Play Store.
3) In the search option, set it to find strings. Set it to 'String' or something similar depending on your software.
4) Search for the 15 digit serial number which you found previously in .sn.bin file.
5) After you find it, replace or edit it to your original serial number. Make sure that you modify ONLY THOSE 15 DIGITS AND NOTHING ELSE.
6) Then save the modified persist.img
7) Restore the modified persist.img using dd commands as above.
8) Almost done, but the new changes in persist won't be detected by the system. So you will have to install the stock pie ROM. Relocking the bootloader is not required as per my testing. So follow the steps to install stock. Use OFRP and decrypt.zip as necessary, to deal with encryption.
9) Now boot up the device.
And voila. Go to settings and check your serial. It should be restored. You can now return to your custom ROM if you want. The serial number will be retained.
Same thing happened with my device too. Widevine security level is stuck at L3.
Although I'm back in the Official Stock ROM!
(locked bootloader)
Apolle said:
Same thing happened with my device too. Widevine security level is stuck at L3.
Although I'm back in the Official Stock ROM!
(locked bootloader)
Click to expand...
Click to collapse
Yes... Even after flashing stock firmware, widevine remains L3.
Some people have suggested me to install the last stock Oreo first and then install Stock Pie.
Maybe the Oreo firmware contains the original persist files...
The Oreo firmwares were around 1.6 to 1.8 GB, whereas the pie firmwares are around 1.5 GB.
So maybe they are right then...
Maybe if its possible for some of you to do this, you could try this...
I also messed up my persist partition. even i'm getting back to all stock (including recovery and locked bootloader) my phone can't recieve update, neither install updates manually. Also, my device is shown in playstore setting as "Device not certified". I'm still searching for a fix for this.
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
Tyakrish said:
Yes... Even after flashing stock firmware, widevine remains L3.
Some people have suggested me to install the last stock Oreo first and then install Stock Pie.
Maybe the Oreo firmware contains the original persist files...
The Oreo firmwares were around 1.6 to 1.8 GB, whereas the pie firmwares are around 1.5 GB.
So maybe they are right then...
Maybe if its possible for some of you to do this, you could try this...
Click to expand...
Click to collapse
I also tried to install Oreo but, I can't update it to android Pie. It always failed.
kayamokid said:
I also tried to install Oreo but, I can't update it to android Pie. It always failed.
Click to expand...
Click to collapse
Could you tell which Oreo firmware ? If its very first Oreo firmware released by Asus, then you might need to update to the last available Oreo firmware and then upgrade to pie...
The last Oreo firmware I believe, prepares the device for pie...
So Pie might get installed after that
Tyakrish said:
Could you tell which Oreo firmware ? If its very first Oreo firmware released by Asus, then you might need to update to the last available Oreo firmware and then upgrade to pie...
The last Oreo firmware I believe, prepares the device for pie...
So Pie might get installed after that
Click to expand...
Click to collapse
If you haven't tried yet, try the persist.img from here & let us know if fix the problem.
Tyakrish said:
Could you tell which Oreo firmware ? If its very first Oreo firmware released by Asus, then you might need to update to the last available Oreo firmware and then upgrade to pie...
The last Oreo firmware I believe, prepares the device for pie...
So Pie might get installed after that
Click to expand...
Click to collapse
Oh, not the first one. i used .192 but no success... i hope there's a fix for this.. i miss stock rom so much...
mauam said:
If you haven't tried yet, try the persist.img from here & let us know if fix the problem.
Click to expand...
Click to collapse
I looked at this persist.img. But it appears weird to me. Just have a look at the contents of my persist image and this one.
Seems like a lot of stuff is missing...
Tyakrish said:
I looked at this persist.img. But it appears weird to me. Just have a look at the contents of my persist image and this one.
Seems like a lot of stuff is missing...
Is this supposed to be in a different format ? How can this be flashed ?
Click to expand...
Click to collapse
Let's see if @Wahyu6070 can enlighten us. His nick is wahyu hidayat on telegram if you want to reach him.
@kubersharma, I have spoken to many people about this issue and no one seems to know much about why it happens and how this issue can be fixed.
Can you give an insight as to why this persist problem happens ?
To save time, I linked to first post of this thread:
https://forum.xda-developers.com/ma...n-fixing-persist-issues-t4024247/post81288631
After much research, I have come to the conclusion that widevine can't be fixed. Since the drm certificates unique to our device are forever lost when some other user's persist is used. The other user's persist may contain some widevine files, but they are unique to his device and won't work with our device.
Completely Agreed with you because what I did confirm that it cannot be fixed.
I flashed Oreo Firmware Raw (Initial Oreo Firmware 158) by Fastboot/adb method. Then Install every single incremental Update by built-in Updater. But unfortunately the Widevine security level remains L3.
Apolle said:
Completely Agreed with you because what I did confirm that it cannot be fixed.
I flashed Oreo Firmware Raw (Initial Oreo Firmware 158) by Fastboot/adb method. Then Install every single incremental Update by built-in Updater. But unfortunately the Widevine security level remains L3.
Click to expand...
Click to collapse
Thanks for all that effort. I also tried with a fastboot firmware posted on 4pda. But no use.
Tyakrish said:
@kubersharma, I have spoken to many people about this issue and no one seems to know much about why it happens and how this issue can be fixed.
Can you give an insight as to why this persist problem happens ?
To save time, I linked to first post of this thread:
https://forum.xda-developers.com/ma...n-fixing-persist-issues-t4024247/post81288631
Click to expand...
Click to collapse
Try pm @wahyu6071 telegram
UPDATES:
- Added a way to make persist image backups (Can be useful for flashing persist.img files).
Check the first post
Apolle said:
Same thing happened with my device too. Widevine security level is stuck at L3.
Although I'm back in the Official Stock ROM!
(locked bootloader)
Click to expand...
Click to collapse
have you used other user's persist? are you able to install OTA after you made this process? i also use other's persist. and my imei is lost. and also, i cant update thru FOTA and manual method. it gives me an error in stock recovery.
kayamokid said:
i also use other's persist. and my imei is lost.
Click to expand...
Click to collapse
Wait a min. Did you lose your imei also ? I thought u only lost widevine L1 ?
Tyakrish said:
Wait a min. Did you lose your imei also ? I thought u only lost widevine L1 ?
Click to expand...
Click to collapse
yes. but i manage to restore it again, by editing .sn,bin file inside of persist folder. terrible happens when this persist problem occurs. i cant install or update stock rom manually. i hope there's a way to fix this. I miss clean, locked and unrooted stock rom.
kayamokid said:
yes. but i manage to restore it again, by editing .sn,bin file inside of persist folder. terrible happens when this persist problem occurs. i cant install or update stock rom manually. i hope there's a way to fix this. I miss clean, locked and unrooted stock rom.
Click to expand...
Click to collapse
You must be talking about Serial number. The file, .sn.bin contains the serial number. I don't think imei is lost if we use someone else's persist. I didn't lose mine and I came across many other people, they also didn't lose imei.
Based on what you are saying, I think serial number gets lost as well along with widevine...
Because even I lost my serial number after installing stock pie via fastboot
Deleted
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