ok so im loving the svn and superlte and all that, can someone please give me some direction as an order to flash all the different mods and such? i understand different orders for different purposes im just looking to get mine as fast as possible and able to tweak the hell out of everything and . Also a follow up question when checking out and after exporting i add my apps and such what do i gotta do besides zipping up the file to make it flash right? has always i appreciate any feed back anyone can give me
BigTexastrev said:
ok so im loving the svn and superlte and all that, can someone please give me some direction as an order to flash all the different mods and such? i understand different orders for different purposes im just looking to get mine as fast as possible and able to tweak the hell out of everything and . Also a follow up question when checking out and after exporting i add my apps and such what do i gotta do besides zipping up the file to make it flash right? has always i appreciate any feed back anyone can give me
Click to expand...
Click to collapse
Not sure I'm quite up to date on the latest ROM slang lingo, but I'll do my best to provide some insight from a developers point of view.
In regards to creating a ROM .zip, which I think is what is referred to as, "checking out and after exporting I add my apps and such what do i gotta do besides zipping up the file to make it flash right?", the process is fairly generic. The ROM .zip (update.zip) file will be processed and loaded in the custom recovery.
The directions are generally all located in the updater-script file under META-INF/*. If the only action being done is adding apps to /system/app on a ROM .zip which already contains apps in /system/app, nothing should need to be changed in the updater-script file.
If apps are being added to /data/app, but nothing in the ROM currently installs to /data, might need to a copy_recursive to updater-script to make sure the /data directory from the ROM .zip is installed properly.
If there are other questions, the more detailed the links and question, the better we can answer! Hope some of the technical details help resolve the question!
Related
So I'm trying my luck at ROM creation and am learning as much as I can. One thing I haven't been able to find through Googling etc is how to port a ROM from one device to another, or more specifically what folders/files need to be replaced in a ROM to make it work on another device?
Appreciate any guidance, thanks guys!
PS I'm using DsiXDa's Kitchen, but it "doesn't support any devices besides HTC devices" and I want to port a ROM to a Dell Streak from an HTC Nexus One. Is it even possible and what files can I manually replace to get it to run?
dcogen said:
So I'm trying my luck at ROM creation and am learning as much as I can. One thing I haven't been able to find through Googling etc is how to port a ROM from one device to another, or more specifically what folders/files need to be replaced in a ROM to make it work on another device?
Appreciate any guidance, thanks guys!
PS I'm using DsiXDa's Kitchen, but it "doesn't support any devices besides HTC devices" and I want to port a ROM to a Dell Streak from an HTC Nexus One. Is it even possible and what files can I manually replace to get it to run?
Click to expand...
Click to collapse
I'm looking at a Streak ROM right now, and it looks fairly standard for Android. I would search for 'vendor tree' and/or 'extract-files.sh' to get an idea about what files and settings you might need. That will get you started. You have to swap kernels, that's a given. You'll probably need a few additional things from a stock Streak ROM, like:
files in:
/system/usr/keychars
/system/usr/keylayout
/system/lib/hw
/system/lib/modules
/system/etc
some libs in /system/lib
Probably a few things from /system/bin and /system/xbin
Look at the *.rc files in both the N1 ROM and the stock Streak ROM. They will call binaries and make changes. It's all tied together and is quite complex for such a 'small' thing... Get ready to do some research and testing and don't expect it to just work right away. If it does, your lucky.
I use WinMerge to compare ROMs all of the time. It will give you clues as to what is needed for the ROM to work on your device. And logcat will also point you in the right direction on occasion
Thanks a bunch gnarlyc!
Least I have a starting point now, going to get to Googling and see what I can figure out. And WinMerge is an awesome tool, thanks for that. I'll post back here if anything. Thanks again!
Anyone else have some information to share as well that could help?
EDIT: How do I get WinMerge to work? I installed it and tried to compare the two .zip files and it just shows jibberish in each window?
dcogen said:
EDIT: How do I get WinMerge to work? I installed it and tried to compare the two .zip files and it just shows jibberish in each window?
Click to expand...
Click to collapse
Well, it shouldn't show gibberish. I have it up right now with two init.desirec.rc files from two different ROMs. It's not going to be able to compare .zips though. Only text files and folders. You'll have to unzip those.
There are other programs that do the same thing, like 'N-way folder compare' and 'Beyond Compare' and plain old 'diff' in Linux or cygwin. Find what works best for you.
gnarlyc said:
It's not going to be able to compare .zips though. Only text files and folders. You'll have to unzip those.
Click to expand...
Click to collapse
I actually found that they have a .zip plugin to allow you to compare .zips and I tried to install it but it just isn't working. When I try to unzip them and just select the unzipped folder it opens it in the selector window instead of just using the folder.
I'll keep messing with it, thanks again for the starting point at least
Hey all, Well i know we could not wait for a Honeycomb theme, i know i cannot, but heres my conundrum.
I have made a honeycomb keyboard, but cannot get it to install for the life of me, ive used the testkeys, shared, platform, etc (all using Signapktic from Stericson. Does anyone have any clue as to why it will not install?
A few questions that i know you might ask, answered ...
No, there is no other keyboard, other than swype, and samsung keypad..
I made it off of the GB keyboard...
Yes, I have made many of themes, many of changes to Frameworks, and have had sucess installing, and running my custom roms....
My question basically is this, IF POSSIBLE, CAN ANYONE SIGN THE FILES I HAVE TO MAKE THIS WORK? PM ME AND I SHALL SEND THE FILES. CREDIT WILL BE GIVIN, I AM ON THE OTHER HAND GOING TO NEED SOME SORT OF PROOF YOU KNOW WHAT YOUR DOING, I WORKED REAL HARD ON THIS, SO FOR RIGHT NOW ITS PRIVATE, HENSE THE PM.
THANKS AGAIN IN ADVANCE. REMEMBER .. LETS GET THIS HONEYTCOMB GOING
I know that most of the keyboards dont work simply by installing but rather need to be pushed to the data\app or data\app_s folder depending on which rom you are running. You can accomplish this using adb or using a file explorer like RootExplorer.
Thanks
Thank you man, this helps a whole lot. Now do i need to re-sign each apk inside the rom folder? or can i just re-sign the .zip?
georgegreco86 said:
Thank you man, this helps a whole lot. Now do i need to re-sign each apk inside the rom folder? or can i just re-sign the .zip?
Click to expand...
Click to collapse
I'm not sure what .zip you're refering to other than a CWM recovery flashable .zip for you keyboard. If this is what you mean, then use the same signiture (key) you'd find in any of the flashable .zips on the forums. In other words, just copy over the META-INF folder from some other .zip to yours. Of course, you'll want to make sure the update-script in this folder is pointing at the proper directories for installation.
For your apk, you should only need to sign it if you changed the AndroidManifest.xml. Otherwise, just keep the META-INF folder from them original apk.
Does anyone know if someone has created a deodex .zip file to flash via customer recovery?
For those that don't know, many of the apk files installed by an official rom will have a .odex file associated with them which slows down your phone considerably. These odex files interact with delvik cache and java VM and from what I understand wreak havoc on data access times and are largely uneccessary. Other dev platforms such as the droid x and evo have a .zip file that you can simply flash via recovery that will "deodex" your apps in system\apps folder. Basicially this zip will take your odex file and associated apk file and take the important information out of the odex and input it into the apk making just one streamlined faster file.... with all of your odex files gone, your phone will spend less time executing programs both for end user and core google apps and your phone will be way faster. Any idea if someone has developed this yet for the streak? Thanks
**EDIT**
I know this is a question but I thought it should go into development due to the potential of some of the dev's responding to this and posting useful developement info that we can try out and report back to the dev section. Plus, most of the trollers in Q&A probably don't know what this is or even care. Thanks
I am interested in this as well
Sent from my Dell Streak using Tapatalk
Steve's roms are pre-deodexed, just look under system/app, you can't find see any odex file, or simply perform a search on 'odex' in root explorer and the result should be none.
sharptv said:
Steve's roms are pre-deodexed, just look under system/app, you can't find see any odex file, or simply perform a search on 'odex' in root explorer and the result should be none.
Click to expand...
Click to collapse
good to know.
although if someone makes an app/file to do the job it will be handy in the future
Pleas do not post in Multiple forums about the same Topic
Does anyone know where I can find a copy of this? I've done a search and all I can find is one from the international version and that's based on the 2.3.1 build.
TIA
check here http://forum.xda-developers.com/showthread.php?t=1286432
daraj said:
check here http://forum.xda-developers.com/showthread.php?t=1286432
Click to expand...
Click to collapse
Nothing there about stock system dump.
BigBolo said:
Does anyone know where I can find a copy of this? I've done a search and all I can find is one from the international version and that's based on the 2.3.1 build.
TIA
Click to expand...
Click to collapse
Entropy512 started with a stock system dump that someone, (maybe Jivy26), made after installing a custom kernel. But I don't remember he ever posted a link to it. He may still have it hanging around, though. That's what he used to make his stock plus root package.
BigBolo said:
Nothing there about stock system dump.
Click to expand...
Click to collapse
Um, what do you think a flashable stock system image is? (Other than being a sparse ext4 image, if you want something loop-mountable use simg2img...)
Seriously - spend just a LITTLE more time reading before you post in a Development thread. This device has been out for only 2 weeks so it's not like the Dev forum has tons of threads.
There's also a dd-derived system dump in page 5 of codeworkx's CWM kernel thread. I used jivy26's tar dump, although I should probably do a consistency check against seattleboi1982's dump.
Entropy512 said:
Um, what do you think a flashable stock system image is? (Other than being a sparse ext4 image, if you want something loop-mountable use simg2img...)
Seriously - spend just a LITTLE more time reading before you post in a Development thread. This device has been out for only 2 weeks so it's not like the Dev forum has tons of threads.
There's also a dd-derived system dump in page 5 of codeworkx's CWM kernel thread. I used jivy26's tar dump, although I should probably do a consistency check against seattleboi1982's dump.
Click to expand...
Click to collapse
I'm actually looking for the system dump in a zip where I can extract it into folders. Not as a image. I want to basically get the media files. I did do a search in several forums trying to find it but came up with nothing.
Maybe I should of been more detailed and specific in my OP.
BigBolo said:
I'm actually looking for the system dump in a zip where I can extract it into folders. Not as a image. I want to basically get the media files. I did do a search in several forums trying to find it but came up with nothing.
Click to expand...
Click to collapse
Can't you just extract the stock system image?
eep2378 said:
Can't you just extract the stock system image?
Click to expand...
Click to collapse
I don't know how to do that...
Then you probably don't belong in android development (yet).
Use 7zip to extract the zip/tar/whatever.
In general, you're not supposed to put requests in Development. This should have been posted in General.
And a stock system dump IS an image dump. Zip files don't preserve permissions, and tar files only do if you prepared them carefully (good thing jivy26 did). The only way to be sure is to dd the partition.
If you want a nice easy to use zip, use paylyhoffman's stock deodexed CWM zip.
Entropy512 said:
In general, you're not supposed to put requests in Development. This should have been posted in General.
And a stock system dump IS an image dump. Zip files don't preserve permissions, and tar files only do if you prepared them carefully (good thing jivy26 did). The only way to be sure is to dd the partition.
If you want a nice easy to use zip, use paylyhoffman's stock deodexed CWM zip.
Click to expand...
Click to collapse
Thanks for clearing it up. My bad I thought this was the section to post requests like that.
Also folks before jumping on the guy, what he is asking for (at least with the .7z file posted) isn't as straightforward as everyone thinks.
If you first extract the 7z file, you'll get a PDA.tar file. Extract that and you'll get the kernel (zImage) and the lovely factoryfs.img.
Try extracting factoryfs.img with your favorite tools and see what happens.
Extracting the factoryfs.img is a real pain unless you are pretty hardcore -- in fact, there was another thread going on the in international SGS II forum with some pretty well known devs (who know their stuff) trying to figure out how to extract that bad boy.
So before everyone starts throwing rocks...you know the story.
Does this look easy to you?
http://forum.xda-developers.com/showthread.php?t=1054836 (relevant discussion starts around post #7)
and another solution (which also is not as simple as "right-click and extract")
http://forum.xda-developers.com/showthread.php?t=1081239
Now -- with that said, if one was really looking for an easy way to pull some media files from a ROM, you best bet would be to try and find a CWM flashable ROM (in a zip format) and do a regular extract on those, and you may find it much easier. They may not be stock, but if it's close, you may get lucky and find some of the stock media in them.
pinoymutt said:
Also folks before jumping on the guy, what he is asking for (at least with the .7z file posted) isn't as straightforward as everyone thinks.
If you first extract the 7z file, you'll get a PDA.tar file. Extract that and you'll get the kernel (zImage) and the lovely factoryfs.img.
Try extracting factoryfs.img with your favorite tools and see what happens.
Extracting the factoryfs.img is a real pain unless you are pretty hardcore -- in fact, there was another thread going on the in international SGS II forum with some pretty well known devs (who know their stuff) trying to figure out how to extract that bad boy.
So before everyone starts throwing rocks...you know the story.
Does this look easy to you?
http://forum.xda-developers.com/showthread.php?t=1054836 (relevant discussion starts around post #7)
and another solution (which also is not as simple as "right-click and extract")
http://forum.xda-developers.com/showthread.php?t=1081239
Now -- with that said, if one was really looking for an easy way to pull some media files from a ROM, you best bet would be to try and find a CWM flashable ROM (in a zip format) and do a regular extract on those, and you may find it much easier. They may not be stock, but if it's close, you may get lucky and find some of the stock media in them.
Click to expand...
Click to collapse
Thanks for clarifying that pinoymutt. Yea basically I know a lot of people don't like the finished charging notification but I don't mind it and I figured it's as simple as just placing the ogg file back in the ui folder. I'm on DG's Cog X2 and he had removed that.
BigBolo said:
Thanks for clarifying that pinoymutt. Yea basically I know a lot of people don't like the finished charging notification but I don't mind it and I figured it's as simple as just placing the ogg file back in the ui folder. I'm on DG's Cog X2 and he had removed that.
Click to expand...
Click to collapse
Doubt it's that simple. I removed the notification by modifying code. I would bet dg did the same.
Well as many of you know we're over most of the hurdles we needed to jump with the CM7 build for Nook tablet.
Updates for the internal version are simple via CWM, the SD version is not so simple of course.
I'm assuming that it should be possible to built an APK that gains superuser permissions then copies the new files to the system. Can anybody confirm this is possible please?
We need to know that we can tell our SD user that they can update their version just as easy as the internal user
Thanks in advance for your help again everyone!
Well presumably this is how ROM Manager and Metamorph both do their thing, just in a slightly more round about way (as they don't come with the files they need to copy). I'm almost 100% sure this is possible, but I've never tried it personally.
EDIT: Looks like this is how you'd do it: http://developer.android.com/reference/java/io/File.html. Specifically the renameTo() method.
CelticWebSolutions said:
Well as many of you know we're over most of the hurdles we needed to jump with the CM7 build for Nook tablet.
Updates for the internal version are simple via CWM, the SD version is not so simple of course.
I'm assuming that it should be possible to built an APK that gains superuser permissions then copies the new files to the system. Can anybody confirm this is possible please?
We need to know that we can tell our SD user that they can update their version just as easy as the internal user
Thanks in advance for your help again everyone!
Click to expand...
Click to collapse
Well there are about a dozen ways to do this. First of one of the hardest things is comming up with the commands/script. I can defiantly do this. If you want an apk, there are a few guys whom could port my script to an apk. I'm going to make a script here that will format, and create partitions and extract directly from the nook, no need to go through the fancy formatting and such, just go into terminal and run the script. Ill post a prototype for you to have the testers test!
Do you think something like BacksideUpdater inside custom ROM for LG Optimus V?
made by JerryScript
JerryScript i very nice guy, I bet if you ask him, he will let you play with his code
if is it what you looking for
Yes, this is possible. I wrote an app that flashes the recovery partition for my older Froyo phone in the very rudimentary Basic4Android. Copying files under root privileges was part of this process. Fairly easy if you find the right coding examples in whatever your development platform of choice.
xdajunkman said:
Yes, this is possible. I wrote an app that flashes the recovery partition for my older Froyo phone in the very rudimentary Basic4Android. Copying files under root privileges was part of this process. Fairly easy if you find the right coding examples in whatever your development platform of choice.
Click to expand...
Click to collapse
So one of the problems is its not really copying. Its more of an extraction from one place to another. We are required to use dd, and fdisk(for formatting).
GREAT! I was worried updates would be to complicated for people
Sent from my Nook Tablet using xda premium
... and I was worried that I might have to wipe my NT clean again to get the updates. After a week with this wonderful upgrade, I've got a LOT of customization I don't want to lose...
Whoops, wrong button with the thanks. Anyway, it occurs to me you could just have people run a script from a terminal emulator. That would probably be the simplest way to do it. Make an Update folder on the SD card, add it to the PATH by default, and users could just copy over the update files and run the script. Just a thought.
Sycobob said:
Whoops, wrong button with the thanks. Anyway, it occurs to me you could just have people run a script from a terminal emulator. That would probably be the simplest way to do it. Make an Update folder on the SD card, add it to the PATH by default, and users could just copy over the update files and run the script. Just a thought.
Click to expand...
Click to collapse
Has to be simple, something like copy an update.zip onto the SD card then run the apk which will automatically run the update in the zip But my knowledge of such things is limited so I need help there
Same process. With the above method, the user would only have to copy over the file, open a terminal, and type 'update'. With the apk idea you just have to add a little more time for someone to actually write the app (not that it would take too long).
Sycobob said:
Same process. With the above method, the user would only have to copy over the file, open a terminal, and type 'update'. With the apk idea you just have to add a little more time for someone to actually write the app (not that it would take too long).
Click to expand...
Click to collapse
Hmm.... that sounds good.
Anybody know how to actually implement it ?
Dammit, idk why I keep hitting the thanks button thinking it's reply >.>
Anyway, it's just a matter of setting the PATH variable to include /sdcard/Update/ or something similar. To make an actual update, make a folder called Update, fill it with all the files that need to be copied over (probably in a directory structure), and write a script that actually copies everything over. You'll need to make sure sh is in /system/bin (I think it is by default).
You could zip the the files as well, using gunzip (busybox?) to extract them before copying them, then deleting them when you're done, just to keep it cleaner for the user.
The only downside to all this is that I don't know how you would flash a kernel.
Sycobob said:
Dammit, idk why I keep hitting the thanks button thinking it's reply >.>
Click to expand...
Click to collapse
That makes two of us!
Sycobob said:
Anyway, it's just a matter of setting the PATH variable to include /sdcard/Update/ or something similar. To make an actual update, make a folder called Update, fill it with all the files that need to be copied over (probably in a directory structure), and write a script that actually copies everything over. You'll need to make sure sh is in /system/bin (I think it is by default).
You could zip the the files as well, using gunzip (busybox?) to extract them before copying them, then deleting them when you're done, just to keep it cleaner for the user.The only downside to all this is that I don't know how you would flash a kernel.
Click to expand...
Click to collapse
I'm guessing you'd just flash it as usual, surely that one is the easiest? Copying stuff to boot partition would hopefully be just as simple, I was mainly worried about updating system files. I could do with building one for the current update to test the theory!