Related
I tried to install the latest and greatest version of cyanogenmod this morning but once it got to the activating part, it would not activate. I tried it a couple times, rebooted, wiped, installed and tried again, but nothing was working.
So, I had enough and wiped everything and restored my previous ROM's backup (CleanROM).
But now, even CleanROM can't connect to the mobile network. When I try to do the *228 thing, I first got an error something about a invalid SIM card. So, I rebooted and now the error message says "A Verizon Wireless SIM card has activated your service and updated your phone's roaming capabilities".
What's weird about that is that it doesn't even call, just pops up that message and I still have no network!
Could it be possible that have the wrong radio now? Anyone know what it's supposed to be and where to download the correct one?
Right now: I535VRLG7
What the f happened? What did cyanogenmod do to my phone??? Please help, my phone is dead in the water at this point.
Was it 10.1.0.1? I tried flashing it myself and data would not work either, first time ever happened to me since running CM. Apparently others are having issues with it as well reading the thread on the dev section. I restored my backup of 10.1.0 and it was fine again thankfully. Also you aren't supposed to *228 on a 4G phone, might want to do a search but others have said that can mess up your phone as well.
NeoMagus said:
Was it 10.1.0.1? I tried flashing it myself and data would not work either, first time ever happened to me since running CM. Apparently others are having issues with it as well reading the thread on the dev section. I restored my backup of 10.1.0 and it was fine again thankfully. Also you aren't supposed to *228 on a 4G phone, might want to do a search but others have said that can mess up your phone as well.
Click to expand...
Click to collapse
Yes, that's the version I was trying to install.
I created a backup of CleanROM that I was running before flashing, but that's not working now either. Network is dead for me.
I am having the exact same issue. Flashed the newest "stable" build of CM 10 and now the phone won't activate. Flashed CM10 RC5 and phone won't activate. Installed my backup I made before I flashed and it will not make/receive calls either. I tried searching the g+ community but did not see anything.:crying:
Jerniganc said:
I am having the exact same issue. Flashed the newest "stable" build of CM 10 and now the phone won't activate. Flashed CM10 RC5 and phone won't activate. Installed my backup I made before I flashed and it will not make/receive calls either. I tried searching the g+ community but did not see anything.:crying:
Click to expand...
Click to collapse
I've tried a bunch of stuff so far, but no luck fixing this. I'm waiting for some files to copy and I'm going to try again. This sucks. I'll post if I have any luck with a fix.
I'm having the same issue. What Baseband are you guys running?
Laxidasical said:
I'm having the same issue. What Baseband are you guys running?
Click to expand...
Click to collapse
I'm on I535VRBMB1, but I was on I535VRLG7 for some reason. Upgrading did not help.
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
I hope I don't have to do that also. I posted in the cm g+ community and I'm waiting on an answer atm. Jumped in irc chat but got no help.
Sent from my Nexus 7 using xda premium
---------- Post added at 06:48 PM ---------- Previous post was at 06:36 PM ----------
ned4spd8874 said:
I've tried a bunch of stuff so far, but no luck fixing this. I'm waiting for some files to copy and I'm going to try again. This sucks. I'll post if I have any luck with a fix.
Click to expand...
Click to collapse
ned4spd8874 said:
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
Click to expand...
Click to collapse
Found this post on G+. Looks like it is a known issue that a radio didn't make it into the build.
https://plus.google.com/110116306685366816729/posts/2wnDGwd9UtX
Jerniganc said:
Found this post on G+. Looks like it is a known issue that a radio didn't make it into the build.
https://plus.google.com/110116306685366816729/posts/2wnDGwd9UtX
Click to expand...
Click to collapse
But I've flashed the radio and it didn't work for me. I tried two different ones and neither worked.
ned4spd8874 said:
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
Click to expand...
Click to collapse
No need to take your phone back to verizon.....The way to fix it is to Odin back to I535VRALF2. Once stock dial *2767*3855# let it do it's thing when it finishes reboot. After that 4G will be back. Re root and flash CM 10.1.0 NOT 10.1.0.1
Well an update on this. I flashed MIUIv5 found here http://forum.xda-developers.com/showthread.php?t=2232800 and it booted up and worked like a champ. From there I booted back into CWM and wiped, etc and installed a fresh RC5 and gapps. When the phone booted up the phone would take calls but would force close. From here I booted back into CWM, again wiped and then installed my RC5 backup I made this morning that was working and crossed my fingers. Well when the phone booted up it is working 100%!
I guess my question is what did 10.1.0.1 break that a flash to MIUIv5 fix?
Same issue. I had to wipe everything, format everything (maybe wasn't needed), flashed the newest nightly, latest baseband (something something F1), and gApps of course. I then had to check the "mobile network" settings and change it to SIM card (instead of NV) then reboot, and it worked.
The "stable" builds have been less stable than the nightlies lately, dunno why...
i'm also having this issue guys, I've noticed that my imei is 0. I've tried punching in the codes to get the utility, but can't get anything working...totally lost
RESOLVED!
It was a PITA, but I got 4G back with CM!
This is how I did it, but be forewarned that your device will be wiped, and it will not be a quick fix.
I first used this post (Section 5) to Odin back to stock.:
http://forum.xda-developers.com/showthread.php?t=1762709
Once I was back to stock, the network was still not working. So I dialed "*2767*3855#", it did something, rebooted and then 4G worked!
After that, I was able to follow the same guide from above (Section 1) to root the device, unlock the bootloader and install a recovery.
Once I was at that point, I installed CM from recovery. I had wanted to install the cm stable version 10.1.0, however I failed to copy that to my SD card before I started this whole process.
I had just moved and don't have many of my "tools" (i.e. sd adapters), so I couldn't even download it on my computer and copy it over. Oh, I also performed a factory wipe at this point as well as format the davlik and system...oops. So, yeah, couldn't simply boot it back up easily to copy the files over...got ahead of myself.
Anyways, I kept my fingers crossed and installed the only one that was on the sd card which was the nightly from 6/29. The good news is that worked!
I have since installed the latest nightly (6/30), because why the heck not? I was already on the previous, so it "shouldn't" hurt, right????
Nope, didn't hurt!
So, now I am running the latest nightly with full network access!
Whew, what a pain! Hope this helps you guys!
ned4spd8874 said:
RESOLVED!
It was a PITA, but I got 4G back with CM!
This is how I did it, but be forewarned that your device will be wiped, and it will not be a quick fix.
I first used this post (Section 5) to Odin back to stock.:
http://forum.xda-developers.com/showthread.php?t=1762709
Once I was back to stock, the network was still not working. So I dialed "*2767*3855#", it did something, rebooted and then 4G worked!
After that, I was able to follow the same guide from above (Section 1) to root the device, unlock the bootloader and install a recovery.
Once I was at that point, I installed CM from recovery. I had wanted to install the cm stable version 10.1.0, however I failed to copy that to my SD card before I started this whole process.
I had just moved and don't have many of my "tools" (i.e. sd adapters), so I couldn't even download it on my computer and copy it over. Oh, I also performed a factory wipe at this point as well as format the davlik and system...oops. So, yeah, couldn't simply boot it back up easily to copy the files over...got ahead of myself.
Anyways, I kept my fingers crossed and installed the only one that was on the sd card which was the nightly from 6/29. The good news is that worked!
I have since installed the latest nightly (6/30), because why the heck not? I was already on the previous, so it "shouldn't" hurt, right????
Nope, didn't hurt!
So, now I am running the latest nightly with full network access!
Whew, what a pain! Hope this helps you guys!
Click to expand...
Click to collapse
Yes, this just worked for me..however I look to be roaming completely when still in Stock
luniz7 said:
No need to take your phone back to verizon.....The way to fix it is to Odin back to I535VRALF2. Once stock dial *2767*3855# let it do it's thing when it finishes reboot. After that 4G will be back. Re root and flash CM 10.1.0 NOT 10.1.0.1
Click to expand...
Click to collapse
This worked for me.
Thanks!
I'm on vacation and tried to flash 10.1.0.1 and got hosed on the the radio connection. Nothing would work. Found an old nightly, 6/21 I believe, on my external SD card. Flashed that bad boy and I'm up and running again. Will do more trouble shooting when I get home in a few weeks and have my PC in front of me.
Sent from my SCH-I535 using Tapatalk 2
Back to RC5
I had a similar issue, upgraded to 10.1.01 and lost all data connectivity. Wiped clean and tried to upgrade again, then I could not get past the network activation screen.
Wiped and went back to a backup of RC5 and it restarted with less issues, but I still needed to go and correct the Mobile Network RUIM/SIM settings before I got data back.
RC5 has been solid, so I'm going to stick to it until there's a fix for 10.1.01.
this didnt work for me
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
If you encrypted your device they only solution to decrypt is to factory reset.
Sent from my HTC6525LVW using Tapatalk
You need to search around here. This is a documented issue with aosp ROMs. Someone put out a command line fix (i think it's in the noon-carrier-specific m8 forum) or you can use the ruu files found in this forum.
electric turd said:
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
Click to expand...
Click to collapse
i just sent in my phone after this same issue i had tried the newest nightly from CM and flashed fine ran through the whole set up process then found out my bluetooth dont work so i restored my most recent bak booted my phone up and i get a message to put in my password that i have never set up
electric turd said:
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
Click to expand...
Click to collapse
I have had this twice now, i fixed it by formatting data in twrp then factory resetting and restoring a backup from my sd. I lost all my internal storage.
factory reset dont work either sorry were both S.O.L. unless u have insurance then just "loose ur phone"
I'm back guys!!!!! I ruu'ed in fastboot. Weird thing was when my phone booted back up it still had supersu!!!!!! That made me happy. I then flashed twrp through flashify and restored a back up I made before this whole fiasco. Thanks again for everything!!!!
So you returned your phone to Verizon over this? If it turns on you can fix it.
electric turd said:
I'm back guys!!!!! I ruu'ed in fastboot. Weird thing was when my phone booted back up it still had supersu!!!!!! That made me happy. I then flashed twrp through flashify and restored a back up I made before this whole fiasco. Thanks again for everything!!!!
So you returned your phone to Verizon over this? If it turns on you can fix it.
Click to expand...
Click to collapse
mine turns off right after it boots dosent matter where it boots to
skcitzo said:
i just sent in my phone after this same issue i had tried the newest nightly from CM and flashed fine ran through the whole set up process then found out my bluetooth dont work so i restored my most recent bak booted my phone up and i get a message to put in my password that i have never set up
Click to expand...
Click to collapse
So you sent in a phone that you broke and that can be fixed but are too lazy to research? And this is why companies lock down bootloaders. If you cant do basic searching, then dont root your phone.
This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
apcake said:
This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
Click to expand...
Click to collapse
Uhhhmmmm would flashing the modems help? (directed towards the more knowledged users)
Sent from my SCH-I535 using XDA Free mobile app
poppers162 said:
Uhhhmmmm would flashing the modems help? (directed towards the more knowledged users)
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
It might. It depends on what modem they are currently on
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
apcake said:
This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
Click to expand...
Click to collapse
First thing I would do is make sure your imei is still present in the about phone section. If it is, move on to the next step.
I would go completely back to stock, Odin flash either the stock 4.3 or 4.4 image depending on which you were on. If you're unsure, post what it says in download mode.
If you do that and you still have no service, then go to verizon and get a new sim card. Flashing a new modem wouldn't fix this situation.
BadUsername said:
First thing I would do is make sure your imei is still present in the about phone section. If it is, move on to the next step.
I would go completely back to stock, Odin flash either the stock 4.3 or 4.4 image depending on which you were on. If you're unsure, post what it says in download mode.
If you do that and you still have no service, then go to verizon and get a new sim card. Flashing a new modem wouldn't fix this situation.
Click to expand...
Click to collapse
it appears as though the sim was wiped
apcake said:
it appears as though the sim was wiped
Click to expand...
Click to collapse
Grab a new sim card.
what i did so far. used odin to flash h1 baseband rom so i can root. rooted with cydia. downloaded e-z recovery. installed cwm. that didnt read my storage and nothing in it would work. installed twrp with e-z recovery. same problem.(edit: when I got to twrp it said "no o.s. found" so I then had to reboot into download mode and flashed the stock rom) Then downloaded android terminal emulator. downloaded cwm and installed by typing in the commands. got into cwm and made a backup. wiped data, cache, dalvik. tried to install "cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte". it installed but went into a boot loop and would end up back at cwm every time. wiped data, factory reset, restored backup. tried again, same thing, restored again. tried installing "cm-12.1-20150915-NIGHTLY-d2vzw" this time. it got stuck saying "patching system image unconditionally.....". wiped data, restored stock, tried again this time with "cm-10.0.0-d2vzw". it didnt even install. now im restoring again to stock.
the reason im trying vzw roms also is because i have a verizon note 2 on straight talk and was gonna try to use that sim card in my s3.
http://forum.xda-developers.com/galaxy-s3-verizon/help/straight-talk-sch-s986c-t3036314/page3
^^this thread has some info about it but im new here and havent found anything else about it. before i try getting it to work with my verizon cdma sim card i at least would like to just get cyanogenmod working on my s3.
am i using the wrong roms? is this in the right forum?
thanks
now supersu is gone from my phone. i just installed es file explorer and checked allow root permissions and supersu didnt even come up. i uninstalled and reinstalled in the play store also and nothing happened
cory733 said:
now supersu is gone from my phone. i just installed es file explorer and checked allow root permissions and supersu didnt even come up. i uninstalled and reinstalled in the play store also and nothing happened
Click to expand...
Click to collapse
You need the d2vzw ROMs, if you are using lollipop then you need to go to developer options and turn on root access, set it to apps and adb.
There is a TWRP made specifically for d2tfnvzw, it has our source code in it, the other d2vzw TWRPs don't mount our devices correctly.
I worked with a dev at OctOS to get our device fully supported, all their d2vzw stiff has our code in it now. I can link you to the TWRP if you have trouble finding it.
I know pretty much whatever you need on this phone, just hit me up with anything you need help with and I'll get you straight.
Have you backed up your IMEI in terminal emulator yet, I recommend doing so because this phone has a habit of losing IMEI when flashing back and forth between ROMs, flashing stock tar won't fix this.
Droidriven said:
You need the d2vzw ROMs, if you are using lollipop then you need to go to developer options and turn on root access, set it to apps and adb.
There is a TWRP made specifically for d2tfnvzw, it has our source code in it, the other d2vzw TWRPs don't mou t our devices correctly.
I worked with a dev at OctOS to get our device fully supported, all their d2vzw stiff has our code in it now. I can link you to the TWRP if you have trouble finding it.
I know pretty much whatever you need on this phone, just hit me up with anything you need help with and I'll get you straight.
Have you backed up your IMEI in terminal emulator yet, I recommend doing so because this phone has a habit of losing IMEI when flashing back and forth between ROMs, flashing stock tar won't fix this.
Click to expand...
Click to collapse
hey droid thanks for getting back to me. i cant find the twrp for the d2tfnvzw, just the d2vzw. were you saying that i could use the d2vzw because it has the straight talk code in it or i need the exact straight talk version? yes if you have the link i would appreciate it because i didnt see anything except the d2vzw. how would i install it with cwm already on there? would it just overwrite it?
i had no idea about backing up imei until today. but this is already after installing the h1 rom and getting it rooted. then trying cm 4 different times. if my info was lost, would it just be blank? or would it have different numbers that are just useless to me. because its still there but i didnt write down the numbers before i did all this. but anyway today i think thats what i did, ive done so much with this phone that i cant even remember exactly, but i opened up terminal emulator, typed in something involving rebootnv/ something and it rebooted then i copied the efs folder from my phone and put a copy on my computer.
i just did another restore of the first backup i made. supersu is still gone. i downloaded my android tools and it says that supersu was still an enabled app. i never hid it or disabled it in any way that im aware of. i tried uninstall and reinstall from play store and the terminal emulator command and the #*#* numbers on the phone dialer. nothing. es file manager also got root access without supersu coming up.
also it seems like its not getting 3g at all. usually it goes from 3g to just 2 bars or one bar where i live. but now its just steady at two bars. even with wifi off. does 3g stop showing up if the phone is not in service? i dont remember.
btw this phone has android 4.1.2
cory733 said:
hey droid thanks for getting back to me. i cant find the twrp for the d2tfnvzw, just the d2vzw. were you saying that i could use the d2vzw because it has the straight talk code in it or i need the exact straight talk version? yes if you have the link i would appreciate it because i didnt see anything except the d2vzw. how would i install it with cwm already on there? would it just overwrite it?
i had no idea about backing up imei until today. but this is already after installing the h1 rom and getting it rooted. then trying cm 4 different times. if my info was lost, would it just be blank? or would it have different numbers that are just useless to me. because its still there but i didnt write down the numbers before i did all this. but anyway today i think thats what i did, ive done so much with this phone that i cant even remember exactly, but i opened up terminal emulator, typed in something involving rebootnv/ something and it rebooted then i copied the efs folder from my phone and put a copy on my computer.
i just did another restore of the first backup i made. supersu is still gone. i downloaded my android tools and it says that supersu was still an enabled app. i never hid it or disabled it in any way that im aware of. i tried uninstall and reinstall from play store and the terminal emulator command and the #*#* numbers on the phone dialer. nothing. es file manager also got root access without supersu coming up.
also it seems like its not getting 3g at all. usually it goes from 3g to just 2 bars or one bar where i live. but now its just steady at two bars. even with wifi off. does 3g stop showing up if the phone is not in service? i dont remember.
btw this phone has android 4.1.2
Click to expand...
Click to collapse
If you want a working TWRP then you'll need the d2tfnvzw version, any d2vzw or d2lte ROM should work fine for you.
If you lose IMEI it won't show in settings. The reboot nvbackup that you did in terminal emulator was the IMEI backup I mentioned, it sounds like you did it correctly, if it gets wiped out for whatever reason then you can restore it by typing "reboot nvrestore", it is saved in a safe place on internal that won't get wiped out between flashes and wipes unless you format internal memory, it will be erased if you do that. As long as the only format options you use are to format system and data partitions then you won't have to worry about losing the NV backup, don't format anything other than system and data, do not format internal SD and you'll be fine. If you ever have to restore the NV backup then you'll have to create a new one like the first time because restoring it erases it from where the backup was kept, to stay backed up after restoring you need to make another.
SuperSU won't show as an app, its built in to system settings.
Did you enable root access in system settings>developer options? It has to be set to " apps and adb" or the device will act like it isn't rooted. When you flashed in CWM and rebooted it should have prompted you to "fix root", select yes if it does.
Yes, the 3G disappears when you don't have service and need to renew time on the device.
Here is the TWRP for d2tfnvzw
https://plus.google.com/+DonaldHoskins/posts/FLdc2CkSHRu
Flash it in CWM then go to the advanced options in CWM and select "reboot to recovery" this will boot you straight from CWM into TWRP, then make your backup and youll keep TWRP and wont need CWM, it would be a good idea to restore your stock nandroid in CWM and boot into it then boot back to CWM then flash the TWRP then reboot into it then make a nandroid of your stock in TWRP because TWRP will not restore CWM nandroids, doing what I just instructed allows you to keep TWRP and a stock nandroid that you can actually restore. After getting TWRP and a stock nandroid in TWRP you can delete the CWM backup from your internal SD if you aren't going back to CWM at any time, you won't need it if you do as I instructed.
Droidriven said:
You need the d2vzw ROMs, if you are using lollipop then you need to go to developer options and turn on root access, set it to apps and adb.
There is a TWRP made specifically for d2tfnvzw, it has our source code in it, the other d2vzw TWRPs don't mou t our devices correctly.
I worked with a dev at OctOS to get our device fully supported, all their d2vzw stiff has our code in it now. I can link you to the TWRP if you have trouble finding it.
I know pretty much whatever you need on this phone, just hit me up with anything you need help with and I'll get you straight.
Have you backed up your IMEI in terminal emulator yet, I recommend doing so because this phone has a habit of losing IMEI when flashing back and forth between ROMs, flashing stock tar won't fix this.
Click to expand...
Click to collapse
Droidriven said:
If you want a working TWRP then you'll need the d2tfnvzw version, any d2vzw or d2lte ROM should work fine for you.
If you lose IMEI it won't show in settings. The reboot nvbackup that you did in terminal emulator was the IMEI backup I mentioned, it sounds like you did it correctly, if it gets wiped out for whatever reason then you can restore it by typing "reboot nvrestore", it is saved in a safe place on internal that won't get wiped out between flashes and wipes unless you format internal memory, it will be erased if you do that. As long as the only format options you use are to format system and data partitions then you won't have to worry about losing the NV backup, don't format anything other than system and data, do not format internal SD and you'll be fine. If you ever have to restore the NV backup then you'll have to create a new one like the first time because restoring it erases it from where the backup was kept, to stay backed up after restoring you need to make another.
SuperSU won't show as an app, its built in to system settings.
Did you enable root access in system settings>developer options? It has to be set to " apps and adb" or the device will act like it isn't rooted. When you flashed in CWM and rebooted it should have prompted you to "fix root", select yes if it does.
Yes, the 3G disappears when you don't have service and need to renew time on the device.
Here is the TWRP for d2tfnvzw
https://plus.google.com/+DonaldHoskins/posts/FLdc2CkSHRu
Flash it in CWM then go to the advanced options in CWM and select "reboot to recovery" this will boot you straight from CWM into TWRP, then make your backup and youll keep TWRP and wont need CWM, it would be a good idea to restore your stock nandroid in CWM and boot into it then boot back to CWM then flash the TWRP then reboot into it then make a nandroid of your stock in TWRP because TWRP will not restore CWM nandroids, doing what I just instructed allows you to keep TWRP and a stock nandroid that you can actually restore. After getting TWRP and a stock nandroid in TWRP you can delete the CWM backup from your internal SD if you aren't going back to CWM at any time, you won't need it if you do as I instructed.
Click to expand...
Click to collapse
thanks for the link and info, ill work on that next. this phone actually never had an IMEI. not even behind the battery. it just has a 2 line section called MEID that shows a Dec and a Hex number. i give one or both of these numbers to straight talk when they activate the phone. (had this phone activated,deactivated and reactivated a couple times)
i had supersu as an app because i installed it from the play store. it was showing before and i use it on my note 2. but now the pop up for granting superuser permission isnt even coming up.
since i cant just switch the sim cards between my two phones, is it even worth putting a verizon rom on my s3? i would still have to call straight talk and have it switched anyway. or is that because the d2lte roms dont work for mms.. is that the only reason to use the verizon roms instead? you said before in pm that if i put my note 2s sim in my s3(after installing verizon rom) that i would have to press *228 to reset the prl. and that might mess it up for the note 2 that im using. would i just have to repeat dialing *228 in my note 2 if i switched the sim back to that one? also i believe you said in a different thread that theres no way to get 4g on these phones? that was also one of my reasons for wanting to put a verizon rom on the s3. basically this phone is a backup that has just become a learning experiment now
cory733 said:
thanks for the link and info, ill work on that next. this phone actually never had an IMEI. not even behind the battery. it just has a 2 line section called MEID that shows a Dec and a Hex number. i give one or both of these numbers to straight talk when they activate the phone. (had this phone activated,deactivated and reactivated a couple times)
i had supersu as an app because i installed it from the play store. it was showing before and i use it on my note 2. but now the pop up for granting superuser permission isnt even coming up.
since i cant just switch the sim cards between my two phones, is it even worth putting a verizon rom on my s3? i would still have to call straight talk and have it switched anyway. or is that because the d2lte roms dont work for mms.. is that the only reason to use the verizon roms instead? you said before in pm that if i put my note 2s sim in my s3(after installing verizon rom) that i would have to press *228 to reset the prl. and that might mess it up for the note 2 that im using. would i just have to repeat dialing *228 in my note 2 if i switched the sim back to that one? also i believe you said in a different thread that theres no way to get 4g on these phones? that was also one of my reasons for wanting to put a verizon rom on the s3. basically this phone is a backup that has just become a learning experiment now
Click to expand...
Click to collapse
I don't know what you've got going on with superSU, does root checker verify you are rooted? If you have root access as normal and everything works then I wouldn't worry about it as long as it works.
Your IMEI should show in system settings>about phone. IMEI has several names: ESN, IMEI and a few more, they are all the same thing, it's what the network uses to identify your device as that particular device and not another. That number is what registers on the network, without it the device is useless, it won't even work on WiFi if its NV bricked.
Dialing *228 on a Verizon SIM ruins it for Verizon, from what I know, it won't work for Verizon after that no matter what you dial. Using the SIM on the ST S3 is only to get signal and data, it doesn't have to be activated by any process, just inserted and OTA programmed in the device. Actually any CDMA SIM works but the Verizon 4G specifically gets the stock MMS working, it even corrects MMS issues on non rooted stock ST S3. The 4G SIM is needed to get the ROMs working because the ROMs are actually built for the Verizon S3 which is a 4G device that requires 4G SIM, that is how Verizon regulates their 4G data, this makes our device require the SIM when running Verizon ROMs, even the d2lte ROMs require SIM because they are built for LTE(4G) devices, hence d2 "lte". The ROMs have to follow their programming, their programming says they must have SIM so a SIM must be used regardless of what the device is.
The 4G was hardware disabled in the device, it can't be re-enabled. This device actually has the Verizon S3's motherboard in it even though it says it is an SCH-S968C, if you open it up and look inside you'll see SCH-I535 stamped in more than one place on the hardware pieces. Its a rebranded Verizon S3 basically with 4G disabled.
Is any of this making any sense yet?
I have a thread that I ran across where a guy used his active Verizon SIM in a ST S3 by going to his verizon user account online and entering the phone info, this is not really a legit way to do it, the network is fooled into thinking one device is the other without the second device actually being legitimately activated on the Verizon network, this is a shady practice and isn't recommended because if the network catches on they'll kill you ESN(IMEI) and the device will be useless and un-repairable. It can be done but isn't worth the risk, I will tell you how to do this, its against the rules on XDA, if you do so then do not come posting here about it no matter what issues you are having, the practice is frowned on around here and most won't help you with it if they are serious about XDA.
Droidriven said:
I don't know what you've got going on with superSU, does root checker verify you are rooted? If you have root access as normal and everything works then I wouldn't worry about it as long as it works.
Your IMEI should show in system settings>about phone. IMEI has several names: ESN, IMEI and a few more, they are all the same thing, it's what the network uses to identify your device as that particular device and not another. That number is what registers on the network, without it the device is useless, it won't even work on WiFi if its NV bricked.
Dialing *228 on a Verizon SIM ruins it for Verizon, from what I know, it won't work for Verizon after that no matter what you dial. Using the SIM on the ST S3 is only to get signal and data, it doesn't have to be activated by any process, just inserted and OTA programmed in the device. Actually any CDMA SIM works but the Verizon 4G specifically gets the stock MMS working, it even corrects MMS issues on non rooted stock ST S3. The 4G SIM is needed to get the ROMs working because the ROMs are actually built for the Verizon S3 which is a 4G device that requires 4G SIM, that is how Verizon regulates their 4G data, this makes our device require the SIM when running Verizon ROMs, even the d2lte ROMs require SIM because they are built for LTE(4G) devices, hence d2 "lte". The ROMs have to follow their programming, their programming says they must have SIM so a SIM must be used regardless of what the device is.
The 4G was hardware disabled in the device, it can't be re-enabled. This device actually has the Verizon S3's motherboard in it even though it says it is an SCH-S968C, if you open it up and look inside you'll see SCH-I535 stamped in more than one place on the hardware pieces. Its a rebranded Verizon S3 basically with 4G disabled.
Is any of this making any sense yet?
I have a thread that I ran across where a guy used his active Verizon SIM in a ST S3 by going to his verizon user account online and entering the phone info, this is not really a legit way to do it, the network is fooled into thinking one device is the other without the second device actually being legitimately activated on the Verizon network, this is a shady practice and isn't recommended because if the network catches on they'll kill you ESN(IMEI) and the device will be useless and un-repairable. It can be done but isn't worth the risk, I will tell you how to do this, its against the rules on XDA, if you do so then do not come posting here about it no matter what issues you are having, the practice is frowned on around here and most won't help you with it if they are serious about XDA.
Click to expand...
Click to collapse
yeah i dont use verizon its just a verizon phone on straight talk.
my copy of the stock rom is this one that im sure youve seen before
COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5
since i couldnt make a copy of my actual stock on my non rooted h2 stock rom.
so youre saying to revert to this before i install twrp? i would install it as a zip and not as a restore correct?
cory733 said:
yeah i dont use verizon its just a verizon phone on straight talk.
my copy of the stock rom is this one that im sure youve seen before
COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5
since i couldnt make a copy of my actual stock on my non rooted h2 stock rom.
so youre saying to revert to this before i install twrp? i would install it as a zip and not as a restore correct?
Click to expand...
Click to collapse
Restore your stock nandroid in CWM, then reboot into system normally, then boot back to CWM and flash the TWRP .zip, then go to advanced options in CWM and select "reboot recovery" it will boot straight to TWRP then you make a nandroid of your stock in TWRP then you don't need CWM or the stock nandroid that was created in CWM.
I'm just trying to explain how to get TWRP and have a stock nandroid in TWRP because the nandroid made in CWM won't work in TWRP, if you're gonna run and keep TWRP then you'll need a stock nandroid to use in TWRP if you ever need it. Otherwise you would have to go back to CWM to restore the stock nandroid that you made in CWM. Doing what I'm saying eliminates the hassle of going back and forth between CWM and TWRP.
If you're already on stock then you don't need to restore the nandroid in CWM, you just need to flash TWRP .zip then reboot to it from within CWM and make a TWRP nandroid and do away with CWM and the nandroid you created in it, your CWM nandroid van be found on your extsd in Clockworkmod/backups folder, just delete the entire Clockworkmod folder.
Droidriven said:
Restore your stock nandroid in CWM, then reboot into system normally, then boot back to CWM and flash the TWRP .zip, then go to advanced options in CWM and select "reboot recovery" it will boot straight to TWRP then you make a nandroid of your stock in TWRP then you don't need CWM or the stock nandroid that was created in CWM.
I'm just trying to explain how to get TWRP and have a stock nandroid in TWRP because the nandroid made in CWM won't work in TWRP, if you're gonna run and keep TWRP then you'll need a stock nandroid to use in TWRP if you ever need it. Otherwise you would have to go back to CWM to restore the stock nandroid that you made in CWM. Doing what I'm saying eliminates the hassle of going back and forth between CWM and TWRP.
If you're already on stock then you don't need to restore the nandroid in CWM, you just need to flash TWRP .zip then reboot to it from within CWM and make a TWRP nandroid and do away with CWM and the nandroid you created in it, your CWM nandroid van be found on your extsd in Clockworkmod/backups folder, just delete the entire Clockworkmod folder.
Click to expand...
Click to collapse
kinda forgot about this project for a while but decided to finish it. i installed the version of TWRP you showed me and it and cyanogenmod installed just fine this time. i actually just installed this twrp from twrp itself. tried putting the sim from my note 2 in my s3 just to try. it didnt work. i didnt dial *288 or anything. but i ordered another sim. will see if everything works when i get the sim.
thanks for your help
maybe spoke too soon. now its not letting me boot into twrp for some reason. even though i already did before and made a backup. i get the blue letters up top saying its booting to recovery but then it just skips it
edit: works when enabling advanced reboot options and rebooting to recovery from phone
cory733 said:
maybe spoke too soon. now its not letting me boot into twrp for some reason. even though i already did before and made a backup. i get the blue letters up top saying its booting to recovery but then it just skips it
edit: works when enabling advanced reboot options and rebooting to recovery from phone
Click to expand...
Click to collapse
Hmm, sounds fishy. Try going back to the TWRP you already had if it worked fine, why the d2tfnvzw is acting funny I couldn't tell you. When you put the SIM in it the ROM should work without having to do anything, dialing *228 and setting APNs is only to get MMS working and only works with the Verizon 4G LTE SIM that I know of.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Hmm, sounds fishy. Try going back to the TWRP you already had if it worked fine, why the d2tfnvzw is acting funny I couldn't tell you. When you put the SIM in it the ROM should work without having to do anything, dialing *228 and setting APNs is only to get MMS working and only works with the Verizon 4G LTE SIM that I know of.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
the twrp i had before couldnt install cm correctly for some reason. now that im on cm12 can i still install that twrp?
the rom seems to be working fine, i can still get into everything else without the sim, it just says no sim. With that sim i didnt get service, i got the "welcome to verizon wireless" when trying to make a call. installing apps seems slow.
somehow ive lost root. supersu wont install the binaries either, im gonna try to figure out how to do that with twrp.
cory733 said:
the twrp i had before couldnt install cm correctly for some reason. now that im on cm12 can i still install that twrp?
the rom seems to be working fine, i can still get into everything else without the sim, it just says no sim. With that sim i didnt get service, i got the "welcome to verizon wireless" when trying to make a call. installing apps seems slow.
somehow ive lost root. supersu wont install the binaries either, im gonna try to figure out how to do that with twrp.
Click to expand...
Click to collapse
As for your root being gone, its probably not, you've got to go into developer settings and set root access to "apps and adb", do that and verify whether you have root after that, also get ES file explorer and set your mount permissions to R/W
If the SIM is a Verizon SIM it should work.
I recommend flashing the newest OctOS d2vzw CM12 has always been too buggy in my opinion, OctOS is super stable, its the best ROM out if all the d2vzw ROMs. The SIM will probably work with OctOS, myself and hundreds of others have been using it with no issues.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
As for your root being gone, its probably not, you've got to go into developer settings and set root access to "apps and adb", do that and verify whether you have root after that, also get ES file explorer and set your mount permissions to R/W
If the SIM is a Verizon SIM it should work.
I recommend flashing the newest OctOS d2vzw CM12 has always been too buggy in my opinion, OctOS is super stable, its the best ROM out if all the d2vzw ROMs. The SIM will probably work with OctOS, myself and hundreds of others have been using it with no issues.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
ok cool got root, you were right, the root access setting was set to disabled. the sim is a straight talk CDMA for verizon. its from the bring your own phone sim card kit that has sims for every carrier. i didnt want to try *288 since you said it could ruin it for my Note 2. but another one is on the way theyre $1.07 from walmarts website.
do you have a link for octos? its based off cm12? im also trying to get an app called drivedroid to work since i cant do much with my note 2's useless locked bootloader. google search for OctOs is bringing me to liquidsmooth.
cory733 said:
ok cool got root, you were right, the root access setting was set to disabled. the sim is a straight talk CDMA for verizon. its from the bring your own phone sim card kit that has sims for every carrier. i didnt want to try *288 since you said it could ruin it for my Note 2. but another one is on the way theyre $1.07 from walmarts website.
do you have a link for octos? its based off cm12? im also trying to get an app called drivedroid to work since i cant do much with my note 2's useless locked bootloader. google search for OctOs is bringing me to liquidsmooth.
Click to expand...
Click to collapse
teamoctos.com ,find the download page and get the newest d2vzw.
I'm not sure that the straight talk SIM will work like the actual Verizon SIM does, in the year that I've been following development on this device I've seen no posts that say the ST BYOP 4G SIM works. I recommend an actual Verizon one, they are only $2-4 on eBay, that's cheaper than the ST SIM and guaranteed to work.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
teamoctos.com ,find the download page and get the newest d2vzw.
I'm not sure that the straight talk SIM will work like the actual Verizon SIM does, in the year that I've been following development on this device I've seen no posts that say the ST BYOP 4G SIM works. I recommend an actual Verizon one, they are only $2-4 on eBay, that's cheaper than the ST SIM and guaranteed to work.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
should i try switching TWRP's before installing this rom?
cory733 said:
should i try switching TWRP's before installing this rom?
Click to expand...
Click to collapse
No, try the d2tfnvzw one first
Sent from my SCH-I535 using Tapatalk
Droidriven said:
No, try the d2tfnvzw one first
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
ok im on OctOs now. stayed with the same TWRP d2tfnvzw version. Same thing with the sim. "welcome to verizon wireless, your mobile number is either not active, or invalid" does *228 do anything besides getting mms to work?
edit: the signal bar icon has a ! in it and when i click on it it says Verizon Wireless 2 GB warning
cory733 said:
ok im on OctOs now. stayed with the same TWRP d2tfnvzw version. Same thing with the sim. "welcome to verizon wireless, your mobile number is either not active, or invalid" does *228 do anything besides getting mms to work?
Click to expand...
Click to collapse
It is supposed to auto program the SIM. I'm not sure it will work on the ST SIM, I know it works for the Verizon SIM, don't try it on the ST SIM, I might fry it and make it useless.
Verify you still have IME, has the phone itself been activated on straight talk, your IMEI has to be registered and activated on the straight talk network. Are you showing any signal bars or the 3G symbol?
Sent from my SCH-I535 using Tapatalk
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.