After a battery empty, I restarted my Defy+. But now it got stuck on "Starting apps." at the end of the boot.
I have to wipe data to make my phone ending the boot.
If I restore data which I previously backup in recovery mode, I'm still stucked with "Starting apps."
How can I debug the settings or data that avoid that? I really want to restore my data.
ronpub said:
After a battery empty, I restarted my Defy+. But now it got stuck on "Starting apps." at the end of the boot.
I have to wipe data to make my phone ending the boot.
If I restore data which I previously backup in recovery mode, I'm still stucked with "Starting apps."
How can I debug the settings or data that avoid that? I really want to restore my data.
Click to expand...
Click to collapse
Are you using the new Teamwin recvoery to flash?
Ive had the same issue ( and many more besides that) for me, to fix the problem i did this:
Go back to recovery (Teamwin) and wipe everything
re-boot, go back to recovery (team win) and flash an older rom with clock work mod recovery, and let it boot.
re- start the phone and then go back to recovery ( clockwork mod) and flash the newer CM10 rom from clcokwork mod (First wipe everything /data/dalvik/cache/factory re-set)
2Pints said:
Are you using the new Teamwin recvoery to flash?
Ive had the same issue ( and many more besides that) for me, to fix the problem i did this:
Go back to recovery (Teamwin) and wipe everything
re-boot, go back to recovery (team win) and flash an older rom with clock work mod recovery, and let it boot.
re- start the phone and then go back to recovery ( clockwork mod) and flash the newer CM10 rom from clcokwork mod (First wipe everything /data/dalvik/cache/factory re-set)
Click to expand...
Click to collapse
Thanx,
Yes Teamwin delivered with cm-10-20130527.
What I done without success:
*Flash older ROM and restore more older data with CWM
*Push with adb unzipped
I should have flashed 10 to 20 times changing some steps each time. Each time I done wipe cache, dalvik and sometimes a data format and a wipe system.
I abandoned the idea to restore my data. Have to reenter all settings manually (find and enter account settings for CSip or some solooong preshared key for Vpncilla and so on).
Then what is positive: I format my data partition to ext4. I learnt a lot from very fragmented information for all those steps. I have a fresh new install.
ronpub said:
Thanx,
Yes Teamwin delivered with cm-10-20130527.
What I done without success:
*Flash older ROM and restore more older data with CWM
*Push with adb unzipped
I should have flashed 10 to 20 times changing some steps each time. Each time I done wipe cache, dalvik and sometimes a data format and a wipe system.
I abandoned the idea to restore my data. Have to reenter all settings manually (find and enter account settings for CSip or some solooong preshared key for Vpncilla and so on).
Then what is positive: I format my data partition to ext4. I learnt a lot from very fragmented information for all those steps. I have a fresh new install.
Click to expand...
Click to collapse
You can use Nandroid Manager to use ur data while the phone is booted, so install it, it will find ur backup, and the u can do a restore of ur apps, with data.
hackergnome said:
You can use Nandroid Manager to use ur data while the phone is booted, so install it, it will find ur backup, and the u can do a restore of ur apps, with data.
Click to expand...
Click to collapse
"Nandroid Manager currently supports nandroid backups created by TWRP and Clockworkmod (v5.xx and v6.xx) based recoveries! ".
Very nice app then. Thank you too late. I immediately install it.
Whole Story:
I'm on a i337m Canadian S4 - Comes with Bootloader unlocked.
Last night I clicked "Format Data" by mistake in the newest TWRP - Lost everything - Could not do anything - flashing Roms did not work, so I downloaded a complete Restore of 4.2.2 from Sammobile and Odin 3.0.7 and was going to flash it back to stock.
About 1/2 way through the flash, something failed regarding a partition - Now my phone will not do anything other than display the below screen. It does not load a recovery, it does not go into download mode. Kies does not detect the phone anymore.
What can I do? Anything?
I'm so depressed over this.
bigystyle84 said:
Whole Story:
I'm on a i337m Canadian S4 - Comes with Bootloader unlocked.
Last night I clicked "Format Data" by mistake in the newest TWRP - Lost everything - Could not do anything - flashing Roms did not work, so I downloaded a complete Restore of 4.2.2 from Sammobile and Odin 3.0.7 and was going to flash it back to stock.
About 1/2 way through the flash, something failed regarding a partition - Now my phone will not do anything other than display the below screen. It does not load a recovery, it does not go into download mode. Kies does not detect the phone anymore.
What can I do? Anything?
I'm so depressed over this.
Click to expand...
Click to collapse
Format data will do nothing other than restore to factory settings, it should boot straight after.
winwiz said:
Format data will do nothing other than restore to factory settings, it should boot straight after.
Click to expand...
Click to collapse
From what I've read, Format Data using the newest version of TWRP deletes everything, causing everything not to work and is some sort of bug.
The ODIN Flash then failed after too.
I have the i337M Canadian version with the S600 Qualcomm
I've flashed via Odin dozens of times before with my previous Note II / S3 - never had one fail.
bigystyle84 said:
From what I've read, Format Data using the newest version of TWRP deletes everything, causing everything not to work and is some sort of bug.
The ODIN Flash then failed after too.
I have the i337M Canadian version with the S600 Qualcomm
I've flashed via Odin dozens of times before with my previous Note II / S3 - never had one fail.
Click to expand...
Click to collapse
Does adb detect the phone?
kingzain900 said:
Does adb detect the phone?
Click to expand...
Click to collapse
I'm not sure - I can see when I get home.
Can a cable cause this? I am not using the Cable that came with the phone - That wasn't included when I bought it. I'm using a Sony Cable from a Xperia T I used to own.
Why did the Odin flash fail to begin with?
Why did Format Data in TWRP cause all this to happen?
bigystyle84 said:
I'm not sure - I can see when I get home.
Can a cable cause this? I am not using the Cable that came with the phone - That wasn't included when I bought it. I'm using a Sony Cable from a Xperia T I used to own.
Why did the Odin flash fail to begin with?
Why did Format Data in TWRP cause all this to happen?
Click to expand...
Click to collapse
You can also ask Does god exist and what is the meaning of life.
Haha. I don't know. Such rethorical questions.
The cable matters because the other cable might not push enough current. Not sure. About the rest I have no idea. TWRP has a bug that's for sure. I don't use it. Check what adb says.
RESOLVED!!!
Tried my Laptop running Windows 7, and switched the cable. Also tried ODIN 1.85 instead of 3.07
Finally! This version of ODIN recongizes my phone.
3rd Attempt at flashing the firmware worked. The first TWO times failed.
Once it flashed, it froze, but factory rest has me back to Stock.
Now - to avoid that format Data button in TWRP, think I'll be giving CWM a try for the first time in years. Need me some Google Edition.
bigystyle84 said:
RESOLVED!!!
Tried my Laptop running Windows 7, and switched the cable. Also tried ODIN 1.85 instead of 3.07
Finally! This version of ODIN recongizes my phone.
3rd Attempt at flashing the firmware worked. The first TWO times failed.
Once it flashed, it froze, but factory rest has me back to Stock.
Now - to avoid that format Data button in TWRP, think I'll be giving CWM a try for the first time in years. Need me some Google Edition.
Click to expand...
Click to collapse
Wiping data, opposed to Formatting data.
TWRP FAQ
What to Wipe in TWRP
If you are switching ROMs (changing from one ROM to a completely different one) then you should perform a factory reset. A factory reset wipes data and cache (which includes dalvik cache). A factory reset will also wipe sd-ext and android_secure if your device has those items. 99% of the time, this is all that you need to wipe and you only need to do it once, not three times as some people would lead you to believe.
If you're installing a nightly update, then oftentimes you don't need to wipe anything at all. However, if you encounter strange behavior, then you may want to consider performing a factory reset. Of course, if the ROM maker recommends that you do a factory reset during an update, then it's a good idea to follow their recommendation.
The vast majority of ROMs wipe system as part of the zip install. This means that in most cases you do not need to wipe system... ever.
At this point, cache (not dalvik cache) is primarily used for recovery. It's used to store the recovery log and for storing OTA (Over The Air) updates. You probably don't need to wipe cache, and cache is already wiped as part of a factory reset.
In most ROMs, dalvik cache is stored in the data partition, so if you do a factory reset, you've also wiped dalvik cache. In a few custom ROMs, especially on older devices with small data partitions, the ROM maker may have moved dalvik to the cache partition to provide you with more room for apps. Since we wipe cache with a factory reset, again, you probably don't need to wipe dalvik. There are a few situations where you may need to wipe dalvik cache when installing updates, but you will know that it's needed when you are greeted with force closes when trying to open some apps.
Depending on your device and its configuration, you may have options for wiping internal storage, external storage, sd-ext, android_secure, and/or an option for formatting data. There's almost no reason that you would ever need to use these items. These options are there for convenience. For instance, if you're getting ready to sell your device, then it's a good idea to wipe everything on the device so that the new owner doesn't get your private data. Note that these wipe options may not be completely destructive. If you store especially sensitive information on your device or are really concerned about your private data, then you may need to look into other options to ensure that your data is fully destroyed.
norml said:
Wiping data, opposed to Formatting data.
TWRP FAQ
What to Wipe in TWRP
If you are switching ROMs (changing from one ROM to a completely different one) then you should perform a factory reset. A factory reset wipes data and cache (which includes dalvik cache). A factory reset will also wipe sd-ext and android_secure if your device has those items. 99% of the time, this is all that you need to wipe and you only need to do it once, not three times as some people would lead you to believe.
If you're installing a nightly update, then oftentimes you don't need to wipe anything at all. However, if you encounter strange behavior, then you may want to consider performing a factory reset. Of course, if the ROM maker recommends that you do a factory reset during an update, then it's a good idea to follow their recommendation.
The vast majority of ROMs wipe system as part of the zip install. This means that in most cases you do not need to wipe system... ever.
At this point, cache (not dalvik cache) is primarily used for recovery. It's used to store the recovery log and for storing OTA (Over The Air) updates. You probably don't need to wipe cache, and cache is already wiped as part of a factory reset.
In most ROMs, dalvik cache is stored in the data partition, so if you do a factory reset, you've also wiped dalvik cache. In a few custom ROMs, especially on older devices with small data partitions, the ROM maker may have moved dalvik to the cache partition to provide you with more room for apps. Since we wipe cache with a factory reset, again, you probably don't need to wipe dalvik. There are a few situations where you may need to wipe dalvik cache when installing updates, but you will know that it's needed when you are greeted with force closes when trying to open some apps.
Depending on your device and its configuration, you may have options for wiping internal storage, external storage, sd-ext, android_secure, and/or an option for formatting data. There's almost no reason that you would ever need to use these items. These options are there for convenience. For instance, if you're getting ready to sell your device, then it's a good idea to wipe everything on the device so that the new owner doesn't get your private data. Note that these wipe options may not be completely destructive. If you store especially sensitive information on your device or are really concerned about your private data, then you may need to look into other options to ensure that your data is fully destroyed.
Click to expand...
Click to collapse
Thanks - I realize this and am installing TWRP as we speak. (I just prefer it)
I was actually reading the Complete Guide in the general section and saw under CWM install that you need to format data between switching Roms.. I never actually did this ever with previous phones. Completely my fault for reading the CWM part, not the TWRP part, right under neath. I thought the Format Data was something S4 specific since this is my 2nd day with the device.
I'm now rooted with TWRP back on.
Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers
sergeantash said:
Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers
Click to expand...
Click to collapse
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.
davyleggend said:
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.
Click to expand...
Click to collapse
Ok, this has given me an idea - I have flashed fresh Cyanogen and now I'm attempting to restore just the 'data' and 'cache' elements of my backup by using the Philz 'Custom Restore' feature...fingers crossed!
So, my idea worked...my phone is now back up and running, what a relief!
I recently updating cyanogen12 to cyanogen13. Things were running well but while running backup I ran out of memory.
Realised I want installing lots of old apps I no longer used so thought I would factory reset and start again!!! Found out the hard way that this is not the done thing.
Now my phone starts to boot into recovery and all that happens is the 'Teamwin' page just flashes on and off. Is there any way to get the phone back or have I bricked it?
Thank you for any assistance
Flash TWRP with ODIN again, see if it boots, if not, flash CM13 without wiping from TWRP and see if it boots then
Make sure you clear the caches from TWRP, might be an idea to wipe SYSTEM before flashing CM13 again too
As long as you don't wipe DATA or INTERNAL STORAGE, you're apps etc will remain
Hello,
I recently did a backup (NucleaROM, 7.1) in TWRP and it strangely went to 101%. Stuck on "generating md5" for a minute.
Then, when I restarted my phone, it acted like 2 times slower than usual, from the boot animation, and didn't stop.
I then did a factory reset and tried flashing the ROM and Gapps again. Open GApps project couldn't finish, TWRP rebooted.
I received the "swipe to allow modifications" slide and actually slided it the second time, because I wasn't able to restore the first time, when I clicked on read only.
I now am stuck in the recovery, I have backups on my external card, TWRP won't read Internal card, I can't factory reset due to mount error and therefore can't restore any backup.
Everything went wrong just after trying to do a normal backup. What did I miss ?
Thx
Well good thing you have a backup on your external card. I'll suggest you perform a "Format Data" in the Advanced Wipe section of TWRP. It should be able to solve it. Looks like a minor corrupted storage problem.