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.
Related
I know there are a lot of questions about this on XDA, but no one seems to give a straight answer on how to fix this or even prevent it.
I flashed kh2 deodexed today via CWM, everything went fine.. I installed titanium backup to restore my apps, which I did, they worked fine until I rebooted the phone. Then the apps dissapeared, and the home screen shortcuts display the SD card icon and they won't open "Application is not installed on your phone".
Then, I did a wipe to data and cache partitions, but this time I restored apps only (without data) one by one, as I needed. Not as a batch, as I did last time, and was working ok. Though, I thought I'd try the ICBINB kh2 ROM, so I flashed it fine. Restored apps through titanium backup, this time one by one, mostly apps only (some of them w/ data) and was working fine, but suddenly the apps dissapeared again.
I'm about to wipe the phone to fix this... but, is there a way to prevent this from happening again?
Is restoring data from titanium causing this?
Well there has been many direct answers on this topic. Factory reset. restore from cwm, not TB.
Sent from my SGH-T959V using xda premium
hey, didn't know that. **presses thanks button**
I just restored apps via cwm, fixed permissions and it's working. It even got my settings back.. wtf. I was living under a rock all this time.
But is it completely safe? I guess that for GB builds, doing backups and restoring this way may be harmless, but probably not the same story if coming from a froyo rom.
Anyway, thanks a lot.
yea, what i did was flash both 2.2.1 and 2.3+ fresh. then backup each and whatever rom you go to, flash the corresponding backup.
Hey guys,
I recently bought an HTC One S. I came from an HTC Amaze 4G, and thus I backed up everything in Titanium Backup *AND* SMS Backup and Restore.
Thank goodness I backed up my texts in SMS B&R.
When I unlocked the bootloader and rooted the device, I went to install TB and restore missing apps and all system data.
I have never had this happen before, but when I rebooted the phone afterwards it said "Loading" on the HTC Sense screen and stayed there forever. It asked a few questions like Facebook login, etc. but still remained stuck on "Loading."
I eventually gave up and decided to take matters in my own hands. I figured that it's likely HTC Sense 3.6 data files were not compatible with 4.0 to a degree to cause issues, so I went into settings and cleared out the data for HTC Sense, and rebooted the phone.
When I rebooted the phone I was finally able to go into the messages app. Turns out I had a new text. NONE of my text message threads were there!!!
I am restoring them right now with SMS B&R.
I don't think this can be an ICS thing because on the Amaze I restored a TB backup the same exact way to a new ICS ROM and everything was fine. Has to be HTC Sense.
Anyhow, I just wanted to warn you guys. Don't trust a TB backup by itself from another device to the HTC One S. It may not work.
I see no reason to believe it won't work if coming from another phone with Sense 4.0, however I would be cautious and AT LEAST backup your text messages with SMS Backup and Restore.
It's still in the process of restoring. I am thinking that should surely work, but until it's done we won't know for certain. Will be certain to update this thread.
PS: I know some of you believe that you should never restore system data when going to a new device/rom (even though this is my 2nd post I've been lurking for quite a while :-D (as a guest)). I prefer to have all my stuff restored. If it causes a problem I am willing to go back and re-flash the rom
--
AR @}-,-`--
you cant restore system data from one phone to another, Thats a recipe for disaster. Even restoring from one ROM to another is risky...
Only ever restore apps and app data, Not anything else.. Ive been using TB for about 2 years now.. Never had a single issue with it
alexanderose said:
PS: I know some of you believe that you should never restore system data when going to a new device/rom (even though this is my 2nd post I've been lurking for quite a while :-D (as a guest)). I prefer to have all my stuff restored. If it causes a problem I am willing to go back and re-flash the rom
Click to expand...
Click to collapse
@ azzledazzle, did u see this? )
yes i saw it, but i dont get why you like to restore system data...
there is nothing of use in it if you are restoring using the same ROM, the data will be in that ROM anyway.
If you are restoring on a new ROM, you cant restore the old data lol
you like to restore system data, yet if you have troubles you wipe and skip restoring data..
Why not just skip system data altogether ?
You sound like you have OCD or something
azzledazzle said:
yes i saw it, but i dont get why you like to restore system data...
there is nothing of use in it if you are restoring using the same ROM, the data will be in that ROM anyway.
If you are restoring on a new ROM, you cant restore the old data lol
you like to restore system data, yet if you have troubles you wipe and skip restoring data..
Why not just skip system data altogether ?
You sound like you have OCD or something
Click to expand...
Click to collapse
System data saves the wallpaper, all icons, folders, etc. in the native launcher, alarms, etc. etc. which is not restored with apps. System data also saves the text messages, and restores them WAY faster than SMS Backup & Restore.
I've never had a problem restoring them until now. I tried one time not restoring system data, following the advice of someone on here who said it was pointless, and ended up losing system stuff. After that, never again do I restore without restoring system data.
I followed the instructions exactly on this page: http://forum.xda-developers.com/showthread.php?t=1663169
CM9 seemed to work fine for a while. I installed Titanium Backup and brought back my apps and just a bit of system data (contacts, voicemail, texts, etc). After I had restored those things, it said it suggested a reboot. I did that, but now it just reboots over and over. I can't get in to the OS for more than a few seconds before it reboots again. Help please!
As that thread specifies, I have a MX2 from CSpire. For now I don't care so much about getting CM9 working as just getting my phone back to a working state. I have both a nandroid and titanium backup on the sd card. I just need very specific instructions on how to get back to the way it was (2.3.6) given that I can't get in to the OS.
Edit: Pulling the battery doesn't resolve anything
Does it let you stay in long enough to remove the app/settings you restored? Are you able to get into recovery mode at all?
If you can get into recovery you might first want to try Fix Permissions and see how that works. If this does not solve it then consider doing a factory wipe and start restoring your apps/settings again one by one and rebooting in between until you get to the particular one that started your reboot problem.
What ROM were you on prior to CM9? Although they should be largely universal sometimes there are some slight changes in custom ROMs that might work well in many other ROMs but not in a select few. Other times it is an app that is not compatible.
The post below might be of some help since your phone seems to have a different method of getting into recovery than what I have dealt with so far.
http://forum.xda-developers.com/member.php?u=4395758
Factory Restore DX2
This might help. It's a factory restore, like you just bought it. http://forum.xda-developers.com/showthread.php?t=1317707
After much sweat, tears, and button pressing, I have gotten it back to stock CM9 and it seems to be behaving as expected. I am going to install apps one by one and reboot between every install. Hopefully I'll find the culprit soon enough.
I've had AOKP (can't remember which version..) installed for a while now and it's been acting funny, boot looping from time to time, but a simple battery pull fixed it each time.
Today I was turning off the phone to switch out the battery, and pulled out the battery before it had finished shutting down the "proper" way. Now when I turn it on, it gets stuck at "Initiating Swagger" with the pink unicorn. I've tried wiping the dalvik cache and formatting /cache.
I'd like to preserve some of the photos and texts, as well as all my apps which I, completely stupidly, didn't back up with Titanium Backup even though I've been meaning to for a little while now. I'm ready to reset and install a new rom if I have to, but I was wondering if there was a simple fix I'm overlooking since all I did was pull the battery out too early, rather than having done anything substantial like installing a new rom. Really appreciate any help, I've been phoneless all day and would love to not go through the motions of a whole new rom.
I JUST DON'T UNDERSTAND
Amb1valence said:
I've had AOKP (can't remember which version..) installed for a while now and it's been acting funny, boot looping from time to time, but a simple battery pull fixed it each time.
Today I was turning off the phone to switch out the battery, and pulled out the battery before it had finished shutting down the "proper" way. Now when I turn it on, it gets stuck at "Initiating Swagger" with the pink unicorn. I've tried wiping the dalvik cache and formatting /cache.
I'd like to preserve some of the photos and texts, as well as all my apps which I, completely stupidly, didn't back up with Titanium Backup even though I've been meaning to for a little while now. I'm ready to reset and install a new rom if I have to, but I was wondering if there was a simple fix I'm overlooking since all I did was pull the battery out too early, rather than having done anything substantial like installing a new rom. Really appreciate any help, I've been phoneless all day and would love to not go through the motions of a whole new rom.
I JUST DON'T UNDERSTAND
Click to expand...
Click to collapse
Looks like pulling the battery while it was shutting down corrupted some essential scripts on your device. So you have to flash a Rom to fix this. Dont worry coz there is something i do which can help you if you want to keep your apps n all. What you have to do is take a clockwork mod recovery backup right now. Then wipe everything including data,cache and dalvik cache. Now flash your Rom. If you want your apps n all then flash the same Rom you had. Now after it is flashed and working, boot to cwm recovery. select backup and restore then go for advanced restore. Select the backup you took. And restore data alone. This should make your phone look like it had never been flashed again with the Rom. Just like you had it before. And if even now the bootloop continues, do the same but first flash the kernel then Rom then do what i asked you to do. Hopes this helps...
Thanks man, that's a great idea, I didn't even think of that. Unfortunately I tried it, without and then with the kernel and it still didn't work.
What I ended up doing (for any of our posterior who happen upon this post) is installed the newest version of AOKP (which I actually didn't have previously), and downloaded an app called nandroid manager, which pulls apps/data, SMS messages, call logs, everything from any nandroid backup. I'm restoring all my stuff right now. Thank god.
Interestingly enough, even after I wiped everything multiple times, when I connected my phone to the computer it had all my photos & other data still on the internal storage. Weird as hell. But whatever.
Amb1valence said:
Thanks man, that's a great idea, I didn't even think of that. Unfortunately I tried it, without and then with the kernel and it still didn't work.
What I ended up doing (for any of our posterior who happen upon this post) is installed the newest version of AOKP (which I actually didn't have previously), and downloaded an app called nandroid manager, which pulls apps/data, SMS messages, call logs, everything from any nandroid backup. I'm restoring all my stuff right now. Thank god.
Interestingly enough, even after I wiped everything multiple times, when I connected my phone to the computer it had all my photos & other data still on the internal storage. Weird as hell. But whatever.
Click to expand...
Click to collapse
Thats pretty interesting.. I never tried AOKP so dunno much bout the way it works. Anyway happy for you man..
Amb1valence said:
Thanks man, that's a great idea, I didn't even think of that. Unfortunately I tried it, without and then with the kernel and it still didn't work.
What I ended up doing (for any of our posterior who happen upon this post) is installed the newest version of AOKP (which I actually didn't have previously), and downloaded an app called nandroid manager, which pulls apps/data, SMS messages, call logs, everything from any nandroid backup. I'm restoring all my stuff right now. Thank god.
Interestingly enough, even after I wiped everything multiple times, when I connected my phone to the computer it had all my photos & other data still on the internal storage. Weird as hell. But whatever.
Click to expand...
Click to collapse
That's because a wipe does not affect sd card or internal storage
brandonarev said:
That's because a wipe does not affect sd card or internal storage
Click to expand...
Click to collapse
Well.. It do affect internal memory on low phones. I am not sure bout devices having large internal storage but wiping data usually removes everything on my internal.
From past 15-20 days I'm facing hanging problem. This happens when I switch on the data on or connects to wifi. As soon as I connects to wifi or data mobile starts hanging due to notifications of apps for eg. Whatsapp Gmail. Sometimes Mobile gets hang when you switch in between multiple apps. It doesn't really matter which rom I'm using. I tried 8-9 different roms since last 15-20 days. well let me give you some extra info about my moto G3. My current recovery is TWRP 3.0.2-r1 current rom is ported Stock nougat 7.1.1 by althafvly. Every time I flash new rom I restore backup from titanium backup app which is taken on previous rom. I take batch backup of almost 45-50 apps and restore them. Is this problem due to my backup process? It's been 1.5 years using this device. Flashing custom roms since 1 year. If anyone is facing same issue or you know the reason behind this, let me know in reply. Thanks for reading and sorry for my bad English.
Uh, if you are using TBP to restore stuff across different ROMs, you must have quite a confused build. At the very least, if you must use TBP across builds, restore the apps but NOT the data.
KrisM22 said:
Uh, if you are using TBP to restore stuff across different ROMs, you must have quite a confused build. At the very least, if you must use TBP across builds, restore the apps but NOT the data.
Click to expand...
Click to collapse
Basically restore only apk and not apk+data.
Ok !! I got it. Is there any another way to restore apps + data without using TBP which creates such a confusing build?
scorpionk189 said:
Basically restore only apk and not apk+data.
Ok !! I got it. Is there any another way to restore apps + data without using TBP which creates such a confusing build?
Click to expand...
Click to collapse
There are lots of ways to restore apk+data, but that is the problem - the app data has stuff in it that (now) refers to many different roms. Unfortunately:
a) when you jump ROMs, or
b) when you are having a problem
You need to restore w/o data and restart the apps. You could try going to apps and clicking storage and clearing cache and data for each one, since maybe you have an idea as to a few that might be causing it. Trial and guess...
You could also nandroid what you have and then wipe and flash a new basic rom with no modifications and test there to see if prob goes away. No one that I have heard of is having the problem.
KrisM22 said:
There are lots of ways to restore apk+data, but that is the problem - the app data has stuff in it that (now) refers to many different roms. Unfortunately:
a) when you jump ROMs, or
b) when you are having a problem
You need to restore w/o data and restart the apps. You could try going to apps and clicking storage and clearing cache and data for each one, since maybe you have an idea as to a few that might be causing it. Trial and guess...
You could also nandroid what you have and then wipe and flash a new basic rom with no modifications and test there to see if prob goes away. No one that I have heard of is having the problem.
Click to expand...
Click to collapse
Ok. Thank you very much for answer. Now i got the clear picture of impact of restoring app+data on new rom. I will try few different methods. And will let you know soon.