Related
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.
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Eric_Eric_Eric said:
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Click to expand...
Click to collapse
There may have been a corruption in your data backup. Just delete that backup and make a new one.
Nope, I tried all three of my backups and had the same problem with all three. Plus, I can't simply make a new backup. I tried restoring to the backup and lost my stuff because it didn't finish restoring my data.
I'm having some issues with cwm too. Sometimes when I'm trying toi recover, it says "md5 mismatch", maybe its a linked problem?
Sent from my GT-S5830 using XDA
rommanager
Install rommanager.apk premium and, to me is to solve the problem
So, I think I figured it out. Apparently, I only get this error when my backup contains more than a certain number of apps (or possibly the /data is over a certain size). Granted, I do have over 350 apps, but why is CWM Recovery messing up while trying to restore a big backup? It really should not affect it, but it seems to. So, I will be backing up with Titanium for my apps, and making nandroid backups only when I have under about 350 apps installed. If anybody else has any insight, please share it with me. Thanks.
The Answer (I am pretty sure...)
Okay, I think I finally figured it out. The reason it was not restoring properly was because I had about 350 user apps installed. My guess is that, while restoring, the recovery (CWM recovery in my case) puts the /data onto the RAM, and the RAM is not large enough to hold that much at once. I deleted a lot of apps, backed up in CWM recovery, and restored back to the backup, and everything worked flawlessly. I am surprised that no one has ever had this problem. So, in the future, I am making Titanium backups of all my apps, batch uninstalling a bunch of them from within Titanium (so that I have under 300 at the most), and then making a backup. Then, I can flash a new ROM, recover, or whatever and finally use Titanium to put all my apps and data back. I just thought I would post this in case anyone else ever finds this problem. It was really frustrating for me, but the insufficient RAM theory seems to explain it. Post your thoughts on the matter.
Eric_Eric_Eric said:
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Click to expand...
Click to collapse
its better to use titanium backup application for you.user friendly and worthy..
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.
Hi all,
Yesterday I was flashing a theme for the Vemon ROM on the M8. I ended up deciding I didn't like it, so I tried to go back and flash a backup I had made. However, once I flashed the backup, the device wouldn't boot up past the HTC One white screen (it will go past the HTC logo by itself, but then the One appears on the screen and stops there). I have no idea why, as I have made backups before and have had no issues. On the default backup name, it does say KOH Release keys. I don't know if that means anything. I was able to get to recovery and flash the base Venom ROM, but I'd like to know why my backups are not playing nice.
Any and all help regarding this would be appreciated.
Did you try wiping everything before restoring your backup?
Sent from my HTC6525LVW using Tapatalk
I had the same, exact issue. Absolutely no reason why it shouldn't have worked. I made sure the Nandroid copied the necessary partitions/directories and also performed a full wipe before restoring the backup. Same issue. I was on TWRP and I'm pretty sure there is some issue with TWRP.
I haven't attempted to make a backup or restore a Nandroid since, so I don't know whether its still an issue.
ChuckFinley1992 said:
Hi all,
Yesterday I was flashing a theme for the Vemon ROM on the M8. I ended up deciding I didn't like it, so I tried to go back and flash a backup I had made. However, once I flashed the backup, the device wouldn't boot up past the HTC One white screen (it will go past the HTC logo by itself, but then the One appears on the screen and stops there). I have no idea why, as I have made backups before and have had no issues. On the default backup name, it does say KOH Release keys. I don't know if that means anything. I was able to get to recovery and flash the base Venom ROM, but I'd like to know why my backups are not playing nice.
Any and all help regarding this would be appreciated.
Click to expand...
Click to collapse
I tried wiping everything yes. I did a factory reset data wipe first, and then tried installing the backup. I don't know why it did not work. I was eventually able to get out of the boot screen with an volume up and power key combination, but it was more frustrating not knowing why this issue was happening. If anyone knows why this is occurring, I would gladly like to know.