Related
I have a Nexus S 4G w/ Sprint, rooted w/ Clockwork recovery. I'm running into problems using custom ROMs. Flashing any ROM goes fine; however the next time I reboot, my lockscreen PIN won't work, and it looks like I've been signed out of my Google account (based on an alert in the notification bar). I've tried CM7, BugglessPete's GRJ90 stock ROM, and ROM v1.1.1 ... tried a couple different kernels too. Each time I flash I do a full wipe, and everything seems peachy until I reboot the phone... so then I have to reboot into recovery and restore my stock backup nandroid. The new radio I flashed seems to work though.
So basically I've always resorted back to just using stock, which really doesn't bother me since Gingerbread + ADW is more than fine IMO. However now I wouldn't mind updating to 2.3.5, without losing root. And I would like to use CM7 when the next stable release comes out...
Thoughts? Thanks!
When you run cm7 or any other rom are you installing gapps and setting everything up again?
When u install a new rom you start with a fresh phone no saved info till you sign into Google.
Sent from my Nexus S 4G using Tapatalk
cc82 said:
I have a Nexus S 4G w/ Sprint, rooted w/ Clockwork recovery. I'm running into problems using custom ROMs. Flashing any ROM goes fine; however the next time I reboot, my lockscreen PIN won't work, and it looks like I've been signed out of my Google account (based on an alert in the notification bar). I've tried CM7, BugglessPete's GRJ90 stock ROM, and ROM v1.1.1 ... tried a couple different kernels too. Each time I flash I do a full wipe, and everything seems peachy until I reboot the phone... so then I have to reboot into recovery and restore my stock backup nandroid. The new radio I flashed seems to work though.
So basically I've always resorted back to just using stock, which really doesn't bother me since Gingerbread + ADW is more than fine IMO. However now I wouldn't mind updating to 2.3.5, without losing root. And I would like to use CM7 when the next stable release comes out...
Thoughts? Thanks!
Click to expand...
Click to collapse
when you do a full wipe, your settings get restored to factory settings. thats what a full wipe is, a factory reset. if you are just updating a rom, do not wipe. like if youre just updating to a newer cm, dont wipe. just update on top and your setting will stay. if youre updating from one rom to another completely different rom, then you have to wipe.
simms22 said:
when you do a full wipe, your settings get restored to factory settings. thats what a full wipe is, a factory reset. if you are just updating a rom, do not wipe. like if youre just updating to a newer cm, dont wipe. just update on top and your setting will stay. if youre updating from one rom to another completely different rom, then you have to wipe.
Click to expand...
Click to collapse
No I'm talking about flashing a new ROM, not just an update. And it works at first - I sign into google, restore my apps, etc. The problem arises the next time the phone reboots (no flashing or anything); after the reboot, my lockscreen code no longer works, as in I can't get past the lockscreen and into my phone, and it looks like I've been signed out of my Google account.
Guys, I have a huge problem. I installed DPI Modder Pro the other day and set to 160. Everything was cool until I realized I could not make a call after installing 7/1. I see the time increasing and the other person I'm calling is getting the call but I can't hear anything, sometimes though its just stuck on "dialing" yet the other person's phone is ringing. I luckily backed up right after installing the 6/30 nightly but I can only use the phone after the first boot from a restore. If I reboot, calls are gone again. Can't make them, can't get them. I flashed back to stock via Odin and was able to repeatedly reboot and have phone access with rogers 2.3.5 stock. I did a clean CM9 install and like usual, the first boot ran the call no problem but after a reboot, nothing. I don't know what else to try. I've fixed permissions, wiped with CWR, you name it. I'm stuck on 6/30 and I can't power down or reboot or I have to restore to get calls back.
Please help. PLEASE.
copene said:
Guys, I have a huge problem. I installed DPI Modder Pro the other day and set to 160. Everything was cool until I realized I could not make a call after installing 7/1. I see the time increasing and the other person I'm calling is getting the call but I can't hear anything, sometimes though its just stuck on "dialing" yet the other person's phone is ringing. I luckily backed up right after installing the 6/30 nightly but I can only use the phone after the first boot from a restore. If I reboot, calls are gone again. Can't make them, can't get them. I flashed back to stock via Odin and was able to repeatedly reboot and have phone access with rogers 2.3.5 stock. I did a clean CM9 install and like usual, the first boot ran the call no problem but after a reboot, nothing. I don't know what else to try. I've fixed permissions, wiped with CWR, you name it. I'm stuck on 6/30 and I can't power down or reboot or I have to restore to get calls back.
Please help.
Try installing a custom from like embryo for Samsung galaxy s2 skyrocket and install it and apply a radio, the developer has a list of the radios which are compatible. Afterwards make sure your data is turned on sometimes when I turn off my phone and reboot my settings get rearranged to where I can't use the web with 4g etc. I hope either of this two things help you out mate
Good luck.
Click to expand...
Click to collapse
Thanks man. I love CM9, things were going perfectly with the nigntlies and all of a sudden this. It's such a kick in the balls man, from laughing it it up with the sickest ROM to not being able to power the phone off. I'm at a loss here, I've tried everything I can think of. Like when you flash stock with Odin then do a clean install of CM9 you'd think the problem would be gone. Nope.
Try out embryo. You'll like it
It works, its fast, you get S voice, and you get the newest touch wiz launcher if your a fan.
---------edit------------
Wrong post above. I am sry mate I hope you find a way to fix it. Make sure you wipe cache and dalvik. However, their is a way to fix it and I hope you find it.
Samsung Galaxy s2 Nuclear Rocket - Embryo 3.2 [UCLE2 BASE]
iPhone 4S - Gave it away, not cool enough
iPhone 3GS - Went for a Swim
Dog - Custom Rom [Golden Retriever] [BEAR2 BASE]
I went from loving this phone to wanting a bus to drive over it. This is bull****.
You can't lower the dpi to anything lower than 190 on cm based ROMs
Sent from my SGH-I727
u do realize its ur own fault right lol? this is a well documented issue, the phone.apk won't work with anything below 190 dpi, thus the reason for ur distress. Turn it up, or search for a modified phone.apk that will work at that dpi that was kicking around in the cm9 thread, but you'll have to look a waaayz bacl
No dude, you don't get it. I've wiped. I've Odin back to stock, full wipe all the way. I rebooted a few times on rogers ics stock and it worked. I then installed cm9 from the ground up using the chopsticks guide. It went perfectly, then, after reboot, boom, no calls. This is with 240dpi in tact.I can text, wifi, data, etc. no problem. But phone, nope. Any reboot of any kind kills the phone, regardless of dpi. I have the modified phone.apk, no difference.
pls help
copene said:
No dude, you don't get it. I've wiped. I've Odin back to stock, full wipe all the way. I rebooted a few times on rogers ics stock and it worked. I then installed cm9 from the ground up using the chopsticks guide. It went perfectly, then, after reboot, boom, no calls. This is with 240dpi in tact.I can text, wifi, data, etc. no problem. But phone, nope. Any reboot of any kind kills the phone, regardless of dpi. I have the modified phone.apk, no difference.
Click to expand...
Click to collapse
Same problem here. .did u find solution?? Pls help
miroslavpena said:
Same problem here. .did u find solution?? Pls help
Click to expand...
Click to collapse
From a reboot I always open up my browser and let it load a webpage, followed by opening up Google Play and letting it load. Then I open the phone and test a call. 9/10 times it works doing it that way. I think the radio isn't loading first like it should be or something. Either way, that's my workaround for this phone I hate/love.
Im back to stock 4.0.3 and now workes fine
Sent from my GT-I9100 using xda app-developers app
NOTE: This is for the Verizon Wireless Samsung Galaxy S3 SCH-I535
Since I'm a new member I wasn't allowed to post this into the developers forum and before I continue: YES, I have searched valiantly for a fix to my particular problem and I spent the entire day new years and most of the day today trying to get CM10.1 to run on my SCH-I535 but ran into problem after problem. Every time I installed any version of CM10 or higher I ran into multiple problems: mainly being that I wasn't able to attain signal, the keyboard wouldn't load or there would be multiple problems with initial setup including having to restart during install so many times I gave up. In the past two days I have Odined back to stock at least 15+ times trying to get CM to run and now that it finally is I believe this is worth sharing.
Before I continue I should mention that your phone should be properly working so if you're in stock and you can't make phone calls or your IMEI is messed up then none of what I'm about to mention is going to work. After you Odin to stock using Root66.tar (http://www.megashare.com/4384479) then type *2767*3855# to reset to factory defaults everything should be running correctly. If not you may have bricked your phone or you have bigger problems for which I cannot help you and I apologize. There's also a torrent file available of the above stock tar file that downloads much faster here: http://forum.xda-developers.com/showthread.php?t=1840030.
So I assume, before I start this, that if you're on these boards you know how to properly root, unlock and flash then recover your phone through CWM 6+. If you do not know how to do this, then you will need to before continuing on.
Use this link: http://forum.xda-developers.com/showthread.php?t=1762709
Now follow Section 1 and pay attention to detail because if you don't you can mess something up and end up having to backtrack which can take valuable time and be amazingly frustrating.
Once these things are done you will need to reboot your phone back out of Recovery mode so you can properly move the necessary zip files onto your internal SD card.
Download CM10 Stable, you can find this here: http://get.cm/?device=d2vzw&type=stable
And download Gapps 4.2.1 here: http://www.teamandroid.com/gapps/ (I used version gapps-jb-20121212-signed.zip)
Put these files on your internal SD card and use EZ Recovery to Flash and then Reboot Recovery, I need to mention as well that when I dragged both of these zip files onto my internal SD I had EZ Recovery open while doing so. I don't know if that had anything to do with it but I thought it was worth mentioning. Clear the cache and data/factory reset then install CM10 followed by Gapps that you installed on the SD earlier.
Once you boot up you should have the phone working but the keyboard will constantly flash a message that it can't run, don't worry about that right now. Now download a nightly version of CM10.1 located here:http://get.cm/?device=d2vzw&type=nightly
(I used cm-10.1-20121231-NIGHTLY-d2vzw.zip)
Now put this on your internal SD card as well and hold the power button for 2 seconds and press restart then select recovery. Now that you're back into the recovery menu CLEAR ONLY CACHE then install the new CM10.1 nightly you just put on your internal SD and then re-install Gapps 4.2.1 from before and reboot. This all worked for me and writing this message is the first thing I wanted to do afterward to make sure no one has to go through the frustration and heartache of constantly failing at installing the ROM they want. I hope this helps at least one person, if you have any questions I will try and answer them to the best of my knowledge but I'm fairly new to all of this.
Or you can just flash CM10.1 first and do this.......
Tap the 4 corners of the screen to bypass activation screen then go into settings> more> mobile networks> and change CDMA Subscription to RUIM/SIM and System Select to Automatic then reboot...
Click to expand...
Click to collapse
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
x714x said:
Or you can just flash CM10.1 first and do this.......
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
Click to expand...
Click to collapse
I have everything working properly now but I wish I would've known this was the matter that would've fixed my problem without all these extra issues. Now my phone app is crashing in the 12-31-12 version of CM10.1. It just suddenly started happening and I can't seem to get around it.
Bosli said:
I have everything working properly now but I wish I would've known this was the matter that would've fixed my problem without all these extra issues. Now my phone app is crashing in the 12-31-12 version of CM10.1. It just suddenly started happening and I can't seem to get around it.
Click to expand...
Click to collapse
Clear it's cache APPS > ALL > PHONE APP > Clear Cache.
x714x said:
Or you can just flash CM10.1 first and do this.......
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
Click to expand...
Click to collapse
What are the correct settings?
I have been doing this a while... and I was already on the 10.0 stable build. So I flashed the 10.1 nightly... Now Play Store closes immediately after opening. I have tried to uninstall and install from .apk without success. CWRM opens and closes immediately , also uninstalled and reinstalled from .apk without success (You can get to it from booting to it with the phone off ). My Gmail app and account nowhere to be found. My attempt to go back to 10.0 were unsuccessful.
Hi all. I've had an issue for a few weeks now. I have apps that are constanly locking up and force closing on my phone. I'm currently running Jelly Beans 11 with a rooted and unlocked GS3.
All different apps force close: gmail, play store, kik messenger, system processes. It seems it's not centralized to gapps for instance.
I've installed Beans 5, 6, 8, 9 once. 10 about 2 times, and version 11 i think 3 times. Each time I do a delvik cache wipe, a cache wipe, and a factory reset via CWM. Some times even the initial setup wizard will lock up after first boot.
I've tried flashing different modems as well, and i'm currently on the newest verizon one, the K3.
If anyone has any information on how to fix this it would be much appreciated. Even a full phone wipe or something... I'm going to try clean rom and CM 4.2 tonight.
In a seperate issue, that may or may not be related:
I'm currently in iraq and i'm using the world phone exploit to get cell service and data here in Baghdad. It used to work great, but now the data connection will be connected, but no data will upload or download for long periods of time. For example i could send a kik message while connected to EDGE network, but it might take an hour for it to actually send. It didn't used to do this...
All things considered i'm wondering if I actually physically damaged the phone somehow...
If I haven't provided enough information, please let me know and i'll be happy to reply.
Ok, i tried CM 4.2 and there weren't any lockups. But i couldn't keep the rom, doesn't seem to be any way to get cell service. it won't let me change the band to global.
Going to try clean rom now.
Clean rom works fine as well...
So why would Jelly Beans ROM, that's worked fine for quite a while for me, through various versions of ICS and JB, to suddenly cause apps to force close and general instability?
I've checked MD5's and they're correct...
I think i still need a few more posts before i can post in the dev section as well.
Any help is appreciated, thanks
Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
+1
fixing permissions is a must after a flash/restore.
ok i'll try installing beans again and using fix permissions afterwards.
Thanks
still not working
Ok, i've tried fixing permissions and i'm still having problems. Gapps has stopped working... System UI has stopped working... I followed the above posts exactly.
Any other suggestions?
Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
gapps was the term that the phone said when it crashed. But no i'm not flashing the gapps, they're included on most of the roms like Jelly Beans 11. I've had a few different gapps force close, like the store and gmail. but i've also had the system ui and kik force close.
Sorry man, it's beyond my knowledge. Never had a bunch of apps stop working that fixing permissions or a clean install didn't fix.
Sent from my SCH-I535 using xda app-developers app
How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.
SlimSnoopOS said:
How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.
Click to expand...
Click to collapse
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?
Icewolf69 said:
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?
Click to expand...
Click to collapse
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.
SlimSnoopOS said:
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.
Click to expand...
Click to collapse
I just did a fresh install of 10, including cache, delvik, factory reset, system partition, and after first boot i went back and fixed permissions. I'm still getting force closes. media service, google play, etc. I don't have many apps on it yet to see what else will force close since i'm not using titanium backup to restore anything. Everything is fresh and coming from the play store...
I should be hitting 10 posts soon so i'll be able to try and post in the beans thread, or the dev section. But any other ideas would be appreciated. Thanks.
I also seem to be getting a lot of "invalid file" and "file couldn't be downloaded" when i try to install apps from the store. Not sure what this means
Beans 12 came out today and I tried installing that and i'm getting the same issue.
Tomorrow i'm going to do a full wipe to stock verizon image. and go through the unlock and root motions unless someone has any more ideas.
Thank you for the help so far, i appreciate it.
I did a complete stock OTA flash last night to verizon's jelly bean, and went through the root and unlock process again. flashed beans 12, and i'm still getting the same error.
I'm on beans 6 right now and it's working great. Going to try changing a few settings in 12 to see if it works and then maybe see if 10 works.
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
That's pretty much it
Unfortunately that's pretty much it. Your phone information should eventually stick (dunno why, but it does eventually) but if it doesn't then try another clean install. (btw have you made a backup of your imei, that might help a little as well.) I've had this problem many times and these work for me pretty much every time.
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
IamMark70 said:
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
Click to expand...
Click to collapse
ive been having this issue when i tired both roms so i ended up on cleanrom and then went over to beans for now due to it been base off of clean rom and having the asop look and feel of a aosp rom and the features of touchwiz and the stabilizability of it
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
IamMark70 said:
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
Click to expand...
Click to collapse
yep its pretty good rom i like it. im kinda having a issue with my picture messages though but probably had a dirty flash when i chose the aosp mms. if you like touchwiz also check out cleanrom its a great stock rom best stable rom and pretty great battery life as well and beans rom i think is based off clean well your welcome hope you enjoy the beans rom aslo i had issues with the sim card to so your not alone
IamMark70 said:
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
Click to expand...
Click to collapse
I downloaded Liquid Smooth 2.4, and it finally addressed the issue of the activation screen popping up after every reboot. So I'm extremely happy and loving the ROM!