Database Info

No Baseband/IMEI/BLUETOOTH/SIM

Hello Guys,
I have a BIIIIIIG] Problem.
Today I updated my Ressurection 6.0.1 Rom to the 14/01 Build, after that my IMEI/BLUETOOTH/SIM was gone.
I literally tried EVERYTHING!
Here's a List of things I tried:
reflashing modemst1, modemst2
deleting modemst1, modemst2
Installing ColorOS
Installing latest Firmware
Clean Flashing the Latest CM13 build
Flashing Kitkat 4.4.4 Stock OS
...
...
I have really no more IDEA what could F****** help, I Think it's over...
Has anyone another Idea? I would be so happy!:highfive:
Please post me some potential solution:fingers-crossed:
PLEAAAASSSEE
:crying:

BadAndroidDoctor said:
Hello Guys,
I have a BIIIIIIG] Problem.
Today I updated my Ressurection 6.0.1 Rom to the 14/01 Build, after that my IMEI/BLUETOOTH/SIM was gone.
I literally tried EVERYTHING!
Here's a List of things I tried:
reflashing modemst1, modemst2
deleting modemst1, modemst2
Installing ColorOS
Installing latest Firmware
Clean Flashing the Latest CM13 build
Flashing Kitkat 4.4.4 Stock OS
...
...
I have really no more IDEA what could F****** help, I Think it's over...
Has anyone another Idea? I would be so happy!:highfive:
Please post me some potential solution:fingers-crossed:
PLEAAAASSSEE
:crying:
Click to expand...
Click to collapse
What twrp version were you using? Use the recommended TWRP 2.8.6.0 when flashing anything it's the only one that works perfectly.
Also it would be a good idea to download latest CM13, use TWRP 2.8.6.0, flash it and the wipe partitions then flash Resurrection Remix 6.0. You probably don't have the latest firmware that's needed
Sent from my A0001 using Tapatalk

Renosh said:
What twrp version were you using? Use the recommended TWRP 2.8.6.0 when flashing anything it's the only one that works perfectly.
Also it would be a good idea to download latest CM13, use TWRP 2.8.6.0, flash it and the wipe partitions then flash Resurrection Remix 6.0. You probably don't have the latest firmware that's needed
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I made everything in twrp 2.8.6.0... I did the procedure you wrote, but it didn't work for me...

Katinatez's 2.8.7.0.5 also works for flashing Marshmallow ROMs. If nothing TRULY works, use this tool: http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
NOTE: This is the absolute factory reset. You will not keep anything. And I mean anything. Storage, recovery, and such will be wiped and it'll put you back at the original CM11s ROM. This solved my issue however. I recommend trying EVERYTHING else first before doing this, and if you do, copy the internal phone storage onto your computer and any TWRP you've made. Good luck.
Oh, also, some firmwares I found for the OPO cause this even though developers say they work for some reason. Try some different firmwares if you can.

BadAndroidDoctor said:
I made everything in twrp 2.8.6.0... I did the procedure you wrote, but it didn't work for me...
Click to expand...
Click to collapse
Then try the unbrick guide probably a corrupt EFS. Last time I screwed mine up had the same symptoms
http://forum.xda-developers.com/showthread.php?t=2879061
Sent from my A0001 using Tapatalk

Renosh said:
Then try the unbrick guide probably a corrupt EFS. Last time I screwed mine up had the same symptoms
http://forum.xda-developers.com/showthread.php?t=2879061
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Sadly my Device isnt recognized by the program.
I installed qualcomm drivers, the drivers in the program but same, no detection.
And i have one more question!
How the f*** should I be able to connext my phone to the pc, but power it on after connecting??!?
The phone starts immediately after connecting and gets detected, guys, im so depressed.

BadAndroidDoctor said:
Sadly my Device isnt recognized by the program.
I installed qualcomm drivers, the drivers in the program but same, no detection.
And i have one more question!
How the f*** should I be able to connext my phone to the pc, but power it on after connecting??!?
The phone starts immediately after connecting and gets detected, guys, im so depressed.
Click to expand...
Click to collapse
If you have access to fastboot there's a solution on the last page. I did something similar, you can search for my posts in that thread and see what issue I had and what I did. I was scared out of my mind and it happened cause of some twrp backup I restored
Sent from my A0001 using Tapatalk

Renosh said:
If you have access to fastboot there's a solution on the last page. I did something similar, you can search for my posts in that thread and see what issue I had and what I did. I was scared out of my mind and it happened cause of some twrp backup I restored
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I tried this before...
So, I cant do the full restore if Fastboot is working?

So, i tried
fastboot delete modemst1 modemst1.bin
fastboot delete modemst2 modemst2.bin
fastboot erase persist
and then flashed oxygenOS, but still no baseband. F***

BadAndroidDoctor said:
So, i tried
fastboot delete modemst1 modemst1.bin
fastboot delete modemst2 modemst2.bin
fastboot erase persist
and then flashed oxygenOS, but still no baseband. F***
Click to expand...
Click to collapse
Where did you get these first two commands cause they're wrong. Go look at the thread and do them the exact same way. Hint: fastboot erase modemst2
Read the thread and follow the exact syntax otherwise you're doing zero work
Sent from my A0001 using Tapatalk

oh, i made a mistake in writing, ofc i used fastboot erase modemst1 and fastboot erase modemst2

oh, the phone behavour is unusual for bricked efs, too, i have no random reboots, I can use it normally, theres simply no baseband and IMEI.....

Sounds like a baseband issue, go here: http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 and install a new baseband.
Could you also dump the output of "logcat -b radio"

(dylanger) said:
Sounds like a baseband issue, go here: http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 and install a new baseband.
Could you also dump the output of "logcat -b radio"
Click to expand...
Click to collapse
So, I solved the Problem
The solution is:
Installing unofficial TWRP 2.8.7.0
fastboot erase modemst1
fastboot erase modemst2
Install OxygenOS 1.0.0, other Versions do not work.

BadAndroidDoctor said:
So, I solved the Problem
The solution is:
Installing unofficial TWRP 2.8.7.0
fastboot erase modemst1
fastboot erase modemst2
Install OxygenOS 1.0.0, other Versions do not work.
Click to expand...
Click to collapse
Nice so it seems twrp 2.8.6.0 wasn't playing nice with flashing firmware on your phone somehow. Enjoy your phone
Sent from my A0001 using Tapatalk

Sim card unrecognized.

Hi guys! I flashed the cm12.1 rom and then the gapps zip. Everything worked fine but with no LTE. So I flashed a 6045l 6.x modem radio and now the sim card is undetected. I flashed back to stock MM and my sim card is still undetected. Is there a fix for this?
I'm on the cricket USA michigan service on the 6945l model.

You flashed back using mobile upgrade software?

I had the same problem and had to reflash the Panasonic Eluga firmware to get my SIM to detect again (then had to restore a TWRP backup after another failed attempt to get LTE back). It seems the 6045i_6.0.1_K7VAUEB0BG00_radio_update_usa.zip from famewolf's Mega folder breaks SIM detection (or I failed to flash it properly ). After coming across this thread, I'm now looking for those referenced files to hopefully restore LTE to my phone.

KJMagnum said:
I had the same problem and had to reflash the Panasonic Eluga firmware to get my SIM to detect again (then had to restore a TWRP backup after another failed attempt to get LTE back). It seems the 6045i_6.0.1_K7VAUEB0BG00_radio_update_usa.zip from famewolf's Mega folder breaks SIM detection (or I failed to flash it properly ). After coming across this thread, I'm now looking for those referenced files to hopefully restore LTE to my phone.
Click to expand...
Click to collapse
I have the 5.02 files from an untouched 6045I, that I use on cricket, it fixed my sim and lte issues, I'm not at home right now but if you think they can help, I can post them when I get home. I flashed them via fastboot, then ran mobile upgrade q and everything was fixed, I'm pretty sure I would not have had to use mobile q, and simply flashing those files allowed eluga switch even to see cricket lte, they just are not 6.0.1 versions so not sure how they would work on a MM rom. Let me know if you want them......
Edit: I see you were flashing CM 12.1, they should work fine just enter fastboot and flash the files after installing 12.1

kal250 said:
I have the 5.02 files from an untouched 6045I, that I use on cricket, it fixed my sim and lte issues, I'm not at home right now but if you think they can help, I can post them when I get home. I flashed them via fastboot, then ran mobile upgrade q and everything was fixed, I'm pretty sure I would not have had to use mobile q, and simply flashing those files allowed eluga switch even to see cricket lte, they just are not 6.0.1 versions so not sure how they would work on a MM rom. Let me know if you want them......
Edit: I see you were flashing CM 12.1, they should work fine just enter fastboot and flash the files after installing 12.1
Click to expand...
Click to collapse
I would appreciate those files when you get a chance. Mobile Q did not restore those files/partitions so I'm running the Eluga lollipop files with a 6.0.1 Project Material build from The Marionette and everything works aside from LTE.

KJMagnum said:
I would appreciate those files when you get a chance. Mobile Q did not restore those files/partitions so I'm running the Eluga lollipop files with a 6.0.1 Project Material build from The Marionette and everything works aside from LTE.
Click to expand...
Click to collapse
here ya go just execute the following
https://mega.nz/#!2c9UVZiA!dxnaFqBgaxi-mp4TrOowD7Qx6AkcPHG7cmUZL4_i1LU
adb reboot bootloader
fastboot -i 0x1bbb flash fsg fsg
fastboot -i 0x1bbb flash modem modem
fastboot -i 0x1bbb flash modemst1 modemst1
fastboot -i 0x1bbb flash modemst2 modemst2
this worked for me and my 6045I variant, you have the 6045O(cricket) variant, I don't see any issues with it working, the radios cant be any different, but you do assume all risk.....

same problem here
kal250 said:
here ya go just execute the following
adb reboot bootloader
fastboot -i 0x1bbb flash fsg fsg
fastboot -i 0x1bbb flash modem modem
fastboot -i 0x1bbb flash modemst1 modemst1
fastboot -i 0x1bbb flash modemst2 modemst2
this worked for me and my 6045I variant, you have the 6045O(cricket) variant, I don't see any issues with it working, the radios cant be any different, but you do assume all risk.....
Click to expand...
Click to collapse
i have the same problem , please can you share key encryption for mega? thanks for your work

vicman2085 said:
i have the same problem , please can you share key encryption for mega? thanks for your work
Click to expand...
Click to collapse
Sorry about that see post above link has been updated with key....
---------- Post added at 07:52 AM ---------- Previous post was at 07:16 AM ----------
gamerlady96 said:
Hi guys! I flashed the cm12.1 rom and then the gapps zip. Everything worked fine but with no LTE. So I flashed a 6045l 6.x modem radio and now the sim card is undetected. I flashed back to stock MM and my sim card is still undetected. Is there a fix for this?
I'm on the cricket USA michigan service on the 6945l model.
Click to expand...
Click to collapse
See fix a few posts above.... You will have to downgrade to eluga switch firmware to do this fix
http://forum.xda-developers.com/idol-3/general/guide-repair-idol-3-t3372076
Also see...
http://forum.xda-developers.com/idol-3/help/warning-eluga-switch-rom-disables-s-lte-t3470543/page1

lte is working
thank you lte is working now

vicman2085 said:
thank you lte is working now
Click to expand...
Click to collapse
Yeah, I was so relieved when it fixed mine, lol but now I have a backup phone, I could not afford, I guess I could always return it to amazon but for 100$ with the JBL earbuds, i may just keep it. Glad it helped you out.

KJMagnum said:
I would appreciate those files when you get a chance. Mobile Q did not restore those files/partitions so I'm running the Eluga lollipop files with a 6.0.1 Project Material build from The Marionette and everything works aside from LTE.
Click to expand...
Click to collapse
Did you get a chance to see if these helped your issue?

kal250 said:
Did you get a chance to see if these helped your issue?
Click to expand...
Click to collapse
I was swamped with work and had to wait until my phone could be down (just in case). Thanks a bunch for the files and adb commands; I loaded them tonight and LTE is back. :good:

KJMagnum said:
I was swamped with work and had to wait until my phone could be down (just in case). Thanks a bunch for the files and adb commands; I loaded them tonight and LTE is back. :good:
Click to expand...
Click to collapse
Glad, everything worked out for you. I was so panicked when I lost LTE, I just assumed using Alcatels upgrade Q software it would fix things, but apparently it does not restore all partitions, which is strange, but at least there is a solution for it now. I have seen posts as far back as June where people have lost LTE, and we are just now finding out how to fix it, thanks to @Mario223 for providing the solution!!

kal250 said:
Did you get a chance to see if these helped your issue?
Click to expand...
Click to collapse
I sent this device to Europe,used eluga to downgrade and then installed Aleks OS and sim card is not detected at all. You think this would fix the issue? don't matter if LTE works as long as H+ is ok.
EDIT: service restored with these radio images.
Now i would like to try maybe European radio to see if LTE will work? does anyone have it?

patt2k said:
I sent this device to Europe,used eluga to downgrade and then installed Aleks OS and sim card is not detected at all. You think this would fix the issue? don't matter if LTE works as long as H+ is ok.
EDIT: service restored with these radio images.
Now i would like to try maybe European radio to see if LTE will work? does anyone have it?
Click to expand...
Click to collapse
Sorry I didn't get back with you sooner, it was a rough day... I have had that happen once, I had to flash those files with sim inserted. Glad things worked out...

Would you happen to have European radio for Europe lte bands? Just to try out both. But I'm guessing eluga baseband didn't work so it's better to keep it with USA lte radios. At least it works.

patt2k said:
Would you happen to have European radio for Europe lte bands? Just to try out both. But I'm guessing eluga baseband didn't work so it's better to keep it with USA lte radios. At least it works.
Click to expand...
Click to collapse
I don't have a backup of those, but anyone with a Y variant may be able to help...

delete
---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------
kal250 said:
I don't have a backup of those, but anyone with a Y variant may be able to help...
Click to expand...
Click to collapse
I have the same problem on 6045Y variant after phanasonic Eluga I lost some bands. The very strange thing and that if I install with phanasonic Eluga leaving inside the sim card of my operator (Tim Ita) recognizes the sim and everything worked, when I try to put a different sim type Vodafone Wind H3G are not recognized. I have to use it again phanasonic EUGA With Inside operator sim that I will want to use then.
I also tried using panasonic EUGA without any sim in the phone but in the end did not recognize any.
I tried with MobileQ update but ninte to do the situation remains as it exits the panasonic EUGA.
Pi would love to restore my phone as it was before I could put any SIM of any operator and was recognized.
Does anyone have the right partitions of the model 6045Y mono sim 16GB thanks in advance.

Thanks to kal250, i can confirm this worked on my mothers phone, which is a 6045Y , and restoring those files and installing 6.0.1 on top worked out well.
What is not good was the panasonic recovery which started this mess ;( but thanks again to kal250

kal250 said:
here ya go just execute the following
https://mega.nz/#!2c9UVZiA!dxnaFqBgaxi-mp4TrOowD7Qx6AkcPHG7cmUZL4_i1LU
adb reboot bootloader
fastboot -i 0x1bbb flash fsg fsg
fastboot -i 0x1bbb flash modem modem
fastboot -i 0x1bbb flash modemst1 modemst1
fastboot -i 0x1bbb flash modemst2 modemst2
this worked for me and my 6045I variant, you have the 6045O(cricket) variant, I don't see any issues with it working, the radios cant be any different, but you do assume all risk.....
Click to expand...
Click to collapse
This killed my wifi. Anyhelp? But i got 4g back

Huawei watch 2 firmware on 4g version.

Hi. I was just wondering is it possible to install huawei watch 2 rom on 4g version. I assume that It would loose 4g conectivity but is it even possible without bricking the watch?
Thank You

I have the same situation as you, no 4g Internet connection after updated to Oreo, try all the roms here in the forum but still no 4g Internet connection, if you try to flash the Bluetooth version of Huawei watch2 roms, you will lost the sim card function, of course you can try it but remember DO NOT flash the BOOTLOADER coz it will brick your watch!!
Also , I tried to flash back to watch 2 4g Nougat 7.1.1 but when I try to flash the bootloader , the device not allow to downgrade the BOOTLOADER to 7.1.1, but you can still flash the rest imgs ( boot, system, userdata, recovery) to get back to Nougat, but after flashing back the 4g Internet connection still not working.
If someone have any solutions, please share and let us know:crying:
Thanks

htc_black said:
I have the same situation as you, no 4g Internet connection after updated to Oreo, try all the roms here in the forum but still no 4g Internet connection, if you try to flash the Bluetooth version of Huawei watch2 roms, you will lost the sim card function, of course you can try it but remember DO NOT flash the BOOTLOADER coz it will brick your watch!!
Also , I tried to flash back to watch 2 4g Nougat 7.1.1 but when I try to flash the bootloader , the device not allow to downgrade the BOOTLOADER to 7.1.1, but you can still flash the rest imgs ( boot, system, userdata, recovery) to get back to Nougat, but after flashing back the 4g Internet connection still not working.
If someone have any solutions, please share and let us know:crying:
Thanks
Click to expand...
Click to collapse
In the twrp thread I posted the 4g Oreo firmware. I don't know if it will fix your problem, maybe flash OEM and aboot? Note aboot is the bootloader, so only as last resort!!!

hackintosh5 said:
In the twrp thread I posted the 4g Oreo firmware. I don't know if it will fix your problem, maybe flash OEM and aboot? Note aboot is the bootloader, so only as last resort!!!
Click to expand...
Click to collapse
Thanks and will try it when I back home
Can I just flashing the aboot and OEM without losing all user data

htc_black said:
Thanks and will try it when I back home
Can I just flashing the aboot and OEM without losing all user data
Click to expand...
Click to collapse
It depends really... Try just boot, OEM, recovery, system. Then try wipe data. Then try all again. Only now can you try aboot. NEVER EVER flash abootbak, it is a backup!!!

hackintosh5 said:
It depends really... Try just boot, OEM, recovery, system. Then try wipe data. Then try all again. Only now can you try aboot. NEVER EVER flash abootbak, it is a backup!!!
Click to expand...
Click to collapse
Thanks , so I should flash in sequence
Aboot
Boot
OEM
Recovery
System
Is it correct？

htc_black said:
Thanks , so I should flash in sequence
Aboot
Boot
OEM
Recovery
System
Is it correct？
Click to expand...
Click to collapse
Only flash aboot if it still doesn't work after the other 4 and a factory reset
Basically, don't flash aboot!!!

hackintosh5 said:
Only flash aboot if it still doesn't work after the other 4 and a factory reset
Basically, don't flash aboot!!!
Click to expand...
Click to collapse
Ok will try as you mentioned:good:

htc_black said:
Ok will try as you mentioned:good:
Click to expand...
Click to collapse
it shows
"target reported max download size of 262144000 bytes
Invalid sparse file format at header magi"
when i try to flash system img
how to fix it?
thanks
Edit: flashing successful but still no 4g data connection, everything remain the same as before , so weird
Bluetooth wifi no problem , calling no problem...

Wanna try to flash aboot but don't know what is the path located...
dd if=" don't really know the location to flash it"
Or I can use the same command fastboot flash aboot to flash it

htc_black said:
Wanna try to flash aboot but don't know what is the path located...
dd if=" don't really know the location to flash it"
Or I can use the same command fastboot flash aboot to flash it
Click to expand...
Click to collapse
Yes use Fastboot only. If it fails though there is no fixing it so I am not responsible for your actions. Only flash with a reliable usb

hackintosh5 said:
Yes use Fastboot only. If it fails though there is no fixing it so I am not responsible for your actions. Only flash with a reliable usb
Click to expand...
Click to collapse
Thanks , btw just wondering what is the extension of the aboot, img or bin? I think I will not flash it, and just bring it to the Huawei repair center.
Thanks for your help

htc_black said:
Thanks , btw just wondering what is the extension of the aboot, img or bin? I think I will not flash it, and just bring it to the Huawei repair center.
Thanks for your help
Click to expand...
Click to collapse
It's an elf afaik, but maybe a bin...
Btw Huawei will charge you - if the bootloader is unlocked you have no warranty.

Finally fixed it by sent it back to Huawei service centre:good: thanks

After smt backup writed but still

i have device which is booted hy smt mode
i was have efs persist backup and i writed
finger fixed but still signals not detected

Lemme tell there my meid was showing 004 something but after retry smt there's no more meid showing anymore

Same here on my prev op8

Same here on my prev samsung m20

L0ND0NB0Y said:
Same here on my prev op8
Click to expand...
Click to collapse
Did u fixed or not? And the worried thing own backup not working

Mr Hassan said:
Did u fixed or not? And the worried thing own backup not working
Click to expand...
Click to collapse
Even if u restored efs and persist, u still have modemst1 & modemst2 to restore which have carrier data and sim unlock data and it's device-unique so u cant copy it from other devices.
It's a closed case thing so move on and buy a new one.

L0ND0NB0Y said:
Even if u restored efs and persist, u still have modemst1 & modemst2 to restore which have carrier data and sim unlock data and it's device-unique so u cant copy it from other devices.
It's a closed case thing so move on and buy a new one.
Click to expand...
Click to collapse
I backup modem and efs by twrp
And i believe efs have modemst1 st2 already have then why not?
And ofcourse i write back own backup

Mr Hassan said:
I backup modem and efs by twrp
And i believe efs have modemst1 st2 already have then why not?
And ofcourse i write back own backup
Click to expand...
Click to collapse
Unfortunately there's some sort of tamper security thingy on modemst1 and modemst2, and fyi the efs partition have the data needed to RECREATE modemst1 and 2 but u have to somehow initiate the recreating mechanism or whatever it's called.
If u work harder u may come to the point where the phone identities the SIM card on the phone then displays the Tmobile SIM locked screen which u probably would wanna use an r-sim beneath the SIM to get past it.
It's really a long way and idk how u can reach the point demonstrated above cuz only one user mentioned that he encountered that Tmobile SIM locked screen and I unfortunately forgot where I did saw that user, so sorry.
Edit:
U could erase modemst1 and modemst2 with fastbootd in order to make the efs partiton recreate modemst1 and 2. It's just a thought u could try.

OnePlus 8t efs wipe(by twrp) procedure needed

Actually I hv OnePlus 8t, successfully converted to global after many tries. Since it was purchased from olx and it's IME wasn't original ,it was on some galaxy Samsung IME number. However with meid I was able to restore it to previous. But during converting rom I messed up with efs now it has no network I can't repair IMEI even sometimes it is unknown baseband. Right now it is on 12 global with fox recovery. I hv made a backup of current efs and persist both in TWRP fox . Now I want to reset efs but I don't know how I can do it by terminal in recovery. Plus I want to know how can I wipe persist too? I need commands for specific partitions.
Thanks
Br Zish

Do you have a backup of the efs partition before it corrupted? Also, why do you want to completely erase it?

Because it is showing one IMEI. And no network. I tried to repair it's meid by third party tool and it is somehow locked no network. And on some builds no baseband either. Yes I hv created backup

Even when I tried to search manual network there isn't any. Somehow radio not working. And I am one hundred percent sure it's efs. OnePlus will generate efs again and I will be able to repair it.

zishhaider said:
OnePlus will generate efs again and I will be able to repair it.
Click to expand...
Click to collapse
I don't know if this is the case, but if your really want to erase the efs partition, the command you were looking for is
Code:
dd if=/dev/zero of=/dev/block/by-name/modemst1

TheNewHEROBRINE said:
I don't know if this is the case, but if your really want to erase the efs partition, the command you were looking for is
Code:
dd if=/dev/zero of=/dev/block/by-name/modemst1
Click to expand...
Click to collapse
Are you sure? Because modemst1 modemst2 and fsg are efs as far as I know.. kindly confirm

And check attached to my first comment it says no directory or such file.

zishhaider said:
And check attached to my first comment it says no directory or such file.
Click to expand...
Click to collapse
You typed the command wrong.
zishhaider said:
Are you sure? Because modemst1 modemst2 and fsg are efs as far as I know.. kindly confirm
Click to expand...
Click to collapse
You can repeat the command with any partition you like.

Well i messed up. I created backup via twrp efs and persist. I flashed stock smt update by msm tool. Again unlocked bootloader (un official) restore perist and efs. Now finger print ok ime ok but no network. I can see network in manual network search but it won't registered. I think there is something in carrier partition which was wiped out kind of sim lock data. My mobile was already unlocked. One thing more I can't see tmobile unlock app in network setting. And start up logo after stock isn't tmobile. It is global one. Strange..

zishhaider said:
Well i messed up. I created backup via twrp efs and persist. I flashed stock smt update by msm tool. Again unlocked bootloader (un official) restore perist and efs. Now finger print ok ime ok but no network. I can see network in manual network search but it won't registered. I think there is something in carrier partition which was wiped out kind of sim lock data. My mobile was already unlocked. One thing more I can't see tmobile unlock app in network setting. And start up logo after stock isn't tmobile. It is global one. Strange..
Click to expand...
Click to collapse
I can share my carrier and persist partitions if you want.

Thanks that will help alot. But along with these two can you share your qcn.(you can edit it before share). As normally if we wipe efs qcn is necessary for network issue fix in generally.

zishhaider said:
Thanks that will help alot. But along with these two can you share your qcn.(you can edit it before share). As normally if we wipe efs qcn is necessary for network issue fix in generally.
Click to expand...
Click to collapse
I don't know what qcn is, sorry. These are my carrier and persist partitions:

Are you on android 13 and rooted?

Tell me which twrp you used?

zishhaider said:
Are you on android 13 and rooted?
Click to expand...
Click to collapse
No on Android 12 but I don't think those partitions are ever updated.
zishhaider said:
Tell me which twrp you used?
Click to expand...
Click to collapse
I dumped the partitions with dd. However if you're looking for a TWRP for Android 13 you can use https://forum.xda-developers.com/t/recovery-unofficial-twrp-oneplus-8t-oos13-2-26-23.4541965/.

How can i write these partition by twrp terminal? Or should i use adb with root?