I've had my S3 for awhile now, and I love it. Almost as good as the original Motorola Droid, which is still my favorite phone ever because of the keyboard and the unlocked bootloader.
I've been having major issues, and I am totally out of ideas, so I turn to those more knowledgeable than me.
Anyway, I was using Liquid Smooth Beta 1, and enjoying my experience. (I am posting this in the Liquid thread as well, but it becomes more of a general issue as the story goes on.) Installed beta 2, and since have had nothing but issues with my S3 and Verizon (where it becomes an issue larger than Liquid's software). After installing beta 2, my phone was no longer able to activate with Verizon, although I still had a mobile data connection and could browse the web and communicate through messaging and social media, as well as receive text messages, although I could not send them.
This is where the issue gets confusing to me. When I boot up recovery, and look to restore a working nandroid backup, it tells me there are no backups to restore. I've been able to deduce that the problem is related to the 0 folder issue with 4.2.1. I tried various different roms trying to get one to activate so that I could at least have a functioning phone but haven't had any real success. I did manage to get pacman running correctly I think, but when I moved on to others (which I am hoping to continue doing lol) I was no longer able to get that to work either. I have other nandroid backups saved on my SD card, although they are hidden way back in 0/0/0/0/0/clockwordmod/backup, so I decided to try copying that to the clockworkmod folder on my sd card, but I could not find it!
Every time I installed a 4.2.1 rom, I got an extra layer of 0, and nandroid would no longer allow me to restore any of those backups.
I made a backup of my current rom, figuring that would show me where nandroid looks for files, but the backup I made does not exist. I searched my entire filesystem, and it finds the backups saved in 0/0/0/0/0 but it does not find any others. How is it possible that nandroid can make a backup and find it, but not have it exist anywhere?????? I even made a second backup to try again and although it was successful, the files just dont exist.
So this morning I finally decided to go at the problem with Odin, and installed the 4.0.4 OTA update that originally came with my phone, as well as the stock radio, but I am still having issues. The phone now activates, but nothing really changes for me, meaning I still cannot make phone calls or send text messages, although I do receive text messages.
Does anybody have any other ideas, or do I need to have my phone replaced through insurance and just eat the cost?
If you're still on ICS dial this *2767*3855#
It may wipe internal SD so backup what you want.
This is a known issue with the 4.2 ROMs
Sent from my LG spectrum (that's right) blazing fast on cm10!
You have to reprovision your phone. Use the dialer code that kitwofan provided. If you upgraded to jelly bean already, you'll need to odin back to 4.0.4 before you can do so.
I just ran into the same problem on another ROM I had to use Odin to flash back to stock.
Sent from my SCH-I535 using Tapatalk 2
That ICS dial code you provided completely cleared up the problem, thanks a bunch.
If anybody has some ideas as to how I could make nandroid backups, and not have them exist anywhere on my sdcard, please let me know, that still puzzles me to no end.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
I've heard of people having issues with making nandroids of 4.2 roms and having the 0 folders when backing up with CWM 5.x.
I changed my recovery to TWRP 2.3.3 and have never had any issues.
Unlocked Verizon GS3
Hello,
I started with Galaxy Note 2- i317M (rogers, canada), rooted with DN3 V4 beta installed. But I wanted to try DN4, so I created a back-up using TWRP and tried installing DN4. However, I later realized that it is not for the LTE versions yet and phone did not recognize SIM anymore. So I wiped the data and tried installing dn3 v5.5, but the phone still did not connect.
Losing all hope I installed DNv4 again, but it still did not work. So i finally just tried restoring from the back-up I made using TWRP. Everything in the phone is same except no network.
Finally I tried restoring from back-up after doing a complete wipe of internal storage and everything except the external card. But still the error does not go away. I researched more about the error and the fact that my imei shows up as null/null. I used the instructions of using EFS professional, but it did not work. The model number in my phone now shows up as SM-G900F and baseband shows as unknown, and it shows DN3V5 Rom despite the clean-up and restoring from DN3V4.
Any guidance available on this please...I need specific steps because after 12 hour search and try-outs I am lost now.....
UPDATE:
Solved it! Here is the solution for anyone in this problem
http://forum.xda-developers.com/showpost.php?p=46231268&postcount=4
worked like a charm.. No reason to throw this and get a new phone
I have had this problem. It didn't happen whilst flashing though. My imei number is now a generic one and I had no efs backup. After 5 days of trying everything I can find I'm giving up. My note 2 is dead as far as I'm concerned. As far as I'm aware to get my imei back I'll have to send it for repair so I'll buy another phone and not a Samsung
I don`t think your phones are dead. I didn`t try it personally, but I`m sure you can restore your EFS back. Just you need to do some research, maybe you could start here:
https://www.google.ro/?gws_rd=ssl#safe=off&q=how+to+recover+efs+folder
Do not give up, read on end you will eventually do it! And, by the way, next time maybe you don`t forget to back up before doing anything to your phone!
nmugurel2003 said:
I don`t think your phones are dead. I didn`t try it personally, but I`m sure you can restore your EFS back. Just you need to do some research, maybe you could start here:
https://www.google.ro/?gws_rd=ssl#safe=off&q=how+to+recover+efs+folder
Do not give up, read on end you will eventually do it! And, by the way, next time maybe you don`t forget to back up before doing anything to your phone!
Click to expand...
Click to collapse
I did back up. with both titanium backup and twrp but it is not working. And I dont think I will give up. I will format is all together and start over if i have to.
Do you think it will work if I format it entirely and start over?
dexterousyash said:
I did back up. with both titanium backup and twrp but it is not working. And I dont think I will give up. I will format is all together and start over if i have to.
Do you think it will work if I format it entirely and start over?
Click to expand...
Click to collapse
Glad to see you solved it!
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
Hey all,
I restored a backup of my old phone made in TWRP – a full backup, including Boot, System, Data, Cache & EFS – onto a new D850 I got. Both the old phone and the new one were able to connect to AT&T before this.
Now the new phone, with the restored backup from the old one, displays a network searching icon indefinitely upon reboot.
Any thoughts as to how to fix this?
- Andi
phnord said:
Hey all,
I restored a backup of my old phone made in TWRP – a full backup, including Boot, System, Data, Cache & EFS – onto a new D850 I got. Both the old phone and the new one were able to connect to AT&T before this.
Now the new phone, with the restored backup from the old one, displays a network searching icon indefinitely upon reboot.
Any thoughts as to how to fix this?
- Andi
Click to expand...
Click to collapse
Why did you restore a EFS back from your old phone to your new one? Unless you backed up the EFS from your new phone there may not be a way to fix this. EFS Is different for each phone you should never restore an EFS from a different device.
Sent from my iPhone using Tapatalk
My *guess* is that I should not have overwritten the new phone's EFS with the old phone's? I think I backed up the EFS of the new phone before doing so; will restoring it fix my issue? If not, how screwed am I?
phnord said:
My *guess* is that I should not have overwritten the new phone's EFS with the old phone's? I think I backed up the EFS of the new phone before doing so; will restoring it fix my issue? If not, how screwed am I?
Click to expand...
Click to collapse
See if you have a backup of the new phones EFS try that and report back. If not it's pretty much a WiFi only device.
Sent from my iPhone using Tapatalk
I restored the new phone's original EFS, and all is well.
FWIW, my reasoning behind flashing everything from the old phone to the new was that is what it said to do in every guide I read about transferring from old to new. I didn't realize EFS was supposed to be excluded; I didn't realize the EFS from one phone would be incompatible with another
In any case, crisis averted – thanks for the confirmations along the way
phnord said:
I restored the new phone's original EFS, and all is well.
FWIW, my reasoning behind flashing everything from the old phone to the new was that is what it said to do in every guide I read about transferring from old to new. I didn't realize EFS was supposed to be excluded; I didn't realize the EFS from one phone would be incompatible with another
In any case, crisis averted – thanks for the confirmations along the way
Click to expand...
Click to collapse
It's not that the EFS is not compatible. But the EFS stores info like IMEI etc. you can't have two phones with the same imei. Each EFS is different. When restoring you don't have to restore every thing though. I'm glad you had a backup! As without that it pretty much would had been an wifi only device. Your very welcome .
Sent from my iPhone using Tapatalk