Related
Hi all,
before I get started I would just like to say thank you to bengalih for
providing his excellent tools. All credit goes to him. Also, this method
would probably have been posted by him, but I think he's done enough
for us already
MODS: If this is in the wrong section, or should not be a thread, please
move it or delete it
So, this thread is basically dedicated to ROM chefs who would like to
make their ROMs compatible with the excellent SASHIMI tool which bengalih
has so graciously provided us with.
To get started, it's quite simple:
Download the attached OEM Package taken from bengalih's new ROM
Extract the Package in your OEM Packages folder (called Packages in KaiserChef and Kaiserkitchen
Cook it up!
What it does:
This OEM Package is actually quite simple. If you look at it, you'll see that it
includes Mortscript, which is used to trigger the .mscr script that is run by a
shortcut in startup, which checks for a SASHIMI folder every time the device
boots, and if there is one, it proceeds accordingly.
again, all credit goes to bengalih
enjoy
reserved.... (you never know)
reserved for changelog (if any)
I hate to ask seeing how bengalih has left, but is this all that is needed for SASHIMI compliance? I ask because the google cache of the tutorial states the use of a SASHIMI.xml file, which is not included in the package. I have not tested out your method, but will soon as I am trying to cook my own rom. I appreciate any help I can get on this as I waited too long before getting the package
this is the google cache here
evilvoice said:
I hate to ask seeing how bengalih has left, but is this all that is needed for SASHIMI compliance? I ask because the google cache of the tutorial states the use of a SASHIMI.xml file, which is not included in the package. I have not tested out your method, but will soon as I am trying to cook my own rom. I appreciate any help I can get on this as I waited too long before getting the package
this is the google cache here
Click to expand...
Click to collapse
See the official SASHIMI Compliance thread here
I hate to make a thread on this but would like to get started soon with learning how to root roms and add the kernel for multitouch and tethering. This is more for my personal use since I just want a stock rom with all the root benefits like jf use to and theses are the questions I have.
1. Will I have to take the update.zip file and extract everything and modify it then resign and I'm done?
2. I read some info on adding busybox and root which seem easy but when I run the chmod command and such everything will be through adb and the files will be on my pc so do I just make sure its all in the right directory and file path?
3. Where are the wallpapers stored in builds along with animations I will be looking into the framwork/framework-res.apk later but still curious
4. The modified kernel for tethering and multitouch is located where along with the market.db file?
5. What is meta.inf and how easy is it to make the cpu 528mhz standard also not sure what BFS and ASOP are haven't been keeping up.
P.S. I would really appreciate some help on this and I don't mind reading if this information is somewhere else so please provide a link and as always gotta show love to those who started this like JF, Hakuro, Cyanogen, Drizzy, and many more like daproy and kornub did a lot of helping.
I hate to make a thread on this
Click to expand...
Click to collapse
You mean you hate starting threads in the correct place?
Thats a fine line here. Although it is a question, it is specifically a development question. Its not a which rom do i choose?
Although android is "open source" these people dont give a **** about people trying to learn how to develop. They will pull the google line or something.
yeah me 2
Trying 2 learn
Im a noob, so I can only answer two of thosew questions
1. Anytime you modify your update.zip you will have to resign before trying to flash it onyour device.
5b. BFS: Brain **** (simple) Scheduler, something to do with the priority of running proccesses or something http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler. AOSP stands for Android Open Software Project, which i believe is just googles standard rom really (but I may be wrong)
I recommend you try out this rom though, kind of like JF but for Donut http://forum.xda-developers.com/showthread.php?t=538456
Very Sorry, double post
Thanks! I'm actually using that rom and its what has me so interested in this cause I hate having to flash another update.zip to get the full root benefits when JF just made everything available in one nice package but looks like I will just have to go through trial an error unless I get some more feedback cause switching between cyan 4.1.11.1 and JF1..51 is killing me and taking up space on my card.
With my little to no knowledge, replacing the boot.img and some files in system/bin with the ones provided in theofficial expansion pack should give you all that you need. With no extra apps.
yeah me 2
Yeah me too
hi,
Did a search for the topic, found lots of threads about cooked or custom ROMs but nothing about uninstalling all the junk in the ROM that I don't want that came pre-installed on the device.
Any links to actual threads that talk about how to do it would be greatly appreciated.
Not looking for a cooked ROM, am fine with the stock Sprint ROM, just want to delete all the extraneous applications that came pre-installed.
Thank you in advance.
If it isn't listed in the remove programs section there is a good chance it is a part of the rom and isn't removable.
See, someone had something for the AT&T version
Rhodium500 said:
If it isn't listed in the remove programs section there is a good chance it is a part of the rom and isn't removable.
Click to expand...
Click to collapse
Unfortunately, they didn't port it for the Sprint and was hoping to find something similiar, and yes, there IS a way to remove stuff from ROM, just trying to find out how.
If you're trying to remove software like NFL Mobile and stuff, this is the way to do it:
- You have to dump stock Sprint ROM into a kitchen
- Search for *.cab files in the OEM folder. When you find some, those will be the only ones that you can remove. All others are mixed into the ROM files and MUCH tougher to remove. Remove the ones you don't want
- Remove install instruction for those cabs in the install.dat file
I know that's VERY vague, but you need to have some knowledge with kitchens and making them to do this. So, try first learning how to dump a ROM into a kitchen and remaking it. Ervius Visual kitchen is very nice. It has a GUI interface and you can dump a ROM right from that. THEN you take the stuff you don't want in it and recreate it!
stickfigure said:
If you're trying to remove software like NFL Mobile and stuff, this is the way to do it:
- You have to dump stock Sprint ROM into a kitchen
- Search for *.cab files in the OEM folder. When you find some, those will be the only ones that you can remove. All others are mixed into the ROM files and MUCH tougher to remove. Remove the ones you don't want
- Remove install instruction for those cabs in the install.dat file
I know that's VERY vague, but you need to have some knowledge with kitchens and making them to do this. So, try first learning how to dump a ROM into a kitchen and remaking it. Ervius Visual kitchen is very nice. It has a GUI interface and you can dump a ROM right from that. THEN you take the stuff you don't want in it and recreate it!
Click to expand...
Click to collapse
Thanks, I was possibly hoping to avoid the kitchen approach. Do know how to do it, didn't want to go that route. There is a utility for the AT&T version that someone created, of course, can't find the link now, crudscraper or something like that. It does exactly this. i was hoping to find something similar for the Sprint version.
Thanks for the reply, vague or not, it's appreciated.
sanjsrik said:
Thanks, I was possibly hoping to avoid the kitchen approach. Do know how to do it, didn't want to go that route. There is a utility for the AT&T version that someone created, of course, can't find the link now, crudscraper or something like that. It does exactly this. i was hoping to find something similar for the Sprint version.
Thanks for the reply, vague or not, it's appreciated.
Click to expand...
Click to collapse
See, every carrier adds it's own software on the ROM, so the AT&T ROM probably has it's own software. I can imagine one way the person could do it is see all the files and registry entries that are in each of the app cabs in the dumped ROM and have the app remove them. Someone would have to specifcally make it for Sprint. It's not something that can be ported from what I know.
If you going to go the route of changing registry settings, etc., then I would first disable the CM_Guardian_Service first. It will put back some of the settings you delete if you don't disable that PoS.
As lately some people are asking me about ROM porting I decided to create this new thread where we can share knowledge about this hard task.
Please note this is a Dev talk thread, so DON'T ASK about fixing a particular ROM problem here. Also don't ask questions like "My phone is bricked! please help!". This IS NOT the appropriate place for it. There are plenty of other threads to help you out.
Also note that this is not a step by step guide (and not a guide at all), it's just a point where you can start from. Android is a very complex system and there are many things I don't know yet. So, research and hard work is what you need to learn it deeply. My first tip is Google really works. Don't be afraid to search
Ok, to the basics. Porting a ROM is no simple task. It requires advanced understanding of how android works and how it is organized. Previous Linux/Unix knowledge helps A LOT. As android is based on this O.S. there are many similarities between both. In fact many ppl consider android to be a kind of linux distro.
The very first task to port a ROM is finding a device which is compatible with your own. For example Defy/Milestone2. Then you are going to choose a ROM to port to your device.
As our devices (Milestone2) have a locked bootloader we now need to find a system image that have a compatible kernel with the ROM we are trying to port. This is mainly based on trial and test and takes a long time. You'll be ending flashing your phone several times with RSD Lite. You should learn how to use MotoAndroidDepacker and how to create a fixed SBF.
The basic procedure to try that:
1. Open original ROM update.zip and remove any files/commands that flashes boot/devtree/recovery/anything.
2. Install this new file on your phone via CW Recovery.
3. Boot into bootmenu and enable ADB so you can read logcat while phone boots.
4. Choose Boot/Normal. If your ROM uses 2nd-init you will need to place/edit/adapt bootscripts into bootmenu 2nd-init folder.
5. Check logcat for errors:
- If you're getting HAL errors you're going to need a new kernel;
- If you can start android without getting HAL errors but still getting errors and bootloop on android animation you should try to replace libs with appropriate original ones.
6. Once you are able to boot android you should test it's features to see what needs to be fixed.
This is what I have to say for now. The thread is now open for discussion.
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
jorgebaruchi said:
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
Click to expand...
Click to collapse
It may be possible, but you'll have a hard time fixing the baseband.
You may have to mod the init.rc scripts and find the right radio binaries (rild is one of them) and drivers.
Ask those ms1 people for help, if they are still with the same phone...
Sent from my Milestone 2 XDA App
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
i guess it is second-init. but not sure
thanks a lot for this !!!
WeeDv2 said:
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
Click to expand...
Click to collapse
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
sahilarora911 said:
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
Click to expand...
Click to collapse
Don't worry, this is the right place
As for your question: yes you can work in windows if you like, but using at least a Linux VM is more productive. I don't have a full list of applications to give you, as different mods may require different tools, but I advice you to have at least:
- Notepad++ (essential for editing text files and keeping linux end-line format);
- dsixda's Android Kitchen (http://forum.xda-developers.com/showthread.php?t=633246)
- 7zip (or some other compress tool you like)
- Moded putty for ADB as working with windows command prompt really suck (http://forum.xda-developers.com/showthread.php?t=803225)
- Oracle Virtual Box (if you are going to use linux VM).
r2beta0 said:
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
Click to expand...
Click to collapse
Thanks again r2beta
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
sahilarora911 said:
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
Click to expand...
Click to collapse
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
r2beta0 said:
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
Click to expand...
Click to collapse
I know a bit about virtual box but as I said I'm not allowed to have softwares not approved by the IT team to be present on the system. Though I can get away with small things like notepad++ and 7-zip, having virtual box on my system may raise some eye brows.
I'm trying to arrange an alternative system.
Me neither. I must do almost everything at home, and at this very moment I simply don't have any free time. I'm afraid you're not going to see me here very often anymore (maybe in a few months? a year? well, it might be a bit too late for milestone2...)
hi. Have a question, I want to remove baseband from a flashable zip (lets say, CM7 from Tezet) , is it posible? I dont know where to look for it (baseband). Thanks!!
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
---UFO--- said:
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
Click to expand...
Click to collapse
Ok thanks for the info.
Sent from my A953 using XDA
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Megalith27 said:
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Click to expand...
Click to collapse
I meant to get to it last night, but I was tired after work and fell asleep watch tv. Eventually, later tonight, I'll be uploading PA for MS2. Check my Defy PA thread in 12-14 hours cause I'm about to go to work and I'm not gonna feel like making a MS2 PA thread or updating my Bravo PA thread -- but the Defy Thread is always up to date when I put out new roms.
Also, I'm looking to get either a Defy or MS2 -- I've heard that there's 3G issues with AT&T users (which I am) with the MS2 -- Apparently the MS2 has different 3G frequencies than AT&T. Are there any AT&T MS2 users who are knowledgeable about that? While I can deal with no 3G, edge only, calls only -- I need to make sure I can at least do that before I commit to something.
I'd rather have the MS2 because I want a hw keyboard and I don't have the $300+ to try and get a Photon Q LTE from eBay (and I don't have to change up my repos if I get a MS2). If anyone here knows of a phone that's AT&T compatible, Defy code compatible, and has a keyboard, please let me know.
Thanks.
//Normally I'd post the latter half in the Q&A section, but ya'll don't have one so I'm just gonna piggyback
//My Bravo doesn't have a Q&A page either -- it needs one that's not my PM box...Don't PM me on how to root your phone and flash CM7 -- read one of the 5 guides on the first page of both General & Dev...:silly:
Ok devs need some help here.
I am trying to port a rom to our Milestone 2...but it bootloops on rom animation.
I tried to logcat it but I don't think it gets as far as adb server to detect the device.and just keeps saying "waiting for device"...so I end up with no logcat to diagnose the problem.
I can logcat my current working rom but only after the phone boots....am i missing something here? please, help
Any help is very much appretiated.
Thanks a lot in advance
Hey Guys!
I tried to put the whole Question in the Title, but now the long form:
As you may imagine, i got a MTK-Based Phone. An Octacore to be precise (Elephone P8). Now there isnt much development going on, so i thought of jumping on the Developement-Train, and begin with something easier.
I thought of bringing a few fixed apk's and workarounds for known Problems into the standard rom.
My Question is:
So i have now a rar, which i have to extract, Open in Flashtool, load the Scatterfile and im ready to flash my Phone. Fine with that, but in the rar are only img-files i cant edit.
(i found a ext4-edit-tool for img-files here on xda, but its not functioning at all.)
But there is a P8update.zip on needrom, someone was keen enough to convert the rar-image into a zip-image, which is flashable through recovery, and the best is: i can just open the zip, and i can edit everything i want!
But how did he do it?
The Rom is JB, and i have KitKat installed and i want to edit a KitKat-Rom.
So how can i convert the rar-kind of rom to the easy editable zip-kind of rom?
Or am i understanding this completely wrong?
Thanks in Advance for any kind Tip youre sure going to give
Greetings from Berlin,
a clueless guy.