Database Info

[ROOT] [KERNEL] [RECOVERY] - Root / Voodoo Lagfix / CWM Recovery

Hi all
Whipped this up for a friend. Thought we'd be nice and share
These packages will work on any current sw version for the Charge.
Please find below kernel and recovery packages hacked for the following:
permanent adb root
installs Superuser and su binary automatically on boot
includes Voodoo ext4 lagfix - CREDIT TO SUPERCURIO! http://project-voodoo.org/lagfix
lowmemorykiller tweaks
sdcard readahead cache speed tweak
If you are using Odin to flash, simply flash the below package. If you are using Heimdall, remove the zImage file from the below package and flash it.
After flashing the first time, you will hear a voice from the phone telling you what is occurring. The conversion to ext4 will take a few minutes. BE PATIENT. Once it boots, Superuser should be installed, and your phone's filesystem will be converted from rfs to ext4. To disable Voodoo lagfix and convert back to rfs, simply create a file on your sdcard inside the Voodoo folder, named "disable-lagfix". Then reboot your phone and listen for the voices again. This will also take a few minutes.
Please familiarize yourself with using Odin or Heimdall and have backup images on-hand if you are going to use this kernel. If you screw up, you will need them
I DO NOT have a Charge, these files have been tested by other users. As always I assume absolutely NO liability for anything that happens if you use this kernel. Phone blows up? It's on you to fix it
If you find this software helpful please click the "Thanks" or the "Donate" button. Either is fine by me. If you would like to investigate the changes that were made, please feel free to find them here, and here.
Enjoy.
EDIT
Uploaded 2nd version
EDIT
Uploaded 3rd version
changed the install scripts around
should copy files more efficiently
fix file ownership and permissions
UNTESTED!
EDIT
Uploaded 4th version
Confirmed root from independent user!
rewrote install process to preserve file path and permissions
will look into the bootanimation graphics issue
http://dl.dropbox.com/u/14764513/VoodooChargeKernel4.tar.md5
EDIT
Uploaded additional recovery file
Flashes custom version of ClockworkMod recovery 3.x
Recovery includes Voodoo specific options for enabling/disabling Voodoo lagfix
Flash with Odin or Heimdall just like the kernel files
HAS BEEN LIGHTLY TESTED! USE CAUTION AND HAVE A BACKUP!
if you do not have root:
* check adb shell and see if you get a '#' prompt. If so, you *have* root on adb, and you may install whatever you want in /system
* check to see if Superuser app is installed
* check to see if /system/xbin/su exists on your phone.
If you have problems, please post the results of those checks. Thanks.

LLGW. Headed to bed now but first thing in the morning, I wondering what I'm doing

Thanks jt!!!! Can't wait to flash this once my charge comes in the mail.
Sent from my SCH-I500 using XDA App

Ok, somebody use this to system dump ED2.
And, uh, is there matching Voodoo clockwork?

s44 said:
Ok, somebody use this to system dump ED2.
Click to expand...
Click to collapse
please
And, uh, is there matching Voodoo clockwork?
Click to expand...
Click to collapse
probably not

What verison of odin should I use? I just flashed this and it failed.

using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1

The kernel flash was successful, and the filesystem conversion took about 8 minutes to run. However, I was not rooted when the phone booted back up. Here is what I did, let me know if I missed a step:
Start on rooted ED1
Accept ED2 OTA
Lose Root
Flash new kernel using ODIN
After ~10 minutes, phone boots successfully, but I do not have root.

asenduk said:
using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1
Click to expand...
Click to collapse
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.

Where's my wifi? Anyone else facing an error when attempting to start wifi?

Yeah it looks like it killed wifi. I also am not rooted.

So if I flash back to rooted ED1 will it wipe my data?

azhockey said:
So if I flash back to rooted ED1 will it wipe my data?
Click to expand...
Click to collapse
I just reversed the filesystem changes and then flashed back to ED1. My data appears to be intact.

moondrius said:
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.
Click to expand...
Click to collapse
had to rename the file to .tar.md5 now its working..

asenduk said:
had to rename the file to .tar.md5 now its working..
Click to expand...
Click to collapse
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?

Updated OP with a new version. Anyone who has flashed the original version, please check adb shell and see if you get a '#' prompt. If you do, then you're technically rooted

NotATreoFan said:
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?
Click to expand...
Click to collapse
Superuser was installed but root was lost... Trying the updated version... On a positive note Quadrant is great! 1400-1550 avg
EDIT: wifi fixed with v2 but still no root.. will try from scratch and report back
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Everything has worked for me. Thank you.
Sent from my ADR6400L using XDA Premium App

yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin

devanmc said:
yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin
Click to expand...
Click to collapse
Click PDA and select the file then just hit start

Unable to Root properly

Hi friends,
I've a problem with rooting my R and need some expert advice.
I'll explain my problem in detail, coz it might be complicated...
So, here is what I did to root my phone
(followed this guide: http://forum.xda-developers.com/showthread.php?t=1406880)
1. Flashed CWM 4.0.0.2 via Odin
2. Made a Nandroid backup
3. Installed Superuser-3.1.3-arm-signed (is this a problem?)
after that I installed "Root check Basic" to confirm if my device is rooted. But the app stays at the screen saying "Please wait for Root Check to complete. System appears to be very slow" and Nothing happens (waited for about 30 min)
After that, I read somewhere that I need to install Busybox. So I tried installing it from the market.
At first, I tried installing from STEPHEN (STERICSON) app, it installed successfully but doesn't open and stalls my phone for some time then I had to terminate it from task manager.
the I tried installing second Busybox by JRUMMY APPS INC. In installed and opened successfully, downloaded the busybox but stops at the following screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and when I open Task Manager it shows the following apps are running (Superuser is greyed out?)
Did I make a mistake somewhere? please help me guys.
I've my nandroid backup, should I restore it?

whatever7276 said:
Hi friends,
I've a problem with rooting my R and need some expert advice.
I'll explain my problem in detail, coz it might be complicated...
So, here is what I did to root my phone
(followed this guide: http://forum.xda-developers.com/showthread.php?t=1406880)
1. Flashed CWM 4.0.0.2 via Odin
2. Made a Nandroid backup
3. Installed Superuser-3.1.3-arm-signed (is this a problem?)
after that I installed "Root check Basic" to confirm if my device is rooted. But the app stays at the screen saying "Please wait for Root Check to complete. System appears to be very slow" and Nothing happens (waited for about 30 min)
After that, I read somewhere that I need to install Busybox. So I tried installing it from the market.
At first, I tried installing from STEPHEN (STERICSON) app, it installed successfully but doesn't open and stalls my phone for some time then I had to terminate it from task manager.
the I tried installing second Busybox by JRUMMY APPS INC. In installed and opened successfully, downloaded the busybox but stops at the following screen
Did I make a mistake somewhere? please help me guys.
I've my nandroid backup, should I restore it?
Click to expand...
Click to collapse
Contact below mentioned thread & dont create another one as you can discussed the issue in already created thread.
http://forum.xda-developers.com/showthread.php?t=1725044
Reported to Justin

kataria.vikesh said:
Contact below mentioned thread & dont create another one as you can discussed the issue in already created thread.
http://forum.xda-developers.com/showthread.php?t=1725044
Reported to Justin
Click to expand...
Click to collapse
I'm Sorry, even I didn't want to make a new thread, but I couldn't find the answer anywhere.
I checked the link you gave to me, but it seems only for ICS.
I'm on GB 2.3.5 and all I want is to root my device and nothing else.

whatever7276 said:
I'm Sorry, even I didn't want to make a new thread, but I couldn't find the answer anywhere.
I checked the link you gave to me, but it seems only for ICS.
I'm on GB 2.3.5 and all I want is to root my device and nothing else.
Click to expand...
Click to collapse
Its ok buddy. Since you are in GB, i think the Superuser u used might be the problem. Gud that u tuk a CWM backup before trying to root. Now follow the below steps.
1. Restore the CWM backup which u tuk before rooting.
2. Reboot the phone. Now check whether the phone is rooted or not using the root checker app. It shud be unrooted (obviously) :silly:
3. Reboot into CWM recovery.
4. Flash the zip which i have attached here.
5. Reboot the phone. Now check whether its rooted. It should have been rooted. You can later install Busybox. I prefer Stericcson's

selva.simple said:
Its ok buddy. Since you are in GB, i think the Superuser u used might be the problem. Gud that u tuk a CWM backup before trying to root. Now follow the below steps.
1. Restore the CWM backup which u tuk before rooting.
2. Reboot the phone. Now check whether the phone is rooted or not using the root checker app. It shud be unrooted (obviously) :silly:
3. Reboot into CWM recovery.
4. Flash the zip which i have attached here.
5. Reboot the phone. Now check whether its rooted. It should have been rooted. You can later install Busybox. I prefer Stericcson's
Click to expand...
Click to collapse
whatever7276 said:
I'm Sorry, even I didn't want to make a new thread, but I couldn't find the answer anywhere.
I checked the link you gave to me, but it seems only for ICS.
I'm on GB 2.3.5 and all I want is to root my device and nothing else.
Click to expand...
Click to collapse
Thanks a million Selva buddy..:highfive:..
@whatever: no pro buddy. If no one is answer then You can PM any user to whom you want help..

selva.simple said:
Its ok buddy. Since you are in GB, i think the Superuser u used might be the problem. Gud that u tuk a CWM backup before trying to root. Now follow the below steps.
1. Restore the CWM backup which u tuk before rooting.
2. Reboot the phone. Now check whether the phone is rooted or not using the root checker app. It shud be unrooted (obviously) :silly:
3. Reboot into CWM recovery.
4. Flash the zip which i have attached here.
5. Reboot the phone. Now check whether its rooted. It should have been rooted. You can later install Busybox. I prefer Stericcson's
Click to expand...
Click to collapse
You're right, the super user was the problem.
But is it safe now to update it via play store?
Thank you selva, you made my day

Glad you got a fix mate, I'll go ahead and close this one up for now :good:
EDIT: Oh and yeah, you should be fine to update from Play Store.
Thanks!

[Q] Precautions to take with root? re looming 4.4.2 OTA

There are how-tos from 2012 about using Voodoo to store root access (like squirrels storing their nuts for the winter) but is there a better way now? ... Am I wrong in anticipating a problem here?
9.18.94.XT926.Verizon.en.US with saferoot
Thanks

I wouldn't take the OTA until someone figures out a way to root the OTA, and that doesn't look very promising. Honestly, I don't think Voodoo will help out here, either.

RikRong said:
I wouldn't take the OTA until someone figures out a way to root the OTA, and that doesn't look very promising. Honestly, I don't think Voodoo will help out here, either.
Click to expand...
Click to collapse
Guess I could educate myself about how Saferoot works, but ... I'm still learning Java! Will be a while before I know how things _really_ work.
Thanks

From the play store:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?

LifeAsADroid said:
For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?
Click to expand...
Click to collapse
As long as you haven't frozen or removed any other system apps, then yes. I usually just do a clean wipe and install with RSD Lite since I remove all kinds of crap when I use stock.
And yeah, you can always flash SuperSU in recovery if your bootloader is unlocked.
/e: On second thought, take that first sentence with a grain of salt. I realized I've never actually taken an OTA the traditional way with a custom recovery installed. It seems like that wouldn't work properly.

killrhythm09 said:
As long as you haven't frozen or removed any other system apps, then yes. I usually just do a clean wipe and install with RSD Lite since I remove all kinds of crap when I use stock.
And yeah, you can always flash SuperSU in recovery if your bootloader is unlocked.
/e: On second thought, take that first sentence with a grain of salt. I realized I've never actually taken an OTA the traditional way with a custom recovery installed. It seems like that wouldn't work properly.
Click to expand...
Click to collapse
Holy cow, I am thanking you all over the place tonight! Such great useful information you have! I was wondering if you wouldn't mind explaining in a little more detail what you mean by "clean wipe and install with RSD Lite". I have a feeling I may or may not have deleted something important along the way. I know I have frozen things in TiBu (which I can defrost, update, and re-freeze or finally delete since this will be our last update from Motorola), and I don't think I have deleted any of the system files as of yet, but I am pretty certain I have modified system files (changing things in SystemUI, etc) for certain mods.
In case the modded files forbid me from taking the OTA, could you explain a little about how you clean wipe and install with RSD Lite?
After final install of KitKat (by whichever method), if I have clean wiped, I'll lose my photos, messages, etc, yes? Is there a way to save that stuff? TiBu backup of the "text messaging" app or the "gallery" app perhaps?
I promise you I am not thread-stalking you around XDA, but thanks again for all your time tonight!

RSD Lite is a software tool you install on your PC to flash Motorola phones in fastboot. If you ever see an fxz package (which I think stands for fastboot xml zip) they can be used by RSD Lite to basically restore your phone to stock. They usually come with a file with different sections that you can comment or uncomment if you only want to flash specific partitions (i.e. only the modem, or just the kernel).
There's probably a better solution for backing up, but I just use TiBu and then copy everything off my internal storage & SD onto my PC temporarily, then copy it back after. I do it so infrequently that I haven't bothered to figure out a better way, sorry.
/e: Meant to include this site, since it has lots of different firmware releases that you can use with RSD Lite:
http://sbf.droid-developers.org/phone.php?device=5
If you have any other questions, let me know.

LifeAsADroid said:
For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?
Click to expand...
Click to collapse
1.5) flash stock from custom recovery.
Note m recovery is in my button goodies. I think hd & m share the same img. Check the md5.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
Voodoo root keeper will work for easy unroot but not for keeping root beyond 4.2.

I personally won't take the update until sometime figures out a way to have root in kit kat.

LifeAsADroid said:
In case the modded files forbid me from taking the OTA, could you explain a little about how you clean wipe and install with RSD Lite?
Click to expand...
Click to collapse
The best solution is to use SamuriHL's House of Moto tools. You must read, read again, and read one more time before installing and using the tool. Once it's set up correctly, it is very easy to use. You can get it here -> http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Read the OP in the thread first. Again, read it and then once more, as he states. The instructions are all there, but you have to read through them entirely before you attempt to use the tools.
I use this all the time when I'm ready to flash back to stock after being on a custom ROM when a new OTA comes out.
I use Titanium Backup to backup all my apps and data to my external SD card.
I use Backup to Gmail app to backup my call log, sms and mms messages so I can restore them later.
I backup my contacts and such to Google as well.
I use Listables to generate a list of the apps I had installed. I have so many that I sometimes forget which ones I used.
After that, I use HoM to flash back to stock and then reinistall TiBu to restore my apps.
Then, I use HoM to flash back the custom recovery (TWRP in my case) and flash root back onto my device (I'm unlocked so I don't have to use an exploit).
However, it would be best to hold off on root if you are wanting to obtain the OTA, unless of course you are using a locked device. Then, you might want to hold off until it's determined if there is a root exploit that will work.
Even though I'm unlocked, I'm going to wait and make sure they don't find a way to relock it. I don't believe they can since it was a physical change in the device (blown fuse - can't unblow it - is that a real word?)
That's it.

Samsung galaxy j max [sm-t285yd] root

How to root samsung j max [sm-t285yd] ???
Pls help...!!!

Plz help me... I can't root my Samsung {t285yd} J max.

:crying:

i also want to root this device. i try all things like king root,towel root everything but no luck.. devloper plz help us to root this device.

Nothing Work
I have been working on a root for this device for the last 6 months. The only place I have made any headway was CF Auto-root. I'm not able to post links yet so just search cf auto root. On the page type sm-t285yd and two options will pop up. Choose one and look for your firmware build. I have not been able to root as of yet, even with this site. It gives you boot/recovery/cf auto-root package. Most of the problems I have faced are due to not being able to get to the recovery once it is flashed in Odin. I will be searching for answers and root until I find one. Of course, I will post it here when I finally break my phone.

Some Light in the Tunnel
I have made some headway with Magisk. I have never used any of the software associated with Magisk, but it seems at least for now, it will do the trick. I will dive into it further tonight and try to post an update shortly.
-Two sites to jump to.
Search Magisk for the best step-by-step
magiskmanager(dot)com - Has great info about magisk
UPDATE: Rooted!! WooHoo!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

TalokiN said:
I have made some headway with Magisk. I have never used any of the software associated with Magisk, but it seems at least for now, it will do the trick. I will dive into it further tonight and try to post an update shortly.
-Two sites to jump to.
Search Magisk for the best step-by-step
magiskmanager(dot)com - Has great info about magisk
UPDATE: Rooted!! WooHoo!
Click to expand...
Click to collapse
In order to flash Magisk you need to have a custom recovery right?. So may I know how you did it?.

You don't need a custom recovery for Magisk. From here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) you follow the odin steps.
there are two ways to install, first was "via custom recovery" and the other "via Magisk Manager v14.0+"
This method does not require root or custom recovery.
you'll need a stock boot image you can extract from tar or md5
Here are the instructions from XDA not my work "By topjohnwu, Recognized Developer / Recognized Contributor on 3rd October 2016, 06:00 PM"
"This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually"
Hope this helps!

Modules working now
I have had a hard time trying to get modules to work in magisk.
Steps taken:
completely removed magisk
re-installed everything
i decided to try a few things
BOOM!! busybox install fixed it all.

Samsung Galaxy Tab J Max SM T-285YD Root with Magisk
I am using magisk for last 5 months. Everything was just fine except one problem.Though my internal storage was blank but it showed that there was no space for new app installation. I had 3 GB blank in internal storage whichi managed to get by linking apps and OBB data to external storage . Please help me if anyone knows any way to get apps installed. Screenshots are attached. Regards

Magisk not working
I also have SM-T285YD and tried magisk flashing the patch boot via odin yesterday ....... i did twice but both the times my device stucked on boot loop please any one help me why it is happening or any other way to root I also found that the twrp builders have created the TWRP file for this device but while flashing via odin i found that the file is in .img format so m not getting the option to flash that please someone help me out through this

Hi,
I have found a twrp for this device in twrp builder.
How ever there is no custom rom it...
Best regards......

j max said:
Hi,
I have found a twrp for this device in twrp builder.
How ever there is no custom rom it...
Best regards......
Click to expand...
Click to collapse
Yes I also found that but thatz in .img format i cant do that via odin ??

AhteVirus said:
Yes I also found that but thatz in .img format i cant do that via odin ??
Click to expand...
Click to collapse
I already have flashed the twrp.
Just you need to make it flashable tar

twrp
yes made it flashable and flashed successfully as per instructions but now when i open it dat shows in red recovery is not seandroid and stucks there only ......and then i have to restart the device

Root Samsung J Max SM-T285YD
Sir Try to many app many proccess but not install TWRP,also Use CF Auto Root,Magisc,king root,kingoroot,dr.foneroot,etc. But Not root my Phone Pls Help me..................

Samsung Galaxy tab J SM-T285YD Dual Sim ROOTED
Hello everyone, this is my first post on XDA, I hope I won't be boring anyone. But it seems that there is no complete guide or tutorial to root the SM-T285YD. I will post here what I did to root it, I followed the lead of some of the other users in this thread and some from other sources.
My device is the SM-T285YD Dual Sim. Here is what I did;
I checked which rom I had installed on my device, it was stock rom from Taiwan, ****T285YDZTU0APL2, android version 5.1.1
I googled for the rom and found it somewhere, it wasn't difficult. I went with Magisk. The instructions were: copy the rom to your device. Here comes the problem, the rom is 2GB it will take up the little free storage left on your internal. So I copied it to my SD card instead. Next instruction, install the magisk apk, version 7. Go to settings in magisk and change the output format to what you intent to use to flash it with after you're done. You have two options; *.img or *.tar. I intended to use Odin to flash when I was done, so I chose *.tar.
When you open Magisk, it will tell you it is not installed, so click install, after which two options appear. Choose "patch rom", select the downloaded rom you saved to your sd card and wait. It will produce a patched boot image in *.img or *.tar file of about 8MB and saves it in your download folder in your internal storage. It may save it in the Magisk folder, just look for it once it is done patching. Copy this patched boot file back to your PC and put the tablet in download mode, then flash it, I had a tar and flashed it with odin 3.10.6
A problem that occurred with me was, although I copied the stock rom I downloaded to the SD card, I still didn't have enough space on my internal storage for Magisk to do it's job, so I had to delete EVERYTHING I could. Flashing went lightning fast and the reboot only took a minute or so longer than normal. ROOTED!!!
Good luck everybody. Hope it helps.
(I edited the text here to make it hopefully clearer and easier to understand, some people didn't quite get it, hope it is clearer now. Of course, as always, if you're not sure about it, or new to it, leave it alone. There is always the risk to brick your device)
It should work if you do it right. Good luck!

This doesn't help.

What didn't work, exactly?

Doctorrico said:
What didn't work, exactly?
Click to expand...
Click to collapse
It does not work, after flashing when I restart the tablet a red text appears in the left corner saying "KERNEL SEANDROID IS NOT ENFORCING" and it stucks on there. I tried to restart it lots of times also did a factory reset but nothing is working.

Mount system as writable in TWRP?

As title says can I safely mount system writable in TWRP to modify build.prop? I would like to push pull the file from TWRP as any changes I make while in Android won't save.
I am mha-l29c567b190 with unlocked bootloader and rooted with phh method. My data is still encrypted at this point.
I'm not familiar enough if what I want to do is going to cause a bootloop or something. I know this will modify system so future OTA will break and I'll probably just decrypt data or figure out how to get back to stock.
I do have backups of everything right after TWRP install (except data since again I'm encrypted) so I may be able to restore that too but don't know if that would work on this phone or not. Thanks!

2nd question. Based on my phone setup, could I uninstall phh superuser from Android, boot to TWRP and restore boot and flash stock recovery to get back to stock? Rooting this phone doesn't seem to have the same advantages of any other phone I've owned so might want to revert back.

Good questions
1. Yes. You can mount /system as read/write if you installed phh superuser using manual. There are two options:
- only root
- root + dm-verity off
Dm-verity is kind of phone's security which is protecting important partition to be modified. Even if you have root and mounting system as read/write and doing something with system, your system partition will go stock state after reboot.
But turning dm-verity off removes this protection and you will able to modify system and other partitions.
2.
To get stock state back you need restore stock boot and recovery.
If you modified system, you have to revert all changes.
But sometimes it is too hard to remember all changes, so best way to get stock is:
- flash stock recovery
- flash stock ROM via Firmware Finder (FF)
It is easiest and quick method.

5[Strogino said:
;74089991]Good questions
1. Yes. You can mount /system as read/write if you installed phh superuser using manual. There are two options:
- only root
- root + dm-verity off
Dm-verity is kind of phone's security which is protecting important partition to be modified. Even if you have root and mounting system as read/write and doing something with system, your system partition will go stock state after reboot.
But turning dm-verity off removes this protection and you will able to modify system and other partitions.
2.
To get stock state back you need restore stock boot and recovery.
If you modified system, you have to revert all changes.
But sometimes it is too hard to remember all changes, so best way to get stock is:
- flash stock recovery
- flash stock ROM via Firmware Finder (FF)
It is easiest and quick method.
Click to expand...
Click to collapse
Thank you for the responses. How do I get dm-verify off?

Does anyone know the drivers needed to get ADB to work in TWRP? I have ADB working fine when in Android and fastboot works fine in bootloader. I would like to modify the build.prop and push it back to the phone. I can't seem to do it either inside of twrp file manager, as it sees /system/vendor as a file and not a path.

bhint15 said:
Thank you for the responses. How do I get dm-verify off?
Click to expand...
Click to collapse
Here is SuperRoot without dm-verity: https://forum.xda-developers.com/ma...oot-mate-9-decrypt-data-t3569986/post71346651
Decrypting data is optional. If you don't wanna it, don't format data (skip linked steps)

5[Strogino said:
;74102755]Here is SuperRoot without dm-verity: https://forum.xda-developers.com/ma...oot-mate-9-decrypt-data-t3569986/post71346651
Decrypting data is optional. If you don't wanna it, don't format data (skip linked steps)
Click to expand...
Click to collapse
That's the guide I used but still can't get build.prop edited. My data is encrypted but system won't write while in Android and while in TWRP adb won't work and I can't copy the file over the old one using TWRP file explorer. Guess I'm giving up with root on this phone seems pointless to have done it with O on its way I just hope I can get it back to stock without breaking it to get the OTA (if it ever hits since I'm C567 and this thing hasn't had a damn update since April)

bhint15 said:
That's the guide I used but still can't get build.prop edited. My data is encrypted but system won't write while in Android and while in TWRP adb won't work and I can't copy the file over the old one using TWRP file explorer. Guess I'm giving up with root on this phone seems pointless to have done it with O on its way I just hope I can get it back to stock without breaking it to get the OTA (if it ever hits since I'm C567 and this thing hasn't had a damn update since April)
Click to expand...
Click to collapse
I can't say what happens on new ROMs, cause this guide slightly old. If you installed phh SuperRoot and phh superuser app from play store, you are able to use root. Check it in terminal.
If yes, try to mount system as read/write.
If yes, use Root Explorer and change system files.
Try reboot after that and notice everything works or not.

5[Strogino said:
;74138910]I can't say what happens on new ROMs, cause this guide slightly old. If you installed phh SuperRoot and phh superuser app from play store, you are able to use root. Check it in terminal.
If yes, try to mount system as read/write.
If yes, use Root Explorer and change system files.
Try reboot after that and notice everything works or not.
Click to expand...
Click to collapse
I have root. It prompts and works. Root explorer (or any other app that modified system) will not write to system, it errors out.
Other weird stuff too though, like Xposed installs in TWRP but doesn't work (says not installed)
I really only wanted root to unlock hotspot so it's not that big of deal.

Here is the solution to your problem my friends. Enjoy!
Works like a charm in Android 10 and later.
https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}