Develop Bugs

Q: stuck in cyanogen boot animation - Flashed back to Cm6

So I got Cm7 running using rom manager, used titanium backup to restore apps + system data, then fixed permissions. For the last 10 minutes it's been stuck in the CM7 screen....
What should I do? Can I pull the battery without harm? Does it take that long to boot after fixing permissions?
Edit: pulled the batter and am trying to boot into recovery...going to wipe the dalvik/cache again.
Edit2: same thing for the last 6 minutes....dang. I guess I'll just nandroid in 5 minutes if it doesn't' get out of it.
Edit3: going to nandroid back. I might try it again later flashing from a Zip instead of using rom manager. I probably won't restore system data either next time. If anyone has any suggestions though please post them.
Edit4: not good...phone is bootlooping cyangen screen after nandroid.
Edit5: Cleared factordata, cache, and when I go to clear dalvik I'm getting
e unknown volume for path sd-ext
Any ideas here?
Edit6: I'm reflashing 6.1.2....okay...got through the boot and now I'm setting up the phone.

You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.

housry23 said:
You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.
Click to expand...
Click to collapse
Will do....I know I had been installing apps to the SD card using CM6 and when I first got CM7 up it said my phone memory was low. I thought it would say on the SD card.
I'll probably try tomorrow again if I get the courage and I most definitely will DL Calkun's tools.
Thanks!
I'm going to guess the nandroid didn't work either because of the phone memory low issue?

I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.

teh roxxorz said:
I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.
Click to expand...
Click to collapse
Wiped manually, installed from zip, and didn't restore system data. CM7 has been running for about an hour now.
Thanks everyone!

Glad that you got it working man.

Is ANY system data safe to restore from Titanium?
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!

phsteve said:
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!
Click to expand...
Click to collapse
You should never restore system settings.
For contacts, open accounts and sync, tap your google account, then sync contacts, and that'll be done.
For texts, people highly recommend sms backup or my backup. Then backup apps and data, then restore only apps and data, and you'll be set.

[Q] Boot Loop after restoring

Hello
i have a boot loop after restoring a backup, because after installing 'gapps' to the Cyanogenmod 7, it didn't work anymore
So i went into the Recovery mode to restore the backup.
But after restoring is the splash screen in a booting loop.
What can i do now?
There isn't another backup on my sd card
Is it possible to install another Rom directly from the recovery menu?

hydrano said:
Hello
i have a boot loop after restoring a backup, because after installing 'gapps' to the Cyanogenmod 7, it didn't work anymore
So i went into the Recovery mode to restore the backup.
But after restoring is the splash screen in a booting loop.
What can i do now?
There isn't another backup on my sd card
Is it possible to install another Rom directly from the recovery menu?
Click to expand...
Click to collapse
I had problems with bootloops after restoring nandroid backup - I restored all but part of it in advanced and it worked...
Check out this thread to see if it helps - http://forum.xda-developers.com/showthread.php?t=985452

brandall said:
I had problems with bootloops after restoring nandroid backup - I restored all but part of it in advanced and it worked...
Check out this thread to see if it helps - http://forum.xda-developers.com/showthread.php?t=985452
Click to expand...
Click to collapse
brandall, thankyou, I was in a nandroid-restore-boot-loop and your tip about not restoreing 'boot' saved me too (messinga around with my brothers Desire and I don't want him kicking my ass becaused of needing an unwanted full wipe)
but it's strange that an nandroid of a fully working installation fails when restored :S (had the same HBOOT when backup and restore, and the restore was made 15 minutes after creation :S )

Go into recovery, wipe everything and restore backup.
Swyped from Oxygen with Transparent XDA App

MatDrOiD said:
Go into recovery, wipe everything and restore backup.
Swyped from Oxygen with Transparent XDA App
Click to expand...
Click to collapse
Yes we both did that, but somehow the backup went broken.
I tried wipeing EVERYTHING and restore backup maybe 5 times, but boot loop every time.
So the solution was to wipe and do an advanced restore were you restored ext, system, data and cache.
But NOT restore Boot!

MrPontus said:
Yes we both did that, but somehow the backup went broken.
I tried wipeing EVERYTHING and restore backup maybe 5 times, but boot loop every time.
So the solution was to wipe and do an advanced restore were you restored ext, system, data and cache.
But NOT restore Boot!
Click to expand...
Click to collapse
Just happened to me, not restoring boot finally got me out of the bootloop, thank god. Thanks for that tip

[Q] Regarding backups and restores. Please help!

Hello XDA, I am in need of great assistance regarding backups and restores, I am somewhat new and not very experienced with this. I'll keep this short.
Here is what I would like to do:
I have a Galaxy Nexus from the Play store and running 4.2.1 from a stock google image I flashed, I have it set up the way I want to with all my apps, etc. Turns out I don't like the performance from this version on my phone as it feels slugish so I want to either try a 4.2.1 ROM or go back to 4.1.2 but I don't want to set up everything again, both having to download the apps and setting them up the way I have them right now, same with my phone settings (brightness, keyboard settings, etc).
Can I do that and if so how? I have a pro version of Titanium Backup but having my backup restored on another rom breaks it and puts me in a boot loop upon reboot. I also tried making a nandroid backup but upon restoring it brought everything back, including the old ROM! Upon some reading I found out about the advance restore and to just restore data but that puts me back in the same boot loop on the new ROM.
Ultimately what I want to do is restore my phone and app settings in a simple way, I don't care about to manually downloading the apps but I do want to restore their settings and phone's settings in an easy way so I can safely try out new ROMs without having to set up every configuration again.
Please help me I've struggled with this for a while and it always keeps me from trying roms.

dont restore system apps/settings, that can cause you to get bootloops... you can try this if you want
- Backup your current setup either with TWRP or CWM (I prefer TWRP)
- Do a full wipe (cache/dalvik cache, system and factory reset)
- Flash the new ROM, gapps and your preferred kernel
- Restore ONLY data from the backup your made
- Reboot and enjoy

k786 said:
dont restore system apps/settings, that can cause you to get bootloops... you can try this if you want
- Backup your current setup either with TWRP or CWM (I prefer TWRP)
- Do a full wipe (cache/dalvik cache, system and factory reset)
- Flash the new ROM, gapps and your preferred kernel
- Restore ONLY data from the backup your made
- Reboot and enjoy
Click to expand...
Click to collapse
I think that's exactly what I did the last time, I created a backup in CWM, performed a full wipe, flashed the ROM, etc, booted up the phone, then went back into recovery and restored the data only from the advanced restore in CWM and that caused me to be stuck in a boot loop when I rebooted.
Could really use some help hopefully someone else can respond.

Zevh said:
I think that's exactly what I did the last time, I created a backup in CWM, performed a full wipe, flashed the ROM, etc, booted up the phone, then went back into recovery and restored the data only from the advanced restore in CWM and that caused me to be stuck in a boot loop when I rebooted.
Click to expand...
Click to collapse
Restoring the /data partition is the problem, it contains the settings for both system and user apps. Probably some system settings are the issue.
Just use TB to restore user apps and their data and then selectively restore system data (NOT the system apps.) I usually restore only SMS/MMS, call logs, and WiFi access points.
Restore system data one or two apps at a time, rebooting after each restore. If bootloop or FC's occur then you know what not to restore next time. Just clear data for the effected app and continue.
Also, in TB the xml restore is usually a safer bet where it's available.

cschmitt said:
Restoring the /data partition is the problem, it contains the settings for both system and user apps. Probably some system settings are the issue.
Just use TB to restore user apps and their data and then selectively restore system data (NOT the system apps.) I usually restore only SMS/MMS, call logs, and WiFi access points.
Restore system data one or two apps at a time, rebooting after each restore. If bootloop or FC's occur then you know what not to restore next time. Just clear data for the effected app and continue.
Also, in TB the xml restore is usually a safer bet where it's available.
Click to expand...
Click to collapse
This did it! Tried it yesterday and it worked, I got almost everything back, thanks!

[Q] stuck in Venom Viper One boot after installing RootCloak

Hello!
I have installed RootCloak and after the needed reboot of the phone, it is always stuck in Viper One logo boot screen.
When I wipe Dalvik, I get the actualization screen from Android and after checking the apps nothing else happens. Just "apps are getting started" and the spinning circle....
Any ideas how to recover my phone?
I can't perform a backup because CWM says it cannot mount the sd-card and there is not enough space on internal memory.....

Can you reflash the rom?
And why are you wanting to do a backup of a corrupt system?

KJ said:
Can you reflash the rom?
And why are you wanting to do a backup of a corrupt system?
Click to expand...
Click to collapse
I have already reflashed the ROM, but no effort.
All I want to save are SMS and photos. Can I secure them on any way?

Do you have a nandroid backup from your recovery that you can restore? And if not... Why? ? Everyone should do a backup before flashing anything.... Then you always can restore to your previous state.
That will not wipe your pics. But sms yes. Just about anything you do will wipe your sms's .
There may be a way to adb pull your texts and even pics... If you can get into adb mode in your recovery. But you'd have search on that, I've never done it.
Anyway, Another option is from recovery, wiping system, data, cache and dalvik and clean installing your rom. Whatever that app did will be wiped. Pics will be fine. But again, sms gone.
That's all the ideas I have. Aside from returning to stock.

KJ said:
Do you have a nandroid backup from your recovery that you can restore? And if not... Why? ? Everyone should do a backup before flashing anything.... Then you always can restore to your previous state.
That will not wipe your pics. But sms yes. Just about anything you do will wipe your sms's .
There may be a way to adb pull your texts and even pics... If you can get into adb mode in your recovery. But you'd have search on that, I've never done it.
Anyway, Another option is from recovery, wiping system, data, cache and dalvik and clean installing your rom. Whatever that app did will be wiped. Pics will be fine. But again, sms gone.
That's all the ideas I have. Aside from returning to stock.
Click to expand...
Click to collapse
I have a nandroid backup when I installed the ROM, sure...
But I did not make a new one while installing RootCloaker, because it is "just an app". so the backup is too old any many SMS will be gone.
Can I access the device via ADB when it is in recovery?

Schlicki said:
I have a nandroid backup when I installed the ROM, sure...
But I did not make a new one while installing RootCloaker, because it is "just an app". so the backup is too old any many SMS will be gone.
Can I access the device via ADB when it is in recovery?
Click to expand...
Click to collapse
If it has the option. In twrp it's in advanced menu I believe. Not sure about others.
Restoring your nandroid will likely get you running. In the future, backup texts with sms backup and restore or a similar app. Then you'll be good.
Or let go of the past like I do.... I start fresh with texts after every flash. But that's me. To each their own. ?
But at this point, you're missing out on your phones functionality over them. And whether you can pull the with adb , I'm not even sure.
Good luck though!

Reboot after booting to recovery

I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".

OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again.
Click to expand...
Click to collapse
I don't think the recovery was "restored" / flashed to the boot partition but maybe try just in case. Flash the boot.img for Viper ROM and see if it stops the bootloop. After that you can make a clean wipe and install the ROM again, not restore but INSTALL. You surely have the ROM's .zip still?
Reason I suggested boot.img: i cannot get anything to restore with the h3g__001 backups keep getting recovery.emmc.win' is larger than target device '/dev/block/mmcblk0p42 error
mmcblk0p42 is the boot partition, so I don't know why TWRP tried to restore/flash a recovery to boot partition. He solved it by manually flashing boot.img after renaming.
if anyone gets this error heres how i solved it.change the boot.emmc.win to boot.img and it let me restore
Just a suggestion...

So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it

OMGMatrix said:
So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it
Click to expand...
Click to collapse
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Not sure if you have to actively choose whether to flash over data or not, I'm not that big into custom ROMs, only tried Viper ROM and even then I kept my original data.

OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".
Click to expand...
Click to collapse
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
I ended up just running an RUU and starting over. I was able to adb pull all my files from internal sd card before i ran it.

mattprice86 said:
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
Click to expand...
Click to collapse
I was using a version of TWRP that had been bundled with a previous version of Viper that was supposed to have been newer, but was actually 2.7.0.1. I updated to the newest (2.8.0.3) from the TWRP site through fastboot, but that didn't change anything. I had somewhat recently updated to the 3.xxx.xxx.7 firmware, but had flashed other roms since that without issue.
BerndM14 said:
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Click to expand...
Click to collapse
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.

OMGMatrix said:
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.
Click to expand...
Click to collapse
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.

BerndM14 said:
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.
Click to expand...
Click to collapse
I don't think you understand.
The restore never happened. It rebooted before anything happened when I told it to restore. Nothing got restored.