Hey all, I am a noob here so please be patient and i'll try to give as much info as possible. I own a Samsung Galaxy SII LTE (SGH-I1727R) on the Rogers network in Canada. I got the great idea to root it, so that I could get rid of some of the ridiculous preloads and wasted space cause my battery seems to die really fast.
So I used the SuperOneClick root program, everything went perfectly fine during the root, superuser showed up after, everything was functioning properly. Soon I realized (as I lost wifi) that I cannot receive data. I see the phone trying to send data (green arrow) but no receiving, and cannot use the internet. Wifi works fine.
I tried all the common things, battery pop, reboots, unrooted it, re-rooted it, factory reset, the only thing I haven't tried is a firmware reset via Kies. After rooting it, my Kies quit recognizing the phone, and kept trying (and failing) to install the drivers. So I downloaded the kies from the site specifically for this phone (seemingly older version, than the fully updated Kies I had), and it gets stuck in an installing loop, asking "Do you want to upgrade your keys?" Yes... "To do that, we need to uninstall old kies", Yes.... "Do you want to upgrade?" Over and over.
So kies doesn't work. But I have tried everything else, and cannot get data to come back. If anyone has any ideas, please let me know.
EDIT: Oh yah, and I've made sure its nothing basic: packet data is on, network mode is set to proper GSM/HSPA/LTE (default)
Hi. I would change the data connect to hspa only. Reclick on data packet and reboot. If that doesn't work, you will have to reflash, the radio(baseband) . You would have to have root and install clockwork mod recovery through the app from manager and get the radio software in the forum. When you use superoneclick to root make sure you use zero rush as the option in setting or you will have problems with root on your phone
Related
Aside from my issue of apps going missing when rebooting...some even when copied right to phone memory...I am now stuck at work and rebooted my phone to find that I now have no data coverage. Internet does not work. I can call and txt and that is it.
I am running a flashed Infuse with Bionix Infinity V2 build. Firmware 2.2.1, Baseband 1997UCKE3, and Kernel Version 2.6.32.9 if that helps. I flashed it a couple days ago and this is the first time i've had this issue. I have not installed anything today either that could have created some kind of conflict. I called ATT just to make sure I still have a data plan in case some weird stuff happened and somehow got taken off and I do.
Is there anything I can try to possibly get this working asap? Thanks in advance!
RE: no data & other problems
Fee454 said:
Aside from my issue of apps going missing when rebooting...some even when copied right to phone memory...I am now stuck at work and rebooted my phone to find that I now have no data coverage. Internet does not work. I can call and txt and that is it.
I am running a flashed Infuse with Bionix Infinity V2 build. Firmware 2.2.1, Baseband 1997UCKE3, and Kernel Version 2.6.32.9 if that helps. I flashed it a couple days ago and this is the first time i've had this issue. I have not installed anything today either that could have created some kind of conflict. I called ATT just to make sure I still have a data plan in case some weird stuff happened and somehow got taken off and I do.
Is there anything I can try to possibly get this working asap? Thanks in advance!
Click to expand...
Click to collapse
Go into settings>wireless and network>mobile network and be sure to turn the packet data ON (enable packet data) It would not hurt to even turn on/enable DATA Roaming
Good luck with it...
If all fails seeing that you have other issues besides the internet/data I guess you will need to use the "Ultimate Unbrick".
I know your fone is NOT bricked but this Ultimate Unbrick method is the only one I know of which will revert your phone to 100% stock retail condition so you can have a fresh start with a 100% working phone.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251&highlight=unbrick
If you decide to use this method, be sure you follow the step by step instructions completely.
Good luck!
Misterjunky said:
Go into settings>wireless and network>mobile network and be sure to turn the packet data ON (enable packet data) It would not hurt to even turn on/enable DATA Roaming
Good luck with it...
If all fails seeing that you have other issues besides the internet/data I guess you will need to use the "Ultimate Unbrick".
I know your fone is NOT bricked but this Ultimate Unbrick method is the only one I know of which will revert your phone to 100% stock retail condition so you can have a fresh start with a 100% working phone.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251&highlight=unbrick
If you decide to use this method, be sure you follow the step by step instructions completely.
Good luck!
Click to expand...
Click to collapse
Thanks, the packet data was already turned on. I tried on/off/on and rebooted again as well. I may just end up reverting to stock and trying again although it would suck to lose everything. It's odd that I haven't messed with anything today and was working earlier. I am hoping it is just a problem in the area but I can txt/call just fine.
I'm working the graveyard shift too..this couldn't have come at a worse time.
EDIT: AT&T says there is an outage in my area and to wait about an hour.
Misterjunky said:
Go into settings>wireless and network>mobile network and be sure to turn the packet data ON (enable packet data) It would not hurt to even turn on/enable DATA Roaming
Good luck with it...
If all fails seeing that you have other issues besides the internet/data I guess you will need to use the "Ultimate Unbrick".
I know your fone is NOT bricked but this Ultimate Unbrick method is the only one I know of which will revert your phone to 100% stock retail condition so you can have a fresh start with a 100% working phone.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251&highlight=unbrick
If you decide to use this method, be sure you follow the step by step instructions completely.
Good luck!
Click to expand...
Click to collapse
Pretty sure I am going to just do the ultimate unbrick now...I lost another 4 apps when rebooting just now. I need to know if I need to return my phone or not before my 30 days is up. It did this even before rooting my phone and I move all my apps to internal phone memory.
I am overjoyed to see that there is finally an official gingerbread update that I can flash, and then a CM7 for this kernel, that doesn't have any bugs that are too annoying. However, it's been a while since I became an expert on flashing my old LG Eve. Is there a thread somewhere that outlines exactly how to do this for this exact phone and mod?
I've got a D2G, with Fission ROM. the phone is unlocked and rooted. I have an original ROM saved to flash to the phone if need be. Everything I would ever need is backed up using Titanium Backup. I've downloaded the GB update and CM7. I think I'm ready to go.
Questions:
- Is there a thread that answers all this already?
- Am I going to run into any problems being unlocked or rooted?
- Does the phone revert back to being locked once the new GB is installed? That would not be good considering I'm in Canada, not on Verizon. I bought my phone unlocked so I don't know how to just unlock it again.
- I remember using nandroid before to make a complete backup of the contents of my phone so that if I screwed up I could just go back to it seamlessly. Same thing this time around?
- I'm not completely illiterate here though, so I'm going to give it a go and you can just correct me where I am wrong. First, put the CM7 and GB files on the SD card. then do a nandroid backup of the phone. Clear data, clear cache. Then use clockworkmod to flash the GB update. then use clockworkmod again to flash CM7. then use clockworkmod again to flash gapps. Start up phone, do a complete restore with Titanium and I'll have all my apps and settings, call history and texts back. I'm probably wrong somewhere in all this, but where?
If there's not already a comprehensive thread on this, let this be it!
You will need to SBF to stock to be able to install the update.
Refer to the following for some instructions:
http://droid.koumakan.jp/wiki/SBF
http://droid.koumakan.jp/wiki/4.5.607_Firmware
http://droid.koumakan.jp/wiki/CyanogenMod
Ok, I read these all over about 5 times. So in a nutshell, these are the steps:
- use rsdlite to put your phone back to the stock firmware 2.4.330
- unroot and remove cwm
- use android recovery to install gingerbread 4.5.607
- root again and install cwm again
- use cwm to install cyanogen and gapps.
Correct?
Also, I am running fission. According to my system info it is firmware 2.4.3. I would rather skip step 1 and just install gingerbread. I am guessing I can't, but please confirm.
Sent from my DROID2 GLOBAL using XDA App
You don't need to unroot and remove CWM after flashing the SBF.
Otherwise everything's correct.
You cannot install the official Gingerbread firmware update onto a phone that is not running stock unrooted 2.4.330 without CWM and with all bundled software intact.
Note: if you need to backup your applications and configuration data, you can do so with CWM. Make a backup under Fission, then perform all those steps above, and once you're running CM7 on 4.5.607, use CWM's advanced restore feature to only restore /data.
So here I am in Gingerbread on my D2G (already further than I thought I'd get!) and you would think it would be smooth sailing from here... except I can't root it now! Is there a different technique for rooting in Gingerbread? I used Z4 before, and it worked in seconds.
OK, I figured out how to root using another thread. and when i am in adb shell I get "#" and not "$" after entering a string of commands.
But, apps think that I'm not rooted. All I need is to install CWM, but it runs into errors, presumably because I am not rooted.
The phone is in some sort of weird half-rooted state.
really weird experience with rooting. I realized that I hadn't done the additional steps where you push superuser to the phone and a couple other commands. So I did that, and then root check said i was rooted. I rebooted, and adb shell was acting like I wasn't rooted! yet root check still said I was. I was able to flash CWM and reboot, and then install CM7. Everything seems great!
except, right from the start I was getting repeated FCs for com.android.phone.
I remember that there's an issue with needing to reboot after switching to GSM... so I'm trying that now. Let's hope that stops the FCs.
So what ended up happening was, I rebooted and stopped getting the FCs for the phone after switching to GSM. So that is good. However, aside from the two minor bugs that I was prepared to live with, this is happening now:
- I have phone and SMS service, just no data. Wireless works fine, and so do GPS and Bluetooth to my knowledge.
- When attempting to select a network to register on, I get the dreaded “Your SIM card does not allow connection to this network” message. I have tried doing this with data/roaming enabled/disabled and with “only 2G” selected. I have also tried a couple of tips I found online such as removing the battery for 15 minutes and also getting a new SIM card.
- At first I was able to enter new APNs, but they wouldn’t save. I hit menu, then save, but it goes back to the APN screen and none are listed. Now, what happens is, if I hit menu, then “add new apn”, nothing happens.
I went into the telephony.db file to manually enter my APNs, and it seems that they are already there, which is good. I re-entered them all manually using sqlite anyway. This did not work. I also noticed that Verizon was listed with a “1” in current, which probably means that Verizon is my current APN. So I removed that 1 and placed it on all my rogers APN entries. Still, nothing is saved at the APN screen in settings, and I can’t enter them through that screen, either. And no data.
Suppose it turns out that this is just a bug with CM7 right now and it’s unusable for me. Obviously I don’t want to go all the way back to Fission on Froyo when I can use gingerbread. How far back into this process do I have to go? Can I just flash GB and it will overwrite CM7?
Did you make a CWM backup of your freshly installed Gingerbread? If so, just restore.
If not, I don't see how you're going to “just flash Gingerbread” without SBF'ing to 2.4.x.
Well, I have done a lot of testing and troubleshooting. I went back to the start of this whole process, and I backed up my APNs and fully tested the phone at every turn, and my conclusion is that CM7 is not friendly to APNs. There was no problem with stock Froyo or stock Gingerbread. With the working APNs that I had, I was able to use data on both. Once CM7 was installed, it was a no go.
I used a couple of apps to backup my APNs both in Froyo and Gingerbread prior to installing CM7, and when CM7 inevitably didn't allow me to use data, I tried to restore my APNs using these programs as well. They say that they worked, and it's true that if you go into root explorer the APNs are there as you entered them or restored them using a program. But it seems these APNs are not going to work unless you actually see them at the APN page in settings. And nothing I have tried up to this point has been able to make any APN show up at that screen.
I think the “Your SIM card does not allow connection to this network” message at the network operators screen, as well as my inability to enter APNs, are 100% related. I also bet there is a simple solution to it!
If anyone has any ideas about how to make an APN stick, and how to force a phone to start using it, please let me know. I'll also post this at the CM7 forum.
I rooted my Samsung Galaxy Tab Plus 7.0 tablet with the tutorial from this site:
http://forum.xda-developers.com/showthread.php?p=24736900
It worked just fine for a couple days, then today I powered up the tablet and when I unlock it, it shows a problem loading all widgets, and within a few seconds the screen goes black, then proceeds back to the unlock screen. I unlock it again and this keeps repeating.
I didn't hack anything else, just installed superuser and a couple of other root apps. Really I haven't done anything else to cause this.
I don't even have enough time to go into settings and do a factory reset.
Any ideas? Perhaps in recovery?
EDIT - I did a factory reset in recovery. Is this going to fix it back to normal? I probably won't root ever again.
It probably has no affect, but what root apps did you install?
superuser, busybox, adfree, rom toolbox (which couldnt even detect my root but I never tried anything else)... those I can remember...
Did you install CWM and do a backup?
Im not sure what that acronym is for. I am new to all this. I followed the simple instructions in that tutorial and that was it.
It seems the issue is gone since my factory reset.
I am not sure if the root is still there however.
If there are extra steps to be done after a root it would help to have them with the tutorial....
A factory reset will remove root from your phone. Rooting it in and of itself should cause no issues like you are having it has to be something you installed and I would suspect ROM Toolbox. I'm not sure this app supports teh GTab+ or even has any useful purpose for us as we have no real ROMs to flash. It also contains a ROM Manager and if its the same one by Koush then it will defintely screw up our tablets.
repo97 said:
I rooted my Samsung Galaxy Tab Plus 7.0 tablet with the tutorial from this site:
http://forum.xda-developers.com/showthread.php?p=24736900
It worked just fine for a couple days, then today I powered up the tablet and when I unlock it, it shows a problem loading all widgets, and within a few seconds the screen goes black, then proceeds back to the unlock screen. I unlock it again and this keeps repeating.
I didn't hack anything else, just installed superuser and a couple of other root apps. Really I haven't done anything else to cause this.
I don't even have enough time to go into settings and do a factory reset.
Any ideas? Perhaps in recovery?
EDIT - I did a factory reset in recovery. Is this going to fix it back to normal? I probably won't root ever again.
Click to expand...
Click to collapse
I have done this ROOT like a million times (i'm a flash junkie)... testing the CM9 roms and back to stock again.. never had an issue with ROOTing the stock ROMs..
Suggest you download the latest firmware for your device and flash using ODIN and factory reset. Repeat the flash & factory reset a few times
Maybe you have the wrong clue of what your problem is. To root your tab is just a matter of put a binary called "su" on a directory on your PATH, usually /usr/bin and set it with proper permissions. This binary gives you superuser powers, but there's nothing on it or at least in the process that installs it that makes it interfere in anything without being called.
So accidentally you did anything that went wrong or any of programs that requires root did.
Sent from my GT-P6210
kzoodroid said:
A factory reset will remove root from your phone. Rooting it in and of itself should cause no issues like you are having it has to be something you installed and I would suspect ROM Toolbox. I'm not sure this app supports teh GTab+ or even has any useful purpose for us as we have no real ROMs to flash. It also contains a ROM Manager and if its the same one by Koush then it will defintely screw up our tablets.
Click to expand...
Click to collapse
Sorry for taking a bit to reply, havent had the chance to get much PC stuff done lately.
Aaah so you think it was the culprit.... its wierd because when I tried to run the rom toolbox it shown that my tab was not rooted.
Then the problems started... as in my tab was rebooting itself and was stuck in a loop.
I did do the factory reset and then used a root checker and noticed it shown as no root access.
I have read that a factory reset does not remove root... are you sure it does completely?
I'd hate to go through another reset as I have set everything up again.
The only bug I have noticed so far with my tab is that the odd app (so far market and dolphin browser) at times I am unable to go back a page... the page just kind of flashes and stays on that page but does not go back. I end up having to restart the app.
Should I reflash with latest firmware and do a factory reset?
If so... I found this site, shall I use these instructions and firmware?
http://www.androidauthority.com/galaxy-tab-7-0-plus-p6200-update-ddkl2-honeycomb-3-2-firmware-45993/
Intro
The info on how to do this is scattered around, thought it might be good to have a post for this, was really annoying for me to get this fixed
Problem
After upgrading to the latest Cyanogenmod 10.1 (cm-10.1-20121224-NIGHTLY-d2vzw.zip), the phone will not connect to the cell network. Some symptoms of this:
- Cannot send/receive text messages
- Cannot make calls, all calls give error "Your account is not authorized to make calls to this phone number"
- On boot, activation starts ("Waiting for network...") but cannot complete
- In Settings -> About Phone -> Status, you see the following info:
-- Roaming: Roaming
-- Mobile Network State: Disconnected
-- My phone number : 000-000-0311 (or similar)
Solution
I tried a number of solutions, but the only way I've seen to fix this is to revert to stock ICS using Odin, then perform a full factory reset. Please note that you will lose ALL data, including anything on the internal storage. The SD card should not be touched. You will also lose your unlocked bootloader, although that is easily restored.
1. BACK UP any data you might need, including clockwork/titanium backups, get them off your phone
2. Follow instructions here to flash the rooted ICS image (stock.vzw_root66.tar) using Odin. The torrent is much faster to download the image.
3. If your phone goes into a boot loop (stuck on the LTE boot logo), boot into stock recovery (Vol Up + Home + Power) and clear data / factory reset
4. Boot up the phone, go into the dialer, type: *2767*3855#
5. Your phone will immediately factory reset itself
You should now have cell connectivity again, and should also have root. You can then unlock your bootloader (get v1.2 here) and finally use Clockwork to re-install another ROM.
Note that after doing the above to restore my cell connectivity, I tried to do a clean install of CM 10.1, with full data wipe and such, and I once again lost cell connectivity and had to factory reset again. It seems to me like something is very broken with CM 10.1 for the VZ S3, and until it's figured out I recommend staying with CM 10.0 (cm-10-20121216-NIGHTLY-d2vzw.zip), which does not appear to have this problem.
funkymonk101 said:
Intro
The info on how to do this is scattered around, thought it might be good to have a post for this, was really annoying for me to get this fixed
Problem
After upgrading to the latest Cyanogenmod 10.1 (cm-10.1-20121224-NIGHTLY-d2vzw.zip), the phone will not connect to the cell network. Some symptoms of this:
- Cannot send/receive text messages
- Cannot make calls, all calls give error "Your account is not authorized to make calls to this phone number"
- On boot, activation starts ("Waiting for network...") but cannot complete
- In Settings -> About Phone -> Status, you see the following info:
-- Roaming: Roaming
-- Mobile Network State: Disconnected
-- My phone number : 000-000-0311 (or similar)
Solution
I tried a number of solutions, but the only way I've seen to fix this is to revert to stock ICS using Odin, then perform a full factory reset. Please note that you will lose ALL data, including anything on the internal storage. The SD card should not be touched. You will also lose your unlocked bootloader, although that is easily restored.
1. BACK UP any data you might need, including clockwork/titanium backups, get them off your phone
2. Follow instructions here to flash the rooted ICS image (stock.vzw_root66.tar) using Odin. The torrent is much faster to download the image.
3. If your phone goes into a boot loop (stuck on the LTE boot logo), boot into stock recovery (Vol Up + Home + Power) and clear data / factory reset
4. Boot up the phone, go into the dialer, type: *2767*3855#
5. Your phone will immediately factory reset itself
You should now have cell connectivity again, and should also have root. You can then unlock your bootloader (get v1.2 here) and finally use Clockwork to re-install another ROM.
Note that after doing the above to restore my cell connectivity, I tried to do a clean install of CM 10.1, with full data wipe and such, and I once again lost cell connectivity and had to factory reset again. It seems to me like something is very broken with CM 10.1 for the VZ S3, and until it's figured out I recommend staying with CM 10.0 (cm-10-20121216-NIGHTLY-d2vzw.zip), which does not appear to have this problem.
Click to expand...
Click to collapse
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Same problem
Having this exact problem. My problem is I do not have access to a windows computer and thus cannot use Odin. I have already performed a Factory reset so I may try the way that involves removing the sim card. I dont know how more people haven't posted on this yet...
---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------
rossida said:
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Click to expand...
Click to collapse
as far as I can tell this does not work. You must have a sim card to get past the second screen in boot up. There is no other option besides to turn of your phone.
Thank you for the help! My phone as been out of commission for the past 2 days and the OP directions fixed it. However the second post did nothing to help out. Worth a shot though
Does anyone know if this can be done from a Mac?? I am a little desperate here. Ive spent most of Christmas day messing with this.
You'll have to find a Windows computer, or install a windows virtual machine using vmware fusion or parallels desktop.
will this work for us cellular??
rossida said:
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Click to expand...
Click to collapse
This has happened to me twice. The second time I used this method and it worked for me. It was only successful when I switched to the executioner 2.5 rom which was on my sd card. Thanks!
Nvm fixed it
*wrong thread*
killerkiyoshi said:
Nvm fixed it
Click to expand...
Click to collapse
How???
Okay, finally have my service back in stock touchwiz. This is what I did for anyone that cares to know: In CM10 during "activation" I pulled my sim card out, let it finish activating, powered down put sim card back in. Then I booted it back up and went to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV). THEN I did a factory reset in CM10 making it look as if I had just flashed it again. Then I booted into recovery and went back to stock TouchWiz where my 4g LTE came back magically and I could call and place texts. Not really any rhyme or reason but my service is back and I am beyond pleased. I am very nervous to flash any roms as of now I might wait til tomorrow luckily I have all my stuff backed up Hopefully it stays this way. Message me with any questions and I will help as much as I can. Merry Christmas
pupsinmytub said:
Okay, finally have my service back in stock touchwiz. This is what I did for anyone that cares to know: In CM10 during "activation" I pulled my sim card out, let it finish activating, powered down put sim card back in. Then I booted it back up and went to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV). THEN I did a factory reset in CM10 making it look as if I had just flashed it again. Then I booted into recovery and went back to stock TouchWiz where my 4g LTE came back magically and I could call and place texts. Not really any rhyme or reason but my service is back and I am beyond pleased. I am very nervous to flash any roms as of now I might wait til tomorrow luckily I have all my stuff backed up Hopefully it stays this way. Message me with any questions and I will help as much as I can. Merry Christmas
Click to expand...
Click to collapse
Yall all need to chill out. Just fix your mobile network settings, toggle airplane mode, and you'll be fine.
You have no reason to fear flashing any roms.... With common sense.
Sent from my SCH-I535 using xda app-developers app
Flash cm10.1 go to settings/networks/cdma subscriptions and change it back to RUIM/SIM. U haz data now. :thumbup:
Sent from my SCH-I535 using xda app-developers app
None of this has worked for me. I have followed the post directions and still have roaming. I am not seeing this option some of you are talking about though " wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)"... is this option supposed to be in the stock ics rom?
Update: the line had been suspended for some very odd reason
Got it working on VZW SG3 for now
This worked for me:
Reboot to recovery and fix permissions (not sure if this step helped just following some other posts) --> change mobile networks to the sim option ---> and most importantly enable National Data Roaming (this is the step that kicked over my signal)
After doing this it has started to let me call out and receive sms. My only concern is what consequences will i have with the national data roaming enabled and secondly when I am in other networks if I will get better signal; i live in a small town and get 1x so I have no idea what will happen till i get into the city but this seems to be a good fix for now. Hope this helps.
Tried all posted solutions and then some, still can't get CM 10.1 working on d2vzw
All,
I have a stock-rooted SCH-I535, and am also unable to get CM 10.1 working without losing the voice connection. It appears that my problem is corrupted NVRAM. Although my IMEI remains correct after flashing 10.1, my phone number and other info (ERI) gets corrupted. After a day of anxious attempts to fix the phone, the only fix I've found is flashing root66 (after which the phone still doesn't boot to the OS), factory reset (allows phone to boot), and then dialing factory-reset code *2767*3855#. For some reason the dialer-initiated reset seems to fix the NVRAM issue while the recovery-initiated reset does not.
After figuring out how to fix the problem, I've tried a handful of ways to get CM 10.1 working properly.
Original try: flash 10.1 over rooted-VRBLK1 using TWRP 2.3.1. After fixing by flashing root66, recovery factory-reset, and dialer factory-reset, I was nervous and made a couple backups.
used the su ; reboot nvbackup commands in this RootzWiki post.
Made a QPST backup with the instructions in this XDA post.
2nd try: factory reset, wipe data/system partitions, re-flash 10.1 with TWRP. This attempt had the same roaming/corrupted phone info result, but this time I was confident because I was armed with the two backup methods above.
I tried using the Samsung MEID RepairV3.5 in this XDA thread, but it wouldn't connect to the phone running CM10.1. I've gotten that tool to connect to the root66 image, so I know I'm following the procedure correctly. However, the developer specifically states that the tool is intended for stock images, so I wasn't surprised that it failed to work on CM 10.1.
with su privilages, I used terminal command "reboot nvrestore". I expected this to work, but it resulted in an unbootable OS. I had to flash root66 and repeat the fix process described at top.
Third try: flashed 10.1 again with TWRP 2.3.1. I tried using the QPST recovery I had created earlier. I got the phone into diagnostic mode (RMNET+DM+MODEM) using terminal commands for AOSP ROMs. For some reason I couldn't get the scripts to work, even with full permissions in the "root" directory -- the script resulted in the phone disconnecting from my computer in MTP mode, but it didn't connect in diagnostic mode. Terminal commands did the trick though -- I may be making some n00b mistake with the scripts. After typing the commands in manually and connecting to QPST, when I told QPST to "restore" the backup, it gave me an error message with incompatible phone, and if I checked the "allow phone/file ESN mismatch" box, the restore failed because the phone didn't respond to the QPST commands. I'm sure the phone was in diagnostic mode because it came up under Device Manager "ports" as depicted in the QPST instructions, so it seems like the corrupted NVRAM was causing problems with making a QPST connection.
Fourth try: TWRP update to 2.3.3.0. Same results as 2.3.1.0.
Fifth try: switch to clockworkmod touch recovery 6.0.2.3. Same result as both TWRP versions.
So, I'm pretty frustrated. I have the phone back up and running rooted-stock VRBLK3. I'd really like to get JB4.2 though, so if anyone can ID the problem, please post! I hope it's a simple fix from a n00b mistake, but after all the fruitless effort above, I expect that it's a more significant issue.
One last thought: I always rebooted into recovery to install the 10.1 image, and I never tried using the ClockworkMod ROM Manager or TWRP-compatible GooManager apps. My wife is tired of me spending the holiday weekend hunkered over my phone, so if anyone wants to try that route please let me know if it works.
The only other idea I have is to install 10.1, then try flashing the VRBLK3 baseband by itself. Again, I don't have the time to pursue this idea (or expertise to know if it's a good one), so any good insight would be appreciated. One last thought: personally, I'm not willing to wander around in voice or data "roaming" even if everything else is working fine. I rely on this phone for daily use, and am not comfortable without the radios working normally.
Happy new year!
thank you. can confrim this method to work for a verity of roms. ha.
vabeachfc3s said:
Flash cm10.1 go to settings/networks/cdma subscriptions and change it back to RUIM/SIM. U haz data now. :thumbup:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This worked, just reboot the phone after you make this change and you'll have your activated phone back with voice/data. :good:
No Service
I flashed CM10.1-m a few days ago (using this method to root and unlock bootloader http://forum.xda-developers.com/show....php?t=2046439 then flashing CM10.1-m through Odin), and my phone worked flawlessly for 2 days. It started to lag a bit during swipe-style text entry (no tracing line or predictive words appeared), so I rebooted hoping to fix the problem.
After reboot I lost all verizon service. The phone said "No Signal" or "Emergency Calls Only." The phone would not identify a mobile network, and no option for CDMA/LTE was available under mobile network settings, although verizon APN's were still identified. I think I lost my IMEI/EFS but don't know enough to be sure.
First I flashed stock VRALG1 android 4.0.4 without success. However after I flashed stock VRBLK3 android 4.1.1 my verizon service was restored.
I would really like to figure out how to keep CM10.1... touchwhiz is awful. Can someone confirm this problem can be fixed through one of the following methods? http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2&nocache=1
Also don't want to trip my flash counter... any idea at what point this would happen?
Hey Xda Devs. This is my first post to this wonderful site. (sorry if in wrong area)
Back to related topic....
I own a Samsung Galaxy SIII - (SCH-I535)
About Three or Four days ago I was sick of using my Cyanogenmod 10. And I decided to do a Factory Restore on it. (Got sick of short battery life and terrible reception)
While doing this it was great (still rooted and running cyanogenmod). Then I got a little stupid and decided I didn't want any Google search in/on my device. So I went and deleted most the apps associated with it. NOT KNOWING it would disrupt my Data / Wi-Fi / and Play Store. (Google store has Unexpectedly Stopped)
So like an idiot, I factory restored AGAIN thinking "maybe it will just go away"
No....
In fact did the inevitable and decided to take out Clockwork Mod and anything else in my SD card thinking maybe that was the reason.
(At this time it was still working ((Send/Receive Calls, Text, and Pics.))) But no data.
Then while on my break at work I put my phone into Clockwork (somehow it was still in my phone) unknowingly I seen a backup. So like any noob I went and clicked Wipe Cache + everything else then prompted with a Recovery.... Well that only made matters WAY worse....
I now sit with a phone that no matter what I do, I can only get into ODIN mode but if left to boot it shows an UNLOCKED Custom Samsung screen but sent to "System software no authorized by Verizon Wireless has been found on your phone. Please....ETC"
I have tried to flash the same way I did but no luck. I tried stock ROM. ODIN always says RESET!!! But does nothing after like it’s just a paperweight now.
I somehow now instead of having 1 custom binary download me have 3....
Everything else says CUSTOM
And Qualcomm secure boot says ENABLE
I’ve been looking for a way to bring it back to just stock ROM.... but no luck on any form, site, or anything!
PLEASE HELP! im sick of using my Droid RAZR M