So stupid me. I've had a Nexus S and a Galaxy S2. I should've known better. However, in my defense I've only run into EFS problems once on my Nexus S and never on my S2. In proper ROM flashing it never becomes an issue.
Up til now I had been doing well. But I guess it has to do with the recent addition by CM to include modems in the ROMs also that causes trouble? TWRP seems to have trouble restoring them. To make a long story short, I was trying to bug test for CM by going back nightly by nightly from 0913 and backwards. Once I isolated the bug, I tried to restore back to my TWRP 0913 backup.
Well what happened upon restore? No signal. No IMEI. No WiFi. Well Crap. No EFS backup.
Steps I have taken to try to restore:
Tried this fix: http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Tried flashing Calkulin's 33R Rooted http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph33r-t2855276
But no dice. I've noticed that my root folder just does not have an EFS folder. I'm not even sure what to do. Am I SOL? Do I just need to return the phone? The worst part is my Nexus 5 is out on RMA as of YESTERDAY (wow timing?).
Question to those who managed to restore their EFS, was your EFS folder somewhat intact? Mine was completely gone. Not sure if anyone can help me here.
Update 9/15:
I flashed Unofficial TWRP 2.7.0.1 and performed a restore of the TWRP backup. It seems that WiFi and Bluetooth can work. Bluetooth and WiFi Mac addresses show. However, IMEI is still empty.
When I reboot its gone.
So I've gotten closer, but no mobile connectivity yet.
I'm not sure whats missing!!! Agh.
First thing have you searched the forum. You are not the first and there have been success stories. You should be searching through here looking for them Instead of waiting for them to come to you. Search man search and I hope you get it done good luck..
playya said:
First thing have you searched the forum. You are not the first and there have been success stories. You should be searching through here looking for them Instead of waiting for them to come to you. Search man search and I hope you get it done good luck..
Click to expand...
Click to collapse
I did search. I showed you links to the threads I found and the solutions I tried. I'm reporting that I've had no luck with those that people claim success with. I'm also asking for more information here because I'm saying that my EFS folder is completely nonexistent (compared with my GS2 for example).
I'm trying to understand what everyone else's situation was because there's even in the threads with success stories, people just say "wow it worked." Done. No more info.
dmo580 said:
I did search. I showed you links to the threads I found and the solutions I tried. I'm reporting that I've had no luck with those that people claim success with. I'm also asking for more information here because I'm saying that my EFS folder is completely nonexistent (compared with my GS2 for example).
I'm trying to understand what everyone else's situation was because there's even in the threads with success stories, people just say "wow it worked." Done. No more info.
Click to expand...
Click to collapse
That was not up when I responded you have since edited your post but its ok I see you are in other threads trying to fix it. I am seeing colorOs, I read where someone reflashed stock rom then flashed radio and it worked.
Edit: Do you have another nandroid you can possibly restore?
playya said:
That was not up when I responded you have since edited your post but its ok I see you are in other threads trying to fix it. I am seeing colorOs, I read where someone reflashed stock rom then flashed radio and it worked.
Edit: Do you have another nandroid you can possibly restore?
Click to expand...
Click to collapse
The posts were there. I only edited the post becuase it said "Lots EFS" and not "Lost."
As for what else I've tried, I have since tried flashing the stock ROM using the 33R ZIP from CyanogenMod. Using Fastboot it basically wipes all your partitions and repartitions everything. No dice. No IMEI still.
I have only 1 Nandroid. Its 5gb so I don't usually make multiple. I actually have Online Nandroid Manager usually keep 2, but since 2.8.0.1 just dropped that day I did a NEW backup prior to going to an older CM ROM. As a result of new backup, I deleted the older ones to save space.
Stupid me. But either way I think the restore feature just screws things up. I never used the unofficial TWRPs to make EFS backups because I'm more scared of unoffical recoveries. I should've just done it anyway. Ugh.
dmo580 said:
The posts were there. I only edited the post becuase it said "Lots EFS" and not "Lost."
As for what else I've tried, I have since tried flashing the stock ROM using the 33R ZIP from CyanogenMod. Using Fastboot it basically wipes all your partitions and repartitions everything. No dice. No IMEI still.
I have only 1 Nandroid. Its 5gb so I don't usually make multiple. I actually have Online Nandroid Manager usually keep 2, but since 2.8.0.1 just dropped that day I did a NEW backup prior to going to an older CM ROM. As a result of new backup, I deleted the older ones to save space.
Stupid me. But either way I think the restore feature just screws things up. I never used the unofficial TWRPs to make EFS backups because I'm more scared of unoffical recoveries. I should've just done it anyway. Ugh.
Click to expand...
Click to collapse
I used the script to back mine up... Well I am always looking around so if I see anything I will let you know
Sent from my A0001 using Tapatalk
playya said:
I used the script to back mine up... Well I am always looking around so if I see anything I will let you know
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yeah good idea. What script BTW if you don't mind sharing.
I should've been more aware, but somehow I figured "its not a Samsung" so I wasn't careful enough.
dmo580 said:
Yeah good idea. What script BTW if you don't mind sharing.
I should've been more aware, but somehow I figured "its not a Samsung" so I wasn't careful enough.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=54623075&postcount=81
Update 9/15:
I flashed Unofficial TWRP 2.7.0.1 and performed a restore of the TWRP backup. It seems that WiFi and Bluetooth can work. Bluetooth and WiFi Mac addresses show. However, IMEI is still empty.
When I reboot its gone.
So I've gotten closer, but no mobile connectivity yet.
I'm not sure whats missing!!! Agh.
dmo580 said:
Update 9/15:
I flashed Unofficial TWRP 2.7.0.1 and performed a restore of the TWRP backup. It seems that WiFi and Bluetooth can work. Bluetooth and WiFi Mac addresses show. However, IMEI is still empty.
When I reboot its gone.
So I've gotten closer, but no mobile connectivity yet.
I'm not sure whats missing!!! Agh.
Click to expand...
Click to collapse
I lost EFS on my S3. I assume you know that EFS is a partition? I had to to type in commands (via ADB or a shell on your phone) to set the permissions and make them stick. This way, when you reboot it stayed.
I half guess that it's something along similar lines.
Ok, EDIT..here is my post relating to S3.
Originally Posted by kocweb
Here is the exact solution for this problem which i have recently had!
You have to root your phone and install Terminal Emulator from Google Play.
Open terminal emulator and type as ;
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
You now should not see the that message anymore. Its because of an EFS corruption. ( Thanks to yesilcin*com (sawgent) ) for exact solution.
Hope it helps!!!
Click to expand...
Click to collapse
dmo580 said:
Update 9/15:
I flashed Unofficial TWRP 2.7.0.1 and performed a restore of the TWRP backup. It seems that WiFi and Bluetooth can work. Bluetooth and WiFi Mac addresses show. However, IMEI is still empty.
When I reboot its gone.
So I've gotten closer, but no mobile connectivity yet.
I'm not sure whats missing!!! Agh.
Click to expand...
Click to collapse
ok so now flash the Color OS that people say seem to help when you get to that point or try flashing stock rom and radio like others have said worked
playya said:
ok so now flash the Color OS that people say seem to help when you get to that point or try flashing stock rom and radio like others have said worked
Click to expand...
Click to collapse
Yeah so i tried flashing both after my recovery and with stock I get WiFi and BT. Reboot and its gone
With ColorOS it doesn't work.
Hang in there guys I think I found a fix. On my way home to prepare a permanent fix for absolutely everything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
markbencze said:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Click to expand...
Click to collapse
As you may know, I have already tried your method and its no good.
Other things I've tried:
Flashing ColorOS 1.20, 2.18, no go
Flashing the factory image of 33R, 38R
Flashing my supposed backup of modemst1, modemst2, but I suspect they are corrupted because they were corrupted when I accidentally restored modem in TWRP
So what's interesting is when I do flash the factory image of 38R with the flashall.bat, upon initial boot, Wifi does work. However, after a reboot, it goes away.
Does anyone think they can help me figure out why that happens and if I can just keep WiFi around at the very minimum?
Edit: I think I'm a special case because most people have just seen reboot loops or persist partition corruption which is easily fixed by flashing the backup persist or the persist in that other thread. However, the issue here is I think what triggered my issue was somehow TWRP offered an option to restore the modem partition (I'm guessing it was TWRP trying to restore an Online Nandroid Backup which by default includes the modem partition). As a result, my modem likely got screwed.
However the fact that I can get WiFi on a first boot after a factory flash leads me to think maybe I'm not all screwed? Even if my IMEI is lost forever, I'll accept that, but if I can get a WiFi only device, that would still be sweet?
dmo580 said:
As you may know, I have already tried your method and its no good.
Other things I've tried:
Flashing ColorOS 1.20, 2.18, no go
Flashing the factory image of 33R, 38R
Flashing my supposed backup of modemst1, modemst2, but I suspect they are corrupted because they were corrupted when I accidentally restored modem in TWRP
So what's interesting is when I do flash the factory image of 38R with the flashall.bat, upon initial boot, Wifi does work. However, after a reboot, it goes away.
Does anyone think they can help me figure out why that happens and if I can just keep WiFi around at the very minimum?
Edit: I think I'm a special case because most people have just seen reboot loops or persist partition corruption which is easily fixed by flashing the backup persist or the persist in that other thread. However, the issue here is I think what triggered my issue was somehow TWRP offered an option to restore the modem partition (I'm guessing it was TWRP trying to restore an Online Nandroid Backup which by default includes the modem partition). As a result, my modem likely got screwed.
However the fact that I can get WiFi on a first boot after a factory flash leads me to think maybe I'm not all screwed? Even if my IMEI is lost forever, I'll accept that, but if I can get a WiFi only device, that would still be sweet?
Click to expand...
Click to collapse
If nothing is working why not just RMA?
All opo come with 1 year warranty
Thanks for the reminder to back up my EFS!
Did anyone manage to find a fix for lost imei
Same thing happened to me yesterday, restored a nandroid, and efs disappeared
Tried flashing full stock, no result
Phone comes on, reboots after a minute
IMEI,bt, wifi mac id,baseband=unknown
Had any luck fixing it?
Looks like I'm in the same boat too.
I have tried everything discussed in this thread and more, to no avail.
Watching this thread closely
Related
First I'd like to say hello to all. I've been looking for the most comprehensive android discussion forum, and I think I hit the jackpot here. Anyway to the point. As it is known by the pros here, The S3 comes from your telecom company loaded with your personal connection info. From what I've read recently, the carriers either don't know how, or simply wont backup the nv and efs data to the onboard chips to preserve it in case of software failure, or mod failure. I did find an article with google explaining that a couple of devs discovered the fix for this inside the bootloader that we can use to force that backup to happen like it should, and it works. I've flashed several times since that backup and not lost the data from the phone. When I install cyanogen mod 11, it does not read those 2 particular memory blocks on booting, thus cyanogenmod does not recover the imei data from the onboard backup, even after a factory reset. I really would like to see if there is a workaround for that because unfortunately for me, any other method for backup is illegal where I live. If I flash back to stock rom, It reads the data back out of the chip, and restores my connection data for the carrier to the efs partition as well as the other 3 displayed in EFS Backup Pro. But I really like cyanogenmod, and since one of it's developers worked at Samsung, I'm really hoping my question finds an answer here.
So my question is is anyone familiar enough with the Cricket version of the S3 and cyanogenmod to tell me of a workaround for that problem if it exists. Thanks in advance for the community's responses.
Did You used the "cricket" Version of cyanogenmod?
Sent from my loved HTC One S using buggy Tapatalk 0.o
LS.xD said:
Did You used the "cricket" Version of cyanogenmod?
Sent from my loved HTC One S using buggy Tapatalk 0.o
Click to expand...
Click to collapse
I used the cyanogenmod installer to install. From what I've read, the universal installer detects my phone and installs the correct version. Also I think that all s3 builds are now unified, so that's not an issue. Tried 10.2 after that, and caused my self more problems than I needed to fix, so I flashed back to stock. But I am going to attempt the mod again after backing up efs and nv if I have to. I can only run 4.3 or 4.4 android, which means I can only run 10.2 or 11 on my phone, or it will nuke the bootloader and hard brick my phone.
Corny007 said:
I used the cyanogenmod installer to install. From what I've read, the universal installer detects my phone and installs the correct version. Also I think that all s3 builds are now unified, so that's not an issue. Tried 10.2 after that, and caused my self more problems than I needed to fix, so I flashed back to stock. But I am going to attempt the mod again after backing up efs and nv if I have to. I can only run 4.3 or 4.4 android, which means I can only run 10.2 or 11 on my phone, or it will nuke the bootloader and hard brick my phone.
Click to expand...
Click to collapse
http://download.cyanogenmod.org/?device=d2cri
Sent from my loved HTC One S using buggy Tapatalk 0.o
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
This is the cricket Version
Sent from my loved HTC One S using buggy Tapatalk 0.o
Versions are correct. Its not a version problem, it's an implementation problem where cm10.2 or 11 does not read the memory blocks that store the eps and nv data. Stock rom from cricket will read them and restore nv data from the chips. (I am not referring to the efs folder that can be seen as root. Im referring to the data stored in the 2 chips that Samsung and Cricket don't tell you about. Normally a corrupted efs folder is backed up from there because no one backs it up first. Google "Samsung derp" and you will find the article I found that explains this. People lose their efs because they don't know this about the knox system, and that it's not backed up properly. When you do not do " su nvbackup" then you lose your number. You do he nv backup procedure correctly and it backs up your current efs, then it's automatically restored whenever you flash a rom that reads those blocks. Cyanogenmod does NOT read those blocks to rebuild the efs/nv data. If it did, then when I do the factory reset after flashing, my phone would work right after the reset, but it does not. Neither version 10.2 nor 11.x reads those blocks.on reboot.
Corny007 said:
Versions are correct. Its not a version problem, it's an implementation problem where cm10.2 or 11 does not read the memory blocks that store the eps and nv data. Stock rom from cricket will read them and restore nv data from the chips. (I am not referring to the efs folder that can be seen as root. Im referring to the data stored in the 2 chips that Samsung and Cricket don't tell you about. Normally a corrupted efs folder is backed up from there because no one backs it up first. Google "Samsung derp" and you will find the article I found that explains this. People lose their efs because they don't know this about the knox system, and that it's not backed up properly. When you do not do " su nvbackup" then you lose your number. You do he nv backup procedure correctly and it backs up your current efs, then it's automatically restored whenever you flash a rom that reads those blocks. Cyanogenmod does NOT read those blocks to rebuild the efs/nv data. If it did, then when I do the factory reset after flashing, my phone would work right after the reset, but it does not. Neither version 10.2 nor 11.x reads those blocks.on reboot.
Click to expand...
Click to collapse
Looked at this already? --> Backup + Restore EFS SIII
I'm not sure how, but I'm up and dialing.
LS.xD said:
Looked at this already? --> Backup + Restore EFS SIII
Click to expand...
Click to collapse
Sorry I didn't get back here. I have an update. Corny007 1, Samsung Galaxy S3 0. I won :highfive: The first time I installed cyanogen I did it with the installer, and like I said, the blocks weren't read. Not sure how or why yet as I'm just starting out, but I did about 2 or 3 days research, kept hitting dead ends, so I decided just to go back and use the installer again. For some reason, and I still have no idea why, as I mentioned my IMEI data would not restore. This time, it did, no backing up required. I do have them just in case, except I never went through the trouble to get them onto my Ext/SD, and I couldn't figure out how to work around version mismatches after Philz was overwritten. I could have installed the SDK, and took a couple more days probably to get it that way, but for some reason, that I still don't know, maybe it was a bugfix between last time and this, not sure. Bottom line is I am modded, and calling. Thanks for the suggestions, I'll hit the thanks button too. By the way, I never answered your question. I did look where you recommended. It just seemed like I was the one exeption to everything I found. EFS Pro for example couldn't make the .tar file, just little headaches like that. Thanks again.
So, I unlocked bootloader of my N5. Flashed CWM Touch. Didn't make any kinda backup (I know I'm stupid) and flashed paranoid android. Now I'm not getting any signals on it. Please, I'm in need of desperate help. Any solutions?
EDIT:
Flashed stock image, good as new This should help people who are as stupid as me
Do the usual flash cache.img first. Failing that, reflash all stock images
Sent from my Nexus 5 using Tapatalk
Hello,
Did you wipe data/factory reset, cache, dalvic cache before flashing PA rom.zip?
IF not, then head over to recovery and wipe everything.. Now flash pa.zip and gapps.zip and finally reboot...
Just flashing the pa rom won't touch the efs...
rootSU said:
Do the usual flash cache.img first. Failing that, reflash all stock images
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Trying this
vin4yak said:
Hello,
Did you wipe data/factory reset, cache, dalvic cache before flashing PA rom.zip?
IF not, then head over to recovery and wipe everything.. Now flash pa.zip and gapps.zip and finally reboot...
Just flashing the pa rom won't touch the efs...
Click to expand...
Click to collapse
But, I did not wipe data/factory reset..I went into mounts and storage and wiped everything except sd-card
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
7alvi said:
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
Click to expand...
Click to collapse
Not yet, flash the factory image. That'll get you to a like new condition.
Sent from my Nexus 5
7alvi said:
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
Click to expand...
Click to collapse
Go to your custom recovery and wipe everything (data/cache/dalvic)... Now flash the rom.zip and gapps.zip and finally reboot and see whether you're able to get a signal or not?
OR
You could use this guide to return to full stock and check... http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
jd1639 said:
Not yet, flash the factory image. That'll get you to a like new condition.
Sent from my Nexus 5
Click to expand...
Click to collapse
I'm flashing the stock image as of now. But, how will it restore my efs partition? By wiping everything in recovery in mounts and storage, didnt i wipe it too?
7alvi said:
I'm flashing the stock image as of now. But, how will it restore my efs partition? By wiping everything in recovery in mounts and storage, didnt i wipe it too?
Click to expand...
Click to collapse
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
rootSU said:
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
7alvi said:
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
Click to expand...
Click to collapse
The 2 lines is are normaly
Try again with admin rights
7alvi said:
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
Click to expand...
Click to collapse
That could be because you extracted the image-hammerhead xxxxx.zip file. dont extract it. it should be there like it is on this picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rootSU said:
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I officially pronounce this phone as un-brickable. Yes it's fixed. IMEI, baseband siganls everything is back... @rootSU I owe you a beer man. I can't emphasize how ****lessly scared I was...thanx a lot!
No worries
Sent from my Nexus 5 using Tapatalk
Just pumping this thread.
I've gone through a few steps but have ran into a snag.
Heres the synopsis;
My device was randomly shutting down while charging so I decided to factory reset to see if that helped.
When I did the the device entered a boot loop and when I went into recovery it would say can't mount cache etc.
I tried re flashing 5.0.1 Lrx22c but again it got stuck in a boot loop.
I managed to flash 4.4.4 and the device finally turns on.
The only problem is that the phone appears to be without any network connection. Google playstore cannot open and crash's and so does the camera and gallery applications. Adding a sim card does nothing to help.
I'm not sure how to fix this problem and I'm at a point where I need to ask for help. I'm Canadian and bought the device through one of our providers, Rogers, and am starting to think that there is a specific set of 'roger' img's that I need to flash and not the ones from the developers site.
Any input would be much appreciated.
Bump bump ^^
There is no such thing as carrier specific factory images. Did you try reflashing the radio, or a different radio? Remove and reinsert Sim? Might be hardware issue otherwise ..
Sent from my Nexus 5 using Tapatalk
At my wit's end.
I realize it's been 2 weeks since you posted but, in the hope that you are subscribed still Radioman66, I'm curious if you did ever manage to fix/reinject your IMEI; I'm Canadian too btw, though I bought my Nexus 5 through Google Play. I've tried flashing stock everything: bootloader, radio, boot, system, cache, userdata via fastboot; only then did my phone reboot properly, but it still has a habit of crashing/rebooting every so often. No IMEI & no cellular reception thus far, so I can only conclude that there is some data corruption at play here. Fortunately it was easy to find my unique IMEI via a sticker on the inside of the back cover of my Nexus 5, for those who aren't aware.
So I'm in the opinion that the issues of bootloops and my IMEI corruption (dialling *#06# on the dialer calls up a bold IMEI header but no number whatsoever) first occurred when my battery drained to zero. I was using a custom rom at the time, Optipop Dark Deodex with f2fs formatted data and cache partitions, + Multirom & multirom compatible TWRP. I'm at a loss for why the EFS partition and thus IMEI would even be accessed by the phone for writing/reading or how a corruption of the partition could even occur. Perhaps I was receiving a text message right at that very moment it turned off? Perhaps f2fs is to blame, who really knows...main thing is my IMEI is corrupted and I'm left with a smart brick, it being no longer a smart phone.
Anyway, long story short it's been like 2 days of searching around but I think this free tool "Setup DFS 15.01.17.0.zip" at cdmatool dot com (can't post link as a newbie so replace dot with a period) may be the real deal; it's possible to download it without registering i.e. demo mode ( which makes you wait tens of seconds between operations). Despite my general comfort with adb, fastboot, cmd tools in general, the CDMAtool's manual is full of stuff and acronyms I don't really know about yet, like COM Ports and what not but I'm hoping to soon understand this tool and will report back my failures/successes. If anyone would be kind enough to perhaps walk me through what I would need to do, I'd be super thankful!!!t
Welp, cheers to not even knowing about the existence of ESN/EFS/IMEI before this unfortunate juncture LMAO--I will definitely make sure to backup my EFS partitions before flashing custom roms from now on...
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
CafeKampuchia said:
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
Click to expand...
Click to collapse
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
dreamerguy00 said:
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
Click to expand...
Click to collapse
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
blackbird5308 said:
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
Click to expand...
Click to collapse
Sorry wrong thread
Sent from E.P.D.Center
I had the same weird problem last night.....
Except my recovery was also reverted to stock.
it happened after i got notifed about an update available couple days in a row which i canceled.
I even have Droidwall and everything but a few apps are blocked from data usage.
What i would suggest is to freeze the ""system update" system app.
I kinda have a feeling the OTA updates have something to do with it.
This happend to me 1 other time a while back with an HTC One X device. Same pattern, System update notifications then couple days of ignoring .... then pooffff...
blackbird5308 said:
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Click to expand...
Click to collapse
I updated my Oneplus One manually to the newest Version of CM12s. While flashing it, my Recovery (TWRP) chrashed. So to be sure I installed my freshly performed Nandroid Backup. But nothing helped. I couldnt connect with the Wifi, no SIM Cards were found, no Bluetooth Connectivity and it had Random Reboots. So i decided to flash back to Stock CM11s (the first ever released). But the Problems were the same afterwards. I flashed the Stock image via ADB and, after I found out nothing changed, via the Oneplus One Toolkit, but the Problems were still there. I also made a video on Youtube to show what happens and i hope that i can repair it and must not send it back to repair, because a repair would cost me up to 300€. So pls tell me a way to fix this Problem, because I really like this Phone:crying::crying::crying:
For the video search "Oneplus One not working" by the User "axel thegamer"
AxelWexel said:
I updated my Oneplus One manually to the newest Version of CM12s. While flashing it, my Recovery (TWRP) chrashed. So to be sure I installed my freshly performed Nandroid Backup. But nothing helped. I couldnt connect with the Wifi, no SIM Cards were found, no Bluetooth Connectivity and it had Random Reboots. So i decided to flash back to Stock CM11s (the first ever released). But the Problems were the same afterwards. I flashed the Stock image via ADB and, after I found out nothing changed, via the Oneplus One Toolkit, but the Problems were still there. I also made a video on Youtube to show what happens and i hope that i can repair it and must not send it back to repair, because a repair would cost me up to 300€. So pls tell me a way to fix this Problem, because I really like this Phone:crying::crying::crying:
For the video search "Oneplus One not working" by the User "axel thegamer"
Click to expand...
Click to collapse
Can't find your video, can you paste the link as text?
gsmyth said:
Can't find your video, can you paste the link as text?
Click to expand...
Click to collapse
i cant, because i made a new account here.
just search "oneplus one not working", then set "filter" on today and you will find it
AxelWexel said:
i cant, because i made a new account here.
just search "oneplus one not working", then set "filter" on today and you will find it
Click to expand...
Click to collapse
Ok found your vid, I see you have flashed the stock image files via ADB, have you done a full factory reset (wiping data) from the phone/TWRP? Its a bit worrying that flashing the stock image files didnt sort the issue. As it seems to be WiFi on/off that causes the reboot it would make me think it was to modem/radio but this should have been written again when you flashed the stock images.
@AxelWexel can you check in your Settings>About phone menu if your IMEI number is showing? Just in case your EFS has become corrupted. It definitely sounds fixable as if something has corrupted and needs wiped fresh.
EFS fix:
http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Also worth a shot, fixing corrupt partitions guide in ADB:
http://forum.xda-developers.com/oneplus-one/general/guide-identifying-fixing-corrupted-t2993500
gsmyth said:
Ok found your vid, I see you have flashed the stock image files via ADB, have you done a full factory reset (wiping data) from the phone/TWRP? Its a bit worrying that flashing the stock image files didnt sort the issue. As it seems to be WiFi on/off that causes the reboot it would make me think it was to modem/radio but this should have been written again when you flashed the stock images.
@AxelWexel can you check in your Settings>About phone menu if your IMEI number is showing? Just in case your EFS has become corrupted. It definitely sounds fixable as if something has corrupted and needs wiped fresh.
EFS fix:
http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Also worth a shot, fixing corrupt partitions guide in ADB:
http://forum.xda-developers.com/oneplus-one/general/guide-identifying-fixing-corrupted-t2993500
Click to expand...
Click to collapse
Thx for the Links and i tried to watch on my phone and there is no imei number. I also did a full wipe after i found the issues. I also tried it via the Toolbox to flash the stock rom back but it hadnt change anything. But I will look the links you postet and reply if anything has changed. But now thx again:good:
P.S: I renamed the Video to "Oneplus One not working (23.06.2015)" to find it more easily
Edit 1: The Second Link with fixing corrupt partitions via adb wont work for me because i dont have root but my bootloader is unlocked. so i cant find the root acsess for adb in the developer options
Edit 2: I installed color os like the link said, done everything it said, but still no wifi, bluetooth and no sim card detection:crying:. Luckily the random reboot stopped Could you again help me further more because it seemed to help
Edit 3: I went back to cm11s, because in color os when i turned the phone off it turned on again, the connectivity was not there. After the install it became worse with the random reboots. I think i must send it to repair and pay 300€:crying::crying::crying::crying:
Good day everybody,
I am a proud owner of a modified Motorola Photon Q. It is my replacement of my well beloved Xperia Pro (in which the flex-cable between screen and board was too fragile).
I recieved the phone, and it had Cyanogenmod 12.1 on it, with working wifi etc. So it was good and well. Except, I like to start from completely 0 myself and choose my own most stable Cyanogenmod possible.
So I flashed a new recovery (twrp 2.7.1.2) and put the zip file of a snapshot from Cyanogenmod (12.1) on my SD.
No trouble on the recovery flash through fastboot, no trouble on formatting everything wih recovery and no trouble installing the .zip package. 0 errors during the entire process.
However, after the installation the wifi nor bluetooth go on. I tried flashing other stable/snapshot versions from Cyanogenmod but none seems to make my wifi actually work the way it should.
I am getting stuck here, does anybody have any idea's for me? This issue is happening on 10.2, stable and 12.1 both snapshot versions.
Any help would be highly appreciated.
Flash stock with RSD Lite. Make sure everything works on stock before moving to anything custom.
Good luck.
arrrghhh said:
Flash stock with RSD Lite. Make sure everything works on stock before moving to anything custom.
Good luck.
Click to expand...
Click to collapse
Thank you for these tips.
I will give this a try, though it is my first time ever with RSD.
What if it does work with RSD? Will this change behaviour towards Cyanogenmod?
M_w_B said:
Thank you for these tips.
I will give this a try, though it is my first time ever with RSD.
What if it does work with RSD? Will this change behaviour towards Cyanogenmod?
Click to expand...
Click to collapse
Possibly. You should always start with stock, and know how to get back to stock on any device you are going to flash with aftermarket firmwares. You need to ensure there are no hardware issue with the device before proceeding with anything aftermarket.
arrrghhh said:
Possibly. You should always start with stock, and know how to get back to stock on any device you are going to flash with aftermarket firmwares. You need to ensure there are no hardware issue with the device before proceeding with anything aftermarket.
Click to expand...
Click to collapse
Well I am sure there are no hardware issues.
When I recieved the phone, it had Cyanogenmod 12.1 with wifi and bluetooth working. I, myself, like to start from 0 So I emptied the entire thing and re-flashed twrp and cyanogenmod 12.1 (snapshot).
From then on it did not work anymore, no matter which recovery or Cyanogenmod (only snapshot or stable) I try.
RSD is new to me, I am used to my Xperia Pro whoes stock kernel was an img on an XDA main ROM/stock list.
I do not have the stock ROM/kernel, since the phone was already modified at its receive.
arrrghhh said:
Possibly. You should always start with stock, and know how to get back to stock on any device you are going to flash with aftermarket firmwares. You need to ensure there are no hardware issue with the device before proceeding with anything aftermarket.
Click to expand...
Click to collapse
From most stock files the link is dead towards its download. Do you have any suggestions perhaps?
M_w_B said:
...
I recieved the phone, and it had Cyanogenmod 12.1 on it, with working wifi etc.
...
no trouble on formatting everything wih recovery
...
after the installation the wifi nor bluetooth go on
...
Click to expand...
Click to collapse
I'm pretty sure that the issue is in the "no trouble on formatting everything" bit.
In recovery, you've erased your /persist partition.
As its content is unique for each device, it won't get restored by flashing a stock firmware via RSD Lite. That partition is not included in FXZs.
Specifically, you've lost your /persist/WCNSS_qcom_wlan_nv.bin and /persit/.bt_nv.bin files which are essential for working WIFI and BT. Among other stuff, they contain your device's unique MAC addresses for WIFI and BT.
You can check the content of your /persist folder. If it's empty, it confirms my suspicion.
To fix it, you will need to restore your /persist partition from your backup. If you haven't made a backup before erasing, you will need someone to provide you with his own personal backup of /persist. Then your and his device will use the same, no longer unique MACs...
kabaldan said:
I'm pretty sure that the issue is in the "no trouble on formatting everything" bit.
In recovery, you've erased your /persist partition.
As its content is unique for each device, it won't get restored by flashing a stock firmware via RSD Lite. That partition is not included in FXZs.
Specifically, you've lost your /persist/WCNSS_qcom_wlan_nv.bin and /persit/.bt_nv.bin files which are essential for working WIFI and BT. Among other stuff, they contain your device's unique MAC addresses for WIFI and BT.
You can check the content of your /persist folder. If it's empty, it confirms my suspicion.
To fix it, you will need to restore your /persist partition from your backup. If you haven't made a backup before erasing, you will need someone to provide you with his own personal backup of /persist. Then your and his device will use the same, no longer unique MACs...
Click to expand...
Click to collapse
I believe you have made my issue clear, I am very thankfull for that!
I can't find my /persist folder in Cyanogenmod 12.1 Snapshot which I am currently running.
kabaldan said:
To fix it, you will need to restore your /persist partition from your backup. If you haven't made a backup before erasing, you will need someone to provide you with his own personal backup of /persist. Then your and his device will use the same, no longer unique MACs...
Click to expand...
Click to collapse
There are obviously more data there. Do you know what data it is?