I'm sorry to say I have no idea but I'm now determined to learn how and I think I'll start with a linux partition.
Anyone care to join me?
I think the Avabox that avaluanchemods posted up included the files to pull out the files from the .img, after that wouldn't it be just like modifying another ROM (with a lot more to mod, of course, to gain root, etc.)?
danaff37 said:
I think the Avabox that avaluanchemods posted up included the files to pull out the files from the .img, after that wouldn't it be just like modifying another ROM (with a lot more to mod, of course, to gain root, etc.)?
Click to expand...
Click to collapse
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
regaw_leinad said:
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
Click to expand...
Click to collapse
Hahaha yeah, getting the images from the ruu is a blast!
u guys want the new sprint ruu turned into a flashable update.zip? isn't that what damages 2.06 basically is? if not i'll do it for you.
I think it's really more that they wanna learn how. Anyone down to throw out some pointers?? I'd be interested to learn too
I was actually just looking into pulling the files from the ruu myself.
extract the exe file. unyaffs the system.img. make an update-script in META-INF/com/google/android/. zip the boot.img META-INF/ folder, and system/ folder and sign it. nothing more to it. lol
zenulator said:
u guys want the new sprint ruu turned into a flashable update.zip? isn't that what damages 2.06 basically is? if not i'll do it for you.
Click to expand...
Click to collapse
well, well howdy stranger! zen you were a great dev on the vogue/android...we need you here my man!
fixxxer2008 said:
well, well howdy stranger! zen you were a great dev on the vogue/android...we need you here my man!
Click to expand...
Click to collapse
this communtiy is a little crazy for my taste. but darchstar answered the question.
http://code.google.com/p/zen-droid/downloads/list
this is a link to the files i use. you must have linux installed to use them as well as pearl which should be installed on most distros. you'll prob have to chmod them executable if you download them.
any questions post them and i'll try to help. i'm glad to see people trying to learn.
regaw_leinad said:
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
Click to expand...
Click to collapse
thats all you need for a rom. is the /system. just place that in a folder along with the boot.img. andddd archive and sign. you have a rom now.
and if you want to know a secret. lol
if you are in windows, all .exe's are archived as zips. change .exe to .rar/zip and then you can unzip and have everything. very simple.
o and you need an update script which you can create, or take someones from a rom and edit it to fit the RUU. and as always give credit where needed
Avalaunchmods said:
thats all you need for a rom. is the /system. just place that in a folder along with the boot.img. andddd archive and sign. you have a rom now.
and if you want to know a secret. lol
if you are in windows, all .exe's are archived as zips. change .exe to .rar/zip and then you can unzip and have everything. very simple.
o and you need an update script which you can create, or take someones from a rom and edit it to fit the RUU. and as always give credit where needed
Click to expand...
Click to collapse
interesting. so in theory this could be done as easily on windows, no linux partitions?
mountaindont said:
interesting. so in theory this could be done as easily on windows, no linux partitions?
Click to expand...
Click to collapse
i hate linux. lol so yes
Not all exe's work like that. Like this one for example....
not even 7zip can get into it.
danaff37 said:
Not all exe's work like that. Like this one for example....
not even 7zip can get into it.
Click to expand...
Click to collapse
uniextract, google it. you are correct some are a certain type that cant be extracted but 99% of RUU's can.
Ok here is a basic run through for extracting the RUU and making an update.zip
1. Run the RUU in windows or through wine. You don't have to run it completely with your phone plugged in. The install shield will extract the files to a tmp folder. Search through your tmp folders until you find it. Inside should be a rom.zip. Unzip it. Inside it should be system.img data.img boot.img etc...
2.
a: Switch to linux. Use unyaffs to extract the system.img. I usually make a directory called system in the same directory as the system image and cd to it. then issue.
unyaffs ../system.img
this will extract it into the system directory that your in. make your changes. add apps/busybox/su etc..
b: You can also use unyaffs for windows from here: http://code.google.com/p/unyaffs/downloads/list it should do the same thing but I've never used it.
3. If you want apps pre-installed to /data then make a data directory with a apps directory in it and put your extra apps there like wireless tether etc... so now you have a directory with
/system
/data
boot.img
4. Use an update script from another rom as a base and modify it to symlink busybox, set the correct permissions, copy data write boot.img, clear cache etc... read through some other update scripts to get the idea of whats going on it's simple text based stuff. The update script is inside the directory
META-INF/com/google/android.
Once done move the META-INF directory to your working directory. so you should now have
/system
/data
/META-INF
boot.img
Zip up the above directorys/files into something like myrom.zip
5. Sign the zip. You'll need java and a testsign.jar and the android sdk. I've never done it without the sdk. Create a directory called sign inside the tools directory of the android sdk. Move testsign.jar and your myrom.zip to the sign directory. Execute the following command while in the sign directory
java -classpath testsign.jar testsign myrom.zip myrom-signed.zip
6. Copy myrom-signed.zip to the root of your sdcard. reboot recovery. nandroid backup. wipe/factory reset. flash update zip.
Good luck.
zenulator said:
Ok here goes a basic run through for extracting the ruu and making an update.zip
1. Run the ruu in windows or through wine. It will be extracted to a tmp folder. Search through the tmp folders until you find it. Inside should be a rom.zip. Unzip it. Inside it should be system.img data.img boot.img etc...
2. Switch to linux. Use unyaffs to extract the system.img. I usually make a directory called system in the same directory as the system image and cd to it. then issue.
unyaffs ../system.img
this will extract it into the system directory that your in. make your changes. add apps/busybox/su etc..
3. if you want apps pre-installed to /data then make a data directory with a apps directory in it and put your extra apps there like wireless tether etc... so now you have a directory with
/system
/data
boot.img
4. use a update script from another rom as a base and modify it to symlink busybox, set the correct permissions, copy data write boot.img, clear cache etc... read through some other update scripts to get the idea of whats going on it's simple text based stuff. the update script is inside the directory META-INF/com/google/android. once done move it to your working directory. so you should now have
/system
/data
/META-INF
boot.img
Zip up the above directorys/files into something like myrom.zip
5 sign the zip. you need java and a testsign.jar and the android sdk. i've never done it without the sdk. create a directory called sign inside the tools directory of the android sdk. move testsign.jar and your myrom.zip to the sign directory. execute the following command while in the sign directory
java -classpath testsign.jar testsign myrom.zip myrom-signed.zip
6. copy myrom-signed.zip to the root of your sdcard. reboot recovery. nandroid backup. wipe/factory reset. flash update zip.
Good luck.
Click to expand...
Click to collapse
uhh...i think ill leave that one too the pros
zenulator said:
Ok here goes a basic run through for extracting the ruu and making an update.zip
Click to expand...
Click to collapse
Interesting. Sounds easy enough, I'll definitely have a go. Thanks for the tutorial.
pseudoremora said:
Interesting. Sounds easy enough, I'll definitely have a go. Thanks for the tutorial.
Click to expand...
Click to collapse
+5, HOLY CRAP guys, I havent checked the forum in a few hours.
Thank you all so much for the insight.
I'll be back in a week!!
nebenezer said:
+5, HOLY CRAP guys, I havent checked the forum in a few hours.
Thank you all so much for the insight.
I'll be back in a week!!
Click to expand...
Click to collapse
There's an easy fix for your problem... Install the XDA Android App. Seriously, my soul belongs to Android now... and XDA has become my home, I HAVE to know what's going on at all times... it's like a drug, lol.
Well I browsed through all the forums and I could not find anything that I am going to explain. There are some tits-bits here and there, but I hope this proves to be useful.
I will also explain if you have a xrecovery backup, then how to extract your games and progress from there.
Many of you might be switching ROMs very frequently or upgrading/downgrading their Android. While doing this, we lose all our apps and games and more importanly the game's PROGRESS, if we do not save them.
There are apps available to save apps/games and progress but there is a way to do all these thing MANUALLY. This for those who want the control in their hands , like me.
PART A:
Here's how you do:
1) Create a backup folder on the sdcard with a name that you like. eg. mybackup
1) from your filemanager or from the shell, browse to the directory /data/app and do ls -l. You will get a list of apps which you have installed.
2) Select the app that you want to save/backup and move it to sdcard folder that you have created. The names here would be long but it will be almost similar to the name you see in the UI.
For eg.
Code:
cp uk.co.aifactory.moveitfree.apk /sdcard/mybackup
. would be the command to backup Move It game.
3) Now go to the the directory /data/data and do a ls -l. browse through the list and find a directory which matches the name of the apk without the .apk extension.
for Eg. for the 'move it' game, you will find a directory uk.co.aifactory.moveitfree
Move this directory to the backup folder
Code:
cp -r uk.co.aifactory.moveitfree /sdcard/mybackup
.
For those working on shell, remember to do cp "-r" as you are copying a directory.
You are done!!. You have backed up your app and all the progress related to that app.
Now you can copy mybackup folder to your PC or keep it in the sdcard if you have enough space. Its your choice...
PART B:
How to get the progress and games back after flashing the ROM or after wipeout.
Its easy. Just reverse the steps mentioned above.
1) copy the .apk file from your backup folder to /data/app through filemanager or shell.
Eg.
Code:
cp /sdcard/mybackup/uk.co.aifactory.moveitfree.apk /data/app
2) copy the data directory to the location /data/data.
Eg.
Code:
cp -r /sdcard/mybackup/uk.co.aifactory.moveitfree /data/data
You are back to business, just browse through your apps and enjoy the games from where you left.
UPDATE :
For Angry Birds, when you are done with the above steps, delete the file
/data/data/com.rovio.angrybirdsrio/files/settings.lua
It app will not open up if you dont do it.
-----------------------------------------------------------------------------------------------------------------
Those who have already backedup their ROMs and not saved their apps as mentioned above, dont worry, I have a solution for that too. I am specifically going to explain the method to get it from xrecovery backup.
When you backup your ROM or system using xRecovery, it stores all the data inside /sdcard/xrecovery/backup/<date>.
Inside that folder, there are 3 img files.
cache.img
system.img
data.img
data.img contains all the data/app/games that you had installed, while system.img contains everything that came bundled with ROM. It might differ a bit per devices, but mostly its data.img
I tried to open this file ".img" with a lot of extraction tools but none could help. Atlast, i got help from our great <zdzihu>, and he said, he saves the archive with yaffs2 compression.
There is an app "unyaffs2" which you can use to extract the contents of the archive. Get it from here http://forum.xda-developers.com/showthread.php?t=910255
This app will extract the contents to the folder where you ask it to. Once you have your data, repeat the above mentioned steps to get your apps and games running!!
Thank you for the how to
it not change owner
this is very big problem
Hi dateno1, can you be more specific?
What app are you trying on
What method u used to copy
What error r u getting exactly
Which device and on which step
Sent from my X10mini using XDA App
ronaksv said:
PART B:
How to get the progress and games back after flashing the ROM or after wipeout.
Its easy. Just reverse the steps mentioned above.
1) copy the .apk file from your backup folder to /data/app through filemanager or shell.
2) copy the data directory to the location /data/data.
You are back to business, just browse through your apps and enjoy the games from where you left.
Click to expand...
Click to collapse
i have question on the process of getting it back.
on step 1 you said copy.
is it also ok if you are going to reinstall it then proceed to step 2.
thanks.
hey guys i just wanted to ask something. Its possible to install apps via update.zip immediately after flashing ROM rite? I searched XDA and found this: http://forum.xda-developers.com/showthread.php?t=917922
but im not sure how to do it and anyway the meaupload link for that download is down. Btw since all my app data together is more than the data partition of the phone (>200mb), is it possible to make the apps link to my second partition of sd card via update.zip script or something? Hope u guys can help me!!
Does anyone know how to do this? if possible i think it would save a lot of time as when reinstalling via titanium backup. this way would be more hassle-free if possible.
So no one knows how to do this? ok then nvr mind i guess it must be too hard or something....
Why not just use an ext partition and app2ext?
Creating an update.zip is possible, but it's not very convenient. Esp keeping it up-to-date.
Mioze7Ae said:
Why not just use an ext partition and app2ext?
Creating an update.zip is possible, but it's not very convenient. Esp keeping it up-to-date.
Click to expand...
Click to collapse
srry if im asking a really dumb qn but does that mean that if u install apps to ur ext2 via link2sd, u dont have to install them again on new ROM?
App2ext is different from link2sd (but they both use ext partition.
In link2sd you usually create /sd-ext/link2sd folder, reboot and then use the Link2SD app to manually move apps to /sd-ext/link2sd. This is good if you want to mix apps on SD and internal.
In app2ext (which I'm suggesting) you instead create /sd-ext/app folder on sdcard and reboot. All your installed apps will be moved there from internal memory and new apps will be installed there automatically. They will still be there after you factory reset or install a new ROM. (To preserve application data you need something else such as titanium backup)
Ohhhhh. Thx a lot!! Ok I just wanna try a bit of programming that's why I asked how to make update.zip. haha. Anyway Thx!!
Sent from my XT720 using XDA App
androidlover123 said:
Ohhhhh. Thx a lot!! Ok I just wanna try a bit of programming that's why I asked how to make update.zip. haha. Anyway Thx!!
Click to expand...
Click to collapse
You can learn by studying the gapps package used by CM or any other update.zip. The "magic" is inside the META-INF folder. META-INF/com/google/android/updater-script has the installer commands that do things like mount /system and extract files, set permissions etc. The final step is to sign the update. OpenRecovery allows unsigned updates, but you should sign anyway even using testkeys--it forces a sha1 verification of the zip files to detect corruption before the update is applied.
Mioze7Ae said:
You can learn by studying the gapps package used by CM or any other update.zip. The "magic" is inside the META-INF folder. META-INF/com/google/android/updater-script has the installer commands that do things like mount /system and extract files, set permissions etc. The final step is to sign the update. OpenRecovery allows unsigned updates, but you should sign anyway even using testkeys--it forces a sha1 verification of the zip files to detect corruption before the update is applied.
Click to expand...
Click to collapse
oooh i can kinda understand the code in the updater-script. for eg: ui_print to print to screen, package_extract_dir to extract files to the directory in whatever folder u state. but what is the update-binary file?
The update-binary is the program that reads and executes updater-script.
Mioze7Ae said:
The update-binary is the program that reads and executes updater-script.
Click to expand...
Click to collapse
Is that something you must write yourself or something? Or just copy from other update.zips?
I just copy it. It's probably in the AOSP source somewhere but I've never looked.
I created a flashab;e zip or flashing TB after a fresh install.
There are two options to create ZIP to install TB as user or system app.
I see that there is an additional file in the flashable zip when i select to install it as a system app.
/system/lib/libtitanium.so
My question is
What is the diffeence between installing tB as user/system and whats the use of the additional .so file.
.so library is a native compiled (binary) library. What is it used for? I don't know, some faster functions of Titanium. Why is it in one ZIP and not it another? Because user .apk has its libs included and they're unpacked by system automatically into its own /data/data/<appname>/lib directory, while system app is expected to have its libs with the rest of system libs, and it doesn't unpack anything.
When the app is installed in /system, it doesn't take place in /data, and (AFAIK) it automatically inherits system permissions. That's about the only difference I'm aware of.
Jack_R1 said:
.so library is a native compiled (binary) library. What is it used for? I don't know, some faster functions of Titanium. Why is it in one ZIP and not it another? Because user .apk has its libs included and they're unpacked by system automatically into its own /data/data/<appname>/lib directory, while system app is expected to have its libs with the rest of system libs, and it doesn't unpack anything.
When the app is installed in /system, it doesn't take place in /data, and (AFAIK) it automatically inherits system permissions. That's about the only difference I'm aware of.
Click to expand...
Click to collapse
Bang on, thanks
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
A reference to ware the file system in oxygen lays for apps.
User app= /data/app (the folders for each user app are not labeled after what they are.)
System apps (in OxygenOS))=/system/product/priv-app or /system/product/app
It depends which type of system app you intend to make to app. Either directory works.
So I like viper4android and will use it as an example.
1 download this version ViPER4Android-FX_2_7_1_0.apk
2: install it as a user app. It should work now but need the rootless driver install in twrp for it 1st.
3: boot 2 twrp, mount all partitions (works better). Flash the zip, reboot to system.
4: verify the app functions add the Ulta low buffer module or what ever else need to be hooked to the app were Systemizing.
5: everything set use a app like Sdmaid to get the actual directory name that oxygenOS installed it to. Just the 1st two letters works for this to ID it in twrp (ware we won't be able to check.
6: boot to twrp. Mount all partitions. open a file manager it has. Go-to the app's directory under /data/app/... That apps directory. Open that directory and move the next directory to...
/System/product/priv-app or /app.
7: you don't have to but you can now use the file manager in twrp to verify that the app folder moved there and rename it to a better ID if you want. Also you better compare the app's permissions to another system app in that directory and match it up.
Reboot and if the directions were followed, you have systemized an app.
This works better than a systemized app, or a magisk/twrp module. Why cause twrp work is the hands-on management.
The droidware I recommend is.
Sdmaid (lookup apps given directory name.)
Orangefox (dual boot) cause I use it.
A file manager to check you work helps. Need root authority. I recommend the one I'll linkup.
In other roms and OSs the system directory for system app placement is just /system/app or prive-app.
Don't forget to mount the partitions before any working in twrp. I realized that about flashing and twrps modules running while I'm editing my system.
Sorry not adding links or apps good luck with it.
One other thing the boot animation.zip file for changing in located /system/product/media on Oxygen 11.
Ohh yeah theirs a app on play store called partitions manage. You can save any partition live while running you OS to a .omg file. If I do that after Systemizing some apps. It makese a system.img with them included. No more work to redo.
Well gonna go get beer or white pirate stuff. Lol
Mod edit: removed references to warez app.