Related
My brother has had his Shift for over a month now and just recently it stopped making/receiving calls and texts.
The first day he got it, I rooted it (it had 2.2), put CM7 on it, and x99 kernel. This is the same setup my Shift, and my friend's Shift have.
Whenever he tries to make a call it says "Your authentication code could not be verified"
Should I hard reset this, call Sprint, un-root, or what?
Thanks.
PS: I rebooted it, and had it shut off for 30min before turning it back on. Should I do a battery pull? That would be slightly tricky since he has the Otter Box case on it.
You don't have to unroot. Just flash a Sense based Rom. Update your Profile and PRL. Then flash back to CM7. Don't Nand back when your done updating your PRL and Profile. That will just put you back where you were.
prboy1969 said:
You don't have to unroot. Just flash a Sense based Rom. Update your Profile and PRL. Then flash back to CM7. Don't Nand back when your done updating your PRL and Profile. That will just put you back where you were.
Click to expand...
Click to collapse
Now when I flash a Sense ROM, I need to wipe the data and cache right? Update the stuff, then flash CM7, gapps, and kernel right?
Just wanna make sure.
doratheconquistadora said:
Now when I flash a Sense ROM, I need to wipe the data and cache right? Update the stuff, then flash CM7, gapps, and kernel right?
Just wanna make sure.
Click to expand...
Click to collapse
Correct.. Do a full wipe, data/cache/dalvik (can't hurt to do it multiple times) Flash a Sense ROM and update PRL and Profile. Wipe EVERYTHING again and flash CM7, gapps and kernel.
Ok. So I downloaded the lastest Mik ROM
Wiped the data and cache. Used CWM to install Mik from the SD card.
Updated the Profile and the PRL.
Made a call to my Shift, rung once then gave me the same "Your authentication code could not be verified message again."
What do I need to do?
doratheconquistadora said:
Ok. So I downloaded the lastest Mik ROM
Wiped the data and cache. Used CWM to install Mik from the SD card.
Updated the Profile and the PRL.
Made a call to my Shift, rung once then gave me the same "Your authentication code could not be verified message again."
What do I need to do?
Click to expand...
Click to collapse
While your still on a Sense ROM, call Sprint and have them refresh your device.
crump84 said:
While your still on a Sense ROM, call Sprint and have them refresh your device.
Click to expand...
Click to collapse
Yeah that's what I'm doing now.
prboy1969 said:
You don't have to unroot. Just flash a Sense based Rom. Update your Profile and PRL. Then flash back to CM7. Don't Nand back when your done updating your PRL and Profile. That will just put you back where you were.
Click to expand...
Click to collapse
+1. Right this is what i did when i was experiencing the same problem, and it worked..
kevowanj said:
+1. Right this is what i did when i was experiencing the same problem, and it worked..
Click to expand...
Click to collapse
Yeah but it didn't for me :/ That's fine though, Sprint got his phone working again
Sent from my Speedy with the XDA app
---------- Post added at 01:48 PM ---------- Previous post was at 01:22 PM ----------
Well it's just one problem after another.
Text and calls work again. I wiped data and cache, then flashed the ROM, gapps, and the kernel.
But now the Wifi is broken...
Clicking on it just says Error.
Now what?
doratheconquistadora said:
Yeah but it didn't for me :/ That's fine though, Sprint got his phone working again
Sent from my Speedy with the XDA app
---------- Post added at 01:48 PM ---------- Previous post was at 01:22 PM ----------
Well it's just one problem after another.
Text and calls work again. I wiped data and cache, then flashed the ROM, gapps, and the kernel.
But now the Wifi is broken...
Clicking on it just says Error.
Now what?
Click to expand...
Click to collapse
What ROM and Kernel are you using? Also, try rebooting and see if you still get the error with WiFi
crump84 said:
What ROM and Kernel are you using? Also, try rebooting and see if you still get the error with WiFi
Click to expand...
Click to collapse
CM 7.0.3.1 and x99.
The same one my phone is using, and the one he was using before. I rebooted and it still just says Error.
I'm going to wipe data/cache, reflash the ROM. Reboot. Wipe cache and flash gapps. Reboot. Wipe cache and flash kernel. Reboot.
That should work then right?
doratheconquistadora said:
CM 7.0.3.1 and x99.
The same one my phone is using, and the one he was using before. I rebooted and it still just says Error.
I'm going to wipe data/cache, reflash the ROM. Reboot. Wipe cache and flash gapps. Reboot. Wipe cache and flash kernel. Reboot.
That should work then right?
Click to expand...
Click to collapse
That should work, just when you do a full wipe the first time it's best to wipe a few times. Also, I usually let my ROM settle in just a bit before I flash a custom kernel.
This happened to me a couple of days ago. i was running Cyclonic 1.1. Here are the steps I did to fix it.
1. Made a Backup.
2. Wiped everything (except sd of course).
3. Flashed a sense rom.
4. Chatted with sprint and they fixed it.
5. Then wiped everything again.
6. And finally restored my ROM.
And everything is working fine now.
Is this the same as the "error 16" issue? My sister got a new shift about a week ago, I downgraded, rooted and flashed it to cm7 right away, and it was fine for a couple of days before not letting her call or text, just saying "error 16".
I called sprint, they did something on their end, then it worked for six hours before doing the same thing. I called them again, tech support said he forced a refresh on all the servers the previous tech hadn't, then it was fine again for a day before getting the same issue. Third call, fixed for twelve hours. During the second call I flashed to mikshifted, wiping everything very well beforehand, updated the profile and prl before sprint fixed it and I went back to cm7.
The fourth call fixed it again, but broke 3g data. Phone failed with error 16 again today and the lady at sprint, upon being told that it was running CM7 said that until I put the stock rom back on, it's going to keep having the same problem. I don't think that's right, or no one else would be able to run an aftermarket room. Any ideas, people?
Just flash the latest nightly.
Mystery solved on my error 16 issue, anyway. Turns out when I flashed the froyo engineering build downgrading from 2.3 to be able to root, I didn't realize it downgraded the radios. My super smart boyfriend figured it out, and newer radio has no problem now keeping authenticated with Sprint.
e: never mind, it worked for about two and a half days and then error 16'd repeatedly again. Flashed to x99's stock rom, we'll see what happens there.
I was going to install openOptimus on my Optimus One, so I made a backup, wiped mostly everything then partitioned the sd card (512MB ext and 0MB swap) and transferred the backup and the rom back to my sd with an adapter. Then I went to install the zip, but it delivered this message:
E:Can't open /sdcard/update-openOptimus-build-2.202.1-thunder-ciaox-signed.zip (bad)
Installation aborted.
I tried redownloading the zip, which didn't work, so I tried a different one which also didn't work. So I gave up and tried restoring, but that didn't work either. Now I have a phone with nothing to boot into but CWM, and no way to install anything new. I have no idea how to fix this and my phone is useless until I do, so what should I do?
It looks like you'll have to start from scratch again. Use the kdz updater. And download the stock firmware for your phone. When you re-root the phone, make sure you reformat your sd card (slow format) before anything. Then you have the absolute latest version of clockwork installed. The same thing happened to me but with a couple reboots it seemed to read my card. But if this isn't the case for you, then google up those items and start allllll over.
Sent from my T-Mobile G2 using XDA
Thanks for the answer, I appreciate it. But how can I get kdz updater to work on my phone if I can't get past clockworkmod?
Seems simple, but you might also want to try another card. I have to admit to having annoyed myself more than once by not checking to make sure an SD card was in fact good BEFORE driving myself crazy trying everything else.
Doesn't sound good... Redoing all that isn't fun either..
Try downloading the ROM using another web browser on your computer just in case the download gets corrupted.
Its pretty simple..there's a button combo to get into emergency mode!! Google it because I forget lol. Then just update it through kdz while its in emergency mode...all fixed
Sent from my T-Mobile G2 using XDA
Btw when u get your phone up and running. Hit that thanx button
Sent from my T-Mobile G2 using XDA
Thanks a ton, I thought it was done for. Got stock back, rerooted and hopefully it'll work when I update CWM and try to install a custom rom.
Okay, flashing the same rom I was trying before is not working. Same problem. Restore is working now, so at least I won't have to use kdz again. Any possibility that I need a specific CWM to flash the current version (2.202) of openOptimus? Cause I have the latest CWM, but openOptimus was last updated in August.
qs96 said:
Okay, flashing the same rom I was trying before is not working. Same problem. Restore is working now, so at least I won't have to use kdz again. Any possibility that I need a specific CWM to flash the current version (2.202) of openOptimus? Cause I have the latest CWM, but openOptimus was last updated in August.
Click to expand...
Click to collapse
Haha! Grrrreat! your up and running again! When you get a chance check out some of my vids on youtube.....xavicivic
---------- Post added at 02:46 AM ---------- Previous post was at 02:43 AM ----------
xavicivic said:
Haha! Grrrreat! your up and running again! When you get a chance check out some of my vids on youtube.....xavicivic
Click to expand...
Click to collapse
Oh and as for that. Flash the latest version. Ummm check the website or get rom manager. It should be there. Before u install the rom. be sure you wipe data, cache, dalvick cache and your good to go from there
So I left Apple, came to Android, rooted my VZW GS3. First time I've ever done anything like this, so I'm new to it. I backed up EVERYTHING using TiBu, did the IMEI backup, Full system/image backup using CWM, unlocked bootloader, etc. Then I flashed to Synergy r46 (august 20th - yesterday's release).
Now I'm at work and my back-up pulled my contacts via Verizon's server, but how do I get back EVERYTHING else? SMS/MMS logs, call logs, apps, app data, etc? Do I need to download TiBu again (fresh from google market) and then load my backups off my Ext-SD card, or what? I guess I'm a bit confused as to where my TiBu items were even stored/saved...I assume it was the ExtSD card, otherwise I would have lost them all upon flashing to Synergy, correct?
Any help to get all my apps and data back on my newly Synergized phone would be awesome!!!! Thanks in advance!!!
Yes download titanium and then point it to the directory you had your back ups saved to (its sd card by default, and which is your phone storage btw) then tab to backup/restore click the check, then once your app data populates, and select run next to restore apps and data.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Sent from my SCH-I535 using Tapatalk 2
I used titanuium backup pro to back up all my Apps and system data. And when I flash a new rom I just redownload titanium pro and it automatically restores all my Apps and system data. It is the easiest app I have used. So to answer ur question.....back up ur apps with titanium then after flashing a new rom go and redownload titanium and restore your system data and apps or just apps alone if that's what u prefer? Does that answer ur question or would u like more detailed instructions?
Sent from my SCH-I535 using xda app-developers app
Welcome to android!
Sent from my SCH-I535 using Tapatalk 2
Another very nice feature of Titanium Backup is its ability to pull data from CWM nandroids. There have been a few times where I was quick to flash a new rom without doing a backup of my apps. This has saved me much time from having to re-flash the nandroid backup, backup via TB, then re-flash to the new rom.
voodoomanx said:
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Click to expand...
Click to collapse
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Weioo said:
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Click to expand...
Click to collapse
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
dan_joegibbsfan said:
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Click to expand...
Click to collapse
I'm fairly certain I did "wipe data/factory reset," I just wasn't sure how it was labeled when I typed that out, but that's really ringing a bell. I think I may have gotten the errors before (using ROM Manager) because I hadn't factory reset? Seems to me I'm good to go! However, my question regarding TiBu still remains.
Edit: In regards to informing you about r46, I'm not sure what to report as I've never used a previous Synergy and have no idea how to compare, other than to the rooted stock ROM. I have heard reports of battery life being worse than the stock ROM, and I can confirm this. I've barely used the phone since I flashed to Synergy and it's dropped 15% battery life in ~3 hours. Seems faster than before but I'm unsure.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
dan_joegibbsfan said:
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
Click to expand...
Click to collapse
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I used the EZ-unlock app in the play store. I did see that a custom kernel was loaded however when i flashed back to my nandroid (stock rooted) I am back on the orignal kernel. Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I agree I have yet to have Synergy boot loop although I'm still on 1.7. I would try to wipe cache and dalvik cache and see if that helps or you could be over clocking to high.
Sent from my Transformer TF101 using xda premium
nguyenvn said:
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
Click to expand...
Click to collapse
I don't know the answer to that specifically. All I know was that I was stable before another modification I made (that said it wouldn't work but I tried it anyway). Since restoring from backup and reloading Synergy and theme I have not seen any weird rebooting anymore.
nguyenvn said:
Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
Click to expand...
Click to collapse
I'm not familiar with that method. I've only used Odin, even when I did have to redo everything I used Odin to stock de-bloated rooted .md5 then CWM'd from there.
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
nguyenvn said:
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
Click to expand...
Click to collapse
That may very well be the issue. 1.9ghz is a very aggressive overclock, and i wouldn't be surprised if was unstable on a good number of phones. Synergy's supposed to boot at 1.5ghz max by default - I don't know whether that was successfully implemented. I personally think it's silly to OC such a capable phone, anyway. Back in the days of the Droid 1, an overclock from the stock 550mhz to 800mhz-900mhz was an enormous improvement. Today, the only thing OCing the S3 gets you is a <10% improvement in Quadrant, more heat, possible instability, and no perceptible difference outside of those silly synthetic benchmarks.
Anyway, in this thread, there seems to be a fair bit of confusion as far as what's what in the android partitions. I'll give you a short rundown.
"aboot" is what's referred to here as the bootloader. It checks to see whether the next partition in the boot sequence, "boot", is authorized. When you unlocked your bootloader, you overwrote aboot with a version that does not perform that check.
"boot" contains your kernel. If your ROM has a custom kernel, it contains a boot.img to overwrite boot.
"system" is the meat of the OS. This is primarily what ROMs flash.
"data" contains all of your apps and settings. When you perform a factory reset, you're reformatting data. If you're flashing a ROM that is significantly different from what you're on now, some of those old settings and data can cause errors, force closes, random reboots, and boot loops. When in doubt, wipe data before flashing a new ROM. When going from one version of a ROM to a newer, very similar version of the same ROM (nightly to nightly), you probably don't need to wipe data, but make a backup just in case. dalvik-cache is also in data; if you wipe data, you've automatically wiped the dalvik cache. It's redundant to wipe data and then wipe dalvik cache.
"cache" is just that, the cache partition. Clearing it won't make you loose anything, at least not anything Android won't silently replace.
So far it seems to be pretty stable on r50. I installed system tuner and brought it down to 1.5 Ghz. I'm not sure why 1.9 is set to default. Doesn't seem like a good idea to me. Thanks all for the help/advice.
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
I don't know if I missed a step or not, but every app and settings screen now takes about 20-30 seconds to open, booting takes 3-5 minutes. The phone is set up with the same ROM, kernel, apps, etc. as a few weeks ago when it was running super-fast.
I reflashed this version of CM 11 which had worked perfectly for me for about a month (this is a Samsung Galaxy Blaze S 4G):
cm-11-20150119-NIGHTLY-t769.zip
I was downgrading back to that after trying a nightly that made staticky lines all over my phone and made it lock up constantly...
When I reflashed, here's what I did (after backing up with TiBu):
In recovery I wiped to factory
Cleared the cache and Dalvik cache
Formatted /system and /data
Flashed the zip of CM 11 from my external SD
Flashed the zip of GaPPs from the external SD
Rebooted
Rebooted fine, I installed TiBu and Link2SD and started restoring apps/moving to 2nd SD card partition.
The phone is much much slower than stock. I don't know what the difference is... can someone please give me a checklist to try or tell me what I might have done wrong in the re-flashing process?
kanjigirl said:
I don't know if I missed a step or not, but every app and settings screen now takes about 20-30 seconds to open, booting takes 3-5 minutes. The phone is set up with the same ROM, kernel, apps, etc. as a few weeks ago when it was running super-fast.
I reflashed this version of CM 11 which had worked perfectly for me for about a month (this is a Samsung Galaxy Blaze S 4G):
cm-11-20150119-NIGHTLY-t769.zip
I was downgrading back to that after trying a nightly that made staticky lines all over my phone and made it lock up constantly...
When I reflashed, here's what I did (after backing up with TiBu):
In recovery I wiped to factory
Cleared the cache and Dalvik cache
Formatted /system and /data
Flashed the zip of CM 11 from my external SD
Flashed the zip of GaPPs from the external SD
Rebooted
Rebooted fine, I installed TiBu and Link2SD and started restoring apps/moving to 2nd SD card partition.
The phone is much much slower than stock. I don't know what the difference is... can someone please give me a checklist to try or tell me what I might have done wrong in the re-flashing process?
Click to expand...
Click to collapse
Hi
There are newer versions of CM11 t769 up already.
You should wipe cache and dalvik after restoring your apps. If it doesn't help, make a clean installation of cm and try if the speed is better. Restoring apps via Titanium Backup while using Link2SD can easily cause errors. May be you have reinstall apps without restore. Also new partitioning of your sd card could help.
LS.xD said:
Hi
There are newer versions of CM11 t769 up already.
You should wipe cache and dalvik after restoring your apps. If it doesn't help, make a clean installation of cm and try if the speed is better. Restoring apps via Titanium Backup while using Link2SD can easily cause errors. May be you have reinstall apps without restore. Also new partitioning of your sd card could help.
Click to expand...
Click to collapse
How do I choose a version of CM to use?? This is new to me, just rooted for the first time last month. I don't know how to choose... I was using that one I mentioned above for a month with zero issues, then upgraded to a new nightly, but had to downgrade back due to problems and that was where my issue here started...
I did wipe cache and Dalvik after restoring my apps, and I did repartition my SD card as Link2SD wasn't working for me after reflashing (I got a new beta version of Link2SD from the developer that worked perfectly).
kanjigirl said:
How do I choose a version of CM to use?? This is new to me, just rooted for the first time last month. I don't know how to choose... I was using that one I mentioned above for a month with zero issues, then upgraded to a new nightly, but had to downgrade back due to problems and that was where my issue here started...
I did wipe cache and Dalvik after restoring my apps, and I did repartition my SD card as Link2SD wasn't working for me after reflashing (I got a new beta version of Link2SD from the developer that worked perfectly).
Click to expand...
Click to collapse
The CM11 builds are sorted by date. Newest build CLICK HERE are always on the top. Latest is 02/23. Keep in mind that CM is still under develpoment and may not run stable.
LS.xD said:
The CM11 builds are sorted by date. Newest build CLICK HERE are always on the top. Latest is 02/23. Keep in mind that CM is still under develpoment and may not run stable.
Click to expand...
Click to collapse
Should I pick the newest build then, and reflash with that? I see there's a stable one for CM 10 for my phone, but it's from 2012...
Should I go with something other than CM? I'm just confused at this point. I like Kitkat and would like to stay with that if feasible (my stock phone was ICS).
kanjigirl said:
Should I pick the newest build then, and reflash with that? I see there's a stable one for CM 10 for my phone, but it's from 2012...
Should I go with something other than CM? I'm just confused at this point. I like Kitkat and would like to stay with that if feasible (my stock phone was ICS).
Click to expand...
Click to collapse
I haven't tested the builds as i don't have the phone, its usefull to read the CM11 thread for your phone to check out bugs. You can try newer builds, but theres no guarantee that everything works. All in all you should go for newer versions from time to time
LS.xD said:
I haven't tested the builds as i don't have the phone, its usefull to read the CM11 thread for your phone to check out bugs. You can try newer builds, but theres no guarantee that everything works. All in all you should go for newer versions from time to time
Click to expand...
Click to collapse
Hmm. My build was stable, I upgraded to a new one, and my phone stopped working. Going back isn't working either.
CM 10.0 is listed as a stable release, I'm wondering if that would be better (i.e. less time spent wiping and reflashing repeatedly) than a new nightly for CM 11?
kanjigirl said:
Hmm. My build was stable, I upgraded to a new one, and my phone stopped working. Going back isn't working either.
CM 10.0 is listed as a stable release, I'm wondering if that would be better (i.e. less time spent wiping and reflashing repeatedly) than a new nightly for CM 11?
Click to expand...
Click to collapse
CM10 = Android 4.1.2
CM10.1 = Android 4.2.2
CM10.2 = Android 4.3.1
CM11 = Android 4.4.4
CM12 = Android 5.0.2
CM10 means you have NO bugs, everything runs stable at the cost that you have a really old rom. If you don't like maintain your phone continuisly its a good choice. I really like trying new stuff, so i flash nearly every new build of used roms / kernels for my phones. So I would stay at CM11. But thats just my personal opinion. By the way you don't need to create backups with Titanium Backup all the time. Just make a backup with your recovery. After installing a new rom, use Titanium Backup with the option "Extract from nandroid backup" to restore your apps. On previous phones I also used tools like Link2SD or Int2Ext, but after some time it always caused problems and never ran 100% stable and fast, so think about if you really need it.
LS.xD said:
CM10 = Android 4.1.2
CM10.1 = Android 4.2.2
CM10.2 = Android 4.3.1
CM11 = Android 4.4.4
CM12 = Android 5.0.2
CM10 means you have NO bugs, everything runs stable at the cost that you have a really old rom. If you don't like maintain your phone continuisly its a good choice. I really like trying new stuff, so i flash nearly every new build of used roms / kernels for my phones. So I would stay at CM11. But thats just my personal opinion. By the way you don't need to create backups with Titanium Backup all the time. Just make a backup with your recovery. After installing a new rom, use Titanium Backup with the option "Extract from nandroid backup" to restore your apps. On previous phones I also used tools like Link2SD or Int2Ext, but after some time it always caused problems and never ran 100% stable and fast, so think about if you really need it.
Click to expand...
Click to collapse
Ack. Well... I like Kitkat a lot. I might get the latest CM11 nightly and new GAPPS and try that first.
I have so little memory, kept running out of space and that's why I use Link2SD. But thanks for the advice on TiBu, I did make a Nandroid backup last night from CWM.
kanjigirl said:
Ack. Well... I like Kitkat a lot. I might get the latest CM11 nightly and new GAPPS and try that first.
I have so little memory, kept running out of space and that's why I use Link2SD. But thanks for the advice on TiBu, I did make a Nandroid backup last night from CWM.
Click to expand...
Click to collapse
PA GApps are quite good and still up-to-date. Use "PICO" to save some space.
LS.xD said:
PA GApps are quite good and still up-to-date. Use "PICO" to save some space.
Click to expand...
Click to collapse
That looks great, thanks very much!
I'll post back here once I get my phone straightened out in the next couple of days to say what happened, in case it helps someone later.
Possibly stupid question - do I need to do anything with the kernel or pit if I'm just installing a new ROM? That was only for rooting, right?
kanjigirl said:
Possibly stupid question - do I need to do anything with the kernel or pit if I'm just installing a new ROM? That was only for rooting, right?
Click to expand...
Click to collapse
Kernel is always included in the new "rom". So everytime you flash a rom, you automatically flash the kernel with it. PIT is the partition table of the phones partition. As long its not clearly necessary, DON'T ever change it!
Got it, thank you for your help!
So last night I wiped the phone and flashed the latest CM 11 (from yesterday) and the Pico package from PA-GApps. The phone is now super-fast again. I restored a few key apps to try out for the next day or so before restoring the rest, but so far so good, everything is back to normal. Thank you so much for the help.
kanjigirl said:
So last night I wiped the phone and flashed the latest CM 11 (from yesterday) and the Pico package from PA-GApps. The phone is now super-fast again. I restored a few key apps to try out for the next day or so before restoring the rest, but so far so good, everything is back to normal. Thank you so much for the help.
Click to expand...
Click to collapse
Sounds great
Quick question - if this thread is still open. The phone's been fine since I flashed CM 11 and Pico GApps, until this morning, when it now does 'Android is Upgrading' every time I boot and every user app crashes as soon as it's opened. I have all auto-syncs and auto-updates disabled, and haven't added any user apps to the phone since Wednesday.
Do I need to flash again, and then have to go through the restore process all over? Or could it be an app causing this? I'm not sure where to look for a source of the problem.