Related
[Tutorial/Mod] Noob Proof how to Edit APK's / Replace “ god mode“with“Ownership Mode"
Tutorial for replacing the name “ god mode “ with the actual function name “ Ownership mode “
And Noob Proof Editing APK’s implemented on Tweaks
Other Posts Links
Solve WiFi Errors , Radio Problem, htc Dev Unlock Method ( how it really Works) Here
Credit
Credit goes to All Developers who enhanced the Original tweak
also to romanbb for creating the original tweaks.
N.B.
If you are not interested in knowing how to edit an APK or Create a Flashable Zip , then Kindly stop here and move on the the next thread of importance to you , Cause this is a long thread
content
Tutorial for Editing APK’s implemented on Tweaks APK included in Rom v7.1 by Developerrobocik
Mod for Rom v7.1 by Developerrobocik , see Ownership Mode a.jpg , Ownership Mode b.jpg
This tutorial can be used with any custom Rom to Edit an APK ( Settings , tweaks , MikTweaks , RCMix Tweaks , … etc ) in about 5 ~ 10 min in the first time , and no more 3~5 min afterwards
i used it for GB APK's , didn't test it with ICS APK's yet
Mod
This Mod is for Rom v7.1 by Developerrobocik ( it functions normal as is , it only changed the displayed string name , Note that some functions need to download components in order to work )
This Mod will restores the string “god mode “ into its actual full development name “ Ownership mode “ or “Get Ownership mode “ , which is more relevant development wise “
Download Links
Mod – Replacing name to Ownershiop Mode or Ownershiop Mode ( Flashable zip ) , For Manual replacement extract the files from within the Mod
Tweaks_for_robocik_Rom_v7.1_Ownership-signed and Permissions.zip
http://www.mediafire.com/?yca15ah0nne5iy9
Or Download attached Zip
All photo attachments and permissions photos
All attached and Permissions Photos.zip
http://www.mediafire.com/?5iihz5eki8a6xot
Or Download attached Zip
NB : Please feel free to PM me regarding any Questions and help in modifying similar APK for other Custom Roms or Rom Version for your own use
if you created your own similar Mod for a Different Custom Rom or Rom Version , PM me to add it in Post # 2
DISCLAIMER
I am not responsible if following this Method results in bricking your phone
Whatever you do is at your Own Risk
Tutorial replacing the name “ god mode “ with the actual function name “ Ownership mode “ or “ Get Ownership mode “
And Editing APK’s implemented on Tweaks
General
I tried to make this tutorial Noob Proof ( for those with little computer skills ) as much as possible , so it is a bit long
This tutorial is implemented on Tweaks , and can be applied for any custom Rom you use that includes ( Tweaks , RCMix Tweaks or any similar tweak ) to restore the name “god mode “ into its actual full development name “ Ownership mode “ or “Get Ownership mode “ , see Ownership Mode a.jpg , Ownership Mode b.jpg
This tutorial can also be used for editing the APK of your choice
Editing an APK means ( decompile “decompress “ the apk , edit xml and smali files , recompile the apk ) , and then sign the APK or zip file .
Please note that editing an apk without decompiling it first , will cause FC ( force Close )
Required tools and Links ( All Free )
Press on any text displayed in “ orange color “ to open the associated link ( web page , or Download link ) , always download latest software versions from those websites
Notepad ++ { to view and edit xml files and smali } , links for Notepad ++ web Page and Notepad ++ installer v5.9.8 ( 5 MB )
apktool { to decompile “ Decompress “ and recompile“ recompress “ APK files } , apktool web page , Download links forWindows users ( 4 MB) :
apktool v1.4.1 is recommended if you encounter error on newer versions of apktool ( in compiling or decompiling ) , provided that you are sure you have followed all steps correctly when using the newer version of apktool
Download apktool-* file ( for All operating systems )
and apktool-install-windows-* file ( Linux and mac users should choose appropriate file )
Unpack both zip files to the Same directory
Java Runtime Environment should be installed JRE or manually choose JRE for any Operating systems or offline installation
Zipsigner 2 ( NOT Zipsigner ) { to sign APK’s and Zip files } , Download Zipsigner 2from Android market
Windows Grep ( Optional ) { to seach all files inside an entire directory for a word } , ( in options you can change the editor to be Notepad++ ) , DownloadWindows Grep( less than one MB )
tips for using cmd window
you don’t need to write full path for the folder , just drag the folder from within “my computer” or Desktop to the cmd window and the path will be written automatically
also for names just copy a name and right click the toolbar of cmd window then choose edit then Paste , see att 1 - cmd Copy&Paste - apktools folder.jpg
You can use up and down arrows to toggle the previously used commands instead of writing them again
Press enter after typing any of the following commands
Steps
1. decompiling “ Decompress “ the APK
here you can find a more detailed information , Procedure , and solve errors
Open your Rom zip in a winrar window and drag the following files to your desktop ( or extract the zip file and find the files ) :
Framework-res.apk located in System \ framework
Tweaks ( or xxxtweaks according to how each rom name it ) located in System \ app
For certain APK’s ( like settings apk ) you will need to extract also com.htc.resources.apk and/or SystemUI.apk ( But this is not needed for tweaks apk )
Extract both apktool-* file and apktool-install-windows-* to the same folder and rename it to apktools and put it in the root of Drive C: ( it includes 3 files aapt.exe , apktool.bat , apktool.jar
Copy both Framework-res.apk and Tweaks.apk ( i.e Tweaks, RCMixTweaks , ???tweaks … etc ) inside apktools folder , see att 1 - cmd Copy&Paste - apktools folder.jpg
Go to windows start menu \ Accessories \ cmd , Right click it and choose run as administrator
In cmd window Navigate to apktools folder by typing the following : cd c:\apktools ( or type cd followed by a space then drag the folder apktools to cmd window ) , you should see this c:\apktools>
Now to decompile (for example tweaks.apk ) , see att 2 - cmd decompile & recompile.jpg
type the following :
Type apktool if framework-res.apk
Type apktool d tweaks.apk ( don’t forget to add “ .apk “ )
Use the exact same original APK name ( case sensitive upper or lower case ) , to avoid typing mistake use cmd copy and paste . Otherwise after editing and signing the apk and try to over-write the original apk , it will not replace the original apk and both APK’s will be there
If you want to over-right the created folder , use apktool d -f tweaks.apk , or delete the created folder and use apktool d tweaks.apk to create it again
A new folder is created with the same name of the Tweak ( i.e tweaks , ???tweaks , …etc ) inside c:\apktools , see att 1 - cmd Copy&Paste - apktools folder.jpg
The apk is now decompiled
( this is not needed for tweaks apk ) , For certain APK’s ( like settings apk ) that requires for example com.htc.resources.apk you will need to add it to apktools folder and execute apktool if com.htc.resources.apk
2. Edit xml and smali Files
Install Notepad++ and put a shortcut at the desktop
Four files to be modified :
open the 4 following files together with Notepad++ by dragging each file to Notepad++ shortcut at the desktop
system_prefs.xml , located in C:\apktools\Tweaks\res\xml\
SystemActivity.smali , located in C:\apktools\Tweaks\smali\com\{ name differ according to developer } rcteam\tweaks\system
SystemActivity$15.smali , located in C:\apktools\Tweaks\smali\com\{ name differ according to developer } rcteam\tweaks\system
godmode.bin located in your Rom zip inside System \bin
Use any PC explorer and navigate into c:\apktools\tweaks then do a search for word including “ god “ . open the files found in the search ( just drag them into Notepad++ shortcut on the desktop)
In Notepad++ press Ctl +F to open search window , type “ god ” and press “ find all in all open Documents “ , the results will be shown at the bottom of the notepad++ window , Double click any line of them and it will move you to its xml file
Replace the string “ god “ with the string “ ownership “ or “ Get Ownership “ as follows :
Double click any line of them and it will move you to its xml file , only replace the highlighted strings
system_prefs.xml : for Android : title ( replace with “ ownership “ or “ Get Ownership “ ) , for Android : key (replace with “ ownership “ to read “ownershipmod_command “ ) , see att 3 - system_prefs.jpg
SystemActivity.smali : replace with “ ownership “ to read “ownershipmod_command “ , see att 4 - systemActivity.smali.jpg
SystemActivity$15.smali : for line const-string v2 ( replace with “ ownership “ or “ Get Ownership “ ) , for line const-string v1 ( replace with “ ownership “ to read “ownershipmod_command “ ) , see att 5a - systemActivity$15.smali.jpg , att 5b - systemActivity$15.smali.jpg
godmode.bin : rename the file itself to ownershipmode.bin ( this file is edited and placed separately )
if needed for other APK’s , you can use Windows Grep to seach all files inside an entire directory for a certain word ( in options you can change the editor to be Notepad++ )
3. Re-compiling “ compress “ the APK
Run cmd as administrator , in cmd window Navigate to apktools folder by typing the following : cd c:\apktools ( or type cd followed by a space then drag the folder apktools to cmd window ) , you should see this c:\apktools> , see att 2 - cmd decompile & recompile.jpg
Type apktool b tweaks ( don’t add “ .apk “ )
Use the exact same original APK name ( case sensitive upper or lower case ) , to avoid typing mistake use cmd copy and paste . Otherwise after editing and signing the apk and try to over-write the original apk , it will not replace the original apk and both APK’s will be there
two new folder are created inside apktools \ tweaks folder :
A folder named “ Build “ , it includes the decompiled files with the saved changes
A folder named “ dist “ , it includes the new modified apk ( not signed yet )
If you want to over-right the created folder , use apktool b -f tweaks , or delete the two created folders and use apktool b tweaks to create them again
4. Signing the APK
Install Zipsigner 2 on your phone , note that the compiled APK is not signed yet
Create a folder on your sd card name it for example “ sign apk and zip “ , Copy the modified compiled APK to that folder
Start Zipsigner 2 and leave all settings as it is “ defaults “ , press “choose in/out “ and navigate to the compiled APK “ for example tweaks “ and select it , then press “ sign the File “ , a massage will tell you that the file is signed ,
Go to folder “ sign apk and zip “ and you will find the signed apk named as ( tweaks-signed.apk ) , copy ( tweaks-signed.apk ) to other location and rename it to ( tweaks.apk ) exactly as the original compiled apk
The apk is now ready to replace the original one located in system \ app
5.Apply the changes
Applying the changes can be done by either of the following two methods :
Create a MOD and Apply it from recovery
Manually by moving both the APK and bin file
Manually by moving both the APK and bin file inside the Custom Rom Zip before installing it
a) Using Manual Replacement
The modified apk is now compiled and signed and ready to replace the original one located in system \ app
Make sure that the modified APK has the exact same original APK name , Otherwise it will not replace the original apk and both APK’s will be there
Set system to read\write using Root Explorer or the original tweak itself ( open tweak then go to system tab , and choose mount system reaed/ write )
Use Root Explorer or any similar apk to review permission and ownership values before over-writing the required APK or bin file
Over-write the Apk or file and correct permission and ownership values to the same values for the original APK or bin fileTweaks Permissions.jpg , Tweaks Owner.jpg ( values are different for other similar tweaks ).
For ownershipmode.bin file , navigate to system \ bin , review permission and ownership values before deleting godmode.bin, then delete godmode.bin and copy ownershipmod.bin inside system \ bin , and correct permission and ownership values to the same values for the original file Ownershipmode Permissions.jpg , Ownershipmode Owner.jpg ( values are different for other similar tweaks )
b) Using MOD Replacement
Put the flashable zip ( MOD ) in your SD Card , Reboot into recovery
Clear dalvik and Cache , use install zip from SD Card , navigate to the file and install it then reboot
6.signing Zip file ( create your own MOD )
For future versions of tweaks apk , your can edit the new APK and use the attached MOD, just over-write the existing files with yours , and flash it
In general you can create a folder with the same attached structure
Create a folder let us call it “ Work “ , Create two folders inside it (META-INF , system ) according to the above attached structure ,
Add both update-binary and updater-script inside folder META-INF \ com \ google\ Android ,
Add the files you want to update inside System folder ( use the same structure as in the original Rom),
highlight both of the two folders (META-INF , system ) then right click then choose send to then compressed folder ( Don’t compress the “ Work folder itself ) , rename the created zip as you prefer
Place prepared zip file on your SD Card and use the same procedure mentioned in Step no 4 (Signing the APK ) and in Step no 5 B ( Using MOD Replacement )
General Notes
+- META-INF/
+- MANIFEST.MF
+- CERT.SF
+- CERT.RSA
...........................com/
.....................................google/
.................................................android/
...............................................................update-script
...............................................................update-binary
...............................................................updater-script
+- system/
.................app/
.........................Tweaks.apk
..................bin/
.........................ownershipmode.bin
Note that the structure of META-INF ( name is case sensitive , as in above att 7 ) is always the same ( MANIFEST.MF , CERT.SF , CERT.RSA are created during singing the flashable zip )
the /system folder can be anything you need ( in our case Tweaks.apk and ownershipmode.bin ) , to add different items for your update you should then if needed modify Updater Script accordingly ,
update-binary , updater-script are needed to let the zip file to be flashable zip ( update.zip ) , For backward compatibility reasons, it's still possible to also add an update-script file.
updater-script is where you put the required commands to be executed during flashing the zip
7. Adding your own Similar Mod or APK here in Post # 2
you can Add your own Similar Mod of Modified APK here in Post # 2 ( For Different Custom Rom or Different Version of a Rom ) , Please PM me
Press the thanks Button for this Post
Reserved .......
Reserved .......
Reserved .......
Reserved .......
Thank you for your time and effort, great tutorial.
Thanks for this great guide. Very helpful and informative.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Thanks for posting this, I will be spending more time on it this weekend. Hopefully this will get you RC status.
Hi,
Have a small doubt regarding APK. Below is what i did,
1. Renamed the SystemUI.apk with .zip
2. Changed the necessary image files in res\drawable-hdpi
3. Renamed the SystemUI.zip to SystemUI.apk
4. Pushed to the \System\app folder.
Problem,
When i moved to System\app app doesn't work. got force closes.
Question:
Am i need to sign apk ? I just changed the .png files, still am i need to sign the apk?
Cyb0rgz said:
Hi,
Have a small doubt regarding APK. Below is what i did,
1. Renamed the SystemUI.apk with .zip
2. Changed the necessary image files in res\drawable-hdpi
3. Renamed the SystemUI.zip to SystemUI.apk
4. Pushed to the \System\app folder.
Problem,
When i moved to System\app app doesn't work. got force closes.
Question:
Am i need to sign apk ? I just changed the .png files, still am i need to sign the apk?
Click to expand...
Click to collapse
after moving the apk ..if its not signed ..you need to fix the permissions ..you can do this via recovery
ganeshp said:
after moving the apk ..if its not signed ..you need to fix the permissions ..you can do this via recovery
Click to expand...
Click to collapse
Thank you for your time in responding!
Yes, i have given necessary permissions as well. but it doesn't seems to work!
if i am changing the .dex files, am i need to sign the apk? On changing the png images and all, am i need to sign it? Among the two, which one requires apk signing?
Backstory
OK if you want to know a little backstory read this post.
This Post is Windows exclusive because it requires Odin and as the Website hosting JOdin (https://forum.xda-developers.com/showthread.php?t=2598203) is down i am unable to find a good substitute. Heimdall isn't working for me...
Disclaimer
This should not cause any dataloss but there is always a slight chance.
I am not responsible if anything goes wrong.
Device Compatibility
Here is a list of Devices which are confirmed to be fixed by this method. Theoretically it should work with every Samsung.
Galaxy J5 (SM-J500FN)
Please let me know if it also works for you (add your exact Device Name)
You will need:
Samsung Device Firmware type in exactly your device name, then select country/provider and download the newest version for you Android version
WinRAR of cours (on Windows)
SkipSoft Unified Android Toolkit
Samsung USB Driver (if you haven't them already)
and Odin
Instructions
1. Open the downloaded firmware .zip archive and extract the content. Then open the extracted .tar.md5 archive again with WinRAR and extract boot.img
2. Install SkipSoft Unified Android Toolkit
3. Copy the boot.img file to the INPUT folder in the installation path of the Toolkit
4. Start it and write 99 for Basic Android Toolkit (and wait for the Downloads to finish if you are using it the first time)
5. Type 8, enter, 2, enter, check if only the boot.img file is listend, then type yes
6. Copy the .tar file from the OUTPUT folder to a folder of your liking
7. Install the USB Drivers
8. Power down your Phone and hold the [VolumeDOWN + POWER + HOME] to enter Download Mode (to confirm press [VolumeUP])
9. Start Odin and Connect you Phone to you PC. If the Device is detected properly the Log box should say something similar to "<ID:0/004> Added!!"
10. press the AP button (formerly PDA) and choose the .tar file you created befor
11. Then press start. If Odin was successful in the left corder should be a green square saying passed
IF UNSUCCESFUL: try using a USB 2.0 usb port on you PC/Laptop if you have one. On PCs try using the motherboard ports on the back
If you get any errors please let me know.
Cannot Find INPUT and OUTPUT folder
I cannot locate INPUT and OUTPUT folders in c:\Unified_Android_Toolkit and confused. Stuck at this stage. Do I create the folder myself? Please advise. Thanks
AcharyaJeeS said:
I cannot locate INPUT and OUTPUT folders in c:\Unified_Android_Toolkit and confused. Stuck at this stage. Do I create the folder myself? Please advise. Thanks
Click to expand...
Click to collapse
INPUT folder must be created and the OUPUT folder will be created by the tool
Please help!!!
Toby4213 said:
Backstory
OK if you want to know a little backstory read this post.
This Post is Windows exclusive because it requires Odin and as the Website hosting JOdin (https://forum.xda-developers.com/showthread.php?t=2598203) is down i am unable to find a good substitute. Heimdall isn't working for me...
Disclaimer
This should not cause any dataloss but there is always a slight chance.
I am not responsible if anything goes wrong.
Device Compatibility
Here is a list of Devices which are confirmed to be fixed by this method. Theoretically it should work with every Samsung.
Galaxy J5 (SM-J500FN)
Please let me know if it also works for you (add your exact Device Name)
You will need:
Samsung Device Firmware type in exactly your device name, then select country/provider and download the newest version for you Android version
WinRAR of cours (on Windows)
SkipSoft Unified Android Toolkit
Samsung USB Driver (if you haven't them already)
and Odin
Instructions
1. Open the downloaded firmware .zip archive and extract the content. Then open the extracted .tar.md5 archive again with WinRAR and extract boot.img
2. Install SkipSoft Unified Android Toolkit
3. Copy the boot.img file to the INPUT folder in the installation path of the Toolkit
4. Start it and write 99 for Basic Android Toolkit (and wait for the Downloads to finish if you are using it the first time)
5. Type 8, enter, 2, enter, check if only the boot.img file is listend, then type yes
6. Copy the .tar file from the OUTPUT folder to a folder of your liking
7. Install the USB Drivers
8. Power down your Phone and hold the [VolumeDOWN + POWER + HOME] to enter Download Mode (to confirm press [VolumeUP])
9. Start Odin and Connect you Phone to you PC. If the Device is detected properly the Log box should say something similar to "<ID:0/004> Added!!"
10. press the AP button (formerly PDA) and choose the .tar file you created befor
11. Then press start. If Odin was successful in the left corder should be a green square saying passed
IF UNSUCCESFUL: try using a USB 2.0 usb port on you PC/Laptop if you have one. On PCs try using the motherboard ports on the back
If you get any errors please let me know.
Click to expand...
Click to collapse
Hello.
I have this problem on a Galaxy J5 (SM-J500FN), but I can't download anything in download mode even with Odin, it fails every time. The phone gives a message reading MDM MODE CAN'T DOWNLOAD
Please help me how to fix this........
Thank you.
Thanks!!
Works perfectly on J5 2016 (SM J510FN).
I owe you, brooo!!
Successfully rooted Simbans 10" Excello Tab using Magisk Manager & SP Flash Tool
Rooting the Simbans 10' Excello Tab. Please note the usual warnings before you attempt rooting an Android device. You're probably voiding your warranty. You risk bricking your device. Neither I, nor the website where you found my words, assumes responsibility for your actions
I bought a 10" Simbans Excello Tab running Android Pie (9) for $130 USD in March 2020. I've rooted all of the ~20 Android devices I've owned. It seemed to me that $130 was a bargain price, but rooting it would be difficult. I found no reports of other owners successfully rooting the Excello Tab. I couldn't even find the OEM firmware for it on the mfr website, so I emailed them on the 4th of July asking for the firmware.
At my request, Simbans added the Excello firmware to its website (https://www.simbans.com/restore.html) on 5 July 2020, along with an SP flash tool, and both PDF and video flashing instructions. Prior to my request, Simbans only listed firmware for its Tango and Picasso tablets. N.B. Although I refer to the Excello firmware by different names, it's ExcelloTab 9.0 Base V1.rar on the official Simbans download site. Similarly, what I call the SP Flash Tool is the Reinstall Tool for Android 9.zip on Simbans' website.
The SP flash tool was a clue to how to root the Excello. SP flash tool is for flashing firmware onto Mediatek chips, which are used in several different phone and tablet brands, including the Excello Tab.
PREPARE YOUR PC. Download the Excello firmware rar file, SP Flash Tools zip, and Extract your SP Flash Tools zip file into a folder, and the Excello firmware rar file into another folder. Although most of you will be using Windows, n.b. there are Linux versions of the SP Flash Tool, and the 64 bit Linux version saved me from a hard brick situation. While you're doing that, download the Windows 10 MTK VCOM USB preloader drivers for your desktop computer.. Thoroughly vet your Windows drivers, following online guides. When you connect your powered off Excello Tab to your PC with SP Flash Tool running, you want to see the VCOM driver recognized (check with Device Manager). When you connect it with MTK Droid and Root Tool (which doesn't support Android >4.5) running, you want to see a different MTK USB driver recognized.
PREPARE YOUR EXCELLO TAB. Enable Developer Options and turn USB debugging on. You do not need to unlock the bootloader (so leave OEM unlocking off in Developer Options) to root the Excello Tab. Download and install root checker and Magisk Manager apps onto your Excello Tab.
In order to root the Excello, you need to hack the Excello's boot.img boot partition. But, we didn't get that file in the Excello firmware archive from Simbans. We will have to capture the Excello's boot partition. We do it by reading back the boot.img partition from RAM. There doesn't appear to be a simple boot.img file loaded onto the Excello. It'builds the boot partition from other files, like a boot-sign.img file.
Change the SP Flash Tool to allow capturing partitions, like the boot.img boot partition. Go to your SP Flash Tools folder, and edit the option.ini file in the SP Flash Tools archive. It's a text file, so use a text editor like Windows' Notepad or Ubuntu's Gedit. Find the [ReadBack] section of the file, and change ShowByScatter=false to ShowByScatter=true. Save your changes.
Run the SP Flash Tool as administrator by running the (Windows) flash_tool.exe with shift-right click on the file, or (Linux) sudo ./flash_tool.sh program. Set it up by selecting the Download tab near the top of the window. Choose your Download agent from the extracted firmware folder. Use the MTK_AllInOne_DA.bin choice. The correct Scatter-loading file for our Excello Tabs is the MT8163_Android_scatter.txt file. If you placed all of the extracted files from your Excello firmware rar file in the same location as the scatter file, the SP Flash tool will populate the fields for boot, recovery, etc. Correct any errors now, before you try to flash or use something that's so out of place that it bricks your device. You can click on any erroneous files and correct their path or name.
When you're ready to capture/readback your boot partition, select the Readback tab, and select only the boot partition. Make sure your Excello Tab is powered down and unplugged from the computer that's running the SP FLash tool. Choose the Read Back action. The tool will wait for you to connect your device. Hold the Volume Down button on your Excello Tab, connect the device, and release the volume down button when the red bar appears at the bottom of the tool window. The boot partition gets written as ROM_10 in your SP Flash tool folder. The boot partition will differ on different MT chip architectures, and different partitions. If your next action was to readback your Excello's (MT8163's) recovery partition, it would be saved as ROM_11, and so on.
If the readback succeeds, a green check mark icon appears on the tool screen, and your boot partition has been captured in a 10.8 MB ROM_10 file located in the SP Flash Tool folder..
Disconnect your Excello, power it up, copy the ROM_10 file to your Excello in a location you will remember, and rename it boot.img. I put mine in my Excello's internal memory's Downloads folder.
Run the Magisk Manager app on your Excello, It will tell you Magisk is not up to date. Click the INSTALL choice, confirm with yes, and choose Select and Patch a file as your method, Navigate to your just-saved boot.img file, and let Magisk do its thing. When it finishes, you will have a rooting magisk_patched.img to replace your stock boot.img. Copy the magisk_patched.img to your Excello firmware folder.
Before you flash your modified boot.img file (magisk_patched.img) to root your Excello, you have to modify your MT8163_Android_scatter.txt file (it's in your firmware folder) to only flash up to and including the boot partition. Load that scatter file in your text editor, and find the partition_name: boot. For the MT8163 chip, it's in the section starting with partition_index: SYS10. As you read about partition_index SYS10, you realize that SYS10 is where ROM_10 gets its name from. Different MT chips have different architectures. An MT6753 chip's boot partition will be in SYS8. After you've deleted all the sections following our 8163's SYS10, save the modded file with another name, like MT8163_Android_scatteredmoddedBOOTONLY.txt.
To root your Excello Tab, run the SP Flash Tool as administrator. Change the scatter file to the one you just modified. Choose the Download tab. The scatter file should only give you the boot partition as a familiar target. Check that partition, and select the magisk_patched.img. Power down your Excelo. Press the Download action on the SP Flash Tool. Hold the Excello's Volume Down button and connect the Excello to your PC running the SP Flash Tool. Release the button when the red bar appears on the flash tool. When the flashing completes with a green check mark icon, unplug the Excello. Boot it up, run Magisk Manager and your root checker. You should have a rooted tablet.
At one point, I hard bricked my Excello. It was my fault, but my Excello wouldn't respond to its power button There was an apparent Windows driver problem, as my Excello Tab wasn't recognized by my Windows PC when bricked, so the SP flash tool errored out with an unrecognized device. Luckily, there's a 64 bit Linux version of the SP Flash tool, and the Linux kernel read the MediaTec chip, allowing the Linux version of the SP flash tool to successfully flash the OEM firmware to unbrick the Excello, readback/create the boot.img, and flash the Magisk_patched.img to root the Excello Tab tablet.
If any of these instructions are confusing or contradictory, ask for clarification before you turn your beautiful $130 10" bargain tablet into the most expensive paperweight you ever bought.
i did all the steps up to the readback part it gives me error i try to readback the boot part and that i have done so far to the tablet
exglynco said:
Before you flash your modified boot.img file (magisk_patched.img) to root your Excello, you have to modify your MT8163_Android_scatter.txt file (it's in your firmware folder) to only flash up to and including the boot partition. Load that scatter file in your text editor, and find the partition_name: boot. For the MT8163 chip, it's in the section starting with partition_index: SYS10. As you read about partition_index SYS10, you realize that SYS10 is where ROM_10 gets its name from. Different MT chips have different architectures. An MT6753 chip's boot partition will be in SYS8. After you've deleted all the sections following our 8163's SYS10, save the modded file with another name, like MT8163_Android_scatteredmoddedBOOTONLY.txt.
Click to expand...
Click to collapse
Hey man, awesome work here. I am trying this myself but I am having trouble going through the part I quoted above. Can you help clarify this? Thanks in advance!
I'm sorry, guys, for not checking in more often. I dropped my Excello and cracked its screen some time ago.
Anyway, I found my old working directory for my rooting Excello project, and attached a couple of screen captures to show you what the OEM scatter.txt file looks like. I used Ubuntu's gedit to open/edit the file. The old CTRL-F command opened up a search box, which found SYS10 around line 179. Chop the file after the SYS10 section/discussion, after line 192, and save the altered file as discussed. See the second screen capture file.
I have managed to revive my "black screen, constantly restart" Nokia 3 (TA-1032). Actually the hard part is to find the correct firmware and DA file. So this will mostly be a resource sharing post than a fully guide.
Things needed:
Firmware (Source)
SP Flash Tool
Download Agent (Source)
nbo unpack script
Latest Python 3 (If you are using a Linux distro, it is most likely to be preinstalled).
Note that Python 3 means Python 3.x(.y), not Python 3.0.
If you are using Windows 7, you can only use Python < 3.9.
Steps:
Download (and install) SP flash tool (5.x).
Download firmware, the download agent and the script.
Extract the downloaded firmware
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
Run SP flash tool (with root/admin privilege).
In the Download tab: Select the "Download Agent" as the downloaded "Download Agent" file from the above link. Select the "Scatter-loading file" as the scatter file from the extracted firmware. And select "Download Only" mode. ("Authenication File" can be left empty). Just let it be the default (all boxes checked, even preloader).
Plug the phone into the computer and click "Download". If the tool just stucks at 0%, or any error occurs that prevent the flash from starting, press and hold both the POWER and VOL UP button on the phone for about 10 secs, and it will be restarted. The click "Download" again (try it again if the error still occurs).
After done with flashing (green tick), close the program and disconnect the phone from the computer. Wait for about 2 mins (idk if it is necessary) then hold POWER to start the phone. Then wait for a long boot ("NOKIA" logo).
Now you have unbricked you phone. Enjoy
Hi,
Thank you for uploading this, I have problems too with my Nokia 3 TA-1032. It's different case than yours, but still I can't turn it on. Can you please write down, how exactly I supposed to run your script in Python3? I have difficulties to extract files. Thank you very much forwardly
JustAGuyWithAndroidPhone said:
Hi,
Thank you for uploading this, I have problems too with my Nokia 3 TA-1032. It's different case than yours, but still I can't turn it on. Can you please write down, how exactly I supposed to run your script in Python3? I have difficulties to extract files. Thank you very much forwardly
Click to expand...
Click to collapse
I'm assuming you are using Windows.
First, download Python 3 from here, then open the downloaded file to install Python.
While installing, if you see a checkbox that say "Add to PATH", check it. Then proceed to complete your installation.
After installing, download the "nb0 unpack script" to the same folder/directory as the firmware file (.nb0).
In that folder/directory, hold Shift and right-click on the file explorer, then click "Open powershell window here" or "Open command window here" (example).
Then type this into the command window (if you have changed the files' name, you also have to change them in the command)
Code:
python nb0-unpack.py NE1-215H-0-00WW-B02.nb0
huupoke12 said:
I'm assuming you are using Windows.
First, download Python 3 from here, then open the downloaded file to install Python.
While installing, if you see a checkbox that say "Add to PATH", check it. Then proceed to complete your installation.
After installing, download the "nb0 unpack script" to the same folder/directory as the firmware file (.nb0).
In that folder/directory, hold Shift and right-click on the file explorer, then click "Open powershell window here" or "Open command window here" (example).
Then type this into the command window (if you have changed the files' name, you also have to change them in the command)
Code:
python nb0-unpack.py NE1-215H-0-00WW-B02.nb0
Click to expand...
Click to collapse
Thank you very much for your advice, the unpacking worked, but the flash not somehow. Here is a picture about what Error code I get.
JustAGuyWithAndroidPhone said:
Thank you very much for your advice, the unpacking worked, but the flash not somehow. Here is a picture about what Error code I get.
Click to expand...
Click to collapse
You didn't select the "Download-Agent" as the Download Agent file from the link on my post. You are using the default Download Agent file of SP Flash Tool. You may also want to download the latest version of SP Flash Tool.
huupoke12 said:
You didn't select the "Download-Agent" as the Download Agent file from the link on my post. You are using the default Download Agent file of SP Flash Tool. You may also want to download the latest version of SP Flash Tool.
Click to expand...
Click to collapse
Yes, you right, because the SP tool don't accept that. Here is a pic about that:
I downloaded the latest SP tool from the link above here in your post.
JustAGuyWithAndroidPhone said:
Yes, you right, because the SP tool don't accept that. Here is a pic about that:
I downloaded the latest SP tool from the link above here in your post.
Click to expand...
Click to collapse
Can you try placing the files to a "legacy-compatible" directory (no spaces, only ASCII characters (like a password)). For example, try placing the files (download agent, firmware, SP Flash Tool) in "C:\phone\nokia3\".
Yes, I relocated as you writed down, and now the download agent is accepted (that one which you linked here above), in an earlier version from the Flashtool, not the latest one. Flashing still need authorization file somehow. ( I tried to flash a rom with Authorization file needed, probably that going to be the reason. Originally I wanted to downgrade my Nokia 3 TA-1032)
huupoke12 said:
Can you try placing the files to a "legacy-compatible" directory (no spaces, only ASCII characters (like a password)). For example, try placing the files (download agent, firmware, SP Flash Tool) in "C:\phone\nokia3\"
Click to expand...
Click to collapse
Yes, I relocated as you writed down, and now the download agent is accepted (that one which you linked here above), in an earlier version from the Flashtool, not the latest one. Flashing still need authorization file somehow. ( I tried to flash a rom with Authorization file needed, probably that going to be the reason. Originally I wanted to downgrade my Nokia 3 TA-1032)
huupoke12 said:
Can you try placing the files to a "legacy-compatible" directory (no spaces, only ASCII characters (like a password)). For example, try placing the files (download agent, firmware, SP Flash Tool) in "C:\phone\nokia3\".
Click to expand...
Click to collapse
I have mistakenly deleted the os of my Nokia 3. PLEASE HELP!!!
The SP Flash tool is still not accepting the download agent!
PLEASE HELP!
Nokia3root said:
I have mistakenly deleted the os of my Nokia 3. PLEASE HELP!!!
The SP Flash tool is still not accepting the download agent!
PLEASE HELP!
Click to expand...
Click to collapse
If you have done the steps exactly as in my instruction and it still fail, then I can't help you anymore. Your phone may be in a different state than mine.
I have successfully unbricked my Nokia 3 (in a constantly restart cycle) on Arch Linux (I don't use Windows). If you want to give it a try, and if you are used to Windows User Interface, I recommend Linux Mint Cinnamon (Ubuntu is another popular choice, but its User Interface is very different from Windows, and Arch Linux is not easy to install if you are not used to command line interface and have some Linux knowledge).
huupoke12 said:
If you have done the steps exactly as in my instruction and it still fail, then I can't help you anymore. Your phone may be in a different state than mine.
I have successfully unbricked my Nokia 3 (in a constantly restart cycle) on Arch Linux (I don't use Windows). If you want to give it a try, and if you are used to Windows User Interface, I recommend Linux Mint Cinnamon (Ubuntu is another popular choice, but its User Interface is very different from Windows, and Arch Linux is not easy to install if you are not used to command line interface and have some Linux knowledge).
Click to expand...
Click to collapse
ok, i will try
huupoke12 said:
I'm assuming you are using Windows.
First, download Python 3 from here, then open the downloaded file to install Python.
While installing, if you see a checkbox that say "Add to PATH", check it. Then proceed to complete your installation.
After installing, download the "nb0 unpack script" to the same folder/directory as the firmware file (.nb0).
In that folder/directory, hold Shift and right-click on the file explorer, then click "Open powershell window here" or "Open command window here" (example).
Then type this into the command window (if you have changed the files' name, you also have to change them in the command)
Code:
python nb0-unpack.py NE1-215H-0-00WW-B02.nb0
Click to expand...
Click to collapse
I am unable to extract the files! PLEASE HELP!!!
huupoke12 said:
I have managed to revive my "black screen, constantly restart" Nokia 3 (TA-1032). Actually the hard part is to find the correct firmware and DA file. So this will mostly be a resource sharing post than a fully guide.
Things needed:
Firmware (Source)
SP Flash Tool
Download Agent (Source)
nbo unpack script
Steps:
Download (and install) SP flash tool.
Download firmware, the download agent and the script.
Extract the downloaded firmware
Install `python3` if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
Run SP flash tool (with root/admin privilege).
In the Download tab: Select the "Download Agent" as the downloaded "Download Agent" file from the above link. Select the "Scatter-loading file" as the scatter file from the extracted firmware. And select "Download Only" mode. ("Authenication File" can be left empty). Just let it be the default (all boxes checked, even preloader).
Plug the phone into the computer and click "Download". If the tool just stucks at 0%, or any error occurs that prevent the flash from starting, press and hold both the POWER and VOL UP button on the phone for about 10 secs, and it will be restarted. The click "Download" again (try it again if the error still occurs).
After done with flashing (green tick), close the program and disconnect the phone from the computer. Wait for about 2 mins (idk if it is necessary) then hold POWER to start the phone. Then wait for a long boot ("NOKIA" logo).
Now you have unbricked you phone. Enjoy
Click to expand...
Click to collapse
THANK YOU VERY MUCH, BROTHER!!!!!!!!!!!!!
It worked!!
Now just have my story..... Actually, this was my friend's Nokia 3 which he gave me to root and I convinced him that I would root it and convinced him that there was no risk in it. Then I rooted the device for him very hardly but then I mistakenly deleted the os of the phone and then I searched the whole internet and found your post.... First of all, I got many errors while unpacking the nb0 file as I was using python 3.0, so I downloaded the python 3.8 installer but it wouldn't install because it was saying that that Service pack 1 was not installed in my Windows 7 but it was, hence I got very irritated and observed the log file and downloaded an update (KB3033929). Then I installed python 3.8 and thus I come to have a working mobile! I again rooted it and gave it to my friend and told him about these happenings.
Once again thank you very much!!! You saved my respect!!
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. how can download scripte ?
majd11 said:
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. how can download scripte ?
Click to expand...
Click to collapse
Right-click on the "Raw" button at the top-right corner, and select "Save link as".
huupoke12 said:
Right-click on the "Raw" button at the top-right corner, and select "Save link as".
Click to expand...
Click to collapse
Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
please help me how do that ?? run the script with .nb0 can you make the vedio please
majd11 said:
Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
please help me how do that ?? run the script with .nb0 can you make the vedio please
Click to expand...
Click to collapse
Read #3 and #13
(#13 is correct, he just downloaded a wrong python version)
huupoke12 said:
I have managed to revive my "black screen, constantly restart" Nokia 3 (TA-1032). Actually the hard part is to find the correct firmware and DA file. So this will mostly be a resource sharing post than a fully guide.
Things needed:
Firmware (Source)
SP Flash Tool
Download Agent (Source)
nbo unpack script
Latest Python 3 (If you are using a Linux distro, it is most likely to be preinstalled).
Note that Python 3 means Python 3.x(.y), not Python 3.0.
If you are using Windows 7, you can only use Python < 3.9.
Steps:
Download (and install) SP flash tool.
Download firmware, the download agent and the script.
Extract the downloaded firmware
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
Run SP flash tool (with root/admin privilege).
In the Download tab: Select the "Download Agent" as the downloaded "Download Agent" file from the above link. Select the "Scatter-loading file" as the scatter file from the extracted firmware. And select "Download Only" mode. ("Authenication File" can be left empty). Just let it be the default (all boxes checked, even preloader).
Plug the phone into the computer and click "Download". If the tool just stucks at 0%, or any error occurs that prevent the flash from starting, press and hold both the POWER and VOL UP button on the phone for about 10 secs, and it will be restarted. The click "Download" again (try it again if the error still occurs).
After done with flashing (green tick), close the program and disconnect the phone from the computer. Wait for about 2 mins (idk if it is necessary) then hold POWER to start the phone. Then wait for a long boot ("NOKIA" logo).
Now you have unbricked you phone. Enjoy
Click to expand...
Click to collapse
huupoke12 said:
I have managed to revive my "black screen, constantly restart" Nokia 3 (TA-1032). Actually the hard part is to find the correct firmware and DA file. So this will mostly be a resource sharing post than a fully guide.
Things needed:
Firmware (Source)
SP Flash Tool
Download Agent (Source)
nbo unpack script
Latest Python 3 (If you are using a Linux distro, it is most likely to be preinstalled).
Note that Python 3 means Python 3.x(.y), not Python 3.0.
If you are using Windows 7, you can only use Python < 3.9.
Steps:
Download (and install) SP flash tool.
Download firmware, the download agent and the script.
Extract the downloaded firmware
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
Run SP flash tool (with root/admin privilege).
In the Download tab: Select the "Download Agent" as the downloaded "Download Agent" file from the above link. Select the "Scatter-loading file" as the scatter file from the extracted firmware. And select "Download Only" mode. ("Authenication File" can be left empty). Just let it be the default (all boxes checked, even preloader).
Plug the phone into the computer and click "Download". If the tool just stucks at 0%, or any error occurs that prevent the flash from starting, press and hold both the POWER and VOL UP button on the phone for about 10 secs, and it will be restarted. The click "Download" again (try it again if the error still occurs).
After done with flashing (green tick), close the program and disconnect the phone from the computer. Wait for about 2 mins (idk if it is necessary) then hold POWER to start the phone. Then wait for a long boot ("NOKIA" logo).
Now you have unbricked you phone. Enjoy
Click to expand...
Click to collapse
my nokia phone is Ta-1032 mtk 6737 and the firmware in the link is mtk 6735 can I use this on my phone MTK 6737??
huupoke12 said:
I have managed to revive my "black screen, constantly restart" Nokia 3 (TA-1032). Actually the hard part is to find the correct firmware and DA file. So this will mostly be a resource sharing post than a fully guide.
Things needed:
Firmware (Source)
SP Flash Tool
Download Agent (Source)
nbo unpack script
Latest Python 3 (If you are using a Linux distro, it is most likely to be preinstalled).
Note that Python 3 means Python 3.x(.y), not Python 3.0.
If you are using Windows 7, you can only use Python < 3.9.
Steps:
Download (and install) SP flash tool.
Download firmware, the download agent and the script.
Extract the downloaded firmware
Install Python 3 if you haven't. Run the script with the downloaded firmware (.nb0) path as the argument. It will extract the files.
Run SP flash tool (with root/admin privilege).
In the Download tab: Select the "Download Agent" as the downloaded "Download Agent" file from the above link. Select the "Scatter-loading file" as the scatter file from the extracted firmware. And select "Download Only" mode. ("Authenication File" can be left empty). Just let it be the default (all boxes checked, even preloader).
Plug the phone into the computer and click "Download". If the tool just stucks at 0%, or any error occurs that prevent the flash from starting, press and hold both the POWER and VOL UP button on the phone for about 10 secs, and it will be restarted. The click "Download" again (try it again if the error still occurs).
After done with flashing (green tick), close the program and disconnect the phone from the computer. Wait for about 2 mins (idk if it is necessary) then hold POWER to start the phone. Then wait for a long boot ("NOKIA" logo).
Now you have unbricked you phone. Enjoy
Click to expand...
Click to collapse
please can i use this on my nokia 3 mtk 6737 ?
Hey everyone,
UPDATE: WORKS WITH ANDROID 13! You can now use the more stable verison!!
Thanks to the people at github, yujincheng08 , updated one of the github commits and was finally able to root this device.
How to unlock:
Should be the same as any other samsung device. Follow my S6 Lite guide.
How to root:
1. Download the firmware for your your tablet, i dont know if i can link the sites but you can google it. (frija is recommended and is the fastest)
2. Extract only the AP portion of the firmware.
3. Open up the AP portion with 7-zip or winrar
4. extract the boot.img.lz4 out of the AP file
5. Download Lz4 https://github.com/lz4/lz4/releases to your pc corresponding version.
6. Extract the LZ4 to the same area where the boot.img.lz4 is
7. Open command prompt in that folder and then do
Code:
lz4 boot.img.lz4 boot.img
8. Download this magisk version from github
Release Magisk v24.3 · topjohnwu/Magisk
For those coming from v24.1, check the full changelog for changes introduced in v24.2. [General] Stop using getrandom syscall [Zygisk] Update API to v3, adding new fields to AppSpecializeArgs [App...
github.com
9. Extract the app-release.apk
10.. Connect your tablet and put it in your downloads folder
11. Install it via th My Files or use a file explorer.
12. Move the boot.img into the tablet and use the magiks that you just installed and patch it using that .
13. Move the magisk_patched version back to your pc, rename it to boot.img and create a tar version of it (i used 7-zip)
14. Open up odin , put your device to download mode and then patch the AP using the boot.tar you just created.
15. It should reboot, wait a few seconds and it may reboot a couple times. Then it may ask you to factory reset and just reset.
16. Once you setup your tablet again, connect your pc and do all that usb setup agagin and then move that app-release.apk again.
17. Youre gonna have to install the app-release again but uninstall the magisk already installed on your device first then install it via the apk
18. It should say additional setup required so do that, reboot and you should have root!
Has anyone else tried this guide?? Not trying to brick my new tablet so would like to know if it works for anyone! Thanks in advance!
Awesomeslayerg said:
Hey everyone,
Thanks to the people at github, yujincheng08 , updated one of the github commits and was finally able to root this device.
How to unlock:
Should be the same as any other samsung device. Follow my S6 Lite guide.
How to root:
1. Download the firmware for your your tablet, i dont know if i can link the sites but you can google it. (frija is recommended and is the fastest)
2. Extract only the AP portion of the firmware.
3. Open up the AP portion with 7-zip or winrar
4. extract the boot.img.lz4 out of the AP file
5. Download Lz4 https://github.com/lz4/lz4/releases to your pc corresponding version.
6. Extract the LZ4 to the same area where the boot.img.lz4 is
7. Open command prompt in that folder and then do
Code:
lz4 boot.img.lz4 boot.img
8. Download this magisk version from github https://github.com/topjohnwu/Magisk/suites/4781599968/artifacts/133467701
9. Extract the app-release.apk
10.. Connect your tablet and put it in your downloads folder
11. Install it via th My Files or use a file explorer.
12. Move the boot.img into the tablet and use the magiks that you just installed and patch it using that .
13. Move the magisk_patched version back to your pc, rename it to boot.img and create a tar version of it (i used 7-zip)
14. Open up odin , put your device to download mode and then patch the AP using the boot.tar you just created.
15. It should reboot, wait a few seconds and it may reboot a couple times. Then it may ask you to factory reset and just reset.
16. Once you setup your tablet again, connect your pc and do all that usb setup agagin and then move that app-release.apk again.
17. Youre gonna have to install the app-release again but uninstall the magisk already installed on your device first then install it via the apk
18. It should say additional setup required so do that, reboot and you should have root!
Click to expand...
Click to collapse
https://github.com/topjohnwu/Magisk/suites/4781599968/artifacts/133467701
This site is don't work. Can you share this file?
Thanks for the notice. Just rooted my device successfully using the latest Magisk build from the master branch. Works great!
@ahrmakrm1235 The github artifacts link will only work if you are logged into Github (create a new account if need to, it is free).
first time rooter here. do you mind specifying what you mean by opening command prompt in the folder? i extracted the contents of the Lz4 application into the folder containing the boot file. when I open command prompt, i drag that folder there and then enter the code, but it's not doing anything.
Thank you so much. I success to root sm-t733
zriw said:
first time rooter here. do you mind specifying what you mean by opening command prompt in the folder? i extracted the contents of the Lz4 application into the folder containing the boot file. when I open command prompt, i drag that folder there and then enter the code, but it's not doing anything.
Click to expand...
Click to collapse
Use 7zip zs, free and works just like 7zip , easier method than the lz4 extract.
@Flaccthehawk I'm going to try it out now and see if it makes a difference. If not, I'll edit and add pictures or a screen recording of what I'm doing wrong.
Edit: I did everything correctly, but I'm having trouble flashing the tar file. It keeps failing. I've already tried updating to the latest odin version of 3.14 & I know the firmware is correct because I downloaded it using frija. Any suggestions? I've attached what the error looks like below and my tablet in download mode in case there's an issue there.
In step 13 when creating the tar file for the boot image, what did you use for this? Did you use 7-zip? And did you select the tar option in the archive option in 7-zip (or another program)? Note that it must be a proper tar file. If the file created is a zip or 7z file, it won't work even if you rename the output file as a tar file.
Can you open the tar file using 7zip. Provide a screenshot of what is displayed here. Also within 7-zip after opening the tar file, click into File - Properties and provide a screenshot of this also.
FYI: I actually removed root for now. I noticed the battery was draining a lot quicker than before with Magisk (I did a clean format/flash too when rooting the device). Removing root, battery life is back to normal.
I'm new here, do I need to unlock bootloader before process this?
Yes, the bootloader needs to be unlocked. Note that the device will be erased when unlocking the bootloader so backup any data that you need before doing so.
@1987tlz Yes, I used 7zip to to open the boot file and selected tar as you can see here.
Thank you so much, success to root (SM-T735).
Hi again, I have problem about SafetyNet test failed (basicIntegrity -, ctsProfile -, evalType BASIC), also I cannot enable MagiskHide (after I enable and back to Magisk home, it's change back to disable). Does it possible to bypass SafetyNet test and enable MagiskHide?
Many Thanks
@zriw It wasn't clear from the screenshots, but for the file patched by Magisk, did you rename this to boot.img? Once the file is named as boot.img, then you create the tar file as boot.img.7z. Now you should be to flash it again using Odin.
@imjizho It looks like you are not using a recent version of Magisk, as MagiskHide doesn't exist anymore. On the latest release, Zygisk needs to be enabled and then you can enforce and configure the DenyList.
For passing SafetyNet, the latest version of this module will do the job:
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
All done! Thanks a lot @1987tlz
I found that the problem occurred when I try to hide the Magisk app, it will installed previous version and cannot change back when restore.
1987tlz said:
FYI: I actually removed root for now. I noticed the battery was draining a lot quicker than before with Magisk (I did a clean format/flash too when rooting the device). Removing root, battery life is back to normal.
Click to expand...
Click to collapse
Can others confirm the battery drain with root?
Rooting was the first thing i did with the tablet, i have no reference if it is really draining the battery.
//edit:
removing some bloatware (netflix, chrome, and so one) lead me to a bootloop
Im not finding bootloader unlock and am not sure if i have done it correctly on this samsung device.
This is what i have done,
1.Settings>About Tablet>Software Information
2.Tap Build Number repetitively until Developer Settings Enabled
3.Settings>Developer Options
4. Turn OEM Unlocking on
Is this all there is to it? I feel like im missing something.
*** EDIT
Found that if holding both volume down and volume up while plugging the tablet into my PC i was able to find more options to bootloader unlock as well as warnings. After accepting those it did a factory reset. I hope this is all i needed to do.
Thank you, i have successfully achieved root!
Typhoon_Master said:
Can others confirm the battery drain with root?
Rooting was the first thing i did with the tablet, i have no reference if it is really draining the battery.
//edit:
removing some bloatware (netflix, chrome, and so one) lead me to a bootloop
Click to expand...
Click to collapse
Have you tried freezing the bloatware apps with Titanium Backup located in the Play Store?