Related
Just in case this post gets moved, I want to identify my device as the Verizon Samsung Galaxy S3 (i535).
To give a little background on my issue, I have an issue with the device. When I first got it back in July, first thing I did was root the device. Naturally, since it was a new device, I was working with experimental methods... a couple weeks ago I thought to download CyanogenMod 10.1 (nightly build) to flash it with 4.2 and rid myself of the persistent OTA update that as we all know could not effectively install because of the measures I took to root. So, I boot into recovery and flash my custom rom. BAM! As it turns out, I did not have an unlocked bootloader and my phone was now teetering on the verge of being a $600 paperweight. I got that dumb yellow triangle saying unofficial firmware detected or some nonsense like that... Anyway, I look around the internet and decided that I was going to revert back to a stock rom using Odin, and then proceed to unlock my bootloader and root the device (I followed method 3 here) I used some touch recovery console that I have never heard of before (backups incompatible with ClockworkMod recovery) and something must have failed because my back up would not flash. I took the hit on losing most everything and reflashed successfully the custom rom mentioned earlier.
After about a week, I noticed the device began to drop data. 4G would just stop at random parts of the day, and I would have to disable and enable the data to get it to reconnect. At this point I was still able to make and receive phone calls and texts. After about 3 days of this, I concluded it was more than likely a bug in the custom rom, and that I could not live with it... so I redid the a fore mentioned tutorial and left the phone as a stock/unlocked/rooted device. The data issue continued, but with a twist. I was now unable to make or receive phone calls or texts. No matter what I did, I could not do anything and the 4G would only stay connected for a matter 5 minutes or so. When I logged into my vzw account, it identified my device as an unknown non-verizon device. Customer service walked me through various soft/hard reset techniques and nothing worked. They also suggested I try a new SIM card, which failed to work.
So, I turn to the bright minds of the android community. I have already decided not to invoke the Verizon warranty offered, where the result is they take my malfunctioning phone in flawless cosmetic condition and replace it with a "like-new" phone in working condition, because I think it's garbage that a warranty would give out used crap (should fix or replace). I have not contacted Samsung customer support yet because I wanted to see what my options were. I've already attempted flashing different radios and nothing seem to make any difference. If I have to, I will revert it back to stock again and invoke Samsung's warranty program, but I would much rather keep the phone. As it sits, I am stuck with my Motorola Droid Razr Maxx, and that just doesn't cut it.
So I ask, is there anything that can be done? Anyone know of a fix for my situation? I saw something about this in my quest for an answer and I don't know if my situation is a fit for this fix. If anyone has any knowledge of my issue and a work around for it, it would be greatly appreciated. I am at my whits end.
It sounds like you've done your homework on your problem.. The only thing in your post I didn't see was your sim card.. Maybe pulling it wait 2min restart. Shut down and insert,, or maybe a reprovision of the sim may be in order..
Ahaaaa....!!!
If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.
HHF2 said:
If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.
Click to expand...
Click to collapse
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.
mkruluts said:
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.
Click to expand...
Click to collapse
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.
HHF2 said:
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.
Click to expand...
Click to collapse
Ok. So I tried the reprovsioning mentioned above. When my phone rebooted I was on data and able to make phone calls. Score! However, I checked the IMEI and it said 0. So, thinking that it was just a matter of time before my device began to stop working again... I did the IMEI fix. Now my phone is placing calls and holding data without issue. The OTA updates are flooding in and installing without issues.
I would like to point out, while I feel better having done the combination of both reprovisioning and IMEI fix, ultimately the initial reprovisioning did appear to resolve the issue.
Thanks to everyone for the assistance provided.
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.
Let me start by saying that I am not new to rooting and flashing firmware, its just been a while since I last did it. I've had a nexus 5 for a few months with sprint in the US. I continually have reception issues and dropped calls so I took the phone in to a store. Before I could do that I had to reset everything to stock. I had no trouble doing any of that. I made a complete backup of my ROM before I did all that using TWRP. I went to the store and they told me to turn off lte in order to reduce dropped calls. After the I got home I set to work re-rooting and unlocking my bootlaoder. However when I went to restore in TWRP it would not recognize the backup even though it had been made only a few hours before. I spent several hours trying to get TWRP to recognize the backup. Whenever I navigated to the directory containing the backup the directory was always empty. I even tried zipping the backup and flashing it but it did not work. Eventually I decided to cut my losses and move on. I plan on taking the phone back to sprint tomorrow because I still have horrible reception issues. I really want to avoid having to go through the whole ordeal again but I am not sure what I did wrong. The only thing I can think of is that immediately after making the backup I moved it off the device onto my laptop but did not modify it in any way. I had some experience with CWM back when I had my old HP touchpad but none with TWRP, however they don't seem that different. Any help is greatly appreciated.
UserNumberZero said:
Let me start by saying that I am not new to rooting and flashing firmware, its just been a while since I last did it. I've had a nexus 5 for a few months with sprint in the US. I continually have reception issues and dropped calls so I took the phone in to a store. Before I could do that I had to reset everything to stock. I had no trouble doing any of that. I made a complete backup of my ROM before I did all that using TWRP. I went to the store and they told me to turn off lte in order to reduce dropped calls. After the I got home I set to work re-rooting and unlocking my bootlaoder. However when I went to restore in TWRP it would not recognize the backup even though it had been made only a few hours before. I spent several hours trying to get TWRP to recognize the backup. Whenever I navigated to the directory containing the backup the directory was always empty. I even tried zipping the backup and flashing it but it did not work. Eventually I decided to cut my losses and move on. I plan on taking the phone back to sprint tomorrow because I still have horrible reception issues. I really want to avoid having to go through the whole ordeal again but I am not sure what I did wrong. The only thing I can think of is that immediately after making the backup I moved it off the device onto my laptop but did not modify it in any way. I had some experience with CWM back when I had my old HP touchpad but none with TWRP, however they don't seem that different. Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you put your backups in the correct sub-directory?
Should be something like: TWRP/BACKUPS/87095jgjg9034/nameofyourbackup
upndwn4par said:
Did you put your backups in the correct sub-directory?
Should be something like: TWRP/BACKUPS/87095jgjg9034/nameofyourbackup
Click to expand...
Click to collapse
Yes, I did. I even tried renaming the backup to "backup" and still had no luck.
Well, this is interesting. I went to Sprint today and they weren't much help but before I went there I reset everything back to stock. I made a backup yesterday and when I got home I put it on my phone and it was recognized immediately by TWRP and I was able to restore it. Not sure what I did wrong last time, if I did anything wrong at all.
UserNumberZero said:
Well, this is interesting. I went to Sprint today and they weren't much help but before I went there I reset everything back to stock. I made a backup yesterday and when I got home I put it on my phone and it was recognized immediately by TWRP and I was able to restore it. Not sure what I did wrong last time, if I did anything wrong at all.
Click to expand...
Click to collapse
Yeah, that's a bit odd. Glad you got it working now.
Sent from some device using XDA Premium mobile app
>> Partial solution was found; still looking for the root of the problem. <<
I recently decided to take the plunge and root my OnePlus One and install sultanXDA's CM 13 ROM on it. It was all going well until I booted up into the ROM and discovered that I couldn't get any mobile data. Everything else was working, calling, texting, wifi, but mobile data seemed to refuse to work. Since I initially flashed sultan's ROM with TWRP 3.0.0, I suspected it was a problem with my modem. Though unable to install TWRP 2.8.6.0 to re-flash everything, I did still flash a new modem via ADB. This didn't help.
I have tried many things to fix this. I rebooted/reflashed. I flashed different ROMs. I tried flashing on TWRP 2.8.6.1, though I believe that one has the same modem problem as the versions after it. As mentioned above I tried flashing a modem over ADB. I took out and re inserted my SIM card. In the end, I tried this guide here to restore my phone to it's original state. The guide flashes the stock versions of everything via ADB. Though it did return me to unrooted COS 12.1, it was not able to resolve my data problem.
After the total reset, all I can think that could be causing it is a hardware problem or that it is caused by something not reset in the 100% restore above.
If any of y'all can help my solve this, or at least offer insight, I would be very grateful.
Preemptive Edit I Guess: This thread was just suggested to me while writing this. I'm going to try the solution here and report back. It's OnePlus' reset to stock method. I'm not expecting much after my first 100% reset attempt, but we'll see.
EDIT: Ok, so the solution above fixed my problem... (edit again: turned out to only be a partial solution. See below.)
I would feel really dumb right now if it weren't for the fact that I slaved over this problem for a good ~8 hours before writing this post. Anyways, I'm not sure how to delete this post or mark it as solved. Sorry for the trouble y'all.
Never delete this post !!
I have the same problem, and I spent much more time to find a solution.
I will try this and will update.
Is it a clean stock rom?
Edit:
Didn't help for me ..
Still the same problem, No mobile internet connection.
Thx anyway.
Yeah, actually I was too hasty is identifying this as the solution. For me, the stock reset brought me back to CM 11 which didn't have a problem with mobile data. But if I try to flash a later ROM or update via OTA, the problem returns. I'm still trying to figure out what is causing it. The only information I can find points to it being a modem problem or APN problem, but I'm sure I have sufficiently checked both of those already.
Either way, I'll keep looking. If I find something I'll return here with it. Good luck
arkasa said:
Yeah, actually I was too hasty is identifying this as the solution. For me, the stock reset brought me back to CM 11 which didn't have a problem with mobile data. But if I try to flash a later ROM or update via OTA, the problem returns. I'm still trying to figure out what is causing it. The only information I can find points to it being a modem problem or APN problem, but I'm sure I have sufficiently checked both of those already.
Either way, I'll keep looking. If I find something I'll return here with it. Good luck
Click to expand...
Click to collapse
Try this:
1) Download the latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
2) Go here and follow step #8: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
3) Then follow step #2 to install a new recovery (you need to make sure to use TWRP 3.0.0 or the unofficial TWRP if you want to flash modems/firmwares correctly)
4) Download the latest ROM of your choice and install via your recovery
ryanmat said:
Try this:
1) Download the latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
2) Go here and follow step #8: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
3) Then follow step #2 to install a new recovery (you need to make sure to use TWRP 3.0.0 or the unofficial TWRP if you want to flash modems/firmwares correctly)
4) Download the latest ROM of your choice and install via your recovery
Click to expand...
Click to collapse
I gave this a try, but booting up after step 3 I still had the same problem. If I understand this method correctly, I think it is essentially the same as the other full restore methods I tried.
I think I may have found the problem though. I was looking at OnePlus' guide to installing OxygenOS. In it they said, "do not try to flash this build through TWRP. You will most likely lose your radio and IMEI which means a trip to our customer support." At this point I have repeatedly reset/restored my modem/radio so I don't think that is the problem, but I haven't seen anything about IMEI before. The IMEI is apparently stored in the EFS partition which as far as I can tell, is not touched by any of the restore methods I have tried. I took a look at my IMEI (about phone -> status) and it turns out my IMEI SV is 00. It's supposed to be a 16 digit number. I found a guide to fixing it, but I think I will just contact OnePlus customer support first.
I'll be back later with my results.
arkasa said:
I gave this a try, but booting up after step 3 I still had the same problem. If I understand this method correctly, I think it is essentially the same as the other full restore methods I tried.
I think I may have found the problem though. I was looking at OnePlus' guide to installing OxygenOS. In it they said, "do not try to flash this build through TWRP. You will most likely lose your radio and IMEI which means a trip to our customer support." At this point I have repeatedly reset/restored my modem/radio so I don't think that is the problem, but I haven't seen anything about IMEI before. The IMEI is apparently stored in the EFS partition which as far as I can tell, is not touched by any of the restore methods I have tried. I took a look at my IMEI (about phone -> status) and it turns out my IMEI SV is 00. It's supposed to be a 16 digit number. I found a guide to fixing it, but I think I will just contact OnePlus customer support first.
I'll be back later with my results.
Click to expand...
Click to collapse
Are you flashing each of the extracted .img files from fastboot, exactly like the guide shows, or are you doing something else?
ryanmat said:
Are you flashing each of the extracted .img files from fastboot, exactly like the guide shows, or are you doing something else?
Click to expand...
Click to collapse
Yep, I ran each command listed in the guide and my phone was definitely in fastboot. Each command had a collections of "OKAY"s and ended with a "finished", which I assume means it executed as expected.
I have tried 2 different sim cards in my OPO (of two different companies, one of them as mine), and mobile data worked perfectly. Is it possible that my phone is ok and the problem happened in the sim card?
AND... my IMEI SV is 00 too. please update here if it has a connection.
Thank you !
omersa99 said:
I have tried 2 different sim cards in my OPO (of two different companies, one of them as mine), and mobile data worked perfectly. Is it possible that my phone is ok and the problem happened in the sim card?
AND... my IMEI SV is 00 too. please update here if it has a connection.
Thank you !
Click to expand...
Click to collapse
I'm not entirely sure what you're saying. Did it not work with the first SIM card, but it worked with the second?
Mobile data problem was occured (to me), after I rooted my OPO and tried to flash a new rom.
I still can't understand how it convinced my sim card, but the fact is that I tried two (to be sure) other sim cards which are not mine, and mobile data worked well.
When I returned my original sim card, problem started again.
So I am almost sure that sim card has a connection, but can't understand why. And why it happend precisely now, cause it worked well over two years.
omersa99 said:
Mobile data problem was occured (to me), after I rooted my OPO and tried to flash a new rom.
I still can't understand how it convinced my sim card, but the fact is that I tried two (to be sure) other sim cards which are not mine, and mobile data worked well.
When I returned my original sim card, problem started again.
So I am almost sure that sim card has a connection, but can't understand why. And why it happend precisely now, cause it worked well over two years.
Click to expand...
Click to collapse
sorry to intrude...but looks like mine problem too...but no connection with provider at all...and it worked 1 month normal (stock opo)..
could u flash the modem to resolve this problem?
jpvr
http://forum.xda-developers.com/one...e-plus-one-t3030545/post65841063#post65841063
Why don't you flash twrp flashable modem?
If your network is present but no data , mostly data service problem. Are you pay your mobile bills ?
Are you activate data services ?
Try this
https://www.androidfilehost.com/?w=files&flid=28032
drmuruga said:
Why don't you flash twrp flashable modem?
If your network is present but no data , mostly data service problem. Are you pay your mobile bills ?
Are you activate data services ?
Try this
https://forums.oneplus.net/threads/cos-12-master-fix-thread.307446/
Click to expand...
Click to collapse
...yes i paid my bills ..
- my network connection to provider is dead...it worked perfecly for 1 month out of the box (see original posting for detailed action i took) this thread is about lack of data connection...but also MODEM related???
- tried the brand new simcard in my old Samsung sII... works perfetly, network connection with provider, data connection and calling..so no simcard problem
Long shot. Change any APN settings from IPv6 to IPv4. That was my problem when I had text/voice but no data.
I made a post on this and then called att gophone, due to seeing other sims working on this thread, and he helped me to fix. Posting my fix here in case others with isue find this post instead of mine.
Turned off wifi.
Turned off cellular data.
Went to APN and changed the apn (ATT Go Phone) from pta to nxtgenphone.
Turned on cellular data.
Finally had H+ above he signal bar, but had an X inside the bar.
Don't know if he did anything on his end, but the X went away after a couple of minutes.
Data was working, albeit kinda slow.
Turned off phone for three minutes per ATT rep.
Rebooted.
Data still slow, but it is at least working. Thinking I need to flash different modem. Battery usage has been higher the last day or two since I flashed c7 anyways.
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.