[GUIDE] Fully Restore Stock and Unroot L90 - LG Optimus L90

Hello, everyone.
Even after flashing stock ROM with kdz your L90 may still display ROOTED in download mode or in the RCT test (open Telephone app and type 3845#*XXX# where XXX is your phone model, 410 for instance if you have a D410hn). The fix is relatively simple:
1. While still rooted, use a file manager with root access and navigate to /persist folder, then backup to a safe place (just in case you need them later) and delete these two files:
rct
rct.cfg
2. Reboot to recovery and do a full wipe: caches, data and system. It's important because maybe some files that trigger the rooted flag may be in /data/local/tmp, for instance;
3. Reboot to Download Mode (bootloader) and follow this tutorial to flash stock kdz:
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Before flashing kdz you shouldn't already see any ROOTED on screen, and after booting to stock the RCT tool should not display that your device is rooted anymore.
PS: I am not sure if deleting these two files will break anything, I have just did these steps and my device doesn't show ROOTED anymore. Ideally, you should backup /persist before rooting (I don't think it's possible anyway, at least not on Lollipop), or at least backup them just after rooting, so you can replace the files as explained is the treads bellow.
Credits
@Drachenminister - http://forum.xda-developers.com/showthread.php?t=2700992
@AriHell - http://forum.xda-developers.com/lg-g3/general/tot-reset-rct-root-check-tool-t2853627
@k0nane - http://forum.xda-developers.com/showthread.php?p=41136026#post41136026

Related

my method for updating successfully to zv8 with root from GV2.0 (zv7)

hello well first off i just finished troubleshooting the **** out of my phone and i see lots of others are having issues as well and its all scattered. so i am going to post my method which should get you updated with MT's AIO which also includes a fix for those who are having permission problems with the AIO.
(this is optional and for those who were having problems with permission errors using AIO on GV 2.0) (skip below for first step of getting to zv7)
first off the main thing that I figured out is that if you are on GV2.0 the kernel by default (at least for me) disables logcat which gives many problems with MT's AIO solution with the error cannot open dev/log/main with all the permission problems with rooting / unrooting on GV2.0. So for those who are having that issue here is the fix:
open root explorer
go into /system/etc/init.d/12gvtw
long click then open up text editor
go to where it says rm /dev/log/main and change it to
#rm /dev/log/main
then save and then reboot which should fix the permissions errors.
now doing that enabled me to be able to have success with the AIO to prepare for the update to zv8 while on GV 2.0 ...
but then I ran into another problem after that was that the OTA update would fail. most likely because the boot.img was not stock (this is just a guess, probably other reasons as well)
----------------------
but what worked for me was going completely stock gingerbread.
so for this fix I simply went to this thread to get completely to stock zv7
http://forum.xda-developers.com/showthread.php?t=1348637
I then downloaded the nandroid and followed MT's instructions steps 1-6
1.) Download the .zip & make sure 4g is enabled.
2.) Place zip in external sdcard
3.) I recommend to wipe data to prevent any problems
I want to emphasize that you SHOULD WIPE DATA NOW AT THIS STEP IN CWM BEFORE IT GETS TO STOCK RECOVERY.
4.) Go to install zip from sdcard
5.) Select RevoZV7GBStock.zip
6.) Reboot
then after that my phone booted up completely stock (with stock boot.img) and wiped data with root still enabled.
then I went to this thread to get MT's AIO zv8 and followed the steps 1-5 (steps 6 and 7 will be completed later)
http://forum.xda-developers.com/showthread.php?t=1566729
1) Download zip and extract
2) Install drivers if not already installed
3) Make sure you are on stock ZV7
4) Click Root&RecoveryAIO.bat
5) Select "Prepare for Update"
then the phone rebooted and was at stock recovery and unrooted and was completely stock but with the added the data/local.prop edits.
so then I went to this thread to download Broken Out Rom from my computer and followed steps 1-2 (steps 3-9 will be completed later) before i completed the AIO process steps 6-7 stated earlier.
http://forum.xda-developers.com/showthread.php?t=1577423
1.) Download the .zip & make sure 4g is enabled.
2.) Place zip in external sdcard
So now you should have your phone completely unrooted with stock recovery with Broken Out Rom downloaded on your phone's sd card (not installed yet).
You are now ready to go to get the OTA update. (step 6)
go to settings > about phone > software update > check new
then you should have the OTA update successfully installed when it reboots.
you now have zv8 installed with no root or cwm.
then i went to MT's AIO for zv8 and clicked option 7 which is too root zv8.
then the phone gave me an error on AIO when trying to root but then CWM still got installed at the end of the AIO process.
so the phone then booted up with no root but CWM was installed but could not get into recovery mode using quickboot to recovery option on the phone due to no root access..
for this fix I then opened up MT's AIO for zv7 found here under step 2 of "How do I completely Return to Stock"
http://forum.xda-developers.com/showthread.php?t=1348637
and then clicked option 7 which is reboot recovery. this booted my phone into recovery.
then I went to continue the process of installing Broken Out Rom (steps 3 and 4 are skipped because we already wiped data initially above)
5.) Go to install zip from sdcard
6.) Select BrokenOutRevo1.1.zip
7.) Do not wipe data after flashing!!!
8.) Reboot!
9.) To Block CIQ Logs Requires Reboot After Initial Boot
You should now have a fully rooted zv8 phone with CWM and can give yourself a pat on the back.
if i forgot to mention things please let me know. this was just my process which worked after much troubleshooting so i thought i'd share it with you all.
My method
Just for people who might be looking for other ways or are a few steps into it and wondering how to proceed, here is my successful method (GingerVolt -> BrokenOut 1.1):
All of the apps, files, and such are found in the various other threads so I will just summarize without links:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Using the OLD AIO, root it.
3 - Using the OLD AIO, install STOCK recovery.
4 - Use Terminal Emulator to echo/create the /data/local.prop
5 - Go to settings->about phone->update and check for new update (and then let it update)
6 - Once you have updated via OTA, use Root&Recovery from the NEW AIO.
7 - Reboot recovery and wipe data
8 - After wiping data and without exiting CWM, flash BrokenOut.
That is what worked for me, I hope it might help others because BrokenOut is frickin awesome (thanks again MT).
LeadPharmer said:
Just for people who might be looking for other ways or are a few steps into it and wondering how to proceed, here is my successful method (GingerVolt -> BrokenOut 1.1):
All of the apps, files, and such are found in the various other threads so I will just summarize without links:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Using the OLD AIO, root it.
3 - Using the OLD AIO, install STOCK recovery.
4 - Use Terminal Emulator to echo/create the /data/local.prop
5 - Go to settings->about phone->update and check for new update (and then let it update)
6 - Once you have updated via OTA, use Root&Recovery from the NEW AIO.
7 - Reboot recovery and wipe data
8 - After wiping data and without exiting CWM, flash BrokenOut.
That is what worked for me, I hope it might help others because BrokenOut is frickin awesome (thanks again MT).
Click to expand...
Click to collapse
Looks good.. although if you did step 1 using LGNPST you don't need step 3. The .tot contains the stock recovery.
I had every problem you could think of (all problems liste here) and this is my method that finally worked:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Factory reset, just in case
3 - Using the OLD AIO (Root&RecoveryAIO), root it (option 1 only!).
4 - Use Check Root app to make sure you have root
5 - Use fileslick app to Change folder permissions and move local.prop file app to
- Open fileslick, click actions, and click show root
- Swipe all the way left until you are at root and see /data folder
- Tap the data folder so it has a green check and then hit actions and select "permisions"
- Check everything in that menu (This will make it so you don't has any permission denied menus when moving the local.prop)
- Put the local.prop file from the "data" folder in the ZV7toZV8Root.zip by tapping it in fileslick, navigating back to the "/data" folder you just set permissions for, clicking "actions" and clicking "copy file to this location"
6 - Go to about this phone in the settings app and check for updates to update ZV8
7 - After reboot use ZV8CWMRecovery.bat (option 1) to install clockwork
8 - After reboot go back and use OLD AIO (Root&RecoveryAIO) to reboot to recovery (option 7)
9 - Reboot recovery and wipe data
10 - After wiping data and without exiting CWM, flash BrokenOut.
11 - DON'T WIPE DATA AFTER FLASH

How do I create a back of system, recovery and boot without root

I want to back up system, recovery and boot so I can root and be able to go back to stock to take otas without having to go back to kitkat and factory reset and all. Otas won' t apply to previously rooted systems, so how to create one without rooting first? I tried twrp, it seems to create a backup but when looking in the folder nothing is there.
You can't
You can't. Because even with ADB commands the phone request for root privileges
It could be that TWRP is using the "legacy" path instead of the default "0" path for the SD card. I use FX file explorer to browse to it. It can be found at /storage/emulated/legacy/. The TWRP folder may be found there, and if so, it can either be copied to /storage/emulated/0/ or you can simply upload the entire folder to a cloud storage of some sort.
Additionally, you would have to restore stock recovery following a TWRP recovery for obvious reasons, so you have to make sure that the stock recovery image is available somewhere to fastboot flash it.
That said, with the new SuperSU, I don't think it modifies the kernel any longer, so a simple unroot from the app would restore /system back to default. The root method simply boots a permissive kernel instead of replacing your phone's kernel. And you wouldn't need to have a TWRP backup of your system partition. Also keep in mind that you would have to restore any other mod to /system such as ad removers which replace the hosts file or wakelock detector app helpers that need to write to /system.

L90 D400h root/unlock bootloader/recovery guide for dummies

Please read full guide before attempting anything once you have fully read and understood the process proceed with caution.
Intro:​
This is the simplified and user friendly process I used to root/ unlock-bootloader and flash recovery for my D400H. I’ve seen many guides and support for other D4xx phones but not for mine which according to original manufacturer software is a D400h model (not D400hn-be careful). Don’t know if this model is set by manufacturer for specific carrier and for branding reasons, which is my guess, but if you have a D400h phone surely this guide will help you. Personally did the research and this guide should save you quite some time, since It took me well over 8 hours to find the correct and working downloads for my D400h.
This is the simplified version so there is no need no for commands, complicated adb pushes, fastboot and other savvy tech jargon; although you will read a lot. As long as you can read follow instructions you should be golden.
As always I am I in no way responsible if you brick your phone (should not be the case but be careful make sure the files and versions of the downloads share the same specs as your d400h), rooting and unlocking your phone will void your warranty (although you can search forum on how to bring your phone back to oem state) always make backups before you start attempting anything, guide should work for other d4xx phones if you select the correct bootloader for your phone. If you are not sure what you’re doing just don’t do it, read, do your own research until you know what you are doing, or decide it’s not worth the risk.
Simplified process:
​ We will:
a) Enable developer-options (enable usb-debugging, and allowing unkown sources)
-needed to be able to install KingRoot​ b) Root device
-Install KingRoot, needed to access root folders and give file browser device administrator privileges​ c) Unlock-bootloader
- needed to be able to install recovery
-Do this by swapping locked aboot file with unlocked downloaded aboot
-use your rooted file explorer es recommended​ d) Install recovery
-Flashify
- make backups and flash custom roms
-TWRP recomended​In this specific order don’t jump the steps.
Detailed process:
A) Enable developer options:
To enable developer options you must go to your phone settings and depending on your specific android version and software you will find it in different places (still under settings menu tree) browse your menu and find Build Number once you have found it tap on top of the builder number till you receive a message that you have enabled developer options. Example of where you might find it are:
Settings > About phone > Build number
Settings > About device > Build number
Settings > About phone > Software information > Build number
Settings > About > Software information > More > Build number
Once you have seen the message enabling developer options or informing you already have them go to main settings menu and access developer options make sure to enable debugging, after that search in developer options or security menu to enable unknown sources make sure that both are enabled.
B) Root:
​This will be the easiest step. I tried many forms and the easiest is to Download KingRoot from original site, any mirroring apk site or make a google search on how to install it.
Once you have installed KingRoot go to app and follow in app instructions to root your phone, for root to work you must restart(reboot) your phone. Sometimes root doesn’t enforce so re-root using KingRoot and reboot again. Do NOT download a root checker or a SuperUser since KingRoot itself has them both built in, once it tells you your phone is rooted (built in checker) you can access king root and in the main menu is the Root Authorization option were you can add manually apps or just wait when app prompts you for authorization.
KingRoot once installed comes with a bundle, ignore purify and all the other stuff direct yourself directly to kingroot for purposes of the guide you can later decide how to proceed.
C) Unlock-bootloader
​So now that we have root privileges, download a root file browser of your preference. I would recommend Es root file explorer, once you download make sure to enable root explorer on the menu (you swipe from left to right on the main window of the es explorer to access main menu- enable root explorer).
Ok this is the part where you must pay attention and be sure on what you are doing.
To be able to install/Flash a recovery we must unlock the bootloader to do this we are going to replace the aboot on our android phone root directory for an unlocked one, we are going to do this by first downloading the correct aboot file.
To know if its the correct file first we must be sure we have a L90 D4xx phone that it’s not a Chinese copy since its processor would be different (Chinesse actualy mod hardware info so it shows the same as original in software, but we will not get into that we will assume its original) the aboot file we download is the same as for the specs of our phone. By this I mean does your phone have nfc, single or dual sim D400hn is not supported. My phone was D400h and fits description of the D405 so after unlocking my phone is now actually a D405 yeay
Be careful to download correct file from this link:
http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632
Once you have downloaded unlocked aboot file (unzip and extract aboot file if zipped or rar file) first copy your original aboot file that’s inside your phone and keep it somewhere accessible like your desktop or laptop. To do this you copy aboot file to phones external memory or some directory that can be accessed from your computer. THIS IS THE ONLY TIME U WILL USE A COMPUTER, though it is optional I highly recommend it. All steps of the guide are to be made from your phone directly (unless you downloaded apk mirror from your computer but again you could have made it directly from your phone).
If you brick your phone you will need original aboot file to unbrick It, via download mode and software, if you cannot do this yourself at least you can give it to the guy who is gonna fix it, having the file makes things easier. If the person who is gonna fix it cannot get a hold on the correct aboot file they wont try hard the can make more and faster money using their time in solving other simple matters they will give it back to you bricked even if its fixable just to not waste their time on it.
Aboot file is in your phone under this directory:
/dev/block/platform/msm_sdcc.1/by-name/
If you cannot get to your root directory google how to do so with your rooted explorer app.
Now that you have back up replace old aboot file with the new one or delete old file and then copy the new one in the same directory. /dev/block/platform/msm_sdcc.1/by-name/
do this with your rooted file explorer, by-name is actually a folder in there you must paste new aboot.
**DON’T reboot your phone just jet and jump directly to Recovery section
D) Install recovery
​Easy-peasy. Download Flashify from play store and use it to flash a recovery from inside the menu, this you can also Google but should be self-explanatory once you have downloaded the app and opened it jut go to Recovery Image.
Since you installed recovery before rebooting your phone and old locked bootloader is gone, because you replaced it or deleted it worse case scenario if you selected wrong aboot file you will still be able to access TWRP or CWM and replace aboot file for original there, to fix your phone if its going in boot loop.
And Voila your D400h is now a unlocked rooted D405 with recovery.
Plz share your experiences on other roms and buy and donate to the apps before mentioned since devs work hard on making and maintaining them.​
What roms have yiu installed? Can any D405 Rom work? thanks for guide. It worked fine

Internal storage encrypted despite all 3 methods. Please help!

Hi!
My only encounter with rooting was several years back when it used to be a simple affair (one click rooting app based on exploits like framaroot etc), so please bear with me.
I'm on Stock Oreo 8.1 (Patch 1 Aug 2019) Sanders 1804 (India) version. I've followed various guides and have been successful in flashing TWRP 3.4.0 (Official Sanders version) and Magisk 20.4. But everytime the phone is rebooted, TWRP can't mount internal storage and shows 0mb.
I tried all three methods I could find:
1. dm-verity zip flashing - Log said fstab not found. Searched and found that from Oreo, Android's encryption approach has been changed. I couldn't make much sense out of those, though.
2. Manually replacing the `forceencrypt` to `encryptable` then flash stock recovery and format data. Didn't work.
3. Formatting data right after TWRP is flashed. Didn't work either.
The maximum it works is for one time when I can connect the device to laptop to add some zips to it to flash. It doesn't make sense to wipe the data when it's the data only that we want to back!
My purpose is to make flashable zip (nandroid) to revert to if anything goes wrong. It was phone's wifi frequent disconnection (or connected but no internet) issue which forced me to try root. I'm not much interested in new ROMs and am fine with stock itself but need a backup of all apps with data etc. Also, I couldn't understand clearly the FAQ on TWRP website that says TWRP doesn't backup internal storage but backup data. As I don't use SdCard, the internal storage is mounted in /sdcard folder only
I'll really appreciate if someone can help me.
Thanks
Found solution from a helpful guy in a Telegram group.
1. Use ONLY attached zip/img files and follow exact same order.
2. Flash TWRP, reboot to recovery
3. In Wipe section, choose Format data, type YES and confirm. Reboot to recovery again.
4. Flash DM-Verity-ForceEncrypt.zip file. Flash Magisk.zip file. Reboot to recovery.
5. (Optional) Make a backup if you want or Reboot to system. Done!
https://drive.google.com/drive/folders/1h8wb78wLH5_VBmkhjpDjyPyDbUG9ZBV4?usp=sharing

Solved - Boot S10 into rooted ROM without requiring 3 buttons pressed

I have purchased my Samsung S10 Exynos and successfully rooted it using the only possible ways that have seems to be available so far. I have gained root, but I was wondering if anyone has solved the issue of having to turn the device on with all 3 keys held down at the same time. I understand that this is because the rooted version of the phone has be installed on the recovery of the phone, but I hope that there becomes a way to turn on the phone with root and use only the power button. I check from time to time, but it seems that this has not been solved yet. If anyone can find a solution for me so that I do not have to keep searching then I will reward them $100. An idea that I had is if there was a way to modify the power button to boot into recovery by itself? I believe this would be impossible but if anyone could think of a way to do that then that would solve the problem. I am okay with never being able to unroot the device if this would be the case.
How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery
DHGE said:
How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery
Click to expand...
Click to collapse
Hello, thank you for the suggestion. I thought about that idea already and I forgot to mention it in my post. I am looking for a way to do it via a cold boot. I know about the reboot into recovery method already, and I know of a way to map the power button to reboot into recovery if held down, but I am looking for a way to cold boot into recovery with just the power button.
I like your idea, but if there was a way to do it as a cold boot then that is ideally what I'm looking for. Your method would work if there was a way to just keep the phone shut down and wait until I hold the power button to turn it on and then it boot into recovery. If you can think of a way to do that then let me know.
The reason I am seeking this is because I root the S10 out to have a proprietary app on it and the app requires root to function properly. I need the power button to boot with root on the S10 so that it will always do so and my employees / customers will not access the non-rooted side of the phone by accident. The 3 button combination is too difficult, so I would need to resort so either a S8 or S9 if the S10 won't allow power button only to boot with root access. The app that I make uses a great amount of battery life so I need the ability to shut down the phone and cold boot it back into recovery. Thanks.
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
Awesome. Your solution sounds perfect for what I was looking for. Yes, I got my S10 back over a year ago and rooted it with patched AP file and magisk. I was only able to find that method even up until yesterday. I would like a step by step if you are able to quickly put one together. If it works then I am glad to grant you the reward for your help. I am willing to do this in the easiest way possible, even if it requires wiping data. I never used the phone so wiping is no problem at all. I am looking to do this to several devices so the easiest and fastest way would be the best. I will look into your comments and see if I can figure out doing this over this weekend. Will keep everyone updated.
pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
I just read some info on the links you provided and i think i can figure it out. if i have any trouble then ill let you know. Dont worry about a step by step for now unless I have any trouble. Thanks!
Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help
pjc21 said:
Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help
Click to expand...
Click to collapse
Hey There, Been busy lately and I haven't gotten around to trying any of these methods until today. Today I attempted the stockrom+CruelKernel. I am having a strange problem. I am acquiring root but as a read-only. I can not make any changes to system files, I can only view them. Can you tell me if you are able to modify or add to the system directory? Let me know. I know your phone is running custom rom + custom kernel, so I just might have to do that if that is the only fix. I have tried several things and read all of the threads but can not find anyone else that is experiencing this issue / I can not find a fix. I'm about to try the custom rom (stock based) + custom kernel to see if that works. If you can tell me if you have access to read/write system files then let me know so I know if this is even possible. Thanks.
I have found out that I can modify system files through twrp recovery, but when I boot into the main operating system then I have root but as read-only.
Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.
pjc21 said:
Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.
Click to expand...
Click to collapse
Cool, I'll give your suggestions a try. I'm a fan of ES File Explorer. They have a root explorer built in their app and previously I had a S8 Exynos and a S9 Exynos and that app worked for those phones but with this S10 the switch is grayed out and no other app is working for me either. On my older S8 Exynos and S9 Exynos I rooted with stock-rom + stock-kernel and just needed TWRP+Magisk and I always was able to modify or add/delete system files with ES file explorer. I guess Samsung is getting more and more strict on allowing this by making us hop through more hoops in order to do so. So far I only have ready only system files on the S10 Exynos which is new to me because the S8 and S9 always allowed modifying system files in the past but I will try your methods you suggested. Worst case I'll attempt the custom-rom + custom-kernel and see if that works. Right now I have stock-rom+custom-kernel. I was able to make changes in the system files in TWRP but hopefully your method will allow me to edit system files without having to switch to TWRP every time I want to change something. I will keep you updated.
On a side note I just rooted a Samsung S20 Exynos and turns out that the system files are read only everywhere whether in TWRP or not, so Samsung keeps making things more difficult on us all. I currently have no way of modifying system files on the S20 no matter what I try but that phone is still much newer so I will give the magicians more time before I look into the forums more for that phone. Right now if I can get the S10 Exynos then I'll be happy.
I'll let you know how things progress. If I get what I need done with this S10 then I am happy to give you a donation for your help in this matter. I would not have gotten this far without your help. Previously the S8 and S9 days were so much easier and people had youtube videos galore that described how to root. The process was easy and everything was unlocked as read write back in the S8 and S9 days.
Yeah I use to use ES on android 6-8 then moved of to solid explorer, very similar ui to ES and also has root explorer but unfortunately it does not work to change permissions on s10 android 10 (bloody samsung/google). So far the only free one I have found is x-plore to be able to do this now. Looks like google is locking down android even more now with android 11

Categories

Resources