wp_mod: Module to disable system write protection
This is a kernel module that disables write protection on the system partition while running the stock kernel.
HTC changed the MMC_MUST_PREVENT_WP_VIOLATION code to make it much harder to crack. I had to redo the module completely, so this is experimental. In the past, it was a simple matter of changing a variable, now we have to replace a function in the kernel so it returns something different, causing the kernel to skip over the write protection code.
I would caution against loading the module after attempting to make changes to the system partition. It could end up corrupting the filesystem. If the module is loaded at boot, there should be no worries.
This module will probably need to be updated to load with future kernels when they are released.
Please consider a donation to support ongoing development
Many thanks to those who have donated!
Download:
wp_mod for GPE Marshmallow 6.0 can be found here:
http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
Sense 4.4.4 (thanks @migascalp):
http://www.mediafire.com/download/4vyqslnc4crsnto/wp_mod_3.28.401.6.zip
Sense 4.4.3 (2.22 base):
wp_mod.ko
Sense 4.4.2:
wp_mod.ko
GPE 4.4.4 (thanks to @italyforever):
wp_mod.ko
GPE 4.4.2:
wp_mod.ko
Installation:
Wait for it to be implemented in your favourite ROM
* or *
Copy the module to your device, and type
Code:
su
insmod /location-where-you-copied-it/wp_mod.ko
Changes:
April 2, 2014 - wp_mod 4.1
-only return non-existing partition number if called by generic_make_request_checks
-remove exit from module (we don't want to be able to unload it)
-clean up code
March 31, 2014 - wp_mod 4.0
-new method for HTC One m8
Source:
https://github.com/flar2/wp_mod
Module was compiled against m8 Google Play Edition source. Some symbol CRC checks had to be hexedited in the compiled module to match the stock kernel. Thanks to Michael Coppola for example of function hooking on arm: http://poppopret.org/2013/01/07/suterusu-rootkit-inline-kernel-function-hooking-on-x86-and-arm/#arm
Nice Job!!!! this is awesome
AWESOME! Thank you! Will test and see
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Confirmed working here. I was able to delete stuff with titanium backup and it stuck after reboot. Thanks so much!
Sent from my M8 via XDA Premium app
So as an end user, before it gets baked into ROMs, we need to load this after each boot?
Worked here as well on the AT&T variant. I added the line to the install recovery script that chainfire uses for SuperSU and it loads it on boot now
what i did was run the insmod command in terminal emulator, made the system rw/ edited /system/etc/install-recovery.sh and added the insmod line in there Sure it would be easier if I had init.d support but I'm on stock and am too lazy to change to a custom rom
You guys are awesome.
Awesome work....Can now scratch my theming itch
Sent from my unknown using Tapatalk
gjlowe said:
So as an end user, before it gets baked into ROMs, we need to load this after each boot?
Click to expand...
Click to collapse
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
mattman83 said:
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
Click to expand...
Click to collapse
Hmmm..I ran the command in the OP and rebooted and when I try to create a directory in / it says that it is a read only file system.
graffixnyc said:
Worked here as well on the AT&T variant. I added the line to the install recovery script that chainfire uses for SuperSU and it loads it on boot now
what i did was run the insmod command in terminal emulator, made the system rw/ edited /system/etc/install-recovery.sh and added the insmod line in there Sure it would be easier if I had init.d support but I'm on stock and am too lazy to change to a custom rom
Click to expand...
Click to collapse
Can you share your zip please
Sent from my HTC One_M8 using Tapatalk
gjlowe said:
Hmmm..I ran the command in the OP and rebooted and when I try to create a directory in / it says that it is a read only file system.
Click to expand...
Click to collapse
You need to run it each time you boot, until it is correctly working as init.
mattman83 said:
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
Click to expand...
Click to collapse
Electronic Punk said:
You need to run it each time you boot, until it is correctly working as init.
Click to expand...
Click to collapse
Ok then, I guess @mattman83 was referring to when we have this in custom ROMs?
gjlowe said:
Ok then, I guess @mattman83 was referring to when we have this in custom ROMs?
Click to expand...
Click to collapse
Yup, I have already added it to my copy of ARHD 3.x and it is working great, so look for a release as soon as Mikes connection allows!
im on the vzw m8. we have temp 'root access' to /system/xbin. is it ok to do this as well? which will make /system writable?
-4ndr01d- said:
im on the vzw m8. we have temp 'root access' to /system/xbin. is it ok to do this as well? which will make /system writable?
Click to expand...
Click to collapse
I don't know what method they use to get root access to /system/xbin. This is probably compatible, if it loads with the Verizon kernel. Backup all your data and try it.
flar2 said:
I don't know what method they use to get root access to /system/xbin. This is probably compatible, if it loads with the Verizon kernel. Backup all your data and try it.
Click to expand...
Click to collapse
jcase has got us root access ...its only writable to /system/xbin and has to run on every boot. the app used is called WeakSauce
but i was thinking. once my phone boots up, i wait til i have root access, then download the file, place it in the correct directory, download terminal emulator and run the commands. then /system becomes writable until next reboot?
@flar2 nice job as always man!! :good:
awesome awesome awesome
looking forward to elementalx on the m8!
For users who have init.d support in their ROM. Flash this and your good to go
https://mega.co.nz/#!XINyDIrB!QcdP3sZJjgKAivkEa7iN8Jusx0e78T1rpA5PT7VGAxQ
Sent from my Note 3
Related
This is something I realized when the init.d hack by naven was posted, it plain didn't work for me, and after some investigation i discovered that not all busybox versions had the run-parts applet.
It has come to my attention to that many users may not have the proper hack installed, at least the ones using my scripts, I had them check in /data for the zipaplign log and it was in fact not there.
I got it working by modding navens hack. Credit goes to him for his discovery.
Here is a link to the flashable zip. If you are using my scripts, check in /data for the zipalign log, if you don't have one, just flash this zip, reboot, and check again.
http://www.sendspace.com/file/9g6ngz
Thanks!
Edit (8/31/2011): Just so there is no confusion, this is not my new Speedy script, this is just a re-hack for init.d originally discovered by naven. This will just help those of you having problems with his hack. Obviously you need to be rooted and have recovery bootstrap.
Just flashed your zip. Log file in /data
Welcome back! Thanks for your work on the X2.
Sent from my DROID X2 using xda premium
Grapejelly!!
Sent from my DROID X2 using xda premium
Worked perfectly
Sent from my DROID X2 using XDA App
Is this a new version of your script then?
Do we have to flash this the same way with recovery (aka renaming it to update.zip) like i had to go with the manual gb update?
Nevermind, figured that out.. but why am i getting a signature verification on install? Where do i turn off sig verification?
SuBDivisions said:
Nevermind, figured that out.. but why am i getting a signature verification on install? Where do i turn off sig verification?
Click to expand...
Click to collapse
There is an option under advanced I think, in recovery, to enable/disable that.....
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
SuBDivisions said:
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
Click to expand...
Click to collapse
You need to use the modified boot -strap recovery available on this forum. D/L it & install it like any other app. When you open it, just read & follow the directions on the screen & you will get to the custom recovery where all good things flash from.
Sent from my DROID X2 using xda premium
SuBDivisions said:
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
Click to expand...
Click to collapse
You should be flashing this thru the Bootstrap Recovery, not the default Android Recovery.
Sent from my DROID X2 using Tapatalk
Ahh HA.. See i know i was missing something.. Thanks have been given.
Zip-align logs were not showing in /data/ for me, so I flashed this, and now they do.
I'm assuming that means the rest of the scripts weren't working either?
Cool. Going to flash this but need a quick question answered.
I have Busybox 1.19.0 installed. I downloaded "Busybox" from marketplace to install 1.18.4 but which location should I chose?
Options are /system/xbin/ or /system/bin/
Thanks
Sorry found this in original init.d hack thread:
BusyBox with run-parts binary, installed in /system/xbin - If you don't have BusyBox, you can download it from the market here.
Click to expand...
Click to collapse
hapyman said:
Cool. Going to flash this but need a quick question answered.
I have Busybox 1.19.0 installed. I downloaded "Busybox" from marketplace to install 1.18.4 but which location should I chose?
Options are /system/xbin/ or /system/bin/
Thanks
Sorry found this in original init.d hack thread:
Click to expand...
Click to collapse
You should be okay on 1.19.0 now, but busybox should always always be installed in xbin.
So which init is better or the working one?
gkitab said:
So which init is better or the working one?
Click to expand...
Click to collapse
Some people find that the re-hack (this thread) works (and the original does not), others find that the original hack works just fine. A way to test is to install my Speedy Gonzales scripts, reboot the phone, and then check in /data for a zipalign log. If not, then flash this re-hack.
I am running speedy. So should I us you init when using yours and his when trying his? How can we tell if yours is working and when using his if his is working? This is getting a bit confusing. I also noticed when I flashed speedy navens old oo got left behind. So I deleted al scripts in init folder and reflashed yours and all yours are now correct.
With his init and your script. Yours scripts are in there but no zipalign in data.
Should I start over by deleting unit folder flash your unit then speedy would that be the safe bet?
Thanks for staying.
gkitab said:
I am running speedy. So should I us you init when using yours and his when trying his? How can we tell if yours is working and when using his if his is working? This is getting a bit confusing.
Thanks for staying.
Click to expand...
Click to collapse
They are two separate things entirely. I posted the re-hack for those having troubles getting scripts to run with naven's original hack. The re-hack posted in this thread doesn't contain any init.d scripts, it's purely the hack. Like I said above, a good way to test his hack is to install my scripts (which it looks like you have), and then use a file manager like Root Explorer and navigate to /data, there should be a zipalign log, if there isn't then his hack isn't working.
Edit: Well, the biggest question is if the init hack you have installed is even working. I'm assuming you have naven's... try the above, let me know if the log is there or not.
I edited my post can you please check it and let me know what you think.
I do have his with your script.
I think I should I should delete init completely and start fresh with yours and your scripts. That sounds like safest bet. Or does naven init need to be there first then yours on top then your scripts. Thanks.
Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Nice one, added to Index.
@op, Good job.
Although my tutorial was word by word the same, apart from maybe few spelling mistakes. ;p
Above is required for Stock Rom which is rooted.
On custom and rooted Rom , you don't need to perform above steps as system is write permitted so running ad away normally works fine.
Regards
Yasir
Sent from my HTC Desire X
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
nightcrow said:
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
Click to expand...
Click to collapse
This symlink method(not mine) is present in ad away FAQs. So credit to the app team.
Sent from my HTC Desire X
Nice guide, first time I'm adfree, even after a reboot
did anyone get it working on desire x... mine still shows ads in apps...
I don't know, after all I'm an amateur, but the problem nightcrow described about how stuff goes back to stock after a reboot is something that happens a lot with the DX's - same thing with the bloatware. I had to remove the bloat apps from a rom.zip and flash that to avoid the problem. Seems to me there is some kind of security built in that goes beyond the norm. Otherwise I don't see why apps like Titanium work to remove apps (even after reboot) for example on most other phones, but not the DX.
Meherzad, I followed the instructions posted by nightcrow and it works for me ... try again, reboot and open an app you know normally has ads to check if it works.
Failed first time (forgot to uncheck fast boot:banghead. Reinstalled and did everything again, now works flawlesly.
ok.. working great......
nightcrow said:
Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Click to expand...
Click to collapse
have no idea how to write in command prompt
umo4u said:
have no idea how to write in command prompt
Click to expand...
Click to collapse
Windows button+R>Type cmd>enter
It doesn´t works for me...It may wont work because i have superuser v3.2?
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
you can do same in advanced-> execute command (or maybe shell - do not remember the exact naming)
adb was not working for me, too.
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
Why do you need ADB when you have TERMINAL in twrp. Just wondering
Anyhow, ADB will be fixed soon
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
michpan said:
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
Click to expand...
Click to collapse
I think you can turn it on.
If you'll not access recovery... when you need recovery, turn fast boot off...
Sent from my hTC branded muffin
i have been messing with init.d for rooted/stock rom t230/nu and i have come up with a modified version of this >> http://forum.xda-developers.com/showthread.php?t=1912504
INSTRUCTIONS:
Flash the attacthed zip in twrp and reboot...
HOW DO I KNOW IF IT WORKED?
in root browser goto /data/local/tmp/ and if there is a file 'init.d_log_test.txt' and inside is written the date, it worked.
if the file is not present something went wrong? please let me know if it went wrong for you an i will fix it..
dont forget to hit thanks and also credit the @jamesst20 in the above link...
Ill give it a go.
Sent from my SM-T230NU
BookCase said:
Ill give it a go.
Sent from my SM-T230NU
Click to expand...
Click to collapse
let me know how it goes as i have only tested on my device... thnx
This will work.....I have it baked into my ROM.
One thing....I'd rename the install-recovery.sh to install-recovery-2.sh as that will break root. SU daemon is called by install-recovery.sh on boot. just a heads up.
g_ding84 said:
This will work.....I have it baked into my ROM.
One thing....I'd rename the install-recovery.sh to install-recovery-2.sh as that will break root. SU daemon is called by install-recovery.sh on boot. just a heads up.
Click to expand...
Click to collapse
i am building a rom at the moment and could not get my head round why it was breaking root lol... cheers dude..
Inside 4ndroid said:
i am building a rom at the moment and could not get my head round why it was breaking root lol... cheers dude..
Click to expand...
Click to collapse
Let me if your still having trouble with root afterwards.
g_ding84 said:
Let me if your still having trouble with root afterwards.
Click to expand...
Click to collapse
oh and in your rom it seems we cant update the su binary and have to flash an updated binary seperetely from within recovery.. i found a work around and now when i flash my rom it says binary needs updating an now in my rom the normal method works and alakasm success
if you need me to explain further pm me an i will go through how i managed it..
In the rom that you're working on is based on CyanogenMod or this stock?
on the other hand just flash this file in Stock T230XXU0ANK3'll see that this is
If you want to enable init.d, you simply install busybox from playstore and download universal init.d, and verify ...
checks in the system / etc / init.d contained in the file 00test & 08setperm :good:
working on my phone 4 tab 7 "T231 :fingers-crossed: :fingers-crossed:
sorry for my bad english
riotaruna said:
If you want to enable init.d, you simply install busybox from playstore and download universal init.d, and verify ...
checks in the system / etc / init.d contained in the file 00test & 08setperm :good:
working on my phone 4 tab 7 "T231 :fingers-crossed: :fingers-crossed:
sorry for my bad english
Click to expand...
Click to collapse
or you could just simply flash the file file in the OP takes alot less time an is simple an staight forward lol..
File is gone
Hello all! If you're familiar with KCAL and suffer from symptoms such as a locked bootloader or non-loadable kernel modules then you may be interested in KCAL Post-Processing Daemon, or KPPD - the all-in-one display tuning tool that you can use to customize your color calibration on the fly!
This does NOT require an unlocked bootloader, custom kernel, or even a kernel that supports module loading, just run the daemon and you're good to go!
To install on a device with a locked bootloader, you'll need to download the kppd release below, and unpack it to prep for some adb fun... (If you have TWRP, you can also flash this in recovery)
Code:
adb push /path/to/kppd /data/local/tmp/
adb push /path/to/postproc.conf /data/local/tmp/
adb shell
su
mount -o rw,remount /system
cp /data/local/tmp/kppd /system/bin/
cp /data/local/tmp/postproc.conf /system/etc/
chmod 0755 /system/bin/kppd
chmod 0644 /system/etc/postproc.conf
reboot
Now at this point, you can use any scripting app to start the daemon on boot, I use ROM Toolbox... http://i.imgur.com/0juzfug.png
And you're done! To edit your display settings, just edit the postproc.conf file... http://i.imgur.com/pjOPbIr.png
Download KPPD
Thanks, works great. Now we need some custom configs
any chance you can update your KCAL Color Control app to support KPPD? Easy way to set the values
Thanks Savoca! I have followed all of your work fairly closely and am very glad we have you around the forums!
This is amazing. Would it work for other LG tablets such as the LG X8.3 with the snapdragon 610?
My G4 is pretty decent but my tablet is super red. Once you get it setup, you constantly have to have Rom Toolbox installed to make this work or do you only need the app for the initial setup?
I think I can answer the second part of this. The rom toolbox thing is just one of many ways to run this script on boot. But you will need SOMEthing to start it no matter what. This could be init script (I think that's what its called, which some roms have built in) Or any custom rom could include it by default.
So no, Rom toolbox isn't really necessary, its just the way he recommended to get it running on boot if you don't know another way.
I am more curious to seen if it will work on my LG tablet. I'll just have to test it out. I guess worst case scenerio is you dont have it auto start on boot. If you mess it up you just reboot.
player911 said:
I am more curious to seen if it will work on my LG tablet. I'll just have to test it out. I guess worst case scenerio is you dont have it auto start on boot. If you mess it up you just reboot.
Click to expand...
Click to collapse
Yes it should work, however it depends on each device's version of the MDSS (Qualcomm display driver). If it doesn't work, let me know so I can add support for it.
I'm wondering if this would work on my G Flex 2 ? Is there any chance that it can break anything if it doesn't work?
---------- Post added at 03:37 PM ---------- Previous post was at 03:05 PM ----------
I've just installed it on my G Flex 2 and it works great. Thanks a lot!
how control this mod with KCAL apk???
armsar1978 said:
how control this mod with KCAL apk???
Click to expand...
Click to collapse
You can't (yet?). Only via the config.
New version uploaded significantly reduces CPU load and removes any delay between modifying the postproc.conf and applying the display settings.
I've read a little and I remember making rgb adjustments regularly with my old gnex years ago...
Wondering if there are suggested settings/values one can recommend for use with the G4 please.
I second this g4 question, any recommended values?
dontbeweakvato said:
I second this g4 question, any recommended values?
Click to expand...
Click to collapse
I'm using these right now: http://imgur.com/UKkOt7x
If you're editing the file at runtime, I recommend you use either FX File explorer or ES File Explorer to edit the config, root explorer and ROM toolbox editors delete the original file and rewrite a new one for some reason (maybe they can fix this in their apps) and kppd looses the original from the kernel.
Does this have an option for sharpness?
"su" doesnt work -> not found
Z900 said:
"su" doesnt work -> not found
Click to expand...
Click to collapse
You need to root your device.
savoca said:
I'm using these right now: http://imgur.com/UKkOt7x
If you're editing the file at runtime, I recommend you use either FX File explorer or ES File Explorer to edit the config, root explorer and ROM toolbox editors delete the original file and rewrite a new one for some reason (maybe they can fix this in their apps) and kppd looses the original from the kernel.
Click to expand...
Click to collapse
"Error occurred while trying to save file. File will not be saved." - using es file explorer. I seem to not have issues with rom toolbox. What's the deal with it not saving after editing?
dontbeweakvato said:
"Error occurred while trying to save file. File will not be saved." - using es file explorer. I seem to not have issues with rom toolbox. What's the deal with it not saving after editing?
Click to expand...
Click to collapse
Sounds like an issue with the app. You could always move the config file to somewhere on /data where you would have write access. Just point kppd to the config location in the init script.
Samsung Galaxy Tab A 7.0 LTE/WIFI 2016 TINKER EDITION ROM (DEOXED/ROOT/XPOSED)
============================================
Update 01/04/2017
-----------------------
Tinker Edition V5.1 is now out.
* Re-added Samsung stock camera and gallery
* revert back to stock vold to fix issues people are having with micro sdcards
Now available for the SM-T285, SM-T280 to follow
Update 10/29/2016
------------------------
TWRP for the SM-T285 here
Early Build of TWRP for the T285 (see post by @ashyx will update this if an official version is released. The T280 version should be available not far behind I believe
Update 09/21/2016
-----------------------
V5 now out (root, deodexed, xposed) for the SM-T280/T285, still working on the SM-T280
Update 09/20/2016
------------------------
Turns out this device is not as locked as we all thought it too be. See thread below for my ordeal and more details:
http://forum.xda-developers.com/galaxy-tab-a/help/resources-samsung-galaxy-tab-7-0-2016-t3431022
Modifications:
===========
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Busybox
* Hijacked Vold (using CM 12.1 sources) to run shell scripts stored in /data/scripts/vold.init
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
* Dolby Atmos mod (09/11/2016) (thanks to @Nando14sunny)
* Deodexed/Xposed (09/13/2016) (thanks to @wanam and @rovo89)
* soft linked /etc/hosts to /data/scripts/hosts and can be edited using adb shell (09/13/2016) (thanks to @venomrat)
* V5: root chainfire's SuperSu 2.78 (09/21/2016) (thanks to @Chainfire)
* stock boot animation
Special thanks also to @ashyx for initially taking a look at this device , I haven't given up on rooting this device yet.
Special thanks to @klemen241 for helping me try out the SM-T280 build
Haven't done extensive testing on Xposed modules, but the pokemon go iv mod/hacked worked and that was good enough for me (Before pokemon Go was patched). If you use this ROM feedback is highly appreciated
NOTES: To be safe, perform a cache wipe using recovery. I didn't need to do this personally but I haven't tested all use cases
NOTES: Since this rom is deodexed, the first boot will take quite a while, so please be patient .
NOTES: if you are coming from V2 and are using the mount_ext4 apps2sd scripts please update it for additional support for the V3 ROM HERE:
https://github.com/jedld/smt285_data_scripts
NOTES: (09/13/2016) Unfortunately, the V3 build fails the Google SafetyNet check, will be a problem if you play Pokemon Go
Other Notes: Removed support for zygote.init scripts in V3 as I am now using the app_process32_xposed binary, will work to get this back soon. I haven't had a need for zygote scripts though. The vold.init scripts shoud still work as before if you are using the apps2sd script
Installation Instructions:
Odin or Heimdall Required. I you are coming from the Stock Rom please wipe/factory reset to be sure. If you are upgrading from V1 or V2 you are not required to wipe unless there are problems. If you are upgrading to V3 cache wipe is recommended using recovery.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Choose the appropriate download for the model (wifi only T280/ lte T285) that you have:
WIFI ONLY Download (SM-T280)
==========================
Link (V5 Deodexed, Rooted and Xposed):
https://mega.nz/#!0Jdg0a4D!XWLES1BwCPrkBlUzqNhRfRi_91LOdawYHydQ_scV2dI
Link (V3 Deodexed and Xposed - with special thanks to wanam with his custom Xposed build (86.0), and credits also to rovo89):
Download from Mega (v3 09/13/2016)
LTE Version Downloads (SM-T285)
===========================
Link (V5.1 Deodexed, Rooted and Xposed):
https://mega.nz/#!ZFFTFKYZ!NAeajNUjIgYI7zOslpWoJ2AeJ-NCKG0Ut8Buz_6eCgU
Link (V3 Deodexed and Xposed - with special thanks to wanam with his custom Xposed build (86.0), and credits also to rovo89):
Download from Mega (v3 09/13/2016)
Link (Original V2 odexed version):
Download from Mega (V2 09/11/2016)
If you have suggestions, send me a PM.
Other Notes (So people don't have to ask):
* I've tried to run superuser daemonsu, but unfortunately the sepolicy scopes for vold and zygote are too narrow in this device for supersu to use despite being root. In theory a version of daemonsu can be made specifically to run on this device with a somewhat castrated functionality though I don't have access to the source code to figure it out. Navigating the sepolicy landmine is hard.
WIFI ISSUES
=========
There are reports of wifi problems with the latest build due to wrong permissions with dhcp hooks, if so you can do the following (big thanks to @_mone):
Using adb shell:
Code:
su
mount -o rw,remount,rw /system
chmod 755 /system/etc/dhcpcd/dhcpcd-run-hooks
mount -o ro,remount,ro /system
/system is readonly by default, which is why you need the remount commands. Reboot your device after just to make sure.
Hi,
The mount_ext4_sdcard.sh script moves all apps to SD card on reboot?
Edit: did not read till the end. System apps are not move.
venomrat said:
Hi,
The mount_ext4_sdcard.sh script moves all apps to SD card on reboot?
Edit: did not read till the end. System apps are not move.
Click to expand...
Click to collapse
It won't by default for safety purposes, however you are welcome to edit the script and try to move them all
jedld said:
It won't by default for safety purposes, however you are welcome to edit the script and try to move them all
Click to expand...
Click to collapse
Thanks for your hard work. It's a pity this device is not as popular as their other models or more people would have already signed the petition.
I regret not doing more research before buying this tablet.
Hello there
At first i want to thank you for your hard work so far
Then i've got a question,
I just built this Tablet (LTE version) in my car. Now i'm on to configure it with Tasker to "act more like a car radio". It was really hard, because of the non rooted device.. But i did it so far
I used a sound mod, called Dolby Atmos (i think it's from lenovo?) on allmost every of my rooted devices to improve its sound.
I'm wondering if it would be possible that you could build in this mod inside a rom for me?
Normally i flash it as a zip file via a custom recovery so it's in the system files. but maybe you could edit it in there before the rom get flashed via odin? I could give you the zip, if u dont find it. It would be really nice!
Greetings from germany
Nando14sunny said:
Hello there
At first i want to thank you for your hard work so far
Then i've got a question,
I just built this Tablet (LTE version) in my car. Now i'm on to configure it with Tasker to "act more like a car radio". It was really hard, because of the non rooted device.. But i did it so far
I used a sound mod, called Dolby Atmos (i think it's from lenovo?) on allmost every of my rooted devices to improve its sound.
I'm wondering if it would be possible that you could build in this mod inside a rom for me?
Normally i flash it as a zip file via a custom recovery so it's in the system files. but maybe you could edit it in there before the rom get flashed via odin? I could give you the zip, if u dont find it. It would be really nice!
Greetings from germany
Click to expand...
Click to collapse
we could try, could you point me to a rom that has the specified libraries for Dolby?
Thank you, for the fast answer!
Here is the flashable zip of the Dolby Atmos, mod i used successfully on my other devices:
Mega
Greetings
Nando14sunny said:
Thank you, for the fast answer!
Here is the flashable zip of the Dolby Atmos, mod i used successfully on my other devices:
Mega
Greetings
Click to expand...
Click to collapse
Ok, wish granted, updated the ROM to include Dolby ATMOs, just redownload the ROM from the link in the main post.
jedld said:
Ok, wish granted, updated the ROM to include Dolby ATMOs, just redownload the ROM from the link in the main post.
Click to expand...
Click to collapse
Wow thank you! I'll test it right now
Edit:
It works like a charm! You really improved my devie with it!
Hi,
If it's not too troublesome, perhaps the next version can symlink the host file to a r/w folder so that ads can be blocked.
Thanks.
venomrat said:
Hi,
If it's not too troublesome, perhaps the next version can symlink the host file to a r/w folder so that ads can be blocked.
Thanks.
Click to expand...
Click to collapse
Possible, though the only r/w partition is data and cache, and it may potentially cause problems when you suddenly try to do a wipe. I'm working on deodexing and porting xposed framework for now. Either that if you've got some IP addresses that need to be blocked I can create an edition that has those entries. I'll see what I can do though there might be away to do it without breaking factory reset/wipe cache.
jedld said:
Possible, though the only r/w partition is data and cache, and it may potentially cause problems when you suddenly try to do a wipe. I'm working on deodexing and porting xposed framework for now. Either that if you've got some IP addresses that need to be blocked I can create an edition that has those entries. I'll see what I can do though there might be away to do it without breaking factory reset/wipe cache.
Click to expand...
Click to collapse
No hurry. I can wait. What you are doing now is more important. :good:
venomrat said:
No hurry. I can wait. What you are doing now is more important. :good:
Click to expand...
Click to collapse
Wish Granted. As a bonus, the latest version of the ROM is now deodexed and Xposed, please refer to the main post for the updates.
Feedback is appreciated.
How can i change the dpi?
Sent from my SM-T285 using XDA-Developers mobile app
corzradio said:
How can i change the dpi?
Sent from my SM-T285 using XDA-Developers mobile app
Click to expand...
Click to collapse
May need to modify build.prop, you may do this yourself here:
http://forum.xda-developers.com/galaxy-tab-a/how-to/guide-samsung-galaxy-tab-7-0-sm-t285-t3438296
Also there may be an Xposed framework modules that do that. Not sure though since I'm ok with the stock DPI
jedld said:
Wish Granted. As a bonus, the latest version of the ROM is now deodexed and Xposed, please refer to the main post for the updates.
Feedback is appreciated.
Click to expand...
Click to collapse
Thanks. Will need to find time to re-flash this weekend.
Regarding xposed have you actually tested any other modules that need root?
I already built a rom with xposed but it was all but useless because pretty much all the modules I use need root.
most of those I tried don't need root so far (youtube adaway, pokemon go iv). Haven't tried those that need root but I suppose those wouldn't work.
I use app settings and it works for dpi change, and you are welcome. I am glad to test stuff, its fun haha. If anyone has questions about t280 you can ask me
how can i boost the volume? since its not rooted i cant find the mixer.xml