Database Info

Problems with switching ROMs

I am having a problem with switching ROMs on my sensation which just started a few days ago. I am currently running ARHD 3.1.1 and it is very stable and I have had no problems whatsoever, but like many here, I like trying out different and new ROMs. Anyways, I did a backup and installed ARHD 3.6.2, and it was forcing close on several apps, and kept getting soft reboots, so I tried RCMix's, and it would load and automatically install some apps and settings that I had on my previous ROM, and it was working fine, but then I started getting soft reboots when I would open any app, so I tried about 2 other ROMs (S3n5eay/Pyramid3D) and same thing, so being fed up I restored my backup and then I began to have superuser problems, so I unistalled updates, cleared data, and still was unable to gain root access. I kept clearing data, installed superuser 2.3.6 then 3.02 and finally got root again, but everytime I reboot I lose root. I then again tried different ROMs, and same thing is happening. I have used superwipe script, ARHD's wipe script, P3D wipe script, formated from CWM, and no matter what, I am still unable to keep a new ROM and keep losing root with my backup. I'm sorry for a long post, but can anyone please help me figure this out. I have upgraded ROMs many a times in the past on this phone and others, and have never experienced these problems, so can someone please help me.

I kinda had the same problem with you, with that being root was the problem. But the ROM's are pre-rooted so that shouldn't be a problem. Try to flash the root file again, until it is succesfull flashed.

Thanks. I'll go ahead and try that.
Sent from Sensational toy running ARHD 3.1.1

Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.

West0000 said:
Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.
Click to expand...
Click to collapse
Well for the most part everyone downloads different software. For that just one of the factors that make us all somewhat "different" this is why everyone has some sort of problems here and there.
Most times a fix can be a reboot or reinstall of the app. Even clearing of caches helps because of data conflicts on the phone. Especially when someone like me that flashes different ROMS, that's why nandroids and backups are key so that if you fudge up your phone, you can always revert back to your nandroid.
And for all the people who are trying to revert back to their nandroid after flashing a different rom, you need to use the wipe data scripts in ARHD or Coredroid to reformat the ext4 before reverting your nandroid. Just a FYI.

All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.

Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.

cbrvnm said:
Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.
Click to expand...
Click to collapse
Keep trying different ROMs and different strategies of when you wipe/restore stuff. It's quite interesting that theoretically identical phones can have different responses to the exact same actions. 2 people can install a ROM in the exact same way and for 1 it will work, the other it won't. You just gotta work it out until you figure out how to manage your particular issues.

Yeah, I hear you. It's just very frustrating when in the past I have switched ROMs on all the phones that I have ever owned without any problems until now. But I'll try different methods and see what happens. I appreciate everyones input. Thanks. Oh, and if anybody has any other suggestions, please, share.

Ok, I was able to get Pyramid3D v0.8.0 working so far. I flashed with superwipe about 3 times then installed the ROM. I did not sign into my account, and installed my apps from titanium first, and then signed in. I got several reboots with setcpu so I unistalled it. I also get a few market fcs. Now the problem that I have is that I installed the 4EXT recovery and my phone is unable to play my music files through any of the music players. I am able to open them with astro, but not music player. But I guess I'll try to figure this one out now. Thanks for the advice.

The Janitor Mop said:
All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.
Click to expand...
Click to collapse
Good post. I didn't realize I should be doing so much wiping even before restoring a backup.
Incidentally, I'm kicking myself now, but in the excitement of flashing my first custom ROM, I forgot to backup my original system. Doh. It's the only time I haven't backed up before changing ROMs, but that's arguably the most important backup to make.

[Q] No SMS on Roms other than Stock GB

Greetings, all. Long time reader, first time posting.
I had recently flashed the HFS and EB ICS roms, and both were running without issue. Then, out of the blue, I stopped receiving SMS. I could still send, but could not receive. I had read on the HFS thread that a few others had experienced this issue. After searching various threads and forums, I couldn't find a solution. After a re-flash of both HFS and EB didn’t fix the problem on either, I flashed a couple of GB roms, and was still unable to receive SMS. Finally, I restored back to Stock GB and SMS worked fine.
I am sometimes able to receive SMS on ICS when WIFI Calling is active, but it is inconsistent.
I’ve tried the following to remedy this issue, with no success:
CWM>Wipe Data, Cache, and Dalvik, Flash rom and Gapps.
CWM>Wipe Data, Cache, and Dalvik, Format Data, System, and Cache, Flash rom and Gapps.
Same steps as above, but with G2x Scrubber (sometimes scrubbing twice) thrown into the mix.
Re-downloading roms, in case of file corruption.
Fixing permissions before and after first boot.
Master reset before and after first boot.
GetRIL.
SMSC Update.
APN delete, restore, manually enter, etc.
Tried multiple SMS apps (Stock, GO, Handcent).
Flashing Gapps after first boot.
Skipping Google account setup on first boot.
I followed all rom installation instructions, including waiting ten minutes before touching the phone after first boot.
I suppose the only thing I haven’t tried is flashing a different Kernel after flashing the rom. My only other thought is to flash the Stock recovery, then re-flash CWM and try it all again.
If anyone has any suggestions, your assistance would be greatly appreciated.

Battery pull?

iArtisan said:
Battery pull?
Click to expand...
Click to collapse
If only it were that simple; but, no, I tried that as well.

Unfortunately I don't have anything to add other than I'm having the same issue with ICS and CM7 roms. I can receive SMS on MIUI and Bionix and have gone through the same troubleshooting steps. I'll add that I've tried a different SIM as well...no dice.
I saw someone post on another thread that they resolved this issue through T-mobile customer support, but I'm skeptical.
EDIT: Maybe I'll at least save you some time...I also tried going all the way back to stock recovery like you mentioned with no luck.

akelty said:
Maybe I'll at least save you some time...I also tried going all the way back to stock recovery like you mentioned with no luck.
Click to expand...
Click to collapse
Thanks. After reading that, I didn't bother trying. I'm happy to say I did a warranty excahnge and ICS is running beautifully on my new G2x, though I still wish I could've figured out what the issue was with the last one. Thanks again for your response and trying out that fix.

If anybody's still following this thread I found a solution for GB roms that cannot receive SMS. I had trouble with EaglesBlood and tried flashing the Trinity kernel...viola! Getting all my texts now.

New to Verizon s3

Hello ladies and gents,
I purchased my girl an s3 and she has been running stock rooted for a while and wanted to try something different so I flashed cm10.1. I factory reset, cleared system, and caches. Then flashed the rom via trwrp 2.3.3 flashed gaps. Everything went successful but she lost all data. I read that it was fixed but I had to Odin root66 and dial that code to do another reset.
What can I do differently that won't lose data next time? The Verizon s3 seems more temperamental than my T-Mobile s3.
Sent from my SGH-T999 using Tapatalk 2

First thing to always do is read the OP for bugs I'm pretty sure he explained the loss of data and how to fix it.
Second would be to research the ROM you are flashing by reading comments from other flashers.
Last would be waiting for a stable version of the ROM to be uploaded.
Have fun and flash with the speed of light

But the things is I did all of those things. I am no stranger to rooting and crack flashing. I'm saying they said the data bug was fixed as of 12/24, I flashed 1/19 and it still broke data. But I guess I'll just lurk the thread... my bad for asking a question in the q/a forum...
Sent from my SGH-T999 using Tapatalk 2

Here's all the info I: have saved in case I come across this problem (again)
Fixing Data
If you flashed a CM10.1 nightly and are stuck at roaming/activating or don't have data, try any of the following (in order of simplicity):
(1) Go into Mobile Settings - Mobile Networks. Change CDMA mode to RUIM, go into airplane mode, come out, it should login to 4g in a minute. You can wait for activating to time out then skip or not install gapps until after setting the correct mobile network setting.
(2) Power down. Take out the sim card and reboot. In mobile network settings set roaming to auto and the subscription to RUIM/SIM, turn off the phone, pop the sim card back in, boot up.
If none of those work this will work for sure:
Originally Posted by Deevious88
Hallelujah! My phone has voice AND data back! (thanks to the posters above)
How to get voice AND data back:
1.) Odin the root66.tar file from http://forum.xda-developers.com/show....php?t=1762204 (the torrent version downloads MUCH faster)
2.) Open the dialer and enter *2767*3855#
3.) DONE! Voice and data should be fixed (it fixed it for me at least, and I had tried EVERYTHING else)
From there just Odin back to Jellybean following http://forum.xda-developers.com/show....php?t=1974114 and you're golden...
That's how to get back to working condition without fail... Might want to post similar instructions in the OP as dirty flashing did nothing for quite a few of us.
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fixing GPS
Originally Posted by invisiblek
GPS - it HAS been working for 98% of builds, however if you cannot get GPS to connect, possibly due to dirty flashing, the following has worked every build for me: Settings - Apps - downloaded - GPS Status - clear cache, clear data, force stop. Then open gps status back up, let it sit with gps on for a moment and see if it starts searching for signal again....if this still doesn't work (sometimes) - settings - apps - all - google services framework - clear data. This has worked 100% of the time but I try to avoid it because if you do this, you need to go open back up the play store and see if it still connects. If not, recovery - clear cache, clear dalvik usually takes care of that.
Clean install of builds has given me 100% functional gps every time.
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Unofficial CM10.1
(I know several people have posted these, I looked quickly and only found mastamoon's which is also what I am running, I'll happily post more here if I find them).
mastamoon http://d-h.st/users/mastamoon
invisiblek http://rootzwiki.com/topic/35602-rom...0#entry1058210
aerovan http://rootzwiki.com/topic/37216-uno...zw-2012-12-18/
First do this: change your CDMA Subscription to RUIM/SIM then your Roaming Mode to Automatic and then reboot.
If doesn't work, try: restoring IMEI and then Odin back to stock.

The RUIM method mentioned prior has always been what fixed my problem when experiencing the same issue as you. Also, definitely back up your IMEI if you have not yet.

[Q] GPS working on EOS4 TF101 B93?

Hey everyone,
I would have posted this in the dev area for the EOS4 JB4.2 ROM section, but I'm not yet allowed to post there. Yesterday I decided to finally take the plunge and root my stock Asus TF101 running ICS 4.0.3, then get JB on there. I've got a Samsung GS3 on JB, so I figured with Asus not going to release anything for the old dog, I'll do it myself *insert Major League reference here: (EFF YOU JOBU...I DO IT MYSELF)*
Anyways...From stock, I used the one click root method which worked great. I then installed Goo.IM and loaded the latest TWRP recovery 2.3.2.3. In addition, I downloaded the latest EOS4 TF101 build which is 93. (http://tinyw.in/vq6z). I also made sure to grab the latest TF101 GAPPS. (http://tinyw.in/b4kI), and finally, downloaded the latest Kat Kernel which is here: http://forum.xda-developers.com/show....php?t=1985882
So...after backing up my apps and data (which for me, seemed like a waste of time, Google downloaded everything for me anyway) I went into TWRP, wiped the caches, wiped the internal sdcard, did a factory reset, then installed the EOS4, gapps, and katkernel, and then rebooted.
Everything came up fine...got everything going, installed, etc. All looked pretty good except I can't seem to get the GPS to work. The system is finding my location based on my WiFi. DOes anyone have any ideas on how I can get the GPS working...or know if it does considering the version I'm now running?
Many thanks in advance.

Did you wipe the system partition prior to flashing?
When changing ROMs I always wipe the cache, davlik, system and factory reset. I do not always wipe the internal. And even when updating to a new version of the ROM I wipe both caches and the System.
I am running TeamEOS Preview B145 (beta to the 94 release) from timduru and my GPS works fine. In about 2-3 minutes I have 9+ satellites and a 15M accuracy.

Thanks for the reply! Darn it... I was following instructions but obviously not well enough. I completely missed the system option. DARN IT ALL TO HECK.
Any ideas on how I should proceed at this stage? I'd like to get that working, but not sure I feel like nuking it again. I will if I have to...I just don't want to volunteer for that!

I think I got the GPS going. I downloaded a GPS test app named, 'GPS Test' (It's not just a clever name!) from Google Play.
I turned it on and the TF101 found about five sats within a couple of minutes down to 30ft precision. I went back inside and opened my trusty dusty Accuweather app and it found my location via GPS without issue.
Not sure...but maybe it had to build its list first? I dunno. Regardless, I think its sort of working. I open Maps and it does find me, but it takes quite a bit longer than it normally did...even when in the house.

CarbonRom Help

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!