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] Upgrade to 4.3.3 problem with recovery twrp

Hi!
I've a big problem...
My nexus 5 configuration: TWRP recovery - Root privileges - Android 4.2.2
The smartphone notified me the availability of Android 4.3.3. I accepted and the package has been downloaded. The phone has rebooted, but there was no trace of the installation. The phone is divided into TWRP recovery.
I rebooted the system from recovery. The system is still Android 4.2.2 and tells me that the system is updated. In fact he says "last update check xx.xx" (where xx.xx is the hour).
Do you have suggestions on how to proceed?
You're my only hope!!
Thank you,
xSliv3r

you have to manually select the ota file to install with twrp. its in /cache i think, but im not 100% sure of that location

Zepius said:
you have to manually select the ota file to install with twrp. its in /cache i think, but im not 100% sure of that location
Click to expand...
Click to collapse
thanks zeus, I think ... I try immediately! I'll keep you updated!

nope...
In cache there is a file called d173d.....signed . I've try to install it but it's failed...

xSliv3r said:
nope...
In cache there is a file called d173d.....signed . I've try to install it but it's failed...
Click to expand...
Click to collapse
You can get the update zip here and info on how to install it http://forum.xda-developers.com/showthread.php?p=47369234
Sent from my Nexus 5 using XDA Free mobile app

[Q] Cancelling In-Progress OTA Updates?

Hello, all!
I'm wondering, how do you cancel an OTA update once it has started? I mean after it has downloaded, and you have chosen to install it.
Here's my problem: Everyone talks about how running an OTA update unroots your phone. No problem, I can just re-root it. What no one talks about (at least I didn't run across it before doing this) is installing OTA updates when you have TWRP installed...
So, my phone downloaded the update, and it asked me to install it. I accepted, it restarted, and TWRP came up. From there, nothing happened. I tried restarting it, and it booted up just fine. After about a minute of being up, the "Phone is shutting down" (or something along those lines) message pops up, and it reboots again.
I'm wondering, how do I go about cancelling the update? I've read online I need to download the update manually and run it through TWRP, but until I learn how to do that (and spend a few hours downloading it on this freaking slow internet connection), I would like to be able to use my phone.
Another alternative that I don't know whether is possible, can I somehow use TWRP to browse to where the OTA update was downloaded to, and install it through there? If so, what would the procedure be for doing so?
Thanks!
ElectroPulse

ElectroPulse said:
Another alternative that I don't know whether is possible, can I somehow use TWRP to browse to where the OTA update was downloaded to, and install it through there? If so, what would the procedure be for doing so?
Click to expand...
Click to collapse
Boot into TWRP, click install, click(Up A Level) until you are at "/" and look in the cache folder for the update zip.
It should be in there.

meekrawb said:
Boot into TWRP, click install, click(Up A Level) until you are at "/" and look in the cache folder for the update zip.
It should be in there.
Click to expand...
Click to collapse
Thanks for the reply!
Is it the "Blur_Version21.23.4.peregrine_retus.retus.en.US.zip" file? If so, that didn't work... Unfortunately it failed.
Here's what it said just before failing:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/cache/..."
Error flashing zip '/cache/..."
Updating partition details...
Any ideas?
Thanks!
ElectroPulse

ElectroPulse said:
Thanks for the reply!
Is it the "Blur_Version21.23.4.peregrine_retus.retus.en.US.zip" file? If so, that didn't work... Unfortunately it failed.
Here's what it said just before failing:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/cache/..."
Error flashing zip '/cache/..."
Updating partition details...
Any ideas?
Click to expand...
Click to collapse
You must have stickmount installed. Uninstall it and try again.
Note: If you changed or deleted anything in /system partition the install will keep failing. You'd have to fastboot flash the system img's from the 4.4.3 firmware.

meekrawb said:
You must have stickmount installed. Uninstall it and try again.
Note: If you changed or deleted anything in /system partition the install will keep failing. You'd have to fastboot flash the system img's from the 4.4.3 firmware.
Click to expand...
Click to collapse
Thank you for the reply.
Nope, Stickmount is not installed. Not sure what other apps there are that could cause this.
Not sure whether I've changed anything in /system... I don't believe I have, but an app I installed very much could have.
I'll look up this "fastboot flash" you are referring to.
Anyway, for now I am good. I copied the .zip OTA downloaded file to another location, hit the "clear dalvik and cache," rebooted, and I'm back to a working 4.4.3.
Problem solved until I decide to try to get 4.4.4 installed! (which I may never end up doing... Now that Cyanogenmod is officially out for Peregrine, I'm probably going to flash it with that when it gets stable enough (i.e. no RAM issues)).

[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.

Problems when updating a previously rooted Nvidia Shield Tablet [MOVED HERE]

[This was already posted, I just moved it to the Shield Q&A.]
As many of you may know, Nvidia has recalled their Shield Tablets. I'll be getting a replacement soon. I'll be rooting it as soon as possible when I get it, but first I have a few questions.
First of all, I rooted my tablet using a guide at IBTimes (that used info from XDA forums) installing CWM recovery.
After rooting I installed Link2SD, pretty much the reason I rooted, to save up some space on my internal memory. Everything was going fine, until I received the recall notice. I moved all my app files back to the internal memory, deleted Link2SD, ran a full unroot on SuperSU, (after a while of hanging on the "Please Wait" screen the app just crashed, it wouldn't load up and Root Checker said I had no root access after rebooting.
I don't know whether this was supposed to happen or whether it should have gone more smoothly, please give me an answer to this and tell me if it affected my system in any way) and fastboot flashed the stock recovery.img.
However when I tried to install the update, I got a red triangle error. After checking the log I got an error saying "Package expects build fingerprint of ... or ..., this device has ...."
I can't remember what the fingerprints were, but the first one was something that began with "nvidia/", had a bunch of numbers in the middle followed by an underscore, then it ended with "/release-keys".
However the device's current build fingerprint was exactly the same as the first, except that it cut off halfway through, right after the numbers and the underscore.
I tried resetting my cache, I tried a wipe of the user data. The only way to fix this for me was to re-install a bunch of stock images - recovery.img, boot.img, system.img, etc.
I don't want to wipe my data next time. So I ask for this in my answer:
- An explanation of what the error means
- How this error is caused
- A way to fix this error without wiping my device
- How to prevent this error
- If what happened to SuperSU in my case is normal and if it affected my device in some way
- And, if possible, a way to install the update successfully without getting this error and without having to unroot or remove CWM, and details on how to do this method and any risks.
Thanks in advance. An answer soon would be appreciated.

Quick answer:
- You don't need to restore to full stock before updating to the latest OTA. This is what I did, running a rooted stock system with TWRP recovery:
-- Go to Settings > About tablet > System updates and continue to click Check Now until the update has been found. I had to click like 4 or 5 times before it was found. It'll download automatically to your device (not your SD card), but I forget where that download location is... XD
-- once you've found your downloaded OTA.zip, copy it to a location you can easily find from your custom recovery.
-- reboot into custom recovery, flash OTA.zip, reflash superSU.zip, wipe cache NOT DATA, reboot
-- wait until device boots up, wait until the Optimizing blah blah process is done.
-- enjoy!
Additional thoughts:
- I've tried the Link2SD app, but I think it messes with my system in a way I don't like; personally I'd rather delete the apps I never use via custom recovery (see THIS THREAD on how to debloat your tablet for yourself!
- I think your error happened when you flashed stock recovery on top of the custom one. To prevent this next time, simply wait for either a flashable zip in THIS OTHER THREAD, or you can check to see if nVidia released any OTA3.1 recovery images if you want that full-stock experience.
Hope this helps!