Develop Bugs

[Q] 5.0.1 Rooted to 5.0.2 Without Data Loss

For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.

Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps

I'm having the exact same problem. I'm attaching what's appearing on TWRP.

All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.

I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.

You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.

yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app

^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.

newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx

mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.

All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?

Root for Stock 6.0.1

From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA

http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

Root works with supersu version 2.62-3. Thanks

sam298 said:
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
Click to expand...
Click to collapse
That wasn't my experience. I took the 6.0.1 update and it failed. So I ran
Code:
fastboot flash system system.img
fastboot flash boot boot.img
using the system and boot images from the 6.0 update. And then I waited for the OTA again. It installed ok.
Using TWRP I installed SuperSU 2.60 for a systemless root of the boot image. Everything is fine.

i can't even get pass installing twrp. every time i flash twrp in fastboot mode it works but it wipes my entire device. booting into twrp shows "NO OS INSTALLED' and even the sd card storage is wiped. the only way to get it to boot is to flash back 6.0.1 full stock rom. any help???

Try nexus root toolkit.

tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
WugFresh did not work for me, after booting into TWRP and looking for the SuperSU and BusyBox they don not show up. Below is a post I have over on WugFresh Forum.
I’m having the same problem as everyone else. I’m using 6.0.1 MMB29K. It goes through the motions but when TWRP launches the /sdcard directory is empty. However, when I reboot and look at the files using an app called File Manager, I see them in /storage/emulated/0/!ReadyToFlash/Root_Files/. However, if I use a app called Root Browser I see a directory called sdcard and in there is !ReadyToFlash/Root_Files/ so they are being copied to the tablet but when you go into TWRP to install them they can’t be found. I tried to use the app Root Browser and make a directory called kiledl, this failed, probably because I do not have root access. Kind of a catch 22 here. I was just going to copy the files in sdcard to my directory and then try again. NO go!!! Anyone else have any ideas? I seems like this is some sort of permissions issue with the files but only from TWRP. I sure hope someone comes up with an answer, WugFresh and ideas?

tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
same result. twrp installed but can't detect my sd card or any files on the device

Download latest SuperSU 2.62-3.
Root via Nexus root toolkit.
Then copy SuperSu to nexus and flash, supersu not from NRT but downloaded latest 2.62-3, busybox and last rar.
Sorry for my English.

Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)

dlkile said:
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
Click to expand...
Click to collapse
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.

aiiee said:
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.

aiiee said:
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Correct only when using TWRP. However, I was using WugFresh NRT and it does a temporary install of TWRP then you install the SuperSU and BusyBox files. However, with the wrong version of TWRP you would not see the files in the SDCard folder, it would be empty. However, booting back to Android and using File Explorer the files where there. Using the modified version of TWRP would correct this.

interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again

r.sorujlall said:
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
Click to expand...
Click to collapse
Yes, here is the link you need to select the LTE or WiFi version depending on you device. I do not have enough post to be able post links, so try removing the "*" from the link below.
forum*.xda-developers*.com/nexus*-7-2013/nexus*-7-2013-qa/mount*-recovery*-t3064562

dlkile said:
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
Click to expand...
Click to collapse
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?

aiiee said:
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
Click to expand...
Click to collapse
You most have the same unit as I do. I just got mine a week ago from GroupOn as well.

i bought mine about a week ago off amazon. i had a gift card and had nothing to buy so i decided to get the N7 and give it a try

Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP

Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
CyanogenMod Thread
Reddit Thread
EDIT3:
WiFi and Settings Issue seems to be resolved
I think the problem had something to do with the baseband version
As per Trex's post (http://forum.xda-developers.com/showpost.php?p=69520362&postcount=2), I had to revert back to the OK1 baseband
Now everything seems to work fine
As for TWRP not working and just going to a black screen, I redownloaded it from the TWRP website and it worked fine
So now both TWRP and CM are installed and working, WiFi works, and Settings don't crash.
Now I've encountered an issue where the camera doesn't focus, and I'm wondering if there's still some plastic film on the camera lens, but I've been picking at it and nothing is coming off and I'm afraid of damaging the plastic if I keep trying...

AbuFiraas said:
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
Click to expand...
Click to collapse
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help

Trex888 said:
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Click to expand...
Click to collapse
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?

Just flashed OK1 via Odin via this thread, but it's just boot looping over and over
EDIT: Did a simple factory wipe and it's working fine now. Currently running unrooted Stock 5.1.1, Baseband N910PVPS4COK1. So I'm basically starting from the beginning, whereas before it was on 6.0 but now it's 5.1.1

Am now rooted but I can't get TWRP installed, I flash it and try to boot to recovery but it just boots to a black screen

Issue seems to be resolved, edited original post

AbuFiraas said:
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Click to expand...
Click to collapse
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware

Trex888 said:
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Click to expand...
Click to collapse
It's working now, I found another post that had all the various stock firmwares on there. Now the issue I'm having is that my camera doesn't focus at all, but I don't know if it's a hardware or software issue. I never checked the camera before rooting the first time. Gonna try going back to unrooted stock again but if that doesn't change anything, I might have to take it to a Sprint store and get a replacement. Hopefully they don't notice the KNOX trip... lol

Losing root on reboot

I recently flashed v30b on my D855. I did a clean (CSE) flash with the LG flash tool 2014 and rooted the device with KingRoot. But every time I reboot I lose root acces.
I installed the bump'd version of TWRP with flashify, but when I try to boot into TWRP I get a MISMATCH_SIG_LEN error before the screen goes black and the led starts blinking. I then pull out the battery to start over with a fresh unrooted phone. I think I loose root acces before entering recovery or something. I did some searching, but the only solution I found was to do a clean install, which I already did.
My goal is to install TWRP to flash custom ROMs. How do I fix this?

I think that after installing root with kingroot you will need to perm root it. Kingroot is only temporaty and even if you uninstall it you get unrooted.

Nikolatas said:
I think that after installing root with kingroot you will need to perm root it. Kingroot is only temporaty and even if you uninstall it you get unrooted.
Click to expand...
Click to collapse
I'm having a sort of similar problem on my D85130d. I downgraded fine from 30g to 30d with LGUP. downloaded kingroot and rooted. That was all good. Installed TWRP and flashed the recovery rom and was able to make a backup of my current stock rom (which has saved my life because I think I've soft bricked my phone about 4 times trying to permanent root hahah). Since I AM new to rooting I think I'm missing a certain step, (or maybe the zips im trying to flash are corrupt?) Basically, tried https://forum.xda-developers.com/tm...wngrading-rooting-t3608851/page3#post74961164 and I've also tried https://forum.xda-developers.com/tm...ock-d851-30d-kdz-flashable-zips-imgs-t3367371. The problem with the first one is its not completely specific and like I mentioned before, I'm a white belt at rooting lol. The second thread gave me hope and i do have TWRP installed so I downloaded the 2 main zips I would need (a. LG-D85130D-Flashable.Boot-AUTOREPACK.zip
and b. SuperSU zip) reboot to recovery and flashed both zips separately then reboot. But I end up with a TMO screen and it stays like that. This last time I even left it loading on that screen for about 2 hours and no such luck. I'm wondering is there something I'm missing? Any help would be greatly appreciated from the XDA gods

HingleMcCringleberry said:
I'm having a sort of similar problem on my D85130d. I downgraded fine from 30g to 30d with LGUP. downloaded kingroot and rooted. That was all good. Installed TWRP and flashed the recovery rom and was able to make a backup of my current stock rom (which has saved my life because I think I've soft bricked my phone about 4 times trying to permanent root hahah). Since I AM new to rooting I think I'm missing a certain step, (or maybe the zips im trying to flash are corrupt?) Basically, tried https://forum.xda-developers.com/tm...wngrading-rooting-t3608851/page3#post74961164 and I've also tried https://forum.xda-developers.com/tm...ock-d851-30d-kdz-flashable-zips-imgs-t3367371. The problem with the first one is its not completely specific and like I mentioned before, I'm a white belt at rooting lol. The second thread gave me hope and i do have TWRP installed so I downloaded the 2 main zips I would need (a. LG-D85130D-Flashable.Boot-AUTOREPACK.zip
and b. SuperSU zip) reboot to recovery and flashed both zips separately then reboot. But I end up with a TMO screen and it stays like that. This last time I even left it loading on that screen for about 2 hours and no such luck. I'm wondering is there something I'm missing? Any help would be greatly appreciated from the XDA gods
Click to expand...
Click to collapse
To be fair, i perma rooted the v30B variant. Im not sure bout the D. I rooted it with kingroot, installed TWRP via autorec, i went in recovery and flashed the file thats in the post, rebooted and then installed supersu from the playstore and im perma rooted. After that kingroot is gone and you are left with supersu. This is the guide i followed https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268

Can Android 10 beta be rooted?

If it can, how? I'm having bootloop issues trying to do that. Thank you.

Bootloop in logo S9

RpRAUC said:
Bootloop in logo S9
Click to expand...
Click to collapse
follow up

Piereligio said:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961

https://forum.xda-developers.com/ga...rooting-installing-twrp-t4012961/post81084623
The patched kernel contained here was the solution for me

S9 ROOT
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q

viktorvlahov11 said:
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
Click to expand...
Click to collapse
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.

it stucks for me on the samsung logo

aidenpearce296 said:
it stucks for me on the samsung logo
Click to expand...
Click to collapse
Try flashing the twrp flashable firmware it may fix your problem
---------- Post added at 08:41 AM ---------- Previous post was at 08:37 AM ----------
viktorvlahov11 said:
Try flashing the twrp flashable firmware it may fix your problem
Click to expand...
Click to collapse
Piereligio said:
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
Click to expand...
Click to collapse
I got it to work on a Bulgarian unlocked model
Maybe try flashing the twrp flashable firmware after the mod

omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it

viktorvlahov11 said:
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
Click to expand...
Click to collapse
I done that, but still stuck on SAMSUNG logo, no boot loop or what. I was waiting 10min, nothing happened.
Any advice?

Hi there,
after having tried different methods to root my S9, which has updated to Android 10 One UI 2.0 this morning, maybe the solution that finally worked for me will help you too.
First I tried to root just like in Pie, as found on the net: flashed TWRP 3.2.3 via Odin, then flashed Magisk with TWRP plus this no-verity-opt-encrypt. Got stuck in bootloop, tried different no-verity/dm-verity versions, Magisk 18.x and Magisk 20.1. Nothing worked, got stuck again every time i rebootet the system again.
Then, after realising that I CANT get back to Android 9 (old rom wasnt Odin flashable anymore, phone didnt boot, BSoD), I first downloaded the new stock rom and bootloader as zip, got it from here:
https://forum.xda-developers.com/showpost.php?p=81615561&postcount=1830.
You have to check if that fits with your version / phone. Once downloaded, I copied both onto my SD card. So now I was able to install at least the new clean stock rom. Oh, and now I used the TWRP version 3.3.1.
Then I found this:
https://forum.xda-developers.com/galaxy-s9/development/root-s9plus-exynos-android10-t4065343
At first I tried to root without the SoLdieR9312's mod, only with MAGISK 20.3 and no-verity. Stuck again, it only bootet to download mode, nothing else. So flashed again the clean stock rom, and after first not keeping the right order (I suppose) I finally followed EXACTLY the instructions 1 - 4 in above manual including SoLdieR9312's mod (I highly recommend first a complete Wipe, format data, and then flash the clean new Rom with Android 10 and bootloader from above link).
Now, to save you the time I spent today: once your phone is bootet (and succesfully rooted via Magisk 20.3, which will happen automatically due to the SoLdieR9312's mod), DONT LET MAGISK UPDATE TO VERSION 20.4!!!! Magisk Manager asks you to update, but when I did update to 20.4, everything fell apart again, it only bootet to download mode.
Now I seem to have it stable and running with 20.3 and the [email protected]. I rebootet 5 times so far just for the sake of it, and it works fine and rootet.
If I can be of further help, please let me know. I spent the last 12 hours on this matter, so dont hesitate.
Greetz from me minus a bunch of nerves
PS: After I wrote the above, I deleted the Knox family in the rootet system, and then it collapsed again and, after BSoD, it only rebootet into download mode. I can not exclude the possibility, that this might have been the reason for some system breakdowns before, as I had to re-do the wipe-clean-install-then-root-then-customize worksteps aroung 8 times yesterday before it was stable as it is now. Now I´ll leave Knox on it, though that itches me a bit. But I´m exhausted for now
PPS: IMPORTANT when I try to create a PIN or a pattern for the lock screen, phone reboots to SIM card PIN screen and then keeps rebooting and rebooting. It looks like there are some interferences with root and PIN / security. I did NOT create a Samsung account, only a google one, cause in the beginning i suspected it might have been a Sam acct problem (I constantly couldnt log into it on the phone). Turns out that might not have been the case, rather a prob between root and setting a lock screen security.