SynergyROM v1.7 - MightyText not connecting - Verizon Samsung Galaxy S III

Flashed SynergyROM v1.7 last night, came back to work and tried to re-connect my MightyText and i get an error saying 'unable to connect'
rebooted into cwm recovery, backed up, full wipe, reflashed previous stock rooted, mightytext worked fine.
rebooted into cwm recovery, full wipe, reflashed synergy 1.7, redownloaded mightytext, not working.
went through various iterations of the above, still no dice.
any suggestions? wouldve posted this in the dev forum but since im a new baby deer, no can. Thanks in advance.

Related

[Q] Kinged Shooter rls 2.1 settings missing

Hi everyone, first post here. Looked around and haven't found an answer to this yet. Phone is EVO 4G
Have flashed this rom multiple times and the rom itself functions well with little to no lag. The problems arise if I do anything in recovery. Tried flashing a kernel (goldenmonkey) and wound up with endless force closes. Did a nandroid restore to a state just before I had flashed the kernel and the force closes continued. Shouldn't the restore have returned everything to the previous state with the stock kernel as that was what I had installed with the rom? That's what always happens with the other rom I have saved on my SD card.
Just a few minutes ago, I reflashed the kingedshooter rom, installed apps, etc. Was planning on trying another kernel, but forgot to put the zip on my SD card. Anyway, I did a nandroid backup (with everything working fine) and as soon as I rebooted the phone, I could not access the settings and the power control widget I had loaded on one of my home screens was gone. I couldn't make phone calls, and would get a force close if I tried to access any settings. Tried to restore to my most recent backup where once again everything was working perfectly and am still having the issues I just described. Anyone know what's going on? Thanks.
Anyone that reads this, please disregard the above. Made a nandroid after installing a theme and kept trying to go back to that. Thanks.

I think I broke it.

I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
At this point, i would suggest to do a full wipe (clear data/factory reset, caches and also format system under storage and mounts). Then flash your flavor of CM7 and while still in CWM, flash the kernel of your choice, DON'T REBOOT, but clear cache/dalvik. Reboot, let it sit for a while and you should be good.
Sent from my LG-P999 using xda premium
Luriden said:
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Click to expand...
Click to collapse
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after that you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Instaling custom kernel instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
ratza66 said:
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Click to expand...
Click to collapse
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Make sure you downloaded his CM7 version and not Stock kernel.
Luriden said:
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Click to expand...
Click to collapse
You welcome, I've added info on how to install custom kernel too
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Luriden said:
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Click to expand...
Click to collapse
You can't install custom kernel on nightly release. Use RC 7.2 and yes do the rom recovery and back it up so the next time you can just restore to any rom that works on your phone.
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Luriden said:
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Click to expand...
Click to collapse
I Think you are missing a one step, Wipe Dalvik. Ok let start from the begining,
First restore your phone to stock, let it boot. Root your phone and install CWM. Install CM7.2 RC rom and let it boot. Go back to the CWM and follow this instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
all these steps are important. I was using CM 7.2 RC with Faux's kernel without any problem and it worked flawlessly
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Luriden said:
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Click to expand...
Click to collapse
Follow this guy on YT, you will find everything there
http://www.youtube.com/watch?v=fxMnnarHaOU
Installing CM7 tutorial
http://www.youtube.com/watch?src_vi...id=annotation_334516&feature=iv&v=Cy9on64jAZs
This one is even better
http://www.youtube.com/watch?v=vUaWXM8GwUI
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Luriden said:
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Click to expand...
Click to collapse
No chance. Nothing will be left over when you wipe your phone. Your SD card is only accessed when you tell CWM to do so. Take your phone back to stock. Do it again this time try either a froyo rom or ICS rom. Then go back wipe everything and install CM7. Sometimes you have to take the long way. after flashing my phone a bazzilion time I learned this the hard way when I couldnt load EB ICS anymore. Had to run GB to get to ICS. Try it in reverse or from a step below and it should go through fine. IF it doesn't, you might have to use ICS instead, which may be stuttery, but works damn well.
DupleX01 said:
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
Click to expand...
Click to collapse
I'm wondering why he still has the issue. YOU CLEAN CACHE BEFORE FLASHING KERNEL/ROM UPDATES!!!
Sent from my LG-P999 using xda premium
For God sake, just flash a random ROM to get access to inside your phone.
1. DIAG your phone OFFLINE with v21e baseband (phone will automatically restart)
2. Let it stay for 5mins after that
3. Use your phone for 15mins
4. Root using 1Click
5. Install CWM
6. Install your ideal ROM + GAPPS (if needed) via CWM
7. Reboot
8. Go outside your living room and watch TV for at least 15mins
9. Reboot your phone into CWM and flash your ideal kernel
10. Enjoy!!!
You better know which ROM/kernel to choose from. Period.
How to upgrade/downgrade your baseband? Do some search, please!
Sent from my LG-P999 using xda premium
I'll do a flash of Froyo or ICS and possibly some baseband research tomorrow. Considering my luck getting a simple rom flash to work, I don't feel too comfortable dealing with the baseband.
A friend was brave enough (somehow) to let me root and install CM7 on his phone, he has the same phone as mine. I got CM7 7.2 RC and Faux's DM UV working like a dream on my first try. Tried it on my phone after recovering it, same problem. So it's a problem that exists deeper on my phone, not with my methods.
The NAND restores for GB and Froyo give me MD5 checksum errors, and the stock zipped rom of GB gives me an installation failed error, so I'm thinking a zipped Froyo rom won't work either, but it might be worth a shot.
Tried Weapon and MIUI too. No go. If I don't get stuck at the blue LG logo, then I'm stuck in a loop between the two LG logos or stuck at a flashing black screen. 8/10 times though it's the blue LG, I think the other errors may have actually been me forgetting to wipe my cache when I was flustered.
I'll try ICS, and hopefully won't get to a point where I have problems installing things I used to be able to, since that seems to be the pattern. After that I finally give up.
I FIGURED IT OUT! Well, sort of. For the hell of it, I downloaded CM7 7.1.0.1 through Rom Manager and it installed fine. It downloaded it to my internal SD, so I hooked it up to my PC to copy the 7.2.0 RC1 to my internal SD and tried installing. No go.
So I went on my phone's web browser and redownloaded 7.2.0 RC1 that way directly to the phone. It works. So somehow, roms I copy from my PC to the phone appear to not work, yet apps and kernels still do. I'm running CM7 7.2.0 RC1, downloaded through my phone's web browser, with Faux's DS UV kernel, copied from my computer. After four days, I finally found a workaround, so I'll stick to it. Whatever works, I guess. I can try reinstalling my USB drivers, but I can probably get by with a combination of the phone's web browser and ES File Manager w/ LAN if need be.

Can't restart or shut down the phone

Hi,
I have flashed new ROM ( [ROM]SKY-ICS 4.2F6-2.6.1 (8/4)(UCLF6 Base) AT&T-OFFICIAL ICS.PROJ MARGARINE, W/ G-NOW).
Phone works fine, exept that I can't shut down or restart the phone - it just freeze.
thanks
I had same problem before... was from backup cwm when I do restaro backup... I just flashed same rom again never I get this problem
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
i had similar problem on previous version of sky ics. i went through the normal process of format system, clear cache, wipe davilic, but regardless of the version of sky ics, it would never shutdown/reboot. (got tired of holding down volume up/down and power to hard boot).
I ended doing ODIN back to att stock and verifying it shutdown/reboots fine.
Then i went through and installed skyics again. BAMMM it works fine afterwards...
Sounds like you had a bad install. Do a factory wipe and clean reinstall of SkyICS. If that doesn't fix it, take yourself back to stock, re-download (and check MD5s on) all files you need to install Sky, then reinstall it.
A good rule of thumb I use if a clean wipe fails, or something just doesn't feel right afterwards, is, "When in doubt, return to stock."
Thanks! problem was solved, I reflashed the stock rom then the custom one
Thanks! problem was solved, I reflashed the stock rom then the custom one
It happens usually due to an old CWM, so if it happens again update it.

[Q] Help!! No call/data connection on Verizon GSIII after flashing CM10.1-20121221

Hello XDA,
Sorry for the long post but I am desperate!
The first ROM I ever flashed was CM 10 M2 which ran well and went without any problems. For this I used CWM. I found a stable nightly early in December and decided to update. I also wanted to store my backups on my external however, so I switched to TWRP and created a new backup of my stock TouchWiz rom using TWRP then backed my CM10 M2 up just in case. I flashed the update without wiping the data (factory reset) but did wipe the dalvik cache. This worked fine; all my apps were still there as well as my background. So when GooManager told me there was a 10.1 update for my Rom I thought why not try it out. I figured this was a big update so I wiped dalvik and did a factory reset. After flashing I ended up in a loop of "com.android.something or other has stopped" which turned into "setup wizard has stopped". The homescreen would not load. Fine. Booted into recovery last night after this and reinstalled my latest backup of the nightly I had been using for about 20 days. Seemed OK but the "android activation" screen was taking forever so I pushed home, plugged my phone in and passed out. I Woke up this morning and tried to send a text but it wouldn't send. Tried to call and I couldn't. Now I have restored every recovery I had (Stock, M2, Nightly) multiple times and same problem except that in stock I get a roaming charge warning. I was sure returning to stock would solve this. Does anyone know what I can do? Im not sure exactly how to factory reset but am willing if thats what it takes.
Thanks a ton!
Pups
Try here: http://forum.xda-developers.com/showthread.php?t=2065285. It has worked for several people.

RESOLVED! [Q] No network access after trying to install Cyanogenmod. Phone dead now.

I tried to install the latest and greatest version of cyanogenmod this morning but once it got to the activating part, it would not activate. I tried it a couple times, rebooted, wiped, installed and tried again, but nothing was working.
So, I had enough and wiped everything and restored my previous ROM's backup (CleanROM).
But now, even CleanROM can't connect to the mobile network. When I try to do the *228 thing, I first got an error something about a invalid SIM card. So, I rebooted and now the error message says "A Verizon Wireless SIM card has activated your service and updated your phone's roaming capabilities".
What's weird about that is that it doesn't even call, just pops up that message and I still have no network!
Could it be possible that have the wrong radio now? Anyone know what it's supposed to be and where to download the correct one?
Right now: I535VRLG7
What the f happened? What did cyanogenmod do to my phone??? Please help, my phone is dead in the water at this point.
Was it 10.1.0.1? I tried flashing it myself and data would not work either, first time ever happened to me since running CM. Apparently others are having issues with it as well reading the thread on the dev section. I restored my backup of 10.1.0 and it was fine again thankfully. Also you aren't supposed to *228 on a 4G phone, might want to do a search but others have said that can mess up your phone as well.
NeoMagus said:
Was it 10.1.0.1? I tried flashing it myself and data would not work either, first time ever happened to me since running CM. Apparently others are having issues with it as well reading the thread on the dev section. I restored my backup of 10.1.0 and it was fine again thankfully. Also you aren't supposed to *228 on a 4G phone, might want to do a search but others have said that can mess up your phone as well.
Click to expand...
Click to collapse
Yes, that's the version I was trying to install.
I created a backup of CleanROM that I was running before flashing, but that's not working now either. Network is dead for me.
I am having the exact same issue. Flashed the newest "stable" build of CM 10 and now the phone won't activate. Flashed CM10 RC5 and phone won't activate. Installed my backup I made before I flashed and it will not make/receive calls either. I tried searching the g+ community but did not see anything.:crying:
Jerniganc said:
I am having the exact same issue. Flashed the newest "stable" build of CM 10 and now the phone won't activate. Flashed CM10 RC5 and phone won't activate. Installed my backup I made before I flashed and it will not make/receive calls either. I tried searching the g+ community but did not see anything.:crying:
Click to expand...
Click to collapse
I've tried a bunch of stuff so far, but no luck fixing this. I'm waiting for some files to copy and I'm going to try again. This sucks. I'll post if I have any luck with a fix.
I'm having the same issue. What Baseband are you guys running?
Laxidasical said:
I'm having the same issue. What Baseband are you guys running?
Click to expand...
Click to collapse
I'm on I535VRBMB1, but I was on I535VRLG7 for some reason. Upgrading did not help.
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
I hope I don't have to do that also. I posted in the cm g+ community and I'm waiting on an answer atm. Jumped in irc chat but got no help.
Sent from my Nexus 7 using xda premium
---------- Post added at 06:48 PM ---------- Previous post was at 06:36 PM ----------
ned4spd8874 said:
I've tried a bunch of stuff so far, but no luck fixing this. I'm waiting for some files to copy and I'm going to try again. This sucks. I'll post if I have any luck with a fix.
Click to expand...
Click to collapse
ned4spd8874 said:
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
Click to expand...
Click to collapse
Found this post on G+. Looks like it is a known issue that a radio didn't make it into the build.
https://plus.google.com/110116306685366816729/posts/2wnDGwd9UtX
Jerniganc said:
Found this post on G+. Looks like it is a known issue that a radio didn't make it into the build.
https://plus.google.com/110116306685366816729/posts/2wnDGwd9UtX
Click to expand...
Click to collapse
But I've flashed the radio and it didn't work for me. I tried two different ones and neither worked.
ned4spd8874 said:
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
Click to expand...
Click to collapse
No need to take your phone back to verizon.....The way to fix it is to Odin back to I535VRALF2. Once stock dial *2767*3855# let it do it's thing when it finishes reboot. After that 4G will be back. Re root and flash CM 10.1.0 NOT 10.1.0.1
Well an update on this. I flashed MIUIv5 found here http://forum.xda-developers.com/showthread.php?t=2232800 and it booted up and worked like a champ. From there I booted back into CWM and wiped, etc and installed a fresh RC5 and gapps. When the phone booted up the phone would take calls but would force close. From here I booted back into CWM, again wiped and then installed my RC5 backup I made this morning that was working and crossed my fingers. Well when the phone booted up it is working 100%!
I guess my question is what did 10.1.0.1 break that a flash to MIUIv5 fix?
Same issue. I had to wipe everything, format everything (maybe wasn't needed), flashed the newest nightly, latest baseband (something something F1), and gApps of course. I then had to check the "mobile network" settings and change it to SIM card (instead of NV) then reboot, and it worked.
The "stable" builds have been less stable than the nightlies lately, dunno why...
i'm also having this issue guys, I've noticed that my imei is 0. I've tried punching in the codes to get the utility, but can't get anything working...totally lost
RESOLVED!
It was a PITA, but I got 4G back with CM!
This is how I did it, but be forewarned that your device will be wiped, and it will not be a quick fix.
I first used this post (Section 5) to Odin back to stock.:
http://forum.xda-developers.com/showthread.php?t=1762709
Once I was back to stock, the network was still not working. So I dialed "*2767*3855#", it did something, rebooted and then 4G worked!
After that, I was able to follow the same guide from above (Section 1) to root the device, unlock the bootloader and install a recovery.
Once I was at that point, I installed CM from recovery. I had wanted to install the cm stable version 10.1.0, however I failed to copy that to my SD card before I started this whole process.
I had just moved and don't have many of my "tools" (i.e. sd adapters), so I couldn't even download it on my computer and copy it over. Oh, I also performed a factory wipe at this point as well as format the davlik and system...oops. So, yeah, couldn't simply boot it back up easily to copy the files over...got ahead of myself.
Anyways, I kept my fingers crossed and installed the only one that was on the sd card which was the nightly from 6/29. The good news is that worked!
I have since installed the latest nightly (6/30), because why the heck not? I was already on the previous, so it "shouldn't" hurt, right????
Nope, didn't hurt!
So, now I am running the latest nightly with full network access!
Whew, what a pain! Hope this helps you guys!
ned4spd8874 said:
RESOLVED!
It was a PITA, but I got 4G back with CM!
This is how I did it, but be forewarned that your device will be wiped, and it will not be a quick fix.
I first used this post (Section 5) to Odin back to stock.:
http://forum.xda-developers.com/showthread.php?t=1762709
Once I was back to stock, the network was still not working. So I dialed "*2767*3855#", it did something, rebooted and then 4G worked!
After that, I was able to follow the same guide from above (Section 1) to root the device, unlock the bootloader and install a recovery.
Once I was at that point, I installed CM from recovery. I had wanted to install the cm stable version 10.1.0, however I failed to copy that to my SD card before I started this whole process.
I had just moved and don't have many of my "tools" (i.e. sd adapters), so I couldn't even download it on my computer and copy it over. Oh, I also performed a factory wipe at this point as well as format the davlik and system...oops. So, yeah, couldn't simply boot it back up easily to copy the files over...got ahead of myself.
Anyways, I kept my fingers crossed and installed the only one that was on the sd card which was the nightly from 6/29. The good news is that worked!
I have since installed the latest nightly (6/30), because why the heck not? I was already on the previous, so it "shouldn't" hurt, right????
Nope, didn't hurt!
So, now I am running the latest nightly with full network access!
Whew, what a pain! Hope this helps you guys!
Click to expand...
Click to collapse
Yes, this just worked for me..however I look to be roaming completely when still in Stock
luniz7 said:
No need to take your phone back to verizon.....The way to fix it is to Odin back to I535VRALF2. Once stock dial *2767*3855# let it do it's thing when it finishes reboot. After that 4G will be back. Re root and flash CM 10.1.0 NOT 10.1.0.1
Click to expand...
Click to collapse
This worked for me.
Thanks!
I'm on vacation and tried to flash 10.1.0.1 and got hosed on the the radio connection. Nothing would work. Found an old nightly, 6/21 I believe, on my external SD card. Flashed that bad boy and I'm up and running again. Will do more trouble shooting when I get home in a few weeks and have my PC in front of me.
Sent from my SCH-I535 using Tapatalk 2
Back to RC5
I had a similar issue, upgraded to 10.1.01 and lost all data connectivity. Wiped clean and tried to upgrade again, then I could not get past the network activation screen.
Wiped and went back to a backup of RC5 and it restarted with less issues, but I still needed to go and correct the Mobile Network RUIM/SIM settings before I got data back.
RC5 has been solid, so I'm going to stick to it until there's a fix for 10.1.01.
this didnt work for me

Categories

Resources