Related
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.
Hi there,
Since I bought GS+ few weeks ago with 2.3.3. (xx??? rom) in Latvia, I have tried several ROMs and always rooted after that from recovery mode by flashing Root.zip.
There was a problem with my def rom, about 80% of sms failed on first send, so i gave it a try for other roms.
Right now I am using rooted XXKP4 (2.3.4.) as I found it the most stable for me - no WiFi issues, but every 2nd sms still fails.
So far I tried asian SZKP6 (2.3.6), european XXKPJ (2.3.5.), XXKPG (2.3.5.), XXKPS (2.3.?). Always the same - they work fine, no sms problem on any of them above 2.3.5 (including), but always there are problems with WiFi - it drops signal and changes connection to 3G/2G. Sometimes it drops every 5-6 minutes, sometimes it drops once in a half hour.
I always wiped data before flashing and did factory reset after flashing with Odin, after that I always root it with mentioned method and restore all my apps/system data with Titanium Backup PRO.
Could you guys help me find out what is the problem?
I want to get fully working 2.3.5 or 2.3.6, without any issues, but right now I am stock with 2.3.4 because I prefer push resend my messages better than Skype video call dropouts because of auto changing internet connection type.
Thanks in advance.
the only thing i can say is had the same issues with wifi dropping and first sms of the day would faili tried all the roms including the one im using now and they all had the wifi faults UNTIL i did a full factory default and erased disk, now im using the XXKPS 2.3.6 and it works fine.
So make sure you do a fresh start after flashing your Rom.
BackDaws said:
the only thing i can say is had the same issues with wifi dropping and first sms of the day would faili tried all the roms including the one im using now and they all had the wifi faults UNTIL i did a full factory default and erased disk, now im using the XXKPS 2.3.6 and it works fine.
So make sure you do a fresh start after flashing your Rom.
Click to expand...
Click to collapse
Factory reset after flashing with this code: : *2767*3855#
Backup first your internal sdcard because the reset will erase it.
I'm also on 2.3.6 KPS and think I have no wifi drops.
And to think I mean, I have not noticed.
Sent from my GT-I9001 using XDA App
Just a question - if I backup my internal sdcard before flashing and full reset with code listed above in previous reply, can I restore (copy from PC) all my files after everything is done?
Sent from my GT-I9001 using XDA App
The same...
Tried two roms (2.3.6 and 2.3.5) which works fine for lot of people here in xda-devs.
Factory reset before, and another reset after flashing, but the same situation. Everything works fine except WiFi - when I open WiFi settings, it shows refresh (search) every 5 seconds and drops after some minutes.
I'm on KPS and havent noticed any wifi drop.
How often does it drop? Does the wifi icon disappear when it drops and reappears when it connects?
i must of just got lucky, all i did after flashing to XXKPS was a complete reboot to factory defaults from settings/privacy/factory data reset and wiped SDcard aswell when asked, i then installed all settings and apps from scratch i didnt use any previous backups.
like i said before i installed XXKPS and got wifi drop outs but this is the rom im using now and the wifi is fine now, the only thing i did diffrently was what i wrote above.
ojconcentrate said:
Does the wifi icon disappear when it drops and reappears when it connects?
Click to expand...
Click to collapse
Jep, this is how it happens - WiFi icon disappears and if connection is active, it drops (interupts d/load, skypoe, etc)
BackDaws - i can notice it before rooting and restoring my apps/sets. Last time I tried xxkps, it dropped for first time before I managed to copy root files to my sdcard, so this is not about restoring.
then just keep flashing it until you get the wifi working, im scared to flash to anything else now as that wifi bug was getting on my nerves.
are you using a Belkin Router by anychance ? ive read that changing the DHCP lease to 2 days instead of forever resolves this problem.
Try it
I'm fairly new to ROMs (this is my second). I have followed the instructions and successfully installed the ROM, modem, and update.
2 questions:
1) Wifi does not work (will not turn on). I had wifi problems on my last ROM. I have reinstalled this ROM numerous times today thinking something must have failed since wifi does not work. This seems to be unique to me since I can't find anything in the thread regarding wifi problems. Any suggestions?
I've gone so far as to use darkside superwipe as suggested in a different thread. Still can't get wifi to turn on (just sits with "Turning Wi-Fi on..." message on screen). Never errors out, just stays like that.
2) ROM Manager: Fix permissions fails. I get the following error when I select fix permissions: "An error occurred while attempting to run privileged commands!" Any suggestions?
Thanks so much for the help!
You should post your question in the ROM thread. The developer (seanscreamz) or one of the other testers will see it and be able to address your problem and help you out.
I can't post in the Dev section yet. 6 more posts and I will ask there.
starting over...
Ok, I figured I might as well make sure that my wifi woes are not a hardware issue. I've reverted back to stock Skyrocket OS to make sure wifi is available and working in stock form.
Following this link http://forum.xda-developers.com/showthread.php?t=1342348, I reverted to stock and I can confirm that wifi works in stock form.
I've also reformatted my sd card in case there is any chance a corruption on it would cause my problems.
Now going to reinstall SkyICS...
bored4long said:
Ok, I figured I might as well make sure that my wifi woes are not a hardware issue. I've reverted back to stock Skyrocket OS to make sure wifi is available and working in stock form.
Following this link http://forum.xda-developers.com/showthread.php?t=1342348, I reverted to stock and I can confirm that wifi works in stock form.
I've also reformatted my sd card in case there is any chance a corruption on it would cause my problems.
Now going to reinstall SkyICS...
Click to expand...
Click to collapse
Are you on CWM touch?
have you went into the busybox app and clicked install?
wifi broken again
I have followed these instructions here http://forum.xda-developers.com/showthread.php?t=1321582 to regain root. After getting root, I installed ROM Manager and selected "Fix Permissions". On reboot, I lost the ability to connect via wifi.
Did I miss a step?
Thanks again for holding a n00b's hand!
AT&T Samsung Galaxy S II Skyrocket Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1383
You have to install busy box
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
john: I'm sure you mean well, but I don't know what your intent was with your posted link.
crazyD: digging your avatar. I'm currently trying to decide between a G26 and XD9sc...
btw, installed and ran busybox. not sure what it did for me. I also updated ROM manager to latest. Accidentally initiated a backup from ROM manager. Will see if wifi is back after that has completed.
Edit: wifi still errors, won't connect. I'm not clear what steps I may have missed or screwed up between being stock to rooted. I will revert back to stock again and try again...
Are you running juice defender? Its giving me problems with my wifi connection!
Sent from my SAMSUNG-SGH-I727 using xda premium
I'm not running Juice Defender. At this point, I'm trying to revert back to stock form again with working wifi.
Edit: ok, reverted back to stock by doing the following
1) reboot into CWM recovery
2) factory reset x3
3) clear cache x3
4) format system x3
5) clear dalvik x3
6) format emmc x3
7) restart and pull battery
8) boot into download mode
9) push stock tar (k0kane) via Odin3 v1.85
I now have wifi again!
So now I get to try to get back to SU and CWM without losing wifi...wish me luck.
still have wifi!
OK, rooted and CWM installed. I still have wifi, which is good. I'm afraid to select 'Fix Permissions' for fear that will break my wifi.
I'm going to install Sky ICS now and see what happens.
sky ics and wifi!
OK, It took a few attempts, but I now have SKY ICS installed and wifi is still working.
I've installed the base ROM and the modem...not the updated yet. My download speeds are terrible, but at least I have wifi. I think the data speeds get better on the update.
Sean's instructions say to let the phone "cache and settle". I have no idea what that means...so will try to wait 10 minutes or so before installing the update.
bored4long said:
OK, It took a few attempts, but I now have SKY ICS installed and wifi is still working.
I've installed the base ROM and the modem...not the updated yet. My download speeds are terrible, but at least I have wifi. I think the data speeds get better on the update.
Sean's instructions say to let the phone "cache and settle". I have no idea what that means...so will try to wait 10 minutes or so before installing the update.
Click to expand...
Click to collapse
My uneducated guess with the data speeds is the modem for UCLE2. I haven't had the chance to go to LTE on SKYICS yet, but data is definitely slower on "4g" networks.
Sent from my cm_tenderloin using Tapatalk 2
quick update
Here is a quick update:
I spent some time redownloading all my apps and in general setting up the phone. I then ran the SKY-ICS update. Everything seemed to be working great.
As an added bonus, the email app in SKY-ICS syncs with my employer's exchange server! Which is so awesome. The stock ROM, and the last gingerbread ROM I had on the Skyrocket would not connect to our exchange server. I was very pleasantly surprised by that functionality.
I then lost wifi again. Wifi seems to be unpredictable and I'm not sure if it is hardware or software related. I again have wifi this morning, but didn't for the last two days. Also, my phone won't restart, it appears to get stuck in a powerdown state.The haptic buttons stay lit, but the screen is blank. I have to pull the battery to get it to restart.
But overall, I'm very happy with the performance and functionality of SKY-ICS. I will do some digging on the restart problem.
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?
Hello ladies and gents,
I purchased my girl an s3 and she has been running stock rooted for a while and wanted to try something different so I flashed cm10.1. I factory reset, cleared system, and caches. Then flashed the rom via trwrp 2.3.3 flashed gaps. Everything went successful but she lost all data. I read that it was fixed but I had to Odin root66 and dial that code to do another reset.
What can I do differently that won't lose data next time? The Verizon s3 seems more temperamental than my T-Mobile s3.
Sent from my SGH-T999 using Tapatalk 2
First thing to always do is read the OP for bugs I'm pretty sure he explained the loss of data and how to fix it.
Second would be to research the ROM you are flashing by reading comments from other flashers.
Last would be waiting for a stable version of the ROM to be uploaded.
Have fun and flash with the speed of light
But the things is I did all of those things. I am no stranger to rooting and crack flashing. I'm saying they said the data bug was fixed as of 12/24, I flashed 1/19 and it still broke data. But I guess I'll just lurk the thread... my bad for asking a question in the q/a forum...
Sent from my SGH-T999 using Tapatalk 2
Here's all the info I: have saved in case I come across this problem (again)
Fixing Data
If you flashed a CM10.1 nightly and are stuck at roaming/activating or don't have data, try any of the following (in order of simplicity):
(1) Go into Mobile Settings - Mobile Networks. Change CDMA mode to RUIM, go into airplane mode, come out, it should login to 4g in a minute. You can wait for activating to time out then skip or not install gapps until after setting the correct mobile network setting.
(2) Power down. Take out the sim card and reboot. In mobile network settings set roaming to auto and the subscription to RUIM/SIM, turn off the phone, pop the sim card back in, boot up.
If none of those work this will work for sure:
Originally Posted by Deevious88
Hallelujah! My phone has voice AND data back! (thanks to the posters above)
How to get voice AND data back:
1.) Odin the root66.tar file from http://forum.xda-developers.com/show....php?t=1762204 (the torrent version downloads MUCH faster)
2.) Open the dialer and enter *2767*3855#
3.) DONE! Voice and data should be fixed (it fixed it for me at least, and I had tried EVERYTHING else)
From there just Odin back to Jellybean following http://forum.xda-developers.com/show....php?t=1974114 and you're golden...
That's how to get back to working condition without fail... Might want to post similar instructions in the OP as dirty flashing did nothing for quite a few of us.
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fixing GPS
Originally Posted by invisiblek
GPS - it HAS been working for 98% of builds, however if you cannot get GPS to connect, possibly due to dirty flashing, the following has worked every build for me: Settings - Apps - downloaded - GPS Status - clear cache, clear data, force stop. Then open gps status back up, let it sit with gps on for a moment and see if it starts searching for signal again....if this still doesn't work (sometimes) - settings - apps - all - google services framework - clear data. This has worked 100% of the time but I try to avoid it because if you do this, you need to go open back up the play store and see if it still connects. If not, recovery - clear cache, clear dalvik usually takes care of that.
Clean install of builds has given me 100% functional gps every time.
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Unofficial CM10.1
(I know several people have posted these, I looked quickly and only found mastamoon's which is also what I am running, I'll happily post more here if I find them).
mastamoon http://d-h.st/users/mastamoon
invisiblek http://rootzwiki.com/topic/35602-rom...0#entry1058210
aerovan http://rootzwiki.com/topic/37216-uno...zw-2012-12-18/
First do this: change your CDMA Subscription to RUIM/SIM then your Roaming Mode to Automatic and then reboot.
If doesn't work, try: restoring IMEI and then Odin back to stock.
The RUIM method mentioned prior has always been what fixed my problem when experiencing the same issue as you. Also, definitely back up your IMEI if you have not yet.