Related
Many of you seem to think that you have been abandonded by the developers moving to the GT-I9100, I do not think this is the case, but you have to remember that developing for a new phone is more fun
Anyway, some of you will already know about my insecure kernels for the GT-I9100, well since Gingerbread on the GT-I9000 I have also been using insecure kernels for my own personal use and have now decided to release them, since if you are like me and like to keep your phone as close to stock as possible they may be of some use to you.
If you like my work, maybe you would like to say thanks by buying me a beer
Insecure Kernels:-
GT-I9000_XWJVZ_insecure
GT-I9000_XWJW1_insecure
GT-I9000_XXJVP_insecure
GT-I9000_XXJVQ_insecure
GT-I9000_XXJVR_insecure
GT-I9000_XXJVS_insecure
GT-I9000_XXJVT_insecure
GT-I9000_XXJVU_insecure
GT-I9000_XXJW4_insecure
password = [email protected]
a quick method for rooting would be:-
Code:
adb remount
adb push busybox /system/xbin/
adb push su /system/xbin/
adb shell chown root.shell /system/xbin/busybox
adb shell chown root.shell /system/xbin/su
adb shell chmod 755 /system/xbin/busybox
adb shell chmod 4755 /system/xbin/su
adb shell /system/xbin/busybox --install -s /system/xbin
You need to make sure that busybox and su are in the same folder as you are typing the adb commands.
You could also push superuser.apk if you have it local:-
adb install superuser.apk
You can use these files to return to the stock kernel if you wish, you will still be rooted but adb will not be running as root on first login via shell.
Original Kernels:-
GT-I9000_XWJVZ_original
GT-I9000_XWJW1_original
GT-I9000_XXJVP_original
GT-I9000_XXJVQ_original
GT-I9000_XXJVR_original
GT-I9000_XXJVS_original
GT-I9000_XXJVT_original
GT-I9000_XXJVU_original
GT-I9000_XXJW4_original
Please DO NOT mirror any of my files, thank you.
I have used your 9100 insecure. Good work. I have also rated this thread a 5-star.
link to github repo for kernel source (most preferrably ^^) please !
what all did you change ?
thanks !
good work
10 chars
On JVS insecure kernel my WiFi connection keeps restarting when it's turned on, can you check it?
Bo$s said:
On JVS insecure kernel my WiFi connection keeps restarting when it's turned on, can you check it?
Click to expand...
Click to collapse
Mine is ok, maybe a bug in JVS makes an incompatibilty problem with your router? Try to flash the JVS original kernel and see if the problem still exists, you will still keep root.
Odia said:
Mine is ok, maybe a bug in JVS makes an incompatibilty problem with your router? Try to flash the JVS original kernel and see if the problem still exists, you will still keep root.
Click to expand...
Click to collapse
Same behavior on stock
Do i understand this correct?? From what i read u are using the kernel u use on your i9100 also on the i9000??? how is this possible?
Gvdn said:
Do i understand this correct?? From what i read u are using the kernel u use on your i9100 also on the i9000??? how is this possible?
Click to expand...
Click to collapse
No, he means that he has done the same work as on I9100.....
The kernels are not compatible!
simone201 said:
No, he means that he has done the same work as on I9100.....
The kernels are not compatible!
Click to expand...
Click to collapse
Lol ty was really going "WHAAAAAAAAT" when i read the OP. Maybe make it cleaer what u mean in the OP.
zacharias.maladroit said:
link to github repo for kernel source (most preferrably ^^) please !
what all did you change ?
thanks !
Click to expand...
Click to collapse
As you probably know, this is not only zach asking kindly or xda-rules. GPL licence, on which android kernel is based, clearly states to release updated source along with the build.
Developers are always welcome when they follow this. Bet you get help here to setup github.
Failing to comply usually ends in some banned/thread locked.
Sent from my GT-I9000 using XDA App
O-T said:
As you probably know, this is not only zach asking kindly or xda-rules. GPL licence, on which android kernel is based, clearly states to release updated source along with the build.
Developers are always welcome when they follow this. Bet you get help here to setup github.
Failing to comply usually ends in some banned/thread locked.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I hope he releases the sources soon....but it is also veeery simple to do an unsecured kernel!
Thanx works fine on JVS, but i needed to remove some stuff from /system/app
No space left....
Brotuck said:
Thanx works fine on JVS, but i needed to remove some stuff from /system/app
No space left....
Click to expand...
Click to collapse
Seems that JVR and JVS have no space left at all in /system folder...strange thing....
could you provide some link can opened in your country.
O-T said:
As you probably know, this is not only zach asking kindly or xda-rules. GPL licence, on which android kernel is based, clearly states to release updated source along with the build.
Developers are always welcome when they follow this. Bet you get help here to setup github.
Failing to comply usually ends in some banned/thread locked.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
The kernel is not compiled from sources, its only a 4 byte change which is injected to the stock kernel. That is the reason there is no source released, the Admins and Mods know this already and the reason this thread is still here alive and not locked.
and its the reason it works correctly with XXJVS.
Bo$s said:
Same behavior on stock
Click to expand...
Click to collapse
Thats bad, which router are you using? Have you tried rebooting the router?
simone201 said:
Seems that JVR and JVS have no space left at all in /system folder...strange thing....
Click to expand...
Click to collapse
Its true, I just remove the Aldiko eBook Reader from /system/app but of cause you can chose some other app you dont like
Gvdn said:
Do i understand this correct?? From what i read u are using the kernel u use on your i9100 also on the i9000??? how is this possible?
Click to expand...
Click to collapse
Sorry for the confusion, I hope the OP is now more clear.
Odia: Thank you for explaining your [KERNEL/MOD]
The kind-of-source is your HowTo in OP on how we can mod any kernel.
Sent from my GT-I9000 using XDA App
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?
Hello guys i'm very happy to share with you this...BRAVIA ENGINE! Enjoy
I tell about this: video
IT's A Post-Processing Engine, so you can view the improvements only on your phone's screen...enjoy new quality!
1) GUIDE for Manual Installation on each Rom! (2.2 & 2.3)
-Download BraviaE Files Pack: HERE
-Extract files on phone and put they in the directory:
Code:
[B]/system/etc[/B]
-Open /system/build.prop with a text editor (like RootExplorer)
and add these lines at the end:
Code:
#Additional Tweaks by XxXPachaXxX
#Bravia Engine Service
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
-Then, Save the file and Exit
-Now, set the right permissions or open a terminal emulator and execute:
Code:
su
busybox chmod 0755 /system/etc/be_photo
busybox chmod 0755 /system/etc/be_movie
busybox chown 0.0 /system/etc/be_photo
busybox chown 0.0 /system/etc/be_movie
-Fully Reboot the device and enjoy BRAVIA
DOWNLOADS:::INFO:::SUPPORT
hi, I had tried but when I write on emulator "busybox chmod 0755 /system/etc/be_photo
" it replies to me "Busybox permission denied"!
which ROM is supported??
It's supposed to work only when viewing photos/vids?
If so, it seems to work for me. Contrast bumped a bit.
Unity 2.39 on European DZ, if anyone's interested.
Would be good if it's possible to add this BE toggle to settings, to disable/enable it on the fly (to compare the image quality, for ex.)
Thanks for your post.
edit: nope, it seems it doesn't work. got another dz to compare and there's absolutely no difference in image quality.
maybe some devs will get their hands on this thing?
Flashable zips ? 0_o where?
Sent from my HTC Vision using XDA App
Yeah I'd like the flash zip
Not into changing permission and crap. Too lazy
Also will it work on miui and cm7?
Sent from my HTC Vision using xda premium
TheUndertaker21 said:
Yeah I'd like the flash zip
Not into changing permission and crap. Too lazy
Also will it work on miui and cm7?
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Same xD Flashing a zip would be nicer than messing with permissions xD
Thanks for your work, but I've tried it and this makes no difference whatsoever.
I've installed it without a problem. I don't see very much difference between having it enabled or not, and installation is too cumbersome to maintain everytime I update to a new rom or nightly. Its cool, but too much hastle. Make it a flashable zip if you want more people to use it.
Not the biggest difference in the world. But it still looks really nice and it's a joy to use. I love it!
bruciato said:
hi, I had tried but when I write on emulator "busybox chmod 0755 /system/etc/be_photo
" it replies to me "Busybox permission denied"!
Click to expand...
Click to collapse
Type "su -", press enter, than type the busybox command.
Honestly, I'm not even sure if this even runs at all. Putting two files in /system/etc and adding 2 lines to build.prop doesn't seem to me that it makes anything run. I'm not 100% sure how build.prop works, so I might be wrong.
I've tried the fix on one G2 and compared to another G2 on the same picture, at the same time. Exact same picture quality, but then again, my eyes might not be good enough.
tsubus said:
Honestly, I'm not even sure if this even runs at all. Putting two files in /system/etc and adding 2 lines to build.prop doesn't seem to me that it makes anything run. I'm not 100% sure how build.prop works, so I might be wrong.
I've tried the fix on one G2 and compared to another G2 on the same picture, at the same time. Exact same picture quality, but then again, my eyes might not be good enough.
Click to expand...
Click to collapse
eyes might not be good enough? lol
If you cannot see the difference then obviously the quality change is insignificant enough to disregard the trouble of typing in all these commands
I applied this patch, but i have to say for me its also hard to see the difference... Is there any way to proof that its working?
Sent from my HTC Vision using XDA App
Stargazer418 said:
Type "su -", press enter, than type the busybox command.
Click to expand...
Click to collapse
no it was a problem with su..now works!But I can't see particular changes..
tsubus said:
Honestly, I'm not even sure if this even runs at all. Putting two files in /system/etc and adding 2 lines to build.prop doesn't seem to me that it makes anything run. I'm not 100% sure how build.prop works, so I might be wrong.
I've tried the fix on one G2 and compared to another G2 on the same picture, at the same time. Exact same picture quality, but then again, my eyes might not be good enough.
Click to expand...
Click to collapse
I agree. I can't tell a difference on video either. I CAN tell when Sony did it's demo but this... nada. I smell bs here. I doubt a rendering engine can be so small. It seems like these are just files that accompany an engine and not the full deal. The OP needs to come up with some proof that this sh!t runs because the consensus is that same everywhere he posts this: it doesn't do a thing!
This is a dev forum. But I have only seen one person reply with anything dev worthy. By that I mean what rom they are using. Just saying you ran this on a g2 or a DZ does not help anything. More info about what your running would be best to make this discussion worth anything.
Also. What video are you attempting to view? Something converted to the phones resolution? Video taken with the phone? A blueray 1080p rip? I see alot of *****ing but no info coming forth.
Sent from my HTC Vision using xda premium
ngc604 said:
This is a dev forum. But I have only seen one person reply with anything dev worthy. By that I mean what rom they are using. Just saying you ran this on a g2 or a DZ does not help anything. More info about what your running would be best to make this discussion worth anything.
Click to expand...
Click to collapse
it was me, lol
But ROM name/version won't help here IMO.
The files OP has uploaded are too small.
And the contents is quite strange. Not an ELF or any other binary. Maybe just a screen color profile, sort of ICC. But it won't work if we just put them onto phone.
There should be some service to manage all these things. Something from /system/lib or /system/framework. There's something about "swiqi" service in original post, but there's no file for this.
Why should our rom just use files put to /etc?
So I'm guessing it won't work... maybe just yet
NeverGone\RU said:
it was me, lol
But ROM name/version won't help here IMO.
The files OP has uploaded are too small.
And the contents is quite strange. Not an ELF or any other binary. Maybe just a screen color profile, sort of ICC. But it won't work if we just put them onto phone.
There should be some service to manage all these things. Something from /system/lib or /system/framework. There's something about "swiqi" service in original post, but there's no file for this.
Why should our rom just use files put to /etc?
So I'm guessing it won't work... maybe just yet
Click to expand...
Click to collapse
that's what I was saying... there are no lib files or any type of an engine to run this overlay. It doesnt work that way.
Is there a flash able zip for cm7.1 stable.?? If solo can someone please pm me please !
Sent from my HTC Vision using XDA App
Hello guys,
I just moved to MildWild CM-7.0 JG Stable, and wonder how to enable my sdext.
I used to run SuperNova Rom and it worked well with my ext4 partition (as its internal memory). With MildWild CM-7.0 JG Stable, I can't find any options or ways to enable this partition.
Please can you help?
That rom has an A2sd script, that only moves the app ( only the apk), without its data, to ext.
Try flashing another script, like mounts2sd.
I believe mw has a2sd script built in.. what memory usage does titanium report?
Sent from my HTC Desire using xda premium
Hi guys,
In the end, I managed to enable sdext with this ROM. That's challenging but amazing of course.
Apache9 said:
Hi guys,
In the end, I managed to enable sdext with this ROM. That's challenging but amazing of course.
Click to expand...
Click to collapse
Hey fren...
How did you managed to do that?
I was pleased with SuperNova's whereby it utilizes SD-EXT as an "Internal Memory" expansion prosthetic too, but it is no longer maintained.
Please share how you did it with us.
Thank you! :laugh::good:
tyan888 said:
Hey fren...
How did you managed to do that?
I was pleased with SuperNova's whereby it utilizes SD-EXT as an "Internal Memory" expansion prosthetic too, but it is no longer maintained.
Please share how you did it with us.
Thank you! :laugh::good:
Click to expand...
Click to collapse
Hi dude,
I used to be with SuperNova, which I think is one of the stablest roms. But yes, it is no longer developed, and I had some camera problem with this rom as well.
Anyway, I follow the instructions from this link to enable SD-EXT in MildWild CM-7:
C:\>adb shell
# mount /system
# exit
C:\>adb push 40ad2sdx /system/etc/init.d/
C:\>adb shell
# cd /system/etc/init.d
# rm 40a2sd
# chmod 755 40ad2sdx
# cd /
# umount /system
# exit
C:\>
Sorry, I'm not allowed to post the link, so you may Google for it. Hope this helps
Thank you! :highfive:
Found the script .ZIP for easy Recovery install.
http://forum.xda-developers.com/showpost.php?p=18602050&postcount=19
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");