Database Develop

[Android] Dr. NoMoRootfs! or How I learned to stop worrying and love the extra space

Everything needs to go in /sdcard/andboot
FILES YOU NEED:
the nbh flashed to your phone
an sd card with the andboot folder at the top level
an androidinstall.tar file plopped into the andboot folder
thats it
then just hold down volume up or dpad center or the middle of your touchscreen when booting and go through the menu to choose where to put things and then install the system. (for those without a dpad, pretend the touchscreen is a giant dpad)
if you're doing it with haret, extract basefiles to your sd, plop the androidinstall.tar into the same folder, and boot, hold down volume up (camera on kaiser/polaris) just like the nand people (but don't pick nand to store the files, it won't work)
---------
all the files
basefiles for the haret folks out there
Grab the nbh files for your device. Only difference between eclair and non-eclair is that eclair is set up to use the newer hw3d driver, non-eclair is set to use the older one (for donut/cupcake)
These do not use rootfs. They remove it completely and free up that extra space in your nand for a bigger, cleaner system.
They also have my new menu-based installer! Yay! Just hold-down volume-up or dpad center or the middle of your touchscreen
THIS WON'T WORK WITH ANY OF THE OLDER SYSTEMS! THE SYSTEM MUST INCORPORATE THE APPROPRIATE FILES FROM ROOTFS (and the rom cooks will let you know when theirs is ready)
The first system to use this is based on eclair 2.1 with working sleep and audio
Here's my tattoo system for this method
FYI Craig & I spent a lot of time on these!!!

How to create a build
How to make your build work with this
So it actually isn't that hard.
Extract your sqsh to a folder somewhere, so you have, say /android/system
Mount/extract whichever rootfs worked best with your system somewhere else, say /android/rootfs
Code:
cp -a /android/rootfs/init.etc/* /android/system/etc
cp /android/rootfs/lib/donut/* /android/system/lib
cp /android/rootfs/lib/modules/* /android/system/lib/modules
cp /android/rootfs/lib/hw/* /android/system/lib/hw
cp /android/rootfs/init.cfg/init.donut.rc /android/system/sysinit.rc
You'll need to modify the sysinit.rc a bit, as in the rootfs some things are commented out that shouldn't be, and it references a few things in /bin or /etc that aren't there anymore.
Also, don't forget to uncomment the line near the top of sysinit.rc that creates a symlink from /system/etc to /etc
Once you are done, just do this to create the installer:
Code:
cd /android
tar cvf androidinstall.tar system
Soon, I may upload some packs for making the process easier, with updated sysinit.rc's for each system type. If I have time, we'll see...
Note, you can update the contents of the .tar file from windows/izarc/winrar/etc and it'll still work. you don't need to keep messing about with linux anymore if you don't want to

How to update things
How to create an update pack
Since not everyone gets things right the first time, and we keep getting updates, the rootfs made it easy to install updates without downloading the whole system again.
Well now anyone can create an update pack
just create a tar file called androidupdate.tar, make sure it has everything in a /system folder with whatever files you want, drop it into /sdcard/andboot and reboot holding down volume-up (camera on kaiser/polaris). Choose the update option and you should be good to go.
If things get wonky when you try to boot up, give the fix permissions option a shot in the installer, if it still fails, try wiping the dalvik cache, that can fix things up too.
About the installer
I ripped it off from here, but put about 6 or 7 solid hours into getting it to fit and react with the keys/screen

May be new
rootfs
may be new
better eclair support
---
with android development this fast for "yomama so old" phone, who knows what future holds?

sshark said:
May be new
rootfs
may be new
better eclair support
---
with android development this fast for "yomama so old" phone, who knows what future holds?
Click to expand...
Click to collapse
whats a rootfs hahaha

Might be something called "Code Name Ginger"....or our tame racing car driver, we call the Stig.

nabicat said:
Might be something called "Code Name Ginger"....or our tame racing car driver, we call the Stig.
Click to expand...
Click to collapse
what the..... that was random

Holy cow.. like there's nothing even in this thread and it's already filling up..

I think I know what it is..
Vilord ported Dalvik from 2.5 which now includes native support for HW accel for MSM7500..

jesus.

Do we still need to have three partitions on the card? Or would one FAT32 partition be sufficient?

@vilord:
is everything needed for the rootfsless nbh in the git? I would like to test this with ´my kaiser

This works for Polaris? Really thanks!

the bootenv git should have everything needed for this. I haven't tested on my polaris yet, but it should "just work" on polaris and kaiser as long as martin's method to drop the active key into /proc works on all hardware.

What happens to the .conf files?
What about /media ?
Thanks for all of your efforts

conf files are no longer used from the sd card.
If the cook put things in the right places, there should be a /system/etc/userinit.conf that gets parsed during android boot, but it is up to the cook to not screw that up.
This way is a lot cleaner, but it does a LOT less handholding for lazy cooks.
the upside is that it is *very* easy for anybody to fix a broken androidinstall by just piecing together what needs to change into an androidupdate.tar
/media is still used if it is on your SD card, but there's enough space and things are fast enough that media files should be included in /system now

This is a HUGE development for rom devs.
I will be honest in saying I've been having a hard time not hitting the 90MB cap with my next Warm Donut release.
Infact, I spent 4 hours yesterday de-odexing and compressing the classes.dex back into the jars and apks to save space.
With this new method this gives us ALOT more space. I applaud you for doing this. It breaks alot of the current builds but at the same time gives us a ton more flexibility for future.
And what I really like from this is it removes the confusion and headaches on configuration, giving the power to the ROM dev to include the necessary settings.
Question though. Different phones (Vogue, Polaris, Kaiser) may require different configurations. In the past it was a simple "just use this conf with this phone"
Thanks again

so when running from haret - getting an error about looking for a system file, I have all the files in andboot folder, any ideas on what I'm missing.

Know what would be really nice? In the setup, the ability to change LCD_Density and resolution.
This would eliminate the confusion users may have in editing the build.prop and rom files to change these values.
I guess the ROM devs could distribute separate files/tars for each res/density but that gets redundant if you know what I mean.

I'm using haret, but I dont see any option to choose to install not to nand, i get into the installer and it says install system so i click that but then it just goes through installation and fails. How do i choose to install to sd card?

Updater-script

I put together a theme that I want to be able to install on my phone. Issue is I am not 100% what updater-script to use nor how to have it setup so that it will put the files in the correct place...do I have to have a command to delete the .apk files that I am theming? Any help would be appreciated. I have attached my file. I am getting a status 6 error so I know that it cannot read something. Not sure what is wrong.

Hatman41 said:
I put together a theme that I want to be able to install on my phone. Issue is I am not 100% what updater-script to use nor how to have it setup so that it will put the files in the correct place...do I have to have a command to delete the .apk files that I am theming? Any help would be appreciated. I have attached my file. I am getting a status 6 error so I know that it cannot read something. Not sure what is wrong.
Click to expand...
Click to collapse
I use update-scripts mainly because if you do something wrong in the script it tells you what line you failed on and you can fix it. Also it's just what I learned on and what I'm comfortable with. If you're flashing a theme good rule of thumb is to make sure you wipe the dalvik cache you can do this with your script.
If you're working with windows don't use note pad it doesn't format the script properly. Try notepad++ if you're on linux just use gedit mac text wrangler.
Make sure you have the correct directory structure set up ie
META-INF/com/google/android/update-script then system/app and or framework.
Here's a simple script that will do the trick for you.....
Code:
show_progress 0.1 0
delete_recursive DATA:dalvik-cache
copy_dir PACKAGE:system SYSTEM:
show_progress 0.2 100
Hope this helps.

Thanks Lou, but I am still getting the error Status 6...that means that it cannot read the file...I am using notepad ++ to edit it. I used only what you provided in the file and the path to the file is Themename\META-INF\com\google\android I also have an update-binary in that dir...do I delete that file?

Try this one.

touchpro247 said:
Try this one.
Click to expand...
Click to collapse
I did not get any error this time and it said that it installed but when I boots up nothing was actually installed.

Hatman41 said:
I did not get any error this time and it said that it installed but when I boots up nothing was actually installed.
Click to expand...
Click to collapse
You don't need an update-binary if you're using an update-script. When you zip up your folders make sure you only have at minimum to folders on your desktop that your compressing the META-INF and it's sub directories and the system folder and it's sub directories don't put those inside anything just select and compress them. Once they're zipped make sure to sign the folder.
If the script didn't give you any errors it sounds like you may have put the META-INF and the system folders inside another folder before you zipped it which may be why nothing installed.

HeyItsLou said:
I use update-scripts mainly because if you do something wrong in the script it tells you what line you failed on and you can fix it. Also it's just what I learned on and what I'm comfortable with. If you're flashing a theme good rule of thumb is to make sure you wipe the dalvik cache you can do this with your script.
If you're working with windows don't use note pad it doesn't format the script properly. Try notepad++ if you're on linux just use gedit mac text wrangler.
Make sure you have the correct directory structure set up ie
META-INF/com/google/android/update-script then system/app and or framework.
Here's a simple script that will do the trick for you.....
Code:
show_progress 0.1 0
delete_recursive DATA:dalvik-cache
copy_dir PACKAGE:system SYSTEM:
show_progress 0.2 100
Hope this helps.
Click to expand...
Click to collapse
+1 I had the error 6 when I made one in notepad and switched to notepadd++. I think I also had to stop using windows explorer to copy it to my phone, but rather adb pushed it. Windows is kinda quirky like that, sometimes.

HeyItsLou said:
You don't need an update-binary if you're using an update-script. When you zip up your folders make sure you only have at minimum to folders on your desktop that your compressing the META-INF and it's sub directories and the system folder and it's sub directories don't put those inside anything just select and compress them. Once they're zipped make sure to sign the folder.
If the script didn't give you any errors it sounds like you may have put the META-INF and the system folders inside another folder before you zipped it which may be why nothing installed.
Click to expand...
Click to collapse
Ok so I took both the META-INF folder and the system folder and moved them both to the root of C and then I zipped both and then signed the zip...now it does nothing...I go into recovery....then I select the zip file and the screen just flashes and nothing happens.
If you want to see what I have done you can get the theme file here. This is for SkyRaider 3.3.3 with the Ucommon pack and all credit for the .png files goes to RUJELUS22, Riptide9, Defitism, Jascias and of course to Ihtfp69 for making the ROM
Download --->> http://bit.ly/aGP66D

Hatman41 said:
I did not get any error this time and it said that it installed but when I boots up nothing was actually installed.
Click to expand...
Click to collapse
I'll try flashing your theme and let you know.

touchpro247 said:
I'll try flashing your theme and let you know.
Click to expand...
Click to collapse
Ok...i forgot to include that it is for the uncommon theme pack for SkyRaider 3.3.3 as it has a custom Rosie that is themed.

Hatman41 said:
Ok...i forgot to include that it is for the uncommon theme pack for SkyRaider 3.3.3 as it has a custom Rosie that is themed.
Click to expand...
Click to collapse
To late lol...
Worked, use this one. Just add the files to the zip.

touchpro247 said:
To late lol...
Worked, use this one. Just add the files to the zip.
Click to expand...
Click to collapse
So I took your file and added it to mine...took both directories and moved them to my C drive...then zipped them up and signed them...went to recovery and installed it...says it was installing...when phone boots back up...no theme installed.

Hatman41 said:
So I took your file and added it to mine...took both directories and moved them to my C drive...then zipped them up and signed them...went to recovery and installed it...says it was installing...when phone boots back up...no theme installed.
Click to expand...
Click to collapse
Don't do that. Just drag your app and framework folders to my zip.
Or
Copy and paste your apps/framework where you see the placeholders.
The reason you can't add it to your file is in your file where it saids "services" it should say "system". And a few other things is wrong w/ your file that I will list when I get a chance.

touchpro247 said:
Don't do that. Just drag your app and framework folders to my zip.
Or
Copy and paste your apps/framework where you see the placeholders.
The reason you can't add it to your file is in your file where it saids "services" it should say "system". And a few other things is wrong w/ your file that I will list when I get a chance.
Click to expand...
Click to collapse
Woot...worked perfect...thanks alot touchpro247!!!!

Hatman41 said:
Woot...worked perfect...thanks alot touchpro247!!!!
Click to expand...
Click to collapse
Np...
This theme is badas* btw

touchpro247 said:
Np...
This theme is badas* btw
Click to expand...
Click to collapse
Thanks...soon as I figure out why my Rosie is not working as it should I will post the theme for peeps to dl. I only put the theme together...I took 2 EVO themes and took the .png files that I liked and made this one. I am using the uncommon Rosie. I will prob also pull the clock as you can see in this screen shot you can see some of the other numbers in it...it only does this for the flip clock...the regular non-flip clock it does not do that.
***Edit*** Ok have the Rosie fixed...I forgot to include the services.jar from the uncommon pack.

Ok I have everything working correctly now have I have posted it here http://forum.xda-developers.com/showthread.php?p=9034373#post9034373

Uncapped/Unthrottled data for Incredibly Re-Engineered

I have done the steps below and have created the services.jar with the uncapped data mod. I used the steps given by BThomas22x.
First make sure you do a nandroid backup!
Flash the zip in recovery and then all should be well.
I have done this and works perfectly for me. Let me know your results.
Note: You do this at your own risk
Read disclaimers at bottom before continuing on with this if you do not know what any of this means.
Incredibly Re-Engineered Version 2.xx
http://www.megaupload.com/?d=0HDXJX85
So far this will work for 2.00 up to 2.20
Originally Posted by BThomas22x
Ok first things first... I just came to the EVO from the Epic, so I'm gonna join this community now .
..::..Disclaimer..::..
You are voluntarily flashing this at your own risk. I can not be held accountable for anything you choose to do on your own. If you try to blame me, I will laugh at you. ....While pointing.
..::..Data Service Governer Killer..::..
1. What does this do?
This is a modification to the services.jar framework file, that allows you to have an un-throttled internet.
2. Will this make my internet faster?
Yes and No. This will not "Upgrade" your internet. This only takes the trottle off, so you can download, or play games and not have to worry about it hitting a certain peak and lagging from that point on. It doesn't provide you with a new internet, only a warm fuzzy feeling from knowing you don't have to worry about it capping off.
3. If I flash this, will it break my phone?
If it did, yours would be the first case I heard of. I've personally flashed it NUMEROUS times.
4. Will this work on any ROM?
Yes. This is not based off a particular ROM, and can be used with ANY EVO ROM. ALTHOUGH If you're Dev has made changes to the services.jar file, this could wipe those changes out. If you are unsure, send me your services.jar file, and i will look for you. Hopefully, i'll be able to make a download list in a couple days with all the Dev's services.jar files, so you can download that specific one. You can always ask your Dev.
5. Do I have to be rooted?
Yes. In order to be able to flash this, you are going to need to have root with a custom recovery. I.E. Amon_Ra.
..::..Install Instructions..::..
Simply download, and place on the root of your sdcard. Then go into recovery and flash it as you would a ROM. Done.
..::..Download..::..
Data Service Governer Killer
..::ALTERNATIVELY::..
You can follow this method if you're Services.jar framework is already modified, or if you aren't sure.
1. Download these 2 files:
Smali_Baksmali
2. Create 2 folders on your C: Drive labeled "Smali" and "Baksmali". (This is for easy access to the folders when being cd'd)
3. Place the 2 downloaded files in the C: Drive folders accordingly. (I.E. Smali.jar in "Smali" folder, and Baksmali.jar in "Baksmali" folder.)
4. Using 7zip or WinRAR (or any other zip program) open the services.jar file that you pulled from your phone. Copy the "classes.dex" file and paste it into the "Baksmali" folder.
5. Open your command prompt and type the following:
cd C:/Baksmali
java -Xmx512M -jar baksmali.jar -o classes/ classes.dex
6. Open the newly created "classes" folder (its inside your Baksmali folder that you should already be in) and navigate through "/com/android/server/". Scroll down till you see the 6 or 7 "Throttle" files. They will be located between "TelephonyRegistry" and "TVCableObserver$1$1". DELETE ONLY THE "THROTTLE" FILES.
7. Back out of the folders until you are in the "Baksmali" folder again. Now open the "Smali" folder you created earlier. Place the "classes" FOLDER in the "Smali" folder.
8. Return to your command prompt and type this:
cd C:/Smali
java -Xmx512M -jar smali.jar -o classes.dex classes/
9. You should now see a "classes.dex" file in your "Smali" folder. This is the NEW compiled services.jar classes.dex file. Pull up the 7zip or WinRAR file you had open earlier, delete the current classes.dex file from the services.jar, and place the newly compiled one in it's place.
10. Place the services.jar file back into your ROM, and boot up. You are now running Unthrottled.
11. If you do not see the "Throttle" files, don't complain they're not there, your Dev may have already taken them out.
What this mod will do for you:
Originally Posted by gmichaelow
I think a bit of clarity is needed here. This mod will only stop Verizon from slowing down your data speeds.
It will NOT help you avoid overage charges.
For example let's say you're on a 250mb a month plan. This mod only ensures that you will get 250mb at unrestrcited speeds. Going over 250mb will still result in an overage charge.
Also, the reason people keep referring to 5gb on their "unlimited" plan is because Verizon starts to throttle data speeds after 5gb of data. That doesn't mean you get charged more, Verizon just slows you down. This mod will prevent that, and only that.
I hope that clears things up.
Click to expand...
Click to collapse

Worked over 2.1 just fine. Thanks!
sent from my Incredible using Tapa Talk

This also work for 2.20?

thanks for doing this dude- waiting for 2.2

aslong as u use the service.jar from incredibly reengineered it will work on any of its versions.

mikesincredible said:
aslong as u use the service.jar from incredibly reengineered it will work on any of its versions.
Click to expand...
Click to collapse
nice work man. gonna add this to the thread. the services wasnt changed from2.00 to 2.20 so it will still work.

chingy51o said:
nice work man. gonna add this to the thread. the services wasnt changed from2.00 to 2.20 so it will still work.
Click to expand...
Click to collapse
Alright cool. Saves the time then. Thanks for the notice

chingy51o said:
nice work man. gonna add this to the thread. the services wasnt changed from2.00 to 2.20 so it will still work.
Click to expand...
Click to collapse
so does this mean that 2.XX's are not "uncapped"

I don't know how everyone else feels but I don't think these data throttle mods deserve separate threads. They are very simple mods and take about two minutes to make. I feel these mods should be posted in the thread for whatever ROM is applied to.

nbanicholas said:
so does this mean that 2.XX's are not "uncapped"
Click to expand...
Click to collapse
by default no. i dont think to highly of it breaking a menu in the settings.. not to mention all this capped data is just speculations..

IHTFP came up with a way to do this without the FC's. You also modify the phone apk. Magnolia ROM has done this as well.

spence341 said:
IHTFP came up with a way to do this without the FC's. You also modify the phone apk. Magnolia ROM has done this as well.
Click to expand...
Click to collapse
I will look into that. Thanks
Sent from my ADR6300 using XDA App

scuccia said:
I don't know how everyone else feels but I don't think these data throttle mods deserve separate threads. They are very simple mods and take about two minutes to make. I feel these mods should be posted in the thread for whatever ROM is applied to.
Click to expand...
Click to collapse
The reason I made it was for people would couldn't make it or wanted to attempt making it. And whether it should be included the rom forum or not. I didn't want questions people had over this to flood the ROMs thread.
Sent from my ADR6300 using XDA App

Hey let me know if you figure out how to do this mod without the force closes. That would be awesome-

Quick question for those who have flashed this. Has anyone noticed less battery life?

josiahb217 said:
Quick question for those who have flashed this. Has anyone noticed less battery life?
Click to expand...
Click to collapse
didn't notice anythign to heavy?

★wildstang83's Guide For Basic Porting★

★wildstang83's Guide For Basic Porting★
You could always go to the TEAM REVERSE website and read the same guide, lol​
Disclaimer​It should be known that there is some risk involved when performing the porting method described below. If you still wish to continue on and follow this guide you are doing so at your own risk. Of course, I will not be held liable for what you do to your device on your own. I will say, use extreme caution and follow every step to its tiniest detail.​
Click to expand...
Click to collapse
Hey guys, I have had a few new users come to me wanting to learn how to port. So I have decided to take a little time and write up a guide for this subject. With this guide we will achieve at minimum a first time boot with Screen load and sound. This will not go into details of fixing G Sensor, MMS, eMMC, Cam or Netflix.​
NEEDED ITEMS:
Windows- Either 32 or 64 bit is fine. Ubuntu will work but is more complex.
7Zip
Notepad++
Android SDK
Android Kitchen
Our most recent Ginger Sense Leak ROM 4.01.605.0
Any Sense 1.0 or 2.1 ROM from the EVO Shift 4G, EVO 4G, HTC Desire. These 3 devices are the easiest to port from. Personally I find that the --EVO 4G is the easiest out of these three and is usually where I port from. Whatever ROM you choose must be deodexed for this guide.
A generic updater-script, update-binary and build.prop. I'll provide those in a link below.
From here on each rom will be refered to in this guide as such:
HTC Droid Incredible GingerSense Leak= Leak
Whatever ROM you choose to port= Port
Ok lets get it.
First things first. Take some measurements of file size.
Take the following size readings:
Ports zipped file size on disk:
Ports unzipped file size on disk:
Ports "system" folder size on disk after extraction: <---This is important!!!
Click to expand...
Click to collapse
We need to know the pre and post system folder size because the system has a max usage space of 250 MB. So in your final rom a system folder size that is below 250 is good. For example, in my latest build of my Pure Speed ROM I was able to achieve a system folder size of 163MB.
Phase One- Start with the Android Kitchen
Open the Android Kitchen and place your port into the original_update folder. Run the kitchen and go through the steps to make your working folder. Just hit enter whenever it asks any questions even when it asks about updater conversion. Once complete, choose the Option 2- Add root permissions. It may say 'su' already present just over ride it and choose option "f" ChainsDD's version. That will complete and go back to the main menu. Select option 3. Add Busy Box. Do the same thing. Now select option 0 for advanced options. In advanced options select option 17 to install busy box runparts. Once that finishes we can build the ROM. Select option 99, let it run then select option 1 for interactive mode, let it run, Then select "y" to zipalign the apks. it will run for awhile and then ask to convert back to updater-script. just hit enter for yes. hit enter to sign the rom. It will ask about renaming, just hit enter to by pass this. We will rename it later. It will say congratulations your rom is done or whatever. just hit enter and then close completely out of the kitchen. Go to where your kitchen is set-up and find a folder called OUTPUT_ZIP. Grab your rom out of there and place it on your desktop.
Phase Two- The actual porting operations
For good measure create two folders on your desktop. One called "Backup" and the other called "Dump". Both the leak and the port should now be on your desktop. Select them both and copy them to your backup folder you just created. Now open your port by right clicking it and navigating to 7Zip and clicking "open archive". Drag it to the edge of your screen. Open the dump folder so that it is side by side with the port. Now in the port navigate to the system folder. Select the "customize, lib and media" folders and drag them to your dump folder. Now delete them from your port along with the "usr" folder as well. You will see a folder in system named "etc". Open that folder and inside you will see a folder called "firmware". Delete the firmware folder. Also delete the "wimax" folder. We do not need it. Now open the Leak. navigate to system/etc and drag the firmware folder from leak to the port. Also drag AudioBTID.csv and vold.fstab from the leak to the port. Close the leak for now. In the port back up to the system folder. Open the bin folder and delete EVERYTHING with "a2sd, apps2sd or wimax" in its name. If there isn't any such things in there then don't worry about it. Now back up to system and go into "xbin". Do the same thing here. Once complete grab the "su" and "busybox" files and drag them to your dump folder on your desktop. Back up to system. Open bin. Drag those two files su and busybox from your dump folder to your ports bin folder. You should now have "su" and "busybox" in both of your ports bin and xbin folders. Now in the port back all the way to the root of the ports zip. You may see a folder called "data". Delete that folder and recreate it. just do it. Now open the data folder. In the dump folder on your desktop create a new folder called 'sysusr". Rename the "customize, lib and media" folders so they are "syscustomize, syslib and sysmedia" These folders are named so because they will be symlinked. Now drag these four folders to the data folder of the port. You can now delete the dump folder from your desktop. We don't need it anymore. Close everything thats open right now. Reopen both the leak and the port side by side. Of the leak navigate to system/usr. Of the port navigate to data/sysusr. Drag the contents only of the leaks usr folder to your ports sysusr folder. Navigate to system/lib of the leak. Navigate to data/syslib of the port. In the syslib folder of the port find the three folders called "egl, hw and modules" Delete them. Drag those same folders over from the leak to the port. Now in the leak system/lib folder find these files: libaudio.so, libaudioalsa.so, libaudioeffect_jni.so, libaudioflinger.so, libaudiopolicy.so, libAudioTrimmer.so, libEGL.so, libgsl.so, libhtc_ril.so and libhtc_ril_switch.so. Drag them to your ports data/syslib folder. Just drag and drop. Close everything on your screen. Reopen both the leak and the port side by side. In the port delete the boot.img and drag the boot.img from the leak over. Close the leak. navigate to "META-INF\com\google\android" of the port and drag and drop in the update-binary and updater-script that I have provided below. Navigate to system of the port and drag and drop the build.prop that I have provided below. one last thing. navigate to system/etc and drop in the apns-conf.xml that I have provided below. Close the port.
Porting is now complete​
We should now be ready to boot. Rename the ports zip if you like and drop it on your sd card, wipe and flash. If it boots, has sound and is somewhat usable pat your self on the back. You've just took the second step to becoming a great dev in the Android world. The first step was having the guts to even attempt this.
Here are those parts you need: wildstang83's Porting Parts​
Guide- How to customize your 2.1/3.0 Hybrid or 3.0 ROM lockring: http://forum.xda-developers.com/showthread.php?p=15681779#post15681779
Click to expand...
Click to collapse
If you run into any trouble while using my guide or notice anything that needs to be updated or added please feel free to PM me.
Credits:
PonsAsinorem- For giving me the idea to write this guide.
newtoroot- I'll never forget who took the time to teach me how to port.
joelZ9614- Allways being supportive especially when times were tuff and no one else was around.
wdfowty
NilsP
Conap
gnarlyc
Man the list goes on so really just a huge thank you to everybody!
Click to expand...
Click to collapse

Thanks! Been wanting to do this for a bit.

lol
10 characters

Guide made me 'lol'.

Alright guys, enough goofing around, lol
I added the whole guide for yall.

Sorry for those trying to read this in the xda app. It gets cut off around where it talks about the system size. You can just hit menu/browser and read it that way.

Porting a HTC Desire ROM tomorrow morning Thank you!

cbren said:
Porting a HTC Desire ROM tomorrow morning Thank you!
Click to expand...
Click to collapse
Good luck buddy. Let me know how it goes or if you need help.

Thanks stang
Sent from my ADR6300 using XDA Premium App

Thanks stang
Youre looking at a crackflashing troll with ORD

WoZZeR999 said:
Guide made me 'lol'.
Click to expand...
Click to collapse
The disclaimer made me lol

Wow this is great bro. I have to try this out!

When I try and flash my port, I get
Finding update package...
Opening update package...
Installing update...
Installation aborted.
It's an evo port and Android 2.3.3 Htc sense 2.1 I think.
http://forum.xda-developers.com/showthread.php?t=1046622

Same one I used and it worked perfectly just try again... follow stangs directions exactly as they're written..
Sent from my ADR6300 using XDA Premium App

Guys, if you are gonna report errors here please provide the error status as well.
It will make it easier for me and everyone else to see what you did wrong(not saying anything bad here) and to know what to look for next time.
A lot of problems can be solved by mounting usb through recovery and then transfering your ports over.

What do we use the OUTPUT_ZIP ROM for? Is that the "port" that we should be messing with?

cbren said:
What do we use the OUTPUT_ZIP ROM for? Is that the "port" that we should be messing with?
Click to expand...
Click to collapse
Yes thats the final rom that you zipaligned and rooted in the kitchen. Now take that and put it on your desktop and build it exactly as my instructions say and you should be good.

Will there be an " Advanced Porting " Thread? If so can you shed some light on github?

hightech316 said:
Will there be an " Advanced Porting " Thread? If so can you shed some light on github?
Click to expand...
Click to collapse
Im not a compiler. Im a porter. I'm sure we could get some info in here though.

hightech316 said:
Will there be an " Advanced Porting " Thread? If so can you shed some light on github?
Click to expand...
Click to collapse
What kind of github info do you need? I'm no where near an expert, but I know how to sync a repo from github to my computer. That's all I've ever needed to do, at least so far.

[Q] How to enable mass storage in CM 10.1 ?

Does anyone know how to enable USB Mass Storage on our phones under CM10.1? I've searched around and found this thread. But since I'm not familiar with changing build.prop I don't dare to do it myself. There are some CWM .zip files around to enable it, but they are on other phone's forums and I'm sure they just replace/change the build.prop so it's definitely not a good idea to flash those on a different phone than the ones they were intended for....
Long story short, does anyone know how to enable it on ours?
TIA!

Update on the process:
I was able to edit the build.prop according to the instructions, but that alone doesn't seem to do anything.
So I decided to try the next step, but where it tells me to do the changes below I wasn't sure what to do.
Thom75 said:
in framework-res.apk/res/xml/storage_list.xml
where oryginal line look like this:
Code:
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:maxFileSize="4096" />
after change look like this:
Code:
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:allowMassStorage="true" android:maxFileSize="4096" />
Click to expand...
Click to collapse
I was able to find the framework-res.apk file, copied to my computer and tried to open it with an XML editor... looked too complicated so I left it alone.
Does anyone know how to mess with that?

Open the .apk file with WinRar
-Drag the file you want to edit on your computer
-Edit the file on your computer
-Delete the old file in Winrar from the apk file
-Put the new file from your computer back in Winrar and save the "new" apk file
-Put the new .apk file on your smartphone
Before you install the new .apk file take a Root Explorer and look at the permissions of the old .apk file and set this permission on the new once...
I hope i could help you

Sivvis said:
Open the .apk file with WinRar
-Drag the file you want to edit on your computer
-Edit the file on your computer
-Delete the old file in Winrar from the apk file
-Put the new file from your computer back in Winrar and save the "new" apk file
-Put the new .apk file on your smartphone
Before you install the new .apk file take a Root Explorer and look at the permissions of the old .apk file and set this permission on the new once...
I hope i could help you
Click to expand...
Click to collapse
Thank you very much for your help! I didn't know apk files were just a compressed library of other files.
Now I am stuck trying to edit the "storage_list.xml" file... I tried to open with a few different xml editors, but could not get clean text like the example before. Any sugestions?
I attached the file below:

Apoena said:
Now I am stuck trying to edit the "storage_list.xml" file... I tried to open with a few different xml editors, but could not get clean text like the example before. Any sugestions?
Click to expand...
Click to collapse
Well, how about decompiling the .apk file with APK Tools instead of just opening it with WinRar? :laugh:
Yes, now I get a clean, editable, decompiled xml file.
I'll try editing both when I get home tonight and will post the results.

I guess this is a problem because of the emulated layout. There is a trick with setprop sys.usb.storage.config mass_storage but it does not work.
Keep me informed if you find something valuable (i'm on original CM10.1, latest nightly 0423 actualy).

Ok, here's the update from last night:
I started over since I flashed the nightly, which is good so I restarted with a clean slate.
- Edited build.prop - OK
- Copied framework-res.apk to my computer
- Decompiled framework-res.apk
- Edited storage_list.xml
- Recompiled framework-res.apk with new storage_list.xml
- Copied framework-res.apk back to my phone
- Deleted original framework-res.apk
- ...... instant restart & bootloop before I could paste the new framework-res.apk in its place
No big deal, just restored a nandroid backup I made before messing with anything and I'm back in business.
Apparently you can't mess with the framework-res.apk while your phone is on (with the OS running)... so now I need to research the right way to push/pull these files from ADB while on CWM recovery. I appreciate if someone could point me in the right direction since I'll be busy at work today.
To be honest, my gut feeling tells me that this is not going to work anyway. But look at what I learned so far... two days ago I wouldn't even think of compiling/decompiling anything... this is what XDA is all about, right?

Imho, the framework_res.apk and various tricks are all enabling or disabling a sys.usb.storage.config key. I'm not understanding nor finding informations about CM10.1 emulated layout, and if there are any reasons to forbid mass storage (because, yes, it seems it is disabled because it is not compatible).
This is something i have hard time with. On Android, you have tons of improvement for rom or kernel XY, but generally undocumented. If you apply this 'per device', the information is very fragmented and difficult to grab.
I was looking for a simple brief on base MTD partitions layout for LG P880, it seems the only way to have this is to dig KDZ files. Perhaps a Wiki would help the wannabe contributers like me to start ?

Any Solution For This Problem ??? I Can't Transfer Any Files To My O4X , What's The Point Of Cyanogenmod Then ??????????????

Nooby305 said:
Any Solution For This Problem ??? I Can't Transfer Any Files To My O4X , What's The Point Of Cyanogenmod Then ??????????????
Click to expand...
Click to collapse
Flash the latest nightly. MTP is working and you cab transfer files that way.
Sent from my tree using a ladder

effectively, if you are flashing for USM, you should stay on LG stock.

I know that the topic got a little old but I'd like to refresh it since more people (e.g. Ubuntu users) could be interested in enabling Mass Storage.
What I've done is:
1) pulled /system/framework/framework-res.apk
2) decompiled it with APKtool
3) added
Code:
android:allowMassStorage="true"
in storage_list.xml
4) builded a new apk
then I've rebooted my phone into recovery and (@Apoena you may be interested in it - there is a possibility to access /system through adb connected with phone in recovery mode) pushed the new framework-res.apk. I've also changed the entry in build.prop to
Code:
persist.sys.usb.config=mass_storage,adb
Everything seemed fine until I've tried to reboot the phone: instead of CM boot logo I got a black screen. Anybody has an idea what went wrong (maybe something during recompilation of the apk)?
And of course sorry for any language mistakes, I'm not a native speaker