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.

System ui stops after fixing permissions

After fixing permission and rebooting I get the Unfortunately system ui has stopped working error. I have tried fixing the permissions in ROM manager and in cwm recovery, same thing happens.
I have tried wiping cache and dalvik after both methods and still the same thing.
I have tried restoring data to system ui with titanium backup after fixing permission and before rebooting and still get the error on reboot.
When I run fix permissions it fixes a lot of them, and I have deleted a lot of unnessary apks from my system apps, but my system has been running great without them, haven't had any issues before fixing permissions.
I have up to date nandroid and titanium backups so I am not in a panic, I am able to restore everything back again, but I just want to know WHY I can't fix permissions.
Any ideas? I am stumped.
Thanks in advance!
Sent from my GT-p5110 using Tapatalk HD

[Q] Need help!! File Permissions

Hi all,
I am new here and here goes my first post/querstion at XDA.
I was using some apk when my Device suddenly crashed. I restarted, everything looked fine. The problem started when I tried to open other apk which needs data file from Android Data folder for second operation. The apk was not able to access the files from data folder. I checked my file explorer and found the permissions(displayed at the end of the folder) have changed to -drw(for sure) from -rw(most probably). With this I am not able to delete/move any file from the device storage because the permissions of all other folders have changed to as abaove. If I try to move file, it makes a new copy on my extStorage but the original file is there as it is. The files can't be deleted either. Since my tab is rooted, I installed Root explorer to change file permissions. The permissions under Owner are all unchecked and Group/Others are checked. When I check the Read/Write/Execute permissions for owner, it says cannot be modified(its default disability message). Fed up of all this I went for Factory reset as a final option. I tried to backup using Ti but after some 10% it said not enough space. So I manually backed up whatever I could and went ahead with reset. I successfully did the factory reset and my tablet looked as fresh as when I bought it the first time. All factory apps only but when I was about to be happy, I opened the device storage just to find all those files and data still there, staring at me with their -drw stamp.
My device is Iberry(China I guess) and works on ICS. It is rooted. I had Su Superuser and busy box installed prior to the factory reset but after Factory Reset all apps are gone except their data in the device storage. Please help!

deleting system apps in recovery keeps them in running os

I want to switch from supersu to superuser, and having an interesting problem that supersu somehow covered up. I have a Nexus 5x running the stock rom. With every months upgrade I would flash using fastboot, go into twrp recovery before first full boot and remove a bunch of unneeded applications in /system/app. When I would boot up those applications would be gone. Somehow this isn't the case with superuser. I can still go into recovery and remove them, but when I boot up all the applications are still in /system/app. If I go back into twrp they are still shown as being missing. I've tried installing es file explorer, but it's unable to delete the applications once the system is up. remounting /system doesn't work either. Any help?
Unrooting supersu caused all the applications to come back; so does supersu not really delete them either, but somehow prevents them from showing up following the recovery scheme or something?

bsd1101 said:
I want to switch from supersu to superuser, and having an interesting problem that supersu somehow covered up. I have a Nexus 5x running the stock rom. With every months upgrade I would flash using fastboot, go into twrp recovery before first full boot and remove a bunch of unneeded applications in /system/app. When I would boot up those applications would be gone. Somehow this isn't the case with superuser. I can still go into recovery and remove them, but when I boot up all the applications are still in /system/app. If I go back into twrp they are still shown as being missing. I've tried installing es file explorer, but it's unable to delete the applications once the system is up. remounting /system doesn't work either. Any help?
Unrooting supersu caused all the applications to come back; so does supersu not really delete them either, but somehow prevents them from showing up following the recovery scheme or something?
Click to expand...
Click to collapse
You aren't doing something right or you don't have something setup correctly. With root, you should be able to unintelligible them completely.
When you removed them, did you wipe cache and dalvik/ART cache before rebooting? If not then the system probably still thinks they are there because they still have data loaded into cache.
I recommend sticking with SuperSU, superuser doesn't work as well as SuperSU
Sent from my SM-S903VL using Tapatalk

I've been googling a bit more. As it turns out there are two system partitions for nougat; in nexus 5x and some other devices apparently. This became more apparent when the file recovery-from-boot.p; which I rename in order to prevent recovery from being overwritten is not renamed when booting the OS. Nougat apparently pulls the system files from somewhere else. So whatever Chainfire did makes it boot the same partition as visible in recovery. Fully unrooting brings all those apps/system partition back. Haven't been able to find a good post that tells me how to to circumvent this without SuperSU; or exactly how this works.

How I fixed my bootloop problem without any format / data loss

Hello everyone, I was able to fix my bootloop occuring after flashing a zip on magisk, without any data loss. I wanted to share what I did to fix since it may be helpful for others. It is useful method worth trying if you know what caused the bootloop. It is definitely not a universal method of fixing bootloops or anything, but If you have a similar problem, you can try these steps.
The bootloop happened after I flashed a zip on Magisk that I downloaded using EdXposed Manager app. I remember downloading the latest alpha version zip and flashing it using Magisk (I had already had the riru core and riru edxposed modules installed on Magisk but on Edxposed manager app, it was showing some error, so I also flashed the zip that I downloaded using the app. I think this caused the bootloop somehow. ) I had no backups.
(I had also "unable to mount /data" problem on TWRP, I am explaining how I fixed that also, if you don't have the problem, you can skip this paragraph)
My TWRP version was 3.2.1.0. And when I was in recovery mode, I was getting "unable to mount /data" error. This is actually a well-known error, but I was able to fix it without a format by just updating my TWRP to 3.3.1.0. After the update, somehow, internal storage could be mounted and everything was fine. My goal by trying to fix this problem is to be able to have a backup using TWRP (using backup feature on TWRP) (just make sure that you didn't choose the compression option on options tab of TWRP backup page).
If you don't have "unable to mount data" problem at all, just make a TWRP backup. (just make sure that you didn't choose the compression option on options tab of TWRP backup page).
So, after having a TWRP backup of everything (actually just System and Data backup would also be fine), I tried to edit my backup files to fix the problem that caused the bootloop.
I changed 2 things in my backup files (you can edit the backup files ending with .win001 etc using 7zip on windows or anything similar. since the backup files are not compressed, you can just delete files) (I edited only the "Data" backup files due to my specific problem, but if your problem is something different, you may have to edit different files also):
1) I deleted everything about EDXposed manager(com.xx.edxposedmanager files) (It might have nothing to do with the fix, I am not sure)
2) In one of the data backup files (probably in the last one), there is a folder called "adb". In adb, there is a "modules" folder. I deleted riru core and riru edxmanager folders in modules.
After these steps, I restored "Data" and "System" using TWRP restore. Bootloop is fixed without any data loss.
If your bootloop is caused by something different, (the point I am trying to tell is) you can edit the nandroid backup files if you know the root of the problem and maybe fix your phone. When I was editing the backup files, I had no hope. As I said, I think this method is worth trying.

I Found this to be true. I also don't see the reason to reflash everything to fix a problem. Thank you for this tutrorial this is an undocumented tactic and i don't know why. Before i discovered this type of surgery i operated under the assumtion that android must be different from other operating systems in some way which would make this impossible. But like you i delved deeper and discovered that this is like a dark art the devs keep to themselves because of what ever but it works. I like this type of post and usually aside from asking for help or a little feed back this is the only type of post i ever make. I mean how do you expect people to learn how to do anything if you never teach them anything useful. EX: "You didn't do it exactly right from the beginning because if left out one thing in my tutorial so you would fail now erase everything and start over." "I only did that to teach you to backup" such bull ****! Thanks again for fighting the good fight.