Okay, so after flashing I didn't have wifi, data connection etc.
I found out my IMEI / BASEBAND were Unknown
I tried everything I could find on the forums then came to the solution I probably lost the EFS partitions
Is there anything I can do to fix / repair it manually, without sending the device away a few weeks for repair?
Pretty sure this is your only hope:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Didn't you backup your EFS partition?
Transmitted via Bacon
timmaaa said:
Pretty sure this is your only hope:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Didn't you backup your EFS partition?
Transmitted via Bacon
Click to expand...
Click to collapse
I'd never heard of it before
I know the basics of flashing etc that's it.
The only backup I had(Not sure if efs is backed up with this as well, but it was a TWRP backup) gave errrors when trying to restore it so I did a full wipe and ended up in this position
PrivateerGerrit said:
I'd never heard of it before [emoji14]
I know the basics of flashing etc that's it.
The only backup I had(Not sure if efs is backed up with this as well, but it was a TWRP backup) gave errrors when trying to restore it so I did a full wipe and ended up in this position
Click to expand...
Click to collapse
TWRP doesn't backup your EFS partition. You'll need to try the fix I linked you to.
Transmitted via Bacon
timmaaa said:
TWRP doesn't backup your EFS partition. You'll need to try the fix I linked you to.
Transmitted via Bacon
Click to expand...
Click to collapse
Tried but no success
I'll await customer support I guess
Just in case(The thread is kinda messy IMO) these are my steps I did:
-fastboot erase persist
-fastboot flash persist persist.img
Didn't fix it.
Also tried the full package provided, installing it and then doing the same steps as above.
Since that didn't work either I tried these commands as well(with no success)
-fastboot erase modemst1
-fastboot erase modemst2
Edit:
I'm suprised there isn't a way to fake it or something?(The IMEI)
I know it's possible for MTK phones, why not for this one.
Or some sort of solution since I still know my IMEI I should be able to recreate those partitions I'd guess
My friend had the same situation wherein the EFS was corrupted.
He flashed the Stock ROM CM11S and it solved the issue. (05Q)
Not sure, if this works for you.
Related
My question is this: I want to take an adb backup, then unlock my bootloader, then restore the adb backup. Will it work (and not brick my device like I've done before!), and if so, will my bootloader still be unlocked or will it be locked again ?
Thanks for advice. If it's really necessary I know I can lose my data and restore everything, but it's a time-wasting pain so I thought I'd try it this way!
Currently I'm on 05Q official stock, no root/busybox, stock recovery and kernel. I.e. everything stock.
pmedwards25 said:
My question is this: I want to take an adb backup, then unlock my bootloader, then restore the adb backup. Will it work (and not brick my device like I've done before!), and if so, will my bootloader still be unlocked or will it be locked again ?
Thanks for advice. If it's really necessary I know I can lose my data and restore everything, but it's a time-wasting pain so I thought I'd try it this way!
Currently I'm on 05Q official stock, no root/busybox, stock recovery and kernel. I.e. everything stock.
Click to expand...
Click to collapse
What about
fastboot boot (twrp) recovery.img
And then make a backup in recovery
And copy the backup somewhere safe
I'm not sure if that works on 5Q though
waterdaan said:
What about
fastboot boot (twrp) recovery.img
And then make a backup in recovery
And copy the backup somewhere safe
I'm not sure if that works on 5Q though
Click to expand...
Click to collapse
Isn't that the same as adb backup?
pmedwards25 said:
Isn't that the same as adb backup?
Click to expand...
Click to collapse
A backup in recovery backs up
System
Data
It won't backup your sdcard
I don't know what adb backup does, I think it backs up your apps and data
waterdaan said:
A backup in recovery backs up
System
Data
It won't backup your sdcard
I don't know what adb backup does, I think it backs up your apps and data
Click to expand...
Click to collapse
You can add parameters to make it backup system, apks, app data, sdcard and others. Should this work in theory?
waterdaan said:
What about
fastboot boot (twrp) recovery.img
And then make a backup in recovery
And copy the backup somewhere safe
I'm not sure if that works on 5Q though
Click to expand...
Click to collapse
You can't boot a recovery with a locked bootloader anymore, they patched that way back in the 30O update I believe.
Transmitted via Bacon
I know i should've backed up everything before flashing but whats done is done!
I have tried at least 10 ways to restore IMEI ranging from:
1-Flashing Color OS
2-Flashing Stock ROM
3-Flashing Modem drivers
4-Flashing CM nightly
5-Flashing Old Stock ROM
6-Flashing persist.img
And the list goes on
Can anybody save me please
awsan said:
I know i should've backed up everything before flashing but whats done is done!
I have tried at least 10 ways to restore IMEI ranging from:
1-Flashing Color OS
2-Flashing Stock ROM
3-Flashing Modem drivers
4-Flashing CM nightly
5-Flashing Old Stock ROM
6-Flashing persist.img
And the list goes on
Can anybody save me please
Click to expand...
Click to collapse
Have you a backup of your EFS folder ?? Restore it
Or try another modem
Or try to flash cm12s via fastboot
jamal2367 said:
Have you a backup of your EFS folder ?? Restore it
Or try another modem
Or try to flash cm12s via fastboot
Click to expand...
Click to collapse
Fixed it after 6 hours of trying stuff thanks to this thread:
http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
And learned a very important thing ~Modem Drivers flashed through recovery never work you always need to use fast boot for them to work
awsan said:
Fixed it after 6 hours of trying stuff thanks to this thread:
http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
And learned a very important thing ~Modem Drivers flashed through recovery never work you always need to use fast boot for them to work
Click to expand...
Click to collapse
Good to See your phone works again ... I have never problems to flash Modems via recovery ...but fastboot are better....
I know this is an old post. But I'm trying to regain my IMEI. I updated my phone to Oxygen and started having problems and I noticed I had no baseband, imei and the phone would constantly reboot. I put in a ticket at OnePlus and the only way they will help ya is if you open your computer up to them for a remote session. I will never buy another devi e from them again!
Anyway.. So this post has given me some hope. From what I'm reading I need to flash these modems through fastboot and not recovery? I can try all these modems to see if I regain my IMEI?
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
Noobie mistake
so I just accidentally formatted the persist partition and now my fingerprint no longer working, in some other forum they got it working by simply flash persist.img backed up from another device. Maybe if somebody could provide one or give any possible workaround this. Thanks
hayatnas18 said:
Noobie mistake
so I just accidentally formatted the persist partition and now my fingerprint no longer working, in some other forum they got it working by simply flash persist.img backed up from another device. Maybe if somebody could provide one or give any possible workaround this. Thanks
Click to expand...
Click to collapse
Re install original rom whit adb
I already flashed the fastboot image, isn't that the same?
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?