A few people have had issues with the EFS getting corrupt or wiped on their OPO before they had a working backup. This guide has so far worked for 4 people to restore their EFS allowing them to access mobile data and bluetooth again.
Note: I really don't know why this works, I have contacted the dev of this rom to ask if he has any ideas but still waiting on a response.
1. Flash official TWRP
2. Flash this ColorOS rom using TWRP - http://forum.xda-developers.com/showthread.php?t=2772627 (you can skip all the account setups if you want)
3. Factory reset
4. Boot and setup ColorOS (you should see a network connect now with your sim card inserted, you will need to toggle mobile data on to test that)
5. If you have data in ColorOS you are good to flash back to CM11S anyway you want (you will need to factor reset after flashing back)
6. Save yourself the headache in the future and backup your EFS
Please post if this fix works for you.:victory:
Edit: I've went ahead and downloaded the ROM and I will hold on to it incase the original mirrors go down for some reason. Please PM me if they do.
One of the ones who can confirm this works. Will post in the official thread.
Worked for me also.
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
tw1tch175 said:
A few people have had issues with the EFS getting corrupt or wiped on their OPO before they had a working backup. This guide has so far worked for 3 people to restore their EFS allowing them to access mobile data and bluetooth again.
Note: I really don't know why this works, I have contacted the dev of this rom to ask if he has any ideas but still waiting on a response.
1. Flash official TWRP
2. Flash this ColorOS rom using TWRP - http://forum.xda-developers.com/showthread.php?t=2772627 (you can skip all the account setups if you want)
3. Factory reset
4. Boot and setup ColorOS (you should see a network connect now with your sim card inserted, you will need to toggle mobile data on to test that)
5. If you have data in ColorOS you are good to flash back to CM11S anyway you want (you will need to factor reset after flashing back)
6. Save yourself the headache in the future and backup your EFS
Please post if this fix works for you.:victory:
Click to expand...
Click to collapse
Hi, i failed and i wiped EVERYTHING of my phone, i only had the fasboot mode, i installed CWM and the cyanogemod rom, now everything works, and i have the imei in the box, however, i dont have the possibility of EFS backup anymore.... any ideas..?
Gambalajillo said:
Hi, i failed and i wiped EVERYTHING of my phone, i only had the fasboot mode, i installed CWM and the cyanogemod rom, now everything works, and i have the imei in the box, however, i dont have the possibility of EFS backup anymore.... any ideas..?
Click to expand...
Click to collapse
Official TWRP doesn't have EFS backup in it, you have the get the unofficial one http://forum.xda-developers.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
Yank555 said:
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
Click to expand...
Click to collapse
Odd, maybe you could try using TWRP to delete everything again including system, then sideload and boot ColorOS.
tw1tch175 said:
Official TWRP doesn't have EFS backup in it, you have the get the unofficial one http://forum.xda-developers.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
Click to expand...
Click to collapse
To add to that you can just boot the unofficial recovery using "fastboot boot recovery.img" to do your efs backup if you would prefer to keep the official TWRP installed. That way it only boots that recovery to allow you to do the backup of your EFS partition and doesn't erase your current recovery. That's how I did it.
sabbotage said:
To add to that you can just boot the unofficial recovery using "fastboot boot recovery.img" to do your efs backup if you would prefer to keep the official TWRP installed. That way it only boots that recovery to allow you to do the backup of your EFS partition and doesn't erase your current recovery. That's how I did it.
Click to expand...
Click to collapse
WOW thanks, i do it and and i tell you how did it go in a few minutes.
I see that the OP has been thanked and this thread has a few success stories so I am giving it a bump for others to view in case of the same issue.
I just flashed the factory image... I never had the problem again
Yank555 said:
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
Click to expand...
Click to collapse
Im having the same problem as you have Yank555. It started with the AudioFX FCs rendering the device useless.
Next i tried to reflash the standard CM11s 25R rom back to get my phone normal again, it didnt work.
Then i remember i have a nandroid from a few days ago. Not thinking to read up on known issues with the OPO EFS i tried a restore.
My EFS is gone and the phone will not work unless im on ColourOs120. Wifi doesnt work, just basic phone functions.
Still waiting for a miracle for this problem.
Any suggestion guys?
jwai85 said:
Im having the same problem as you have Yank555. It started with the AudioFX FCs rendering the device useless.
Next i tried to reflash the standard CM11s 25R rom back to get my phone normal again, it didnt work.
Then i remember i have a nandroid from a few days ago. Not thinking to read up on known issues with the OPO EFS i tried a restore.
My EFS is gone and the phone will not work unless im on ColourOs120. Wifi doesnt work, just basic phone functions.
Still waiting for a miracle for this problem.
Any suggestion guys?
Click to expand...
Click to collapse
Did you open a service request ? Any response ? So far all I got 5 days later was a "please fastboot flash factory images, case closed." which quite obviously did not help, so case reopened, but again nothing from them in 4 days, now.
But I wonder if my first thought is still correct, flawed emmc as flashing seems to work ... might be a radio hardware issue ? Just don't quite get what the AudioFX has to do with that... cause simply rooting the device and installing apps and making a few nandroid backups is no way to brick anything.
But anyway, tbh, OnePlus is mostly dead to me as a company, worst invest ever so far, nice if your device works, but service is not even close to bad, it's pretty much non-existing ... and for a supposedly "best service ever" it's quite, let's say, "impressing"
JP.
Nope, i have not tried opening a ticket, mine is a grey import from China.
There is something terribly wrong somewhere hardware wise. The audiofx problem only happens if i flash the CM11s. After ColourOS i have tried flashing the CM11 M8.
Im also wondering if i should try to use this OPO made rom to see if it can help.
https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/
jwai85 said:
Nope, i have not tried opening a ticket, mine is a grey import from China.
There is something terribly wrong somewhere hardware wise. The audiofx problem only happens if i flash the CM11s. After ColourOS i have tried flashing the CM11 M8.
Im also wondering if i should try to use this OPO made rom to see if it can help.
https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/
Click to expand...
Click to collapse
Give it a go, not much to lose. Didn't work for me, though.
JP.
Sent from my Nexus 5 running stock rooted AOSP on Yank555.lu v1.0-alpha5 kernel.
This worked for me! I'm back in business! Thanks guys for getting this figured out, I thought my phone was done.
I hate to bring this back up.
I have a Nandroid of my stock CM11S on my phone. I used it for the update to 300 to get firmware, then made a backup of it and went back to the custom Rom I had been on.
Today, I went and restored the backup of CM11S to sideload the newest update. Weirdly, after restoring I have an unknown baseband. But if I go back to the custom Rom backup I still have a baseband.
I wonder if TWRP just didn't backup the correct partitions? I am on the offficial TWRP. But I do have a backup that contains my EFS backup from the other TWRP that has that option.
I think I know what corrupted my efs....I used the official twrp 2.7.1.1 which for some reason saves modemst1. I remember restoring st1 when I corrupted it the first time with the official 2.7.1.1. Well I did it again trying to restore a nandroid with the official twrp 2.7.1.1. Do not restore the saved modemst1 from the official twrp 2.7.1.1. You will encounter problems.
So, this same thing happened to me...i happily using 30O and not really any issues and getting good battery life~17 hrs w/moderate use. And no other bugs.
Found the 33R update here on the forums and downloaded it and flashed through TWRP.
Thats when trouble found me, lost network and wifi stuck trying to turn on but never finds wifi. Then reading through xda someone suggested to check IMEI and it was gone. I had NOT done any prior back ups other than Nandroid prior to flashing update.
Restore still didn't fix it.
I tried this (flash ColorOS and CM11) but still didnt fix it. I was bummed as my OPO is very new and I had been happy with it.
CM11 or by restore, windows will not detect it even with drivers loaded. Flashing colorOS would allow windows XP to recognize internal and allow me to send files so i tried custom ROMs and CM stock and Mahdi but none worked. Luckily my TWRP still works and i am able to boot and get into fasboot.
I finally got mine fixed with rooted stock 33R from here on xda!
Now my OPO is back in business!!!
Save st1 and st2 with vonnegut's method http://forum.xda-developers.com/showthread.php?p=54623075.. Put it in a safe place for later. I uploaded them to google drive and onedrive . It saved me today.
For those of you that were able to recover, did you lose your entire EFS folder? Mine is completely gone and I don't think this ColorOS trick works either. I've tried it all last night and I fell asleep at my desk
Hi all. had an issue while trying to load up LinageOS last night. Was having trouble with keeping root. Seem to have solved that by using Magisk 11.6 and the SUaddon rather than any superuser version.
Anyhow as part of this i went back to a TWRP backup of which i had 3 different versions (stock and lineage) available being a bit ocd with backups. They all flashed ok, but for ALL of them, when the phone booted it kept telling me had wrong pattern when i tried to unlock. Not good. Thought only way back was to factory reset and do all the app loading and setup again.
After a bit of searching found this thread and this post.
https://forum.xda-developers.com/showpost.php?p=69189392&postcount=65
Worked a treat.
The other methods didn't and i suspect are obsolete.
Anyow, posted for info if anyone else runs into this problem. Success dependent on having working TWRP and being able to boot to that as you need to use the File Manager capability in TWRP.
Seeyahs!
Same thing happened to me last week, when I tried lineage, found the answer on HTC forum,.
So avoid that from happening , before you make a backup, unlock all securities( pin, password, fingerprint) then make a backup, next time you restore your backup, it will boot without any issues.
ta for that. will try.
Hello guys !
I was rocking OOS 4.5.3 with TWRP and root all fine, and I tried some dualboot stuff that I saw here on XDA (plot twist, don't try it) and then I ran into issues
I managed to reinstall the rom fine, but at the reboot, my fingerprint sensor wasn't picking up my fingers
I found out that when I try to register a fingerprint, it works fine, untill the last step where it stop picking my finger (not even vibrates)
I also noticed that it's impossible to delete a stored fingerprint
Any ideas ?
GMX1PT said:
Hello guys !
I was rocking OOS 4.5.3 with TWRP and root all fine, and I tried some dualboot stuff that I saw here on XDA (plot twist, don't try it) and then I ran into issues
I managed to reinstall the rom fine, but at the reboot, my fingerprint sensor wasn't picking up my fingers
I found out that when I try to register a fingerprint, it works fine, untill the last step where it stop picking my finger (not even vibrates)
I also noticed that it's impossible to delete a stored fingerprint
Any ideas ?
Click to expand...
Click to collapse
On man I'm in totally the same situation with you! I tried that dualboot too and stuck in boot screen, so i flashed the original rom zip and managed to boot well but the fingerprint isn't working any more......:crying:waiting for solutions
Okay, now that I woke up I will try to do a data wipe, I'll tell you about it, please do tell me if you find something
I'm also unable to activate wifi
Sounds like a good question for the dual boot thread.
If I remember right from previous threads about dual boot on other devices is, you should delete your original fingerprint or set it up as no lock before doing all the stuff with dual boot. I might be wrong.
ab7casper said:
Sounds like a good question for the dual boot thread.
If I remember right from previous threads about dual boot on other devices is, you should delete your original fingerprint or set it up as no lock before doing all the stuff with dual boot. I might be wrong.
Click to expand...
Click to collapse
Well, can't see where it is listed in the instructions, but thankfully this issue is nothing a full wipe can't fix
GMX1PT said:
Well, can't see where it is listed in the instructions, but thankfully this issue is nothing a full wipe can't fix
Click to expand...
Click to collapse
It's not, it was just a user having that issue on a Nexus 6P. Reset should fix. Set it up without a lock on it, then you should be able to set up fingerprints for each rom.
Thinking about. It, that sounds like a lot of hassle if you just want to try out different roms quickly.
GMX1PT said:
I'm also unable to activate wifi
Click to expand...
Click to collapse
I did not do this dual boot but I ran into WiFi not activating (endless searching for a WiFi access point), but I was able to fix it. Your probably uninterested in how I got into the situation but I fixed it with a previous nandroid backup done with one of the earlier versions of TWRP. Here are the steps that recovered WiFi:
Using TWRP, advance wipe Dalvik & Cache
Restore from a nandroid backup (OOS v4.5.2 in this case) ONLY system & /System
Reboot into the system and ignore TWRP's no OS warning
Using TWRP, advance wipe Dalvik & Cache
Reboot back into TWRP recovery and flash the Full v4.5.5 OTA file (~1.6GB) AND flash root (e.g. SuperSU)
Clear Dalvik&Cache and reboot into the system
After I did that everything return back to normal including the WiFI issue. The fingerprint scanner is working normally and I never lost any data what so ever.
Hello, so i was running @xXx 9.1 and i decided to update to 9.2. So I simply dirty flashed (which should normally work) and rebooted. However I was stuck on the booting logo for ages to I bootted back to TWRP to try and reflash, however when I got to TWRP, everything was encrypted (sdcard/ was full of nonsense which looks like encrypted files). However it didn't ask for my password as it usually did and I can't find a single way to manually decrypt. Does anyone know what I can do to not loose ALL my data?! I backup via Titanium Backup as I usually do incase of a data problem but my entire internal storage is not accessible.
Hope someone can help!
just flash stable oos5 firmware+modem, phone should boot and able to decrypt.
Im_Mattgame said:
Hello, so i was running @xXx 9.1 and i decided to update to 9.2. So I simply dirty flashed (which should normally work) and rebooted. However I was stuck on the booting logo for ages to I bootted back to TWRP to try and reflash, however when I got to TWRP, everything was encrypted (sdcard/ was full of nonsense which looks like encrypted files). However it didn't ask for my password as it usually did and I can't find a single way to manually decrypt. Does anyone know what I can do to not loose ALL my data?! I backup via Titanium Backup as I usually do incase of a data problem but my entire internal storage is not accessible.
Hope someone can help!
Click to expand...
Click to collapse
same problem any answer?
Suraxit said:
same problem any answer?
Click to expand...
Click to collapse
What version of TWRP are you running. This is an old thread.
Hi there,
I have two D5503's , one main one with PWR_BTN broken and with ROOT and one where the button works but the vibration is way too loud and never been ROOTED.
Anyway, after playing around trying to get rid of KingRoot and go to SuperSU it didn't work so I made a TWRP Backup of all internal partitions.
For some reason the phone didn't want to boot from one moment to the other and just went from "Sony Xperia Screen" to "Powered by Android Screen" and then rebooted.
No worries I thought, I got a backup. Then wiped everything and used TWRP to recover the previously made backup. After Restore was done - same behaviour.
So I thought - oh well, what the heck. Try a new ROM from XDA. That's what I did, flashing "[email protected][email protected]" from here in the forum.
Then I downloaded the most important apps and configured them, running a backup afterwards with the thought "if anything goes wrong I can still go back to this fresh image where SuperSU works fine and all the cr*p from the past years of using the phone and not wanting to "re-initiate" my phone. So just for kicks and wiped it again and then restored the freshly made backup. :crying: boohoo, same bootloop again.
To make it short: Is it me doing something wrong or what is going on?
Thanks for your time reading this and your input. :good:
Greetz
James
Hi Mods and Admins, I just found out I posted this in the wrong forum.
Can you please move it to here: https://forum.xda-developers.com/sony-xperia-z1-compact/help
Thanks!