OK, probably something silly I am not aware of so I hope it does not turn out to be.
Device HTC One X International.
CWM : v5.8.4.0
HBoot : 1.36.0000
So I have just changed my ROM from Cyanogen Mod 10.1.3 to SlimBean build 2.2 of Slim Bean 4.3.1. I have jumped from few ROMs over the past year without any issue apart from the know ones.
Anyway I did a backup of the Cyanogen 10.1.3 I was using, reset the data, wiped the cache and Dalvik and installed SlimBean.
The issue I am having is when I advanced restore the data from my previous Cyanogen ROM backup like I have done with each ROM change to keep apps and authenticators,etc; whenever I try to go into the security settings it basically crashes (Settings has stopped working message). I have wiped and used the stock SlimBean and it is working fine, the issue only comes up once I advanced restore the backup ROMs data.
I have reflashed the Slim boot.img, and got another copy of the SlimBean ROM just in case but that has not helped.
Everything else works fine just this one issue.
I know I am not using the latest CWM, could this be the problem?
Any help would be greatly appreciated.
Related
I was on MIUI for a while and it was working perfectly. but thought I'd try MikG (Sense 2.0 and GB 2.3.3) to see what Sense 2.0 was like. I've since flashed back to MIUI, using a nandroid backup as a restoration point. After I boot up my phone, I'm fine, I restore with Titanium Backup (mostly new apps and Accounts, etc) and my phone works fine on the first boot. However, if I reboot my phone, no matter what, I get a bootloop and have to nandroid all over again. Using Tiamat kernel v4.0.0 and MIUI v1.4.29. Any way to fix this?
Extra info: Didn't have bootloops on original MIUI or MikG.
it sounds like you need to do a fresh install or something (maybe a newer release?)...why don't you try wiping cache and dalvik and just reflash the rom without having to wipe everything...if not then i would recommend a clean install
When you restored your apps, ect, did you restore system settings? That'll send you into bootloop for sure.
I am currently using CM9 on my GNex because it has a built-in Profiles management application in Settings.
Is this feature exclusive to CM? Do other ROMs have this feature? I have tried various market apps to replicate this functionality, but none of them seem to work the way the CM9 one does.
I thought I had seen someone using AOKP and it had this in his Settings, but when I tried to Flash that ROM, I got a ton of errors on reboot and didn't find Profiles in the Settings section either.
Also, as I am relatively new to Android (this is my first Android device), should I do a complete wipe data before installing a totally different ROM to avoid process errors? I am using Clockwork Mod recovery to flash ROMs and just performing the default "wipe Dalvik cache" before installing a new ROM. So far, the only ROM I am able to install/update is CM9. AOKP and Codename Android just gave me a ton of process errors after booting and were just unusable. As such, i am currently stuck using CM9, but have really bad wifi performance with it.
TIA!
bryanus said:
Also, as I am relatively new to Android (this is my first Android device), should I do a complete wipe data before installing a totally different ROM to avoid process errors? I am using Clockwork Mod recovery to flash ROMs and just performing the default "wipe Dalvik cache" before installing a new ROM. So far, the only ROM I am able to install/update is CM9. AOKP and Codename Android just gave me a ton of process errors after booting and were just unusable. As such, i am currently stuck using CM9, but have really bad wifi performance with it.
TIA!
Click to expand...
Click to collapse
Yes. Yes Yes Yes Yes. ALWAYS do a full data wipe when moving from one ROM to another ROM. You can sometimes get away with not wiping if you are simply upgrading to a newer version of the same ROM, but anytime that you run into issues after installing a new ROM please do make sure that you wiped data before posting/complaining about issues.
Thank you for your clarification. The next time I try a completely different ROM I will do a full data wipe. I assume flashing new Nightlies of the ROM I am already running doesn't require a full data wipe?
But can you or anyone else tell me if AOKP or any other ROMs have the "Profiles" feature in Settings, like CM9 does? Or is this exclusive to the CM9 ROM?
Thanks again.
bryanus said:
Thank you for your clarification. The next time I try a completely different ROM I will do a full data wipe. I assume flashing new Nightlies of the ROM I am already running doesn't require a full data wipe?
But can you or anyone else tell me if AOKP or any other ROMs have the "Profiles" feature in Settings, like CM9 does? Or is this exclusive to the CM9 ROM?
Thanks again.
Click to expand...
Click to collapse
I haven't seen it anywhere else, though AOKP does offer a Quiet Hours option.
THANK YOU!
Using your suggestion to do a wipe data when flashing a rom, I downloaded the latest CM9 nightly, and just installed it wiping both the data and cache.
After my initial setup and installing the speedtest app, my ping is back to normal at ~25ms and 15mb down and 2 up!
Do you always (or recommend) wipe the data even if you are just updating the current ROM?
Hopefully one of my other apps wasn't the cause of this issue, but I'll soon find out once I have re-installed everything.
Thanks again.
bryanus said:
Using your suggestion to do a wipe data when flashing a rom, I downloaded the latest CM9 nightly, and just installed it wiping both the data and cache.
After my initial setup and installing the speedtest app, my ping is back to normal at ~25ms and 15mb down and 2 up!
Do you always (or recommend) wipe the data even if you are just updating the current ROM?
Hopefully one of my other apps wasn't the cause of this issue, but I'll soon find out once I have re-installed everything.
Thanks again.
Click to expand...
Click to collapse
The ROM developer will usually state in the changelog / release notes if a wipe is required/recommended for an upgrade. Rule of thumb though:
1) Updating ROM to newer version, same Android release (ex: 4.0.3 -> 4.0.3) ==> No wipe
2) Updating ROM to newer version, different Android release (ex: 4.0.3 -> 4.0.4) ==> WIPE
3) Changing from one ROM to another ROM (CM9 -> AOKP) ==> WIPE
Interesting. After reinstalling my apps one by one, I've been running speedtest and found that Airsync/Doubletwist is the cause of my slowness. Uninstalling and rebooting fixes the speed/ping issue right away. Glad I bought this app. Not.
Been a bit confused on this. When I initially got this phone i317 (rogers), I rooted no problem, got TWRP running no problem and first thing did a nandroid. Flashed the older stable version of paranoid android 2.54 (i believe) which is based on 4.1.2. No issue what so ever.
As well before i go on, I've been rooting phones a while. Never bricked anything and definitely know the concept of the search button.
After running PA for a day or so and not seeing too many people having issues flashing roms on this phone i flashed another ROM (unfortunately I cant remember which one, but it was one of the popular ones on xda) TWRP had no issues flashing.
When the rom booted and android itself loaded i then had three FC errors and android rebooted. Ok thought it was a bit odd. Said screw it and recovered a backup. However any backup i flashed the error continued. Tried flashing the original PA rom again, the issue continued. Eventually had to reflash in odin the original rooted stock rom.
As you have read this issue has been resolved. My question is what happened? Is this a common problem with this device? Is it perhaps an issue going between 4.1.2 and 4.1.1? Is this just an issue with the devices internal memory? I have yet to read anyone having similar issues, however am not on xda as much as i used to be.
I am really just making sure that i am not missing something obvious or if this was simply an isolated issue before i sample some other ROMS floating around this site.
Any input is appreciated.
Sent from my SGH-I317 using Tapatalk
Did you happen to wipe data before you flashed the new Rom? I have never experienced any force closes while flashing roms.
This is what I usually do when going in between roms.
1. Wipe data/cache twice
2. Flash rom
3. Usually start to hate the Rom after the first minute.
4. GO into recovery
5. Wipe data twice
6. Restore from CWM recovery.
7. Fix permissions (just in case there was a mixup (usually helps resolve force closes)
Hope this helps. If you do happen to wipe data then I am as lost as you are . Maybe try fixing permissions? I am fairly new to android but I have been picking up modding it pretty quick.
______________________________________
Phones: iPhone 4 - > iPhone 5 - > Note 2 (Always on AT&T)
ROM: International N7105XXDMA6 by miscom
LINK: http://forum.xda-developers.com/showthread.php?t=2016575
Kernal: Perseus alpha32.1
A lot of bloatware removed.
Screen on time after normal charge: 7-8 hours always.
I don't think this is a process thing.
I always full wipe before a new rom, clear dalvic and such. This was something different.
Have been stuck in many a bootloop, but never one that caused rebooting when a recovery is flashed or a different rom for that matter.
Sent from my SGH-I317 using Tapatalk 2
Some ROMs require a factory reset wipe on top of the cache and dalvik wipe. I've used PA, and when I did the standard cache and dalvik wipe to PA from JellyBeer, I had repeated FCs, which namely was System UI. Even a nandroid restore after a cache and dalvik wipe had no effect. I was still getting the same FCs. I ended up using all four wipes with TWRP and a clean flash of JellyBeer, then a nandroid restore, to get rid of the FCs. Of course, several of my settings got wiped, including DPIs. Some ROMs just don't play well with other ROMs without a factory reset after the cache and dalvik wipe, which gets rid of your settings for a clean flash.
The other possibility is you're going between 4.1 and 4.2 ROMs. 4.2 ROMs create a new directory that puts all your files into due to multi-user login capabilities. Switching to a 4.1 ROM would certainly cause confusion within the phone without transfer the files back outside of the new directory.
Thank you. That was exactly what I needed to know. Was a scary issue the day after I purchased this phone outright lol. Not an issue I've experienced before with any other device.
Cheers.
Sent from my GT-N7105 using Tapatalk 2
Hi Guys,
I have a Rooted Galaxy Nexus. From Last Month, I am facing a strange problem. I had two custom roms stored in my machine
1. JB Sourcery 5.2
2. Xylon Maguro 2.7.7
I downloaded JBSourcery Encore, and tried to install it through Recovery. I have TWRP.
The TWRP program said that Installation of the ROM with Gapps package was successful. But when I Rebooted my phone, It got Stuck on the JBSourcery Logo while booting.
Then I switched back to JBSourcery5.2. It got installed perfectly.
After Some time , I installed XYLON rom with the same procedure. It also installed correctly, But when again I tried to install JBSourcery 5.2,
I faced the same problem I faced with JBSourcery Encore.
So, I switched back to XYLON 2.7.X.
Last week I copied PA3.99 custom rom with Android4.3. I installed it yesterday with new gapps package and it got installed correctly. I didnt like that rom interface so, I decided to go back to Xlon as it was the only working rom left in my phone. But when I tried to Load XYLON rom this time, then I went into BootLoop with XYLON Logo on the screen.
In Short, whenever I install a new rom on my phone, and if I switch back to my prevoius rom, then my previously working rom goes into bootloop. (Please note that I wipe cache/dalvik cache every time I install a new rom.)
Can Someone please help me to solve this issue???????
Please......
pkalekar said:
Hi Guys,
I have a Rooted Galaxy Nexus. From Last Month, I am facing a strange problem. I had two custom roms stored in my machine
1. JB Sourcery 5.2
2. Xylon Maguro 2.7.7
I downloaded JBSourcery Encore, and tried to install it through Recovery. I have TWRP.
The TWRP program said that Installation of the ROM with Gapps package was successful. But when I Rebooted my phone, It got Stuck on the JBSourcery Logo while booting.
Then I switched back to JBSourcery5.2. It got installed perfectly.
After Some time , I installed XYLON rom with the same procedure. It also installed correctly, But when again I tried to install JBSourcery 5.2,
I faced the same problem I faced with JBSourcery Encore.
So, I switched back to XYLON 2.7.X.
Last week I copied PA3.99 custom rom with Android4.3. I installed it yesterday with new gapps package and it got installed correctly. I didnt like that rom interface so, I decided to go back to Xlon as it was the only working rom left in my phone. But when I tried to Load XYLON rom this time, then I went into BootLoop with XYLON Logo on the screen.
In Short, whenever I install a new rom on my phone, and if I switch back to my prevoius rom, then my previously working rom goes into bootloop. (Please note that I wipe cache/dalvik cache every time I install a new rom.)
Can Someone please help me to solve this issue???????
Please......
Click to expand...
Click to collapse
You noted in your post that you only wipe cache and davlik. When you install a rom your supposed to do a full system wipe. And for sh!ts and giggles, try using cwm instead of twrp to install your roms. I hear mixed things about twrp.
Sent from my Galaxy Nexus using xda app-developers app
mkuehl06 said:
You noted in your post that you only wipe cache and davlik. When you install a rom your supposed to do a full system wipe. And for sh!ts and giggles, try using cwm instead of twrp to install your roms. I hear mixed things about twrp.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
But if I perform System wipe, then all the data such as images, contacts, downloaded aplications will be wiped from my phone... right?
And if I take a backup of that data on PC, and then after installing a new rom, if I paste it back in the phone, will it work??
pkalekar said:
But if I perform System wipe, then all the data such as images, contacts, downloaded aplications will be wiped from my phone... right?
And if I take a backup of that data on PC, and then after installing a new rom, if I paste it back in the phone, will it work??
Click to expand...
Click to collapse
Yes you will loose all your user data when you do a full system wipe. ive never copied and pasted data from my phone to my pc and then back tbh, i just let it all sync with my google account. the applications will restore when you sync your google account to your phone after the wipe since you have to have a google account to use play store. if they are external applications (ones you downloaded the apks for and installed them manually) you will have to reinstall those, as playstore will not recognize them. just about every custom rom op gives you instructions on how to install the roms, and im pretty sure they all say you must wipe all data before installing. failure to do a system wipe, will cause boot loops.
You can use "titanium backup" Ort "helium" to save your apps and Data.
Images and music normaly won't be deleted. But you should make a Backup anyways.
Gesendet von meinem Galaxy Nexus mit Tapatalk 4
so i have an s3 i747M currently was sitting on slimrom build 7, but i felt as if i had battery issues so went to explore different roms, after finding a couple(i.e. stable slim rom build 9, cyanide alpha lolipop build, cyanogenmod alpha, resurrection rom, candykat rom) i went back to restore the initial system, but when i did CWM recovery would finish maybe half of the restore and then boot up the backup... usually after the restore you would have to boot manually, i've tried other functions like wiping user data, but would still boot on it's own before finishing wipes... anyone know how to fix this?
Have you tried re-installing CWM? Were you trying to restore a KK ROM over an L ROM? I had trouble restoring a KK backup on a Nexus 4 that had been running a custom L ROM.