Disclaimer : I am in no way an experienced developer and make sure that you have the stock firmware if needed. Please do not follow this guide if you do not know what you are doing.
Description
This is something I thought of doing as I needed this tablet for university work. I do not promise support but will post if I get more things like this done.
Kernel with Defex disabled for Samsung Galaxy Tab A 8.0 (2017) T385.
The boot image was repacked with a stock boot image and a custom compiled kernel only with modifications to remove defex and to be able to flash magisk on the latest firmware (XME-T385DXU3CTH2-20200828114930) which it was extracted from.
The ZImage is attached if you want to repack it by yourself.
I do not guarantee if this will work on your device. Flash at your own risk.
Notes on Flashing and Root
What I have used :
1. Flash boot.img to BOOT in heimdall with `--no-reboot`
heimdall flash --no-reboot --BOOT boot.img
2. Use key combo to get into TWRP Recovery
3. Factory Reset -> Type yes
4. Reboot into TWRP Recovery
5. Flash Universal+DM-Verity+and+ForceEncrypt+Disabler+(2020-11-02)
6. Flash RMM_Bypass_v3
7. Reboot into System and verify that the kernel version is correct (3.18.120 Feb 9 2021)
8. Reboot to Recovery and flash Magisk normally
Download
Github Release
Credits
@corsicanu - RMM_Bypass_V3
@SebaUbuntu - Device Tree Skeleton
References
RMM Bypass Guide
Compiling Kernel Guide
Defex Discussion Github Magisk
Android Image Kitchen
Probably keep another post just in case.
Its worked and my SM-T385 has been rooted !!!
Thank you so much for your kernel @brokenaxe
GitHub Link not working !!!
Thankyou sooo much mann.. You don't know how frustrated I was with three SM-T385 tabs in my office which were dead slow and desperately needed root. Those things straight up bootlooped after installing magisk and I was always back to square one. You're a lifesaver. Thanks again...
Related
Hi,
I've been trying to compile TWRP for Galaxy Tab Active 2, as I have one and no one was creating it.
I'm currently stuck on "recovery not seandroid enforcing" after flashing the recovery.
Configuration is as follows:
Minimal Omni + twrp from https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git
Source kernel downloaded from Samsung sources + other try with kernel pulled from stock boot.img.
My device tree + source kernel: https://github.com/Shedaim/gtactive2lte.git
Build succeeds (took some time, but it succeeds now).
So far I built recovery.img and boot.img on 10 different configurations with no luck.
Tried flashing the whole boot.img and tried the recovery alone.
Would appreciate some help on how to proceed.
Best regards,
Shedaim
EDIT: Managed to build TWRP. Find the new post here.
This thread is meant to address all the common hurdles that are commonly faced by people who are new to treble devices (chef to be specific) and help them to troubleshoot/avoid some small yet critical steps during flashing new ROMs and working with fastboot and recovery in general. It will be continually updated with new stuff as it goes along.
I will be referring to the Motorola One Power and Moto P30 Note as chef only from now on.
The unlocking guide is available in This XDA Thread!
IMPORTANT:
1. Flashing refers to the process of doing a clean flash, with the inclusion of fastboot -w command
2. Latest ADB and Fastboot drivers are required to be installed, else the installation may halt mid-way.
3. Stock ROM refers to the Android One ROM for the Motorola One Power [XT 1942-2]
IMPORTANT: AS OF RIGHT NOW, PEOPLE WHO HAVE INSTALLED STOCK PIE (EITHER VIA UPDATE OR FIRMWARE) WILL NOT BE ABLE TO USE ANY OTHER ROM OTHER THAN THE STOCK PIE ROM. RADIO INTERFACE LAYER IS BROKEN IN OREO SOURCE BUILT ROMS AND THAT CURRENTLY INCLUDES LINEAGE 16 SO PLEASE WAIT FOR PIE SOURCE CODE FROM MOTOROLA FOR THAT TO BE FIXED.
1. I unlocked my chef . How do I flash TWRP in place of the stock recovery?
Solution:Currently you cannot as there is no recovery partition in the device. You have to manually boot TWRP onto the device using fastboot to use it. Follow as directed:
Boot the device into fastboot mode
Use command fastboot boot <path/to/TWRP.img> to boot TWRP temporarily.
2. I am done with TWRP and I want to flash Lineage OS 16 on my chef. I simply flash the .zip archive right?
Solution:No. Before you flash anything,
Take a backup of atleast your EFS and PERSIST partitions using TWRP and off-load it for safekeeping to restore in future if needed. You can also trigger a full backup if you require.
SUPER IMPORTANT: Flash this .zip file to copy the System A/B partitions. If this step is skipped, you will be responsible to brick your own device. THIS STEP IS ONLY REQUIRED ONCE AND ONLY ONCE IN THE LIFETIME OF YOUR DEVICE! YOU WON'T BE NEEDING THIS THE NEXT TIME YOU FLASH ANY ROM. .
After that, flash your dearest custom ROM and get going.
For Lineage OS 16, follow This XDA Thread.
3. I am done testing LOS 16, I want to flash a GSI. Shall I use a stock Vendor Image for the GSI on my chef?
Solution:No. The stock Vendor image is causing bootloop issue in most GSIs. It is recommended to use Lineage OS Vendor to flash a GSI on chef. So flash LOS and then flash your favourite GSI.
Also, Super Important: for those who haven't used lineage before flahing a GSI, it is required to boot Lineage OS first before flashing a GSI.
4. I am done experimenting, I want to go back to the stock image. How do I proceed?
Solution:Follow this XDA thread for it. And don't install OTA updates directly from the device. It will come in the next step.
5. I want to install OTA updates on the stock ROM. How do I proceed?
Solution:Follow this XDA post for it. The installation process is described here. You have to be clever enough to get the appropriate OTA update.
Credits:
@erfanoabdi : TWRP, LOS 16, AB partition management
@rushiranpise : Unlocking guide
@dayask : Testing the process, guide for reflashing stock ROM
@nageen9211 : Testing ROMs
For any additional queries, feel free to contact us at our Telegram Group
For more regular updates, follow our Telegram Channel
Always remember: You have to be smarter than your smartphone to be able to use it!
Cheers and Happy Flashing!
Note to readers
The above guide is for stock kernels only (including lineage)
The custom Darkone Kernel has constant updates and fixes major bugs often. Please follow the linked thread to test it out if you want to. Cheers!
Anyone have flashed GSI ROM? FOr me after flash GSI HavocOS have bootloop :/
DIdn't flash copy system A/B partitions, stuck on bootloop with custom roms.
Watched some youtube videos and didn't read this post before flashing custom ROM. Flashed Custom ROM without flashing A/B partitions. Now I have a phone stuck on bootloop when done anything in TWRP. or I can use my phone with stock ROM installed by fastboot method.
Installing or restoring anything from TWRP results in boot loop.
Restoring the backup I made before flashing, completes the restoration process normally. But when rebooting to system, TWRP prompts me that no OS is installed. If I reboot anyway, its either stuck on bootloop or reboots to recovery and asks me to try again or factory reset, or boots into bootloader mode.
Installing custom ROM begins with Step 1, takes a bit time and starts step 2 and shows completed. Doesn't echos any comments. But when i reboot, same prompt shows saying no OS installed. Reboot anyway and stuck on bootloop or reboots to recovery and aks me to try again or factory reset, or boots into bootloader mode.
Now I installed stock ROM with fastboot method and phone is boots up into system just fine.
Sometimes TWRP can't mount anything.
So am I stuck with stock rom or is there any solutions?
Also, installing stock ROM with fastboot mode showed this error in between scripts
(bootloader) is-logical:xxx_a: not found
and
(bootloader) is-logical:xxx_b: not found
but is able to use the phone just fine with stock ROM.
Hi all, I just updated to April 2020 firmware with no issues. Just waiting on a Kirisakura update and we'll be right back to where we left off. =)
edit: nevermind, Kirisakura 4.2.0 works perfectly fine!
In case anyone is looking for them, here is the stock and Magisk Patched boot images:
Magisk v20.4 patched boot image: https://www.androidfilehost.com/?fid=4349826312261763723
Stock boot image: https://www.androidfilehost.com/?fid=4349826312261763724
I'll also post my update procedure in case it helps anyone else out. This was my first OTA on this device (just got it last month), and I was able to update with absolutely no problems, no loss of root, no need to change Magisk or EdXposed settings/modules/etc. SafetyNet still passes, etc. Very seamless and I'm definitely happy with going with a Pixel as my next device. =D
This is ONLY for QQ2A.200405.005 firmware - it goes without saying, PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING.
UPDATE PROCEDURE (using a PC. I know there are other posts covering other methods, but this was the fastest, easiest, most reliable and intuitive way for me, and I didn't need to do any additional research, so I chose to do it this way)
** I was previously on March 2020 firmware and these steps therefore correspond as such.
I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
this may not be necessary, but I didn't want to find out, plus this was the quickest and most intuitive way for me anyway.
1. boot into bootloader
----------------
** I was on Kirisakura kernel, so I needed to flash BOTH the stock boot and dtbo March 2020 images - make sure you flash the proper corresponding images to your current pre-update firmware.
2. fastboot flash boot boot.img
3. fastboot flash dtbo dtbo.img
- these steps to restore stock recovery, dtbo.img also necessary for some kernel installations
-----------------
4. use volume keys to change selection to boot to Recovery Mode
* when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload flame-ota-qq2a.200405.005-2b5150a4.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot flame-qq2a.200405.005-magisk_patched-20.4.img
9. done, start the phone
This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. So far, no issues at all for both me and my wife's phone (P4 XL and P4). Magisk and Xposed are playing nice with these builds so far.
All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
Edit: To be nice to the noobs, and also because I have nothing better to do at this moment thanks to the pandemic, here are the stock boot and dtbo images (FOR MARCH 2020) as well as a direct link to the April 2020 OTA zip:
flame-qq2a.200305.003-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261763748
flame-qq2a.200305.003-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261763749
April 2020 OTA Zip from Google: https://dl.google.com/dl/android/aosp/flame-ota-qq2a.200405.005-2b5150a4.zip
thanks for the guide and files! i followed it step by step and had no probs at all. i have both the 4 and 4XL and wanted to stop in and say thanks for both guides. update went smooth on both devices
btw i was using stock kernel but restored both the boot and dbto images just in case. no problems there either.
HELLO THERE
Here's a list of all working roms, twrps, kernels and more for MediaPad T5.
If you want a guide of how to install, go to this post.
Report issues to T5 Support group from here
I'm making a MEGA folder with all specific (needed to work) and non-specific zips, kernels and twrps
N-S --> CAN USE NON-SPECIFIC ZIPS (may not work)
S --> NEEDS SPECIFIC ZIPS TO WORK ( can use non-specific compatible too)
PR --> Pre Rooted ROM
PRX --> Pre Rooted but doesn't work
UR --> Un Rooted ROM
U --> Untested ROMs (may work but I've not tested it yet)
M --> MODDED FOR T5 COMPATIBILITY
Modded roms are tested and proved to work. All the roms in the list are
compatibles, but newer versions may cause some installation errors.
Join the telegram group if you have any issue and I'll take a look as fast as I can.
PRX - LineageOS by @DarkJoker360 N-S
LeaOS by @AltairFR S U
PR - CrDroid by @Hami_Do N-S M
I tried the following roms on AGS2-W09
Did not boot:
lineage-18.1-20220224-UNOFFICIAL-iceows-pra
crdrom-v313+211013-arm64-avZ
crDroid_v7.10_11-WAS-21092021
Too large to install:
crdrom-v315+220202-iceows-pra
Works:
lineage-18.1-20211106-UNOFFICIAL-prague
CryptLoad said:
I tried the following roms on AGS2-W09
Did not boot:
lineage-18.1-20220224-UNOFFICIAL-iceows-pra
crdrom-v313+211013-arm64-avZ
crDroid_v7.10_11-WAS-21092021
Too large to install:
crdrom-v315+220202-iceows-pra
Works:
lineage-18.1-20211106-UNOFFICIAL-prague
Click to expand...
Click to collapse
crdroid should work. Go to the telegram grou chat to get the modded version until I release it. crdrom is about to get fixed. Lineage too.
crDroid_v7.10_11-WAS-21092021 does work
same for:
lineage-18.1-20220523-UNOFFICIAL-prague
LeaOS-20220616-UNOFFICIAL-iceows-pra.img (uploaded 1 day ago)
It took me more than a day to figure this out but if you have flashed Magisk in one of these custom ROMs then you need to restore the original KERNEL.img and RAMDISK.img form your stock firmware, otherwise everything will boot loop (even if you restore the initial custom ROM you have flashed first time). This is mostly because Magisk modifies the boot.img to apply the root patch.
As a side note here: you can install magisk.zip through TWRP immediately after reflashing your starting/initial custom ROM to be able to boot as before.
To do this I have used HuaweiFirmwareFinder (website + proxy app) to download update.app and then extracted the imgs with HuaweiUpdateExtractor and then used fastboot to flash the images.
It is useful if you have remembered your previous stock version as there can be conflicts with other images (like erecovery or recovery_ramdisk) if they have different versions.
Also I have never used TWRP to do the inital flashings, just fastboot because I see many threads here with people bricking their tablets.
denzelcris said:
crDroid_v7.10_11-WAS-21092021 does work
same for:
lineage-18.1-20220523-UNOFFICIAL-prague
LeaOS-20220616-UNOFFICIAL-iceows-pra.img (uploaded 1 day ago)
It took me more than a day to figure this out but if you have flashed Magisk in one of these custom ROMs then you need to restore the original KERNEL.img and RAMDISK.img form your stock firmware, otherwise everything will boot loop (even if you restore the initial custom ROM you have flashed first time). This is mostly because Magisk modifies the boot.img to apply the root patch.
As a side note here: you can install magisk.zip through TWRP immediately after reflashing your starting/initial custom ROM to be able to boot as before.
To do this I have used HuaweiFirmwareFinder (website + proxy app) to download update.app and then extracted the imgs with HuaweiUpdateExtractor and then used fastboot to flash the images.
It is useful if you have remembered your previous stock version as there can be conflicts with other images (like erecovery or recovery_ramdisk) if they have different versions.
Also I have never used TWRP to do the inital flashings, just fastboot because I see many threads here with people bricking their tablets.
Click to expand...
Click to collapse
This makes sense as flashing the boot also flashes the KERNEL and RAMDISK (correct me if I'm wrong). But do you know if you should do the same if you flash the system? I'm trying to flash a GSI but my device goes to a boot loop after flashing the system.
crDroid is working...just dont forget to unpack the x.z-file
Hi, anyone can help me?. I'm trying to install leaos on my Huawei Mediapad T5 (i'm not new on this), but everytime i reboot It when It finish installing, It keeps rebooting when It has to show the first configuration screen.
Nevermind, i finally got It to work
So I Found Out How To Root SCV40 Or Any Japan Varient Matter Of Fact
This Does Require You To Have A PC And Have Odin And Download Mode In Tact
WARNING
THIS WILL TRIP KNOX AND CAN MAKE YOU LOSE ACCESS TO SAMSUNG PAY AND HEALTH AND STUFF
I WONT BE RESPONSIBLE FOR THE DAMAGE CAUSED BY YOU IF YOU MESS UP
IF THIS IS YOUR FIRST TIME GO WATCH SOME SAMSUNG ROOT VIDEOS FOR A BETTER IDEA
ONLY WORKS ON ANDROID 10, YOU COULD TRY IT ON LOWER VERSIONS BY DOWNLOADING LOWER FIRMWARE BUT AGAIN I AM NOT RESPONSIBLE FOR THE DAMAGE CAUSED
Method #1
DOWNLOADS:
N9600 Klabit Kernel
Modded Odin 1.14.1 ( I Used Normal 1.14.1 But Modded Is Better Sooooo Ok)
Firmware To Flash (Using Odin)
TWRP
Magisk (Go To Github And Download Cuz If There Is New Update You Will Get It Right Away)
Now....
How To Root:
Install Odin And Put Klabit Kernel On Your Phone SD Card
Flash The Firmware Using Odin In Download Mode
Flash TWRP In AP Section With Odin In Download Mode
Format Data In TWRP And Reboot To Recovery Again
Install Your Klabit Kernel In TWRP
Install Magisk
Congrats, Your Mobile/Phone Is Rooted
Special Thanks To:
Klabit For DM Verify Disabled Kernel
Topjohnwu For Magisk
Next Droid For Giving Me The Idea
Enjoy Your Rooted Phone/Mobile
Method #2
THIS DOES REMOVE THE DOCOMO LOGO IF YOU USING THE NORMAL SCV40 FIRMWARE
AND IT DOESNT HAVE BLOAT WARE
I RECOMMEND YOU USE THIS METHOD
So This Method Req A Custom Rom So Get A Custom Rom Or Get This One
Downloads:
Odin
Dot OS
TWRP
Magisk From Github
So Go Into TWRP And Wipe Data
Then Reboot Back Into TWRP
Install The Dot OS GAPPS Edition Or Dot OS And GAPPS With TWRP
After That Install Magisk With TWRP Or Boot Up The Phone First Then Install Magisk With TWRP
Enjoy Your Rooted Phone
Method #3
This Is Called The Stock Root Cuz It Req You To Root With The Stock Rom That Came With Your Phone
THIS IS KINDA RECOMMENDED CUZ I DID THIS ONLY ONE TIME
Downloads:
Odin
TWRP
N9600 Klabit Kernel
Magisk From Github
SCV40 Firmware For SCV40 Based Note 9
So What Your Gonna Do Is Flash TWRP With Odin And Boot Into TWRP
Download And Copy The Magisk And Klabit Kernel To SD Card
Go Into The Wipe Option In TWRP And Wipe Data
Install Klabit Kernel And Magisk Then Reboot To System
It May Bootloop For Some Secs But Then It WIll Be Done
Enjoy
Sub To Me One YT A Vid Will Be Coming Out About This Soon
THIS WILL NOT WORK FOR OTHER DEVICES
I FORGOT TO MENTION IT WILL BOOT LOOP FOR SOME SEC
no one gonna thank me?
n9600 works with scv40????
CheapPlayz said:
no one gonna thank me?
Click to expand...
Click to collapse
Thanks in Advance! I will give it a try on my Docomo variant.
Highsp30 said:
n9600 works with scv40????
Click to expand...
Click to collapse
no
CheapPlayz said:
no one gonna thank me?
Click to expand...
Click to collapse
Thanks for the guide, CheapPlayz! It helped me get on the right track to update my SCV40.
Brother thanks lot. BTW is there any android 12/13 custom roms for Note 9 ( SCV40) ?
Thanks bro! It's useful for my Note9(N-9600).
Final, I root my phone.
I am using a DOCOMO variant. Which kernel I should use? g9600 or g9650 or n9600?
please help! I am gonna do it tomorrow.