Develop Bugs

Possibly speed up some ROM's with these tweaks (only works with non-BFS kernels)

I reported a couple of kernel tweaks I came across on the web the other day but there has been no response yet so I thought I'd start a new thread to catch peoples attention!
The tweaks are for non-BFS kernels only (e.g. Flykernel 10a) and alter a couple of the parameters within the scheduler. I dont know enough about linux kernels to give more details but I was hoping someone who did know more would explain what the parameters do.
After applying the tweaks my phone is the smoothest I have ever felt it be and subsequently I have returned to 528MHz. Even now it feels smoother than I have had it on any other ROM when OC'ing > 600MHz. This means my battery life has seriously increased too. My phone has been running 26 hrs with email and weather updates with still 66% left.
I am currently using elelinux 1.8 and flykernel 10a @ 528MHz and I honeslty dont feel the need to flash any ROM updates anymore (yet!). The tweaks are:
EDIT: Due to some confusion I would like to make it clear in the following commands DO NOT type the '#' or '$' symbols. These are just to indicate what the terminal shows.
from ./adb shell or terminal emulator on phone
$ su
# mount -o remount,rw /system
# echo 'kernel.sched_latency_ns = 600000' >> /etc/sysctl.conf
# echo 'kernel.sched_min_granularity_ns = 400000' >> /etc/sysctl.conf
# echo 'kernel.sched_features = 24188' >> /etc/sysctl.conf
# mount -o remount,ro /system
# sysctl -p
(the following should print after typing previous command)
kernel.sched_latency_ns = 600000
kernel.sched_min_granularity_ns = 400000
kernel.sched_features = 24188
# exit
$ exit
Try them and see if it makes your phone smoother. Im sure they will. and if they dont then just delete the sysctl.conf file and you should return to normal on next boot.
EDIT2: Ok so it has become apparent that the tweaks to dont speed up ALL ROMS as the title suggests. I apologise for this over big-uppery. I think the main reason for this is that some devs have already incorporated similar tweaks (cronos?). Also erasmux has been playing around with the tweaks and he has suggested that not all the tweaks have a significant effect on performance. Of course you are all welcome to play around too and find whats suits you best. As for me, im going to leave the tweaks in because for the first time since buying my hero i am pleased with its performance and I dont see the point in removing a couple of lines from a file if it makes no difference!
Also, it is worth noting that there may be some down side to these tweaks as pointed out by Decad3nce on page 5 (post #44) in that apps requiring constant cpu time such as gps may become jumpy. I havent noticed any ill-effects yet but then I havent been on any long drives with sat-nav either so I dont know. (if you have already got yourself seriously lost or missed some meeting I apologise).
If after reading all this you still want the tweaks either follow the instructions above or flash the updated kernel elelinux was kind enough to compile (page 3) or there is another link on page 4/5 i think
Now if C0mpu13rFr34k would hurry up and finish that theme my hero may well be perfect!

Oh wow Thanks i will try this now also does this affact the bechmark scores in anyway ill report if does

A-MA-ZING, wow it's so smoother ! it work so fine !

haha how you get that done so fast im still typing
Edit: Grrrrrr..!!!!!!! Terminal crashed when typing this owell try again

I've not benchmarked it since applying tweaks but I don't think this will change benchmarks. It just improves the 'interactivity' which is all I want to do. Benchmarks are just numbers!
Sent from my HTC Hero using XDA App

ah okay thanks
Edit: just done and rebooted first impresions WOW Thanks alot realy smoothed things up a bit becnch marks are around the same (5.2)mflops for me

too bad im using bfs kernel...

orangeclanz said:
too bad im using bfs kernel...
Click to expand...
Click to collapse
Just flash non-BFS and try it. It will be worth it. If you don't like flash back!
Sent from my HTC Hero using XDA App

it is smoother : )
thanks!
Floyo 0.8

will it work with the official kernel that i got with my hero? 2.1.

liorweitz said:
will it work with the official kernel that i got with my hero? 2.1.
Click to expand...
Click to collapse
As far as I know it will work. Though I think you will need root to write a file to the /system directory.
Sent from my HTC Hero using XDA App

Anyone tried adding this to one of the init.d scripts and seeing if it helps speed?
You will need root to use most of these, as they are setting kernel params, and IIRC that requires root.

Doesn't the .config file cause the settings to be applied at startup?
Sent from my HTC Hero using XDA App

f_padia said:
Doesn't the .config file cause the settings to be applied at startup?
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Yes, if you compiled a kernel using these tweaks in .config, then they would be applied at startup by default. This would just let people test it out and see if they wanted to compile using these settings for good, as I imagine they will.

doesn't work at me 3x error
# sysctl -p - says short write - im not sure if is this normal
kernel.sched_latency_ns = 600000 - not found
kernel.sched_min_granularity_ns = 400000 - - not found
kernel.sched_features = 24188 - - not found

BuzzyFuzzy said:
doesn't work at me 3x error
# sysctl -p - says short write - im not sure if is this normal
kernel.sched_latency_ns = 600000 - not found
kernel.sched_min_granularity_ns = 400000 - - not found
kernel.sched_features = 24188 - - not found
Click to expand...
Click to collapse
Are you definitely on a non-BFS kernel? I think this is an issue if you have a BFS kernel.
Sent from my HTC Hero using XDA App

f_padia said:
Are you definitely on a non-BFS kernel? I think this is an issue if you have a BFS kernel.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
yes, FlyKernel-10a

can someone copy the code in to a post here? so I could just copy paste into CMD, beacuse I really not very good with that stuff.
Thanks,
Idan.

BuzzyFuzzy said:
doesn't work at me 3x error
# sysctl -p - says short write - im not sure if is this normal
kernel.sched_latency_ns = 600000 - not found
kernel.sched_min_granularity_ns = 400000 - - not found
kernel.sched_features = 24188 - - not found
Click to expand...
Click to collapse
hmm im not too sure to be honest. If you followed the instructions as I listed them I dont think you should have the problem. It seems as though the commands werent written to the sysctl.conf file. Again im not really very good at programming so I cant give you much more help. sorry
idanfima said:
can someone copy the code in to a post here? so I could just copy paste into CMD, beacuse I really not very good with that stuff.
Thanks,
Idan.
Click to expand...
Click to collapse
If you have the Android SDK then go to the tools folder in a command prompt (or terminal in linux) and run:
adb remount (./adb remount)
adb shell
then the following: (if you go straight through the terminal emulator in your phone dont run the above 2 commands)
$ su
# mount -o remount,rw /system
# echo 'kernel.sched_latency_ns = 600000' >> /etc/sysctl.conf
# echo 'kernel.sched_min_granularity_ns = 400000' >> /etc/sysctl.conf
# echo 'kernel.sched_features = 24188' >> /etc/sysctl.conf
# mount -o remount,ro /system
# sysctl -p
(if your above commands worked it should print:
kernel.sched_latency_ns = 600000
kernel.sched_min_granularity_ns = 400000
kernel.sched_features = 24188)
# exit
$ exit
and you should be done.

if i have a recovery image but not SU apk, can i still do it?

[MOD] Youtube 'Gingerbread' ported to Eclair

Hiya,
due to my brother not having the luck of having Froyo on his phone I took a look at it and hacked the newst YouTube app to work with Eclair. I had to remove two calls and add android.util.base64 which was introduced with Froyo. However, it should work flawlessly. If you encounter any problems, feel free to post here along with a little description and if possible a logcat dump of the exception.
Download:
http://ul.to/emt639
Old Download:
- http://ul.to/kxu37d
- http://www.mediafire.com/?5bdc88opu6qt9nz
You have to remove the default YouTube app before you can install this one over.
Using ADB Shell this should just work:
adb remount
adb shell rm system/app/YouTube.apk
adb uninstall com.google.android.youtube
then you can just install it over using the package manager or with adb (adb install YouTube_signed.apk).
Hope this helps, enjoy the re-designed Youtube app!

rolle3k said:
Hiya,
due to my brother not having the luck of having Froyo on his phone I took a look at it and hacked the newst YouTube app to work with Eclair. I had to remove two calls and add android.util.base64 which was introduced with Froyo. However, it should work flawlessly. If you encounter any problems, feel free to post here along with a little description and if possible a logcat dump of the exception.
Download:
- http://ul.to/kxu37d
- http://www.mediafire.com/?5bdc88opu6qt9nz
You have to remove the default YouTube app before you can install this one over.
Using ADB Shell this should just work:
adb remount
adb shell rm system/app/YouTube.apk
adb uninstall com.google.android.youtube
then you can just install it over using the package manager or with adb (adb install YouTube_signed.apk).
Hope this helps, enjoy the re-designed Youtube app!
Click to expand...
Click to collapse
So is this the Eclair or Froyo Version?

wow, thanks this works perfectly. i used root explorer to push the file. thanks again

So this is Froyo's youtube app made to work with Eclair ??
Why does the title say gingerbread ??

PhoenixFx said:
So this is Froyo's youtube app made to work with Eclair ??
Why does the title say gingerbread ??
Click to expand...
Click to collapse
"[MOD] Youtube 'Gingerbread' ported to Eclair"
In layman terms, its the youtube app from gingerbread ported to eclair

Daneshm90 said:
"[MOD] Youtube 'Gingerbread' ported to Eclair"
In layman terms, its the youtube app from gingerbread ported to eclair
Click to expand...
Click to collapse
I know what a mod and a port means ..
Just that OP's post is confusing, he is trying to help his brother who doesn't have Froyo, hence I assumed he is trying to port the latest version (which I thought Foryo's youtube app) to eclair.
EDIT : Just realized that the new Youtube app on the market is claimed by some sites as a Gingerbread youtube app. (and its only available for 2.2) .. ok now it makes sense.

Works fine, thank you.
After you sign in to see your uploads, after exiting the app it doesn't run any more (force close).

PhoenixFx said:
I know what a mod and a port means ..
Just that OP's post is confusing, he is trying to help his brother who doesn't have Froyo, hence I assumed he is trying to port the latest version (which I thought Foryo's youtube app) to eclair.
EDIT : Just realized that the new Youtube app on the market is claimed by some sites as a Gingerbread youtube app. (and its only available for 2.2) .. ok now it makes sense.
Click to expand...
Click to collapse
Does it matter just say thanks and stop being clever.
Sent from my GT-I9000 using XDA App

Good work man. Hope this gets pushed on to all eclair custom roms
Sent from my GT-I9000 using Tapatalk

Fixed a API call that requires Froyo
http://ul.to/emt639

works great on my vibrant.

Just an FYI I only needed to delete the original YouTube.apk and replace with the posted Froyo version in the system/app directory.

Nice work, useful when samsung are being bums upgrading the SGS to 2.2
torres76 said:
Does it matter just say thanks and stop being clever.
Click to expand...
Click to collapse
If he didn't look it up most of us wouldn't have understood what the title exactly meant. Yes it matters as some people want to know what they're installing and what different versions mean.
Sent from my GT-I9000 using XDA App

hi guys. When i type adb remount one the cmd it said no such file or directory

lelf said:
hi guys. When i type adb remount one the cmd it said no such file or directory
Click to expand...
Click to collapse
Yeah.. Here too.. Maybe this has something to do with recovery?
Solved it this way:
Code:
$ su
su
# mount -o rw,remount -t rfs /dev/block/stl9 /system
mount -o rw,remount -t rfs /dev/block/stl9 /system
# rm system/app/YouTube.apk
rm system/app/YouTube.apk
# exit
exit
adb uninstall com.google.android.youtube
adb install signed_YouTube.apk

Congrats roll23k, your mod has made it to all the android news sites and even Reddit!.
Sent from my GT-I9000 using Tapatalk

Latest Youtube app update is out, would you be updating this port?

Which version has this "gingerbread" youtube app??
And after installation there is no opportunity to keep it up to date by the market, am I right?

[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?

[Q] Dim capacitive buttons on cm10 roms

Hi all,
After 3 days of searching, I still can't find a init.d script that dims the capacitive buttons of my One X in a cm10 rom.
I found it for sense roms but not for jellybean aosp cm10
Could someone please help me?
Thanks in advance

No one have an idea?

Tabtoub said:
No one have an idea?
Click to expand...
Click to collapse
Hmm, try to modify the stuff I have in my signature. No idea it will work, I use this only to shut them off. I hate them.
try to use something else as the 0 in the init.d
echo 0 > /sys/class/leds/button-backlight/brightness
chmod 444 /sys/class/leds/button-backlight/brightness
the chmod is for disabling access to the file after you change the value

[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");