Database Develop

[Q] Droid 4 CM10.1 Stuck at Boot

My phone will currently not boot bast the CyanogenMod boot screen.
I flashed my phone several months ago to CM10.1 It was the update that patched the "masterkey" bug. I have been using it daily since then with no problems.
Today, I turn my phone on, and it just hangs at the boot animation.
There were no significant changes since the last time it was powered on. I think I installed McPixel from the humblebundle, and uninstalled a game from the playstore called Krog. No setting changes of any significance.
I've tried booting into safestrape and deleting both the cache and the dalvik cache, neither has helped. My stock rom still loads just fine, but i had factory reset it quite a while ago. I do have a backup of the rom from about 40 days ago i can try restoring, but i would love a more nondestructive way to fix this.

Try booting into safestrap, wiping system, cache, and dalvik, then reinstall the ROM and gapps.
Droid 4 - Avatar

kwyrt said:
Try booting into safestrap, wiping system, cache, and dalvik, then reinstall the ROM and gapps.
Droid 4 - Avatar
Click to expand...
Click to collapse
0.o wouldn't that be a LOT more destructive than just restoring the old backup?

pyro42 said:
0.o wouldn't that be a LOT more destructive than just restoring the old backup?
Click to expand...
Click to collapse
Nope. You are not wiping data so all your apps, setting, etc will still be there.

the data itself will remain if you just wipe the system, cache and dalvik cache but be sure to reinstall the latest stable build of CM and gapps for it
Sent from my XT894 using xda premium

kwyrt said:
Nope. You are not wiping data so all your apps, setting, etc will still be there.
Click to expand...
Click to collapse
ah gotcha gotcha...
unfortunately it didn't work.
for troubleshooting's sake, i went ahead and made a backup of the rom in it's non-working state.
i restored my old backup, it boots just fine.
restored borked backup (tested it, still won't boot), wiped cache/dcache, wiped system, installed cm-10.2-20130821-NIGHTLY-maserati.zip and gapps 20130812, wiped cache/dcache again for good measure, then reboot and waited 10 minutes, still won't pass boot logo.
so i figure someting's wrong with Data right? so i rebooted to safestrap and did a factory restore, then wiped cache/dcache, and still won't boot.
so now i'm going at it the opposite direction. restoring the working backup, restoring just the data from the nonworking backup, then upgrading CM/Gapps
rebooting.. and....
blank screen with full backlight. not so much as a CM logo.
i guess for now i am going to restore back to the old backup, update the rom, and go about reconfiguring, unless anyone has any more suggestions?

pyro42 said:
ah gotcha gotcha...
unfortunately it didn't work.
for troubleshooting's sake, i went ahead and made a backup of the rom in it's non-working state.
i restored my old backup, it boots just fine.
restored borked backup (tested it, still won't boot), wiped cache/dcache, wiped system, installed cm-10.2-20130821-NIGHTLY-maserati.zip and gapps 20130812, wiped cache/dcache again for good measure, then reboot and waited 10 minutes, still won't pass boot logo.
so i figure someting's wrong with Data right? so i rebooted to safestrap and did a factory restore, then wiped cache/dcache, and still won't boot.
so now i'm going at it the opposite direction. restoring the working backup, restoring just the data from the nonworking backup, then upgrading CM/Gapps
rebooting.. and....
blank screen with full backlight. not so much as a CM logo.
i guess for now i am going to restore back to the old backup, update the rom, and go about reconfiguring, unless anyone has any more suggestions?
Click to expand...
Click to collapse
Yeah, definitely sounds like something in /Data. Only other possible option I can think of would be to use Titanium Backup. It has an option to "Extract from Nandroid backup". It's under the "SPECIAL BACKUP/RESTORE" options. I've never used that option before so I have no idea how or if it would work but might be worth a shot.

kwyrt said:
Yeah, definitely sounds like something in /Data. Only other possible option I can think of would be to use Titanium Backup. It has an option to "Extract from Nandroid backup". It's under the "SPECIAL BACKUP/RESTORE" options. I've never used that option before so I have no idea how or if it would work but might be worth a shot.
Click to expand...
Click to collapse
wonderful idea, unfortunately TB crashes when i point it at either backup.
buuut i did find Nandroid Manager * ROOT which looks like it might be working.

if you really wanna see if it is the data or not have you tried to
flash 10.2 or whatever you started out with... then restore -just-
the data to the freshly flash system and then do a wipe of all
said caches... I do that sometimes to get a fresh start on my
os itself.. works pretty well. Just do not restore the cache just
the data part. Or restore with MD5 checking... if it doesn't check
out then you know for a fact that the data partition in that specific
nandroid isn't any good :/

[Q] Resurrecting my Captivate, ONLY boots to CWM

I'm trying to resurrect my I897 Captivate. I put it in the drawer a couple of years ago with Glitch kernel and AOKP ICS on it. My wife destroyed her Skyrocket (S2) and she needs a phone to use as a stand-in for a couple of months.
I wiped it, no nandroid backup since I had no plans to use any of the data on it, and began trying to install Cyanogenmod. I was planning to use the recent M5 snapshot of CM11 but am ok with going to 10.2.1 stable if 11M5 doesn't work.
However, I just can't get it to boot. It will go into recovery mode fine (in fact, it boots to recovery even when no buttons are pressed).
I went back, wiped everything, formatted all partitions, and started with CM7, then CM9, then CM10.2.1 to get the partition scheme updated and just to be sure it wasn't CM11M5. However none of those change the issue. It just refuses to boot anything but recovery.
I've repeatedly done wipes and factory resets, including going back and formatting the partitions. I've tried the "install CM twice" trick. The phone just does not want to boot the images.
The install processes seem to go fine. No errors reported during .zip install.
I went through many different pages that are meant to break a recovery loop, most of which just have you do the basic reset and reboot, but so far have found no way to break the cycle.
Any ideas?

jahfry said:
I'm trying to resurrect my I897 Captivate. I put it in the drawer a couple of years ago with Glitch kernel and AOKP ICS on it. My wife destroyed her Skyrocket (S2) and she needs a phone to use as a stand-in for a couple of months.
I wiped it, no nandroid backup since I had no plans to use any of the data on it, and began trying to install Cyanogenmod. I was planning to use the recent M5 snapshot of CM11 but am ok with going to 10.2.1 stable if 11M5 doesn't work.
However, I just can't get it to boot. It will go into recovery mode fine (in fact, it boots to recovery even when no buttons are pressed).
I went back, wiped everything, formatted all partitions, and started with CM7, then CM9, then CM10.2.1 to get the partition scheme updated and just to be sure it wasn't CM11M5. However none of those change the issue. It just refuses to boot anything but recovery.
I've repeatedly done wipes and factory resets, including going back and formatting the partitions. I've tried the "install CM twice" trick. The phone just does not want to boot the images.
The install processes seem to go fine. No errors reported during .zip install.
I went through many different pages that are meant to break a recovery loop, most of which just have you do the basic reset and reboot, but so far have found no way to break the cycle.
Any ideas?
Click to expand...
Click to collapse
my advice is, go to stock GB, then flash ICS, flash a KitKat kernel, reboot recovery and then flash CM 11..
hope this works for you!

Yeah that was my next plan, already have the stock ROM downloaded. Will report back. Was just hoping there was a known issue that I could fix without reverting. Not a big deal Thanks.

Stock Rom
jahfry said:
Yeah that was my next plan, already have the stock ROM downloaded. Will report back. Was just hoping there was a known issue that I could fix without reverting. Not a big deal Thanks.
Click to expand...
Click to collapse
Hello jahfry! Glad to hear you got the stock ROM. Would you mind telling me where you got it from? All the links I've found here are dead… I am in a similar situation as you - managed to get a custom rom going but have lost all trace of EFS folder/ nv_data.bin file…. Need to go back to stock to start again… Any help appreciated!

asianlight said:
Hello jahfry! Glad to hear you got the stock ROM. Would you mind telling me where you got it from? All the links I've found here are dead… I am in a similar situation as you - managed to get a custom rom going but have lost all trace of EFS folder/ nv_data.bin file…. Need to go back to stock to start again… Any help appreciated!
Click to expand...
Click to collapse
Stickied threads: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
Search goes a long way

Unable to install latest Mokee build properly

Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?

isketch93 said:
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
Click to expand...
Click to collapse
I had 70% similar scenario ,but different error. i could boot into mokkee rom but crashed during initial setup ,below were the steps i used to fix it
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
got perfectly working Mokee ROM in MI3

bluethilak said:
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
Click to expand...
Click to collapse
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?

A nandroid backup is to be used in case of failure (and as a backup... but you should have backups anyway so data loss isn't the end of the world) - an app backup is so you can reinstall the apps with settings in Mokee.

isketch93 said:
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
Click to expand...
Click to collapse
Nandroid backup is nothing but a complete backup of both Rom and Data.It will in a zip format ad gets saved in your internal memory
[Clockworkmod for CWM/TWRP for TWRP recovery]
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
Let me tell you How I handle my backup plans for my device because at least per week i will be changing the ROM.
1) I always save my contacts in Google contacts(So a normal sync will do)
2)I backup all app data and Message data using EasyBackup
:good::good:

I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?

bluethilak said:
...got perfectly working Mokee ROM in MI3
Click to expand...
Click to collapse
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps

isketch93 said:
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
Click to expand...
Click to collapse
Dude banks gapps latest is for 5.1.0 lolipop ,mokkee is still in 5.0.x try other gapps ,PA or MInimal or get old Bank Gapps of correct lolipop version.:good:
---------- Post added at 10:06 AM ---------- Previous post was at 09:59 AM ----------
isketch93 said:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
Click to expand...
Click to collapse
Clear some space at least 2gb temporarily in you Internal Memory ,Since you will be backing up your App Data,it definitely requires a lot of space .

TWRP 2.8.7.1 Backup Failure?

Last night I suddenly started having issues with TWRP making a NANDROID backup. I checked the log and it says:
E: Error opening 'system/addon.d' -- error : Not a directory
E: Error in Generate_Tarlist !
Any ideas what could be going on? I searched the forum and found one other person with this issue and they didn't find a solution. I reverted to an older version of TWRP and still nothing. Any help at all would be appreciated, thanks.

No one?

I just finished doing a backup in TWRP 2.8.7.1 with no errors.
I don't know what could be causing yours. Maybe reflash the recovery? See if that works.

Peylix said:
I just finished doing a backup in TWRP 2.8.7.1 with no errors.
I don't know what could be causing yours. Maybe reflash the recovery? See if that works.
Click to expand...
Click to collapse
I've tried everything. Reverted back to older TWRP versions, reflashed, everything. I guess I'll have to just fully wipe my phone.

ComradeCase said:
I've tried everything. Reverted back to older TWRP versions, reflashed, everything. I guess I'll have to just fully wipe my phone.
Click to expand...
Click to collapse
Damn, well I hope you got it sorted.

Peylix said:
Damn, well I hope you got it sorted.
Click to expand...
Click to collapse
Figured it out! If anyone else is having this issue, make sure you have a flashable ROM + GAPPs on your internal SD and just wipe everything but internal storage and reinstall your ROM. It sucks but it worked and with Titanium Backup getting back to my old configuration didn't take long.

No Mobile Data after Nandroid Restore

I don't think I can edit the title so I'll write it here for anyone who wants to help: This problem is SOLVED. (Y)
So the matter is a bit complicated and I can't guarantee I even remeber everything I did but I'll try to include as much detail as I can:
I had the Stock Rom (OOS4.0.0) running, OEM unlocked & rooted when the OOS4.0.1 OTA notification kept nagging in the back of mind. I thought I should just leave it ago because I already had a feeling it would go wrong...
So I download the Full .zip and flashed it through TWRP 3.03-1 and after that it was stuck on the boot screen for more than 15 minutes or so. So I restarted it again and this time it booted butall my data was deleted and it gave me an error about the encryption having failed. But as you probably know, one can't flash anything on an encrypted phone so I checked back in TWRP and it was really encrypted. Checked back in the phone's settings: Also encrypted. I then used a tool to force decryption (it also wipes all the data) and I was back to square one.
From that moment on I tried: 1. restore nandroid (all partitions included [that includes EFS]). It got me to the booting screen, but when I unplugged it shut down and a reboot got me to the battery screen. I had 72% left so at this moment I thought it had nothing to do with it not booting at 72%. Then I wiped everything (checked every box in TWRP) and was left without any OS. Then I let my phone charge to 100% and re-restored the nandroid OOS4.00 and it worked but I had the Unlock-Bug, I was able to fix that. Then it booted but it wasn't able to recognize any SIM cards, so I fixed that by re-re-restoring with TWRP 3.03-0 (which automatically replaced 3.0.3-1 after the nandroid) and everything worked fine. until I went out today and realized I had no mobile data. I doubt it has something to do with EFS because everything else is working fine (calling, checking IMEI wih *#06#).
I then proceeded to check the APN and it looked ok, I then tried another SIM card (from the same provider) and it didn't change anything.
My provider is the german company 1&1 (1und1) but it uses vodafone APN.
I have no clue what to do right now so I am asking you guys for help.
Thanks in advance!

Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.

Inciter said:
Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.
Click to expand...
Click to collapse
First of all: Thanks for your reply.
I don't know if there was a misunderstanding but I only ever flashed the full 1,4gb .zips.
Also I am running 4.00, because I had to restore it as the 4.0.1 flash ruined my phone. Just now I flashed 3.03-1, wiped dalvik & cache and flashed the 4.02 .zip which I got from this [https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074] thread but it left me stuck on "patching image uncoditionally" or something and then I rebooted and now I am stuck on the +1 booting screen (not even the animation, just the +1 logo witht he "powered by android" signature in the bottom).
I have the feeling it's a software bug not related to what I did with my phone. it was just luck that I did not havfe that problem prior to my nandroid restore or something. I mean: Looking at it from a logical perspective: When you restore your phone with a full nandroid backup it should be exactly the same phone, shouldn't it?

Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.

Inciter said:
Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.
Click to expand...
Click to collapse
I have no problem with that, but my device does.
I can't flash anything because TWRP (bot 3.03-0 and 3.03-1) will be stuck at "patching system image unconditionally", ( I tried the full 4.02 .zip and the ful 3.54 .zip that I am 10000% sure used to work, because I used it before the Nougat release).
Wiping everything but Internal and USB OTG changes nothing.
If you have any idea how I can get to a fresh start, I would really appreciate it.
EDIT: I am sorry, I don't know what you mean by TugaPower Rom. I never installed anything like that - atleast not knowingly.

Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.

Inciter said:
Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.
Click to expand...
Click to collapse
So, I have the means to decrypt my device through a tool I found here on the forums last month. It does wipe all your data, though. Anyways: I was able to restore mobile data through an older nandroid backup (and yes: all my back ups include all partitions; glad I was smart enough to do that haha). That worked for me and made me come to the conclusion that the back up I used first was somehow corrupted. Then I restored the data partition using my most recent nandroid back up and now I am back in the game. Thanks for all your help so far!
The only thing that kind of makes me worry is that I only get ~60mbit/s through speedtest even though I should get 200. I know I was able to get 200Mbit/s at some point using that phone, but I don't remember if it was with OOS 3xx or the OOS 4.00 update. So I can't tell whether it has something to do with me restoring the phone, my WiFi connection (a speedtest with my lan-connected desktop gave me 200) or just an android bug.
I'll wait until weekend when I have the means to test it with another 200k connection - and imho 60k is enough for anything I do with my phone anyways and I don't plan on reselling the phone in the future, so it won't kill me even if it is nandroid-related.

Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.

Inciter said:
Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.
Click to expand...
Click to collapse
Thank you, I just checked the wifi-speed with an iPhone 6 and it even got lower results (>30k) so I assume it has something to do with the WiFi itself at the moment and not with the OP3t.
And even if the backups are not always satisfying: I want to quote someone I read on some forums doing my research to fix this phone: "The seasoned user knows: A backup makes the difference between an awesome phone and a beautiful brick." That is a most evident truth to me now haha.