Related
Hello.
I have a problem with my phone: I install MIUI 6 (doesn't matter what version), I set it up with restore, it runs ok till the first manual reboot. Then it gets blocked at the black "MI"screen. Won't enter in the OS. Any methods to determine the culprit? Maybe taking a log (how to do that?) It gets kinda annoying to flash the zip again and again everytime I do a reboot.
Thank you.
reneftw said:
Hello.
I have a problem with my phone: I install MIUI 6 (doesn't matter what version), I set it up with restore, it runs ok till the first manual reboot. Then it gets blocked at the black "MI"screen. Won't enter in the OS. Any methods to determine the culprit? Maybe taking a log (how to do that?) It gets kinda annoying to flash the zip again and again everytime I do a reboot.
Thank you.
Click to expand...
Click to collapse
dot restore,just go for a fresh clean install,
if that also doesn't work,then simply go for fast boot method
ZenR2 said:
dot restore,just go for a fresh clean install,
if that also doesn't work,then simply go for fast boot method
Click to expand...
Click to collapse
I have lots of apps and it would take me ages to manually install them all. Back-up and restore from MIUI is my savior.
I also have Xposed Framework, that requires a reboot after install. That reboot works. First I thought it was xposed's fault, but I guess if it would have been that the phone won't start after the reboot it required. Same thing happens with wsm.
Don't install xposed ..
(I had same problem)
Clean install miui 6 once again
Paras1259 said:
Don't install xposed ..
(I had same problem)
Clean install miui 6 once again
Click to expand...
Click to collapse
Same problem meaning your phone won't boot after a while or right after installing Xposed?
I really don't get it. For example, i just clean installed MIUI, restored the apps, installed Xposed + modules and I can do as many restarts as I want, it will boot every single time. The problem appears after a while, I guess starting tomorrow morning it will get screwed up again, although I won't install any apps or anything in the meanwhile.
Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?
Please search next time...
The password is as follows: (type or exactly as written below)
default_password
Pilz said:
Please search next time...
The password is as follows: (type or exactly as written below)
default_password
Click to expand...
Click to collapse
I typed it as you wrote it with the underscore and no uppercase letters but it gives me Password Failed, Please Try Again
I actually made a quick search before posting and I tried this password before.. Another solution is to wipe data/factory reset but if possible I'd like just to re-install TWRP or remove the password somehow
you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.
xBeerdroiDx said:
you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.
Click to expand...
Click to collapse
I assumed he already did this, but in which case we have all been here at one point. I learned the hard way twice now...
kal eh said:
Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?
Click to expand...
Click to collapse
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me
TheSkillfulTroll said:
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me
Click to expand...
Click to collapse
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.
xBeerdroiDx said:
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.
Click to expand...
Click to collapse
Op said he doesn't want to wipe data and he doesn't have access to recovery (I think) saw your post about manual flashing though, pretty good
Sent from my Nexus 6 using XDA Free mobile app
ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?
sinceg1 said:
ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?
Click to expand...
Click to collapse
could be a twrp bug? are you on the latest version? you can try just updating the recovery, via fastboot or app(like flashify). if that doesnt work you can try wiping out the recovery partition(via fastboot) then reflashing the recovery.
yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?
sinceg1 said:
yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?
Click to expand...
Click to collapse
why? all that is is flashing supersu or removing it? that had nothing to do with your recovery. you dont need root to have a custom recovery.
ok, so it seems the next thing to try is wipe recovery partition then reflash recovery. i'll begin looking into how to do that. thank you again.
Had this problem last night, if you have a pattern password try using this:
1 2 3
4 5 6
7 8 9
I had an upper case L and it translated to 2589 and that's what unlocked it for me. Hope this helps someone
Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...
mclisme said:
Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...
Click to expand...
Click to collapse
Are you encrypted?
i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?
sinceg1 said:
i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?
Click to expand...
Click to collapse
Absolutely. If your storage is encrypted, TWRP cannot access it without you entering a password. If you don't enter the password, your storage would appear to be blank to recovery.
I personally prefer to wipe my entire device and keep a kernel that does not enforce encryption. Encryption (in my opinion) makes life difficult for rooted users.
seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.
sinceg1 said:
seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.
Click to expand...
Click to collapse
I'm new to the N6 so I am not sure about decrypting as a process. I just did a full wipe, flashed a kernel that doesnt force encryption .
[Q] >> I've Installed Xposed & Installed Modules, and Now I'm STUCK! Please Help? <<
Hello, I have a Galaxy S5 G900T and I installed Xposed and it was interesting as I thought it was a "Cydia" equivalent to the Android. And I installed modules that could help "tweak" my S5, and after I have finished installing them and I rebooted, now I CAN'T SEE OR ACCESS MY LOCKSCREEN PASSWORD! The one that is the Pattern Lock where you can do a square or Z pattern.. but it just disappeared and it's not even showing up, even if I tapped a lot. You can see my picture attachment below which even the Emergency Button and even the Camera in the corner was gone in the lockscreen
Although I can still receive Calls, Messages and even Alarm Notifications, my real suspicion is that I've installed an Xposed Module, that Disabled my entire lockscreen or something that I haven't fully checked out yet, that caused this without me knowing it
Now I know I have options to do Factory Reset and etc.. however, I know there is still a way I can AT LEAST access my Home Screen or Have a Lockscreen reset itself to show up so I can figure out which of the apps or modules that made my lockscreen disappeared
Does anyone know a way in which we can reset the Lockscreen for it to show up? Or a way to be able to access the Home Screen? Or be able to uninstall Xposed and its modules remotely?
Boot into custom recovery, mount data partition and delete /data/data/de.robv.android.xposed.installer/conf/modules.list
C3C076 said:
Boot into custom recovery, mount data partition and delete /data/data/de.robv.android.xposed.installer/conf/modules.list
Click to expand...
Click to collapse
OR he could just flash this http://forum.xda-developers.com/showpost.php?p=60468815&postcount=18
A few fix tips
A few things you could try.
1) Flash the xposed framework disabler zip file via your recovery. Find out how to do that here
2) Use ADB to disable the pattern. Find out how to do so here
3) As a last resort, completely factory reset your phone. A google search will point you in the right direction.
Hope this helps, don't forget to thank if it does.
@C3C076 @Agent-Droid @Kris the wizz 15 Thank you for your replies! I tried doing flash a lot of times and even put the Zip files in my SD card and even tried out the methods in http://forum.xda-developers.com/showthread.php?t=2620456 but now the next problem is I keep getting this error "E: footer signature is wrong, E: signature verification failed", and even if it says "Applying Update Complete'' it just reboots it and does nothing
How can we go through that?
EDIT: I haven't did the ADB procedure as I'm still trying to understand all of this, I would really appreciate any help given
You have to use custom recovery since only they can be set to ignore signature verification of zip files to be flashed. If it is a custom recovery, check its options.
Finally it's fixed now! IT WAS A MIRACLE! I suddenly remembered and I actually used AndroidLost in my computer and it helped "unlocked" the screen, but the funny thing was it didnt fully unlock the screen but it just opened Google Speech, and by that time, MultiWindow was opened so I was scared to death and just backed up everything, removed the lockscreen, and uninstalled Xposed and the modules that messed up.. I was scared as hell but now its working lol
But what I found out about my recovery is that, It's pretty much "broken" seeing that even USB debugging wont work in my computer, Kies and Odin can't read my phone being plugged in, and My Recovery can't even Flash zip files anymore therefore kinda rendering it useless not unless, I fully factory reset my phone
Now for people who don't wanna go through this experience, I fully recommend you download "AndroidLost" or any of those apps that help you unlock your phone when your phone is lost.. and to also read http://forum.xda-developers.com/showthread.php?t=2620456 so you can be prepared and have a better Recovery so you don't have to go through this
Take note of that
Just to clarify
MoRTiZz3 said:
@C3C076 @Agent-Droid @Kris the wizz 15 Thank you for your replies! I tried doing flash a lot of times and even put the Zip files in my SD card and even tried out the methods in http://forum.xda-developers.com/showthread.php?t=2620456 but now the next problem is I keep getting this error "E: footer signature is wrong, E: signature verification failed", and even if it says "Applying Update Complete'' it just reboots it and does nothing
How can we go through that?
EDIT: I haven't did the ADB procedure as I'm still trying to understand all of this, I would really appreciate any help given
Click to expand...
Click to collapse
Well, the xposed disabler zip counts on you having a custom recovery installed. You (correct me if I'm wrong) seem to be running stock samsung recovery, which won't flash the zip properly due to certain signatures that the recovery needs.
Since you've already rooted, any warranty you may have had is probably null and void anyway, so you may as well go the whole nine yards and install a custom recovery. You can find out how to do so here or here
Not only will this enable you to flash the xposed disabler zip file, it will also open you up to a world of custom Roms.
The ADB procedure basically uses root access to reset the pattern in your phone so as to enable you to use any pattern you please. That should help you access the xposed app to disable all the modules, and re-enable them as needed.
None the less, here's a few informative links:
1) What is ADB?
2) What's fastboot?
3) Easily intall ADB and Fastboot
4) What is a custom recovery?
5) What is a custom ROM?
Read through these, and then we can make a comprehensive decision.
Sorry for assuming you don't already know this stuff.
ok, I think I know the answer, but checking for any other ideas. For some reason my phone was trying to unlock in my pocket, and of course it failed 10 times, and says it is going to wipe phone. It reboots to recovery, but fails dm verification, I assume because it is rooted. I select reboot and it goes back to welcome, says sd card is removed, and it is going to wipe phone because of failed login, and reboots again. Question is best way to get out of this loop. If I do factorey reset from system recovery, will I lose root? Can I get it again? or do I need to refresh my brain and remember how to odin and install a rooted stock rom? any ideas on what would be easiest?
Just did factory reset, kept root, even kept all my blacked out apps
Just run repair assistant
joe12401 said:
ok, I think I know the answer, but checking for any other ideas. For some reason my phone was trying to unlock in my pocket, and of course it failed 10 times, and says it is going to wipe phone. It reboots to recovery, but fails dm verification, I assume because it is rooted. I select reboot and it goes back to welcome, says sd card is removed, and it is going to wipe phone because of failed login, and reboots again. Question is best way to get out of this loop. If I do factorey reset from system recovery, will I lose root? Can I get it again? or do I need to refresh my brain and remember how to odin and install a rooted stock rom? any ideas on what would be easiest?
Click to expand...
Click to collapse
Just did factory reset from the computer, just run repair assistant, Its a very easy way.
Reggards
Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS),
i am not responsible if anything goes wrong. You are still the one who tryed to flash the files. Even tough this should work as it worked for me and some friends.
Hello XDA
This is my first post (sorry if one already exists)
Today i am going to tell you how to root the Galaxy S9 International on android 9 Pie on stock touchwiz rom.
First of all download all these files;
Prince comsy odin: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Team win recovery https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
ElementalX Kernel https://elementalx.org/devices/samsung-galaxy-s9/
No verity encrypt: https://androidfilehost.com/?fid=962187416754474353
Magisk 18.0 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Now for the root
First you need to unlock OEM, you can do this in developer options,
If there is no developer options you need to enable this
you can do this in: Settings>About Phone > software information > click 5 times on build number.
When you unlock OEM everything on your phone gets wiped so make a backup!!
When the wiping is complete, turn off your phone and go to download mode (Vol down + Bixby + Power)
Then connect the phone to your pc and start odin
In odin go to options, and disable f.reset and auto reboot.
Then press the AP button and select the TWRP image you downloaded.
When TWRP is flashed, force reboot your phone (Vol down+ Power) when it is powered off quickly press Vol Up + Bixby + Power to get into recovery
Swipe to allow modifications. And format /data
Then reboot into recovery.
When rebooted mount USB Storage and connect the phone to the PC
Then you can click&Drag the other files (elemental, Magisk, No verity)
When the files are on the phone, go to install and search for the files you just put on the phone.
Install in this order:
Flash No-Verity-Encrypt
Then flash the custom kernel (ElementalX)
And as last flash Magisk.
When you did this, you want to Factory reset, Wipe cache and Dalvik.
Then you can reboot the phone, and install it.
(It is possible that you stay at the boot logo for a long time (Not the galaxy s9 one but the next one) What you need to do then is let it boot for 5 minutes, then force reboot (vol down+Power) and then the phone boots fine)
Again, just to make sure check if OEM is still unlocked (sometimes this get locked again)
Please note that when you do this, you lose secure folder and other functions, also is the knox tripped (0x1)
But the Fingerprint, Irisscanner and samsung account works.
SOMETIMES IT IS NEEDED TO INSTALL THE MAGISK MANAGER MANUALLY, YOU CAN JUST DOWNLOAD THE FILE FROM THE LINK IN THIS POST
Hope this helps.
If you do have any questions, please do the following first;
Note any errors that odin or your phone gives you. I want to help you, but i do need to know what is going wrong.
(Sorry for my bad english)
reserved
So you won't need RMM-state_bypass on pie anymore?!? Seems hard to believe...
And why exactly you need to flash that custom kernel, which benefits does this bring with it?
sarius02 said:
So you won't need RMM-state_bypass on pie anymore?!? Seems hard to believe...
And why exactly you need to flash that custom kernel, which benefits does this bring with it?
Click to expand...
Click to collapse
If you dont use the custom kernel, you will get RMM error.
Iris scanner wont work, Fingerprint wont work, Samsung account wont work. When you reboot the phone you get a little "Bootloop" at the lockscreen (Screen flashes and is unusable and your pattern isn't saved)
I dont know what else breaks because i cant even get past the lockscreen with stock kernel
(Also you get better performace and battery life)
Hope this helps
work it with s9+?
Sorry for my English...
Yes, but you want to use tgpkernel then otherwise it will not work (problems described abovel
https://www.androidfilehost.com/?w=files&flid=288240
Last samsung phone i rooted was the note 3, and i remember that doing that "tripped" knox 0x1 and this basically voided the warranty. It's the same with S9? is there some non-reversible change that happens to the phone when rooting?
effry said:
Last samsung phone i rooted was the note 3, and i remember that doing that "tripped" knox 0x1 and this basically voided the warranty. It's the same with S9? is there some non-reversible change that happens to the phone when rooting?
Click to expand...
Click to collapse
Yes, the knox will still trip (0x1).
In europe, when you can show that the root is not the cause of the problem, they have to fix it under warranty.
Also there are some functions you will lose (forever)
Knox,
Samsung pass,
Samsung Pay,
S-Health(you can fix this one with a build.prop tweak)
Secure folder
If you plan to use one of these (exceptpt s-health) It is better not to root your phone (there are still external app's you can use if you plan to root your phone)
Is there a way to update the stock firmware when you have root? Or do i have to do all over again?
I have this lock screen flashing bootloop issue, what is the fix? I have tried factory restores but get the same results once I set a lock/passcode and reboot. Samsung Account and Bixby also do not work as you mentioned.
You can use TGPkernel then,
Some phones have this issue, some not.
I have seen that 3 friends of mine it worked, and also on 3 not, so this is a very weird issue
What was the fix with them is to install TGPkernel
@co9
The only way i know is to install a custom kernel,
Otherwise you have to download latest stock rom, and flash this using odin.
wich changes your recovery.img and boot.img, aswell as the kernel. so you have to flash this all over again
Thanks for the answer. I already have a custom kernel. So if i always want to have the latest Samsung firmware i have to flash it through odin and do the whole root procedure again?
I tried this method but now everytime I reboot the phone my bluetooth paired device are lost. They also get deleted if I turn ON and OFF the Airplane mode. Anyone else having the same issue ?
Is anyone else experiencing an issue where the password, pin, or pattern set before setting up fingerprint scanning acts like what was entered is incorrect, not allowing you to setup fingerprint scanning?
I've tried setting up fingerprint scanning on initial setup as well as skipping and trying after the phone has been setup but had no luck. What ever I set initially will not work when I'm prompted later on when trying to setup fingerprint scanning or tying to access other secure features. The phone just prompts to try again acting like I entered in the wrong password, pin, or pattern. I've even tested by setting up a REALLY simple password with no luck.
I have confirmed in the settings that Elemental is installed.
Edit: I did find this thread https://forum.xda-developers.com/galaxy-s9/help/root-galaxy-s9-exynos-9-0-android-pie-t3884267. I tried the no-verity-opt-encrypt-6.0.zip that was suggested in some posts but had no success. I've also tried the TGPKernel but had not change in the issue. I am able to setup fingerprint scanning on fresh firmware install but after installing TWRP and everything else the above issue happens.
Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
See lot of people have trouble, here are the steps to do, dont get confused keep it simpel nothing more
1 Flash the last pie build (sammobile.com) with Odin, restart mobile, let system install
2 Enable unlock OEM (settings->about phone->softare information-> tap a few times on build so developer options tab is in settings go there and enable oem unlock)
3 Flash TWRP (twrp.me/) with Odin and immediately after the flash hold bixby+volume up+ powerbutton to go to TWRP
4 In TWRP, swipe to allow modifications.
5 Go to Wipe - Format (yes). Press the back button all the way to home of TWRP
6 Reboot recovery
7 In TWRP, swipe to allow modifications, click on install button and flash dm-verity v1 and press the back button all the way to home of TWRP
8 Click on install button and flash magisk v18
9 Reboot system and let system (android 9) install enter pin, google account and so on...
10 Install magisk app
11 Open Magisk, if you see there is no root/magisk installed, no worry!! Just download Magisk from the Magisk app to the download folder on your phone, restart your phone adn go to TWRP and install Magisk again.
Done!
Used Software:
Odin3_v3.13.1
Twrp 3.2.3.2
no-verity-opt-encrypt-samsung-1.0
Magisk-v18.1
MagiskManager-v7.0.0
menhammer said:
Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
See lot of people have trouble, here are the steps to do, dont get confused keep it simpel nothing more
1 Flash the last pie build (sammobile.com) with Odin, restart mobile, let system install
2 Enable unlock OEM (settings->about phone->softare information-> tap a few times on build so developer options tab is in settings go there and enable oem unlock)
3 Flash TWRP (twrp.me/) with Odin and immediately after the flash hold bixby+volume up+ powerbutton to go to TWRP
4 In TWRP, swipe to allow modifications.
5 Go to Wipe - Format (yes). Press the back button all the way to home of TWRP
6 Reboot recovery
7 In TWRP, swipe to allow modifications, click on install button and flash dm-verity v1 and press the back button all the way to home of TWRP
8 Click on install button and flash magisk v18
9 Reboot system and let system (android 9) install enter pin, google account and so on...
10 Install magisk app
11 Open Magisk, if you see there is no root/magisk installed, no worry!! Just download Magisk from the Magisk app to the download folder on your phone, restart your phone adn go to TWRP and install Magisk again.
Done!
Used Software:
Odin3_v3.13.1
Twrp 3.2.3.2
no-verity-opt-encrypt-samsung-1.0
Magisk-v18.1
MagiskManager-v7.0.0
Click to expand...
Click to collapse
Don't root this phone without flashing a custom kernel or a modified stock kernel. It will drain battery and reduce the performance or even crash the system.
Look in the TWRP thread there it is explained why you shouldn't do it.
Emre67511 said:
Don't root this phone without flashing a custom kernel or a modified stock kernel. It will drain battery and reduce the performance or even crash the system.
Look in the TWRP thread there it is explained why you shouldn't do it.
Click to expand...
Click to collapse
My personal experience is i have rooted using this method and have had no problems
Hi all,
I tried to flash twrp but never succed.
S9+ last firmware from samsun android 9 pie (update from smart switch)
Then option developper activated, no oem unlock menu found,
boot into download mode and there is written oem unlock desactivated so ok
with odin try to flash (ap, reboot freset unchecked)
then fails and message in red on the phone :
"only official released binaries are allowed to be flashed recovery"
History :
I was in galaxy project oreo, i wanted to upgrade with pie, but reboot cycle
so rescue with odin and original oreo firmware, then update to pie
thanks for help
regards
To get the oem unluck button visible.
After fresh install, go to time/date in settings, choose manual and set the date 1 mount prior (march will be februar)
Than go to software update, choose manual en click on dowload updates manually.
Restart your phone and the oem unlock button in developer options will be there
Cheers
thank's for answering,
Update done, reboot ok but still not oem options in developpers section