Hi,
My mobile data no longer works. I've done a lot of research, tried every fix, to no avail. My WiFi works, it's only my mobile data.
Things I've tried:
Following this guide: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Completely reverting to stock
Flashing a stock, rooted 44S + radio files
Flashing ColorOS, and then flashing CM11S using this guide: http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Sticking the SIM card in my Galaxy S3 to see if it works (spoiler: it does)
Restoring previous nandroid while data was working fine
Under ColorOS, I have a notification that says "The NV partition is invalid!". Just thought I'd mention that.
Stupid me didn't backup my EFS. No APNs, unknown IMEI, unknown baseband, etc.
I'm at a loss guys. I'd greatly appreciate your help.
Thanks,
Niko
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
timmaaa said:
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
Click to expand...
Click to collapse
Yup. Sadly didn't work.
You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon
timmaaa said:
You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon
Click to expand...
Click to collapse
You think it would be worth trying to get a new sim card from my carrier?
It isn't the SIM that's the problem, your EFS partition is corrupt.
Transmitted via Bacon
If my EFS partition was corrupt, why does my Wifi work?
That's normal.
Transmitted via Bacon
I FIXED IT! This is exactly what I did.
* Flash ColorOS from this post: https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
* Download and install OTA updates for ColorOS
* Flash back TWRP
* Flash 44S (Pre-Rooted)
* Boot up phone without SIM in (at this point I checked the settings and to my joy saw that baseband wasn't unknown
* Power down, insert SIM in, reboot
NikoZBK said:
I FIXED IT! This is exactly what I did.
* Flash ColorOS from this post: https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
* Download and install OTA updates for ColorOS
* Flash back TWRP
* Flash 44S (Pre-Rooted)
* Boot up phone without SIM in (at this point I checked the settings and to my joy saw that baseband wasn't unknown
* Power down, insert SIM in, reboot
Click to expand...
Click to collapse
Hi, have the same issue. Did you flash the ColorOS thru a recovery or thru SDK Tools? and what recovery did you use to flash if you flashed with a recovery?
grneyez said:
Hi, have the same issue. Did you flash the ColorOS thru a recovery or thru SDK Tools? and what recovery did you use to flash if you flashed with a recovery?
Click to expand...
Click to collapse
I flashed ColorOS in fastboot mode, so through SDK tools. I manually flashed every .img. In other words, I just followed the guide in the link I gave.
NikoZBK said:
I flashed ColorOS in fastboot mode, so through SDK tools. I manually flashed every .img. In other words, I just followed the guide in the link I gave.
Click to expand...
Click to collapse
I gonna give it a shot, see what happens. I'm not so good in with SDK tools.
grneyez said:
I gonna give it a shot, see what happens. I'm not so good in with SDK tools.
Click to expand...
Click to collapse
Please post back how it goes.
NikoZBK said:
Please post back how it goes.
Click to expand...
Click to collapse
I will thanks.
NikoZBK said:
Please post back how it goes.
Click to expand...
Click to collapse
Worked like a charm, thanks so much for your help.
timmaaa said:
You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry, bit of a noob here!
What is the EFS and how would I go about backing it up? I don't see any option for that in TWRP?
Rkr87 said:
Sorry, bit of a noob here!
What is the EFS and how would I go about backing it up? I don't see any option for that in TWRP?
Click to expand...
Click to collapse
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
NikoZBK said:
I FIXED IT! This is exactly what I did.
* Flash 44S (Pre-Rooted)
Click to expand...
Click to collapse
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?
DGX_Goggles said:
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?
Click to expand...
Click to collapse
44S is short for XNPH44S, which is the latest build of CM11S (the stock firmware) for this phone.
Transmitted via Bacon
DGX_Goggles said:
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?
Click to expand...
Click to collapse
No, I did this for the global version, but the steps should work for you as well.
Related
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
dudekiller said:
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
Click to expand...
Click to collapse
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
quendil said:
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
Click to expand...
Click to collapse
im still getting invalid bootloader img
dudekiller said:
im still getting invalid bootloader img
Click to expand...
Click to collapse
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
quendil said:
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
Click to expand...
Click to collapse
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
dudekiller said:
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
Click to expand...
Click to collapse
Oh damn...
On bootloader when you give the command fastboot devices does it show you anything?
i wonder if the TWRP bug is why i was getting bootloop when flashing Bootanimations the other day?
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
alright guys i figured it out i did a oem lock and unlock and then the factory image worked so im stock right now... it might stay that way for a bit.. lol
comicbookguy72 said:
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
Click to expand...
Click to collapse
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Zepius said:
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Click to expand...
Click to collapse
his first priority is fixing it. his second priority is possibly finding out why he borked it and not making the same mistake again. i've borked stuff learning and fixed it with toolkits.
not everyone wants to learn ADB or fastboot commands, or install the SDK, and NOT EVERYONE HAS TO. not everyone is a would-be developer
dudekiller said:
they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
Click to expand...
Click to collapse
So why did you flash via TWRP then?
Han Solo 1 said:
So why did you flash via TWRP then?
Click to expand...
Click to collapse
i didnt go through the faqs before installing, i looked at the rom and what it offered. it said stable so i wasnt to worried about bugs since i was coming from cm11
I was restoring to stock and got this error at the update -w step. I am returning to the 38R release and I am stuck at the boot screen with no luck.
Any advice?
How did you install adb/fastboot? That error usually comes due to an outdated version.
Transmitted via Bacon
timmaaa said:
How did you install adb/fastboot? That error usually comes due to an outdated version.
Transmitted via Bacon
Click to expand...
Click to collapse
I was using this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
And I downloaded the firmware link provided for the 64GB version in step number 1.
I used the flash-all.bat command and it never rebooted correctly at the end.
bukithd said:
I was using this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
And I downloaded the firmware link provided for the 64GB version in step number 1.
I used the flash-all.bat command and it never rebooted correctly at the end.
Click to expand...
Click to collapse
That wasn't what I asked, I asked how you installed adb & fastboot.
timmaaa said:
That wasn't what I asked, I asked how you installed adb & fastboot.
Click to expand...
Click to collapse
Ahh, sorry. Now that you mention it, I am using adb/fastboot from an old toolkit. You pretty much pointed out what I was just looking into. I'm downloading the new sdk files now...
bukithd said:
Ahh, sorry. Now that you mention it, I am using adb/fastboot from an old toolkit. You pretty much pointed out what I was just looking into. I'm downloading the new sdk files now...
Click to expand...
Click to collapse
Cool, that should fix it for you.
Transmitted via Bacon
timmaaa said:
Cool, that should fix it for you.
Transmitted via Bacon
Click to expand...
Click to collapse
Well now I get something new...
"Device not unlocked cannot flash or erase"
I unlocked it already... I have the stupidest stuff happen to me. I've already tried fastboot oem unlock again... didn't work.
bukithd said:
Well now I get something new...
"Device not unlocked cannot flash or erase"
I unlocked it already... I have the stupidest stuff happen to me. I've already tried fastboot oem unlock again... didn't work.
Click to expand...
Click to collapse
Quite a few people have had to deal with the spontaneous locking of the bootloader, I can't remember the fix off the top of my head though. It's been discussed quite a bit in this q&a section though.
Transmitted via Bacon
hey guys , I bought an OPO in china when I was on vacation but now it has the color os which is horrbile and has no google services. how can I switch to the Cyanogen?
Take a look at the general section or faq. There must be guides how to change to cm11
Send by Hyperdrive on one+One
I did check but the problem is that i have the 64gb and i saw people saying that after they changed to the cyanogenmod it showed that they had 16 GB only
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow sections 1, 2, 3, and 8. You shouldn't have any problems with your userdata (64gb internal storage) at all, but if you do it's as simple as flashing the correct userdata file.
Transmitted via Bacon
timmaaa said:
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow sections 1, 2, 3, and 8. You shouldn't have any problems with your userdata (64gb internal storage) at all, but if you do it's as simple as flashing the correct userdata file.
Transmitted via Bacon
Click to expand...
Click to collapse
Hey thankyou very much but I have a problem
I started following the instructions until i got to UNCHECK UPDATE RECOVERY WITH SYSTEM UPDATES , well i have the color os and it doesn't have that option in developer options??!?
Could I just download the newest TWRP recovery instead of the 2.8.1.0 and then it won't have anything to update to ?
Or do I have to somehow find this "Update recovery with system updates" button?
Thankyou very much guys
I skipped the custom recovery part Because of the option that I couldn't find(Advice from the OP forums) and went straight to 8 And it still worked!!!!!!!!
tomgilon said:
Thankyou very much guys
I skipped the custom recovery part Because of the option that I couldn't find(Advice from the OP forums) and went straight to 8 And it still worked!!!!!!!!
Click to expand...
Click to collapse
The point of installing the custom recovery was so you could make a backup of your stock system in case you need it in future. So whoever told you to skip that part doesn't know what they're talking about.
Transmitted via Bacon
timmaaa said:
The point of installing the custom recovery was so you could make a backup of your stock system in case you need it in future. So whoever told you to skip that part doesn't know what they're talking about.
Transmitted via Bacon
Click to expand...
Click to collapse
Why do I need to have a backup of my stock system?
tomgilon said:
Why do I need to have a backup of my stock system?
Click to expand...
Click to collapse
Just in case something goes wrong in future and you need to restore your phone to the way it was when you opened the box. It doesn't matter now though, it's too late.
timmaaa said:
Just in case something goes wrong in future and you need to restore your phone to the way it was when you opened the box. It doesn't matter now though, it's too late.
Click to expand...
Click to collapse
There is nothing I can do to make sure my phone will work if something goes wrong?
I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.
Have you tried using CyanDelta?
https://play.google.com/store/apps/details?id=com.cyandelta
Transmitted via Bacon
Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk
timmaaa said:
Have you tried using CyanDelta?
Transmitted via Bacon
Click to expand...
Click to collapse
Tried that earlier today, didn't help anything.
gmac1990 said:
Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yeah, I think that might be my best bet. I guess it's better than nothing, haha. Thanks for you answers guys.
It probably is due to not having updated firmware. Which nightly? Wipe everything and flash the most recent nightly or go to blisspop thread and find the updated firmware zip it's around 30mb and flash that. It should fix your boot loop issues
Sent From Lollipopified Bacon Goodness!
The firmware can be found here:
http://www.vanir-exodus.net/exodus/bacon/
Transmitted via Bacon
Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.
Skizwack said:
Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.
Click to expand...
Click to collapse
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
I suppose that may have been my problem all along. The main problems I was having were just little bugs (system UI very rarely crashing, and a couple other minor annoyances), but I guess those could have been caused by having the wrong firmware. Maybe I'll give it another go soon. Now that I'm all settled in to CM11S, haha. Thanks again!
Has anyone else had any issues with the automated download and install feature in the CM12 settings? Mine will download the night lies and even automatically boot into TWRP but it doesn't flash?
timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?
Skizwack said:
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?
Click to expand...
Click to collapse
which recovery and version are you using?
playya said:
which recovery and version are you using?
Click to expand...
Click to collapse
TWRP 2.8.4.1
Skizwack said:
TWRP 2.8.4.1
Click to expand...
Click to collapse
What's the name of the firmware file you flashed?
Transmitted via Bacon
timmaaa said:
What's the name of the firmware file you flashed?
Transmitted via Bacon
Click to expand...
Click to collapse
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.
Skizwack said:
I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.
Click to expand...
Click to collapse
have tried different version TWRP?
Skizwack said:
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.
Click to expand...
Click to collapse
What about when you download the whole ROM zip from the CM site?
geowolf1000 said:
have tried different version TWRP?
Click to expand...
Click to collapse
The version he's on is fine.
timmaaa said:
What about when you download the whole ROM zip from the CM site?
Click to expand...
Click to collapse
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.
Skizwack said:
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.
Click to expand...
Click to collapse
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.
timmaaa said:
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.
Click to expand...
Click to collapse
If I remember right, I do. I'm on the latest version now though, so I can't really test it. When a new one comes out tomorrow I'll give it a go and see what happens.
My phone suddenly reboot during WhatsApp. After reboot, Welcome screen appear like 1st time boot after flash new rom. I have to select language and everything. Need to update all default software that come with 11S. But if I reboot again, same thing happen like I explained above. Running on 44S and stock kernel.
Sounds like you have a corrupt data partition. Is your bootloader unlocked?
Transmitted via Bacon
Yes. Bootlooder is unlock. Any solution for me. I upgrade to 05Q also wont solve the problem
Jerenk said:
Yes. Bootlooder is unlock. Any solution for me. I upgrade to 05Q also wont solve the problem
Click to expand...
Click to collapse
Are you saying that you flashed 05Q but it didn't help?
Transmitted via Bacon
timmaaa said:
Are you saying that you flashed 05Q but it didn't help?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes. I do OTA update to 05Q
Jerenk said:
Yes. I do OTA update to 05Q
Click to expand...
Click to collapse
How did you update?
Transmitted via Bacon
I update via OTA. Reboot into TWRP to install update. Is that what u asking for?
Jerenk said:
I update via OTA. Reboot into TWRP to install update. Is that what u asking for?
Click to expand...
Click to collapse
Yeah that was what I meant. Unfortunately I think you're going to need to wipe though because just installing the update doesn't fix the problem (corrupt data partition). I think you'll need to fully wipe your phone and start fresh. First you should copy any important photos, music, etc from your phone to your PC. Just connect your phone to your PC while you're in TWRP and you should be able to copy your media from the phone using Windows. Once you've done that, go to my guide thread and follow the instructions in section 8 to flash the stock images.
Transmitted via Bacon
My phone seem to be back to normal. Thank you. Any idea what cause it?
So it booted back up and ask your apps and settings were back to normal? That's really strange. I have no idea why/how that'd happen.
Transmitted via Bacon
timmaaa said:
So it booted back up and ask your apps and settings were back to normal? That's really strange. I have no idea why/how that'd happen.
Transmitted via Bacon
Click to expand...
Click to collapse
Yes it does. But Im planning to clean flash 05Q later today. Thanks again for support