Related
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
How did you install Magisk?
When I open Magisk Manager v5.6.4, I get a "Magisk is not installed" and I only have the settings option.
No "install" options.
I have the same tablet. don't know of any twrp that can work with it, therefore leaving me with Magisk Manager only.
Id' be glad to get some help
Thanks,
SOLVED: You must have a functioning network interface in order for the "install" button to appear and you need internet connection to "install the v16 zip".
Magisk is OpenSource though, right? so probably it can be changed to allow offline installation as well.
Rooteed
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info!
I followed every steps till the end and everything went smoothly. But once I rebooted the tablet, I got the red label on the top left corner: "custom binary blocked by OEM lock". The tablet won't boot properly anymore "OEM unlock" was enabled in the Developers options, I double checked to be sure before flashing.
Edit:
Actually, the "custom binary blocked by OEM lock" appears as soon as I modify the system partition (I wanted to modify the Generic.kl in the keylayout folder on the system partition). If you do not touch anything, everything is fine.
[X-POST from here ]
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Keep in mind that you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)
Hello.
I tried this but when i using the magisk manager i have an error meassage and the following log:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.022 secs (48342181 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu)
- Boot Image Modification Tool
mmap failed with 12: Out of memory
! Unable to unpack boot image
! Installation failed
Can you help what i did wrong?
Thank you
oem unlock does not appear
SOLUTION FOUND
how do you oem unlock
I have wasted hours on this, waited weeks, tried the date trick with a legit setup, but the oem unlock never appears, running oldest version of firmware 7.1.1 feb 2018, what gives?
Tried reinstalling firmware via odin, successful flash but no factory reset. Suspect this made no difference. Got the security fail on PIT error, needed a new version of odin and selecting individual AP etc. files fixed this.
apparently you need a samsung or google account
So trying a samsung account... no dice
Now trying adding a sim card as well... success
OK after months of waiting and trying things, this just worked!
Update- I lost the date trick, have to wait 7 days after step 7 on auto date, just appears in developer options no need to press manual update.
https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-skip-rmm-prenormal-install-t3749468
- try downloading UK rom which was released before december '17 (october)
See if it lets the below process work again?
0/ install sim card (was not even the original carrier one in my case although my phone is not carrier locked)
1/ factory reset
2/ on reboot skip all accounts, do not enter a name do not turn on wifi, accept minimal amounts of things
3/ set date to 1/4/19 - turn off automatic date
4/ turn off automatic software updates
5/ enable developer options and turn off auto update system
6/ turn on wifi (date changes)
6b/ change date back
7/ Install samsung account (I went to samsung cloud) (date not changed but software update now triggered despite not touching manual update)
8/ (for interest look at manually check for software updates - it already says 1/4/19 last checked)
9/ reboot
10/ (date is now changed back to today again without my permission)
11/ (it pops up asking to install an update, despite auto updates turned off. - LATER)
12/ (last checked software date is now today (because I left wifi on I think through a reboot) this is 4/5/19 over 1 month later)
13/ go to developer options for the 27868745# time
OEM UNLOCK APPEARED HOLY ****
It is between Bluetooth HCI snoop log and Running services on the dev page, top of the developer options
Since the RMM prenormal thing triggered I had to do this again, so the above instructions do work.
If you stuff up the date just factory reset and start again. Reflash not required
I used a brand new throwaway samsung account for this but thats possibly up to you.
RMM state prenormal
OK now that I've jumped through hoops, installed TWRP
I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.
Apparently you need to install an RMM patch as well which is not mentioned in this thread.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
So, odin -> ap -> TWRP download
quickly press power-up-home when it resets!!!
recovery is not seandroid enforcing appears and TWRP starts.
1. back up all partitions to microsd!
2. install
a TWRP -> magisk
b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???
wipe cache/dalvik reboot
on boot:
"Verification failed"
"Unable to restart your device the integrity verification has failed.... erase all your data"
Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.
"Verification failed..."
I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.
Reflash TWRP with odin, now it halts at TWRP menu.
https://forum.xda-developers.com/ga...t/how-to-recover-verification-failed-t3775722
Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP
unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs
---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------
Take 3
"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
seems a few up to 6.0
BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP
Verification FAIL.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Take 4 - try reinstating boot.img with no mods.
Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet
Verification Failed! Reset
Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.
Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.
So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.
Or a new version of TWRP that supports encryption? 3230+ I have 3230...?
Try Stock RO system - twrp - dm verity - magisk
Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.
Verification failed again.
#&%^&^#%$#[email protected]#%[email protected]#%#$%
Option 556
Install dmverity patch using stock recovery.
Gives error can't find /misc partition - pretty sure these are TWRP zips only.
Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???
Verification bootloop FIX:?
I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.
DMM preload did not trigger on this!
As soon as it succeeded I installed TWRP in case DMM triggers.
Now with fixed data partition (presumably) retry TWRP
1. no verity patch (6.0)
2. magisk
cannot install DMM as it alters system partition...?
No cache wipe.
Lets see what happens...... Black screen but this time
'encryption failed' reset. Press reset.... TWRP does a factory reset
'encryption failed'
LOL now I have an encryption failed bootloop.
Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache
Now install TWRP (not booted once yet)
Install verity patch 6.0
install magisk 19.1
Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!
Android is starting... WELCOME
HOLY **** IT WORKED
DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
2/ flash stock AP - do NOT boot system yet
3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the first time
So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.
It actually boots now.... will update if further problems
Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...
Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.
Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.
Skype keeps stopping.
Reboot and YES only officially released binaries are allowed to be flashed boot loop.
So lets do this again!
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
8skip 2/ flash stock AP - do NOT boot system yet
8skip 3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the second time
Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@
Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$
After waiting 7 days
1/ Use stock recovery factory reset, then immediately hold down-home-power download mode
2/ Odin TWRP, then immediately hold up-home-power to enter TWRP
2a/ TWRP swipe to allow modifications (for RMM patch)
3/ TWRP install RMM patch
4/ TWRP install no verity patch
5/ TWRP install latest Magisk
NB Magisk seems to install itself as an app - its just there.
...Safetynet pass despite RMM editing /system phew
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Driss35 said:
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Click to expand...
Click to collapse
You don't have to choose any file type. Magisk scans files automatically.
Also, if your file type is ".lz4", you have to change it to ".img". Unless, you can't continue.
@Drnms thanks for this thread. But, some places have to be updated because of new Magisk versions.
Did App data remain after rooting
Drnms said:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
Click to expand...
Click to collapse
Hi Dmms,
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.
Hi, in case it is still relevant:
- Tab does a factory reset when booting first time after the boot img is flashed, data on the device is lost. Data on the SD card is not affected
- In my case, flashing boot.img with Odin didn't work. Odin said success, but no root. Heimdall worked fine, tab was rooted at first attempt
Does this guide also work for Android 9 ?
Edit: So it works with Android 9 also but I had to unpack the boot.img with 7zip ZS according to this post https://forum.xda-developers.com/t/samsung-a40-how-to-root.3929496/post-79902328
and re-pack it with normal 7zip according to these steps:
Do you have the boot.img.lz4 file to boot.img unpacked?
You have renamed the magisk_patched.img to boot.img?
You used the normal 7zip to package into a .tar file? Not the 7zZs?
You used the normal Odin 3.14?
Hello, did you manage to remove the "format as internal" lock?
Hi guys,
Trying to root this tablet, when I load the patched magisk file in Odin and perform the download. The tablet restarts and loads like normal but the tablet isn't rooted.
Any ideas?
alguma fortma?
How to Root Note 9 with Magisk on Android 10 (Q) without Custom Recovery (Eg.. TWRP)
This method will work with most of the latest Samsung devices running Android 9/10. (Tested and Working on Galaxy Note 9 (Exynos) with Android 10 Q).
WARNINGS: I am not responsible for any damage made. Your device warranty will be void. Do it at your own risk.
Warning: Before Installing Magisk
Installing Magisk WILL trip KNOX
Installing Magisk for the first time REQUIRES a full data wipe. Backup before continue.
You have to have your bootloader unlocked before following the instructions
REQUIREMENTS: (Basic knowledge about android rooting.)
Stock Firmware
Odin v3.14.1
Magisk Manager (You can find in Downloads section of Magisk Thread, I used Magisk Manager v7.5.1)
STEP 1 Unlocking Bootloader (This may need to Wipe your Data/Factory Reset.)
Enable Developer Mode on the Galaxy Note 9
To Enable Developer Mode Open Settings option.
Under Settings option, select About phone, then choose Software Information.
Scroll down the screen and tap Build number several times until you see a message that says "Developer mode has been enabled".
Tap on the Back button and you will see the Developer options menu under Settings, and select Developer options.
Toggle the OEM Unlock option on
Then tap on the Turn On button
STEP 2 Patching and Flashing (This may need to Wipe your Data/Factory Reset.)
Download the firmware for your device.
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Install the latest Magisk Manager
In Magisk Manager: Tap Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files. (I have copied with MTP)
Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files (I have used CSC instead of HOME_CSC). (Never flash only an AP file, as Odin can shrink your /data file-system if you do). Important: Uncheck “Auto Reboot” in Odin Options!
Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
STEP 3 Wipe data/factory reset (This may need to Wipe your Data/Factory Reset. : D)
We now want to boot into the stock recovery to factory reset our device. Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the Note 9 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen. (I had to release power button when Note 9 logo appeared).
Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system. (Just select Select Reboot system now)
The device will automatically reboot for the first time it boots. This is completely normal and done by design.
After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
You shall see Magisk Manager in your app drawer; if not, manually install the Magisk Manager APK and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
How to Root Note 9 with Magisk on Android 10 (Q) with Custom Recovery (Eg.. TWRP)
This method will work with most of the latest Samsung devices running Android 10. (Tested and Working on Galaxy Note 9 (Exynos) with Android 10 Q).
WARNINGS: I am not responsible for any damage made. Your device warranty will be void. Do it at your own risk.
Warning: Before Installing Rooting your device
Rooting your device WILL trip KNOX
Rooting your device for the first time may REQUIRES a full data wipe. Backup before continue.
You have to have your bootloader unlocked before following the instructions
REQUIREMENTS: (Basic knowledge about android rooting.)
Stock Firmware
Odin v3.14.1
TWRP For Android 10
Magisk Latest Stable ZIP or (I used Magisk Canary from Github)
DM-Verity, Force Encryption, and Disc Quota Disabler (I used Dm-Verity & ForceEncrypt Disabler v02.02.2020)
STEP 1 Unlocking Bootloader (This may need to Wipe your Data/Factory Reset.)
Enable Developer Mode on the Galaxy Note 9
To Enable Developer Mode Open Settings option.
Under Settings option, select About phone, then choose Software Information.
Scroll down the screen and tap Build number several times until you see a message that says "Developer mode has been enabled".
Tap on the Back button and you will see the Developer options menu under Settings, and select Developer options.
Toggle the OEM Unlock option on
Then tap on the Turn On button
STEP 2 Flashing Stock Firmware (This may need to Wipe your Data/Factory Reset.)
Reboot to download mode
To Boot into the Download Mode Power Off your device
Make sure you have a USB Type-C cable connected to your PC
Then press and hold the Volume Down and Bixby buttons at the same time
Hold these two buttons down and you insert the USB Type-C cable
Continue holding these two buttons down until you are greeted with the splash screen for Download Mode
Press the Volume Up button to bypass the splash screen and enter the Odin Mode
Now open Odin on your PC, Flash your firmware AP, BL, CP and CSC files. Important: Check “Auto Reboot” in Odin Options and keep your device in your hand and eye on Odin.
After you get flash got PASS! in Odin your device will restart and you will see blue screen saying you device is updating (or similar statement) for 2-5 seconds and then your device will restart again. (Next Step is Very Importent).
As soon as the screen turns off for second restart you have to press Power + Bixby + Volume Up to boot into the stock recovery. (I had to release power button when Note 9 logo appeared).
Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Power Off and remove your USB Type-C cable from your device.
STEP 3 Flashing TWRP(This may need to Wipe your Data/Factory Reset.)
Now your device is in power off state you have to boot into the Download Mode to flash TWRP. (You can get info on STEP 2 to boot into Download Mode)
Now open/reset Odin on your PC and go to the Odin option uncheck “Auto Reboot”
Click on the AP button to select TWRP file (Eg: twrp-3.3.1-r3.7-q-crownlte.tar) and click Start. (Next Step is Very Importent).
After you get flash got PASS! in Odin Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the Note 9 it is Power + Bixby + Volume Up). Since we want to boot into TWRP recovery, continue pressing the volume up button until you see the TWRP recovery screen. (I had to release power button when Note 9 logo appeared).
STEP 4 Rooting You Device (This may need to Wipe your Data/Factory Reset.)
In TWRP you have to swipe to allow the modification
Now format your data Tap Wipe->Format Data and type yes to continue. (You can Skip step 2 and 3)
No go back to TWRP home screen by pressing back button multiple times and tap Reboot and then click Recovery. (Your device will restart to TWRP recovery mode).
Insert your USB Type-C cable to connect your device to PC.
You will get your device MPT drive in my computer, Copy Magisk Canary zip file and Dm-Verity & ForceEncrypt Disabler v02.02.2020 zip file to your device.
Now you have to flash Magisk Canary in TWRP click Install and select Magisk Canary zip and start flashing. Then flash ForceEncrypt Disabler in TWRP. (If you get the mount error whioe installing ForceEncrypt Disabler then just ignore it and move to next step).
Click reboot to boot your system.
Done! Enjoy
Biometrics and fingerprint work after root?
Trimis de pe al meu SM-N960F folosind Tapatalk
Detonatte said:
Biometrics and fingerprint work after root?
Trimis de pe al meu SM-N960F folosind Tapatalk
Click to expand...
Click to collapse
Yes it works
Guessing this is non snapdragon use only. I don't see any models this works with but root isn't possible with North American note9 as far as I know. The boot loader is locked down.
I don't understand...where, how flash magisk_patched.tar ????
Please edit title to say this is Exynos only
thanks ..
secure folder still work after root?
Detonatte said:
I don't understand...where, how flash magisk_patched.tar ????
Click to expand...
Click to collapse
Follow STEP 2 Patching and Flashing (This may need to Wipe your Data/Factory Reset.)
Download the firmware for your device from sammobile or via Frija
Unzip the downloaded firmware on your PC and copy the AP tar file to your mobile device. (It is normally named as AP_[device_model_sw_ver].tar.md5).
Install the latest Magisk Manager on you mobile device.
In Magisk Manager: Tap Install → Install → Select and Patch a File and select the AP tar file that you have copied from your pc.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar.
Copy the patched magisk_patched.tar file to your PC with adb pull /sdcard/Download/magisk_patched.tar. (Do not use MTP as it is reported to corrupt files. (I have copied with MTP)).
Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files (I have used CSC instead of HOME_CSC). (Never flash only an AP file, as Odin can shrink your /data file-system if you do). Important: Uncheck “Auto Reboot” in Odin Options!
macgyver40 said:
Guessing this is non snapdragon use only. I don't see any models this works with but root isn't possible with North American note9 as far as I know. The boot loader is locked down.
Click to expand...
Click to collapse
Yes this is only for Exynos version, before posting this tutorials I don't have info about this.
TokedUp said:
Please edit title to say this is Exynos only
Click to expand...
Click to collapse
Done.
moaz1988 said:
thanks ..
secure folder still work after root?
Click to expand...
Click to collapse
Currently I am not using this System-as-root method to root my device because working version of Dm-Verity & ForceEncrypt Disabler is released so I am using TWRP method to root my device so I can't test secure folder on this rooting method. Now my device is rooted with Magisk via TWRP and secure folder is working without any issue so I think it will work with this method too.
Zer0De8th work perfect root with: twrp-3.3.1-r3.7-q-crownlte.tar, Magisk-v20.3(20300).zip and Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip
Thx very much man!!!
Detonatte said:
Zer0De8th work perfect root with: twrp-3.3.1-r3.7-q-crownlte.tar, Magisk-v20.3(20300).zip and Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip
Thx very much man!!!
Click to expand...
Click to collapse
Glad to know it works for you.
And SecureFolder work perfectly!
Trimis de pe al meu SM-N960F folosind Tapatalk
Hello
Thanks to the authors of this tutorial, and others on XDA, I completed a detailed procedure to Root the Galaxy Note 9 SM-N960F under Android 10 with the Recovery Custom TWRP which allows the backup and restoration of all partitions.
This procedure may seem long because it is very detailed because there are very important points not to miss so that the partitions are not locked by Android 10.
I hope the French / English translation is good because I am very bad in English
cordially
https://forum.xda-developers.com/showpost.php?p=81695605&postcount=324
Montero try backup and restore with TWRP? Work??
Trimis de pe al meu SM-N960F folosind Tapatalk
Yes work very fine for All partitions
Detonatte said:
Zer0De8th work perfect root with: twrp-3.3.1-r3.7-q-crownlte.tar, Magisk-v20.3(20300).zip and Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip
Thx very much man!!!
Click to expand...
Click to collapse
Me too....
Restoring my data using Titanium Backup..
Samsung acc working
How to enable hidden menu since no more CSC folder (feature.xml)?
inamie said:
Me too....
Restoring my data using Titanium Backup..
Samsung acc working
How to enable hidden menu since no more CSC folder (feature.xml)?
Click to expand...
Click to collapse
Here is the new location for CSC feature.xml "/odm/etc/omc/XXX- your country code/conf/cscfeature.xml".
You have to Decode / Encode CSC files use OmcTextDecoder .
Many of the old CSC features don't work on Samsung Android Q
Zer0De8th said:
Here is the new location for CSC feature.xml "/odm/etc/omc/XXX- your country code/conf/cscfeature.xml".
You have to Decode / Encode CSC files use OmcTextDecoder .
Many of the old CSC features don't work on Samsung Android Q
Click to expand...
Click to collapse
Thanks,
Any idea how to set Magisk Manager.
New version 7.5.2 no option to hide selected application..
cant use certain apps like shopee pay and ewallet on rooted device.
Previous version 7.5.1 no problem.
SIZE="6"]Use this guide if your tablet is running on android 9. Android 10 is not covered in this guide[/SIZE]
Instructions:
Code:
* READ EVERTHING BEFORE YOU START OR ASK QUESTIONS
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard & a lot. :D
I’m not an expert, I’ve just put some pieces together to achieve the following.
If you have problems, I’m not sure if I’m able to help you
You need to have some basic knowledge
Always have the correct software and backup all your data.
o Also download before you start the stock files, so that you are able to quickly reverse everything via: sammobile
Remember to backup your data!!!!
If you have trouble and the tablet is not working flash the firmware which you’ve downloaded via odin
Working ROMS (Which I’ve tested so far):
IF you want to install a custom ROM, you need to choose the correct custom ROM
Choose the ARM 32-bit with 64-bit binder AB (also known as A64B).
LineageOS 17.x GSI here
Legion ROM GSI here
From OEM stock firmware:
Download TWRP https://forum.xda-developers.com/ga...rp-3-3-1-2019-galaxy-tab-10-1-t3934805/page35
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
Check if OEM unlock is enabled in the developer settings (it should be enabled and greyed out) IF so yeey you did It. If not start over.
Install custom ROM:
Well installing a custom Rom is quite easy .
Download a GSI ROM you like and put it on a SD cart
Go into TWRP
Select “install”
Click on “install image”
Click the on the ROM
In the next screen where we need to select the partition, select the “System Image”
Swipe to confirm
If you want ROOT and or install GAPPS follow the extra steps bellow. If NOT, just reboot the system
Extra’s install MAGISK and or install GAPPS
First of all download the files you want.
Magisk: here
GAPPS: here
You want root? You need to prepare the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. Which we can prepare and flash after you finished the setup of the tablet. You need more info check the following: link
Go back to the TWRP home screen
Select “Wipe”
Select advanced wipe
Check “system”
Click on “repair or change file system”
Click on “resize file system” (if you’ve receive an error, don’t worry just do It again).
o You should see “resizing… done.”
Go back to the TWRP home screen
Select “install”
Select the zip file(‘s) you want and flash them
o IF you receive an error if you want to install the GAPPS zip like “not enough space” go back and resize the system partition
o IF you receive an errro if you want to install Magisk, go back and resize the system partition
Remove “dalvik and cache”
Reboot system
Setup your tablet
Now for the last step to root the tablet all the way
Go into Magisk manager
On the Magisk dashboard you’ve should see that you have the latest version of magisk. Press on the “install” button at the right side
o Select “Select and Patch a File” select the TWRP IMG you still have on the SD card
o Magisk should create a “magisk_patched.img”.
If you have the “magisk_patched.img” go into TWRP and flash this IMG over the recovery
o Install
o Select “install image”
o Select the “magisk_patched.img”
o Flash it over the “recovery”
o Reboot system
Yeey you have a Samsung sm-t515 which is rooted and you have a custom ROM.
one last question
massivekind said:
Instructions:
Code:
* READ EVERTHING BEFORE YOU START OR ASK QUESTIONS
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard & a lot. :D
I’m not an expert, I’ve just put some pieces together to achieve the following.
If you have problems, I’m not sure if I’m able to help you
You need to have some basic knowledge
Always have the correct software and backup all your data.
o Also download before you start the stock files, so that you are able to quickly reverse everything via: sammobile
Remember to backup your data!!!!
If you have trouble and the tablet is not working flash the firmware which you’ve downloaded via odin
Working ROMS (Which I’ve tested so far):
IF you want to install a custom ROM, you need to choose the correct custom ROM
Choose the ARM 32-bit with 64-bit binder AB (also known as A64B).
LineageOS 17.x GSI here
Legion ROM GSI here
From OEM stock firmware:
Download TWRP https://forum.xda-developers.com/ga...rp-3-3-1-2019-galaxy-tab-10-1-t3934805/page35
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
Check if OEM unlock is enabled in the developer settings (it should be enabled and greyed out) IF so yeey you did It. If not start over.
Install custom ROM:
Well installing a custom Rom is quite easy .
Download a GSI ROM you like and put it on a SD cart
Go into TWRP
Select “install”
Click on “install image”
Click the on the ROM
In the next screen where we need to select the partition, select the “System Image”
Swipe to confirm
If you want ROOT and or install GAPPS follow the extra steps bellow. If NOT, just reboot the system
Extra’s install MAGISK and or install GAPPS
First of all download the files you want.
Magisk: here
GAPPS: here
You want root? You need to prepare the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. Which we can prepare and flash after you finished the setup of the tablet. You need more info check the following: link
Go back to the TWRP home screen
Select “Wipe”
Select advanced wipe
Check “system”
Click on “repair or change file system”
Click on “resize file system” (if you’ve receive an error, don’t worry just do It again).
o You should see “resizing… done.”
Go back to the TWRP home screen
Select “install”
Select the zip file(‘s) you want and flash them
o IF you receive an error if you want to install the GAPPS zip like “not enough space” go back and resize the system partition
o IF you receive an errro if you want to install Magisk, go back and resize the system partition
Remove “dalvik and cache”
Reboot system
Setup your tablet
Now for the last step to root the tablet all the way
Go into Magisk manager
On the Magisk dashboard you’ve should see that you have the latest version of magisk. Press on the “install” button at the right side
o Select “Select and Patch a File” select the TWRP IMG you still have on the SD card
o Magisk should create a “magisk_patched.img”.
If you have the “magisk_patched.img” go into TWRP and flash this IMG over the recovery
o Install
o Select “install image”
o Select the “magisk_patched.img”
o Flash it over the “recovery”
o Reboot system
Yeey you have a Samsung sm-t515 which is rooted and you have a custom ROM.
Click to expand...
Click to collapse
you have been very kind. I'd like to ask you one last question. for the t515 (since the lineage os is generic) do you also use a particular kernel (which optimizes performance maybe) ?. thanks
gcomunale71 said:
Instructions:
you have been very kind. I'd like to ask you one last question. for the t515 (since the lineage os is generic) do you also use a particular kernel (which optimizes performance maybe) ?. thanks
Click to expand...
Click to collapse
No I don't have any, but if there is one for the 510 give it a try.
Of course backup before flashing
Hi,
Thanks for the guide. Which ROM you recommend? Everything working for you (LTE modem etc)?
Can you now install 64bit apps from Google Play? Any chance you can check if the DJI Fly app is working on your SM-T515?
https://play.google.com/store/apps/details?id=dji.go.v5
Thanks
liamR said:
Hi,
Thanks for the guide. Which ROM you recommend? Everything working for you (LTE modem etc)?
Can you now install 64bit apps from Google Play? Any chance you can check if the DJI Fly app is working on your SM-T515?
https://play.google.com/store/apps/details?id=dji.go.v5
Thanks
Click to expand...
Click to collapse
Well, It's still a 32bit rom. I've tried to install the app but I'm unable (prob because the app is 64bit)
Everything works fine, I'm running the lineageOS ROM. I have a data bundle and I'm able to internet with it (if I want )
massivekind said:
Well, It's still a 32bit rom. I've tried to install the app but I'm unable (prob because the app is 64bit)
Everything works fine, I'm running the lineageOS ROM. I have a data bundle and I'm able to internet with it (if I want )
Click to expand...
Click to collapse
I thought that this custom ROM is 64bit
When I bought the TAB A I thought it's a bargain, I didn't know that I wouldn't be able to install 64bit apps.
massivekind said:
Instructions:
Code:
* READ EVERTHING BEFORE YOU START OR ASK QUESTIONS
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard & a lot. :D
I’m not an expert, I’ve just put some pieces together to achieve the following.
If you have problems, I’m not sure if I’m able to help you
You need to have some basic knowledge
Always have the correct software and backup all your data.
o Also download before you start the stock files, so that you are able to quickly reverse everything via: sammobile
Remember to backup your data!!!!
If you have trouble and the tablet is not working flash the firmware which you’ve downloaded via odin
Working ROMS (Which I’ve tested so far):
IF you want to install a custom ROM, you need to choose the correct custom ROM
Choose the ARM 32-bit with 64-bit binder AB (also known as A64B).
LineageOS 17.x GSI here
Legion ROM GSI here
From OEM stock firmware:
Download TWRP https://forum.xda-developers.com/ga...rp-3-3-1-2019-galaxy-tab-10-1-t3934805/page35
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
Check if OEM unlock is enabled in the developer settings (it should be enabled and greyed out) IF so yeey you did It. If not start over.
Install custom ROM:
Well installing a custom Rom is quite easy .
Download a GSI ROM you like and put it on a SD cart
Go into TWRP
Select “install”
Click on “install image”
Click the on the ROM
In the next screen where we need to select the partition, select the “System Image”
Swipe to confirm
If you want ROOT and or install GAPPS follow the extra steps bellow. If NOT, just reboot the system
Extra’s install MAGISK and or install GAPPS
First of all download the files you want.
Magisk: here
GAPPS: here
You want root? You need to prepare the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. Which we can prepare and flash after you finished the setup of the tablet. You need more info check the following: link
Go back to the TWRP home screen
Select “Wipe”
Select advanced wipe
Check “system”
Click on “repair or change file system”
Click on “resize file system” (if you’ve receive an error, don’t worry just do It again).
o You should see “resizing… done.”
Go back to the TWRP home screen
Select “install”
Select the zip file(‘s) you want and flash them
o IF you receive an error if you want to install the GAPPS zip like “not enough space” go back and resize the system partition
o IF you receive an errro if you want to install Magisk, go back and resize the system partition
Remove “dalvik and cache”
Reboot system
Setup your tablet
Now for the last step to root the tablet all the way
Go into Magisk manager
On the Magisk dashboard you’ve should see that you have the latest version of magisk. Press on the “install” button at the right side
o Select “Select and Patch a File” select the TWRP IMG you still have on the SD card
o Magisk should create a “magisk_patched.img”.
If you have the “magisk_patched.img” go into TWRP and flash this IMG over the recovery
o Install
o Select “install image”
o Select the “magisk_patched.img”
o Flash it over the “recovery”
o Reboot system
Yeey you have a Samsung sm-t515 which is rooted and you have a custom ROM.
Click to expand...
Click to collapse
first of all thanks for the great work.
Sorry if this is a stupid question , but before i brick my new SM-T515 I would rather ask the experts.
Now, i have rooted the stock ROM folowing the steps in https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root with no TWRP and want to install one of the custom ROMs you have tested.
will I lose root if flash the Legion ROM GSI?
if yes, can you please put some steps together to root and install TWRP?
i still have the “magisk_patched.tar" from the stock ROM, would that work for the Legion ROM GSI?
dj-rjay said:
Instructions:
first of all thanks for the great work.
Sorry if this is a stupid question , but before i brick my new SM-T515 I would rather ask the experts.
Now, i have rooted the stock ROM folowing the steps in https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root with no TWRP and want to install one of the custom ROMs you have tested.
will I lose root if flash the Legion ROM GSI?
if yes, can you please put some steps together to root and install TWRP?
i still have the “magisk_patched.tar" from the stock ROM, would that work for the Legion ROM GSI?
Click to expand...
Click to collapse
In theory it should work. I've already covered "root" also in the guide
I've followed the steps and have Lineage installed on my T515, but when I plug it into my computer it can't see the Tablet in Windows Explorer. I've set it to MTP mode and enabled USB debugging. Strange thing is when I use ADB DEVICES I can see it. Also when I plug it in, the tablet makes a sound and it says 'Usb Debugging...' on screen. It just won't show up in Windows.
Also when I try and use File Explorer on the tablet, it can't see the SD Card. I've tried formatting it for 'Portable' but it when I go back in it says it corrupted. When I format it for Phone Storage, it shows the extra space for the phone storage but I also can't see it in the File Explorer.
Anyone else come across this?
Sambuca11 said:
I've followed the steps and have Lineage installed on my T515, but when I plug it into my computer it can't see the Tablet in Windows Explorer. I've set it to MTP mode and enabled USB debugging. Strange thing is when I use ADB DEVICES I can see it. Also when I plug it in, the tablet makes a sound and it says 'Usb Debugging...' on screen. It just won't show up in Windows.
Also when I try and use File Explorer on the tablet, it can't see the SD Card. I've tried formatting it for 'Portable' but it when I go back in it says it corrupted. When I format it for Phone Storage, it shows the extra space for the phone storage but I also can't see it in the File Explorer.
Anyone else come across this?
Click to expand...
Click to collapse
Mm strange, i don't use both functions so I can't really help you.
Maybe you could format the sd card via twrp?
On my side the sd card works. Didn't format the sd card so don't really know
Sambuca11 said:
I've followed the steps and have Lineage installed on my T515, but when I plug it into my computer it can't see the Tablet in Windows Explorer. I've set it to MTP mode and enabled USB debugging. Strange thing is when I use ADB DEVICES I can see it. Also when I plug it in, the tablet makes a sound and it says 'Usb Debugging...' on screen. It just won't show up in Windows.
Also when I try and use File Explorer on the tablet, it can't see the SD Card. I've tried formatting it for 'Portable' but it when I go back in it says it corrupted. When I format it for Phone Storage, it shows the extra space for the phone storage but I also can't see it in the File Explorer.
Anyone else come across this?
Click to expand...
Click to collapse
I have the same issue. Any solution?
zamboj said:
I have the same issue. Any solution?
Click to expand...
Click to collapse
I haven't found one yet, I'm going to try go back to Stock as I need my computer to be able to see the tablet to transfer files over. I've tried installing the Legion custom rom and it does the same thing. I'm not sure but I'd love to get an answer to this and I'd love to use a custom rom.
Are there any other Android 10 roms that I could try?
Sambuca11 said:
I haven't found one yet, I'm going to try go back to Stock as I need my computer to be able to see the tablet to transfer files over. I've tried installing the Legion custom rom and it does the same thing. I'm not sure but I'd love to get an answer to this and I'd love to use a custom rom.
Are there any other Android 10 roms that I could try?
Click to expand...
Click to collapse
I have a work app that need a little more ram: the solution is LineageOs (used 1,2gb vs 1,5gb of the stock rom) and I transfer files through recovery. I tried LegionOS but is full of bugs and file transfer doesn't work the same.
I'm back to stock and my computer and can see my table and the SD card is working fine. Its a shame as I'd love to use LineageOS but for now I'm stuck on stock.
I don’t know what I’m doing wrong so need some help please. I’ve installed TWRP and multidisabler. I’ve wiped the system cache data etc like I was flashing a custom rom.
I’ve downloaded the rom from the links flashed it via system image but I still get the message no os installed rebooted and just a bootloop saying unlocked boot loader press power button to start then nothing no booting image from linageos. Just repeats.
Can anybody tell me or guide me on what I could have done wrong and what what I should being
daljitbanga said:
I don’t know what I’m doing wrong so need some help please. I’ve installed TWRP and multidisabler. I’ve wiped the system cache data etc like I was flashing a custom rom.
I’ve downloaded the rom from the links flashed it via system image but I still get the message no os installed rebooted and just a bootloop saying unlocked boot loader press power button to start then nothing no booting image from linageos. Just repeats.
Can anybody tell me or guide me on what I could have done wrong and what what I should being
Click to expand...
Click to collapse
Mm strange I didn't experience this problem. Like I stated go back to stock and start over. This time don't wipe the system partition.
Thanks for the reply I will try that when I get home later in the day and will post the outcome after.
Are there any other roms the we could also try.
massivekind said:
Mm strange I didn't experience this problem. Like I stated go back to stock and start over. This time don't wipe the system partition.
Click to expand...
Click to collapse
I followed what you said but I’m stilling getting the bootloop for some reason could share links of what rom you downloaded and etc.
Because there must be a mistake in making.
Also to what I’ve been reading is that I need something of treble enabler for the device but I really don’t know.
massivekind said:
Mm strange I didn't experience this problem. Like I stated go back to stock and start over. This time don't wipe the system partition.
Click to expand...
Click to collapse
I finally managed to get LineageOS installed. I just deleted all the files and redone loaded them, returned back to stock and did the whole process all over again.
And it worked. ? ? so maybe somewhere down the line put have been a corrupt download or something.
Custom rom has whole different feeling on the tablet now. Thanks again for tutorial, I’ve been waiting for something like this for a while.
You don’t know of any other roms there out there to try?
daljitbanga said:
I finally managed to get LineageOS installed. I just deleted all the files and redone loaded them, returned back to stock and did the whole process all over again.
And it worked. ? ? so maybe somewhere down the line put have been a corrupt download or something.
Custom rom has whole different feeling on the tablet now. Thanks again for tutorial, I’ve been waiting for something like this for a while.
You don’t know of any other roms there out there to try?
Click to expand...
Click to collapse
You've could try havoc os https://sourceforge.net/projects/ha...v3.5-20200522-Official-a64-ab.img.xz/download
Topic over here, I'm not sure if there are things not working, thats something you'd could figure out
https://forum.xda-developers.com/galaxy-tab-a/how-to/rom-havocos-v3-5-treble-guide-t4108127
I didn't tried this one, but is could be an option
Hi, here's a guide on how install crDroid 7.5 (A11) on Redmi 8
UPDATE: THERE'S 7.5 VERSION AVAIABLE, IF YOU ARE USING 7.4 FOLLOW THIS STEPS TO UPDATE WITHOUT LOSING DATA (NEW ROM IS IN MEGA FOLDER, ):
1- Reboot in recovery
2- Go to Wipe -> Avanced wipe -> wipe dalvik, cache and system
3- Go to Reboot -> Recovery
4- Now follow the normal guide from the flashing of the .img file as system image
VERY IMPORTANT: DON'T FORMAT DATA AFTER FLASHING GSI FIXER OR YOU WILL LOST ALL YOUR DATA
Features:
- All functions of the phone work (face unlock, fingerprint, voLTE, voWIFI, hotspot, bluetooth, fast charge, DT2W, ...)
- Magisk safetynet passed without flash nothing (screenshot at the bottom)
- Permissive Selinux by default (in settings is writing disabled, it's wrong) but you can switch to enforcing with
SelinuxModeChanger app, apk at the bottom
What doesn't work
- Nothing if you use fixes below
Note 1: You may have problems with the brightness or sim calls/sms, there are solutions:
- For brightness: Open settings -> Go in "Phh Treble Settings" -> "Misc Features" -> Scroll until you are in backlight menu -> Select "Force alternative backlight scale" and "Enable auto-brightness overlay" -> then deselect both and reboot
- For sim calls: Open settings -> Go in "Network and internet" -> "Mobile network" -> Tap on "Preferred network type" and select "GSM/WCDMA/LTE" or "Global" (try which is better for you) and then reboot
Note 2: If you fing bugs tell me in comments, maybe I could help you (I'm not the developer of the rom)
IMPORTANT ADVICE:I am not responsible for any damage caused to your device by not following the steps, all the steps were tested on my personal device and are confirmed, my device is Redmi 8 4/64
Installation Steps - All the files you need are HERE
Note 3: I did the installation coming from Mui 12.0.1 stock (flashed in fastboot with Mi Flash) and there was no problem in the installation process or in the boot process, YOU NEED THIS ROM IF YOU WON'T PROBLEMS
1- First make a backup of all the necessary information in case something goes wrong you can easily recover, Charge the battery at least 80%
All your data will be deleted during the process
2- Unlock the Bootloader if you have not already done it or do not know how to, follow this post: http://en.miui.com/unlock/
3- Before continue following steps estract on pc "crdrom-v302-210315-arm64-bvZ.img" from "crdrom-v302-210315-arm64-bvZ.img.xz" and activate USB debug in phone settings
4- Reboot in fastboot and connect the phone to the pc with cable
5- Install on pc minimal adb tool (zip at the bottom), flash the TWRP recovery typing " fastboot flash recovery ", now drag twrp file near the command, then vbmeta typing " fastboot --disable-verity --disable-verification flash vbmeta " and drag vbmeta file near the command. Finished the procedure type " fastboot reboot " and hold volume + on the phone until you see the recovery screen
6- Scroll on the slider at the bottom of the phone screen to access in the TWRP
7- Go to Wipe -> Format data -> type "yes"
8- Go to Reboot -> Recovery
9- Go to Wipe -> Avanced wipe -> wipe dalvik, data, cache and system
10- Go to Reboot -> Recovery
NOW YOU HAVE TO TRANSFER ALL OTHER FILES OR IN THE INTERNAL STORAGE OF THE PHONE OR IN SD/USB WITH OTG CABLE
11- Go to Install -> Select the storage where you have files -> Install img -> select "crdrom-v306-210425-arm64-bvZ.img" (Extracted from the .xz file) -> select "system image" and flash
12- Wait and then go to Reboot -> Recovery
13- Wipe -> Advanced wipe -> select "system" and click on "Repair or change file system" -> Resize system
14- Wait and then go to Reboot -> Recovery
15- Install -> Select the storage where you have files -> Flash "GSI-BUGS-FIXER_11_Q.zip"
16- Wipe -> Format data -> type "yes"
17- Wait and then go to Reboot -> Recovery
18- Install -> Select the storage where you have files -> Flash "BiTGApps-arm64-11.0.0-R19_signed.zip"
19- Wait and then go to Reboot -> System
20- Configure phone and enjoy your new rom
Note 4: I reccomend you to flash magisk after you have configured the rom to avoid problems, I leave you the zip to flash in recovery below
Note 5: I reccomend you the best gcam I've found for Redmi 8, everything works except slow motion, link HERE
Thanks for the attenction
-Estatè
Happy that many GSI roms are under develment. I hope this phone will die due to hardware, as there are lots of options in future to keep the software updated.
Anyway, if someone intends to try, following is the link of all GSI Roms.
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Can i flash vbmeta through recovery
Naulels said:
Can i flash vbmeta through recovery
Click to expand...
Click to collapse
Hey
I'm not using crDroid yet, but I've already installed TWRP.
It is advertised that you should flash vbmeta when you're installing TWRP.
I hope I can help you
Hey !
I wanna try this but I have rooted my phone so here is my question : do I need to remove the root to install this GSI ?
Thx a lot
Volume doesn't work correctly, I cannot increase or decrease the volume. And I plugged my headphone not play through headphone, it play through speaker. Sorry my English
Naulels said:
Can i flash vbmeta through recovery
Click to expand...
Click to collapse
No, you have to flash it with ADB like twrp
letouvetpierre said:
Hey !
I wanna try this but I have rooted my phone so here is my question : do I need to remove the root to install this GSI ?
Thx a lot
Click to expand...
Click to collapse
I recommend you to remove it from the magisk app to avoid problems but I think that would be the same
Naulels said:
Volume doesn't work correctly, I cannot increase or decrease the volume. And I plugged my headphone not play through headphone, it play through speaker. Sorry my English
Click to expand...
Click to collapse
I haven't this problem, have you flashed the gsi fixer? Did you start the installation from miui 12.0.1? It's really important, anyway, you can try to do again the procedure
Does VoLTE and VoWIFI works ? It's a GSI so I'm not thinking it works...
letouvetpierre said:
Does VoLTE and VoWIFI works ? It's a GSI so I'm not thinking it works...
Click to expand...
Click to collapse
Yes, all work fine becouse you flash the gsi fixer for gsi roms on redmi 8
Estatè Mosconi said:
I haven't this problem, have you flashed the gsi fixer? Did you start the installation from miui 12.0.1? It's really important, anyway, you can try to do again the procedure
Click to expand...
Click to collapse
I have reinstalled and fixed it, thanks
Hey !
I'm so happy !
Everything works on that GSI rom, but I haven't the certification on SafetyNet.
With the covid-tracing app, there is a little problem but it's with all the custom roms so...
Thanks a lot for your guide !
letouvetpierre said:
Hey !
I'm so happy !
Everything works on that GSI rom, but I haven't the certification on SafetyNet.
With the covid-tracing app, there is a little problem but it's with all the custom roms so...
Thanks a lot for your guide !
Click to expand...
Click to collapse
Hi, I'm happy for you, for safetynet try the magisk module, I didn't have this problem, anyway, try the rom and than leave a feedback, it could be useful for other people who want to try this rom
I can't get this rom to work correctly. Did the steps as described, but it has SELinux not enforced and Google play isn't certified. Tried multiple times.
EDIT: seems my phone is soft bricked now (Can't install any rom). Going back to xaomi stock to try again.
I tried again and got it to work. The certificate patch throws an error but Google apps are working.
I get an SE Linux not enforcing error. though.
Is there anything I can do about that?
I lost the treble-overlay-xiaomi-redmi8.apk file ,I should problems with the brightness
ndduc said:
I lost the treble-overlay-xiaomi-redmi8.apk file ,I should problems with the brightness
Click to expand...
Click to collapse
There is the solution for brightness in the guide, you don't need that file
Estatè Mosconi said:
There is the solution for brightness in the guide, you don't need that file
Click to expand...
Click to collapse
thanks you, i fixed
ndduc said:
thanks you, i fixed
Click to expand...
Click to collapse
Ok good
Hi, here's my guide on how install Ancient OS 5.2 (A11) on Redmi 8
What doesn't work
- Bluetooth
- 4g network and VoLTE (Fix below)
- Brightness slider and auto-brightness (Fix below)
Fixes:
- For brightness: Open settings -> Go in "Phh Treble Settings" -> "Misc Features" -> Scroll until you are in backlight menu -> Select "Force alternative backlight scale" and "Enable auto-brightness overlay" -> then deselect both and reboot
- For 4g and VoLTE: Open settings -> Go in "Network and internet" -> "Mobile network" -> Tap on "Preferred network type" and select "LTE" and then reboot
Note 1: If you find a fix for bluetooth describe it in comments, I will update the guide
Note 2: If you fing other bugs tell me in comments, maybe I could help you (I'm not the developer of the rom)
IMPORTANT ADVICE:I am not responsible for any damage caused to your device by not following the steps or negligence at the time of this process, all the steps were carried out and tested on my personal device and are confirmed, my device is Redmi 8 4/64
Installation Steps - All the files you need are HERE
Note 3: I did the installation coming from Mui 12.0.1 stock (flashed in fastboot with Mi Flash) and there was no problem in the installation process or in the boot process
1- First make a backup of all the necessary information in case something goes wrong you can easily recover, Charge the battery at least 80%
All your data will be deleted during the process
2- Unlock the Bootloader if you have not already done it or do not know how to, follow this post: http://en.miui.com/unlock/
3- Before continue following steps estract on pc "system-arm64-AB-vndklite.img" from "AncientOS-R-Society-v5.2-ARM64_AB_vndklite-Iron-20210227-vanilla.zip" and activate USB debug in phone settings
4- Reboot in fastboot and connect the phone to the pc with cable
5- Install on pc minimal adb tool (zip at the bottom), flash the TWRP recovery typing " fastboot flash recovery ", now drag twrp file near the command, then vbmeta typing " fastboot --disable-verity --disable-verification flash vbmeta " and drag vbmeta file near the command. Finished the procedure type " fastboot reboot " and hold volume + on the phone until you see the recovery screen
6- Scroll on the slider at the bottom of the phone screen to access in the TWRP
7- Go to Wipe -> Format data -> type "yes"
8- Go to Reboot -> Recovery
9- Go to Wipe -> Avanced wipe -> wipe dalvik, data, cache and system
10- Go to Reboot -> Recovery
NOW YOU HAVE TO TRANSFER ALL OTHER FILES OR IN THE INTERNAL STORAGE OF THE PHONE OR IN SD/USB WITH OTG CABLE
11- Go to Install -> Select the storage where you have files -> Install img -> select "system-arm64-AB-vndklite.img" and flash it (Extracted from the zip)
12- Wait and then go to Reboot -> Recovery
13- Wait and then go to Reboot -> Recovery
14- Wipe -> Advanced wipe -> select "system" and click on "Repair or change file system" -> Resize system
15- Wait and then go to Reboot -> Recovery
16- Install -> Select the storage where you have files -> Flash "GSI-BUGS-FIXER_11_Q.zip"
17- Wait and then go to Reboot -> Recovery
18- Install -> Select the storage where you have files -> Flash "open_gapps-arm64-11.0-nano-20210130-TEST.zip"
19- Wait and then go to Reboot -> System
20-Configure phone and enjoy your new rom
Note 4: Rom is pre-rooted, you only need to install magisk apk, file below
Note 5: I reccomend you the best gcam I've found for Redmi 8, everything works except slow motion, link HERE
Thanks for the attenction
-Estatè
zas far as i know bluetooth works on vendor from lineageOS 16 from this forum, there are the same bugs on every rom with original vendor.
Why U use my fixes and manuals without request to me? Your manuals wrong and makes bootloop. Before stupid copy-paste read instructions.
All roms booted without any permissiver. Certification patch retarded and not supported Android 11.
GSI FIXER is rom and vendor-specified.
Number in name = Android in rom
Letter in name = Android in vendor
kulaklığımı algılamıyor
edit: Fixed
Vicuel said:
does not detect my headphone
Click to expand...
Click to collapse
Open termux and type....
su
Then give termux root access....
Then type.....
setprop persist.sys.overlay.devinputjack true
mwaseem851 said:
Open termux and type....
su
Then give termux root access....
Then type.....
setprop persist.sys.overlay.devinputjack true
Click to expand...
Click to collapse
This needs to be done after every reboot?
gattud said:
This needs to be done after every reboot?
Click to expand...
Click to collapse
Nono, only paste it in termux with root access and reboot, then you will solve the problem forever
mwaseem851 said:
Termux'u açın ve .... yazın.
su
Sonra termux root erişimi verin ....
Sonra yazın .....
setprop persist.sys.overlay.devinputjack doğru
Click to expand...
Click to collapse
thanks
Don't use any my GSI-BUGS-FIXERS from XDA. This fixes retarded and no more supported!
Don't say to me in Telegram chat about bugs if you use fixes and instructions from any users of XDA except me.
I used the gsi bugs fixer in Telegram
@Estatè Mosconi If you haven't already I suggest you take a look in your PM inbox.