Related
I'm sure this question has been answered before, but I can't find it anywhere, so here goes:
I always thought that whenever a ROM is installed it completly wipes and overwrites the /system partition. But perhaps I figure wrong, maybe the files/folders within /system are overwritten and any other pre-existing files are left behind.
Which is it?
I ask this because I notice that the size of /sytem in an update.zip varies from one ROM to another, this suggests to me that perhaps files can be left behind when a ROM is installed. Also I'm curious why it's sometimes possible to upgrade a rom without a wipe and sometimes it isn't.
It depends on how the ROM is set up to install...
Basically, a flashable zip is just a bunch of files and a script that installs the package. If the script also has instructions to erase files or directories, then it will...
Sent from my Nexus One using XDA App
it depends on what you are doing. if i flash a full ROM to my phone, it will just upgrade everything as if it were a real OTA from google, meaning it keeps every thing in tact. if i wipe the phone first, of course it re-writes everything. so it's a tough question to answer.
Thanks danger-rat, perfect explanation.
It's quite interesting that we rely on the ROM-dev to wipe whatever is necessary (as a manual wipe from Recovery-mode does not wipe /system). So I guess it's possible to install a new ROM and be left with bits of the old one still in /system if the ROM-dev didn't specifiy a format of /system.
danger-rat said:
It depends on how the ROM is set up to install...
Basically, a flashable zip is just a bunch of files and a script that installs the package. If the script also has instructions to erase files or directories, then it will...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
deleted .
Finally ! That bug was very annoying to me.
I'll try the fix asap, thanks a lot!
e: works like a charm!
Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something
j4n87 said:
Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .
Click to expand...
Click to collapse
Because you posted it in the "Themes and Apps" section
thanks a lot for post here
great job
kackburt said:
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something
Click to expand...
Click to collapse
you mean copy the actual zip file into the ROM zip and then flash?
jonny68 said:
you mean copy the actual zip file into the ROM zip and then flash?
Click to expand...
Click to collapse
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.
Tried on UD3.3.0 wont boot... :s
People dont understand that this work the best on CM7 nexus roms.
That by installing this fix on CM7 or AOSP you will probaly lose the robo and high volume on first call fix. That most roms have custom libs including this lib. Minimum requirements I would say CM7 2.34 and AOSP 2.34 since cm7 and AOSP are the most equal roms to each other.
To say it simple you cant just simply flash this on every rom also make sure your permission is right.
Is this fix able to work on an HTC Desire running 2.3.4 Oxygen ROM?
jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
If you have a nandroid backup, you should be on the safe side!
Try to wipe cache partition first, then the dalvik cache and then flash the zip-file.
All of these actions take place in the CWM.
Hope it works!
The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4
jens1288 said:
The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4
Click to expand...
Click to collapse
Yes, that fix works fine. I'm not sure it fixes the few seconds delay that affects all Gingerbread phones though but there was another potential workaround submitted for that too.
http://review.cyanogenmod.com/#change,5420
I have yet to include it in my build and try it though.
The story on the front page links to the wrong fix. The libaudio fix was for the wonk on the Nexus One. The libaudio library is hardware specific and may cause issues on other devices that don't share the same processor.
I've submitted a patch to gerrit that helps with the call delay here:
http://review.cyanogenmod.com/#change,5420
Thank you for clearing that up jyxent. To go into a bit more detail...
The fix that was posted, as jyxent mentioned, is for the Nexus One. That is for the infamous "wonk" that has been plaguing N1 users since the Gingerbread nightlies started (who woulda thunk it was just a single line that needed to be added).
The 2-3 second delay is something that affects most (if not all) Gingerbread installs. Currently there isn't a simple "fix" for this. It requires recompiling portions of Gingerbread. jyxent's fix is submitted to CM, but I don't see any reason why this can't be applied to AOSP as well. It has yet to be reviewed by the CM dev team (at least it doesn't have any comments on it yet). It might be something that can be made into some device-independent flashable zip, but it has yet to be created.
j4n87 said:
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.
Click to expand...
Click to collapse
done thanks
Can this be done manually with root explorer, by copying the libaudio.so to/system/lib and a reboot?
Hi all!
Well, thanks to everyone for their donations-- without you, this wouldn't be possible.
I present to you, one stepping stone towards custom ROMs: the shipping ROM on the device, backed up as a NANDROID.
What is this?
This is the shipping ROM on the device. There are no changes to this ROM besides being rooted.
Click to expand...
Click to collapse
How do I use this?
Extract the contents of this file to your SD card (external SD card) under
Code:
/clockworkmod/backups/
and you will end up with a
Code:
/clockworkmod/backups/revo_stock
folder.
Run Clockwork on your device, and select "Backups and Restore" then "Advanced Restore". Select "revo_stock" as the backup to restore, and choose to restore ONLY "system".
(You can also restore boot.img, but it is unnecessary, and I only left that in there for future use.)
Click to expand...
Click to collapse
What does this backup include?
This backup ONLY includes /system and boot.img. There is no recovery.img in this backup, nor is there a /data or /cache.
Click to expand...
Click to collapse
Will I lose my apps or information if I restore this backup?
No you will not, this backup will not touch your /data partition.
Click to expand...
Click to collapse
Why is this useful?
Accidentally erased something important in /system?
Removed something and now 4g Hotspot doesn't work?
Restore this, and it'll fix that... of course all the stock OS will come back, but hey-- you get a second chance
Click to expand...
Click to collapse
Downloads
http://goo-inside.me/private/iomonster/files/revo_stock.zip
Special thanks to Snipa and s0up for hosting this file for me, as I really really really hate upload sites.
Click to expand...
Click to collapse
Contact Me!
Got an issue with this release? Post here!
Want to contact me privately? PM me on XDA or Rootzwiki
Twitter your thing? Follow me, @tylerfixer on Twitter
Join the official LG Revolution dev IRC channel at freenode on #lgrevolution
I'm IOMonster on IRC!
Click to expand...
Click to collapse
thanks icecube, i hit refresh all yesterday waiting for this!!!!!!!!!!!!!!!!
leemsami said:
thanks icecube, i hit refresh all yesterday waiting for this!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
i meant thecube!!
Haha! No worries, it's 3:30AM
do i push this through adb or do i extract it on windows then put it on my sd card.
leemsami said:
do i push this through adb or do i extract it on windows then put it on my sd card.
Click to expand...
Click to collapse
Extract through windows and put on your SD card in the proper folder.
its telling me that i have a md5 mismatch!!! i will try downloading it again.
Thanks cube please keep up the hard work! I wish I could do something to help other then sending some $$$ I would love to help bring the revolution along.
Viva la revolution.
Did anybody use this yet. i tried and it says my md5 does not match. i tried numerous times
Haven't tried it yet but I checked the MD5 against the images and they are correct.
Ah, sorry, forgot to state select "Advanced Restore" or whatever it's called-- JUST restore system.img.
If you select "Restore" it looks for the /data and recovery.img in the nandroid.md5 file, and when it doesn't find it, it errors out with an md5 error.
I'll edit the instructions now...
Just tested this. I can't advanced restore the system.img either. Comes back with MD5 mismatch. I can restore my own backups without a hitch however.
[Edit] I forgot to mention. There's a carriage return on the Rooted Factory-Stock ROM MD5 file. Removing it didn't seem to matter. I was thinking that maybe it was the culprit.
Agh! you just gave me the answer... I saved it in windows, rather than linux, so the line endings are wrong...
If you're able to, just open the file nandroid.md5 in Notepad++ or something like it, and remove the extra blank line, and change the line endings to UNIX style.
Thanks, I'll re-upload the .zip when I'm on a faster connection.
The actual .img files themselves are good, though.
thecubed said:
Agh! you just gave me the answer... I saved it in windows, rather than linux, so the line endings are wrong...
If you're able to, just open the file nandroid.md5 in Notepad++ or something like it, and remove the extra blank line, and change the line endings to UNIX style.
Thanks, I'll re-upload the .zip when I'm on a faster connection.
The actual .img files themselves are good, though.
Click to expand...
Click to collapse
thanks thecube, it worked with the notepade++ steps and unix style.
re-uploaded. Should work just fine now.
Is there a version of this with everything? In other words, not just system but data, etc. I somehow am stuck in CWR...don't have a nandroid backup. I pushed this to the right place on the SD card, did the system restore, but it still repeatedly boots into CWR. Is there anything that will do a FULL restore instead of just system?
Thanks in advance.
MarkyD311 said:
Is there a version of this with everything? In other words, not just system but data, etc. I somehow am stuck in CWR...don't have a nandroid backup. I pushed this to the right place on the SD card, did the system restore, but it still repeatedly boots into CWR. Is there anything that will do a FULL restore instead of just system?
Thanks in advance.
Click to expand...
Click to collapse
Hm, so you did a data wipe from within Android. Yep, that'll get you stuck in CWR, but it's not a problem with the backup, it's that the LG bootloader isn't happy with Clockwork.
When installing Clockwork, did you make the p8 backup?
so im having the same problem i even started a thread too but im an idiot and didnt make that p8 backup because the md5sum didnt match so i stopped there but clockwork still seem to flashed to the phone now im in clockwork everytime i boot up was wondering any way to work around this if not guess imma just get a new phone until there is a way
rodney323 said:
so im having the same problem i even started a thread too but im an idiot and didnt make that p8 backup because the md5sum didnt match so i stopped there but clockwork still seem to flashed to the phone now im in clockwork everytime i boot up was wondering any way to work around this if not guess imma just get a new phone until there is a way
Click to expand...
Click to collapse
There is a way, I just haven't written it into an easy-to-use program yet.
For now, if you haven't made a p8 backup, the easiest method is for you to come on IRC and have me adb into your phone and fix it for you.
If I get a spare moment though, I will work on a stuckinclockwork.zip that you can flash using clockwork to get you out of clockwork.
Stuck in clockwork fix:
http://forum.xda-developers.com/showthread.php?p=15501302#post15501302
FIXED! All credit goes to eww245.
eww245 said:
[edit] This will remove su-backup from a terminal emulator
Code:
su
busybox mount -o remount,rw /system
/data/data/*voodo*/files/chattr -i /system/su-backup
rm /system/su-backup
Click to expand...
Click to collapse
So I tried restoring a nand I made today and got an error while restoring /system. I'm using CWR 5.0.2.6. I'm on leaked 5.7.984 and was trying to restore a nand from the exact same software. Any ideas how to fix this? It flashes a through some .apk's, .odex's, and .ogg's then goes to the below screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
redsox985 said:
So I tried restoring a nand I made today and got an error while restoring /system. I'm using CWR 5.0.2.6. I'm on leaked 5.7.984 and was trying to restore a nand from the exact same software. Any ideas how to fix this?
Click to expand...
Click to collapse
Any other details would be nice to have, safestrap/bootstrap, any files you edited.
If you're using safestrap, and restoring from a non-safe to a safe system, there could be a problem, you would have to get Hashcode for confirmation though..
ChaoticWeaponry said:
Any other details would be nice to have, safestrap/bootstrap, any files you edited.
If you're using safestrap, and restoring from a non-safe to a safe system, there could be a problem, you would have to get Hashcode for confirmation though..
Click to expand...
Click to collapse
Oh, sorry, I thought saying CWR 5.0.2.6 was enough to indicate Koush's modded bootstrapper. But yes, it's bootstrap. I made the nand before i flashed over MavRom to try the tweaked dock addon, it didn't work as I liked, so I tried to restore it, not even 30 mins after making it, and it failed. I talked, on Twitter, to HashCode for a bit and he finally said go talk to Koush, so I plan on doing that later today.
redsox985 said:
Oh, sorry, I thought saying CWR 5.0.2.6 was enough to indicate Koush's modded bootstrapper. But yes, it's bootstrap. I made the nand before i flashed over MavRom to try the tweaked dock addon, it didn't work as I liked, so I tried to restore it, not even 30 mins after making it, and it failed. I talked, on Twitter, to HashCode for a bit and he finally said go talk to Koush, so I plan on doing that later today.
Click to expand...
Click to collapse
There could be a possibility that its just a bad nandroid backup too..
When I did a restore with the same bootstrapped cwm I got the same error, but I just rebooted my phone anyways and everything was restored.
Sent from my DROID3 using XDA App
I am having the exact same issues. Even trying to restore back to stock .890 with root only. Using modded bootstrap which can use bp tool to get into recovery. Emailed clockwork mod twice no answer.
ChaoticWeaponry said:
There could be a possibility that its just a bad nandroid backup too..
Click to expand...
Click to collapse
I've tried with multiple backups, and I've used some before so I know they're good.
gkitab said:
I am having the exact same issues. Even trying to restore back to stock .890 with root only. Using modded bootstrap which can use bp tool to get into recovery. Emailed clockwork mod twice no answer.
Click to expand...
Click to collapse
I got a hold of Koush pretty easily with Twitter. I'm going go make a video of the error here within the next hour or so. Gotta make a nand first, just in case it decides to work this time.
I am experiencing the same error with Droid 3 Bootstrap and 5.7.894.
This happened to me in the past with Safestrap, because I accidentally hit the back button and cancelled the backup during safe system toggle. Had to uninstall/reinstall safestrap.
Sent from my DROID3 using xda premium
Rotkaeqpchen said:
I am experiencing the same error with Droid 3 Bootstrap and 5.7.894.
Click to expand...
Click to collapse
Let me guess...you used Root Keeper as well? Check out this video I made. I made it to show Koush the error I was getting and by going frame by frame I was able to see the last thing trying to restore before it hits the error. "su backup"
http://www.youtube.com/watch?v=cbGUXXN4YiE
Man, thanks, this is the answer... Thanks for finding this out, now we only need a solution for this
Rotkaeqpchen said:
Man, thanks, this is the answer... Thanks for finding this out, now we only need a solution for this
Click to expand...
Click to collapse
I have an idea and I'm doing some testing now. If it works, I'll edit the OP with what I did. As of now, it all makes sense it my head.
EDIT: How can I make a .tar file? I currently am using 7zip and it's hitting an error.
Ok, I may be making progress here. The ArchiDroid seems to be helpful. We'll know in a bit here when it completes.
EDIT 3: Here's where I'm stuck.
1. Download ArchiDroid
2. Extract system.ext3.tar from my most recent backup on my ext SD card.
3. Move "su-backup" from the newly extracted system folder to my ext SD card directory.
4. Use ArchiDroid to recompile the system folder.
5. Rename system.tar to system.ext3.tar
6. Move system.ext3.tar into the host folder of my newest Nandroid backup.
7. Reboot into CWR and restore.
*MD5 Mismatch*
Any ideas?
Trying something else here... Details in 20 or so. If it works, it's practically idiot proof and how it illuded me makes me want to...
EDIT: It's a work in progress... :/
Ok so here's what I did. su-backup is stored in the /system directory. I tried deleting it, then making a nand backup, then restoring it. But as soon as su-backup is deleted (I put a copy on my ext SD), it regenerates itself. I uninstalled Root Keeper, but something remains that causes it to regenerate, thus the restore fails.
EDIT2: Currently Tweeting with the VooDoo Root Keeper dev. trying to find how to delete this da** thing.
Download an app called Titanium Backup, backup all of your apps, and SBF back to stock. That's how I solve my phone problems
Sent from my DROID3 using XDA App
redsox985 said:
I have an idea and I'm doing some testing now. If it works, I'll edit the OP with what I did. As of now, it all makes sense it my head.
EDIT: How can I make a .tar file? I currently am using 7zip and it's hitting an error.
Ok, I may be making progress here. The ArchiDroid seems to be helpful. We'll know in a bit here when it completes.
EDIT 3: Here's where I'm stuck.
1. Download ArchiDroid
2. Extract system.ext3.tar from my most recent backup on my ext SD card.
3. Move "su-backup" from the newly extracted system folder to my ext SD card directory.
4. Use ArchiDroid to recompile the system folder.
5. Rename system.tar to system.ext3.tar
6. Move system.ext3.tar into the host folder of my newest Nandroid backup.
7. Reboot into CWR and restore.
*MD5 Mismatch*
Any ideas?
Click to expand...
Click to collapse
If you change anything in the backup the md5sum changes as well. The md5 cwm is checking against doesn't match. I'd think there's a file somewhere in the nandroid that contains the md5 sum to check for. You could maybe try replacing Yeh old md5 with the new one.
Good luck.
Sent from my ADR6425LVW using XDA App
ChaoticWeaponry said:
Download an app called Titanium Backup, backup all of your apps, and SBF back to stock. That's how I solve my phone problems
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Have it. I don't want to have to SBF from a computer though. Being able to use CWR is ideal.
erismaster said:
If you change anything in the backup the md5sum changes as well. The md5 cwm is checking against doesn't match. I'd think there's a file somewhere in the nandroid that contains the md5 sum to check for. You could maybe try replacing Yeh old md5 with the new one.
Good luck.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
That's a good idea. Back to the lab...
Also, I talked to the dev of VooDoo Root Keeper. He made some pretty good points about possible bugs in CWR that could be making it fail when it shouldn't. From Twitter @supercurio
there's a bug in nandroid if it fails to deals with su protected backup that must be fixed, because it uses standard Extfs features.
Aren't latest recoveries supposed to format partitions instead of trying to remove files recursively? First bug's here.
if you really has to to delete it manually, chattr -i /system/su-backup
yes, as superuser indeed. chattr tool should be part of your busybox, if not, look into my app's /data directory. Then rm su-backup
Click to expand...
Click to collapse
Tried this, but I couldn't get it to work. I'm an ADB noob.
redsox985 said:
I have an idea and I'm doing some testing now. If it works, I'll edit the OP with what I did. As of now, it all makes sense it my head.
EDIT: How can I make a .tar file? I currently am using 7zip and it's hitting an error.
Ok, I may be making progress here. The ArchiDroid seems to be helpful. We'll know in a bit here when it completes.
EDIT 3: Here's where I'm stuck.
1. Download ArchiDroid
2. Extract system.ext3.tar from my most recent backup on my ext SD card.
3. Move "su-backup" from the newly extracted system folder to my ext SD card directory.
4. Use ArchiDroid to recompile the system folder.
5. Rename system.tar to system.ext3.tar
6. Move system.ext3.tar into the host folder of my newest Nandroid backup.
7. Reboot into CWR and restore.
*MD5 Mismatch*
Any ideas?
Click to expand...
Click to collapse
Number 2 won't work properly vfat filesystems cannot retain the permissions and ownership. It should be extracted on a Linux box or if there's room you could extract it to a temp directory on /data which will retain the permissions.
Another option that might work is Total Commander it should be able to delete files from an archive without extracting. It is not in the market, search google for it.
eww245 said:
Number 2 won't work properly vfat filesystems cannot retain the permissions and ownership. It should be extracted on a Linux box or if there's room you could extract it to a temp directory on /data which will retain the permissions.
Another option that might work is Total Commander it should be able to delete files from an archive without extracting. It is not in the market, search google for it.
Click to expand...
Click to collapse
I can't find a non-beta working version of TC, so I'll try the extract to /data later. Also, I can't seem to get the adb method given to me by @supercurio to work.
redsox985 said:
I can't find a non-beta working version of TC, so I'll try the extract to /data later. Also, I can't seem to get the adb method given to me by @supercurio to work.
Click to expand...
Click to collapse
Whats wrong with the beta? Works for me
You referring to chattr? Try # busybox chattr
Maybe you don't have the symlinks
eww245 said:
Whats wrong with the beta? Works for me
You referring to chattr? Try # busybox chattr
Maybe you don't have the symlinks
Click to expand...
Click to collapse
When I try to start the beta, it says it's a beta and I have to click a text box closing it. Send me your apk? And could you type up the exact script for what to enter into adb to push busybox with chattr and then the command to erase the file? Thanks. I only started using adb last night! :O!
Finally got my Sprint CDMA Gtab with broken internal Sd working on CM10.1. However I can't get the gapps package install and I don't have a working clkworkmod recovery ... It always gets clobbered.
Is there an easy way to install gapps from within Android?
Cm10.1 kernel definitely contains a cwm recovery.
How is yours without one?
Gapps is a pack of apk and files.
Read the updater-script in its META-INF folder and you can do exactly like what the script does, manually.
Sent from my GT-P1000 using xda app-developers app
priyana said:
Cm10.1 kernel definitely contains a cwm recovery.
How is yours without one?
Gapps is a pack of apk and files.
Read the updater-script in its META-INF folder and you can do exactly like what the script does,
Click to expand...
Click to collapse
This is one of those CDMA Gtabs with the busted internal SD so all the partition assignments are screwy. The ROM I've had most luck with is the CM10.1 with the Humberos? Kernel... Don't know if it contains CWM. Every time I flash in the ROM it wipes CWM but if I reinstall CWM then the ROM doesn't boot so right now they are mutual exclusive.
Trying to install a gapp apk file with FileManager doesn't work... It gets going but then says install failed... I presume the partitioning is screwing it up.... Gave it perms and made /system rw, still no go.
Anyways I just reinstalled the whole thing, oddly I have to flash another CM10 ROM first with CWM (which doesn't boot) then follow it with the 10.1 ROM but this time I also did the gapps. Now everything is 'fine' although I still don't have CWM...
UPDATE: I see that others are finding their recovery clobbered with this Rom...
http://forum.xda-developers.com/showthread.php?t=2043421