Related
My maps gps lock got totally f*cked by synergy 1.7 so it was suggested to go back to stock and reroot since flashing new rom from clean wipe did not work.
A lot of links and methods are out of date, so I was wondering what the best way to get back to stock at this point.
I have the latest odin on my computer, I guess I'm looking for the most recent or most reliable stock image to flash.
Thanks
SGS3 production
SGS3 production
I think a lot of people recommend the root66 stock..... But I'd try noSympathy's image
Sent from my SCH-I535 using Tapatalk 2
I'm rooting immediately after so whatever is a proven version will make me happy
SGS3 production
They're both rooted so no need to do after. Both are tried and true, noSympathy's is based off the last OTA but some people like to start from scratch so that would be root66.
Sent from my SCH-I535 using Tapatalk 2
I want to get back to unrooted stock.
I can't seem to locate the route66 stock image
SGS3 production
http://forum.xda-developers.com/showthread.php?t=1762204
It's up to you but it's just more work to go unrooted then root yourself. Check the development threat there maybe an un rooted image there
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:36 AM ---------- Previous post was at 07:27 AM ----------
http://forum.xda-developers.com/showthread.php?t=1755386
Thought there would be a newer one but here's unrooted...
Sent from my SCH-I535 using Tapatalk 2
My main reason to flash stock was I was told that would be the only way to restore my faulty gps lock.
Do you think flashing a stock rooted image would do the same for me? Or should I flash unrooted image then start fresh? Time is not a concern, im patient
SGS3 production
FormeriPhoney said:
My main reason to flash stock was I was told that would be the only way to restore my faulty gps lock.
Do you think flashing a stock rooted image would do the same for me? Or should I flash unrooted image then start fresh? Time is not a concern, im patient
SGS3 production
Click to expand...
Click to collapse
Flash back to stock then root. Click link in sig.
i tried this......still having the same issue, switched from CM10 back to stock and had issues with my GPS being way off, like by 3300 meters off haha.....so flashed back to stock, still had the issue, so i used the rooted stock image and flashed that and i'm still off by about over 2k meters.....don't use my navigation or maps all that much but when i do need it i'll have a bit of an issue lol
I had issues with my gps for a few days. If was real flaky but got better with synergy 1.5. I have since move to 1.6 with a fresh install and am still okay. Check out a app called gps status. See if you can see any gps satellites. Maybe in that app clear your agps state in tools. Then if that doesn't work try to download gps assistance with the same app in the same settings. Make sure your out side for this stuff with your gps. It's probably not gonna hit ya sitting on the couch.
Sent from my SCH-I535 using Tapatalk 2
FormeriPhoney said:
My maps gps lock got totally f*cked by synergy 1.7 so it was suggested to go back to stock and reroot since flashing new rom from clean wipe did not work.
A lot of links and methods are out of date, so I was wondering what the best way to get back to stock at this point.
I have the latest odin on my computer, I guess I'm looking for the most recent or most reliable stock image to flash.
Thanks
SGS3 production
SGS3 production
Click to expand...
Click to collapse
I used the stock image from here:
http://samsung-updates.com/device/?id=SCH-I535
and used this method for rooting:
http://forum.xda-developers.com/showthread.php?t=1792342
my gps doesnt work at all
After Odin back to stock, non rooted image my GPS is fixed.
Now on CM10, loving it. Not sure if I'll ever try synergy again bc of that nightmare situation.
I use my gps pretty much all day. I needz it
SGS3 production
New AOKP JB issue with radio
Well I am trying to get something fixed and I am going through a complete restore to do this.
But just so you are aware the new AOKP JB release will kill your data. I learned a hard lesson with this when trying to recover and nandroid back to my previous rom. It killed my data completely and would not allow me to do anything with data in any rom. I used the root66 stock rom in hopes it would work, and that didnt even solve the issue.
Right now I am restoring a factory image through kies and seeing if that will do what I need. If it does, I am sticking with stock roms for awhile until AOSP roms have more time to develope with less bugs.
douglasf01 said:
Well I am trying to get something fixed and I am going through a complete restore to do this.
But just so you are aware the new AOKP JB release will kill your data. I learned a hard lesson with this when trying to recover and nandroid back to my previous rom. It killed my data completely and would not allow me to do anything with data in any rom. I used the root66 stock rom in hopes it would work, and that didnt even solve the issue.
Right now I am restoring a factory image through kies and seeing if that will do what I need. If it does, I am sticking with stock roms for awhile until AOSP roms have more time to develope with less bugs.
Click to expand...
Click to collapse
It sounds like you may have lost your IMEI or MEID. I hope you made a backup with QPST.
still had IMEI
toy028 said:
It sounds like you may have lost your IMEI or MEID. I hope you made a backup with QPST.
Click to expand...
Click to collapse
Well it turns out I still had my imei present on my phone and even after a factory reset like I did wit kies it still didnt work. Initially I wasnt able to get past the activation screen on the root66 rom, but I was able to with the stock factory image from kies in which case this allowed me to follow the steps in this link.
http://forum.xda-developers.com/showthread.php?t=1838791
Once I did that my phone rebooted and everything came back as it was never gone, well except for all of my data on the internal sd card, but that is to be expected.
After 2 hours of going through numerous steps I finally found a fix, mind you not the most simple of fixes, but a fix none the less.
I think I am just going to stay stock for awhile like I mentioned and wait for the OTA that comes out in 2014 lol, unless in review of AOSP roms the issues present now are gone after sometime.
Tks
Nice. Tks
Gps works like a champ on beans!
Gps seems to work substantially better on cm10 than on stock....ran the GPS test and i locked onto 14/19 satellites.
Beamed via NFC through the local store to the internet from my SGS3.
Ok, so I've discovered something interesting. Being the crack flasher I am, I often flip flop between AOSP, the occasional AOKP and TW roms. Seeing as I have a little 7 year old brother, my mother finds it nice to be able to instantly transfer stuff back and forth when dealing with him thru NFC and WiFi direct, so NFC is a big factor for me, in addition to being able to use Google Wallet. I notice that as long as I stick to AOKP/AOSP, my NFC is fine, but the minute I flash a TW rom and go back to AOKP/AOSP, it instantly breaks NFC functionality completely, regardless of me doing anything else.
For instance:
1) Odin back to stock ICS
2) Flash CM10 or any other AOSP/AOKP rom and check NFC functionality and its able to be toggled
3) Flash TW
4) Immediately flash back to CM10 and NFC will be grayed out and unable to be toggled
The same could be said for doing it this way:
1) Odin back to stock ICS
2) Flash TW
3) Immediately flash CM10/AOKP/AOSP rom and check NFC and it's grayed out and unable to be toggled.
What can be going on in TW that completely snaps NFC functionality so that you can't use it in CM10? All the MD5 checksums are valid and none of them have issues when being flashed, so I know it's not in part to doing anything wrong. Also, the only way to fix this is to flash back to a TW rom OR Odin back to stock if you want it to work in CM10 and stick to strictly that styling of ROM.
Known AOSP problem, it's not TW.
I don't know the technical reason for why but I have read in passing that you must have NFC checked on the ICS rom PRIOR TO flashing an AOSP rom. NFC is unchecked by default on TW so each time you observed it greyed out in AOSP roms is because you did not leave it turned on within TW. It sounds weird, especially since you wipe data when switching between roms but try it and see what happens.
Sent from my SCH-I535 using xda app-developers app
I'm not trying to hi-jack your thread, but i have been trying to find a solution to my nfc issue... Have you ran into a situation neither tw or CM10/AOKP/AOSP won't enable. When i try to do it in tw it just jumps back to the off position. and in cm it just stays grayed out.
Bern612 said:
I'm not trying to hi-jack your thread, but i have been trying to find a solution to my nfc issue... Have you ran into a situation neither tw or CM10/AOKP/AOSP won't enable. When i try to do it in tw it just jumps back to the off position. and in cm it just stays grayed out.
Click to expand...
Click to collapse
Have you returned to stock via Odin and observed the same issue still?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Have you returned to stock via Odin and observed the same issue still?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
yes i locked, odin back and still same issue. I stole wife battery, put that in my phone. Same issue. i rerooted, have tried every rom i could and still nothing. running beantown 2 now.
The main issue i have is i took it to Verizon, they said they would switch it out but i would lose unlimited
Bern612 said:
yes i locked, odin back and still same issue. I stole wife battery, put that in my phone. Same issue. i rerooted, have tried every rom i could and still nothing. running beantown 2 now.
The main issue i have is i took it to Verizon, they said they would switch it out but i would lose unlimited
Click to expand...
Click to collapse
That's unfortunate but it looks like you need a replacement in this case. Have you contacted Samsung to see if they'll exchange it for you?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
That's unfortunate but it looks like you need a replacement in this case. Have you contacted Samsung to see if they'll exchange it for you?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
No never thought of calling them. I actually thought i could only use verizon. I thinking about just giving it to my son, and getting the note II. My phone is on a business plan and his is on a plan with my wife, so i was going to do it that way.
And sorry digitalsynner85 for stealing your thread
SlimSnoopOS said:
Known AOSP problem, it's not TW.
I don't know the technical reason for why but I have read in passing that you must have NFC checked on the ICS rom PRIOR TO flashing an AOSP rom. NFC is unchecked by default on TW so each time you observed it greyed out in AOSP roms is because you did not leave it turned on within TW. It sounds weird, especially since you wipe data when switching between roms but try it and see what happens.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
this is the same experience ive had.
if you ever have it greyed out all you need tod o is the followng...
1. nandroid
2. flash a tw rom.
3. enable NFC.
4. Restore nandroid.
5. enable NFC.
hasnt failed for me yet.
ddurandSGS3 said:
this is the same experience ive had.
if you ever have it greyed out all you need tod o is the followng...
1. nandroid
2. flash a tw rom.
3. enable NFC.
4. Restore nandroid.
5. enable NFC.
hasnt failed for me yet.
Click to expand...
Click to collapse
This is the answer, works great.. Thank the man!
Did you know there is a NFC fix zip in the CM10 nightlies discussion? Flash this in recovery after you flash back to CM10 and it should fix NFC.
Props to the person who made this zip (dont have time to look right now, sorry)
Lol I know about odin'ing back to stock and all that, I was being curious as to the technical reasons as to why flashing a touchwiz rom then going back to cm10, even through a restored backup would cause the nfc capabilities to break, that was the purpose of the thread thanks for everyone's input so far
Beamed via NFC through the local store to the internet from my SGS3.
annoyingduck said:
This is the answer, works great.. Thank the man!
Click to expand...
Click to collapse
It doesn't work 4 me. not at all.
my steps
1.Nandroid my CM10 14/11
2.Flash tw ICS from Mobile Odin
3.Turn NFC on/off/on (it works)
4.Restore my CM10 nandroid
5.try out NFC. Nothing to do. greyed flag.
Tried also those steps:
1.Nandroid my CM10 14/11
2.Flash tw ICS from Mobile Odin
3.Turn NFC on/off/on (it works)
4.NEW installation CM10
5.try out NFC. Nothing to do. greyed flag.
Any ideas?
Turn on nfc, sbeam, basically everything. That's weird its not working. What I did was restore a nandroid of Jellybomb, turned on everything, went to recovery, did not wipe anything, restored aosp rom, nfc worked.
annoyingduck said:
Turn on nfc, sbeam, basically everything. That's weird its not working. What I did was restore a nandroid of Jellybomb, turned on everything, went to recovery, did not wipe anything, restored aosp rom, nfc worked.
Click to expand...
Click to collapse
ok. I'm trying not to wipe anything. do u think wiping could be the problem?
Seams to be. Others reporting the same thing
Along time ago I made the mistake of wiping cache, dalvik and flashing a kernel without resetting wallet. I figured I wasn't wiping data so I was good (just lazy.) I did make a backup with working wallet.
Now my Nfc will work (I've transfered songs and pics through s beam) but it sometimes greys out and won't stay on. It works than stops, reboot does not change it. If I get it back before I go to bed when I wake up its broke again.
I'm currently on Clean Rom ULE not that I think that's the problem.
Sent from my SCH-I535 using xda premium
make nandroid, flash stock rom, tick on NFC, restore nandroid
win. worked for me everytime.
why are you resettin wallet ever? Ive swtiched between 10ish roms and ive never reset anything. it works everytime no issues
Do you get a box that says "unfortunately nfc has stopped"? I used to get that and finally fixed it by flashing back to the stock rom and restoring data from my old rom so I didn't lose anything. Fixed the problem for me and didn't lose any apps or how my home screen was set up.
ddurandSGS3 said:
make nandroid, flash stock rom, tick on NFC, restore nandroid
win. worked for me everytime.
why are you resettin wallet ever? Ive swtiched between 10ish roms and ive never reset anything. it works everytime no issues
Click to expand...
Click to collapse
That's what I do and it will work. Than the next day its greyed out again When its on I've successfully transferred files before it greys out again. So I know its not completely borked. Just frustrating.
Sent from my SCH-I535 using xda premium
maybe it has something to do with resetting wallet. ive never done that. never read that you had to do that.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
if youre flashing a JBTW leak instead of an ICS rom maybe that has something to do with it. are you doing TWJB leak instead of ics? ive always done ICS
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
kennyglass123 said:
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
Sorry bout that..I just restored stock nandroid with Nfc on now it's greyed out again. I Odined stock rooted yesterday hoping that would help but wondering if I should try to Odin straight stock with a data wipe.
Really just wondering if anyone else is experiencing this.
Sent from my SCH-I535 using xda premium
you need to check NFC on when you flash teh stock rom, did you do that?
after that, not sure what to tell you. fixed NFC multiple times doing that method on a fwe different GS3s.
ddurandSGS3 said:
you need to check NFC on when you flash teh stock rom, did you do that?
after that, not sure what to tell you. fixed NFC multiple times doing that method on a fwe different GS3s.
Click to expand...
Click to collapse
Ya it works than stops. I know what your saying just like on aosp. Flash stock click it on flash again. I don't know. I remember reading about how the "secure element" in the Nfc chip could lock up but if that's the case how have I used it at all? Anyway I appreciate the help. I've had enough for the moment.
Sent from my SCH-I535 using xda premium
I was using Twrp file manager in recovery and noticed the NFC Apk. Had the VRLF stock radio after it. So I flashed back from the new blk jb leak. That seems to have fixed it. I tried to take a screenshot of the apk in root explorer but it doesn't list the baseband after the apk. like it did in twrp. Maybe I'm crazy as I'm sure one has nothing to do with the other but why was it listed like that in twrp file manager?
Edit it wasn't twrp it was settings/apps
Sent from my SCH-I535 using xda premium
Hmm some error about tapatalk sever uploading photo damn xda premium.
So I'm totally at a loss of where to go or what to even search for.
I have a verizon Galaxy s3 that I rooted and unlocked the bootloader on. I flashed a couple ROMs and now it won't connect to the network. It tells me it is in roaming mode only. I called verizon, but they said to just return the phone because it won't talk to their network.
I've read some things about "triangle away" and I kind of tried that. But it kept telling me that my flash count was 0 anyway. So it didn't do anything.
My IMEI and ICCID are correct to my sim card and phone. I originally flashed CM10 for the verizon s3 and it worked great for a few weeks. Then I tried a couple others and they worked also. Then I flashed the euroskank ROM, and that's when it no longer would connect. I went back to a previous nandroid, and still no connecting.
I don't know what the problem is, or what to search for, or where to go.
Should I try to install a stock rom. I know I keep seeing things about odin and installing the stock rom. Should I do that? That's something I haven't tried yet.
So, I tried reprovisioning the phone with *2767*3855#
And when I did that, it said sorry, your phone is not yet activated.
But I know it is, or, at least was activated. And when I call verizon they tell me it has been activated already. I don't know what to do. I'm thinking of trying to go back to stock
Same Problem
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
SpencePatriot said:
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
Click to expand...
Click to collapse
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
sin 7227 said:
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
Click to expand...
Click to collapse
Well that's good to know that you got it back working again. Sounds like it might be just be the ROM and not anything weird that we did to cause the loss of connectivity.
Thanks nertskull
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Input
halfgod85 said:
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Click to expand...
Click to collapse
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the Cyanogenmod update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Mitch90 said:
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the CM update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Click to expand...
Click to collapse
My S3 is having the same issue after a CM10 modification. Reflashing to a stock ROM fails, wiping and reflashing fails, trying a different rom on cwm fails, no backups to flash to (all result in error). So I stumbled upon this thread, read about reprovisioning, and I took it to mean input the numeric code into the phone dialer. I did that, and nothing happened. Can anyone provide insight on reprovision and how to do it? Google search on reprovision isn't giving me any hints.
If the reprovision is just failing and I've been doing it right, does anyone have any other suggestions? Really hoping my phone isn't soft-bricked with no ability to call/text.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Darthbull said:
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Click to expand...
Click to collapse
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
stuck...
I tried all the above, stock, radios, kernels, codes, ##RTN#, none of it works, my radio works cause i tried 911 and it jumped on roaming and began to make call at which point of course i hung up before letting it connect any words of wisdom... at this point just a tablet for wifi
stang68x said:
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
Click to expand...
Click to collapse
Bump
no sd wipe
stang68x said:
Bump
Click to expand...
Click to collapse
neither *2767*3855# nor ##786# wipe sd card, files on sd card stay intact
I have a galaxy note 2 on Verizon. This used to happen to me on CM 10.1 first stages but issue got fixed as the nightlies started. It only happened to me when I sometimes rebooted the phone or when the battery completely drained from 100-0% then when I would charge it and boot the phone it would show me an x and no signal bars. I would have to restore to a TW rom to get it to activate again but going into settings and switching to CDMA/LTE mode. Now I'm on ParanoidAndroid 2.99beta ROM and it still gives me that issue. Hopefully soon it will be fixed.:fingers-crossed:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
This worked for me after trying everything else. I wish I found this 4 hours ago.
wwonka69 said:
This worked for me after trying everything else. I wish I found this 4 hours ago.
Click to expand...
Click to collapse
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
wwonka69 said:
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
Click to expand...
Click to collapse
Ok it only works if you are on 4.04 as far as I can tell.
bump:good:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
Thank you buddy,
This helped me get my phone back in working order -- For those of you wondering why the "*2767*3855# is not working is because you are using the wrong flash. You must use "Official VRALG1 4.0.4" - and currently the link is down on the thread - I just googled it and found it elsewhere. I tried one of the other OTA's and it would not work. Also, do exactly as netskull described - even regarding the antenna. When using VRALG1 4.04 - The second i entered the last "hashtag (#)" it popped up another screen which helped get my phone working. I did not have to press send or anything. Kind of sucks that I lost all data on my internal card, but I DID back it up and now I will have to go through and restore. Since some people were wondering -- It did not mess with anything on the external card... It did unroot my device, however, so I will have to do that again as well.
For some reason, flashing the latest MIUI messed up my phone and put it in roaming all the time. Oh well, happy i got it working, and subscribed . Thanks once again Nertskull.
I was running slim 4.2.1 for quite some time with no problems, i loved it. I flashed 4.2.2 and my phone got stuck in NV and my phone number would come up as 000-000-3370. On first boot everything seems to be fine except that i get an error when i try to open up the play store. On my next boot is when I would see these problems. I tried everything from dirty flashing from a working 4.2.1 rom to completely formatting everything, even my external sd, and the same thing happens. This happens with every 4.2.2 rom out there. When i reboot i get stuck on the activating screen and my phone will get stuck in NV and ruim/sim wont stick no matter what i do. i don't know what else to do. someone please help!
It isn't a rom issue it is an S 3 issue that randomly occurs when flashing ROMs. You will have to flash the stock rom and reprovision your phone. I know because it has happened to me twice and both times it was with a Touchwiz ROM. You should have backed up your IMEI just in case this happens.
my imei is backed up. but why is it only 4.2.2 roms that do this?
I was able to flash back to a 4.2.1 Rom, namely pure Google for now, with no problems. but when I flash any 4.2.2 Rom the same thing happens.
All 4.2 ROMs used to do this to me.
However.
Only also happened when I flashed miui.
Now I run liquid smooth and haven't had the problem since.
sent from that young galaxy.
God bless the American people!
do u guys think I should Odin back to stock, then root, unlock, and try to flash 4.2.2?
Actually, there is an easier way
I have had this happen numerous times and it lef me to mess with my phone a little bit. I originally thought that setting it to CDMA/SIM and then rebooting would fix the problem, but I found a simpler solution to that. The last time I encountered the problem I simply set the phone to RUIM/SIM under mobile networks and then Turned on airplane mode for a few seconds then turned it off and I found my number under phone settings and everything. Try that and let me know how it goes.
Edit: Sorry, the term is RUIM/SIM, not CDMA/SIM. My bad.
hmmm, I'll definitely give that a shot later on tonight.
well I tried it, it works. but only temporarily. once I reboot it reverts back to how it was. any other thoughts?
anyone?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
try this. i had the same problem. http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2
nope, none of that works either. no matter what I do ruim/sim will not stick on a reboot on any 4.2.2 Rom. I'm really getting frustrated with this.
no one has any other solutions for me?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
Does your phone display an IMEI number?
Settings->About->Status
Don't need the number, just to know if you have it there....
Also do you still have Root/Unlocked bootloader?
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Chitala383 said:
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Click to expand...
Click to collapse
Have you done a complete factory restore through Odin? You would lose root and unlocked bootloader, but it may be faster to restore to stock, and reroot/mod than to try to find an "easy" fix. I was having some issues the other day in between a few ROM's, but I just factory restored, and restarted from "scratch". Now I am running perfect.
You may have already tried, but on page 1 you asked if you should, and I did not see a confirmation you did so.
Had the same problem... And yes, the phone must be reprovisioned. Although sometimes you can just adjust the network settings and change it from NV. That worked for me also.
Sent from my SCH-I535 using Tapatalk 2
I flashed root 66 via Odin, bootloop. flashed the ma2 stock image, bootloop. then flashed the lk3 stock image with success. but still with the same results as before.
tomorrow I'll try flashing g1 and start from scratch there. what do u guys think?
well, I odin'd back to bone stock G1, rooted with rootdebugfs, flashed cwm with ez recovery, unlocked my bootloader with ez unlock, flashed liquidsmooth 4.2.2 rc2 and guess what. same ****!!!!!!!!!!!!! i'm really getting fed up with this. someone has to have a solution to this cuz this is really pissing me off.