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.

Need experienced dev help w/ adb root vs. flashing *.tar (/system) root through Odin

I was originally rooted by using invisiblek's original "stock" root, which contained some Sprint stuff, so I opted to do a clean start from a stock Verizon rom, but to save time I rooted using the adb script method from GS3DebugFSRoot http://forum.xda-developers.com/showthread.php?t=1792342 instead of Root66, which requires a 1.5 GB image download then must be flashed through Odin.
I did this to avoid some of the strange app behaviors from the rooted "Sprint" rom, but after rooting through adb with an automated script, some root apps don't function properly, even though they're getting root permission.
After doing some research and restoring my sprint NAND backup several times to compare, the main things I noticed are:
1. After rooting through adb, the Superuser.apk app is installed in /data/app (which is a user app location) as opposed to /system/app in the case of the flashable root method.
2. Superuser.apk is called com.noshufou.android.su-1.apk instead
3. Superuser.apk from a flashed rom has these permissions (seen using root-expl)
rwsr-sr-x, but the adb method file xxxxxx.su-1.apk has these permissions rwxrwxr-x
4. The owner of the file is "root" when flashed through Odin, but "system" when rooted with adb.
Otherwise, the su binary itself is ok, it is a newer version and larger in size compared to the flashed versions, but it has the right permissions and is located correctly in /system/xbin.
I tried deleting the xxxxx.su-1.apk in /data/app and copying Superuser.apk to /system/app, to make it a system app, reset permissions and "owner" and "group" to root, but lost root after rebooting, so had to start back from my NAND backup again.
Does anyone know how to make Superuser a system app in the /system/app folder without losing root?
Also, I'm not sure this is the cause, but Titanium Backup has a hard time detecting root every time I start it, and has to be restarted multiple times, which wasn't a problem when flashed root w/ Odin, and most importantly, DroidWall is not blocking ANYTHING, whether it's in whitelist or blacklist mode, which it did when I used Odin to flash a rooted rom. I've tried everything, bu to no availe, can a dev that might have an idea what is going on here, help me with this and point me in the right direction to look for what to fix to get DroidWall to work, and if that is causing these issues, to get Superuser installed in the right folder?
Thank you

Nvm, I can't seem to find it again, I know I saw it somewhere though. If this was the OG Droid or Droid 2 I could tell you how to adb push no problem, but it's my first Samsung device. I don't know if anything is different, and I don't wanna be responsible for a brick :S

[Q] Rooted Nexus 5 - Return to total default '/supersu'?

Hey guys,
I've done a little Google-ing but I can't find an answer to this one...
So I rooted my new Nexus yesterday but today I started to create myself some backups of the stock ROM just in-case I ever need or want them.
While I was doing this I went through the following process:
1. Ran Google's Factory Image: https://developers.google.com/android/nexus/images#hammerhead.
2. Installed TWRP through Fastboot.
3. Rebooted my bootloader.
4. Opened TWRP's File Manager.
5. Noticed a weird folder...
So from the steps that I have listed above, I'm pretty sure that It's safe to say that the only data/software that is held on my device's storage at the particular point in time is Google's (excluding TWRP), correct?
So back to this weird folder... I noticed a folder in the following directory "/" and it was called "supersu". Is this folder something to do with the Stock Google OS or is this some kind of left-over folder from the ROM that I had used yesterday (unlikely seeing as I have just ran the factory image)?
Here is a DIR Listing of "/":
boot
cache
data
dev
etc
firmware
licence
persist
proc
recovery
res
root
sbin
sdcard
supersu (the folder which raised my suspicion)
sys
system
tmp
usb-otg
Am I in the wrong mindset? Does Google's Factory Image re-format the whole device including "/" or does it just do certain DIRs? Is that "supersu" folder mine or did Google already have that?
Thanks,
LewisD94
EDIT: I know what it is!
TWRP have a built-in service that allows you to install SuperSU to your device without having to download or flash it manually, I'm pretty sure that this folder would have landed it's self on my device when I installed the TWRP recovery through Fastboot... It's the only thing I can think of, testing it now but flashing the Factory Image without a custom recovery. Will report back with results.
FIXED: It must be something to do with TWRP's SuperSU service as I previously mentioned...
I have just ran Google's Factory Image: (https://developers.google.com/android/nexus/images#hammerhead) and installed ES File Explorer then navigated to "/" and I no longer have the folder in question...
New DIR listing of "/"

I don't have that folder. I have the latest TWRP installed. I really wouldn't worry about it though. Just delete it if you don't use Super SU
Sent from my Nexus 5

SuperSU is superuser which grants root access to apps. It was likely left over from a previous ROM because unless you completely wiped the SD card it remains inert.
When you return to completely stock like in the general sticky everything is going byebye.
There are stock ROMs hanging around development that are deodexed or odexed whatever you want. Some of them even have goodies inside.

When you root and unlock bootloader, the super user is installed during the process. Nothing to worry about. SU acts as your phones front door security screening any elevated/administrative task. This is what sprint personnel look for when excepting returns on devices. They know if your rooted and you try to say there is a issue with your device, if they see SU installed they'll know it was probably you who caused it. Besides the main fact but you have nothing to worry about. If you go completely stock and re lock your bootloader, just delete the folder off your SD card.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Must be a TWRP thing. I use CWM and I dont have a supersu folder.

[Q] Can't restore TiBu update.zip on 5.1

I created an update.zip with my apps+data using Titanium Backup (Pro) on 5.0.1 before I updated to 5.1. I then did a completely clean flash of the 5.1 image (following these instructions, method 2). After that, I did the basic setup of Android and installed Titanium Backup again from the store. I rebooted, flashed and booted into TWRP, then flashed SuperSU 2.46. Rebooted into the system, gave TiBu root access (since other threads said you need to do that before update.zip files can be flashed). Rebooted back into TWRP, finally try to flash update.zip, but I get the error below. Does anyone know why this would be the case?
Additionally, since receiving the error, I have installed busybox and tried fixing my SD card permissions in case they were the problem, no dice.
I do have all of the individual app backups on my computer if update.zip isn't going to work for some reason, and I took a full TWRP backup before upgrading as well (transferred all to my computer since the instructions clear personal data).
Error message:
Installing '/sdcard/update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Failed to sysMapFile '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
UPDATE: Just discovered that Android is doing the "Optimizing apps" process at every single normal boot, whether I flash something or not.

vaindil said:
I created an update.zip with my apps+data using Titanium Backup (Pro) on 5.0.1 before I updated to 5.1. I then did a completely clean flash of the 5.1 image (following these instructions, method 2). After that, I did the basic setup of Android and installed Titanium Backup again from the store. I rebooted, flashed and booted into TWRP, then flashed SuperSU 2.46. Rebooted into the system, gave TiBu root access (since other threads said you need to do that before update.zip files can be flashed). Rebooted back into TWRP, finally try to flash update.zip, but I get the error below. Does anyone know why this would be the case?
Additionally, since receiving the error, I have installed busybox and tried fixing my SD card permissions in case they were the problem, no dice.
I do have all of the individual app backups on my computer if update.zip isn't going to work for some reason, and I took a full TWRP backup before upgrading as well (transferred all to my computer since the instructions clear personal data).
Error message:
UPDATE: Just discovered that Android is doing the "Optimizing apps" process at every single normal boot, whether I flash something or not.
Click to expand...
Click to collapse
You have TWRP and you flash successfully supersu2.46. Why you need update.zip? what is this?
just in case run in terminal:
Code:
su
restorecon -FR /data/media/0
maybe it help.

Snapchat on a rooted Pixel?

Hi,
Is there a current way to use snapchat on my rooted pixel? I tried unrooting to log in and re-root, but it didn't work as well.
I don't have another rooted device to do titanium back up and I am on android Nougat so I can't install xposed frameworks.
any suggestions people?

unrooting, logging in, and rerooting always works for me....is the app data being deleted somehow when you unroot/root?

Unrooting, logging in and rerooting also worked perfectly for me a couple of times. I don't know any other working method yet.
Don't forget to make a backup of Snapchat with Titanium Backup just after rerooting, so next time you face that issue you can just restore from TiBu.

Hey I just wrote a guide on this. No need to unroot! https://forum.xda-developers.com/pixel/how-to/guide-log-to-snapchat-stock-rooted-rom-t3590473
I'll copy and paste the steps from my thread to here so people can see it. You have to be on stock firmware for this to work.
1. Download the full system image for your device + build (https://developers.google.com/android/images)
This worked on my Pixel, it should work for other Nexus/Pixel/Pixel XL devices as well though.
2. Unzip the file
3. Unzip the image-sailfish-XXXXXX.zip inside the new folder
4. Connect your device to your computer with ADB and reboot to bootloader
5. fastboot boot path/to/boot.img (inside the folder from step 3.)
NOTE: Please make sure to fastboot BOOT, NOT fastboot FLASH.
6. Once booted, log in to Snapchat. It should work.
7. Reboot.
8. Backup Snapchat in Titanium Backup so you don't have to do this again.