So i decied to go to carbon rom because my phone has been acting strange, YouTube would keep resigning in everything i would launch it, Random crashed and freezes and has just been acting up for no good reason. I was running CM 10.1 nightly and dont apply ant mods to it or anything like that becuase i like it simple.
When i flashed the rom i did it with gapps but they were not intalled when i boot, all i got was my SIM pin popup like i usualy get. So i re-flashed gapps and still no luck. So i said f*** it and found another build of it and copyed it to my SD Card and was going to flash it. Like i allways do i went to factory reset and all i got was a long log of cant remove lost+found and same happed when i tryed to wipe the system. and that didnt look good so i pulled the battery and booted recovery with the key press and it would get to teamwin screen but would reboot. Opened oden on my desktop, reflashed teamwin tar and that didnt help it. So i was lucky that i loaded the rom and i rebooted to recovery and am copying all my /data/media to a sdcard that i have
So can anyone give me some links to the 16GB PIT and all that jazz so i can get thing back up and running
And no i am not a n00b becasue i have been working with android and other phones long enough to know what i am doing
powercamg4 said:
So i decied to go to carbon rom because my phone has been acting strange, YouTube would keep resigning in everything i would launch it, Random crashed and freezes and has just been acting up for no good reason. I was running CM 10.1 nightly and dont apply ant mods to it or anything like that becuase i like it simple.
When i flashed the rom i did it with gapps but they were not intalled when i boot, all i got was my SIM pin popup like i usualy get. So i re-flashed gapps and still no luck. So i said f*** it and found another build of it and copyed it to my SD Card and was going to flash it. Like i allways do i went to factory reset and all i got was a long log of cant remove lost+found and same happed when i tryed to wipe the system. and that didnt look good so i pulled the battery and booted recovery with the key press and it would get to teamwin screen but would reboot. Opened oden on my desktop, reflashed teamwin tar and that didnt help it. So i was lucky that i loaded the rom and i rebooted to recovery and am copying all my /data/media to a sdcard that i have
So can anyone give me some links to the 16GB PIT and all that jazz so i can get thing back up and running
And no i am not a n00b becasue i have been working with android and other phones long enough to know what i am doing
Click to expand...
Click to collapse
I think this is what you are looking for. Follow the guide and you will be on stock, rooted, and unlocked.
http://forum.xda-developers.com/showthread.php?t=2046439
mapatton82 said:
I think this is what you are looking for. Follow the guide and you will be on stock, rooted, and unlocked.
http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Iv been able to load a rom but now i cant write to the phone, i have now found a guide talking about unbricking it useing odin anf a nand erase all and thats not working eather, any story i can tell verizon so i can get a replacement today?
Update!
Iv been useing http://forum.xda-developers.com/showthread.php?t=1840030 to try to get my phone back and so far it has failed but i decied to switch computers, all my computers are now running windows 8 and i ws doing this on my development computer / server and then i switched to the last computer to have windows 7 next to my main computer and what do you know it worked, the nand erase worked and now its booting im sure i will have to re-unlock the bootloader and all but im happy now
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
Hi guys, I just registered @ xda because it looks like it's the only serious and feedback active community available. In 10 minutes I found most of the info I was looking for, but I still want to make sure what Im planning to do is fine before I mess up again. Here's the issue:
I was fooling around with the tablet and had just rooted it so I could get rid of some bloatware, and decided to go further and install cyanogen, just for the looks. So I got this thing cm-10.1-20130411-EXPERIMENTAL-p3110-M3 from the official site, which was I put on a folder inside the tablets storage (not on the 16gb SDcard it had in it). I downloaded Rom Manager and skipped through the "search and download rom" and went for the option of looking for it inside the SD card. I had the Backup options and the wipe cache and data ON.
So I proceeded and it booted, started to do the backup and at some final point it had an error, something like "could not backup Data!". I had the options of rebooting, some other stuff and the option of installing a rom from the SD Card. I went for it and searched for the .zip inside the storage, and installed it. It did it withouth trouble, and when it finishd it prompted me to install an update, which I didn't (don't know why).
Then, I went for the reeboot option and when it started I get the normal samsung's black screen with the device's name on it, but then I get a fast glitching image that sweeps through the screen and the cyanogen startup logo which gets stuck for ever.
Click to expand...
Click to collapse
Now Im past it, I can get to download or recovery mode, so I moved onto getting the original firmware so I can clean-install again. I got it from sammobile, chose the one belonging to Chile (that's where I got the tablet), and it's 729mb of data. The tablet is a Samsung Galaxy Tab 2 7.0 P3110
If I flash it with Odin will everything be fine? All I have to do is that thing in downloadmode when I rooted it, but with that 729mb file? Should I put it in the external SD or is it more convenient to place it in the internal storage?
I appreciate your help in advance, I know this is as basic as it gets but messing up again would cost me dearly, since I have to do other stuff.
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
billysam said:
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
Click to expand...
Click to collapse
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
aguscanzani said:
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
Click to expand...
Click to collapse
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
billysam said:
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
Click to expand...
Click to collapse
You guys have helped me a lot. I've worked everything out and now i've got to reinstalling android on it, AOSP's 5.1.1 Lollipop. It's beautiful. There's just one problem: Since it came with no apps at all, I wanted to install everything on it again. Problem is, when I go to google play, it shows that i've already got my apps installed, so it wont let me download them, and it doesn't matter if I place the APK's inside the tablet as there's no manager to open them. Even if I download apk's through the tablet's own web browser, it says it can't open the file. Any ideas on this?
so here's my story:
I bought a used j7 prime. it had android 6.0.1 and it was working fine. even though it didn't seem rooted, the device status was custom and i couldn't get updates. so i downloaded android 7 firmware and i flashed it with Odin. the phone worked fine but i was getting the famous "not registered on network" error. I tried different solution that only made the phone worse. the last thing i tried was flashing an EFS folder ( i think ) that i downloaded through odin and the got messed up. so i flashed android 7 again but then my IMEI was unknown, so i rooted the phone and tried to restore the EFS folder that i had already backed up using EFS Professional, but i get an error message saying "unable to extract archive".
i have no idea what to do and i really need help.
thank you in advance.
nasralli said:
so here's my story:
I bought a used j7 prime. it had android 6.0.1 and it was working fine. even though it didn't seem rooted, the device status was custom and i couldn't get updates. so i downloaded android 7 firmware and i flashed it with Odin. the phone worked fine but i was getting the famous "not registered on network" error. I tried different solution that only made the phone worse. the last thing i tried was flashing an EFS folder ( i think ) that i downloaded through odin and the got messed up. so i flashed android 7 again but then my IMEI was unknown, so i rooted the phone and tried to restore the EFS folder that i had already backed up using EFS Professional, but i get an error message saying "unable to extract archive".
i have no idea what to do and i really need help.
thank you in advance.
Click to expand...
Click to collapse
Did you flash all Firmware (AP, BL,CSC,CP)?
AP, BL, CSC, CP is the new model for installing Firmware
hi
please flash this file with odin.https://drive.google.com/file/d/1TUXAQT4qJPZg9Qrt0ColKZQCxwW1mOG1/view?usp=drivesdk
for fix this problem use this way:
1. download and install partition backup program
https://drive.google.com/file/d/1XQf_jAZR164MI5kDbFPXLGBNKz56GgPY/view?usp=drivesdk
2. download efs image file(attention this file for j7 prime model only)
https://drive.google.com/file/d/1CxVhAxdmlpElo2gvKKNJ_cDrs2PTxByI/view?usp=drivesdk
3. download and exteract this help file for restor efs.img file with partition backup program on your phone.
https://drive.google.com/file/d/1V6UXQqxKMQ1bBXavUGoc8SkGjKDSXtHU/view?usp=drivesdk
I have the same problem on my SM-610F that I bought thinking that flashing would fix the prob.
It also says that the Device Status is custom and IMEI is unknown.
I didn't do any modification after buying it.
Just flashed TWRP by Odin and now it's it says Unable to mount /data.
Been searching for further fixes so far. ??
this happend to a lot, well just install any roms here you will get imei back.
Sent from my SM-G610F using XDA Labs
AmirRouichi said:
well just install any roms here you will get imei back.
Click to expand...
Click to collapse
Any rom means any Custom ROM? I've tried flashing the stock rom, but in vain.
Service Centre told me to send it back to Oman where it was brought from. ??
A S Ovin said:
Any rom means any Custom ROM? I've tried flashing the stock rom, but in vain.
Service Centre told me to send it back to Oman where it was brought from. ??
Click to expand...
Click to collapse
There are 2 ways to bring back the imei
1. you need to flash custom rom or stock rom ( Custom rom link: https://forum.xda-developers.com/t/therealrom-pure-edition-g610x-9.4009347/
Note: Before installation remove the sim. One installation done and reboot the system and once home screen comes insert the sim)
2. one more method is there try once it may helpful for you. First remove the sim from the device. Do network setting reset in the Settings->About-> Reset option-> Select only Network and wifi reset. Note this will erase your saved network passwords. Then install google dialer from playstore. Run the below code *#*#27262826#*#* in google dialer. A screen will come to install CSC features. In the first drop down select the country you want (for india select INS) and submit. Reboot the system. After completion insert the sim and enjoy ur mobile network. It will work for VOLTE. If above code doesn't pop up that option then u need to install rom again.
do it this only in
A S Ovin said:
I have the same problem on my SM-610F that I bought thinking that flashing would fix the prob.
It also says that the Device Status is custom and IMEI is unknown.
I didn't do any modification after buying it.
Just flashed TWRP by Odin and now it's it says Unable to mount /data.
Been searching for further fixes so far. ??
Click to expand...
Click to collapse
About the /data thing. Go to TWRP, select wipe, advanced wipe, click on data, select Repair or Change File System, Change File System, Choose EXT3, let it do. Then go to home screen, and do the same but choose EXT4. You can now access your data until you reboot to Stock ROM or any OneUI/TouchWiz based ROM.
This happens as Samsung encrypts(?) the /data partition. About the IMEI, the factory effed up. You need to send it back to where you bought it and seek replacement.