Hi,
when i download some roms, release after release, i saw that, sometimes, only some files are changed.
if i make a little zip with only the differencies comparing two zip, and if i change updater-script
(deleting "delete system" process , deleting flashing kernel lines, generaly, at end of script and managing other things)
can someone confirm that if my updater-script never delete /system/ , i have no risk to "kill" my device ?
i have an idea about the reply but its good to have a thread about this question, no ?
i have test this following when i run a 2nd rom with dorimanx kernel.
- I search about differencies on two spirit releases rom. (using 7zip , good interface to compare and you have the total size of each folder in zip)
- On a structured folder, i keep only the new files from new release.
(apk, binary,priv-app,framework..., comparing them using size files essentialy because using the date as comparison filter never help in this way)
- i run my 2nd rom
1 - Remember us, with dorimanx kernel, when we are dualbooting roms, no matter the position rom you are run at a moment (1rst or 2nd), you will be able to see /system/ and /data/ partitions from the other rom which generaly sleep
2 - On PC, i generaly use WINSCP soft to acces easily on all structured folders of my device. (just let you know)
So,
- i launch WINSCP on PC, then i can log-in as root on my device, 2nd rom runing.
- in the interface gui of WINSCP, on left side, i see my extracted differencies structured with all files and in right side, i can see all folders from my device.
- with the interface gui from WINSCP, i can copy all that i need in /system_pri_rom/ and /data_pri_rom/ , which are the auto-mounted partitons from 1rst rom
- if DEV have moving some apks from /system/app/ to /system/priv-app/ , i move the files too. If DEV have delete some files, i delete too.
- when i reboot my 1rst rom, it booted without any trouble.
result :
the +
i dont flash anything
i dont change kernel
the -
looking for differencies between 2 zip take time
the +/-
i dont format/delete entire system and maybe with time, this can be corrupted.
If someone can help me this way by making a little script which can make the differencies with an output zip , it will be much appreciated
thanks.
Related
HULU FLASH 10.3 PERMANENT FIX
First off thanks to redvexx over at the Epic XDA 4G Forum http://forum.xda-developers.com/showthread.php?t=1153196 from whose flashable zip file I extracted the files and from his explanation of what his zip update does figured out how we can accomplish the fix manually. He also gives credit to imneveralOne for the foundation of his own work. Many thanks to them both!!
The fix redvexx has posted at the above link is meant to be flashed, which I tried doing using our System Recovery and Android recovery without success. After much trial and error this is what I did on my phone to get Hulu to work using Dolphin HD or Boat Mini browser; I am not responsible for what happens on your phone. And in all fairness and full disclosure I AM A SERIOUS NOOB here and this is my 1st “I did this so can you post”… if anyone can create a “cleaner” way to do this for god’s sake go for it…lol
You must have BusyBox installed (I recommend ver 1.18.2 or lower because at some point you’re gonna try one of zeppelinrox’s great scripts and that’s what he recommends and what I’ve got installed and it works)
** When renaming or creating files and folders leave off the “_” marks**
- Install Adobe Flash 10.3 from the market and make sure auto update is DISABLED
- In your Browser (I think Dolphin HD works best) you must change the UA setting to Desktop and I recommend setting “enable plug-ins” to “always on” but not sure if that is strictly required
- Create the folder “flash” in /data (as in /data/flash)
- Download the attached “DX2_GB_Hulu_Flash10.3_fix.zip” file to your phone and extract the 5 files it contains
- Copy or Move “s98fixflash.sh.txt” to /mnt/sdcard, then rename “s98fixflash.sh” (remove the .txt)
- Copy or Move “libflashplayer.so” “libstagefright_froyo.so” “libstagefright_honeycomb.so” and “libysshared.so” to the /data/flash folder you should have already created
- Using Script Manager open “s98fixflash.sh”, check “Run as Root” and “Run at Boot” then click save.
- Reboot and and you should be able to enjoy Hulu in your browser without having to pay for a VIP subscription (you will not be able to watch VIP content only the free content). Most people seem to have smoother video using a setting of 288 in Hulu; mine seems to work fine set at 360.
What does the fix do? Well, from what I understand and have read Flash 10.3 recopies the files located in /data/data/com.adobe.flashplayer/lib during each boot-up; wiping out any fix that may have been in place. The “s98fixflash.sh” script copies the “fixed” files saved in the flash folder back to the /data/data/com.adobe.flashplayer/lib (after Flash 10.3 does it's copy during boot-up) during each boot-up thus putting the fix back on every boot-up. (or I could be totally wrong and just got lucky; see NOOB admission above...)
Of course to undo this (say if it gets in the way of any future GB update) all you need do is delete or change the name of “s98fixflash”; script doesn’t run, files aren’t replaced, it’s like it never happened because, well, it didn’t…lol
In closing i hope I've done well with my 1st post and some of you folks find it useful. But if I've made a mess of it my apologies in advance.
This is a request to all ROM developers to add their ROMS to ROM Manager.
This will make installing ROMS very easy and efficient for users without even touching the computers.
GUIDELINES:
FOR USERS:
1)You need to download and install the latest recovery from this page:
http://forum.xda-developers.com/showthread.php?t=1243133
2)Download ROM Manager from the market.
3)Open ROM Manager >Options>Manual Flash Override>Spice Mi700,Commitiva N700 and more>Clockwork Mod 3.x.
4)To download ROMS go to the download ROMs page.
FOR DEVELOPERS:
Go to the Developer Portal on:http://www.clockworkmod.com/
P.S.-I have already added a ROM on ROM Manager.
Feel free to download and try it.
GH - Keep up the excellent work & thanks.
My Vpad7 (ITE - Hwv 1.7) has been on CWM 3.0.2.8 and I upgraded to 5.0.2.6 - easy & simple with posted instructions in linked site - was running TJ_Style's ROM patched with non-OC kernel before but running EU.V1.7b ITE now.
Once I rebooted Recovery and navigated to Advanced/Debug Menu to Check Log, etc. - there's no "Go Back" option or menu item available, pressing the device's "Back" button does not work (tried other variations too.) Reset via the pin hole and reboot again into Recovery, check the newly reformatted card with partition/ext, and no "Go Back" option or menu item to Cancel/Undo or Escape.
Perhaps I missed the changes and I re-read the latest info posted ....
Otherwise, this is really & truely great - please kindly check and advise, much appreciated.
P.S. Looking forward to get it partner with ROM Manager and to reflash the EU V1.7b ITE ROM, etc. to the device as I've issues with the (DT's A2SD) scripts associated with the SD-Ext3 configuration.
The reason the back button is not working is because i build this ROM usings TJstyle's kernel which is not compatible with your device input hardware
The kernel was built using the source provided by FIH.
This source does not have the touchsreen input driver for the latest Viewpad7.
Only solution to this problem and all other ITE hardware related problems is to contact Viewsonic and ask them to provide the updated kernel source or borrow the driver from a similar Viewsonic device such a Viewpad10.
If you have a root file manager
open the file :sys/devices/virtual/input/input1/name
and post me the contents
googlehome said:
The reason the back button is not working is because i build this ROM usings TJstyle's kernel which is not compatible with your device input hardware
The kernel was built using the source provided by FIH.
This source does not have the touchsreen input driver for the latest Viewpad7.
Only solution to this problem and all other ITE hardware related problems is to contact Viewsonic and ask them to provide the updated kernel source or borrow the driver from a similar Viewsonic device such a Viewpad10.
Click to expand...
Click to collapse
Thanks, understood & it make sense to me. I will contact VS's tech. support with a request & see what they can provide or offer, etc. and post back results. Also, will search around for drivers from VPad10 ....
P.S. Even without the working "Back" button in Recovery, I managed to use it to format the mSD card, wipe & install new ROM, etc. - it's a bit tricky but manageable. And, the EU v1.7b ROM with ITE hardware support loaded ext3 nicely .... Kudo's
googlehome said:
If you have a root file manager
open the file :sys/devices/virtual/input/input1/name
and post me the contents
Click to expand...
Click to collapse
Used Astro File Manager to take a screenshot (attached) and to try to open the "name" file - it appeared to be a blank one, file size 0 or zero. Used ES File Explorer and getting the same ?? Is there anything specific to look for, or should I just try to extract/copy the file and upload it, kindly let me know. Thanks.
Letitride said:
Used Astro File Manager to take a screenshot (attached) and to try to open the "name" file - it appeared to be a blank one, file size 0 or zero. Used ES File Explorer and getting the same ?? Is there anything specific to look for, or should I just try to extract/copy the file and upload it, kindly let me know. Thanks.
Click to expand...
Click to collapse
Uploading the file would be great.
googlehome said:
Uploading the file would be great.
Click to expand...
Click to collapse
Here's the file saved in zip format. If this isn't it and/or you need another file or folder, just let me know or PM. Thanks.
in sys/devices/virtual/input/
how many folders do you have?
can you upload the name file of each folder?
googlehome said:
in sys/devices/virtual/input/
how many folders do you have?
can you upload the name file of each folder?
Click to expand...
Click to collapse
Checking under ....
there are 3 folders - input0, input1, input2
there is a "name" file in each of them, extracted each "name" file & zipping them together for upload.
Big thanks for looking into this for a possible resolution.
** Attached zip file has 3 name file:
name.input00 (renamed from name - for the input0 folder)
name.input01 (renamed from name - for the input1 folder)
name.input02 (renamed from name - for the input2 folder)
Changing them back to just name & putting them where they belong should do it. Please let me know if this isn't working and/or you need something else. Thanks.
I did some searching online and checked the kernel config of both the ITE and non ITE and came to the conclusion that:
The ITE and the non ITE devices differ by only one aspect i.e. touchscreen.
all other aspects are the perfectly the same.
The driver source file for the ite touchscreen hardware which should have a name similar to ite_i2c.c
is not being used by any other device.(Yet to confirm)
The only solution is to ask viewsonic to release the driver source file which they should under the GNU General Public License
googlehome said:
.... solution is to ask viewsonic to release the driver source file which they should under the GNU General Public License
Click to expand...
Click to collapse
Thanks for looking into the ITE driver issues, I will do a live chat with support on Monday - requesting the source file, and let's see what happen next. There's an Escalation Survey that I can fill out in email format for their reference & resolution/followup - will provide them with my Vpad7's serial number. Their download library & database on device drivers, ec. aren't the best - and is actually blank, zero for the Vpad7 here in the U.S. market. Well, one can ask & wish for it.
I reformatted my 16G mSD card & put it back in the pad, formatted it & set up a 1MB partition with zero swap file size, checked it to confirm that ext3 is present - before rebooting it again, then enable USB support, transferred zip files back and proceeded to flash the custom ROM file. I only use the pin method to reset or exit the sub/menu with the "Go Back" button not available, so it's fine. DT's A2SD installed & so forth, but the scripts not loading/running so did the A2SD check, A2SD reinstall and, A2SD cachepart - ran these from terminal, su enabled & all is good. Free of both internal space and memoryfor the pad to run. Most users (since many seemed to be using non-ITE hardware) will not run into problems but a few of us will, hopefully these info will be useful to the newbies ....
Ext4 partition is not supported in the ite kernel and im guessing even ext3 is not.
Try formatting the sd-ext partiton to ext2.
ITE Screendriver
Hello!
I have used es file manager to view the content of sys/devices and in folder
virtual/input1 the "name" file shows "ITE TOUCHSCREEN".
Now i think it would be helpful to zip the whole folder devices because there must be the screendriver in it ?!
About:
This tool is meant to easily compare the contents of two rom archives and allow easy manipulation by copying files from one rom to another and removing files from a rom archive. The idea is to specify two rom archives which have the same structure, usually something like the following:
[data]
[META-INF]
[sdcard]
[system]
flash_image
modem.bin
zImage
I made it because I would like to know which files/apks might have been removed from one rom compared to another, which isn't always clear from the descriptions. But then thought other people might find it usefull as well, so here it is
It's written in java, just extract the zip and run through run.bat (windows only) or the .jar file.
Update, version 2 added
Ok, I tested it today and seems to work fine... Was able to reflash a rom modded with this tool (file from another rom added, other files removed).
For now it just allows transferring of files between roms and removal of files from a rom archive.
How it works:
1. Load the rom-archives (zip only) using the browse buttons. If one file is selected all contents are simply listed, in case 2 files are supported only the extra files per rom are listed.
You can filter on .apk/.odex files only by using the checkbox and pressing 'Scan'.
2. By using the 'Copy >>' and '<< Copy' buttons you can copy files between roms, these entries will be colored GREEN in the respective table views.
3. By using the 'Remove files' buttons you can remove files from the roms, these entries will be colored RED in the respective table views.
4. Save the rom by pressing the proper 'Save Changes' button and specifying the name of the .zip it has to be saved to.
A progressbar will show the progress and you'll get a message telling you when it's done. It's not the fastest but it does the job. The resulting zip can then be flashed through clockworkmod (at least the one I tested it with could ).
THere are prolly some bugs when you move files back and forth and delete files in between and adding them again, etc... I just tested it with moving a few files from one rom to another and deleting a few form the target rom. This worked fine, but please let me know about bugs and issues.
Update, version 2.1 added
Allrighty, I included the data from the spreadsheet found here:
http://forum.xda-developers.com/showthread.php?t=1069924
To display information about the selected apk's in the table. This gives you a quick overview about what an apk does and whether or not you can and want to remove it. It's displayed in a little text area below the table.
I also changed it so that by default one 'view' is shown, once a first archive is selected the option to select a second one is enabled by displaying the proper buttons. Only after a second file is specified the complete view is shown (two tables, etc).
That's it again for now
Use it at your onwn risk!
Thanks this is very helpful tool.
Would love to see this further developed...two thumbs up!
Sent from my GT-I9100 using Tapatalk
Subscrived to this topic in a hope to see development on it
Sent from my GT-I9100 using xda premium
Woooww, this tool is awesome, how about adding feature like u can copy one or more file from one archive to another one so we can not only remove but also add
I hope u will improve this app further in the future!
Sent from my GT-I9100 using Tapatalk
Thanks for the comments people, good idea about moving apk's to one and another as well indeed To be continued (and always open for suggestions!)
Also updated main post, but...
I rewrote it to allow removal of files and copying of files between two rom packages, I haven't been able to test it myself yet (finished it just now and really need to catch some sleep) but will try to do so tomorrow... However, if anyone else wants to give it a shot as well please let me know and I'll send it (tomorrow evening or monday prolly). I will not put it up before it has been tested and it is about 2:30am here so time to go to sleep. If I get a chance to test and upload tomorrow I'll do so...
Will try to check this topic tomorrow again but can't promise... Busy day.
Clever tool. Will definitely watch this develop
Gr8 work pal. Please continue your development. Is really a handy tool.
Updated 1st post with new version and some instuctions/clarifications
wow. missing that tool.
And another update, added ifnormation display about the apk's using the spreadsheet from this source:
http://forum.xda-developers.com/showthread.php?t=1069924
and changed the UI a bit to make it a bit simpler...
ps. Thinking about adding a feature where you can add seperate apk's/files... Would have to think about how to add that without rewriting too much.
The cookers of roms are by default including bunch of applications to ROM which i dont want to have and each time flash new version i need to manually remove them (like all google applications which takes quite a while and i am quite successfull at missing some). The rom is a zip file so i could make a program to kick apks out of rom automatically and repack it which isnt much of work to do but i am worried if such rom would still work. There is also a second problem, the digital signature which from expirience produces the yellow warning triangle at boot, i dont have problem with creating my own public/private keys and signing the rom but again i have no clue where the signature should be and where to register a private key (or maybe the samsung one is known?).
Is there some document on this topic or someone is prepared to help me out?
takes 20-30 seconds to open titanium and do a batch uninstall of the apps you dont need
Hmm... i dont use it but i will try, although i would still rather do a batch remove of all unwanted applications on my own before they even get installed. And adding a new application to install first also wouldnt be a bad idea (LBE privacy guard)
You can just extract the rom zip and from that delete the apks you dont want from the System --> App folders or Data --> App folders if there is anything in there. You could also use this 'opportunity' to choose which Kernel and Modem etc you wanted if you plan on changing / flashing different ones later. Re-zip and flash!
I will say this though, in the past i've done this and for some reason certain apps that I left in the zipped rom didn't install, no biggy though
Ok, this was the answer i was searching for. One more thing, what to do with digital signature?
Custom rom .
Open with Win Rar do not extract.
Open System Open Apps
Delete whatever you dont want and is safe to do so .
Close Win Rar and flash rom .
jje
Hmm, i am just playing with one thought, if the android is tied to apk extension for installing, the changing of zip header (actually from historical reasons it is footer ) to rename the apk to ap_ for unwanted application would acctually kill it from installing without ever unpacking it... and the code is actually even more trivial, search and replace...
I pulled down `boot.oat` from an API22 Android phone. It's Android 5.1 Lollipop which brought the change from Dalvik to ART and is a bit mistified (at least for me).
To make it exact this is from an old Xperia Z Ultra (factory ROM, nothing is/was customized).
As far as I understand, modifying boot.oat is not easy, and permanent, as this file is regenerated every time whenever a package installation/deinstallation is happened.
I need to modify a class which resides in `framework.dex` which I found in `boot.oat` (/system/framework/arm/boot.oat).
I have several questions I don't really understand:
1.) I have `framework.jar` in /system/framework, but it's size is 309 bytes, contains only manifest.mf. Does this file has any correlation to `framework.dex` in `boot.oat`?
2.) What is `boot.art`? It was not needed to deodex `boot.oat`.
3.) How can I properly put back my modifications to `boot.oat`? (Can I brick the device by providing a wrong `boot.oat`? Or- as it can be regenerated after package changes, it will also be simply regenerated if it's invalid?)
4.) How can I make my change permanent, i.e. survive boots, package installations, etc (in general boot.oat regeneration)?
Thanks for reading folks!