[FIRMWARE] Collection of ESSENTIAL update images for those on Custom ROMs - Essential Phone ROMs, Kernels, Recoveries, & Other

[06-02-2020] This thread will be closed, but I will keep updating the NOVENDOR AFH folder during next months so please just check there. (I may re-open it at a later time if I decide its necessary).
As the title says, I plan to keep a collection of the ESSENTIAL updates here in this thread because I intend to keep my Mata for a while still and I want to stay updated every month. :good:
WARNING - These are custom made zips as you would download them from ESSENTIAL, except with SYSTEM modifying partitions removed. So anyone who is running on a Custom ROM can easily run the batch file to flash all the other updated partitions at once in FASTBOOT. Easy pz! :good:
HOW TO:
These aren't your usual "TWRP flashable" zips! Please read and follow the instructions below:
INSTRUCTION:
Download ZIP file
Unzip in a location of your choosing
Reboot PH1 to Fastboot
Make your PC/Laptop can communicate with the device
Run the BAT file inside the EXTRACTED folder
Follow the instructions given.
Profit!
-----
DOWNLOADS:
HERE!
NOTE: Feb2020 needs the Feb ROM patch before flashing otherwise you'll end up in a bootloop.
-----
NOTE:
Nothing will be wiped!!
EDIT (11-01-2020): Thanks to (@dragynbane222) for fixing the Linux/Unix script. Zip re-uploaded!
Click Thanks below if you appreciate the work. :good:
Have fun.
Camo.

Reserved.
Extra seat for the future.

If I'm in stock but with elemental x kernel Is necessary this or I have to download all the ota file in the essential developer web and apply in TWRP?

mpena said:
If I'm in stock but with elemental x kernel Is necessary this or I have to download all the ota file in the essential developer web and apply in TWRP?
Click to expand...
Click to collapse
You can still use the images in the zip files from this thread, but you wont get the SYSTEM, VENDOR or KERNEL updates.

Would I need to reflash TWRP and Root after this?

foueddyf said:
Would I need to reflash TWRP and Root after this?
Click to expand...
Click to collapse
Nope you don't. Nothing is wiped.
All the small partitions are silently updated, just run the BAT or SH (if you're on Linux).

CamoGeko said:
Nope you don't. Nothing is wiped.
All the small partitions are silently updated, just run the BAT or SH (if you're on Linux).
Click to expand...
Click to collapse
I'm on Linux, ran the sh script and it all worked perfectly, thanks man!
:good:

foueddyf said:
I'm on Linux, ran the sh script and it all worked perfectly, thanks man!
:good:
Click to expand...
Click to collapse
Fantastic.
Thanks for the feedback! :good:
Sent from my mata using Thebear Blue XDA Labs

Hey, wasn't too hard fixing the script, hope it comes in handy to whomever uses it.

Sorry I hate to be or look stupid... I just don't want a bricked phone or a phone I have to resetup again, but I'm on a custom Rom so do I just run the batch file it do I need to tweak something in order to get the security update? And what is said tweak if need be to do so? Thank you!

jrodbrown58 said:
Sorry I hate to be or look stupid... I just don't want a bricked phone or a phone I have to resetup again, but I'm on a custom Rom so do I just run the batch file it do I need to tweak something in order to get the security update? And what is said tweak if need be to do so? Thank you!
Click to expand...
Click to collapse
Aside from this, the dev also has to pull in the latest security patch in the source code then build it. These zips only provide the updated former.

Man, my pc drives me nuts! I can get it to connect with my phone most of the time, but it is just so fickle about running the scripts in fastboot. I know if I try it on another computer, it'll be fine. BLAH! Just me venting

FYI since updating to this Firmware my phone stops saving wifi passwords. I need to reenter passwords after any reboot i.e. the saved networks are all gone.

Thread closed per OP Request.
The link in the OP will stay active, as the host is continuing to be updated.

Related

Xposed Installer destroyed my Toshiba AT300SE rooted

I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
i'll try this
kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Seems that disabler zip did not work.
Any other brilliant ideas................
Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk
kingvortex said:
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.
Rooks said:
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.
Click to expand...
Click to collapse
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.
Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Only brilliant idea here was flashing something before backing up your rom.
Sent from my Nexus 5 using Tapatalk
GermainZ said:
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.
Click to expand...
Click to collapse
I did not mean to be rude or ANY disrespect.
So guys, PLEASE point me to right direction so that i can bring back my device.
rovo89 said:
In case you get into a boot loop:
First, try using the safemode by pressing any hardware key repeatedly. You can find a short explanation how it works here.
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
rovo89 said:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Where can i find disabler zip file?
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Rooks said:
Where can i find disabler zip file?
Click to expand...
Click to collapse
From the linked post:
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
Rooks said:
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
GermainZ said:
From the linked post:
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
Click to expand...
Click to collapse
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.
Rooks said:
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.
Click to expand...
Click to collapse
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.
Rooks said:
Yes i've tried three different files, all failed to install.
Click to expand...
Click to collapse
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?
Rooks said:
Where can i find disabler zip file?
I downloaded some file from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.
GermainZ said:
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.
Click to expand...
Click to collapse
I'll try to get logcat for this issue.
rovo89 said:
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?
Click to expand...
Click to collapse
Yes, it's the stock recovery and i've tried several times with hardware keys but safe mode did not work in my scenario.
esgie said:
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.
Click to expand...
Click to collapse
I've tried three different file with different sizes (143kb, 121kb and 145kb), all these files include the same script ("updater-script" file) by Tungswenty.
ui_print("");
ui_print("");
ui_print("------------------------");
ui_print(" Xposed disabler tool ");
ui_print(" by Tungswenty ");
ui_print("------------------------");
ui_print("");
ui_print("Mounting system partition");
ifelse(!is_mounted("/system"),
run_program("/sbin/busybox", "mount", "/system"));
assert(is_mounted("/system"));
ifelse(run_program("/system/bin/sh", "-c", "test -f /system/bin/app_process.orig") == 0,
(
ui_print("Restoring the original app_process file");
assert(run_program("/sbin/busybox", "cp", "-a", "/system/bin/app_process.orig", "/system/bin/app_process"));
set_perm(0, 2000, 0755, "/system/bin/app_process");
ui_print("Restore complete.");
ui_print("You should now be able to boot normally and remove all traces of Xposed from within the Installer app.");
),
(
ui_print("No backup found for app_process, nothing to be performed!");
));
ui_print("");
ui_print("Done.");
ui_print("");
Click to expand...
Click to collapse
Rooks said:
Yes, it's the stock recovery
Click to expand...
Click to collapse
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).
rovo89 said:
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).
Click to expand...
Click to collapse
I've stock rom and recovery, there is no custom rom or recovery available for my device (Toshiba Excite 10 SE aka AT300SE).
So with stock rom and recovery it won't accept any zips and i can't format system partition with stock recovery. And about adb, i don't know where to start. In recovery there is an option to push a file through adb but when i connect my device while this option, my pc does not recognize the device, neither i can update the adb drivers.
Rooks said:
I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.
Click to expand...
Click to collapse
HOW YOU ROOT...???!!!
PLEASE TELL ME
I CANT FIND IN WEB....
Give me a links if you can ....
THANKS

How to solve random reboots and other issues in Lollipop ROMs in S2 hd lte

UPDATED
Since these issues have been fixed in newer builds but as a s2 hd lte users, we have no option but to use older builds which have many issues. I found a workaround for them. If you are having wifi or other radio related issues, contact the ROM developer. This post can't help you. Flashing latest baseband helped me and could work well for you as well. Lets talk about two of the most common bug that haunts our device
1 Apps auto closing->( only for LMY48G builds,if you have newer builds,just flash gapps and reboot. to check go to about phone-> build number)
This is a webview related bug.
Download latest gapps from opengapps.org.
I prefer aroma installer as smaller packages don't have webview included,which will make the bugs worse.
Flash gapps. Dont forget to select 'android system webview' from the aroma installer.
Download the zip file from the
link
https://mega.nz/#!0d5Tiaja
Decryption key !JAG5Im-T75YN1CKIOiOcyDDaBH2ILD6dzwxw4xnhrBc
Extract "libwebviewchromium.so" and "libwebviewchromium_plat_support.so"
It is taken from stock samsung ROM and only works on armv7 devices.
Copy them to /system/libs using ESfile explorer or any other root explorer.
Overwrite the original file if asked.
give permission (-rw-r-r) to both file
Reboot to recovery
Flash this file "cm12.1 android system webview" from this thread(only for cm12.1, will cause bootloops in Xenon hd and resurrection remix)
http://forum.xda-developers.com/xperia-m/themes-apps/mod-google-android-webview-t3109216
Apps will now no longer auto close in your face without warning
((-> After testing for a month, I concluded that these steps are optional and use only if you want to have google android webview instead of cm12.1's built in 'android system webview'))
2) Now the most important part, random reboots.
This was reported on earlier builds of lollipop by many users.This is mostly caused by minfree that android uses to manage memory. If you navigate to sys/modules/lowmwemorykiller/parameters you can see 4 or 5 files. two of those files have wrong permissions. They are "adj" and "minfree".
If you give them (rw-r-r) permissions, you can adjust minfree values. the stock values are too aggressive and would cause constant reboots, freezes. Download romtoolbox, navigate to task manager, swipe left. you can choose to use any presets. i use 8,12,24,60,70,80 as minfree values.
Dont check "auto apply on boot" because you need to repeat this whole process after a reboot as those two files"adj and minfree" will be replaced from boot.img on boot by kern
Permanent fix: unpack boot.img. Navigate to ramdisc and open init.rc file in notepad. Find the line
chmod 0220 /sys/module/lowmemorykiller/parameters/minfree
chmod 0220 /sys/module/lowmemorykiller/parameters/adj
Change both values to 0644
save and close
Repack boot.img
Put it back inside the zipfile using winrar or use flashify from playstore to update boot.
I found tool to unpack qualcomm boot.img from this website. Full credits to the developer who made this tool.
http://www.droidbeep.com/how-to-unpa...-img-qualcomm/
download ROM toolbox and apply your preferred values
3. Low storage and optimizing apps(configuring ART compiler)
After google updated android runtime from JIT to ART, apps take up huge space and "optimizing app" takes forever. But there is workaround for that too.
1)Open build.prop in any text editor.
2) find these two lines:
dalvik.vm.image-dex2oat-filter=........(blah blah)
dalvik.vm.dex2oat-filter=...(blah blah)
3) Change both of these lines to
dalvik.vm.image-dex2oat-filter=speed
dalvik.vm.dex2oat-filter=Verify-none
If these lines doesn't exist, in your build.prop,you have to add them manually
4) save your build.prop file
5) reboot to recovery and wipe dalvik cache
After this check your storage space, You will have plenty of storage left and optimizing apps should be faster. It works just like old JIT compiler from older android versions.
if this doesn't work for you, you have to edit these same lines from default.prop by unpacking boot.img
I have fixed this issue by editing init.rc inside boot.img, but i dont know if i should post it here or not.
diabolicalprophecy said:
I have fixed this issue by editing init.rc inside boot.img, but i dont know if i should post it here or not.
Click to expand...
Click to collapse
please, for e120s
OIAUser said:
please, for e120s
Click to expand...
Click to collapse
Please extract Boot.img from the zip file and send it. I don't have boot.img for e120s, or i can tell you how to do it yourself if you are interested.
Tell me how, I'll try to do it myself.
I will be very grateful
any way to fix wifi & soft reboot on e120s ???
if you need log or any thign about my devices i will link it to you!!
OIAUser said:
Tell me how, I'll try to do it myself.
I will be very grateful
Click to expand...
Click to collapse
I have updated the post on how to do it. You can find the required tool here with detailed instructions
http://www.droidbeep.com/how-to-unpack-and-repack-boot-img-qualcomm/
kdlinh said:
any way to fix wifi & soft reboot on e120s ???
if you need log or any thign about my devices i will link it to you!!
Click to expand...
Click to collapse
You can try wiping phone efs through odin in order to fix radio issues
1 Download stock jb rom
2 Check "phone efs clear". This is most important.
3 Click pda
4 click start
5 wait for phone to boot up
6 go to settings->software update to check if you are running latest jb build. Soft reboots and radio issues are usually caused by old baseband version.
7 Proceed with usual old way to install lollipop.
This way odin will wipe your efs settings to rebuild from scratch.
still ploblem ??? :? wait how to clear efs
at first time i have checked this box but failded ,
kdlinh said:
still ploblem ??? :? wait how to clear efs
at first time i have checked this box but failded ,
Click to expand...
Click to collapse
you need Stock jb rom to do this. I also had this issue in e120l, but clearing phone efs fixed radio issues for me. you need odin3v 1.85 and samsung usb drivers.
You can find it alongside " phone bootloader update". Be careful not to select this one by accident.
diabolicalprophecy said:
you need Stock jb rom to do this. I also had this issue in e120l, but clearing phone efs fixed radio issues for me. you need odin3v 1.85 and samsung usb drivers.
You can find it alongside " phone bootloader update". Be careful not to select this one by accident.
Click to expand...
Click to collapse
i have checked this efs box but failed :crying::crying:
kdlinh said:
i have checked this efs box but failed :crying::crying:
Click to expand...
Click to collapse
which firmware did you tried this with? i have no problem doing this with astap 8 or stock jb rom for e120l.
http://i4khmers.blogspot.com/2015/09/official-firmware-samsung-galaxy-sii.html try this
its E120SKSJMH3 version
Once again, I read the instructions .. understand. But in the archive libraries are no libvebvievhromium .so file. "There's a file" libwebviewchromium_loader. "This is critical?
OIAUser said:
Once again, I read the instructions .. understand. But in the archive libraries are no libvebvievhromium .so file. "There's a file" libwebviewchromium_loader. "This is critical?
Click to expand...
Click to collapse
you get "libWebviechromium .so" file while installing gapps package. Go to opengapps.org and download aroma installer.
there are two files in the archive i uploaded, libwebviwechromium_loader.so and libwebviewplatsupport.so. You need to extract and replace those files in system-> libs after flashing gapps package. The built in webview will cause random apps shutdowns. this file is critical. You need libwebviewchromium_loader to start webview app. your system will not function properly without it.
diabolicalprophecy said:
which firmware did you tried this with? i have no problem doing this with astap 8 or stock jb rom for e120l.
http://i4khmers.blogspot.com/2015/09/official-firmware-samsung-galaxy-sii.html try this
its E120SKSJMH3 version
Click to expand...
Click to collapse
failed it still this error it seems like i stuck , have at least one error when i up rom to an open source cook rom
kdlinh said:
failed it still this error it seems like i stuck , have at least one error when i up rom to an open source cook rom
Click to expand...
Click to collapse
have you checked debugging option from developer options before doing this? Make sure your data cable is not faulty. please make sure you have a backup of efs partition if you are having network issues with all ROMs. try hellcat and stock based roms for testing to make sure you are not having this issue only on lollipop or kitkat. Also try to wipe boot from recovery menu before flashing.
diabolicalprophecy said:
have you checked debugging option from developer options before doing this? Make sure your data cable is not faulty. please make sure you have a backup of efs partition if you are having network issues with all ROMs. try hellcat and stock based roms for testing to make sure you are not having this issue only on lollipop or kitkat. Also try to wipe boot from recovery menu before flashing.
Click to expand...
Click to collapse
i means that when i up the stock based roms none of error found but when i up rom to cm11 cm10 hellkat miui cm12 & ressuction
ERROR at least found one in this open source rom
kdlinh said:
i means that when i up the stock based roms none of error found but when i up rom to cm11 cm10 hellkat miui cm12 & ressuction
ERROR at least found one in this open source rom
Click to expand...
Click to collapse
I also had this the same issue.
There is a link to latest baseband in hellkat thread. Thats where i got it. Sadly Its only for E120L
Search the hellkat thread to see if there is one for e120s as well.
I obviously didn't look further as i don't own e120s.
diabolicalprophecy said:
I also had this the same issue.
There is a link to latest baseband in hellkat thread. Thats where i got it. Sadly Its only for E120L
Search the hellkat thread to see if there is one for e120s as well.
I obviously didn't look further as i don't own e120s.
Click to expand...
Click to collapse
can you give me the links , at least what i can do now is tried to install your baseband
it will brick your phone. Its for E120L only

TWRP, ROOT and disable Encryption for Yoga Tab 3 Plus (YT-X703F/L)

TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
WARNING!!! Be careful what you do here. One mistake and the device is soft-bricked. I take no responsibility for bricked devices, lost warranty or even OTAs not working!! Booting and/or flashing files from this post is on your own risk.
Requirements
Unlocked bootloader
Yoga Tablet 3 Plus with and without LTE (YT-X703L and YT-X703F) are supported
Known Issues
WARNING! Our device uses dm-verity (verified boot). The system partition should remain read-only. Otherwise a bootloop will occur. You can flash my modified kernel or SuperSU to resolve this but OTA's are no longer possible! You have to restore a factory image or clean system backup to receive OTAs
Potentially DRM keys are lost! Pure unlocking and rooting does not cause the issue. However, there have been reports of lost DRM keys by some unknown action. It is advised to act with caution. Losing your DRM keys can lead to issues with some apps which use DRM which could then have limited or no functionality. E.g. Netflix will only stream in SD (480p). You can check with DRM info if you still have L1 security level which means DRM keys are intact.
Download
Official TWRP for YT-X703F (Wifi): twrp.me
Official TWRP for YT-X703L (LTE): twrp.me
Instructions
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Setup the tablet again and reboot again to the bootloader
Then run
Code:
fastboot boot twrp-3.2.1-0-yt_x703f.img
to temporarily boot into TWRP. You can also flash if you are sure
Select to keep system read only when TWRP starts to avoid modification which will make OTAs impossible
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Additional Downloads
Backup of original boot, recovery and system image for YT-X703F S000936: MEGA
Modified Boot image with forceencrypt disabled and it switches off CABC fully. You need to factory reset after flashing to format data without encryption boot_yt_x703f_s000963_noforceencrypt_cabc.img (YT-X703F S000963) / boot_yt_x703l_s000963_noforceencrypt_cabc.img (YT-X703L S000963) . Use
Code:
fastboot flash boot boot_yt_x703f_s000963_noforceencrypt_cabc.img
to flash the kernel in fastboot. SuperSU or Magisk should be flashed afterwards if root is desired.
Full factory images with flash tool and instructions YT_X703F_S000689, YT_X703L_S000704, YT_X703F_S000725, YT_X703L_S000725, YT_X703F_S000734, YT_X703L_S000734, YT_X703L_S000744, YT-X703F_S000744, YT-X703L_S000963, YT-X703F_S000963 and OTA updates: MEGA (These images contain the individual boot, recovery and system images that you need to restore from any modification mentioned above)
System Updates (OTA)
In order to successfully apply Lenovo system updates after root you have to restore the original boot, recovery (if you flashed TWRP) and system partitions from your current installed version (e.g. S000744) for your variant of the tablet. This will NOT delete your apps and data but will unroot. Note that OTAs are block based and always check the contents of most of the partitions. This means that all of these partitions (except your data) have to be original and have to be on the exact same version (e.g. S000734) for the update to succeed.
See here for instructions how to restore the partitions with fastboot.
Credits
@pogo1975 - for providing the factory images and fixing the AV sync issue
@launcher20 and @deecept - for testing the LTE version
TeamWin
Changelog
v4:
Now official TWRP with version 3.0.3-0
v3:
enable full disk encryption for access to the encrypted data partition
update TWRP kernel to latest S000725 version
v2:
add support for LTE variant (YT-X703L)
add further mount points to be able to backup more data
Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.
Doing good work here.
Who wants to bet on a race between matshias and Lenovo support for who can fix the issues with this device first?
That's great and fast, I'm thinking tab 3 plus is getting hot now.
Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?
so you know, i've managed to install xposed thanks to this thread https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 and is working well.
wayney said:
Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.
Click to expand...
Click to collapse
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Gogoho said:
Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?
Click to expand...
Click to collapse
The LTE variant is probably very similar and it wouldn't be much work. But I don't own the device, so I would need some help. So someone with the LTE variant who is not afraid to experiment with fastboot and adb and who can provide me with the details needed I am happy to compile a TWRP for it.
LineageOS is much much more work than TWRP. For an experienced cyanogenmod/LineageOS dev it is not much of a thing and would take only a few days, especially since it is a Qualcomm device and there are already ports for devices with SD 652. But for me this is new as well so it'll take much longer. As soon as I have time I'll look into it.
matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.
wayney said:
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.
Click to expand...
Click to collapse
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany
matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
matshias said:
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany
Click to expand...
Click to collapse
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.
wayney said:
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.
Click to expand...
Click to collapse
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.
Unmodified System Image
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI!vcO9dpSJX...Grjb7k3z6mjnqA
wayney said:
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI
Click to expand...
Click to collapse
Perfect!!
Can you send me the key for the download via PM or post it?
matshias said:
Perfect!!
Can you send me the key for the download via PM or post it?
Click to expand...
Click to collapse
Let's try that again.
https://mega.nz/#!bos0GIjI!vcO9dpSJXp6cKtdH07Kt0RSaqpqQ7Grjb7k3z6mjnqA
matshias said:
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.
Click to expand...
Click to collapse
Thank you guys for spending times on it, it would be wonderful if Lenovo people do thing like this way, too.
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
Hahaha got to love the dark corner of the Russian internets :laugh:
pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.
matshias said:
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.
Click to expand...
Click to collapse
so long as it's safe and not loaded with malware...

[MOD][RECOVERY] Working TWRP recovery for Pixel on Android O

EDIT:
My mod is not needed anymore!
Everything is fine now, the TWRP guys made the decryption in their latest version (3.2.1 at the time of this post) possible, even with android 8.1.
Go ahead and download it from twrp.me. and don't forget to thank them, because it was a LOT of hard work! Google made big changes under the hood, and it took a lot of patience and endurance to adapt.
Big up to @Dees_Troy and the rest of the team!
Hey People! It seems, that after weeks of trying, hundreds of reboots, countless tests, I can present you a working version of TWRP 3.1. for the Pixel with Android O Developer Preview 4.
Edit: and it also works on the final Android O.
But let's not rush into things.. First of all a DISCLAIMER:
This is a TEST release, you are using it at your own risk. If your phone gets damaged in any way, nobody else but you can be held responsible. If you do not agree, stop reading and don't use this mod!
I would like to give credits to the people who helped me, and made all this possible:
First of all, @Chainfire, who did more then you would think Among other things, he was the one who showed me how to use tune2fs and reset quotas on /data, which makes it possible to mount it. Without this , I couldn't even start. So thank you very much!
Of course where would we be without @Dees_Troy and the other TWRP guys (i.e.: CaptainThrowback, nkk71, steadfasterX, _that...), who created and maintain TWRP, and demonstrated some serious patience on IRC , where I was asking them for help. For days. For weeks Thank you guys! You helped a lot!
What is this "mod"?
This is stock, normal TWRP 3.1 compiled from source, for the Google Pixel (sailfish) with some small tweaks to make it possible to mount /data, and decrypt it.
Can you use it on the Pixel XL (marlin)?
I don't know... I don't have a Pixel XL to test. If you want, you can buy me one and I'll be glad to compile, prepare, and test it for you.
EDIT: Chainfire "tested a few zip installs" and those were working for him on the Pixel XL, so maybe it is worth a try guys! - thanks for this CF! -
What happens behind the curtains?
I made some modifications to a script that prepared stuff to make the decryption of /data possible. Now it does a bit more... It copies libraries and binaries from /system and /vendor partitions to /system and /vendor folders, so they can be un-mounted (needed for backup). Basically, the recovery uses the real files/commands of the currently installed android os to prepare and mount /data partition (to make it ready for decrypting).
I updated the fstab file, so TWRP knows what to mount where.
I also changed a few things in the order how services are started during TWRP boot.
This is mostly everything. I was only changing external parts/files/tools of TWRP. The original code, the core is left intact.
How well was it tested?
I have only 1 phone, the pixel. I have only tested on this one phone, and it works for me. Of course I can't be certain it will for you, but you will see if you try it
I tested decrypting of /data, flashing a zip file, making a backup. Didn't dare to test restore yet
How can you try it?
This is not a flashable zip, this is a bootable image. So to use it, you have to put the phone into fastboot mode, and fastboot boot the image.
1. reboot the phone into fastboot mode
- if you have adb: adb reboot bootloader
- if you don't, then turn off the phone and press volume down while turning it on
2. open a terminal and issue the following command:
Code:
fastboot boot <path to your twrp image here>
(for example: fastboot boot /home/you/twrp-3-1-pixel-bootable-mod.img)
What about a flashable zip?
I had some quick test runs only for now, and it was working for me (flashing the zip, rebooting to recovery) until I flashed supersu, or rebooted the phone to android. I will need some more time to work on this, and see what is going wrong. So please be patient, I will try to do something, but can't guarantee it will work. Soon. Anytime.
Enough of the talk, you can download the image file from here:
https://www.androidfilehost.com/?fid=745425885120753892
Good luck and don't forget to report back!
I will try to do my best to help you, but I have a family and I inted to spend most of my time with them. Please be patient!
If you like my work, you can buy me a beer, it is damn hot here right now, and I would love to drink one
Edit: Because I'm a noob and couldn't push my changes to the gerrits, I created a diff file with all my changes.
If you are checking it, please take into account, that I was in a hurry, and there was a point where I said "F*** it!" and I copied ALL the libs and bins from /system and /vendor
Anyway, here it is : https://www.androidfilehost.com/?fid=817550096634795329
reserved...
I've only tested installing a few ZIPs but that seems to work fine (on Pixel XL).
I've looked at your modified script and I see the tune2fs commands and copying /system and /vendor files, but I don't see where you actually mount/decrypt /data. Or is this still handled by the TWRP binary?
Chainfire said:
I've only tested installing a few ZIPs but that seems to work fine (on Pixel XL).
I've looked at your modified script and I see the tune2fs commands and copying /system and /vendor files, but I don't see where you actually mount/decrypt /data. Or is this still handled by the TWRP binary?
Click to expand...
Click to collapse
Hi Chainfire!
I'm happy to hear, that it works on the Pixel XL
Thanks for the confirmation!
Yes, decrypting the data partition is still being handled by TWRP. I added some debug lines to the C code, you can see it in /tmp/recovery.log.
The main issue was mounting /data first, and I had to enable file based encryption instead of vold...
Thanks, I'll have to make time in the very near future to prep my phone for a fresh install.
I haven't had a need to host Android files since I moved on from LG devices before my HTC 10 and Pixel, but I highly recommend Android File Host with optional FTP access on request.
If you prefer a regular cloud service, I recommend Mega. They give 50GB for free and they have an Android app as well as Windows. Possibly others (Mac?), not sure.
My God this is amazing. Thank you so so much.
bbender716 said:
My God this is amazing. Thank you so so much.
Click to expand...
Click to collapse
You are welcome! Try to imagine how happy I was when I first succeeded At that time I had to issue 5 commands after boot, and restart it twice to make it work
But I was already able to flash ARISE sound mod and I almost cried of joy
roirraW "edor" ehT said:
Thanks, I'll have to make time in the very near future to prep my phone for a fresh install.
I haven't had a need to host Android files since I moved on from LG devices before my HTC 10 and Pixel, but I highly recommend Android File Host with optional FTP access on request.
If you prefer a regular cloud service, I recommend Mega. They give 50GB for free and they have an Android app as well as Windows. Possibly others (Mac?), not sure.
Click to expand...
Click to collapse
Ahh I haven't thought of Android File Host! Although I downloaded gigbytes of roms, and mods from there already
Thanks for the tip!
is my path is cd/adb what command i write before twrp.img
gubacsek said:
Hey People! It seems, that after weeks of trying, hundreds of reboots, countless tests, I can present you a working version of TWRP 3.1. for the Pixel with Android O Developer Preview 4.
But let's not rush into things.. First of all a DISCLAIMER:
This is a TEST release, you are using it at your own risk. If your phone gets damaged in any way, nobody else but you can be held responsible. If you do not agree, stop reading and don't use this mod!
I would like to give credits to the people who helped me, and made all this possible:
First of all, @Chainfire, who did more then you would think Among other things, he was the one who showed me how to use tune2fs and reset quotas on /data, which makes it possible to mount it. Without this , I couldn't even start. So thank you very much!
Of course where would we be without @Dees_Troy and the other TWRP guys (i.e.: CaptainThrowback, nkk71, steadfasterX...), who created and maintain TWRP, and demonstrated some serious patience on IRC , where I was asking them for help. For days. For weeks Thank you guys! You helped a lot!
What is this "mod"?
This is stock, normal TWRP 3.1 compiled from source, for the Google Pixel (sailfish) with some small tweaks to make it possible to mount /data, and decrypt it.
Can you use it on the Pixel XL (marlin)?
I don't know... I don't have a Pixel XL to test. If you want, you can buy me one and I'll be glad to compile, prepare, and test it for you.
EDIT: Chainfire "tested a few zip installs" and those were working for him on the Pixel XL, so maybe it is worth a try guys! - thanks for this CF! -
What happens behind the curtains?
I made some modifications to a script that prepared stuff to make the decryption of /data possible. Now it does a bit more... It copies libraries and binaries from /system and /vendor partitions to /system and /vendor folders, so they can be un-mounted (needed for backup). Basically, the recovery uses the real files/commands of the currently installed android os to prepare and mount /data partition (to make it ready for decrypting).
I updated the fstab file, so TWRP knows what to mount where.
I also changed a few things in the order how services are started during TWRP boot.
This is mostly everything. I was only changing external parts/files/tools of TWRP. The original code, the core is left intact.
How well was it tested?
I have only 1 phone, the pixel. I have only tested on this one phone, and it works for me. Of course I can't be certain it will for you, but you will see if you try it
I tested decrypting of /data, flashing a zip file, making a backup. Didn't dare to test restore yet
How can you try it?
This is not a flashable zip, this is a bootable image. So to use it, you have to put the phone into fastboot mode, and fastboot boot the image.
1. reboot the phone into fastboot mode
- if you have adb: adb reboot bootloader
- if you don't, then turn off the phone and press volume down while turning it on
2. open a terminal and issue the following command:
Code:
fastboot boot <path to your twrp image here>
(for example: fastboot boot /home/you/twrp-3-1-pixel-bootable-mod.img)
What about a flashable zip?
I had some quick test runs only for now, and it was working for me (flashing the zip, rebooting to recovery) until I flashed supersu, or rebooted the phone to android. I will need some more time to work on this, and see what is going wrong. So please be patient, I will try to do something, but can't guarantee it will work. Soon. Anytime.
Enough of the talk, you can download the image file from here:
(If you know a good file hosting service, please let me know):
https://drive.google.com/open?id=0BycCshQzwZmBaUtialo5Y01Dc3c
Good luck and don't forget to report back!
I will try to do my best to help you, but I have a family and I inted to spend most of my time with them. Please be patient!
If you like my work, you can buy me a beer, it is damn hot here right now, and I would love to drink one
Click to expand...
Click to collapse
Any help don't want reistall all again!!!!
is my twro .img is on cd/adb what command i write to flash this beauty?
Well, I was able to boot to TWRP, and successfully flashed WETA audio mod. However, upon rebooting, the V4A app wasn't there.
gubacsek said:
You are welcome! Try to imagine how happy I was when I first succeeded At that time I had to issue 5 commands after boot, and restart it twice to make it work
But I was already able to flash ARISE sound mod and I almost cried of joy
Click to expand...
Click to collapse
Hilariously, the ARISE sound mod is exactly why I had flashed back from DP4. I'm close with those guys and they know their stuff for sure.
mngdew said:
Well, I was able to boot to TWRP, and successfully flashed WETA audio mod. However, upon rebooting, the V4A app wasn't there.
Click to expand...
Click to collapse
Same here
I just tried ARISE. This one installs, but failed to update the driver.
mngdew said:
I just tried ARISE. This one installs, but failed to update the driver.
Click to expand...
Click to collapse
Interesting. I also tried side loading the v4a apk packaged in WETA, granted root permissions and it attempted to install drivers but failed.
mngdew said:
Well, I was able to boot to TWRP, and successfully flashed WETA audio mod. However, upon rebooting, the V4A app wasn't there.
Click to expand...
Click to collapse
maflin18 said:
Same here
Click to expand...
Click to collapse
mngdew said:
I just tried ARISE. This one installs, but failed to update the driver.
Click to expand...
Click to collapse
maflin18 said:
Interesting. I also tried side loading the v4a apk packaged in WETA, granted root permissions and it attempted to install drivers but failed.
Click to expand...
Click to collapse
Guys! Check the free space on /system! On Android O DP4 I had about 100MB free space, and I had to remove some **** before flashing anything. Try /system/app and Pinyin input, Chinese input apks....
The recovery is fine...
What? I don't know what I did differently this time, but the the app keeps asking to install the driver again and again everytime I open the app even though there was a successful driver installation notification.
gubacsek said:
You are welcome! Try to imagine how happy I was when I first succeeded At that time I had to issue 5 commands after boot, and restart it twice to make it work
But I was already able to flash ARISE sound mod and I almost cried of joy
Click to expand...
Click to collapse
Can u pls send link for arise which u have flash...
kiran8631 said:
Can u pls send link for arise which u have flash...
Click to expand...
Click to collapse
It was this one:
https://drive.google.com/file/d/0BycCshQzwZmBRFRJSXAwTDhHcm8/view?usp=drivesdk
At last! I got it working.
gubacsek said:
It was this one:
https://drive.google.com/file/d/0BycCshQzwZmBRFRJSXAwTDhHcm8/view?usp=drivesdk
Click to expand...
Click to collapse
Facing this issue...

[Root][SM-T590] Samsung Galaxy Tab A 10.5 (2018) root tutorial

Disclaimer: Your warranty will be void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Hi.
Based on the feedback from this thread, the following steps can be used to aquire root on the SM-T590. The process is quite similar to rooting other devices by using Magisk. It might also work on other versions of the SM-T59x family, which can be OEM unlocked (sorry Verizon users).
Obtain the boot image
Get the firmware that matches the version installed on your device. This is important, otherwise you can easily end up in a bootloop.
Extract the AP tar.md5 file, e.g. "AP_T590XXU2ARJ1_CL14463952_QB20043720_REV00_user_low_ship_MULTI_CERT_meta.tar.md5".
Upon the extracted files, there is a file called boot.img.lz4. Extract it. Important: Most standard compression tools, e.g. 7-zip, are unable to extract lz4 compression ccorrectly. Use the offical lz4 binary from your Linux distribution or get the Windows version here. Once extracted, you should have a file called boot.img.
Patch the boot image
Copy the boot.img file to your device.
Download and install the Magisk Manager apk from the offical Magisk Thread.
In Magisk Manager settings, set the image format to "img.tar".
Enable the "Keep AVB2.0/dm-verity" in the Magisk main screen.
Hit "Install" and select "Patch boot image".
Select the boot image copied previously to your device.
Once finished, the patched image will be located in the Download directory on the internal storage.
Copy the patched image back to your PC.
Unlock and flash
Go into settings and enable developer settings.
In the developer settings, select OEM unlock, read the help text and enable the unlock, if you consent.
Once the device is factory reset and rebooted, turn the device off.
Boot the tablet into download mode.
Flash the patched boot image with Odin in the AP-slot
Reboot, Install Magisk Manager apk again and check if root is available.
Have fun.
Thanks to @gscollier, @airmaxx23 and @EinsamerSpieler for testing.
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
did you find a solution?
stupid question
I know this is a dumb question but where do you get the firmware....
Also was wondering if that reboot thing is still an issue.
I'll still root, I would like to try the LineageOS, eventually... how well does this work with Android apps/F-droid?
Update: still looking for confirmation on which boot image to use... guess you can't do a backup before flashing like you used to be able to do.
I installed heimdall and adb both seem to work
heimdall instructions
User848 said:
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
Click to expand...
Click to collapse
the same happens to me.
I also tried removing some microsoft apps with Titanium, but after removing the excel, it goes to a kernel panic...
And then there's the "Security notice" from "SecurityLogAgent" notifications (unauthorised actions have been detected, unauthorised access to a secured area)
any solutions, followed steps but no root
I have the same problem Root is present but once i try to rename a file in /system/app, the device reboots.
Using SM-T590 with canadian image:T590XXU2ASC1
Using Magisk version V7.1.2(208) - V19.1 (19100)
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Quick help please, I have the patched boot image on my pc but when I click the AP slot on odin it doesnt detect it only finds tar, md5 files etc. in the settings i cant change the format to .tar there is no option.
IET_DEMO said:
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Click to expand...
Click to collapse
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
mingkee said:
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
Click to expand...
Click to collapse
Well I did it on android 8.1.0, seems like it work on Oreo too
IET_DEMO said:
Well I did it on android 8.1.0, seems like it work on Oreo too
Click to expand...
Click to collapse
How about Titanium Backup?
It works on rooted T510
mingkee said:
How about Titanium Backup?
It works on rooted T510
Click to expand...
Click to collapse
I dont have or use Titanium Backup, I usually clone my devices with twrp backup
There needs to be a better option that works without the current issues when rooting. You either end up with reboots or can not log in to Samsung account at all
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Would it work on 595? Bootloaders should be the same without boot loop?
vq8acsxht said:
Would it work on 595? Bootloaders should be the same without boot loop?
Click to expand...
Click to collapse
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
kidkrooks said:
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
Click to expand...
Click to collapse
Mine is on it's way. I will try it when I get it. I think bootloaders should be same in in both 590/595.
kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Does this still have "Modifying system files leads to reboot" issue or it's solved ?

Categories

Resources