Database Info

[Q] Samsung Galaxy S3 Derp.

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.

Issues after cm13 flashing, infamous bootloop, and other festivities

Hi everyone.
Let's start from the beginning, and by advance excuse me for my poor English : I happen to be a delighted owner of the Oneplus One by the Oneplus company. I've flashed different versions of cyanogen on my phone, rooted it multiple times and I never encountered any kind of problems. Thus, until I decide yesterday to flash the latest release of cyanogen, cm13 (nightly). I did some researches, followed the usual steps, flashed the right opengapps version along with cm13 and.. everything went great. Except that my phone couldn't resolve himself to detect my SIM card anymore. I tried different things in order to solve the problem, including re-wipe the phone "factory reset" style, removing SIM card, wait for the phone to cool down and played with data roaming, but nothing worked. Fortunately I had my fresh nandroid backup waiting to be restored. That's when the real deal start :
even after having restored the full nandroid backup (which make me downgrade to cm12.1), the SIM card wasn't detected.
So I decided to wipe data, dalvik, cache and system, in order to get my phone back to its original state. But the problem remains, and worst of all, the phone now tends to reboot punctually without any reasons.
I surely did something wrong for the phone to end in this state, but I can't see what..
I use TWRP 2.8.7.0 custom recovery, and the phone OS is now cm12.1-YOG4PAS3JL.
Oneplus One 64GB.
Sorry for the length of the complaint, and by advance thanks for your answers.
P.S : I did tried to search for similar threads in the forum, but I didn't manage to found anything that was directly related.

It could be an issue with the modem not being flashed properly when you went from Lollipop to Marshmallow due to TWRP 2.8.7.0. Try TWRP 2.8.6.0, and then either restore the nandroid backup or clean wipe + reflash CM13 nightly.

oble said:
It could be an issue with the modem not being flashed properly when you went from Lollipop to Marshmallow due to TWRP 2.8.7.0. Try TWRP 2.8.6.0, and then either restore the nandroid backup or clean wipe + reflash CM13 nightly.
Click to expand...
Click to collapse
Thanks a lot for your response. I've been searching a lot and the problem effectively seems to be the modem not being flashed properly. So I tried to flash it manually, (found the file 2 threads higher, sorry I can't post links yet) via fastboot and then flashing cm13 (with twrp 2.8.6.0), considering the fact it seems to have worked for others.
But no matter what I do, the issue remains : the phone isn't able to detect SIM card and goes into crash, rebooting every 2mn..
I've tried to flash cm13 unnoficial version by sultan, following his instructions, but no improvement either.
Even my nandroid backup (running cm 12.1) can't detect SIM anymore, have serious wifi connectivity issues, and keeps rebooting randomly at very reguliar intervals..
I'm really beggining to feel hopeless,
but thanks again for your time and your advices, really apreciate it.

It seems that I have same problem..... after flashing CM13 and restoring backup
Any progress with this problem?
Edit - If my phone is connected into PC with USB cable it doesnt restarts

gersa said:
It seems that I have same problem..... after flashing CM13 and restoring backup
Any progress with this problem?
Edit - If my phone is connected into PC with USB cable it doesnt restarts
Click to expand...
Click to collapse
Same for me, the phone stops crashing and rebooting randomly once connected to pc via USB cable. But still doesn't recognize SIM card. Wifi also seems to work better.
No further progress unfortunately, I've tried everything, from restoring the phone to its factory state to flashing all "stable" roms (cyanogen), nothing worked.

MethylHaine said:
Hi everyone.
Let's start from the beginning, and by advance excuse me for my poor English : I happen to be a delighted owner of the Oneplus One by the Oneplus company. I've flashed different versions of cyanogen on my phone, rooted it multiple times and I never encountered any kind of problems. Thus, until I decide yesterday to flash the latest release of cyanogen, cm13 (nightly). I did some researches, followed the usual steps, flashed the right opengapps version along with cm13 and.. everything went great. Except that my phone couldn't resolve himself to detect my SIM card anymore. I tried different things in order to solve the problem, including re-wipe the phone "factory reset" style, removing SIM card, wait for the phone to cool down and played with data roaming, but nothing worked. Fortunately I had my fresh nandroid backup waiting to be restored. That's when the real deal start :
even after having restored the full nandroid backup (which make me downgrade to cm12.1), the SIM card wasn't detected.
So I decided to wipe data, dalvik, cache and system, in order to get my phone back to its original state. But the problem remains, and worst of all, the phone now tends to reboot punctually without any reasons.
I surely did something wrong for the phone to end in this state, but I can't see what..
I use TWRP 2.8.7.0 custom recovery, and the phone OS is now cm12.1-YOG4PAS3JL.
Oneplus One 64GB.
Sorry for the length of the complaint, and by advance thanks for your answers.
P.S : I did tried to search for similar threads in the forum, but I didn't manage to found anything that was directly related.
Click to expand...
Click to collapse
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short

gersa said:
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
Click to expand...
Click to collapse
Already saw it, but thanks ^^ that's where i found my file modemst.bin
so did it work for you ?

The same thing happened to me last week. I was using Materialized TWRP 2.8.7.0, which I think caused issues with my updating of Sultanxda's 13.1 ROM. SIM card was never detected, phone would restart shortly after every boot. I tried everything I could find to get my baseband and IMEI back.
In the end, only this solution worked for me, and I had to do it twice. I don't know why.

I had the same problem. I got back to TWRP 2.8.6.0 and then flashed the latest CM13(wiped System). after that without wipe i flashed sultans's CM13 then gapps and got the sim working again.

jp.esteban said:
The same thing happened to me last week. I was using Materialized TWRP 2.8.7.0, which I think caused issues with my updating of Sultanxda's 13.1 ROM. SIM card was never detected, phone would restart shortly after every boot. I tried everything I could find to get my baseband and IMEI back.
In the end, only [link] this solution[/URL] worked for me, and I had to do it twice. I don't know why.
Click to expand...
Click to collapse
Thanks for the link. I tried to flash the zip, but twrp(2.8.6.0) gave me an error : Error flashing ONEPLUS+ONE-FIX-Windows.zip
I tried to clean flash it and dirty flash it, nothing seems to work.

ashishsaggu said:
I had the same problem. I got back to TWRP 2.8.6.0 and then flashed the latest CM13(wiped System). after that without wipe i flashed sultans's CM13 then gapps and got the sim working again.
Click to expand...
Click to collapse
I've tried multiple times, it doesn't work. SIM card is not recognized, phones goes to reboot after 30s of use.
Whatever rom I flash the problem ain't solved, even after factory reset from original OS (cm 12.1)..
I really begin to think there is no solution, I've tried to flash my phone at least 20 times with different roms, fix, firmwares, modem, everything that is available on the net and I couldn't notice even the slightest change in the comportment of my phone.
Anyway, thanks a lot for your proposal, I guess it HAVE to work, but for some irrational reason it doesn't...

MethylHaine said:
I've tried multiple times, it doesn't work. SIM card is not recognized, phones goes to reboot after 30s of use.
Whatever rom I flash the problem ain't solved, even after factory reset from original OS (cm 12.1)..
I really begin to think there is no solution, I've tried to flash my phone at least 20 times with different roms, fix, firmwares, modem, everything that is available on the net and I couldn't notice even the slightest change in the comportment of my phone.
Anyway, thanks a lot for your proposal, I guess it HAVE to work, but for some irrational reason it doesn't...
Click to expand...
Click to collapse
Did U flash over TWRP or ADB?

Just popping in to say I have the same problem. I'm trying the various solutions presented in the thread and I'll come back and report if anything worked. I would also appreciate any other suggestions that you may have
For the record, I got into this predicament through the following steps:
1. I was flashing some CM nightly (sorry, I don't remember which one), and after reboot the touch screen didn't work anymore
2. I flashed the OxygenOs .zip that I had saved on internal storage through TWRP
3. After flash touch screen worked but no sim detected
4. Flashed CM 12.1 still no sim
5. Flashed back to OxyOs, still no sim. Curiously I am unable to reboot via software.
Anyway, I basically have all weekend to work on this, so awayyyy we go!
---
<Edit>
Wow that was fast. I followed this guy's instructions (fastboot flashing modemst, then CM12.1) and it seems to be working like a charm! Good luck everybody else!

gersa said:
Did U flash over TWRP or ADB?
Click to expand...
Click to collapse
I flashed via TWRP(2.6.8.0) and via ADB for modemst1.bin and modemst2.bin.
By the way, there's a little improvement : I flashed kalkulin's_stock_OPO Rom and that stopped my phone from rebooting.
Now cm13 is running kinda fine, except it still doesn't detect SIM card, even after reflashing modemst1 and modemst2
Edit : When I try to flash oxygenos, oneplus fix or cm12.1, (roms that are supposed to fix sim detection problem), it doesn't work : Error flashing Zip file. via adb or twrp, that's the same. (excepting the fact that error in adb is about trustzone)
I think my efs partition is somehow corrupt, and unfortunately i have no way to restore it.

MethylHaine said:
Thanks for the link. I tried to flash the zip, but twrp(2.8.6.0) gave me an error : Error flashing ONEPLUS+ONE-FIX-Windows.zip
I tried to clean flash it and dirty flash it, nothing seems to work.
Click to expand...
Click to collapse
It's not supposed to be flashed. Unzip the archive on a Windows PC, then use the .bat files in there to fix your phone.

jp.esteban said:
It's not supposed to be flashed. Unzip the archive on a Windows PC, then use the .bat files in there to fix your phone.
Click to expand...
Click to collapse
Effectively, I kinda did things completely wrong there, sorry. (I'm an exclusive linux user for my defense ^^)

Okay guys, I finally solved my problems.
Here's what I did to fix reboot crashes and SIM detection issues :
-Flash TWRP(2.8.6.0)
-Wipe everything except internal storage
-Flash Calkulin's_Stock_OPO_XNPH44S_ROM_v1.0.zip (can't post links yet, sorry)
-Boot system
-Once done, reboot to bootloader (in command prompt : sudo adb reboot bootloader)
-In command prompt, type the following commands (It will delete modem and /persist partition ! be careful) :
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
-If you need to fix "Unable to mount /persist" error in TWRP :
adb shell
make_ext4fs /dev/block/mmcblk0p15
-Flash Oxygen OS (i flashed oxygen_1.0.0_flashable.zip)
That should restore EFS and fix the issues.
Well, that was kind off a pain in the ass, but now my problem is solved, and i'm currently running cm13 quite fine.
Make a backup of your EFS partition.
Thanks to all the people that helped me by posting in this thread !

It's a nightly build, it bound to have some problems.

i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops
---------- Post added at 03:08 AM ---------- Previous post was at 03:07 AM ----------
gersa said:
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
Click to expand...
Click to collapse
i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops

Samsung Tab 2 10.1 (CM11) unable to wipe/factory reset/install CM update

I have been routinely flashing CM 11 ROMs on nightly basis since the past year without any problems. However, the last Nightly I installed started giving me errors like xyz.process.com stopped etc etc. So, I decided to wipe everything through my TWRP recovery by wiping cache, data, internal storage (I have done this before for a clean install many times), but this time even when I wipe EVERYTHING and flash the latest nightly and the Gapps, the tablet boots into the same old version. I have done this repeatedly but with no success.
The strange thing was that when I even tried uninstalling individual apps, like I installed Whtsapp, Viber, Twitter, a few games, they did get uninstalled but on the next reboot, all the apps were back?! How is it even possible?!
Steps I have done to resolve this issue:
1-Flashed the newer ROM, nothing changed.
2-Tried wiping everything to no avail.
3-Tried flashing stock ROM like 20 times via Odin but it always fail midway.
4-Tried flashing Philz recovery via Odin, it succeeds but when I reboot in recovery, the same old TWRP recovery is there.
5-Tried flashing newer TWRP recovery via img file by booting into recovery,finding the img file and flashing it, it also succeeds but when I reboot into recovery, it still boots into the older TWRP recovery.
6-Tried flashing newer TWRP via Odin, it too succeeds but when I reboot into recovery, the old version is still there.
I mean, anything I do, the system wont change/wipe. Please help!

16gb Tab2?
Sounds like a emmc issue,maybe a emmc firmware update is needed to get back right access to your tab, in bad case the emmc needs a replacement. If you are from europe: i know someone from austria who can fix it for you. Added some notes about that issue on the faq on my github userpage.

Can you install https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check and post a screenshot of it?
~ All my work, news etc. on http://andi34.github.io ~

I tried install the app but was unable to as the gapp.google.com stop working thing wont let me. So I tried installing it through the web, it didnt install but the tab rebooted and is now stuck at boot. Wont shut down either

How to fix the emmc issue? Update? I m far away from Europe

Rag888 said:
How to fix the emmc issue? Update? I m far away from Europe
Click to expand...
Click to collapse
Update the emmc firmware (only via ISP possible) or replace the emmc. Maybe you can find someone who's able to do it...

Android-Andi said:
Update the emmc firmware (only via ISP possible) or replace the emmc. Maybe you can find someone who's able to do it...
Click to expand...
Click to collapse
Via ISP? Pleas explain. And are we sure that this is am emmc problem? Because I can boot and use the tab to some extent, it's not totally bricked I guess. What about the procedure here: http://forum.xda-developers.com/galaxy-tab-2/general/discussion-alternative-tab-2-emmc-bug-t3306862

Rag888 said:
Via ISP? Pleas explain. And are we sure that this is am emmc problem? Because I can boot and use the tab to some extent, it's not totally bricked I guess. What about the procedure here: http://forum.xda-developers.com/galaxy-tab-2/general/discussion-alternative-tab-2-emmc-bug-t3306862
Click to expand...
Click to collapse
I am not an expert on this, someone else would have to explain it if you have further questions about ISP etc.
I am quite sure it's the problem, if wipe / format does nothing and flash via odin also doesn't change anything... Your emmc is read only...
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
Click to expand...
Click to collapse
On a faulty EMMC firmware it happens a lot faster.
There's no way to boot from microSD, you would need to flash a modified boot.img at least which is imposible if the emmc is read only.
~ All my work, news etc. on http://andi34.github.io ~

Thanks for your input. Well, Odin is able to write the recoveries to the Tab, and shows that they are pass, doesnt that mean it is still writing? Also, Odin attempts to write the stock firmware but fails half way, I also also suspect a faulty cable. And should I try the procedure given in the link I quoted?
I am also downloading the Jtag suite like here: http://forum.gsmhosting.com/vbb/f672/p5100-how-repair-2118618/

Ok, I just saw your website https://andi34.github.io/faq_de.html I think I am screwed.

OnePlus One... I'm pretty sure I messed up my EFS partition.

UPDATE:
I have baseband wifi and bluetooth back but my IMEI is still showing up as 0 and no signal. I know the phone is reading the sim because I can see the phone number saved on the sim info.
Also getting "OEM_NV_Backup The NV Partition is invalid!" when I boot OxygenOS
Does anyone know where I can get 16GB installs for ColorOS and OxygenOS? I have a 16GB phone but when I use the msm download tool to install ColorOS I end up with a 64GB install.

Do you have any backup for the EFS partition?

I had same problem about EFS partition and No IMEI too. So I am almost sure that flashing completely untouched official Oxygen OS downloaded straight from official site will solve your problem as it did mine. Just download "Build" from here (oneplus forum) and flash it with latest TWRP. After that you'll get your fully working network connectivity back. Then just flash any other ROM you like, but look for perfect modem first (c6 works best in Asia and c7 rest of the world, but try both if you want). All the best :fingers-crossed::good:

SaurabhMumbaiOneS said:
I had same problem about EFS partition and No IMEI too. So I am almost sure that flashing completely untouched official Oxygen OS downloaded straight from official site will solve your problem as it did mine. Just download "Build" from here (oneplus forum) and flash it with latest TWRP. After that you'll get your fully working network connectivity back. Then just flash any other ROM you like, but look for perfect modem first (c6 works best in Asia and c7 rest of the world, but try both if you want). All the best :fingers-crossed::good:
Click to expand...
Click to collapse
gonna try that now, should I take any other steps before flashing in twrp like wiping anything?

so I tried installing oxygen through twrp but I was getting error 7 (phone is marked as A0001 and install is marked for OnePlus). I tried using the files and instructions from the oxygen 2.14 thread and somehow my phone hard bricked lol, I've learned so much about this phone in the last 2 months.
Gonna throw ColorOS on there and try going straight to OxygenOS from there.

So I had to wipe everything (system, cache, etc) before twrp let me install oxygen. I got oxygen installed but now it loops in oneplus screen and I got this issue come up after installation finished

Some more progress... was able to install oxygen os finally and it look like I'm almost done coming back from this nightmare. Baseband is back, WiFi and Bluetooth work, now just need to see about restoring my iemi, I've found some info on how to restore imei so I'll try that tomorrow sometime after waking up. I've learned so much about this damn phone! !

My bottom screen has also stopped working. The replacement screen you brought from, it is original or clone?? How does it feel to the screen when you buyed the phone from your friend. And i hope you'll get back your imei too

Rex2688 said:
My bottom screen has also stopped working. The replacement screen you brought from, it is original or clone?? How does it feel to the screen when you buyed the phone from your friend. And i hope you'll get back your imei too
Click to expand...
Click to collapse
It's not original. Screen is fine the only downside to non oem front assembly is that that capacitive buttons will not be as bright, some have reported that they don't light up at all, seems to be luck of the draw.

intehweeds said:
Some more progress... was able to install oxygen os finally and it look like I'm almost done coming back from this nightmare. Baseband is back, WiFi and Bluetooth work, now just need to see about restoring my iemi, I've found some info on how to restore imei so I'll try that tomorrow sometime after waking up. I've learned so much about this damn phone! !
Click to expand...
Click to collapse
As I can see from your screenshot from previous reply, you are not using official ROM. Completely official ROM is named as "OnePlus_Bacon_OxygenOS_201601190107". There was no need to wipe internal storage. Use this guide to modify the updater script. It worked for me perfectly. Then flash it and just boot into ROM. I was able to recover everything including IMEI number by this method.
And yeah, I feel the same way. I've learned so much from our beloved Bacon :laugh:

intehweeds said:
Some more progress... was able to install oxygen os finally and it look like I'm almost done coming back from this nightmare. Baseband is back, WiFi and Bluetooth work, now just need to see about restoring my iemi, I've found some info on how to restore imei so I'll try that tomorrow sometime after waking up. I've learned so much about this damn phone! !
Click to expand...
Click to collapse
You have baseband so your imei is back

yet another update
installed oxygenos with twrp, I have baseband wifi and everything but no data signal and my IMEI is 0
I've hit yet another wall :crying:
Why isn't there a 16GB version of ColorOS and OxygenOS? When I install ColorOS via msm download tool I end up with a 64GB install, I think this might be causing my "OEM_NV_Backup The NV partition is invalid!" issues as well.
Just need to resolve those two issues, bad nv partition and my IMEI being 0
Anybody know where I can get a 16GB version of colorOS, I have a feeling I overlooked something I was supposed to tweak

giaur said:
You have baseband so your imei is back
Click to expand...
Click to collapse
That's what I thought but my IMEI still shows up as 0

I don't understand why you are not flashing official Oxygen OS even after saying it solved each and everything for me?? And since it is official, it is bound to support 16 GB variant as well.

http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Ok, so the link I posted should be a last resort. You will find a recovery tool that I used when my IMEI would not return correctly. Follow all instructions, but do note that this will completely wipe everything, and if I remember correctly, that includes all personal files. The tool should land you back on the original software (like CM11S). I say try EVERYTHING else people tell you first before doing this. You're essentially starting over your phone. Good luck!
EDIT: Your recovery will be stock as well.

SaurabhMumbaiOneS said:
I don't understand why you are not flashing official Oxygen OS even after saying it solved each and everything for me?? And since it is official, it is bound to support 16 GB variant as well.
Click to expand...
Click to collapse
I did flash the official one. I used the link from the oneplus page that takes me to a forum post. At first I wasn't able to do it with twrp but afterwards I was able to
I did it once with the tool they provided and a second time through twrp, imei still 0

Inflection said:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Ok, so the link I posted should be a last resort. You will find a recovery tool that I used when my IMEI would not return correctly. Follow all instructions, but do note that this will completely wipe everything, and if I remember correctly, that includes all personal files. The tool should land you back on the original software (like CM11S). I say try EVERYTHING else people tell you first before doing this. You're essentially starting over your phone. Good luck!
EDIT: Your recovery will be stock as well.
Click to expand...
Click to collapse
done this already and still IMEI is 0

intehweeds said:
done this already and still IMEI is 0
Click to expand...
Click to collapse
Aww, I'm sorry man. Best of luck finding a solution.

What should I backup?

Hello, I have been struggling with an issue in my moto e5. I unlocked bootloader & installed custom roms. Then I thought I should go back to the stock rom & I did so. But after booting up, mobile data doesn’t work (No service). Auto rotation doesn’t work. Also it can't detect when I pick up my phone. But in custom roms, there is no issue like this! I flashed stock rom using rescue and smart assistant tool. I also did flash using fastboot commands batch file. But the issue persists.
Next I found that imei is lost in stock rom. So I installed custom rom, backed up "efs" from twrp, installed stock rom & restored the efs. I got my imei numbers back! But no service and auto rotation issue is still there along with other disabled sensors.
What else should I backup and restore? Or what should be my next steps?

One always backs up the whole Stock Andoid before flashing anything. Only blue-eyed people do not.

jwoegerbauer said:
One always backs up the whole Stock Andoid before flashing anything. Only blue-eyed people do not.
Click to expand...
Click to collapse
Yeah,, my bad..