Develop Bugs

[DEV] UK Stock System Dump - Build ITL41D

Going to preface this with the fact that I'm relatively new to the dev scene. I'm still learning, but we all learn by doing right?
This dump is taken from my rooted UK retail O2 Galaxy Nexus. Rooted using adb method (not superboot method) - http://forum.xda-developers.com/showthread.php?t=1352004
Not entirely positive these are done perfectly (especially the .zip) but I think that may creatable from my dd image anyways. I'd appreciate someone with dev experience looking over these and okaying them, and maybe regular users staying away from trying to do anything with these until someone more experienced says they're alright?
I just figured that seeing I uploaded these for 2 people I may as well make them publically available for all.
I'm also including the steps I took inside code tags for anyone to point out any mistakes I may have made.
DD Image as requested by Maximilian Mary:
Code:
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/system of=/sdcard/galaxynexussystem.img
Available here: http://www.megaupload.com/?d=KXFYSMT2 or http://multiupload.com/CPP4L2553Y
Zip file as originally requested by Revolution
I followed http://www.robmcghee.com/android/creating-an-android-update-zip-package/ - Thinking back I realise I probably didn't need to sign it, whoops
Code:
## Create folders dump, dump/system, dump/META-INF/com/google/android
cd dump
adb pull /system system
## Edited /META-INF/com/google/android/update-script with:
## show_progress 0.1 0
##
## copy_dir PACKAGE:system SYSTEM:
## set_perm_recursive 0 0 0755 0644 SYSTEM:app
## show_progress 0.1 10
##
## Zip system and META-INF folders into gnsys.zip
## Signed using testsign.jar
Available here: http://www.megaupload.com/?d=KXFYSMT2 or http://www.filesonic.com/file/3935308085/gnsys-signed.zip
If anyone spots anything wrong with either my commands or my files, please reply with what I did wrong so I can learn from that, thanks.

el3ctrik said:
Going to preface this with the fact that I'm relatively new to the dev scene. I'm still learning, but we all learn by doing right?
This dump is taken from my rooted UK retail O2 Galaxy Nexus. Rooted using adb method (not superboot method) - http://forum.xda-developers.com/showthread.php?t=1352004
Not entirely positive these are done perfectly (especially the .zip) but I think that may creatable from my dd image anyways. I'd appreciate someone with dev experience looking over these and okaying them, and maybe regular users staying away from trying to do anything with these until someone more experienced says they're alright?
I just figured that seeing I uploaded these for 2 people I may as well make them publically available for all.
I'm also including the steps I took inside code tags for anyone to point out any mistakes I may have made.
DD Image as requested by Maximilian Mary:
Code:
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/system of=/sdcard/galaxynexussystem.img
Available here: http://www.megaupload.com/?d=KXFYSMT2
Zip file as originally requested by Revolution
I followed http://www.robmcghee.com/android/creating-an-android-update-zip-package/ - Thinking back I realise I probably didn't need to sign it, whoops
Code:
## Create folders dump, dump/system, dump/META-INF/com/google/android
cd dump
adb pull /system system
## Edited /META-INF/com/google/android/update-script with:
## show_progress 0.1 0
##
## copy_dir PACKAGE:system SYSTEM:
## set_perm_recursive 0 0 0755 0644 SYSTEM:app
## show_progress 0.1 10
##
## Zip system and META-INF folders into gnsys.zip
## Signed using testsign.jar
Available here: http://www.megaupload.com/?d=KXFYSMT2
If anyone spots anything wrong with either my commands or my files, please reply with what I did wrong so I can learn from that, thanks.
Click to expand...
Click to collapse
Thanks
Let my ROMs rock
---------- Post added at 03:46 PM ---------- Previous post was at 03:34 PM ----------
netchip said:
Thanks
Let my ROMs rock
Click to expand...
Click to collapse
UPDATE: I've unpacked the img file and imported the proprietary files.
So we can make ROMs

It appears MU is returning an error if you try to access the files.
I've uploaded the 2 files to other mirrors too, apologies if anyone has tried to grab these and failed.

I'm about to have some fun with this right now , i'm home from school i'm about to eat & work on something .

netchip said:
UPDATE: I've unpacked the img file and imported the proprietary files.
So we can make ROMs
Click to expand...
Click to collapse
I don't get it. What's here that's not at http://code.google.com/android/nexus/drivers.html#maguroitl41d ?
Sent from my Nexus S using XDA App

matt2053 said:
I don't get it. What's here that's not at http://code.google.com/android/nexus/drivers.html#maguroitl41d ?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That arent not all the needed files
Sent from my GT-I9100

Can I ask for boot image as well?

mike1986. said:
Can I ask for boot image as well?
Click to expand...
Click to collapse
You can generate your own with the AOSP repos
Sent from my GT-I9100

netchip said:
You can generate your own with the AOSP repos
Sent from my GT-I9100
Click to expand...
Click to collapse
Got one already, thanks

Why do you work with every single device , just saying ? Are you going to get the Galaxy Nexus , cause your doing work for the Amaze also now . I don't get it .
mike1986. said:
Got one already, thanks
Click to expand...
Click to collapse

Revolution said:
Why do you work with every single device , just saying ? Are you going to get the Galaxy Nexus , cause your doing work for the Amaze also now . I don't get it .
Click to expand...
Click to collapse
Because I like what I'm doing Is there any problem with it?

Nope , just asking a question .
mike1986. said:
Because I like what I'm doing Is there any problem with it?
Click to expand...
Click to collapse

@mike1986 - You cooking up anything for the DHD?

Custom hboots for HTC Desire (bravo)

I was completely board off my so decided to make some custom hboots for everyone, i have tried all 16 of them and all work fine. In the "Custom_hboots.zip" file there is 2 folders
[1] hboot.img
[2] PB99IMG
(16 hboots in each folder)
So you can flash just the "hboot.img" or you can do it the "PB99IMG" method. Every file in both folders have md5sum so make sure to just double check before you flash and of course at your own risk....In bootloader it will now say "AlphaRev XDA" (didnt know what else to put) So here are all the different hboot sizes...
Guide on flashing PB99IMG method... Credit @abaaaabbbb63
http://forum.xda-developers.com/showpost.php?p=45298337&postcount=21
System / cache / data
80 /5/ 352 - 90 /5/ 342 - 100 /5/ 332 - 110 /5/ 322 - 115 /5/ 317 - 120 /5/ 312 - 130 /5/ 302 - 135 /5/ 297
155 /5/ 277 - 165 /5/ 267 - 190 /5/ 242 - 200 /5/ 232 - 210 /5/ 222 - 215 /5/ 217 - 225 /5/ 207 - 250 /5/ 182
Download ~ REMOVED BY MODERATOR
Credit to Thalamus
ps: these hboots are for HTC Desire (bravo) only

Nice one, jmc. Very useful.
Just out of curiosity, do these hboots work on the CDMA Desire?

Re: Custom hboots
abaaaabbbb63 said:
Nice one, jmc. Very useful.
Just out of curiosity, do these hboots work on the CDMA Desire?
Click to expand...
Click to collapse
no they dont because the Thalamus hboot patcher uses AlphaRev hboot and if u look at the Desire General/stickies theres a thread by rootSU and he said CDMA users will brick their device if they us AlphaRev hboots. dont know why. i must read it actually.

As can be treated as stock or CM7.
Rom ever ask you any of them.
regards

AW: Custom hboots for HTC Desire (bravo)
Delete plx

Could you please create a 325 /5/ 97 hBoot for me?
I need a large system partition for my Sense 4 rom..

WhiteNeo said:
Could you please create a 325 /5/ 97 hBoot for me?
I need a large system partition for my Sense 4 rom..
Click to expand...
Click to collapse
:what:
What sense 4 rom? Theres 2 roms i know of and both work best with CM7r2 hboot.
U can make ur own if u really need it
http://d-h.st/OxZ
from my HTC Desire
RSK Sattelite SuperSense4.1

Are you talking about CoolDroid Revolution?
I've already tried this rom, but it is rather slow in my opinion. Probably because all the apks are on the ext4 partition.
That's why I'm trying to move the whole system files and system data to internal, mounting the sd-ext partition as /data.
Should improve the performance.
Btw, thanks for your link. I've been looking for exactly that file for nearly an hour now.

Firstly, thanks.
Do you just flash these using fastboot?

echidna3 said:
Firstly, thanks.
Do you just flash these using fastboot?
Click to expand...
Click to collapse
Yes.
Code:
fastboot flash hboot <path>

echidna3 said:
Firstly, thanks.
Do you just flash these using fastboot?
Click to expand...
Click to collapse
Or in bootloader, PB99IMG method.
RSK Sattelite SuperSense4.1

and where to take for cdma

*klim* said:
and where to take for cdma
Click to expand...
Click to collapse
Dont know, dont have a cdma device. Search google

You can find this thread on Desire Index! Great job jmcclue!:good:

Mr.Mefisto said:
You can find this thread on Desire Index! Great job jmcclue!:good:
Click to expand...
Click to collapse
Cheers big ears
(not that u have big ears, its just a saying haha)

jmcclue said:
no they dont because the Thalamus hboot patcher uses AlphaRev hboot and if u look at the Desire General/stickies theres a thread by rootSU and he said CDMA users will brick their device if they us AlphaRev hboots. dont know why. i must read it actually.
Click to expand...
Click to collapse
I read the thread and can't make any sense of what the "brick" issue is there.
I have heard of something called an "engineering HBOOT" which I think is what's needed.
If there's tut's specificly for hboots, or on the Android booting process itself, that I could download as HTM or PDF I'd love it (I only use Wifi on my device)
Thanks for your work
Virginwidow

Thanks. Just one question. Can small size of cache (5mb) cause force closing of some programs (Smart office 2, Ez PDF Reader). It runs only after 3-4 tries?

GDB007 said:
Thanks. Just one question. Can small size of cache (5mb) cause force closing of some programs (Smart office 2, Ez PDF Reader). It runs only after 3-4 tries?
Click to expand...
Click to collapse
No. I have been using the cm7r2 hboot, with 5mb cache, and I had no such problems.

One question: Can you also flash custom hboots via Android Flasher?
EDIT: Never mind, it works.

Flahsing the 155-5-277 on HTC Desire Android 4.1.1 and CM10 did not work.
abaaaabbbb63 said:
Yes.
Code:
fastboot flash hboot <path>
Click to expand...
Click to collapse
Hello,
I have an HTC Desire and on that runs Android 4.1.1 and Cyanogenmod10 (versie CM10-Elk759, build number: Elk_0161jb_JRo03R, Kernel version 2.6.38.8-evervolv-turba-jellybean). I tried to flashboot the 155-5-277 image file but after that, my phone did not start up again (got stuck at the initial HTC screen). After flashing the original hboot image again, things worked as before.
My questions now are:
1 What may have caused this (and related to this)
2 Could it be that the 5M Cache is too small for the HTC Desire with Android 4.1.1 and Cyanogenmod10?
3 Would it be possible for the original author of this article to provide some image file with Cashes of e.g. 20 or 30M?
Kind regards,
Gerard

[Developer Discussion] JB Rom Creation

Hi All,
I'm starting this thread so that we can compile in one location the methods we attempted to create a zip for the recent Jellybean update, and hopefully advance the creation of this rom. This should be mentioned before starting.
ONLY POST IF YOU HAVE RELEVENT INFORMATION REGARDING THIS JELLYBEAN ROM.
This Includes:
Procedures
Logcats
Test Builds
Helpful Suggestions (Be Specific)
To start, I've attempted the following alterations on the zip level:
Straight System dump with updated updater-script
System dump with default updater script
Modified updater script removing patch elements
Utilizing the Canadian Rom, which flashed and appplying new system.
Swapping out radio flashing and boot.img with shellnutt's boot.img
I also have the following plans:
System Dump on Canadian Rom, and default boot.img
Recursive Deleting of patched files
Example
Code:
assert(apply_patch_check("/system/3rd_party/videowiz/lib/libMvMMAS.so", "65cfe8efc36cf58669e5fb9f30274bc49c3f9703", "e1a051bb2562af8d9b106ef4b875f85a6109ee9e"));
set_progress(0.003080);
delete("/system/3rd_party/videowiz/lib/libMvMMAS.so");
Than initiate the normal package_extract_dir("system", "/system");
Any other information would be great. Some developers have gotten it to flash but not boot.
Also, here's a link to the test builds I released.
http://goo.im/devs/AdriVelazquez/Roms/Nightlies/TestSprint
Thanks to all the developers that have been working on it.

This is what I've tried:
Used the boot.img & system.img. from dump to compile a rom in dxsdia's kitchen. I was able to apply root to the boot.img and compiled a zip but it wont flash. I then added the updater script from the dump but it still wouldn' t flash. Ithink my problem is in the updater script. I didn't take thetime to configure the kitchen properly for the optimus G but will do so tonight. I have the 2 test zips at home and I'll post them tonight if anyone wants to take a look.

Suggestion:
Since houstonns Korean port boots, and all is well except radio, would it also help to look at that system dump along with the Canadian? Maybe something to utilize?

johnq54 said:
Suggestion:
Since houstonns Korean port boots, and all is well except radio, would it also help to look at that system dump along with the Canadian? Maybe something to utilize?
Click to expand...
Click to collapse
I already tried that. That was the test zip I did last night.
Sent from my LG-LS970 using xda premium

I also tried both mentioned here, none worked for me as well. I contacted couple of friends to help us out, Scott (Scrossler cleanrom series) already answer me back, he's looking into it, I will let u guys know if they get something working.
Edit: houston answer as well, he is gonna work on it as well.
LROD'S OPTIMUS G

As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.

dastin1015 said:
As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.
Click to expand...
Click to collapse
There is no /proc/emmc on my phone, but I've attached what I have in /proc/mounts in case that helps.

grktaurus83 said:
There is no /proc/emmc on my phone, but I've attached what I have in /proc/mounts in case that helps.
Click to expand...
Click to collapse
This is what I was looking for. Thanks!

dastin1015 said:
As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.
Click to expand...
Click to collapse
Please, for safety, only use the by-name mount points. Below are the partitions for the American and Candian variants.
http://pastebin.com/Rej3FgQS

Shelnutt2 said:
Please, for safety, only use the by-name mount points. Below are the partitions for the American and Candian variants.
http://pastebin.com/Rej3FgQS
Click to expand...
Click to collapse
I'm using the by-name mount points. Wasn't sure if the Optimus G was proc/emmc or not.

Thanks dastin for answering and thanks guys for getting what he needs to help us.
LROD'S OPTIMUS G

do we have any logcats?

dastin1015 said:
I'm using the by-name mount points. Wasn't sure if the Optimus G was proc/emmc or not.
Click to expand...
Click to collapse
A bit late but might still be helpful to others. Here is a pastie of the by-name goodness as clear as a bell. This is the Sprint varaint
http://pastebin.com/teQmXDX9

If anyone needs anything from the stock JB ROM let me know. I am running it and can provide any files or anything.

_Epic said:
If anyone needs anything from the stock JB ROM let me know. I am running it and can provide any files or anything.
Click to expand...
Click to collapse
Same here
Sent from my LG-LS970 using xda premium

Veritass said:
Same here
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
can either of you post the build.prop? I won't be updating.

interloper said:
can either of you post the build.prop? I won't be updating.
Click to expand...
Click to collapse
How's this?
http://pastebin.com/yjNnR2sh
Sent from my LG-LS970 using xda premium

interloper said:
can either of you post the build.prop? I won't be updating.
Click to expand...
Click to collapse
Here's the build.prop
http://pastebin.com/UXSBvNMj
Provided by epic since I haven't done the update also.
Sent from my LG-LS970 using xda premium

I sent Adriel build.prop file but forgot I could copy text and post to pastebin. That's why we both posted. Lol.
Sent from my LG-LS970 using xda premium

Good morning to all, We have another dev, his name is negamann303 from the evo 3d forum, he's working hard on our project, already send me stuff to test, we will not post anything because these zips are highly flammable and all the testing is done in a spare phone I have, I will keep u guys updated.
LROD'S OPTIMUS G

[DEV] (UPDATED)dsixda Unoffical Kitchen Support & Mounting Points(Linux Only)

EDIT: do not convert updater to update script. Your rom will not boot. When asked decline.
Update: now supports T-Mobile, AT&T and Sprint Models Enjoy!
*This is just a quick fix mod to bring support to the dsixda's android kitchen
*This for new users that would like to edit their favorite rom
*I did not make this software all i did was simply extracted the stock recovery.img and added support for our device.
Credits to the kitchen be longs to dsixda and the orginal thread here: http://forum.xda-developers.com/showthread.php?t=633246
MOUNTING POINTS:
/boot emmc /dev/block/mmcblk0p20
/system ext4 /dev/block/mmcblk0p16
/data ext4 /dev/block/mmcblk0p29
/cache ext4 /dev/block/mmcblk0p18
/recovery emmc /dev/block/mmcblk0p21
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

VIIRU§ said:
*This is just a quick fix mod to bring support to the dsixda's android kitchen
*This for new users that would like to edit their favorite rom
*I did not make this software all i did was simply extracted the stock recovery.img and added support for our device.
Credits to the kitchen be longs to dsixda and the orginal thread here: http://forum.xda-developers.com/showthread.php?t=633246
You can get the edited kitchen that supports our device here: https://www.dropbox.com/s/yytrca4l72khtrw/Android-Kitchen-0.223_MODDED.tar.gz
MOUNTING POINTS:
/boot emmc /dev/block/mmcblk0p20
/system ext4 /dev/block/mmcblk0p16
/data ext4 /dev/block/mmcblk0p29
/cache ext4 /dev/block/mmcblk0p18
/recovery emmc /dev/block/mmcblk0p21
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Click to expand...
Click to collapse
Might want to add the model_variants too

Posting this here, as well. Just in case someone finds it useful.
You can get Heimdall 1.4 for Win32 here:
https://bitbucket.org/benjamin_dobell/heimdall/downloads/heimdall-suite-1.4.0-win32.zip
Just wiped and returned to a completely virgin MDL install on my device. Then used Heimdall to grab the PIT file. You can download the file here:
https://dl.dropboxusercontent.com/u/21231693/gs4.pit
I then used the Heimdall to print the PIT information which you can download here:
https://dl.dropboxusercontent.com/u/21231693/gs4PIT_info.txt

Mr Impossible said:
Might want to add the model_variants too
Click to expand...
Click to collapse
I only added support for The T-Mobile GS4 not any other variants of the Galaxy S4
Sent from my SGH-M919 using xda premium

VIIRU§ said:
*This is just a quick fix mod to bring support to the dsixda's android kitchen
*This for new users that would like to edit their favorite rom
*I did not make this software all i did was simply extracted the stock recovery.img and added support for our device.
Credits to the kitchen be longs to dsixda and the orginal thread here: http://forum.xda-developers.com/showthread.php?t=633246
You can get the edited kitchen that supports our device here: https://www.dropbox.com/s/yytrca4l72khtrw/Android-Kitchen-0.223_MODDED.tar.gz
MOUNTING POINTS:
/boot emmc /dev/block/mmcblk0p20
/system ext4 /dev/block/mmcblk0p16
/data ext4 /dev/block/mmcblk0p29
/cache ext4 /dev/block/mmcblk0p18
/recovery emmc /dev/block/mmcblk0p21
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Click to expand...
Click to collapse
How did you get the mount points? I have a Sprint GS4 and I have spent several hours trying to pull the mount points so I can add Kitchen support for the Sprint GS4 but have been unsuccessful.
I have tried cat /proc/mounts from adb shell and it doesn't return what I would expect. I have also looked at the .FSTAB file in system/ect and am unsure how to interpret it to get mount points in a form like you have listed.
Any help would be greatly appreciated.

Landon4444 said:
How did you get the mount points? I have a Sprint GS4 and I have spent several hours trying to pull the mount points so I can add Kitchen support for the Sprint GS4 but have been unsuccessful.
I have tried cat /proc/mounts from adb shell and it doesn't return what I would expect. I have also looked at the .FSTAB file in system/ect and am unsure how to interpret it to get mount points in a form like you have listed.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I pulled if from the stock recovery image... thats how I do it. I can add support for your device too if u like
Sent from my SGH-M919 using xda premium

VIIRU§ said:
I pulled if from the stock recovery image... thats how I do it. I can add support for your device too if u like
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
That would be awesome. If you wouldn't mind could you teach me how to pull it myself from the stock recovery? I am trying to do as much as I can to learn but I have hit a wall on this one.

Landon4444 said:
That would be awesome. If you wouldn't mind could you teach me how to pull it myself from the stock recovery? I am trying to do as much as I can to learn but I have hit a wall on this one.
Click to expand...
Click to collapse
I know 2 different ways to do this the manually way and the lazy. And I myself much rather use option 2. Lol.... so do u have ubuntu and your build environment setup?
Sent from my SGH-M919 using xda premium

VIIRU§ said:
I know 2 different ways to do this the manually way and the lazy. And I myself much rather use option 2. Lol.... so do u have ubuntu and your build environment setup?
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
I really appreciate you taking the time to help me with this. I do have Ubuntu and my build environment set up as described in some of the guides on XDA.

Landon4444 said:
I really appreciate you taking the time to help me with this. I do have Ubuntu and my build environment set up as described in some of the guides on XDA.
Click to expand...
Click to collapse
Okay download a sprint GS4 rom and a AT&T GS4 and pull the build.prop from both and upload them and send me the link.
Sent from my SGH-M919 using xda premium

VIIRU§ said:
Okay download a sprint GS4 rom and a AT&T GS4 and pull the build.prop from both and upload them and send me the link.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
I just sent you a PM with a Google drive link to the Sprint and ATT build.prop files.
I also followed a procedure to extract the recovery.img using an advanced option in the kitchen in an effort to get the mount points from the recovery.fstab file which did not give me what I was hoping for. I have also put the recovery.fstab file on google drive.

Landon4444 said:
I just sent you a PM with a Google drive link to the Sprint and ATT build.prop files.
I also followed a procedure to extract the recovery.img using an advanced option in the kitchen in an effort to get the mount points from the recovery.fstab file which did not give me what I was hoping for. I have also put the recovery.fstab file on google drive.
Click to expand...
Click to collapse
That's wat u need to get the mount points from recovery.fstab of the device u want to add support for. Im not sure why u getting that error if you pulled that from jfltespr recovery.img but no worries I added support sprint and att version....
Sent from my SGH-M919 using xda premium

VIIRU§ said:
That's wat u need to get the mount points from recovery.fstab of the device u want to add support for. Im not sure why u getting that error if you pulled that from jfltespr recovery.img but no worries I added support sprint and att version....
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
Thanks. I guess my recovery.fstab file should not have come out like that?

Landon4444 said:
Thanks. I guess my recovery.fstab file should not have come out like that?
Click to expand...
Click to collapse
Lol no... and your welcome...
Sent from my SGH-M919 using xda premium

VIIRU§ said:
Update: now supports T-Mobile, AT&T and Sprint Models Enjoy!
*This is just a quick fix mod to bring support to the dsixda's android kitchen
*This for new users that would like to edit their favorite rom
*I did not make this software all i did was simply extracted the stock recovery.img and added support for our device.
Credits to the kitchen be longs to dsixda and the orginal thread here: http://forum.xda-developers.com/showthread.php?t=633246
Download: https://www.dropbox.com/s/fg4kb1eor5di4bn/Android-Kitchen-0.223_rev2.tar.gz
MOUNTING POINTS:
/boot emmc /dev/block/mmcblk0p20
/system ext4 /dev/block/mmcblk0p16
/data ext4 /dev/block/mmcblk0p29
/cache ext4 /dev/block/mmcblk0p18
/recovery emmc /dev/block/mmcblk0p21
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Click to expand...
Click to collapse
You tested?
Enviado desde mi SGH-I337M usando Tapatalk 2

So did you get it working?
I had already updated the kitchen with necessary files for AT&T, Rogers/Bell/Telus, T-Mobile and I9505 as well as various other script files that needed changing. However, it gets stuck at boot screen.
https://github.com/dsixda/Android-Kitchen/tags
My discussion here:
http://forum.xda-developers.com/showthread.php?t=2283070
EDIT: Please don't distribute entire versions of my kitchen that have been modified and passed off as a particular version number. Only submit individual files.

There's no need to test the points are just the same as our only a minor edit was need im 99.999% sure it will work all USA versions stated in the op
Sent from my SGH-M919 using xda premium

dsixda said:
So did you get it working?
I had already updated the kitchen with necessary files for AT&T, Rogers/Bell/Telus, T-Mobile and I9505 as well as various other script files that needed changing. However, it gets stuck at boot screen.
https://github.com/dsixda/Android-Kitchen/tags
My discussion here:
http://forum.xda-developers.com/showthread.php?t=2283070
EDIT: Please don't distribute entire versions of my kitchen that have been modified and passed off as a particular version number. Only submit individual files.
Click to expand...
Click to collapse
Yea it's working. I edited a rom on my tmo version and my cousin's AT&T version. This was never intended to as a distribution of your work. Nor have I ever taken credit for if. In fact I'd much rather you test it and update the official thread.
No credit needed I just figured you was retired like you thread started so I added support to meet the needs of my own laziness. I was talking to a new kernel dev and told him he couldn't use the kitchen to split boot.imgs faster. So I posted thinking others here might want it. Then a sprint user wanted help abd about 15 AT&T user PM me for support and well here it is lol. Thats the story feel free to take over from here....
Sent from my SGH-M919 using xda premium

Awesome, great work!
Can you post an updater-script from these files, so that I can compare? Thanks.

dsixda said:
Awesome, great work!
Can you post an updater-script from these files, so that I can compare? Thanks.
Click to expand...
Click to collapse
Looks like their is an error in converting the updater to an update I didn't catch it cause I always manually edit my updater. I'm checking your verify_update_ script. Then its converting to an update the script is reporting part of the updater that it should not be...
EDIT: it's also rewriting the script as
format("ext4", "EMMC", "/dev/block/mmcblk0p16");
mount("ext4", "EMMC", "/dev/block/mmcblk0p16", "/system"); "0 /system/
instead of
format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p16", "/system");

[DEV] [MOD] Repartitioning

http://forum.xda-developers.com/showthread.php?t=1388996
Has anyone thought of doing this?
Edit: compiling parted is harder then i thought !!
I will work on getting parted built for our Nexus 9
Because Parted 1.8.8.1.179-aef3 does not work on our Nexus 9
Note: will update this thread with a lot more info
When I get it working.
Note: if I got it built
I will test this on my Nexus 7 first. if everything goes well
Then I will do this on my Nexus 9
http://www.gnu.org/software/parted/
XDA:DevDB Information
Repartition Test, ROM for the Nexus 9
Contributors
USBhost
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2015-11-06
Last Updated 2015-11-06

Reserved 1

Reserved 2

USBhost said:
http://forum.xda-developers.com/showthread.php?t=1388996
Has anyone thought of doing this?
Edit: compiling parted is harder then i thought !!
I will work on getting parted built for our Nexus 9
Because Parted 1.8.8.1.179-aef3 does not work on our Nexus 9
Note: will update this thread with a lot more info
When I get it working.
Note: if I got it built
I will test this on my Nexus 7 first. if everything goes well
Then I will do this on my Nexus 9
http://www.gnu.org/software/parted/
Click to expand...
Click to collapse
I think in nexus 9 , repartitioning is not required as apps are installed in internal storage and no limit is there.. :what:

Ishwara Sandesh C M said:
I think in nexus 9 , repartitioning is not required as apps are installed in internal storage and no limit is there.. :what:
Click to expand...
Click to collapse
Well I was thinking of making
system smaller by 1g
and making data bigger by 1g

USBhost said:
Well I was thinking of making
system smaller by 1g
and making data bigger by 1g
Click to expand...
Click to collapse
Nice :thumbup:
Sent from my Nexus 9 using XDA Free mobile app

USBhost said:
Well I was thinking of making
system smaller by 1g
and making data bigger by 1g
Click to expand...
Click to collapse
Yes! This is exactly what I was looking for!
I commented about this somewhere I remember. Seems like I have way more space in my system than I need.

wifesabitch said:
Yes! This is exactly what I was looking for!
I commented about this somewhere I remember. Seems like I have way more space in my system than I need.
Click to expand...
Click to collapse
Lets hope that in can compile it

Wow cool! Gl!

Ishwara Sandesh C M said:
I think in nexus 9 , repartitioning is not required as apps are installed in internal storage and no limit is there.. :what:
Click to expand...
Click to collapse
There is even more utility for purpose of dualbooting a more conventional linux distro.
I.e., add a menu-driven multi-boot bootloader to the start of the boot partition, allow to select either a conventional android boot, or a <pick your favorite linux flavor> boot, which of course, loads a different kernel, and a different base filesystem. It is conceivable to share the userdata partition, i.e. /data/media for regular linux userdata and sharing data between android and another distro, but it would be helpful to set a couple of GB aside for the system data.

You're a brave soul @USBhost. Btw, you look good in green! Congrats
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
You're a brave soul @USBhost. Btw, you look good in green! Congrats
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks!!
Compiling parted is hard! !

USBhost said:
http://forum.xda-developers.com/showthread.php?t=1388996
Has anyone thought of doing this?
Edit: compiling parted is harder then i thought !!
I will work on getting parted built for our Nexus 9
Because Parted 1.8.8.1.179-aef3 does not work on our Nexus 9
Note: will update this thread with a lot more info
When I get it working.
Note: if I got it built
I will test this on my Nexus 7 first. if everything goes well
Then I will do this on my Nexus 9
http://www.gnu.org/software/parted/
Click to expand...
Click to collapse
This approach requires you to be S-OFF & modify your bootloader - this also requires a modified kernel.
I have been using another less invasive approach successfully since ~3 years (even posted about it somewhere on xda); I'm basically using the system partitions (userdata, cache, system) as separate LVM volumes.
You can even have encryption!
You just need a LVM binary (and cryptsetup if you need encryption - automatic decrypting if you have the key as OTG) and a slightly modified boot.img (along with the recovery if you want to avoid manual work):
Obviously, you need to modify the fstab to point to the /dev/mapper paths as well as the LVM initialising part as service at the top of your init.rc

adwinp said:
This approach requires you to be S-OFF & modify your bootloader - this also requires a modified kernel.
I have been using another less invasive approach successfully since ~3 years (even posted about it somewhere on xda); I'm basically using the system partitions (userdata, cache, system) as separate LVM volumes.
You can even have encryption!
You just need a LVM binary (and cryptsetup if you need encryption - automatic decrypting if you have the key as OTG) and a slightly modified boot.img (along with the recovery if you want to avoid manual work):
Obviously, you need to modify the fstab to point to the /dev/mapper paths as well as the LVM initialising part as service at the top of your init.rc
Click to expand...
Click to collapse
This this a nexus
So S-OFF is not needed
And I don't think you need to modify the bootloader
P.S.
Can any one help me compile parted
So far no luck

USBhost said:
This this a nexus
So S-OFF is not needed
And I don't think you need to modify the bootloader
P.S.
Can any one help me compile parted
So far no luck
Click to expand...
Click to collapse
1: you could use the fdisk builtin busybox binaries
2: you could use sgdisk instead fdisk/sgdisk. There are even some on xda: http://forum.xda-developers.com/showthread.php?t=1605535
3: here are some busybox (along with a variant compiled against glibc instead of bionic), LVM, & cryptsetup binaries: https://drive.google.com/file/d/0B8rpJsF4EG0Yb2FWT3liOTRucnM

Any progress with this? That 2.5GB System partition is overkill. Would definitely transfer 1GB of that to my Data partition.