Stock kernel with:
SELinux set to permissive mode
Knox removed completely
Upstream patches from the Linux mainline (3.4.39 - 3.4.107)
Nothing added. No tweaks, no gimmicks, nothing.
Download
KitKat Permissive Kernel for SM-P600:
Download - [V2: 10/05/2015] - fixes some minor trouble with .107
Basic Troubleshooting
If you'r WiFi is forgetting paswords:
Edit your build.prop in: /system (you'll need to mount as R/W)
Find the line that says: ro.securestorage.support=true and change it to false.
If you're having FC issues, make sure the following apps are totally removed from /system/app
KNOXAgent.apk
KNOXAgent.odex
KnoxAttestationAgent.apk
KnoxAttestationAgent.odex
KNOXStore.apk
KNOXStore.odex
KNOXStub.apk
ContainerAgent.apk
ContainerAgent.odex
KLMSAgent.apk
KLMSAgent.odex
ContainerEventsRelayManager.apk
ContainerEventsRelayManager.odex
And change the following in build.prop
ro.config.tima=1 to 0
ro.config.knox=1 to 0
XDA:DevDB Information
UpstreamPermissive Kernel, Kernel for the Samsung Galaxy Note 10.1 (2014 Edition)
Contributors
xluco
Kernel Special Features:
Version Information
Status: Stable
Created 2014-05-19
Last Updated 2015-05-10
Great! Thanks for this.
Sent from my SM-N900P
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thanks xluco. you're the best
xluco thanks a lot for this. Would you have any time for version for us poor p605 owners still with 4.3? This enforcing selinux is killing me in my efforts to use Linux
fastguy said:
xluco thanks a lot for this. Would you have any time for version for us poor p605 owners still with 4.3? This enforcing selinux is killing me in my efforts to use Linux
Click to expand...
Click to collapse
Yep, do you know if anyone has the 605 kernel source posted anywhere other than the samsung opensource website, its so bloody slow
xluco said:
Yep, do you know if anyone has the 605 kernel source posted anywhere other than the samsung opensource website, its so bloody slow
Click to expand...
Click to collapse
I don't know. But I can try to download latest nc3 one and try to upload it to mega for example. I don't know if that would be faster though
Any chance to make one for P601?
egotheist said:
Any chance to make one for P601?
Click to expand...
Click to collapse
I'll look into it
xluco said:
I'll look into it
Click to expand...
Click to collapse
You are my hero :fingers-crossed:
is the 605 the same as 605V?
xluco said:
Yep, do you know if anyone has the 605 kernel source posted anywhere other than the samsung opensource website, its so bloody slow
Click to expand...
Click to collapse
Hi, I downloaded it and uploaded only the kernel to Mega. Link is below. I'm not sure if this is the latest but this is the only one for pure P605. The NC2 one seems to be for SM-P605V_NA. Mine is international version.
https://mega.co.nz/#!UZcTWa7R!e8TVCrdvkfAyTlpHG4ewF2aSC9Uod7CtE9XkNtKmAqY
Let me know if you also need the Platform files or any subset of it, as that file is huge!
---------- Post added at 02:44 PM ---------- Previous post was at 02:37 PM ----------
xluco said:
is the 605 the same as 605V?
Click to expand...
Click to collapse
I read in XDA somewhere that it's same in HW but LTE frequency support is different (ie Verizon) and possibly the partition layout can be different.
fastguy said:
Hi, I downloaded it and uploaded only the kernel to Mega. Link is below. I'm not sure if this is the latest but this is the only one for pure P605. The NC2 one seems to be for SM-P605V_NA. Mine is international version.
https://mega.co.nz/#!UZcTWa7R!e8TVCrdvkfAyTlpHG4ewF2aSC9Uod7CtE9XkNtKmAqY
Let me know if you also need the Platform files or any subset of it, as that file is huge!
---------- Post added at 02:44 PM ---------- Previous post was at 02:37 PM ----------
I read in XDA somewhere that it's same in HW but LTE frequency support is different (ie Verizon) and possibly the partition layout can be different.
Click to expand...
Click to collapse
Thanks mate downloading now, much appreciated. I don't need the platform files but I do need the ramdisk, if you're running stock rom I can point you in the right direction if you don't know how to extract it
Here is the situation as it stands
There is no KitKat kernel source for 601 or 605 (just 605V)
I'll do an permissive kernel for JB for those two devices, but I need unmodified stock ramdisks.
If you have either of those devices and are running stock jelly-bean, you can extract the ramdisk by using Terminal Emulator and typing
Code:
dd if=/dev/block/mmcblk0p14 of=/sdcard/boot.img
However this will only work if the partitions are in the same order as the SM-P600 :/
Further, I only have the SM-P600 so I can't test anything I produce for other devices and therefore I can't guarantee that it won't completely bugger your device, nor will I be held responsible
fastguy said:
Hi, I downloaded it and uploaded only the kernel to Mega. Link is below. I'm not sure if this is the latest but this is the only one for pure P605. The NC2 one seems to be for SM-P605V_NA. Mine is international version.
https://mega.co.nz/#!UZcTWa7R!e8TVCrdvkfAyTlpHG4ewF2aSC9Uod7CtE9XkNtKmAqY
Let me know if you also need the Platform files or any subset of it, as that file is huge!
Click to expand...
Click to collapse
does the kernel.txt or some file like that tell you which _defconfig to make? thanks
xluco said:
Here is the situation as it stands
There is no KitKat kernel source for 601 or 605 (just 605V)
I'll do an permissive kernel for JB for those two devices, but I need unmodified stock ramdisks.
If you have either of those devices and are running stock jelly-bean, you can extract the ramdisk by using Terminal Emulator and typing
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
However this will only work if the partitions are in the same order as the SM-P600 :/
Further, I only have the SM-P600 so I can't test anything I produce for other devices and therefore I can't guarantee that it won't completely bugger your device, nor will I be held responsible
Click to expand...
Click to collapse
Hi xluco, here it is from my custom 4.3 firmware, but the kernel was stock.
https://mega.co.nz/#!QFc0jTzB!Utn2ly10to155Oj2YjGwMe3ZkSVCzPlsEOkz_u7TIGI
I'll also download a fully stock one and upload the boot.img. I'm willing to test it on my P605.
xluco said:
Here is the situation as it stands
There is no KitKat kernel source for 601 or 605 (just 605V)
I'll do an permissive kernel for JB for those two devices, but I need unmodified stock ramdisks.
If you have either of those devices and are running stock jelly-bean, you can extract the ramdisk by using Terminal Emulator and typing
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
However this will only work if the partitions are in the same order as the SM-P600 :/
Further, I only have the SM-P600 so I can't test anything I produce for other devices and therefore I can't guarantee that it won't completely bugger your device, nor will I be held responsible
Click to expand...
Click to collapse
xluco, I checked the partition layout on my SM-P605, mmcblk0p9 in my system points to "pad" partition. I dont know what this is, so I also extracted the one "boot" points to, just in case. It is mmcblk0p14. file is here:
https://mega.co.nz/#!YVMl2Q4Z!HddMuuDbzom0v1gXxmP7bXmO-QAbG71QpJNAt5nHoII
I'm also attaching the partition layout from /dev/block/platform/msm_sdcc.1/by-name/
xluco said:
does the kernel.txt or some file like that tell you which _defconfig to make? thanks
Click to expand...
Click to collapse
Sorry just recognized this post. Here's the text file from the samsung package, I think it does refer to the defconfig as below:
make VARIANT_DEFCONFIG=msm8974_sec_lt03eur_defconfig msm8974_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig
xluco said:
Here is the situation as it stands
There is no KitKat kernel source for 601 or 605 (just 605V)
I'll do an permissive kernel for JB for those two devices, but I need unmodified stock ramdisks.
If you have either of those devices and are running stock jelly-bean, you can extract the ramdisk by using Terminal Emulator and typing
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
However this will only work if the partitions are in the same order as the SM-P600 :/
Further, I only have the SM-P600 so I can't test anything I produce for other devices and therefore I can't guarantee that it won't completely bugger your device, nor will I be held responsible
Click to expand...
Click to collapse
I attached KK kernel version of P601. I'll appreciate if you can modify it to permissive and add NTFS aupport.
hopeshadow said:
I attached KK kernel version of P601. I'll appreciate if you can modify it to permissive and add NTFS aupport.
Click to expand...
Click to collapse
Thanks for the effort, and I'll download it just in case, but theres no KK kernel source on the samsung opensource website for the 601 yet so theres not much I can do without that
fastguy said:
Sorry just recognized this post. Here's the text file from the samsung package, I think it does refer to the defconfig as below:
make VARIANT_DEFCONFIG=msm8974_sec_lt03eur_defconfig msm8974_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig
Click to expand...
Click to collapse
fastguy said:
xluco, I checked the partition layout on my SM-P605, mmcblk0p9 in my system points to "pad" partition. I dont know what this is, so I also extracted the one "boot" points to, just in case. It is mmcblk0p14. file is here:
https://mega.co.nz/#!YVMl2Q4Z!HddMuuDbzom0v1gXxmP7bXmO-QAbG71QpJNAt5nHoII
I'm also attaching the partition layout from /dev/block/platform/msm_sdcc.1/by-name/
Click to expand...
Click to collapse
fastguy said:
Hi xluco, here it is from my custom 4.3 firmware, but the kernel was stock.
https://mega.co.nz/#!QFc0jTzB!Utn2ly10to155Oj2YjGwMe3ZkSVCzPlsEOkz_u7TIGI
I'll also download a fully stock one and upload the boot.img. I'm willing to test it on my P605.
Click to expand...
Click to collapse
Thanks guys
Related
Klin's Custom Kernel for YP-G1 USA and INTL
Latest Version: R3
This is a custom kernel that I made based off of STeVE's 3.0 sources. (He gave me permission to release this) I will be adding more features and continue to develop it. The sources are here: https://github.com/klin1344/Galaxy-Player-4.0-Kernel
Please be patient if there are problems as this is my first kernel and everything is still a learning process for me. (I'm completely new to Linux) Enjoy .
Disclamer: I will not be responsible if you brick your device or if any weird stuff happens.
R1 features:
- EXT4 support (See instructions in 2nd post on how to convert to EXT4)
- Insecure kernel (root in ADB)
- All features from STeVE's 3.0 kernel
R2 features:
- Improve touch screen responsiveness
- Custom bootanimation support; the kernel will look in both /data/local/ or /system/media/ for bootanims
- Netarchy/coolbho3ks SoD patch from Entropy512's source (allows you to use screen off profiles of under 800Mhz)
- Lots of tweaks and mods for overall performance and responsiveness
R3 features
- Ported ClockWorkMod 5.2.0.7 from semaphore kernel source for the I9000
- Raised FPS cap to 72
- Raised RAM from 341 MB to 352 MB
--Doing this would break HD video recording and taking photos while taking videos on the I9000, but our device has none of those features, so it shouldn't have any issues.
- More reliable and easier way of converting to EXT4 (see below) (thanks zaclimon for the advice)
How to install:
Check the PDA slot and flash the .tar in ODIN. Or if you're on Linux, extract the zImage from the .tar and flash with Heimdall.
All releases are here: http://www.mediafire.com/?m1bjqojv5ln6o
Thanks to:
- Entropy512 and rumirand for their kernel sources
- STeVE for his custom kernel and source
- Many kernel devs in other SGS and Nexus S forums for their kernel sources as well
- zaclimon for testing initial release and helping me with MD5 mismatch issues
How to convert to EXT4Instructions are for R3 only
1. Flash my kernel.
2. Make sure you have about 14 MB free space on /system.
3. Boot into CWM recovery and do a full nandroid backup.
4. Reboot, and from your computer go to the CWM backup directory on your sd card.
5. Change all the files from ".rfs.tar" to ".ext4.tar".
6. Open nandroid.md5 with a text editor and change all the ".rfs.tar" to ".ext4.tar". Save and close.
7. Eject the device from your computer FIRST. This step is crucial. Then disconnect from your player.
8. Reboot to CWM recovery and do a full restore.
Note: If you're using R5 of my KlassicROM then system is already EXT4.
Thanks to zaclimon for advising me to eject from computer first
If you appreciate my work and want to encourage me to continue developing, don't post "thanks", just click it!
Reserved for future use.
Thanks for your continual development for this player with the custom kernel. Is the CWM the same version from Steve's kernel, or have you put in a newer version?
Regarding your new rom release, I'm always reluctant to change things when they are working well. I hesitated (slightly) going from R3 to R4 and now I'm doing the same thing going to R5.
Quite frankly, R4 works great for me but I'll probably change over to R5 soon enough. LOL Also, if I'm understanding your release notes correctly for R5, I can no longer replace sanim zip with my own boot anim in /system/media, is that correct?
Thanks again, klin.
Mike T
webdroidmt said:
Thanks for your continual development for this player. Funny, I'm always reluctant to change things when they are working well. I hesitated (slightly) going from R3 to R4 and now I'm doing the same thing going to R5.
Quite frankly, R4 works great for me but I'll probably change over to R5 soon enough. LOL Also, if I'm understanding your release notes correctly for R5, I can no longer replace sanim zip with my own boot anim in /system/media, is that correct?
Thanks again, klin.
Mike T
Click to expand...
Click to collapse
Yes bootanimation is no longer supported, but thats an easy fix I will add to this kernel.
Sent using Tapatalk
How long should the device stay at the boot animation after converting the filesystems? Mine has been sitting for more than 5 minutes. I'm on Klassic R5
EDIT: Didn't know R5 was already using EXT4 until I read the note at the top of the page. Change it to a larger font and make it bold so people can read it better.
Screenshot
anyone ??
pentatonicfunk said:
Screenshot
anyone ??
Click to expand...
Click to collapse
It's a KERNEL not a ROM.
There is not screeshot. The kernel is the core of a linux architecture, the one that handle the drivers, the filesystem etc ...
The Rom is the "software" that is around the kernel with all the apps.
See the kernel and the rom as a onion, kernel as the centre and rom as the rest.
What is the benefit of EXT4?
Ext4 file system is much faster than Samsung's proprietary rfs filesystem. It is basically voodoo lagfix, except you have to manually convert instead of it doing it automatically.
Sent using Tapatalk
klin1344 said:
Ext4 file system is much faster than Samsung's proprietary rfs filesystem. It is basically voodoo lagfix, except you have to manually convert instead of it doing it automatically.
Sent using Tapatalk
Click to expand...
Click to collapse
So that makes closer to how others like HTC does it?
caseyatbt said:
So that makes closer to how others like HTC does it?
Click to expand...
Click to collapse
I'm not sure what HTC uses, but the Linux standard us ext4.
Sent using Tapatalk
Updated to r2.
Edit: oh yeah, some suggestions for a kernel name would be nice.
Sent using Tapatalk
Hmm, how about "Klin's kool kernal"
Or "Klin's kustom kernal" might be better?
"Netarchy/coolbho3ks SoD patch from Entropy512's source"
What is that, btw? Nvm about that, just read about it in entropy512's thread.
One more thing: you said somewhere that you had ported a newer version of cwm than what is in Steve's rom, is that in here?
Sent using Tapatalk
iJimaniac said:
Hmm, how about "Klin's kool kernal"
Or "Klin's kustom kernal" might be better?
"Netarchy/coolbho3ks SoD patch from Entropy512's source"
What is that, btw? Nvm about that, just read about it in entropy512's thread.
One more thing: you said somewhere that you had ported a newer version of cwm than what is in Steve's rom, is that in here?
Sent using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestions.
The CWM had too many problems than it was worth to sort everything out so I'll have to stick to steves cwm implementation for now.
Sent using Tapatalk
Nice!
Can I just flash this over the current kernel? (R1)
I'm on your r5 ROM.
And also, does this version fix the lagging issues in internet browsers and games?
Se7enex said:
Can I just flash this over the current kernel? (R1)
I'm on your r5 ROM.
And also, does this version fix the lagging issues in internet browsers and games?
Click to expand...
Click to collapse
Yes it is compatible with my ROMs. I'm not sure if it fixes the issues because I'm not using Klassic anymore so I can't test it. But I'm using rooted/deodexed stock with this kernel and it is pretty smooth.
Sent using Tapatalk
klin1344 said:
Yes it is compatible with my ROMs. I'm not sure if it fixes the issues because I'm not using Klassic anymore so I can't test it. But I'm using rooted/deodexed stock with this kernel and it is pretty smooth.
Sent using Tapatalk
Click to expand...
Click to collapse
Found a problem. If you are to flash r2 from stock and follow the steps you get suck and the logo. You have to flash r1 follow the steps and then r2.
Edit: On a side note I only see system and cache are the only ones that are converted to ext4. Is that supposed to happen?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey klin, can you post screenshots of the mounts like mine on the post above so I know I'm not alone? The app is Android system info. I feel bad for you cause it seems like i'm annoying you with problems
This is a Windows Batch Script/Tool to make any 4.4 based ROM to full F2FS compatibility !! This tool can convert any existing ROM from ext4 to Full F2FS Compatibility in a few clicks !! All tools necessary for conversion included in the batch file itself !!
Basic Info
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
DISCLAIMER
Code:
*I am Not responsible for any bricked devices,SD cards or thermonuclear attacks.
*Please do some research about what you are doing before you use the tool.
*YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Current Device Compatibility
Code:
1. Nexus 4 ( Mako )
2. Nexus 7 2012 Edition ( Grouper)
3.Nexus 5 (HammerHead)
Prerequisites
Code:
1. A Hammerhead
2. Any 4.4 based ROM with [B][U]busybox [/U][/B]installed
3. Proper F2FS Compatible Recovery and Partition Zip from
[url]http://forum.xda-developers.com/google-nexus-5/orig-development/recovery-twrp-2-7-0-0-f2fs-support-t2746030[/url]
4. Any Windows version and my batch script
Features
Code:
1. One Click F2FS Conversion Process
2. All tools included in the Zip file itself
3. Changes only the relevant parts of your updater-script keeping the rest unmodified
4. Compatible boot.img included in the ROM itself
5. Now Scripts are Device Specific
6. Error conditions at many places so a noob cant go wrong
***Special note for CM /CM based ROM users***
Code:
I dont test the script since I dont own an HH !! This is the CM kernel by @kdh2834
If it does not work kindly post the detailed error on the thread . Will try my best to resolve it
***Special note for Stock ROM users***
Code:
The script requires busybox and since stock roms dont have busybox the repacked ROM wont boot up.
In such a case the best option is try out any other AOSP based ROM/or a Stock ROM with busdybox installed
Instructions
Code:
[LIST=1]
[*] Unpack the Zip file you downloaded from Link Below to a folder named F2FSROMConvetor (Dont Mess with the name).
[*] Take Care that the path you extract my Zip for eg in my case "C:\Users\Nabendu\Desktop\F2FSROMConvetor"
does not contain any blank spaces in between or else the script will not work as intended.
[*] Run F2FS Convertor.bat
[*] Select your device
[*] Place the Zip in the Extract /Input directory when prompted
[*] The script will Unpack your ROM
[*] Select option of boot.img based on your rom
[*] Repack your ROM
[*] A black window will open showing the Repacking progress. Dont close my Blue Window anytime during it the repacking process.
After 100% repacking is done the Black Window will close automatically and you can now press any key to Continue
[*] Check NEW F2FS ROM directory for the Repacked ROM
[*] Flash and Enjoy
[*] Cleanup the working directory cleanup.bat (Cleans everything including original input ROM.Only a copy of the Output ROM is maintained)
[/LIST]
***FAQ's***
Q. I get errors compiling the ROM on my XYZ Windows Version?
A. Read through my steps once again especially point 1 & 2. Hopefully u can get it to work.
If you think you are doing everything correctly post it on the thread and Ill try to reply within 24Hrs.
Q. I want to do it on Linux !! Why you no create bash scripts ?
A. Im not good at bash scripting !! Also dont own a Linux Distro so cant help you guys !! But look here @jolinnard has a script for Linux users
https://github.com/figue/f2fs-scripts/blob/master/convert_ROM_to_f2fs.sh and make necessary changes for Hammerhead updater script if any
Q. I can do the same with the Convert to F2FS apk on the Playstore ?
A. Sure you can. Converting on mobile is easier also. But only reservation is that it is paid.Not everyone can afford it.
Also time permitting Ill create a Android Terminal Script based on jolinnards script for Linux.
Q. Do you think I can convert it myself ?
A. Yes its just clicks . Read my steps and do it you wont go wrong.
Download Links
1. V1.1 OLD
2.V1.2 NEW
Changelog
Code:
V1.0 Intial Release
V1.1 : Add Device Support
1) Added Device Compatibility : Nexus 5
2) Scripts now will come seperate for each device.
3) Did some cleaning up on my messy script
V1.1 : Add more Boot.imgs for N5
Credits
Code:
@legolas93 For bringing F2FS to Nexus and also for providing the boot.img for the script
[user=4439521]@mikaole[/user] For the German Translations and extensive testing
[user=2002216]@jolinnard[/user] For the amazing F2FS kernels he is providing
[user=4544860]@osm0sis[/user] For his amazing Android Image Kitchen.The cleanup.bat script is taken from his tool.
[user=3325155]@fishears[/user] For helping out on the kernel side.
[user=5501864]@USBhost[/user] For being the lone tester for the N7 ( 2012 )
[user=4450732]@CallMeAldy[/user] For the CM trick and his compilation thread
[user=4851200]@Rohit02[/user] For being the beta tester
[user=14325584]@kdh2834[/user] For his AOSP Kernel
And all other beta testers !! Sorry if I forgot anyone from the list !!
Screenshots in the Next Post
Hit the Thanks button if you Like My Work
Screenies
Screenies atlast
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Excellent test on
Big thanks
c-rom v6.4 Network Connectivity fail
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
I dont own a HH so not much I can help you with !! But try flashing a different kernel on top of it , think it should work !! And does c rom used the aosp kernel in the first place !! Look at the thread for modified Kernels , i guess flashing one should solve your problem !!
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img (AOSP) that NABENDU1 provide inside his tool will not work with your rom.
c-rom is aosp based.
micr0g said:
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img that NABENDU1 provide inside his tool (AOSP) will not work with your rom.
Click to expand...
Click to collapse
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
belictony said:
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
Click to expand...
Click to collapse
Okay you have the com.androidprocess phone fc problem right !! If its only that Ill patch the kernel myself and get you a new one in a few mins and rest assured it will work for sure !!
rabbo3 said:
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
Click to expand...
Click to collapse
Yup what kind of Rom u use !! If it has differential update like Mokee OS or xdelta ( I dont know xdelta/opendelta in detail ) like Omni I can create some kind of allied script for it too !! Put the same question in the N7 2012/N4 but dint get any responses for it mosly due to devs still use the traditional way !! Anyways if anyone wants patching for those im up for the task !!
EDIT: Version 1.2 for HH online ( Bigger Size due to 4 boot.imgs included in the script itself)
Dl Link : https://mega.co.nz/#!dxcVmQRS!5zv6RCqJs82rv5-aW3GqICW5YgCPuZtUhiH0F1vpVP8
Changelog:
Added CM boot.img ( Untested by me ) thx to @kdh2834
Added Purity boot.img ( Untested by me) thx to @kdh2834
Added AOSP com.android process phone fc boot.img ( Untested by me) thx to @me
Kindly post feedback on the thread !!
I will fix the screenies sometime later or tomm
I've used this tool to successfully switch over to f2fs-all with crDroid (a CM based rom). My biggest problem, however, is that I am completely unable to flash elementalx afterward because it freezes on boot. Anybody found a way to fix this?
Edit, I'm an idiot. I found out I have to manually mount /system before flashing ElementalX
fantastic job, works great with cm11-m6,very faster
Great!
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
tavocabe said:
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
Click to expand...
Click to collapse
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
NABENDU1 said:
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
Click to expand...
Click to collapse
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
callidus_ex_de_latebros said:
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
Click to expand...
Click to collapse
Moto G is infact already has /data partition in F2FS file format !! The only thing is making the cache and system full f2fs !! For this firstly your kernel dev should take a initiative to create a fully compatible f2fs kernel and also a f2fs recovery !! Once that is done I would be more than glad to help you guys out !! Anyways till then enjoy f2fs on /data !!
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
Works fine on my crDroid setup. Did it work for you before with Euroskank? Have you tried toggling from MTP to PTP and back? If you have a secure screen lock in place, are you ensuring that you have unlocked the phone after plugging it in? Are you waiting to plug the phone in until after it's booted up? Just trying to rule out the obvious troubleshooting steps
Sent from my Nexus 5 using Tapatalk
work in 4.4.3?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
It works for me using omni-elementalx.
danielalonso said:
work in 4.4.3?
Click to expand...
Click to collapse
Yes
To @NABENDU1
Hi, so far everything is good, only complain is that most of the times when I reboot to recovery and flash any update to rom/kernel or when I add a new rom using multirom (tested and working good with omni, slim and paranoid), when finished and reboot the phone I see the boot screen many times. Like a bootloop but eventually it makes it to the rom or the multirom menu to select a rom. Is this because of my configuration of f2fs with multirom or maybe the kernel I use (elementalx shared with all the roms)?
@NABENDU1 thank you very much for this, it's quick and easy as well as educational (to me)
Creating a new thread as posting modding info in the official thread might be considered rude/inappropriate/hijacking.
Read the official thread first, starting october 6 2014.
These modding descriptions are for the works of the AOSPA and AOSPA-legacy team, about 101% of the credits go to @ayysir and @houstonn and all oft PA team. Awesome stuff.
Feel free to donate to them in the way of their liking.
And of course @777jon, owner of the cited unofficial VS980 thread, who gave the essential hint about the display-caf package
This thread is intended to provide a knowledge base for modding the official builds as long as they seem flawed for some of us. Feel free to reference helpful stuff from other threads in accordance to forum rules.
D802 @ AOSPA 4.6b3
Here's what made the issue go away for me on D802. This might be dangerous, so don't do it if you can't live with the risk of bricking your phone, you are entirely on your own if something goes wrong.
Prerequesites:
- Install official 4.6b3 AOSPA-legacy zip-image to phone
- [optional] Install Renders Kernel
- Install updated root
- Download and extract unofficial 4.6b3 VS980 zip-image from @777jon 's thread (yeah, it's the wrong phone, but we need only one file; find thread in Forum yourself, got yelled at for crosslinking stuff before )
Procedure:
-MAKE NANDROID BACKUP!
-Copy file from extracted VS980-image [zip]/system/lib/hw/hwcomposer.msm8974.so to phone's sdcard folder via USB (eg. ./Download)
-Start terminal on phone or adb shell
-Create backup dir:
Code:
mkdir /sdcard/noheatbackup
-get root access by typing
Code:
su
-make /system writeable by typing
Code:
mount -o remount,rw /system
-backup existing file by typing
Code:
cp /system/lib/hw/hwcomposer.msm8974.so /sdcard/noheatbackup/
-overwrite existing file by typing
Code:
cp /sdcard/Download/hwcomposer.msm8974.so /system/lib/hw/
-reboot by typing
Code:
reboot
-Note that you will need to be on a root shell to remove the backup again with
Code:
rm -r /sdcard/noheatbackup
:
Screenshot after replacing /system/lib/hw/hwcomposer.msm8974.so : Heat issue gone, see temp in status bar. After deep sleep, temps are about 3-5 K over room temperature.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
D802 @ AOSPA 4.6b3
Thanks for creating a new thread man, but i don't think this qualifies for the Original Development section though
@Judge Joseph Dredd please move to correct section
mjwhirly said:
Thanks for creating a new thread man, but i don't think this qualifies for the Original Development section though
@Judge Joseph Dredd please move to correct section
Click to expand...
Click to collapse
Just move it whereever this kind of stuff belongs to. I still have to learn forumish [emoji17]
D802 @ AOSPA 4.4
Oh yes. See me:
Can i do it?
Download the vs980 From Post on original g2 development thread. Extract the zip and copy the file. (the 06/29 version)
Download the official beta 3 on aospal and extract it. Now i'll copy the file before and paste on beta 3 extracted zip, then i replace it. Now i'll zip the files and flash them via twrp. This method works too?
bielphc said:
Oh yes. See me:
Can i do it?
Download the vs980 From Post on original g2 development thread. Extract the zip and copy the file. (the 06/29 version)
Download the official beta 3 on aospal and extract it. Now i'll copy the file before and paste on beta 3 extracted zip, then i replace it. Now i'll zip the files and flash them via twrp. This method works too?
Click to expand...
Click to collapse
No, i meant the 4.6v3 version from october. Might work the way including it to the zip, but I'm really new to this and haven't tried.
Benztown said:
No, i meant the 4.6v3 version from october. Might work the way including it to the zip, but I'm really new to this and haven't tried.
Click to expand...
Click to collapse
Ok. you saved my life. Thx. i love this rom but i dont want to cook a pizza on him.
thx
"-overwrite existing file by typing cp /sdcard/Download/hwcomposer.msm8974.so /system/lib/hw/"
My phone rebooted of it self after doing the step above!?
But the copying seem to have worked! Thanks a lot for this guide!
For me doesn't work.
slade9220 said:
For me doesn't work.
Click to expand...
Click to collapse
Did you take the VS980 zip from @777jon s thread? I guess the official one has the same issues as the d802 official one.
Also I did it in an ADB shell, dunno if it works on phone's terminal.
D802 @ AOSPA 4.4
Benztown said:
Did you take the VS980 zip from @777jon s thread? I guess the official one has the same issues as the d802 official one.
Also I did it in an ADB shell, dunno if it works on phone's terminal.
D802 @ AOSPA 4.4
Click to expand...
Click to collapse
Thanks.. I'll try! ✌
Edit: IT WORKS! THANKS!
Do Anyone try the new 4.6Beta4?!
I wonder if you can just take the hwcomposer.msm8974.so file from any rom based on dr87's source?
Its the same thing right?
______________
Edit
I just extract the lib from 3 different rom cm unofficial by fabioio (no number), pa vs980 (1), and mahdi 920 (2). Fabioio's cm is smallest and both pa and mahdi are of the same size.
punyategar said:
I wonder if you can just take the hwcomposer.msm8974.so file from any rom based on dr87's source?
Its the same thing right?
______________
Edit
I just extract the lib from 3 different rom cm unofficial by fabioio (no number), pa vs980 (1), and mahdi 920 (2). Fabioio's cm is smallest and both pa and mahdi are of the same size.
Click to expand...
Click to collapse
I didn't compare the sources and also didn't check for device dependencies. If its design is done properly there shouldn't be any though. So yeah you should be able to take it from any dr87 based image as long as the structure doesn't change between different commits.
For the size that might just be different compiler options or even just symbol paths. Difficult to compare.
Also with this whole pa closedsource vs. pa opensource one cannot be sure what's really behind the official builds. Can someone actually bring me up to speed what's behind this open/closed source nonsense? Just IP protection?
D802 @ AOSPA 4.4
slade9220 said:
Do Anyone try the new 4.6Beta4?!
Click to expand...
Click to collapse
After what I've read... I'll stay miles away from that build [emoji16]
D802 @ AOSPA 4.4
Benztown said:
I didn't compare the sources and also didn't check for device dependencies. If its design is done properly there shouldn't be any though. So yeah you should be able to take it from any dr87 based image as long as the structure doesn't change between different commits.
For the size that might just be different compiler options or even just symbol paths. Difficult to compare.
Also with this whole pa closedsource vs. pa opensource one cannot be sure what's really behind the official builds. Can someone actually bring me up to speed what's behind this open/closed source nonsense? Just IP protection?
D802 @ AOSPA 4.4
Click to expand...
Click to collapse
The closed source thing is supposedly because that particular stuff(?) Is still buggy. Seeing how stuff go at desktop linux, this reason is really weird.
Yeah i just did the copy paste thing, i got stuck at lg logo. Right as i paste it the cellphone rebooted. I havent changed permission. I havent tried it for the second time though. Not sure if itll be the same.
punyategar said:
The closed source thing is supposedly because that particular stuff(?) Is still buggy. Seeing how stuff go at desktop linux, this reason is really weird.
Yeah i just did the copy paste thing, i got stuck at lg logo. Right as i paste it the cellphone rebooted. I havent changed permission. I havent tried it for the second time though. Not sure if itll be the same.
Click to expand...
Click to collapse
That does indeed seem weird. It seems to me that custom roming is more about magical coding wizardry and fame than about progress in a classical open source sense. Maybe it's just an issue about age. I'm obviously too old...
Strange, my phone didn't reboot. I did it with adb shell and su.
D802 @ AOSPA 4.4
Introduction
Aug 06 Update: ROM is now pre-rooted using @ShinySide's kernel.
Note: Currently, none of the ROMs in this thread are rooted. Flash SuperSU will cause boot-time force-closes that I haven't yet solved. This happens if you try to flash SuperSU 2.46 or 2.49 (BETA), on any of the ROMs in this thread, or any stock image of G900TUVU1FOF6 provided by Samsung/SamMobile.
You must upgrade your firmware to be able to use these ROMs. To do this, you can download the ODIN flashable from downloads, unzip the file, and then flash the resulting .tar.md5 in ODIN under PDA. This will update your bootloader and Modem as well. If you don't have access to windows, you can use Heimdall. To use Heimdall for Galaxy S5, download the source code of Heimdall, and apply this patch. Once you have done this, you can run heimdall found in the 'build' or 'bin' directory of the source code after compilation. After upgrading your firmware, make sure to flash a custom recovery again, which can be done by downloading the .img.tar (if you plan on using ODIN -> PDA) or the .img (if you plan on using Heimdall -> with argument --RECOVERY twrp<version>.img) from TWRP.
Versions and Descriptions
COMPLETE: The full stock ROM, includes KNOX, no SystemUI patch. It is a simple flashable which includes metadata correction.
WITHRINGTONES: A heavily debloated ROM, but includes all of the default sounds, including bootsound, notification sounds, etc.
SLIM: A heavily debloated ROM, which simply removes most of the default sounds from the previous package.
*KNOX is removed, but Settings.apk was not patched to show this change.
*Settings may crash if an unsupported operation is run on the debloated versions such as:
Add New Ringtones
Face Recognition
etc...
Click to expand...
Click to collapse
Images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Installation instructions
* Download the ROM (see the next section)
* Reboot to Recovery
* Clear Cache & Dalvik (and also Data if you're coming from AOSP)
* Flash the ROM
* Reboot
Click to expand...
Click to collapse
Download
SLIMv2
SLIM
WITH-RINGTONES
COMPLETE
ODIN Flashable (SamMobile copy)
Click to expand...
Click to collapse
Changelog
Code:
Current changelog: -- 08-06-15
[note] -- SLIMv2 is now pre-rooted
[note] -- Certain oriental fonts removed.
[note] -- Installing any audio picker provider (eg: ES File Explorer) will allow you to add ringtones, so ringtones still left out.
Click to see older changelog:
Code:
07-11-15
[note] -- Initial Release
Click to expand...
Click to collapse
FAQ
Please look at the ScreenShots for question about what is still included in the ROM.
A more detailed FAQ will be added as question are asked.
XDA:DevDB Information
G900TUVU1FOF6, ROM for the T-Mobile Samsung Galaxy S 5
Contributors
rmanne
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: G900TUVU1FOF6
Based On: TouchWiz
Version Information
Status: Stable
Current Stable Version: 2
Stable Release Date: 2015-08-06
Created 2015-07-11
Last Updated 2015-08-06
Thanks for this. It's exactly what I've been looking for. Downloading the debloated with ringtones now.
Edit: for some reason the play store is telling me that Google+ is incompatible with my device.
@rmanne A lost of apps deleted would be helpful! Can you provide that?
itskapil said:
@rmanne A lost of apps deleted would be helpful! Can you provide that?
Click to expand...
Click to collapse
Here's a diff of the two files: https://www.diffchecker.com/mob5jg06
I'm a bit too lazy to type out all of the deleted apps.
It says the complete version systemui is not patched. What patching are you referring to?
Also, is this rom deodexed?
Thankx!
Nice job. Will you post a patched Settings.apk later to replace? Most likely i would be doing things to crash often... :silly:
So before I go and start flashing this ROM I wanna make sure I do it right.. So this is stock touchwiz running 5.1.1 ? And I see I have to update bootloader where would I find the link to that ? I'm still new to the gs5 lol.
WARNING
When you install this ROM you will have no APN settings (with ringtones version) and the phone will not allow to to add a APN.
DO not install until OP fixes this
Hybrid Divide said:
is this rom deodexed?
Click to expand...
Click to collapse
No, it is Odexed. The SystemUI patch is for removing the quickconnect/sfinder bar.
Kilokk said:
Nice job. Will you post a patched Settings.apk later to replace? Most likely i would be doing things to crash often... :silly:
Click to expand...
Click to collapse
Patching the System.apk on an Odexed ROM would prove difficult, so I'll more likely add back some of the features, since they're not technically bloat.
AndroidGee209 said:
So before I go and start flashing this ROM I wanna make sure I do it right.. So this is stock touchwiz running 5.1.1 ? And I see I have to update bootloader where would I find the link to that ? I'm still new to the gs5 lol.
Click to expand...
Click to collapse
Correct. Check the 'intro' section of the first post. It has instructions on how to update your device to the latest bootloader, modem, etc. Make sure to backup your user data first.
vphotographic said:
When you install this ROM you will have no APN settings (with ringtones version) and the phone will not allow to to add a APN.
Click to expand...
Click to collapse
Check Settings>More Networks>Mobile Networks>Access Point Names. If you installed the latest bootloader and modem, you should be seeing fast.t-mobile.com added by default, and if you click the '+', you should be able to add more APNs. Please tell me if this didn't work for you. This ROM was extracted directly from the tar.md5 source, I removed no APNs or anything to do with CSC for that matter.
rmanne said:
No, it is Odexed. The SystemUI patch is for removing the quickconnect/sfinder bar.
Patching the System.apk on an Odexed ROM would prove difficult, so I'll more likely add back some of the features, since they're not technically bloat.
Correct. Check the 'intro' section of the first post. It has instructions on how to update your device to the latest bootloader, modem, etc. Make sure to backup your user data first.
Check Settings>More Networks>Mobile Networks>Access Point Names. If you installed the latest bootloader and modem, you should be seeing fast.t-mobile.com added by default, and if you click the '+', you should be able to add more APNs. Please tell me if this didn't work for you. This ROM was extracted directly from the tar.md5 source, I removed no APNs or anything to do with CSC for that matter.
Click to expand...
Click to collapse
I did not get any APN's plus i cannot add one ??
Paul
You guys see this? http://forum.xda-developers.com/tmo...t/root-kernel-root-method-fof6-5-1-1-t3158005
vphotographic said:
I did not get any APN's plus i cannot add one ??
Paul
Click to expand...
Click to collapse
If you go back to that menu, try to click on the 3 dot menu and reset to default. If it doesn't fix anything, can you paste a screenshot of your settings?
DevVorteX said:
You guys see this? http://forum.xda-developers.com/tmo...t/root-kernel-root-method-fof6-5-1-1-t3158005
Click to expand...
Click to collapse
Yep, it should work on this. For now, it's probably the only way to root these ROMs.
you mind if I simply take your base and deodex it It would make rom development faster right now
malbert16442 said:
you mind if I simply take your base and deodex it It would make rom development faster right now
Click to expand...
Click to collapse
Oh of course I wouldnt mind, go ahead!
Delete
pottyvick said:
My sim isnt recognized when i use this...restoring my 5.0 works so not sure why no sim with this rom
Click to expand...
Click to collapse
Are you just trolling going around from ROM to ROM with the same post: http://forum.xda-developers.com/showpost.php?p=61886724&postcount=57
muniz_ri said:
Are you just trolling going around from ROM to ROM with the same post: http://forum.xda-developers.com/showpost.php?p=61886724&postcount=57
Click to expand...
Click to collapse
Actually no... i realized i flashed the 5.1.1 bootloader and modem via that other thread so i asked over there... forgot to delete it here, sorry
pottyvick said:
Actually no... i realized i flashed the 5.1.1 bootloader and modem via that other thread so i asked over there... forgot to delete it here, sorry
Click to expand...
Click to collapse
Mine isnt recognised either with no APN and i cant add one via the 3 dots. Im on OB1 firmware.
vphotographic said:
Mine isnt recognised either with no APN and i cant add one via the 3 dots. Im on OB1 firmware.
Click to expand...
Click to collapse
Its probably because youre on OB1 firmware.. you need to flash the latest firmware and modem i believe...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
attached is recovery log sir
Er. Aditya said:
attached is recovery log sir
Click to expand...
Click to collapse
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
SuperR. said:
sepolicy-inject is not available for windows currently. I should have removed the option for Windows, and will in the next update. Is this a feature that still needs to stick around? I am not sure if I can get it working in Windows due to the pre-compiled Linux libs in the source. I am also not sure if you can compile libsepol on Windows. If you can get this source compiled for Windows, I can add the feature
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
Click to expand...
Click to collapse
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Er. Aditya said:
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Click to expand...
Click to collapse
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
bcrichster said:
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
Click to expand...
Click to collapse
These wheels are rolling faster each day. We will ride
SuperR. said:
These wheels are rolling faster each day. We will ride
Click to expand...
Click to collapse
Lmao. Right on! If anyone can get this right, it's You and these guys helping here @SuperR. [emoji41] Catching some air!
Sent from my N9515 using Tapatalk
SuperR. said:
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Click to expand...
Click to collapse
yes both were created using latest kitchen 3.0.1.4 , same firmware and procedure
here are the scripts sir
SuperR. said:
v3.0.1.8
Changes:
Windows: Use 7-zip (included) to extract img files instead of Imgextractor.
Windows: Fixed missing symlinks in updater-script.
Windows: Fixed many file contexts not being set correctly.
Windows/Linux: Fixed system/SYSTEM on devices that use SYSTEM.
Linux: Do not create metadata lines for symlinks.
I think this will fix most of the flashing problems. Let me know how it goes
WINDOWS NOTE: It is important that the tools get updated. The updater should take care of it, but if you get errors that 7z is not found, go to Misc tools > Reset tools.
IMPORTANT: Start your rom fresh and extract from system.img again. Make sure you delete 00_project_files directory if you are reusing an existing project.
Click to expand...
Click to collapse
i still got the error 7 even i clean cloned kitchen sir
Er. Aditya said:
i still got the error 7 even i clean cloned kitchen sir
Click to expand...
Click to collapse
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
SuperR. said:
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
Click to expand...
Click to collapse
u have been a rock and we are so glad ur trying to get this to work sir i am attaching a working script and supeR script with recovery log
edit : the modified one again gave that error
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
samsung device ?
SuperR. said:
v3.0.1.9
Changes:
Windows: Fixed b key press not being recognized.
Added a Back option to the root method options.
Only allow key presses that correspond to menu options.
Fixed project name adding an extra superr_ when creating new project from the project selection menu.
Set permissions of configure.sh to 777 instead of /tmp to 755.
@Er. Aditya - This includes the change I sent you in the PM. No clue if it will work for you, but worth a try. No need to extract the system.img again if you extracted using v3.0.1.8. Just change perm types to something else and then back to set_metadata and it will update the updater-script for you.
Click to expand...
Click to collapse
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
SuperR. said:
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
Click to expand...
Click to collapse
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Er. Aditya said:
samsung device ?
Click to expand...
Click to collapse
HTC
Er. Aditya said:
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
Click to expand...
Click to collapse
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
OMJ said:
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Click to expand...
Click to collapse
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently. I could switch this over to 7-zip in Windows if needed now that it is included anyway.
SuperR. said:
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently.
Click to expand...
Click to collapse
i have been having issues since this config.sh has been introduced sir
Er. Aditya said:
i have been having issues since this config.sh has been introduced sir
Click to expand...
Click to collapse
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
SuperR. said:
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
Click to expand...
Click to collapse
[emoji23] [emoji23] Nice!! [emoji41] [emoji41]
Sent from my N9515 using Tapatalk
Er. Aditya said:
I am ready!
Click to expand...
Click to collapse
Here are 3 to try. I may come up with some others if they don't work. When you flash it, we want to see the by-name path on the screen and not get errors. Let me know how it goes