How odd... I attempted to perform a system dump so that I can get to work porting my ROM to this phone. But, when i try, it hits an error saying that "superuser.apk" was not found. All I have on this is SuperSU, not Superuser. Thoughts?
Nevermind. The phone was just misbehaving.
Related
Hello All:
Here is a rundown...
Started with JF1.42-RC33 with Apps, Data, Dalvik to SD...
Went to JF1.5 without a wipe and then updated the radio.
All of this went fine. Now when I start up the phone, it
gives me the "System UIDs Inconsistent" message. I press
the button and then everything loads fine. All 125 Apps
are there, Market works correctly, notes are still there,
and I have tested every App and there are no issues.
Loving the new ROM by the way... no stability issues so
far.
The message on the phone says to wipe the data. If there
is not other way to get rid of the nagging error then so
be it... I still have my Nandroid backup from the JF1.42
image.
Just wanted to see if there was possibly a way to fix this
in ADB or the recovery console...
Also, it is in my nature to try and understand these things.
Could this have happened because my /data directory is
on the SD and therefore was not cleared during the Flash
process? Just guessing...
Any ideas?
L8r,
Vermithrax
Vermithrax said:
Hello All:
Here is a rundown...
Started with JF1.42-RC33 with Apps, Data, Dalvik to SD...
Went to JF1.5 without a wipe and then updated the radio.
All of this went fine. Now when I start up the phone, it
gives me the "System UIDs Inconsistent" message. I press
the button and then everything loads fine. All 125 Apps
are there, Market works correctly, notes are still there,
and I have tested every App and there are no issues.
Loving the new ROM by the way... no stability issues so
far.
The message on the phone says to wipe the data. If there
is not other way to get rid of the nagging error then so
be it... I still have my Nandroid backup from the JF1.42
image.
Just wanted to see if there was possibly a way to fix this
in ADB or the recovery console...
Also, it is in my nature to try and understand these things.
Could this have happened because my /data directory is
on the SD and therefore was not cleared during the Flash
process? Just guessing...
Any ideas?
L8r,
Vermithrax
Click to expand...
Click to collapse
wipe and re-set your symbolic links .. all your apps will be back but not their data..
Thanks... I guess I will just take the easy way out and wipe the phone... I have tried various ADB and busybox commands to no avail... What I do not understand is the phone works perfectly after the Nag screen is gone... No force closes... no missing functionality...
I will not do the wipe until this afternoon... Just in case some Linux guru has any ideas...
L8r,
Vermithrax
Unless the nag screen bothers you, or shows up more than once per boot, Id leave it. If you start seeing instability or forcecloses then Id wipe.
Unless there is a good reason to Id avoid a wipe. Of course I dont have OCD so one nag per reboot wouldnt bother me. If you do or it does bother you then yeah wipe.
Solved... For me at least...
I had solved this problem some time ago, but I just thought I would add this to the thread in case others find their way here through a search...
All I did was move the /data/data back to the internal memory...
rm /data/data
busybox cp -a /system/sd/data /data
rm -r /system/sd/data /data
reboot
Had a couple of stale NFS file errors, so I could not really delete the /data directory from the /system/sd. However, there are threads that help with this issue.
Probably the cleanest solution HERE
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.
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)).
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.
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...