I was trying to unlock the sim-lock on my OnePlus 9 T-Mobile and somewhere read that it can be done by deleting modemst1, modemst2, and persist partitions. So, I deleted them, but it didn't work. Instead, the WI-FI also stopped working.
After trying different MSM Download Tools for weeks, somehow modemst1 and modemst2 partitions were restored, but still cannot restore the persist partition. Without persist partition sensors are not working. For example, it does not auto-rotate, brightness auto-adjustment does not work, etc.
Can anyone help me with this?
Thank you!
c0d3f0rc37 said:
I was trying to unlock the sim-lock on my OnePlus 9 T-Mobile and somewhere read that it can be done by deleting memst1, memst2, and persist partitions. So, I deleted them, but it didn't work. Instead, the WI-FI also stopped working.
After trying different MSM Download Tools for weeks, somehow memst1 and memst2 partitions were restored, but still cannot restore the persist partition. Without persist partition sensors are not working. For example, it does not auto-rotate, brightness auto-adjustment does not work, etc.
Can anyone help me with this?
Thank you!
Click to expand...
Click to collapse
So in essence you broke your device. You probably have lost fp scanner,wifi,nfc,rotation. I really don't know what to tell you other than msm your device back to stock. And you didn't back up persist . This partition is device specific. If you do get it fixed properly I'd leave it the hell alone.
You can't just delete critical partitions
So, there's no way to fix this? I can assume that the phone is wasted?
c0d3f0rc37 said:
So, there's no way to fix this? I can assume that the phone is wasted?
Click to expand...
Click to collapse
Try and contact OnePlus and get a remote session. One of their techs will get you on correct MSM and get phone fixed.
c0d3f0rc37 said:
So, there's no way to fix this? I can assume that the phone is wasted?
Click to expand...
Click to collapse
The persist partiton can only be fix by oneplus in factory or spending money for someone that has the hardware required to fix it.
Related
UPDATE: So hopefully this title and OP update take as I don't want to spam the forum with threads. Despite have dozens of Android phones since the original G1 I am stumped by this, but I imagine a guru could solve this puzzle. Here we go:
I messed up my phone partition table when I messed up the last step from the dual boot TWRP thread. I tried fixing my newly bricked phone using MSM tools but it's a converted GM1915 Tmobile OP7P running global firmware. The Tmobile stock MSM recovery pack MEGA link has gone dead, so I tried the Tmo to Int'l conversion files again. The phone booted, but I kept getting "NV Backup warning - dynamiic partition is invalid". I could make calls, but had no orientation sensor, no mobile data, baseband shows blank in fastboot mode, etc. I've tried flashing fastboot ROMs as well but no matter what, the dynamic partition invalid message pops up.
It seems ike this is an EFS issue, so late last night I tried a few more things. IIRC, I was able to flash that persist.img via "fastboot flash persist persist.img", and in any case most everything seems to work now, including the sensors. But, I'm still getting that dynamic partition invalid error and no baseband shows on my bootloader screen. I
'm guessing there's still some corruption in EFS? I'd understood from reading that even with persist.img one good thing was to erase the modem files and persist first, because then they will regenerate, according to this post.
So, I tried these commands with plans to then flash persist.img again....
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
It won't let me erase them though, as it says the critical partitions are locked. Do you think this path might fix whatever issue is triggering this message, and if so, does anyone know how to do it? I think I may have use dd, but I'm not sure which partitions I'll be looking to erase and how to do it that way, either.
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
¿GotJazz? said:
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thanks, but that's what I've been trying. No joy so far. I need to check because actually it may have hung on params or some other issue that an L2 driver update could fix. Of course me figuring out how to fix that will be the next feat, LOL.
Updated thread title and OP with new info. Phone almost back to 100%, but still getting an error message.
So another update as I learn. Now that I've gotten TWRP and Magisk back on it, I realized there is another odd thing with the phone now. Just before the bootloader unlocked warning screen, for a fraction of a second there's a message that says SMT Download Failed. More reading seems to suggest that using an SMT recovery in conjunction with MSM tool can fix the SMT Download Failed message. Most of these say you need to have an EFS backup, which some suggest that you can wipe EFS (as indicated in OP) and it will regenerate.
I've taken a TWRP backup of EFS, but I'm not sure whether I should proceed with the wipe processes with so many saying you should have an EFS backup (lesson learned, yes you should - and don't delete/misplace it like I did). Anyway, I'm wondering if going through that process might resolve that, as it could be a flag that didn't get set right, or whether or not there's some issue with my EFS that means my backup from the current state is worthless.
Maybe my EFS isn't corrupt after all, maybe it was the persist.img that needed to fix the sensores and now I'm good except for some flag that's triggering the SMT Download Failed message and the subesquent dynamic partition invalid message?
Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work
yulian6766 said:
Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work
Click to expand...
Click to collapse
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.
vettejock99 said:
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.
Click to expand...
Click to collapse
Your problem is recover your IMEI?
yulian6766 said:
Your problem is recover your IMEI?
Click to expand...
Click to collapse
The phone shows IMEI right now, and calls and mobile data work, so except for the weird " SMT download failed!!! please check your download flow is right" message at boot start and the NV Backup UI warning Dynamic partiton invalid messages the phone otherwise seems just fine. I'm pretty comfortable with system, boot, and data partition stuff from all my time at this, but I'm just being extra cautious that by erasing my modems via some sort of commands or SMT flash that I can at least get it back to where it is now even if I can't get back to an error-free state.
Have you tried flashing QCN file?
yulian6766 said:
Have you tried flashing QCN file?
Click to expand...
Click to collapse
I had heard about and used QPST before, but QCN is new to me. I did a quick search and it sounds like on some phones like ASUS ROG, you REALLY need to have one to recover from erasing your modems. Oneplus phones recreate those if they are erased, don't they?
Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.
Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.
Velrix said:
Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.
Click to expand...
Click to collapse
Good stuff. I'll definitely post a resolution here if I get it all. Just glad to have the phone working again for sure!
yulian6766 said:
Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.
Click to expand...
Click to collapse
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.
I did go ahead and try a SMT flash. Unfortunately, while I've gotten it to start, it ultimately gets to "Param preload" then I see the Status of Connection change to N/A and then it just hangs....grrrr...
vettejock99 said:
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.
Click to expand...
Click to collapse
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me
yulian6766 said:
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me
Click to expand...
Click to collapse
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?
vettejock99 said:
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?
Click to expand...
Click to collapse
I choose the same option
yulian6766 said:
I choose the same option
Click to expand...
Click to collapse
So if we're both choosing WWAN-DHCP for the driver mode, I'm not sure why it wouldn't work. Right now everything is working and I told the NV Backup UI notification to Never Show so it will probably be a few days before I get around to trying to get the whole thing to flash properly. My OCD is really the only thing that would drive me to do it
I think I messed up my phone, after do the "dd zero" command to the modemst1 modemst2 and fsg partitions the mobile signal dont work, but I made a QCN backup before do that, because I think that solve if anything goes wrong, so I did it. After that a tried to restore QCN backup but the still dont work.
My fault was not to make a backup of the partitions using dd command, I also try to resolve this using MSM tool but dont, so anybody has a solution to this?
Thanks in advanced.
yulian6766 said:
I think I messed up my phone, after do the "dd zero" command to the modemst1 modemst2 and fsg partitions the mobile signal dont work, but I made a QCN backup before do that, because I think that solve if anything goes wrong, so I did it. After that a tried to restore QCN backup but the still dont work.
My fault was not to make a backup of the partitions using dd command, I also try to resolve this using MSM tool but dont, so anybody has a solution to this?
Thanks in advanced.
Click to expand...
Click to collapse
You mean you did
dd if=/dev/zero of=/dev/block/bootdevice/whatever
To your imei partitions?
I'm sorry but if you did that you need to contact oneplus and get a motherboard replacement. No one can help you
If you're feeling experimental you can try putting the phone into diag mode and restore imei however it is way difficult to do so than it sounds and you might cause even more damage
If you want to go the diag way google is your friend however some features like widevine, WiFi, Bluetooth might not work unless you can get a mac address for those
anupritaisno1 said:
You mean you did
dd if=/dev/zero of=/dev/block/bootdevice/whatever
To your imei partitions?
I'm sorry but if you did that you need to contact oneplus and get a motherboard replacement. No one can help you
If you're feeling experimental you can try putting the phone into diag mode and restore imei however it is way difficult to do so than it sounds and you might cause even more damage
If you want to go the diag way google is your friend however some features like widevine, WiFi, Bluetooth might not work unless you can get a mac address for those
Click to expand...
Click to collapse
Thanks for your answer, but the imeis are still there, I dont get any invalid imei error or null error.
yulian6766 said:
Thanks for your answer, but the imeis are still there, I dont get any invalid imei error or null error.
Click to expand...
Click to collapse
Maybe is dumb question but do you try fuul install off os firmware?
Sent from my GM1910 using Tapatalk
Geto-Fraer said:
Maybe is dumb question but do you try fuul install off os firmware?
Sent from my GM1910 using Tapatalk
Click to expand...
Click to collapse
I use MSM Tool, various upgrade packages and dont work, that methods dont touch EFS partitions
Someone could help me with a .img backup of this partitions? modemst1 modemst2 and fsg.
Hi good people at XDA. This is my first post on this website and I am absolutely hoping to receive help from you all to find a way out of the depressing and extremely anxious situation I'm in.
I was using my OP6 normally today and while I was typing something on Telegram the phone suddenly froze and after I re-booted it, it took me to the Qualcomm Crashdump screen.
My OP6 isn't tampered in any way (no bootloader unlocked, no TWRP recovery installed, nothing rooted).
At the moment, I can enter the fastboot mode while pressing volume up and power button.
The crucial thing is the data which I MUST RETRIEVE, can't afford to lose it.
Could y'all please suggest a way where the data can be retrieved or the phone can be revived without data loss?
I did read the forums on MSMDownload Tool but I believe it wipes off the phone, right?
PLEASE HELP!
If ADB ( read: USB Debugging ) got enabled on phone - what is the door to Android OS - then try this to pull out user-data stored on phone
Code:
adb devices
mkdir "C:\RECOVERED_DATA"
adb pull /sdcard C:\RECOVERED_DATA
jwoegerbauer said:
If ADB ( read: USB Debugging ) got enabled on phone - what is the door to Android OS - then try this to pull out user-data stored on phone
Code:
adb devices
mkdir "C:\RECOVERED_DATA"
adb pull /sdcard C:\RECOVERED_DATA
Click to expand...
Click to collapse
Thanks @jwoegerbauer for the prompt response. I can surely try that. Considering that I'm fairly a noob, could you please share in a bit detail, the steps I need to take before executing those commands?
Also, since there's a tiny chance that USB Debugging may not have been enabled, what's the alternative that I consider?
Thanks!
Since I must retrieve the data in internal SD, can this help me enter the OS?:
1. Extracting the boot.img of the latest version that's currency installed on my OP6, from payload.bin
2. Testing if this boot.img can revive me into the OS by fastboot boot boot.img.
Also, one pressing doubt: does a fastboot flash boot boot.img command erase internal SD contents??
Please help!
Any help, anyone?
pagan_1 said:
Any help, anyone?
Click to expand...
Click to collapse
My friend has the same problems. Did you find any ways to retrive data? I found a way to use msm tool but it surely erases all data and its his college memories so I'm trying to find alternate ways. Does the msm tool work on bootloader locked phones?Sorry that I am of no help to you. I too am a novice
KannanSathyanarayanan said:
My friend has the same problems. Did you find any ways to retrive data? I found a way to use msm tool but it surely erases all data and its his college memories so I'm trying to find alternate ways. Does the msm tool work on bootloader locked phones?Sorry that I am of no help to you. I too am a novice
Click to expand...
Click to collapse
No man. Still looking for some solutions. Read umpteen threads only to see that MSMDownload Tool erases data because it first unlocks bootloader (which mandatorily wipes data), flashes system files and then relocks it.
But I'm pretty sure, there exists some way out to flash a OP 6 with locked bootloader but retaining userdata partition intact.
Hoping to receive some solution here from this community of Android geeks.
pagan_1 said:
No man. Still looking for some solutions. Read umpteen threads only to see that MSMDownload Tool erases data because it first unlocks bootloader (which mandatorily wipes data), flashes system files and then relocks it.
But I'm pretty sure, there exists some way out to flash a OP 6 with locked bootloader but retaining userdata partition intact.
Hoping to receive some solution here from this community of Android geeks.
Click to expand...
Click to collapse
Hey man, were you able to do anything abut it? I'm in the exact same situation. Don't mind losing the phone if I'm able to save the data.
Smohi said:
Hey man, were you able to do anything abut it? I'm in the exact same situation. Don't mind losing the phone if I'm able to save the data.
Click to expand...
Click to collapse
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
pagan_1 said:
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
Click to expand...
Click to collapse
Oh, that's awesome. I have some hope then. Do you mind telling me what your location is. I'm based out of bangalore and wondering I'll have to take it to your specialist incase I don't find any solution locally. All others have been saying they were asked to replace motherboard by Oneplus service centres. Please let me know of your repair centre as well. I'll try to atleast speak to them. Thank you so much
pagan_1 said:
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
Click to expand...
Click to collapse
How much did it cost? They changed IC and since then your phone is working properly?
pagan_1 said:
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
Click to expand...
Click to collapse
Bro can i have your number please i m stuck with the same problem since last year but not got the solution to boot up my phone normally its always showing crash dump mode. I tried everything but nothing worked for me.
like many even i too ugraged my op6 to oo11.1.1.1, rooted was running well for a week till i encountred face crash dump mode error
Stupid thing i did was instead of flashing fastboot oos 10.3.8 i tried to flash msm 10.3.8 which didnt solve crash dum and also locked my BL.
now nonof the msm could solve crash dump nor we can unlock BL bz we cant toggle OEM in Dev option,
i discussed with @L0ND0NB0Y regarding this, his suggestion would be to take a backup of oos10.3.8 config partation of a working rom, then use edl to flash it on affected op6, by that way we can unlock bootloader and flash fastboot rom.
we need to fide a working op6 and back config which @L0ND0NB0Y can guide us. if it works he ll creat a post to solve crashbump and BL locked issue.
if this wont work, we may need to wait for msm oos11 file.
update : managed to solve crash dump by flashing msm international 5.1.5 but ended up getting black screen with white notification light, if my op6 had BL unlocked all i had to do is to boot stock/twrp recovery and factory wipe.
1.I have a rog phone 5 covert to tecentgame. When I move to version WW but then there is a fingerprint error (losing the system fingerprint authentication). Who can help me?
2.There is an opinion that restoring the system partition can fix the above situation, do not know if it is true or false?can anyone guide me on how to do the above?
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
It's a known issue. As of yet, it appears this is a drawback to the conversion.
I'm currently working on a solution to get fingerprint working after a conversion. I've located the error and a Magisk module should be able to fix it. I can't make any promises until that theory is fully tested, though.
Of course my Magisk install is broken and won't install from storage...
I need the system/vendor/etc/vendor_(something)_styles.xml
Started a thread for it, since those with a working reader are unlikely to be looking through this thread.
losing fingerprint sensor happend always or its random issue?
yaser86100 said:
losing fingerprint sensor happend always or its random issue?
Click to expand...
Click to collapse
It's basically part of the conversion until that is perfected.
twistedumbrella said:
It's basically part of the conversion until that is perfected.
Click to expand...
Click to collapse
maybe one day thats be perfect ?
yaser86100 said:
maybe one day thats be perfect ?
Click to expand...
Click to collapse
Probably. They got there on the 3, from what I've seen.
..................
twistedumbrella said:
It's basically part of the conversion until that is perfected.
Click to expand...
Click to collapse
Unlocking BL and converting WW, there is a chance of losing your fingerprints, but back up the persist partition before conversion, you don’t have to worry about losing your fingerprints. Once you lose your fingerprints, you only need to restore the persist partition and your fingerprints will be normal. But it can only correspond to this phone, and restore on other phones is not possible.
yaser86100 said:
losing fingerprint sensor happend always or its random issue?
Click to expand...
Click to collapse
The quote below was meant for you. No idea why I was tagged instead.
johnny886 said:
Unlocking BL and converting WW, there is a chance of losing your fingerprints, but back up the persist partition before conversion, you don’t have to worry about losing your fingerprints. Once you lose your fingerprints, you only need to restore the persist partition and your fingerprints will be normal. But it can only correspond to this phone, and restore on other phones is not possible.
Click to expand...
Click to collapse
twistedumbrella said:
I need the system/vendor/etc/vendor_(something)_styles.xml
Started a thread for it, since those with a working reader are unlikely to be looking through this thread.
Click to expand...
Click to collapse
what shoul i change?
i rooted my rog phone 5
i dont know what to do to being back my fingerprint
i havent backuped
shayantt98 said:
what shoul i change?
i rooted my rog phone 5
i dont know what to do to being back my fingerprint
i havent backuped
Click to expand...
Click to collapse
Follow one of the newer threads. The info here is extremely outdated.
I've corrupted my persist partition while attempting to upgrade from Android 11 to Android 12. I had a backup, but it doesn't appear to be working.
As far as I know, but correct me if I am wrong, this partition is identical in every Pixel 4XL.
Would anybody be willing to share theirs so I can fix my phone?
Oh, I have a similar problem with an S5:
https://forum.xda-developers.com/t/sm-g903f-wifi-and-bluetooth-broken.4380225/
dogeen said:
this partition is identical in every Pixel 4XL
Click to expand...
Click to collapse
Now that you mention it... Thanks for this hint btw but shouldn't the persistent partition at least differ in IMEI and MAC or is that stored elsewhere?
IMEIs are in modemst1 and modemst2. Not sure where MAC is
SigmundDroid said:
Oh, I have a similar problem with an S5:
https://forum.xda-developers.com/t/sm-g903f-wifi-and-bluetooth-broken.4380225/
Now that you mention it... Thanks for this hint btw but shouldn't the persistent partition at least differ in IMEI and MAC or is that stored elsewhere?
Click to expand...
Click to collapse
Apparently, I hadn't corrupted my persist. modem1st and modem2st govern both WIFI and mobile. Problem solved.
Good news here as well: Was about to sell it and saw that it won't boot... so I flashed it with one my many stockROMs collected lately (which I had all tried before).
Now, this time, during the initial setup it did show all wifis and works again. I'd guess my previous attempt "repaired" it (once I figure out what that previous thing was, I shall report).
Edit: Nah, never did figure it out... also it stopped working again - just like ungrateful black magic... Finally I sold it.