Database Info

[Q] Recovery Reboot problems

Hi, All,
Sorry if this has been answered before, I could not find it through search.
Whenever I reboot my Droid 2 Global, it goes straight into recovery (ClockWorkMod). I press the camera button and it reboots into the OS just fine. I tried uninstalling Clockwork, reinstalling ClockWork but that does not help.
Tried flashing but the regular firmware that I found did not work for my D2G phone.
Anyone has any clue on how to fix this?
Thanks,
shadov

Try actually removing CWM hijack files, and then reinstalling it.
Go to /system/bin, find logwrapper.bin; if it's there, delete logwrapper and rename logwrapper.bin to logwrapper. Check if the problem persists (I highly doubt it), then try reinstalling CWM.

Worked
That worked, thanks, man!
Are there any resources that explain how ClockworkMod (or any recovery hijacking) works? Wanted to understand better what actually happens on the system level.
Thanks

The false logwrapper CWM installs starts the CWM binary when there's a certain file present in a certain directory. If there's no such file, it just starts logwrapper.bin and startup continues as usual. That's about it.

I tried installing ginerbread update abd it fails. That's why I am trying to solve this problem in the first place.
When I tried installing the update today, it downloaded the update, rebooted and went into recovery partition and started extracting it (progress bar was moving for about 5 seconds), then I saw droid with exclamation point, phone rebooted again and said "Update failed"
Any tips?
Sent from my DROID2 GLOBAL using XDA App

I'm a bit tired of explaining this all over again.
Download the standalone update file from somewhere, or fetch it from your phone's /cache directory with Root Explorer once the download completes (do not confirm installation, just fetch the zip file). Place it into the root directory (/) of your SD card. Rename it to update.zip. Reboot into stock recovery. Choose install sdcard:update.zip. Check the error messages it displays.
For 99% of the cases the problem is CWM's logwrapper.

[Q] CWM Backup Folder not showing - CWM sees backups

Okay, so I am rooted on stock with ElementalX and philz touch recovery. I typically alternate between elementalX and stock kernel. About 2 weeks ago whenever I make a backup it backups fine, however when I go to my clockworkmod folder via root explorer it is not there. However Philz touch/CWM sees the backup folder and can restore and backup to it. I have wiped everything, I have flashed back to stock with the firmware and fastboot, where it completely wipes everything with a fresh install. Same results. I am out of ideas. If I try to copy over a clockworkmod folder with backups I have on my PC or even try to create a clockworkmod folder it gives me an error that its unable to create this folder and or copy it from my PC to my Nexus 5.
Anyone have any ideas as to what is happening? I even tried philz touch to make backups as if they were made in TWRP, so it creates a TWRP folder, but that does not do anything either. Any help would be appreciated as I am out of ideas.

ozzmanj1 said:
Okay, so I am rooted on stock with ElementalX and philz touch recovery. I typically alternate between elementalX and stock kernel. About 2 weeks ago whenever I make a backup it backups fine, however when I go to my clockworkmod folder via root explorer it is not there. However Philz touch/CWM sees the backup folder and can restore and backup to it. I have wiped everything, I have flashed back to stock with the firmware and fastboot, where it completely wipes everything with a fresh install. Same results. I am out of ideas. If I try to copy over a clockworkmod folder with backups I have on my PC or even try to create a clockworkmod folder it gives me an error that its unable to create this folder and or copy it from my PC to my Nexus 5.
Anyone have any ideas as to what is happening? I even tried philz touch to make backups as if they were made in TWRP, so it creates a TWRP folder, but that does not do anything either. Any help would be appreciated as I am out of ideas.
Click to expand...
Click to collapse
CWM is outdated.
"Internal Storage" on the Nexus 5 is /data/media/0 (which is what /sdcard is also symlinked to)
CWM uses the outdated legacy location of /data/media/clockworkmod (note the lack of /0)
Therefore you cannot see CWM backups if you look in the internal storage while booted into Android.
Development on Philz Touch has also come to an end - you should use TWRP.

Lethargy said:
CWM is outdated.
"Internal Storage" on the Nexus 5 is /data/media/0 (which is what /sdcard is also symlinked to)
CWM uses the outdated legacy location of /data/media/clockworkmod (note the lack of /0)
Therefore you cannot see CWM backups if you look in the internal storage while booted into Android.
Development on Philz Touch has also come to an end - you should use TWRP.
Click to expand...
Click to collapse
Flashed TWRP and redid a new backup, went to the root explorer and no folder fo TWRP is present, if I go back into TWRP it sees the backup I made but that is it. For some reason I am unable to see the folder.... any ideas?

ozzmanj1 said:
Flashed TWRP and redid a new backup, went to the root explorer and no folder fo TWRP is present, if I go back into TWRP it sees the backup I made but that is it. For some reason I am unable to see the folder.... any ideas?
Click to expand...
Click to collapse
Try deleting the TWRP folder using TWRP itself, reboot the recovery, change a setting or two then make a backup again.
Also make sure you're using a newer version of TWRP if you aren't already.

Sounds like a job for restorecon

rootSU said:
Sounds like a job for restorecon
Click to expand...
Click to collapse
OP says he completely wiped everything while flashing factory images though, so I dunno

Lethargy said:
OP says he completely wiped everything while flashing factory images though, so I dunno
Click to expand...
Click to collapse
If recovery can see it in /data/media/0.but android cant, it must mean storage isn't aligned correctly. Root cause? Unknown. Workaround has to be restorecon though
Easy test. Browse to /data/media/0/TWRP with a root explorer

rootSU said:
If recovery can see it in /data/media/0.but android cant, it must mean storage isn't aligned correctly. Root cause? Unknown. Workaround has to be restorecon though
Easy test. Browse to /data/media/0/TWRP with a root explorer
Click to expand...
Click to collapse
Guess its still possible but wouldn't really expect it to happen after a full wipe. Worth a shot anyways now that you've mentioned it.

rootSU said:
If recovery can see it in /data/media/0.but android cant, it must mean storage isn't aligned correctly. Root cause? Unknown. Workaround has to be restorecon though
Easy test. Browse to /data/media/0/TWRP with a root explorer
Click to expand...
Click to collapse
What is restorecon?
Edit - Flashed toe factory image again and each time I run the flash factory image I get this at the end of each flash, see attached
Found this, its the same issue I am having:
http://androidforums.com/threads/twrp-lollipop-and-the-nexus-5.883331/
Now after flashing a factory image phone just hangs, bootanimation goes on forever and ever, so for now I have no working Nexus 5. Any ideas?
Edit - Flashed TWRP and used MTP mode, internal data is completely blank, no android folder, etc... just empty...

Update, flashed factory image for 4.4.4 and that flashed without errors, going to let it boot up and do its thing. Once done I will try to flash 5.0.1 again.. will report back.
Update - Guess I am stuck for now on 4.4.4. Flashing 5.0 or 5.0.1 fails on userdata as previous screenshot.

ozzmanj1 said:
Update, flashed factory image for 4.4.4 and that flashed without errors, going to let it boot up and do its thing. Once done I will try to flash 5.0.1 again.. will report back.
Update - Guess I am stuck for now on 4.4.4. Flashing 5.0 or 5.0.1 fails on userdata as previous screenshot.
Click to expand...
Click to collapse
Out of curiosity, how much ram do you have on your pc?
Sent from my Nexus 9 using XDA Free mobile app

I am running on 8gb ram

I think I may have resolved the issue, I factory flashed 4.4.4, rebooted, then flashed a recovery, rebooted, then copied over a nandroid backup from end of last month, and restored from that back to 5.0.1. All seems well now, I did not wipe anything when doing the restore. Everything seems to be working now.. will report back if I see any other issues. Thank you to all for your assistance.

rootSU said:
Sounds like a job for restorecon
Click to expand...
Click to collapse
I am back with the same issue. Flashing 4.4.4 image flashes okay, however any attempt at flashing 5.0 or 5.0.1 causes an error just as its wiping userdata. Only way around is to flash 4.4.4 and then restore with a nandroid, which I keep plenty of those laying around.
Mind if I ask what the tutorial is for restorecon? Thank you.

TWRP 2.8.6.2 Fails to Backup

I installed TWRP 2.8.6.2 from the link in the first post of the Lollipop thread (http://forum.xda-developers.com/photon-q-4g-lte/development/cyanogenmod-12-1-photon-q-t3073781 ). I assume this is the latest/correct version for PQ?
I want to backup data so I can reformat data as f2fs and be able to use latest kernel.
I've tried backing up just data, or all four selections, with and without compression. Everything I've tried fails with error 255.
The log shows /data/data/com.skype.radier failed. So I deleted skype cache, data, then uninstalled. Retried backup again and still fail. Tried to manually delete folder, it won't delete nor will any of the subfolders (error 39 from es explorer). Tried to delete using TWRP's file manager, still won't delete (ERROR=1)/
a piece of TWRP log where it shows the errors.
I:addFile '/data/data/com.skype.raider/files/myskype.name/media_messaging/emo_cache/^80485FFBB32073DC42B65F944722AD423320F0EA974A6BF94F^pthumbnail_5b11e5f1-d716-4f57-842d-6ffdb8b257f3_distr' including root: 1
E:Error adding file '/data/data/com.skype.raider/files/myskype.name/media_messaging/emo_cache/^80485FFBB32073DC42B65F944722AD423320F0EA974A6BF94F^pthumbnail_5b11e5f1-d716-4f57-842d-6ffdb8b257f3_distr' to '/external_sd/TWRP/BACKUPS/T0695028XX/2015-12-15--15-40-38_cm_moto_msm8960_jbbl-userdebug_4.4.4_KTU84Q//data.f2fs.win000'
I:ERROR tarList for thread ID 0
E:Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/T0695028XX/2015-12-15--15-40-38_cm_moto_msm8960_jbbl-userdebug_4.4.4_KTU84Q/data.info'
E:createTarFork() process ended with ERROR=255
Backup Failed.

Well just great. I wanted to backup but instead deleted everything. After posting I kept searching and trying ways to be able to delete that. Finally came to something that suggested using fcsk to check/repair the filesystem. Said to boot to recovery, adb shell, unmount and then run it. That didnt work cuz there was no unmount command in adb shell that I could find. Then I found in the TWRP menu there was a repair filesystem command, thought that was great! Ran it. And it wiped my data folder completely.
Not very happy right now.

I had the same problem as you when trying to convert to F2FS, and lost many hours of work as well! In my case the backup actually worked when using compression, so I thought all was good even though I never could get it to restore. I was able to get some of the data back by untarring the backup files themselves though, so you could maybe even look at the unsuccessful backup files if you had something important to recover.
In post 161 of this thread http://forum.xda-developers.com/pho...anogenmod-12-1-photon-q-t3073781/post64064173 a developer has compiled TWRP 2.8.7.0 for the Photon Q and it appears backup works. I never have tried it myself though as I hadn't seen the post in time. I just ended up using titanium backup.

Well I'm in an even worse situation now. I tried restoring from the failed backup and now my phone crashes and reboots a minute or two after booting. So I figured I better reinstall gapps. However, I can't get into recovery anymore. Just sits forever of the TeamWin screen. Reloaded recovery thru adb fastboot and it still does the same thing. So I can't even get into recovery to try flashing gapps again or if it came to it wipe data and start clean. I'm phoneless.

RSD Lite back to stock...

FlashFire with HTC One A9?

Anyone used ChainFire's FlashFire with the One A9?
I've used it for backups successfully but have yet to restore anything with it (a little squeamish to do so :silly.
And I'll just add, if anyone has used it and could offer any tips or procedures that would be great.

FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app

CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app
Click to expand...
Click to collapse
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?

theNdroid said:
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?
Click to expand...
Click to collapse
Of course. Root is required to use FlashFire. I use Xposed as well, and I've had no problems updating via FlashFire.

CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Click to expand...
Click to collapse
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?

eelpout said:
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?
Click to expand...
Click to collapse
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***

CSnowRules said:
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***
Click to expand...
Click to collapse
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.

eelpout said:
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.
Click to expand...
Click to collapse
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.

CSnowRules said:
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.
Click to expand...
Click to collapse
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.

eelpout said:
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.
Click to expand...
Click to collapse
Ok, this post will go a bit off topic. That being said, I can offer two courses of action. I take no responsibility for anything in this post.
Safest--almost no risk (my personal preference)
1. Backup your data partition, including internal SD via TWRP to ext SD or USB OTG drive. Flash the latest RUU from HTC. Boot stock and apply OTAs until there are no more updates available. Fastboot flash the latest TWRP, and finally restore your data and flash the latest SuperSU via TWRP. Reboot your fully updated, rooted A9 with all your data still intact.
A little risky and untested to my knowledge--could result in a hard brick if something partially fails. FLASHING BOOTLOADERS IN FLASHFIRE IS STILL ALPHA FOR HTC DEVICES!!! This may work with s-on...but may require s-off.
Your system partition must have never been mounted r/w for this to work.
2. Download the OTA zips for your phone from the first update available to the latest and the latest SuperSU and TWRP. Use FlashFire to do everything in one shot. Select allow flashing bootloaders in FlashFire settings, select your OTAs for installation from oldest to newest (don't select restore boot and recovery), select TWRP and SuperSU for installation, disable everroot and preserve recovery. Cross your fingers and timidly press flash... If all is successful, you should have the same end result as option 1.
I STRONGLY recommend the first method, but if you're feeling lucky and decide to try the second method, please share how it goes, since this post is FlashFire related and this would be the ultimate test of FlashFire for our devices.

For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.

NuShrike said:
For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.
Click to expand...
Click to collapse
The solution for problem 1 can be handled in TWRP. The files can be deleted via TWRP's file manager or the built in terminal, which may be easier for some people.
Also, the solution for the corrupted data and internal SD is to create an image of the data partition (just like the system image backup option). This can be done via dd in TWRP or adb. It requires a large amount of storage and it takes longer, but I've had to do it, since I use VIP Access by Symantec for work. A normal file based backup in TWRP breaks that app. This also keeps the pin/fingerprint data intact.
If we could have that implemented in a user friendly manner, that would be great, but I'm sure CaptainThrowback and Chainfire both have bigger issues to deal with. I could probably figure out a solution, but the work wouldn't be worth it for my own benefit, since I'm fluent with the Linux command line.

oneplus 6 LineageOS 17 -> 18 . Failed TWRP Restore (255)

Greetings,
I had lineageos 17 on my one+6 and after making a twrp backup and making sure i had all my files that i wanted i took the plunge and upgraded to lineage 18.
This would have been great except that I didnt actually have all the files I wanted. I critically forgot to make a manual separate backup of signal messenger. I need to get the history of signal messenger back. The only way i can think to do this, is to restore the twrp backup i made before upgrading and then making a backup with signal messenger app and then restoring the signal backup in lineage 18.
I attempted to restore my TWRP backup. When I made the TWRP backup I had checked ALL the boxes and saw no errors on the screen. When i attempted to restore i checked all the boxes on the screen and got what appears to be a fairly common error (255) when attempting to restore data (not sd/usb).
After, when i went to reboot twrp notified me that there was no OS installed. I rebooted anyway. I ended up stuck in a bootloader loop. I then downloaded
10.3.6-OnePlus6Oxygen_22.J.48_OTA_048_all_2010042239_c0c1fee2ee-FASTBOOT.zip
Click to expand...
Click to collapse
Then i unzipped that file and typed in the linux terminal:
fastboot -w update images.zip
Click to expand...
Click to collapse
I now have a working phone again.
I would like to know how do i restore the TWRP recovery image that I made at the beginning of the whole process. I'm pretty sure if I can do that I can then make a new Signal backup and be fine.
While doing lots of trouble shooting for the last 36 hours or so, it seems relevant to mention that my phone used to require I enter a PIN in order to use it, and I had to enter that same PIN in TWRP before I made the backup. The temporary OxygenOS I installed to just have a working phone number for work does not have a pin.

I have never had any success restoring TWRP backups so I eventually gave up relying on them after the 4th failed attempt.
But I distinctly remember reading this piece of advice:
0. Copy the TWRP backups onto a separate storage (I assume you have already done that)
1. Install the original ROM that is present in the backup; don't restore the System partition
2. Once installation has completed, restore only the Data partition and ignore all the rest such as cache, system, boot, etc.
3. Reboot
Personally, I have never tried it. But just from reading it, it seems like it may just work. Or it might not.

adeklipse said:
I have never had any success restoring TWRP backups so I eventually gave up relying on them after the 4th failed attempt.
But I distinctly remember reading this piece of advice:
0. Copy the TWRP backups onto a separate storage (I assume you have already done that)
1. Install the original ROM that is present in the backup; don't restore the System partition
2. Once installation has completed, restore only the Data partition and ignore all the rest such as cache, system, boot, etc.
3. Reboot
Personally, I have never tried it. But just from reading it, it seems like it may just work. Or it might not.
Click to expand...
Click to collapse
I appreciate the reply.
It's the data partition that's throwing this 255 error, which it seems to have something to do with it being encrypted i'd guess? In the future, is it possible to just dd the whole thing somehow?

karenmcd said:
I appreciate the reply.
It's the data partition that's throwing this 255 error, which it seems to have something to do with it being encrypted i'd guess? In the future, is it possible to just dd the whole thing somehow?
Click to expand...
Click to collapse
Have you tried wiping the /data partition from TWRP's Advance Wipe?

karenmcd said:
Greetings,
I had lineageos 17 on my one+6 and after making a twrp backup and making sure i had all my files that i wanted i took the plunge and upgraded to lineage 18.
This would have been great except that I didnt actually have all the files I wanted. I critically forgot to make a manual separate backup of signal messenger. I need to get the history of signal messenger back. The only way i can think to do this, is to restore the twrp backup i made before upgrading and then making a backup with signal messenger app and then restoring the signal backup in lineage 18.
I attempted to restore my TWRP backup. When I made the TWRP backup I had checked ALL the boxes and saw no errors on the screen. When i attempted to restore i checked all the boxes on the screen and got what appears to be a fairly common error (255) when attempting to restore data (not sd/usb).
After, when i went to reboot twrp notified me that there was no OS installed. I rebooted anyway. I ended up stuck in a bootloader loop. I then downloaded
Then i unzipped that file and typed in the linux terminal:
I now have a working phone again.
I would like to know how do i restore the TWRP recovery image that I made at the beginning of the whole process. I'm pretty sure if I can do that I can then make a new Signal backup and be fine.
While doing lots of trouble shooting for the last 36 hours or so, it seems relevant to mention that my phone used to require I enter a PIN in order to use it, and I had to enter that same PIN in TWRP before I made the backup. The temporary OxygenOS I installed to just have a working phone number for work does not have a pin.
Click to expand...
Click to collapse
For what I know you need your device to be decrypted to restore from custom recovery.

I've had some luck in similar situations using Titanium Backup to extract an app and data from TWRP backup.
Your mileage may vary.