Removes unnecessary applications on your device.
Please note that a factory reset is required after flashing the .zip below, thus still being in beta mode. Any attempt to boot without a factory reset after flashing will get you stuck on the boot animation.
APPLICATIONS REMOVED
Code:
("/system/app/Photos");
("/system/app/MobileManager");
("/system/app/MobileManagerService");
("/system/app/QuickMemo");
("/system/app/QuickMemoService");
("/system/app/SystemUpdate");
("/system/app/AsusBoost");
("/system/app/AsusBrowser");
("/system/app/AsusDrawRes");
("/system/app/AsusMirror");
("/system/app/ASUSWebView");
("/system/app/AWS");
("/system/app/BasicDreams");
("/system/app/BbblerActors");
("/system/app/BRapps");
("/system/app/CleanMaster");
("/system/app/CMSecurity");
("/system/app/DataTransfor");
("/system/app/Dreye");
("/system/app/Drive");
("/system/app/DriveActivator");
("/system/app/eMusic");
("/system/app/Ezding");
("/system/app/eztable");
("/system/app/Galaxy4");
("/system/app/Gameloft");
("/system/app/Gmail2");
("/system/app/Hangouts");
("/system/app/HoloSpiralWallpaper");
("/system/app/Kindle");
("/system/app/KKBOX");
("/system/app/Maps");
("/system/app/MFinanceHK-Bold");
("/system/app/Music2");
("/system/app/MyASUS");
("/system/app/MYingHei_18030-M");
("/system/app/NoiseField");
("/system/app/Omlet-stub");
("/system/app/PCLinkBinary");
("/system/app/PCLinkManager");
("/system/app/PhaseBeam");
("/system/app/PhotoFrameWidget");
("/system/app/PhotoTable");
("/system/app/PuffinBrowser");
("/system/app/RemoteLink");
("/system/app/Syndor");
("/system/app/talkback");
("/system/app/Tripadvisor");
("/system/app/Videos");
("/system/app/WhatsNext");
("/system/app/WidiInputService");
("/system/app/YahooAuction");
("/system/app/YahooECShopping");
("/system/app/YahooMall");
("/system/app/YouTube");
("/system/app/ZenFlash");
("/system/app/ZenTalk");
("/system/app/ZenUIHelp");
("/system/app/ZinioReader");
("/system/app/ZinioSettingsProvider");
("/cache");
("/data/dalvik-cache");
("/data/resource-cache");
("/system/priv-app/ASUSAppInstallationService");
("/system/priv-app/AsusBackup");
("/system/priv-app/AsusEasyLauncher");
("/system/priv-app/AsusFreshGreenTheme");
("/system/priv-app/AsusKidsLauncher");
("/system/priv-app/AsusLiveDemoService");
("/system/priv-app/AsusLiveDemoUI");
("/system/priv-app/AsusLovelyPinkTheme");
("/system/priv-app/AsusPhotoCollage");
("/system/priv-app/AsusTask");
("/system/priv-app/ASUSZenUIPCSuite");
("/system/priv-app/AsusZenUIServices");
("/system/priv-app/CMSKeyV3");
("/system/priv-app/GameCenter");
("/system/priv-app/LogUploader");
("/system/priv-app/MicroFilm");
("/system/priv-app/ShareRimBinary");
("/system/priv-app/SuperNote");
("/system/priv-app/Velvet");
("/system/priv-app/ZenCircle");
("/system/etc/cdrom_install.iso");
("/system/tts");
DEVICES SUPPORTED
ZenFone 2 Laser (ALL VARIANTS)
MARSHMALLOW FOR ZE500KL NOT SUPPORTED YET (SCRIPT WOULD STILL FLASH SUCCESSFULLY)
STEPS
Flash the .zip image via TWRP
Factory reset the device via the "Wipe" menu
Reboot the device via the "reboot > system" menus
Done!
(TO REVERT BACK, FLASH THE FULL STOCK ROM. NO DATA SHOULD BE LOST - not tested yet)
Should any issue arise, or that you would like to feedback on whether more applications should be removed, or to be placed back in, please comment below.
Downloads
https://drive.google.com/open?id=0B6QXDUz9wzc9N0U4Q1ZnMzZmWnM
Updated for firmware version 1.17.40.1234
Hello everybody! I'm really caught up with lots of work and really do not have the time now to do up the script. Also, I just sold my ZenFone to someone else (for a better one) thus being unable to check whether the script (when updated) works alright/perfectly or not, thus, I have decided to close this project entirely. This may be my very first contribution to the XDA community, but nonetheless, the support given was tremendous. Thank you once again.
If any of you are willing to do up an updated version for the script, you may use my script as a base to modify or as a reference.
THIS IS NOT THE ACTUAL SCRIPT
Code:
show_progress(0.750000, 0);
ifelse(is_mounted("/system") == "/system", unmount("/system"));
ifelse(is_mounted("/cache") == "/cache", unmount("/cache"));
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/cache", "/cache");
show_progress(0.050000, 5);
[B]delete_recursive("/xda/Rizzed");[/B]
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/resource-cache");
show_progress(0.200000, 10);
[B]delete_recursive("/system/xda/Rizzed");[/B]
unmount("/system");
unmount("/cache");
ui_print("Bye!");
THIS IS NOT THE ACTUAL SCRIPT
Anyways, happy modding!
Works well on ZE500KG, since it has only 8gb every bit of space is nice. Thanks.
Had to delete 5th line of \META-INF\com\google\android\updater-script to skip verification
Ahhh yeap! Really sorry, I only allowed "Z00L" devices in the code, but did not give further thought for other devices... I will update the file, removing the verification checks for specific device models!
EDIT: Download Updated (new changes applied)
I will be pushing this to a "non-beta" mode this weekend, when I am free. Hopefully it works!
ZE601KL
Hi,
Is this script compatible for ZE601KL?
Alucarde said:
Hi,
Is this script compatible for ZE601KL?
Click to expand...
Click to collapse
It is compatible for all ZenFone 2 Laser variants. Do remember that you need to factory reset after applying this.
Also, are there any applications which you would like me to include/exclude specially for you in this script?
Do tell me if any errors occur.
Have you created a version for marshmallow yet?
andrehsu said:
Have you created a version for marshmallow yet?
Click to expand...
Click to collapse
Not yet as of now.
I will update my post later for ZE500KL devices.
Working for ZE601KL
Rizzed said:
It is compatible for all ZenFone 2 Laser variants. Do remember that you need to factory reset after applying this.
Also, are there any applications which you would like me to include/exclude specially for you in this script?
Do tell me if any errors occur.
Click to expand...
Click to collapse
Hi Rizzed,
I finally flashed TWRP and your Debloater yesterday for my ZE601KL. It is definitely working.
I wonder if you could include the following in your script:
1. (Essentially all the ASUS apps)
2. ASUS Calendar (can be installed via Play Store)
3. Flashlight
4. File Explorer
Thanks!
Someone tried this in ZD551kl? Did this de-bloat helps the performance of battery? Thankyou!
EDIT: Please check my second post.
Tested on my ZE601KL - works ok. Still DON'T forget to do factory reset!
Works fine on me too.
Thanx
Related
Made a new thread for the update.zip versions of the LagFix since i have had people asking me to do that so it doesn't get cluttered up together with RyanZA's fix in his thread.
Only one file included... Will overwrite old root version.
Testet on firmware: (Did a fresh reflash every time)
I9000:
I9000XWJG5 (Eclair - Europe)
I9000XWJM1 (Eclair - Europe)
I9000XWJM5 (Eclair - Europe) (Thanks Peaster111)
I9000XXJP2 (Froyo - Europe)
I9000JPJG8 (Eclair - Africa)
Captivate: (Thanks to Zilch25 for testing)
I897UCJH2
I897UCJH3
Instructions:
(Note that i recommend that you do a fresh reflash through ODIN.)
1. Download the update.zip of your choice and rename it to update.zip.
2. Place it on your internal sdcard.
3. Turn off your phone.
4. Hold down Vol Up+Power button+Home Button for a couple of seconds until u see the galaxy logo .
5. Use the up and down buttons to get to update.zip.
6. Press menu button on update.zip to select it.
7. After install, the phone restarts.
8. Go to the newly installed 'SL4A' application from the app list, open it and choose either LagFix_Ext2.sh or LagFix_Ext4.sh to install the fix.
9. The script should run takes around 2-4 mins before it reboots.
10. First reboot after applying script will take some time as it's moving data around and mounting folders.
Regarding Step 4: What is written is for GT-I9000 version.
For Captivate and Vibrant as other people with that phone.
For Captivate people that are trying this on I897UCFJ6 please read the following post: http://forum.xda-developers.com/showpost.php?p=7939738&postcount=177
Notes:
The current version works on Froyo BUT you can only use the ext2 option as the current kernels in Froyo doesn't support ext4.
Known Bugs:
Got no idea if people still will have problems with changing fonts with ext2 since it works for me.
Credits:
RyanZA - Original bat fix
husq510 - Supplied files needed to enable ext4 support
Zilch25 - For being my test subject on the Captivate board
Donations:
Had a few people ask for donation link so here it's: Donate
Do note though that you don't have to donate if you don't want to.
Changelog:
v.2.3.3
Minor bug fixes.
Put all into one file that will remove old root and reapply new root in the same zip file.
v2.3.2
Removed custom hosts file for ads blocking as that was the problem with SL4A crashing.
v.2.3.1
Changed version of SL4A which should fix the FC that SL4A is giving.
v2.3.0
Scripts redone to do all moving of data on boot to minimize chance of loosing applications and settings.
Firmware check added to scripts to check if your firmware needs GPS Logging fixed.
Removed support for Ext3 as there is no reason to have it since we can use ext4
Added custom apn-conf.xml file for APN settings.
Added hosts file for blocking ads.
v2.2.2
This fix is for Captivates running firmware I897UCJH2
Turns off GPS logging and removes whatever logs that might already have been made
v2.2.1
Fixed old bug with /data/app-private
Added checks to scripts so they check if your system has support for the filesystem you choose
v2.2
Added Check_Space.sh to sl4a
Added support for ext4 (Only works on eclair builds)
Busybox 1.17.1 is NOT required anymore, but is the version i'm including.
v2.1
Based on RyanZA's v2.3
Added support for ext3 (Only works on eclair builds)
Removed support for /dbdata/databases
Changed /data/app-private from mount to symlink
Added two versions of the zip's. One for people who already have a rooted SGS and one that will root the SGS.
v2.0
Based on RyanZA's v2.0
Initial release.
Added support for /dbdata/databases
Added support for /data/app-private
Hey, would you like me to test this on JP3??
Thread
is it possible to undo this lag fix? what scores in quadrant are we expecting with this?
All lag is gone with this or is there some left as I encounter in ryan's? tnks in advance for the hard work
Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)
Thread Astaire said:
Hey, would you like me to test this on JP3??
Thread
Click to expand...
Click to collapse
You are welcome to test it on JP3 if you want to but just remember Clockworkmod Recovery can have problems with applying the update.zip's
rbanaco said:
is it possible to undo this lag fix? what scores in quadrant are we expecting with this?
All lag is gone with this or is there some left as I encounter in ryan's? tnks in advance for the hard work
Click to expand...
Click to collapse
There is a script included to remove the lagfix. From test with stock kernel quadrant score is excepted to be around 2100-2200 with ext2 and 1800-1900 with ext4.
From all the testing we have been doing on this release when fixing bugs there haven't really been that much lag... you might see small lag when opening an application for the first time or when installing an app since we are using a different method this time where we don't move the application's apk's after it's installed, but personally i haven't seen this yet.
omrij said:
Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)
Click to expand...
Click to collapse
Hmm no idea tbh... You might be able to open the zip, replace the files and close it again without losing the signature that it's signed with, but this is something that i haven't tried yet so don't know if it will work.
thanks for the answer.. one more question if you don't mind answering.. what would you advise ext2 or ext4? which provide better performance despite of the score? thank you
rbanaco said:
thanks for the answer.. one more question if you don't mind answering.. what would you advise ext2 or ext4? which provide better performance despite of the score? thank you
Click to expand...
Click to collapse
I would recommend ext4 since it have journaling, which means there is a smaller chance on losing data if your phone lose power by pulling the battery or if the battery reach 0%.
Other people would say ext2 since ext4 might reduce the lifetime on the NAND since it has journaling
I have only tested the ext4 myself pretty much while i have had others to test both ext2 and ext4. Also this is what Zilch25 has posted about ext2 and ext4 on the captivate forum:
Is EXT2 for me?
If you want your Quadrant scores to be bloated beyond belief and don't care if your data spontaneously combusts (Results may vary). Alternatively if you're worried about your NAND wear leveling not being able to handle the strain of EXT4 journaling.
Okay EXT2 is scary, how about EXT4?
You can't afford for your things to get corrupted? Weirdo. Real world performance between EXT4 and EXT2 is barely noticeable if at all, for the everyman this is probably your best bet.
Click to expand...
Click to collapse
omrij said:
Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)
Click to expand...
Click to collapse
i think u can replace or delete files as u like.
i replaced, delted or added files every time before i flashed a new ROM, like HACKECLAIR or SamSet.
Works well.
applying ext4 gives me the stopped unexpectedly google error
Yeah I can second that... after a full wipe SL4A is giving me FC's now too =P
Just wanted to add:
EXT2 may be less safe than EXT4, but to-date, there has been no reports of any corrupt or lost data using the EXT2 fixes. This is over a pretty huge sample over a fairly long period. Not to say there are no problems with EXT2, but there has not been any impact to anyone for using EXT2 as yet.
Other than that, awesome job Tayu! Looks great!
yep, i get the force close for either script from sla4
OK ill reupload with the old version of sl4a then.
Im still not sure wether i should go for Ryan's one-click .apk fix or this one.
Anyone tested this one on I9000XXJM2? wich is stock firmware for me.
Tayutama said:
OK ill reupload with the old version of sl4a then.
Click to expand...
Click to collapse
v2.3.1 uploaded which replaces sl4a_r1 with sl4a_r0 which was the one used in the older versions of the fix. Should fix the problem with getting force close
Tayutama said:
v2.3.1 uploaded which replaces sl4a_r1 with sl4a_r0 which was the one used in the older versions of the fix. Should fix the problem with getting force close
Click to expand...
Click to collapse
Applying it now, I'll let ya know how it goes
do i need to remove the previous sl4a?
A.VOID said:
do i need to remove the previous sl4a?
Click to expand...
Click to collapse
would be the best as they each got a different name.
If you got root explorer you can remove it from /system/app
It's called: sl4a_r1.apk
Tayutama said:
would be the best as they each got a different name.
If you got root explorer you can remove it from /system/app
It's called: sl4a_r1.apk
Click to expand...
Click to collapse
Yeah you might need to... I just reapplied without removing it and only r1 shows up =P
Changelog -
v.01
-Removed: Torch.
-Installation: shortened ascii on updater-script
-Fixed radio
-Fixed Camera (Use ActionSnap)(You can get MIUI camera viewfinder to work it just wont' write the files correctly atm. After opening MIUI Camera change settings > picture size to 3MP)
-Broke altdrawer. Sorry. APK invalid. remove from system/app and install from attatchment if you want it; i'll fix it for .02
-Maybe some more things...
v.00
-Ported
2nd update up..
No camera, Sorry. Havn't been able to test wifi. Will remove torch.apk and various others... Would also like to hcange data config for launcher to default 3d cube animations and to default the appdrawer to grid rather than list...
Lots of Espanol > Engles translations still needed...
Credit to: MIUI team, XDA, Rdanner, Jorgonv, sferrariba(defy thread poster)
Link to original thread I found.
http://forum.xda-developers.com/showthread.php?t=1238592
Download:
v.01http://www.mediafire.com/?fbg3860xvcr5is7
v.00http://www.mediafire.com/?ig4r0oes9m4ja8w
Wipe your data/cache and dalvik just incase,
apply update
I'd like to go to that day that the camera works in gingerbread roms for bravo!!
I really would like to use gingerbread in bravo, Im coming from Cliq XT and Backflip (Well, I still have them both) and they have fully working gingerbread roms!
Well the only thing we can do is wait till @rdannar or some else get the camera working!
Ya i'll work on the camera too soon i'll be honest he's going to have a better clue than I am...
I found a 2.2 sense rom for the defy i am going to try to port so that that way we can have a little Rosie/SenseUI too...
after that i'll probably try to see whats up with the camera,
i believe if i can ddms the forceclose on the camera i can read up a bit on that too and see whats up; i pmed rdanner about what camera modifications particularly he noticed were needed for his msgingerblur cause that's android 2.3.4 aswell,
for a camera i suggest msgingerblur or the stock froyo diet thing rdanner made
rubbachicken said:
Ya i'll work on the camera too soon i'll be honest he's going to have a better clue than I am...
I found a 2.2 sense rom for the defy i am going to try to port so that that way we can have a little Rosie/SenseUI too...
after that i'll probably try to see whats up with the camera,
i believe if i can ddms the forceclose on the camera i can read up a bit on that too and see whats up; i pmed rdanner about what camera modifications particularly he noticed were needed for his msgingerblur cause that's android 2.3.4 aswell,
for a camera i suggest msgingerblur or the stock froyo diet thing rdanner made
Click to expand...
Click to collapse
At this point, people need to stop relying on others to get a Defy rom, any Defy rom (CM7 nightlies, MIUI weekly update, regular roms that regular developers made), to work on the Bravo. It is a very simple process.
1) Open ROM in Winzip
2) Delete all the folders and files except for "system"
3) Download this
4) Extract files "motorola" and "META-INF" to a known location
5) Move extracted "META-INF" to / (root) of the ROM
6) Delete folder "motorola in /system/ect
7) Move extracted "motorola" to /system/ect
Not to be a **** but did anyone have anything useful to post?
Fixed camera same story as w/ rdanners only works w/ 3rd party so far miui camera not working actionsnap is though new upload coming soon
rubbachicken said:
Fixed camera same story as w/ rdanners only works w/ 3rd party so far miui camera not working actionsnap is though new upload coming soon
Click to expand...
Click to collapse
Can't wait to try it with the 3rd party app workaround. And thank you! Seems now a days too many people don't appreciate the work people put out there if it isn't perfect. Up until now no rom is perfect. I have a Droid Incredible and the dev community is pretty big, a lot of roms for it and all still have bugs here and there. Keep up the work. I know there is a lot of people out there that don't really post but really appreciate any work you are doing for the Bravo community
One thing I'm having an issue with is settings for the apks...
for example when you select a 3d effect for the launcher, it saves the file in /data/data,
i can get /data/apps to copy over frm the update-script but all attempts so far to get /data/data over havn't worked (since it's copying /data i assumed it would copy /data and it's subdirectories aswell), i've tried to unpack the apks and change the default settings then repack them, that's how I broke altdrawer in .01...
Does anyone have a thought on this? is it likely there is a script clearing /data/data on first boot?
Primarily I want to make folders for the launcher, and put all the icons in them... I found the workspace.xml file that lists the x/y coords of the icons etc... but I can't seem to get any changes to affect it ... (This was found inside the apk)
BravoMotorola said:
At this point, people need to stop relying on others to get a Defy rom, any Defy rom (CM7 nightlies, MIUI weekly update, regular roms that regular developers made), to work on the Bravo. It is a very simple process.
1) Open ROM in Winzip
2) Delete all the folders and files except for "system"
3) Download this
4) Extract files "motorola" and "META-INF" to a known location
5) Move extracted "META-INF" to / (root) of the ROM
6) Delete folder "motorola in /system/ect
7) Move extracted "motorola" to /system/ect
Click to expand...
Click to collapse
I agree on this. While it won't get the camera working, it is still a more proper way of making a port. Still reading up on android development (as I got older I get less inclined to do something without understanding what I am doing first) but as a system builder I know it's better to make a new system from scratch rather then taking an image from one machine and sticking it on another. Too many things break that way
Sent from my HTC Glacier using XDA App
Sorry haven't gotten around to pm and stuff.. work a lot on weekends
@ rubbachicken
What did you do to get camera working? I think I know but would be good for others to know also.
For copying data you need to first delete data recursive then make sure the correct folders have correct permissions after you copy them in the script.
Or you may have to make a tmp folder and do a package extract to push folders on but set permissions to write into data
Not sure about permissions, then download yaffs explorer from market and it has a setting to show what permissions are needed for each file and folder.
@dontbejeff
You are right... it is better to start from a vanilla build made for bravo. But that is some serious coding for a device that doesn't even have a leaked gingerbread rom like defy. If we ever had a leak or something similar then camera would be easy...
That is how I figured out this much of camera by working with froyo stock roms first (T-Mobile). To figure out what is different in the roms.
Sent from my MB520 using XDA App
rdannar said:
Sorry haven't gotten around to pm and stuff.. work a lot on weekends
@ rubbachicken
What did you do to get camera working? I think I know but would be good for others to know also.
For copying data you need to first delete data recursive then make sure the correct folders have correct permissions after you copy them in the script.
Or you may have to make a tmp folder and do a package extract to push folders on but set permissions to write into data
Not sure about permissions, then download yaffs explorer from market and it has a setting to show what permissions are needed for each file and folder.
@dontbejeff
You are right... it is better to start from a vanilla build made for bravo. But that is some serious coding for a device that doesn't even have a leaked gingerbread rom like defy. If we ever had a leak or something similar then camera would be easy...
That is how I figured out this much of camera by working with froyo stock roms first (T-Mobile). To figure out what is different in the roms.
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
YES, that information would be great. Then we could get working camera on CM7 and other Defy roms. PLEASE, rubbachicken give that info!
ui_print("[*] Copying Apps");
package_extract_dir("data", "/data");
ui_print("[*] Setting Permissions");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
set_perm_recursive(1000, 1000, 0777, 0776, "/data/local");
make sure you use the correct mount for the data wich depends on what updater binary you are using
i am pretty sure he moved over the com.camera.jar
the etc/camera permissions files.
and the 3 camera etc files in main etc folder.
cheers
rdannar said:
ui_print("[*] Copying Apps");
package_extract_dir("data", "/data");
ui_print("[*] Setting Permissions");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
set_perm_recursive(1000, 1000, 0777, 0776, "/data/local");
make sure you use the correct mount for the data wich depends on what updater binary you are using
i am pretty sure he moved over the com.camera.jar
the etc/camera permissions files.
and the 3 camera etc files in main etc folder.
cheers
Click to expand...
Click to collapse
I must still be a major noob, what's the first part of your post about?
BravoMotorola said:
I must still be a major noob, what's the first part of your post about?
Click to expand...
Click to collapse
ui_print("[*] Copying Apps");
displays: Copying Apps...
package_extract_dir("data", "/data");
extracting files from .zip directory "data" to phone directory "/data"
ui_print("[*] Setting Permissions");
displays: Setting Permissions...
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
setting permissions for all files is "/data/app"
set_perm_recursive(1000, 1000, 0777, 0776, "/data/local");
setting permissions for all files is "/data/local"
Here is some MIUI straight from MIUI team. It has the camera working (ALL RUBBACHICKEN'S WORK, and in the same condition) And it is full English (fixes one of his problems)
MIUI.us_MB520_1.8.19_Eng.zip
All credit to rubbachicken
I have to be honest i'm not sure exactly what I did ... I copied over the etc/permissions files that were relevant to the camera, also replaced all the libsocameraclient and whatever else I could find, the mot_ise_imager or something like that was replaced too, i'll make a more specific list of files tomorrow...
I was up till 5am last night so i'm kinda on break today haha...
thanks for the help w/ the permissions etc, i wasn't sure what permissions to set for the /data/data
Info for what I did to get the camera working; (As best as I can remember, and applied to CM7 and tested.)
found here;
I have recieved a bit of credit for this from the bravo community and i'd like to just mention real quick that i primarily just copied and pasted, if files were edited to make this work beyond which files are there, that was probably rdanner or walter devs... I have a feeling I gathered some files from rdanners gingerblur since it was working....
Maybe that's where I got the com.motorola.camera.xml and .jar found in /etc/permissions and /system/framework
I know i directed my attention to that because it's a GB rom w/ camera working.
Anyway, theres the instructions I followed...
Great job doing miui. Main files is mot. Sh file in etc. then egl libs.. At this point the camera.jar does nothing... Permissions probably dont make huge difference. Egl, gles. Gls files all do.
Surface flinger.so does also but that is okay due to similarities with defy
Sent from my MB520 using XDA App
dsixda's Android Kitchen - Now for Samsung Galaxy S
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of version 0.178, you can now create your own Galaxy S ROMs with the kitchen.
I'd like to thank Perka for testing and providing feedback, and also for giving me some ideas through his tutorial in his Ultimate ROM Cooking Guide.
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S with a ClockworkMod custom recovery. The kitchen supports the GT-I9000, but should also support most of its variants, such as the Captivate, Fascinate, Vibrant and Epic.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
IMPORTANT (DO NOT IGNORE THIS STEP): To verify your variant of the Galaxy S works in the kitchen, read this post.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
factoryfs.rfs (and optionally: cache.rfs, zImage)
PDA.tar.md5 (and optionally: CSC.tar.md5, PHONE.tar.md5)
PDA.tar (and optionally: CSC.tar, PHONE.tar)
TAR/ZIP file containing factoryfs.rfs (optional: cache.rfs, zImage, modem.bin)
TAR/ZIP file containing PDA.tar and others
TAR/ZIP file containing PDA.tar.md5 and others
Custom ROM:
ZIP file originally created by the kitchen from the stock firmware (NOTE: The kitchen does NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a factoryfs.rfs but then didn't include the cache.rfs, then you have the option to add a cache.rfs later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Optional: Add a rooted kernel (zImage) to the base of your working folder
You can create a ROM without a zImage and thus keep the existing kernel on your device, although keep in mind that a newer ROM may not work with a kernel meant for older ROMs!
If you use the stock kernel (zImage), you can always replace it later with the CF-Root kernel or any other custom/rooted kernel. Just replace the stock zImage anytime before you build the ROM.
Optional: Add a modem.bin to the base of your working folder, or remove the existing modem.bin if you don't want it. You can flash the ROM with or without a modem.bin.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers, and to prevent confusion, please only discuss Samsung Galaxy S in this thread!
Most of all, have patience, take your time and enjoy!!
thanks for info mate exactly wat im looking for
cheers
Thx for this. Working very well.
Very nice guide
Just what i was looking for great
Sent from my GT-I9000 using xda premium
Thanks works very well! *5 stalls *
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Gvdn said:
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Click to expand...
Click to collapse
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
dsixda said:
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
Click to expand...
Click to collapse
So no matter what i try it wont work with kitchen? Damn too bad i was starting to know my way around it now
Kitchen made the whole rom without a problem tho. Using the boot.img option and following Perka guide. Just seems its not generating the Meta file correct.
Do u have any idea to what i asked earlier? If there is only 3 different update-binaries , can i get all 3 and test em out and 1 will work for sure or it wont work no matter what?
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
dsixda said:
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
Click to expand...
Click to collapse
Ok thx alot. Sadly no subforum for Gio
CWM issue
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
krazykipa said:
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
Click to expand...
Click to collapse
I'm having the same problem here with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS, I tried to move to DarkCore_4.0_JVS and the device get into reboots (just after activating lagfix).
its 2 days now that im working on stock rom and trying only to root and deOdex... help?
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
bhundven said:
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
Click to expand...
Click to collapse
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
dsixda said:
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
Click to expand...
Click to collapse
Looks like the SGH-T959V file exists. Thanks for helping me figure that out!
I am having an issue with wi-fi not be able to connect after i have flashed my build.. and thats about it. I'm not sure whats causing it any ideas?
EDIT:
Was the updater-script, i swapped it out with another and all is well.
There are problem with kernels. I can't change?
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
xtrem88 said:
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
Click to expand...
Click to collapse
If it's basically the same device then it should support it. Just make sure you have an entry in the kitchen for the ro.product.device value. See the note in the 2nd step in Post #1.
MultiROM lets you install multiple ROMs into subfolders, just by flashing them using a modified TWRP.
This is an unofficial port of MultiROM originally developed for the Nexus series to our beloved TF300T.
Big thanks @Tasssadar for the original work!
THIS IS AN EARLY VERSION OF THIS PORT, NOT ALL FEATURES ARE FULLY TESTED.
But please test and give feedback, so I can eventually remove above line.
Features
Run a primary Android ROM from the normal partitions.
Run multiple secondary ROMs from subfolders on an SD card or on an external USB stick/drive.
Easily add/update your primary and secondary ROMs using a modified version of TWRP.
Install Ubuntu and Ubuntu Touch as secondary ROMs Not supported yet.
And more...
Changes vs. official MultiROM
This section is mostly useful for people using MultiROM on another device. New users can safely ignore it.
My first test - installing a plain CM 11, installing MultiROM, and then installing OmniROM with its own kernel - failed gloriously. The reason was that the official MultiROM re-uses the kernel of the currently installed Android system and that kernel does not include the kexec hardboot patch required for MultiROM to work properly.
The beauty of MultiROM is that - once installed with a proper kernel - it allows an average user that has never heard about kexec and never installed a custom kernel to run multi-boot at the touch of a finger. So I decided that my first simple use case must be supported.
The obvious solution was to ship a working kernel with MultiROM, save the currenly installed kernel for the primary ROM and boot that via kexec. The idea is to sacrifice another 10 secs on booting the primary ROM for making MultiROM much easier to install and to use. However, this decision led to several changes in the TWRP user interface:
The "share kernel with primary ROM" option was removed. Each ROM has its own boot image and is always booted via kexec.
The "Inject current boot sector" on the MultiROM screen button was replaced with a "Reinstall" button. Use this, if you have overwritten the boot sector, for example via fastboot. Mind, reinstalling MultiROM will save the current boot partition and use it for booting straight into the primary ROM, so better make sure this works, before running reinstall, or you won't be able to boot into your primary ROM after reinstallation.
The "Add/Remove boot.img" button on the ROM management screen has been replaced with "Replace boot.img" and can be used to easily install a custom kernel for that ROM.
Looking forward to your feedback on this major change!
Downloads
Downloads are available from the "Downloads" tab at the top of the page.
MultiROM installer including the modified TWRP:
multirom-vXX-YYYYMMDD-UNOFFICIAL-tf300t.zip
TWRP for MultiROM (not needed, if you use the installer):
twrp-multirom-vXX-YYYYMMDD-UNOFFICIAL-tf300t.blob
Installing and Upgrading MultiROM
Please read the following instructions carefully, and make sure you understand each step and what it will do to your tablet. The steps are working for me, but you are ultimately responsible, for what you are doing with your own tablet. I will not be responsible, if you brick your tablet, or if your wife gets angry at you for being too preoccupied with your tablet.
Make a backup!
MultiROM will modify your system, and if anything goes wrong, this backup will be more than helpful.
Check the version of your bootloader.
On the bootloader screen, check the version shown on the top left. MultiROM was ported and tested on version 10.6.1.27.5. If your bootloader version is 10.6.1.27.1 or 10.6.1.15.3 you should have no issues. Version 10.6.1.8 might work, but is likely to cause issues; upgrading is highly suggested. For any other version, make sure you first upgrade your bootloader, or you risk ending up with a brick,
Flash the lastest multirom-vXX-YYYYYYYY-UNOFFICIAL-tf300t.zip
Reboot right away!
Make sure you see the blue progressbar on the first boot screen and you see another automatic reboot.
Then the MultiROM boot screen should show up.
Now you should be able to boot your primary ROM via MultiROM. For next steps, check out "Installing ROMs" in the next post.
Uninstall MultiROM
The uninstaller for the official MultiROM has not been ported yet, but you can get rid of MultiROM following these steps:
Flash your favourite (not MultiROM) recovery.
Restore your boot partition from a backup or re-flash your ROM.
Remove the "multirom" folder on the sdcard.
The latter is optional. You may keep it around for trying MultiROM again later.
Changes
2014-03-16:
Fixed MultiROM reinstallation from TWRP.
Some fixes for swapping primary/secondary ROMs.
Some fixes for primary ROM initrd.
Added support for Ubuntu Touch (needs upcoming manager app).
2014-03-02:
Support secondary ROMs on SD card (not fully tested).
Use packaged initrd instead of the primary ROM's.
Some bug fixes.
2014-02-13:
Allows flashing 4.2-based ROMs without removing the assert line in the updater-script.
Several bug fixes for more stability.
Note that changes may be documented, before the downloads are available. Please check back a little later in that case.
Future Work
In no particular order:
Provide uninstaller.
Add the missing features listed above.
Fix TWRP for encrypted filesystems.
Allow replacing the kernel for any ROM, keeping the ramdisk.
Remove unnecessary drivers (net, sound, camera) from the kernel (currently breaks building the kernel).
XDA:DevDB Information
MultiROM for TF300T, a Tool/Utility for the Asus Transformer TF300T
Contributors
f69m
Version Information
Status: Alpha
Created 2014-02-11
Last Updated 2014-03-16
Installing ROMs
Custom 4.2- and 4.4-based ROMs
To install/update your primary ROM, just flash it as usual with the modified MultiROM TWRP, using "Install" from the main screen.
Installing a secondary ROM is just as easy, but use:
Advanced > MultiROM > Add ROM
You can update a secondary ROM by flashing it from the ROM management screen, using;
Advanced > MultiROM > List ROMs > [select your ROM] > Flash ZIP
OTA updates using the update manager coming with your ROM should work fine for both primary and secondary ROMs.
Note: It is no longer necessary to remove the assertion from a 4.2 updater-script.
Gaps, SuperSU, etc.
You can flash additional ZIP files for a secondary ROM from the ROM management screen, using:
Advanced > MultiROM > List ROMs > [select your ROM] > Flash ZIP
Asus Stock ROM
Asus stock ROM has a different installer and won't work the same way as custom ROMs.
Here are the steps to install stock ROM as your primary ROM:
Sorry, I have not tested this myself yet, please let me know, how it works out.
Unzip the Asus ROM twice to get the blob.
Flash the blob using fastboot.
Boot into stock ROM.
Re-install the modified TWRP using fastboot (use the separate download).
In TWRP: Advanced > MultiROM > Reinstall.
This should give you a working MultiROM setup with stock ROM as your primary ROM.
If you need more detailed instructions on the first two steps, please refer to the guides in the General section.
Ubuntu Touch
Coming soon...
Ubuntu
Not working yet.
Notes on Specific ROMs
CROMi-X 5.3
Don't try to install CROMi-X as a secondary ROM. It has an amazing installer, but that will nuke your primary ROM's /system partition.
Trouble-shooting
If your primary or one of your secondary ROMs is not booting properly, it can help to restore the boot partition of the primary ROM and then do a clean reinstall of MultiROM.
No worries, you can move your installed secondary ROMs to the side and move them back later.
First try restoring the boot partition from your latest backup, before installing MultiROM and reboot.
If your device boots cleanly into your primary ROM, without showing the MultiROM boot screen, you can skip ahad to step 3.
Next try flashing an unmodified recovery, re-flash your primary ROM and reboot.
If your device boots cleanly into your primary ROM without showing the MultiROM boot screen, you are ready to go to step 3.
Otherwise you should post your issue.
Use a root terminal or a root exlorer to remove the folder /data/media/0/multirom.
Alternatively you can rename that folder, keeping your installed ROMs.
Note: though this folder is on the sdcard, you have to use the path given; trying to use /sdcard or /storage you will get "permission denied", when trying to remove or rename the folder.
Reflash the latest multirom-v*.zip and reboot.
Make sure you see the blue progressbar on the first boot screen and you see another automatic reboot.
Then the MultiROM boot screen should show up.
Try booting your primary ROM. It should now start cleanly.
Try installing a secondary ROM, or move it back to /data/media/0/multirom/roms/ from the folder you renamed above.
Just moving back the folder will make it show up on the MultiROM boot screen.
Please read and follow each step carefully.
If these steps do not make all your ROMs boot properly, please post about your issue in this thread.
Source Code Repositories
The easiest way to build MultiROM is using my manifest following the build instructions below.
Here is a list of the MultiROM-specific repositories that can be built by adding them to the OmniROM tree:
Latest manifest:
https://github.com/f69m/android
MultiROM (check out to "bootable/multirom"):
https://github.com/f69m/multirom
TWRP for MultiROM (check out to "bootable/recovery"):
https://github.com/f69m/multirom-twrp
libbootimg (check out to "external/libbootimg"):
https://github.com/Tasssadar/libbootimg
TF300T device config (check out to "device/asus/tf300t"):
https://github.com/f69m/android_device_asus_tf300t
TF300T kernel (check out to "kernel/asus/tf300t"):
https://github.com/f69m/android_kernel_asus_tf300t
Look out for branches named "multirom-*" in above repositories.
Please check the manifest for the latest stable branch.
Build Instructions
Using my manifest makes it easy to check out the MultiROM repositories and a small part of the OmniROM tree needed for building.
Code:
repo init -u git://github.com/f69m/android -b multirom
repo sync
manifest/pick-cherries.sh
source build/envsetup.sh
lunch mrom_tf300t-userdebug
make -j4 multirom_zip
Sweet! Thanks man, this looks pretty cool!
Sent from my SGH-T999 using xda app-developers app
Finally, first download is up!
Let me know, how it works for you.
Thanks for your work.
Now I use CROMi-X 5.3 ROM. If I install MultiROM and TWRP for MultiROM, the exist CROMi-X 5.3 ROM can keep on primary ROM??
z1022 said:
Now I use CROMi-X 5.3 ROM. If I install MultiROM and TWRP for MultiROM, the exist CROMi-X 5.3 ROM can keep on primary ROM??
Click to expand...
Click to collapse
Absolutely, just flash the multirom-*.zip file (includes TWRP), and you should be able to boot into CROMi-X via MultiROM.
But I have not tested with CROMi-X yet, so make sure you have a backup!
Sent from my TF300T using Tapatalk
Thanks
I will try later and report back.
CROMi kernel should be not included the kexec. Can I use the Multirom to install second ROM ??
z1022 said:
I will try later and report back.
Click to expand...
Click to collapse
Great, looking forward to hearing about your experiences.
CROMi kernel should be not included the kexec.
Click to expand...
Click to collapse
The CROMi-X kernel does not need kexec for my MultiROM port to work. This is different from the official MultiROM for Nexus. See post #1 on more details.
Can I use the Multirom to install second ROM ??
Click to expand...
Click to collapse
Of course, that's the whole idea!
Check post #2 for instructions.
Sent from my TF300T using Tapatalk
Hi f69m!
1000 THANKS!
I successfully installed this MultiROM on TF201 with bootloader from TF300T v. 10.6.1.27.1 ! :laugh:
As Primary ROM i have NIGHTLY CM11 for TF300T. As "virtual" ROM i installed the same ROM (i want to examine the new GRIMKERN_KitKat).
All works properly with 1 exception:
Don't works the touchscreen during "blue" window for ROM-selection.
So I had to specify the "default" firmware in TWRP.
Dasdranamin said:
Hi f69m!
1000 THANKS!
I successfully installed this MultiROM on TF201 with bootloader from TF300T v. 10.6.1.27.1 ! :laugh:
Click to expand...
Click to collapse
Wow, amazing!
All works properly with 1 exception:
Don't works the touchscreen during "blue" window for ROM-selection.
So I had to specify the "default" firmware in TWRP.
Click to expand...
Click to collapse
Hmm, not quite sure, what you mean with "blue" window. You mean the MultiROM menu that comes up after boot? If yes, could you send me a copy of /proc/last_kmsg after booting your ROM? It has the kernel log of MultiROM; maybe I can spot the issue there.
Sent from my TF300T using Tapatalk
f69m said:
Wow, amazing!
Hmm, not quite sure, what you mean with "blue" window. You mean the MultiROM menu that comes up after boot? If yes, could you send me a copy of /proc/last_kmsg after booting your ROM? It has the kernel log of MultiROM; maybe I can spot the issue there.
Click to expand...
Click to collapse
Yes. That's what I meant.
Dasdranamin said:
Yes. That's what I meant.
Click to expand...
Click to collapse
Thanks for the log. It is a different touchscreen, but don't see anything that should cause issues.
In TWRP touch is working fine?
I'll have a look at the differences in the input handers and will probably send you a special version with more logging.
Sent from my TF300T using Tapatalk
f69m said:
Thanks for the log. It is a different touchscreen, but don't see anything that should cause issues.
In TWRP touch is working fine?
Click to expand...
Click to collapse
Yes, in TWRP touch works without any problem!
I'll have a look at the differences in the input handers and will probably send you a special version with more logging.
Click to expand...
Click to collapse
That would be great! Thanks in advance!
f69m said:
Great, looking forward to hearing about your experiences.
The CROMi-X kernel does not need kexec for my MultiROM port to work. This is different from the official MultiROM for Nexus. See post #1 on more details.
Of course, that's the whole idea!
Check post #2 for instructions.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
z1022 said:
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
Click to expand...
Click to collapse
I successfully installed just now on TF201 Omni 4.4.2. ROM TF300T Homebuild versions [20140126] (it's last ROM with MultiWindow feature) + Gapps Mini Modular Package.
All works properly. :good: MultiWindow too.
how long omni finished the booting.
---------- Post added at 11:59 PM ---------- Previous post was at 11:50 PM ----------
z1022 said:
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
Click to expand...
Click to collapse
Try CM11 in second ROM. still stick in CM11 booting screen.
z1022 said:
how long omni finished the booting.
Click to expand...
Click to collapse
First time about 5 min (with Gapps).
Next times about 2 min.
Nice! cant wait to try this, thanks for your hard work!
Hi f69m,
I found: in "MultiROM menu that comes up after boot" I can select a ROM by VOLUME UP/DOWN and confirm by POWER (like in "old" CWM). :laugh:
Firstly a big thanks to @Ryuinferno for this very interesting thread:
http://forum.xda-developers.com/showthread.php?t=1933849
Unfortunately, above script does not work in case of Samsung Qualcomm (Snapdragon) devices running 4.4.2 KitKat stock kernel.
Fortunately @shazzl in post #438 suggested a very interesting idea to start run-parts using /system/etc/init.qcom.post_boot.sh
I tuned, nuanced and implemented this idea in real life by creating my add_initd.sh script. I have created also a CWM/MOP flashable file to apply this modification as simple as possible
Requirements:
- a rooted Samsung Qualcomm (Snapdragon) device
- custom recovery (CWM/TWRP) or Mobile Odin
- Busybox installed (every custom ROM should contains it, in case of (CF-Auto-)rooted pure stock - just install it using THIS APP from Play Store)
Download link:
add_qcom_initd.zip
Installation:
1. Custom recovery (KNOX 0x1) - open file using "Install Zip" option and confirm "Yes - install..."
2. Mobile Odin - open file using "OTA/Update ZIP" option. UNTICK Everroot! This type of installation let you keep KNOX 0x0 if you still kept this flag (thanks to udating every ROM by Mobile Odin PRO only)
NOTE:
I tested it only on Galaxy Note 3 (N9005), but I think it should work on any Samsung Snapdragon device (eg I9505).
Installation should be safe because I've used safe mount command in updater-script:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
I'm not sure about the update-binary, so please feedback if it works
In case of problems - I will create a fixed ZIP compilation especially for I9505
Double thanks:
a, great advance for users with knox 0
b, great thx for especifiying a way of installing that do not triggers knox :highfive:
Indha Lezzio said:
Double thanks:
a, great advance for users with knox 0
b, great thx for especifiying a way of installing that do not triggers knox :highfive:
Click to expand...
Click to collapse
Sorry? You have to have custom recovery which triggers knox.
Sent from my GT-I9505 using XDA Premium 4 mobile app
I rooted my 4.3 with saferoot, upgraded to kk with mop and my Knox is 0 and my phone is rooted . And with mop and this script I can have init.d support without tripping Knox as stated by the OP. Will test at home
Enviado desde mi GT-I9505 mediante Tapatalk
Tested and works very well on my Galaxy S4 I9505 Kitkat, no bootloops or anything! And I still retain my Knox 0x0 after the flash! Thank you very much alexndr!