Related
Well this is my second time I am trying to install custom ROM on any android phone. First one was some cheap phone from local brand. And I ended up in bricking that phone. This time it seems I have boot looped beloved Nexus 6. :crying:
So now I know I have very poor experience with MODing stuff.
I decided to install latest lineage OS on my Nexus 6.
I followed steps given on lineageos.org tutorial:
Enabled developer options
Enabled USB debugging
Enabled OEM unlock from developer options
Installed adb drivers
Connected Nexus 6 to PC using USB
Selelcted transfer photos (PTP) mode on nexus 6 in the prmpt that appeared after connecting USB
Booted into fastboot by doing "adb reboot bootloader" command (I have my volume down button screwed up while replacing battery. Though there is no visible damage. I dont know what happened . So I was not able to boot into fastboot by holding volume down while mobile powers on. )
Downloaded TWRP and installed it doing "fastboot flash recovery twrp-x-x-x-x-shamu.img" command
The lineageos.org tutorial then asks to boot into recovery using volume down key. But since mine was screwed up, I didnt know how I can do that. So I fiddled a bit in fastboot mode and found that when I press volume up, there comes "recovery mode" option. So I pressed power button when recovery mode is shown when in fastboot mode. It successfully booted in TWRP recovery.
Then I tried to perform the backup from the TWRP. I used to get something "unable to mount..." error. I tried it twice/thrice. Then I booted into Android. I realized that I can run "adb reboot recovery" command to get back into the recovery. So I tried that but then I got No Command error. So I pressed and held power button for some time, it booted into android. I ran "adb reboot bootloader". When in fastboot, I pressed volume till it showed recovery option and then pressed power button to boot into recovery. Then I tried backup again and it worked this time. So it never worked when I boot into TWRP for first time. I had to boot into android and then again back into TWRP (through fastboot) second time for it to work. This pattern repeated for other things.
Then I tried to perform backup of system through TWRP. Somewhat similar thing happened. It was giving "Unable to mount..." error. So I boot into Android, then into fastboot, then into TWRP and it worked. I booted into Android and copy pasted those backup files on my PC.
Then I tried to perform wipe from TWRP. It again gave "Unable to mount..." error. So I again followed above steps. Booting Android -> Fastboot -> TWRP and then performed wipe (I wiped everything cache, system etc). It worked.
Then lineageos.org tutorial asks to put lienageos zip at /sdcard/ using command "adb push filename.zip /sdcard/". I guess I tried it in recovery and it was not working. Hence I selected to reboot in bootloader (or I guess System) from TWRP. (I am not remembering this last steps as I was noting down only those steps which worked in notepad which are explained till last point in this procedure. But I know I rebooted from fastboot after wiping) And thats where I screwed it up :crying: . Now only Google logo displays. When I long press power button, the Google logo diappears for a while and reappear. Irony is that my volume down also seems to be screwed. What options I am left with???
... mmh
I miss the step "fastboot oem unlock" between 7. and 8. (before flashing TWRP) to open the bootloader
Your step "3. Enabled OEM unlock from developer options" is just the requirement to open the bootloader!
You have to open the bootloader with the adb prompt "fastboot oem unlock" after booting to bootloader!
1. open bootloader
2. reboot system !!!
3. reboot to bootloader
4. flash TWRP (custom recovery)
my advice - back to start ...
please look here for the last factury image and flash the whole image as described
-> https://developers.google.com/android/images
Mahesha999 said:
[*]Selected transfer photos (PTP) mode on nexus 6 in the prmpt that appeared after connecting USB
Click to expand...
Click to collapse
Select Transfer files.
When you boot after flashing LOS the forced encryption flag is set.
When the internal memory was decrypted.... the encryption process starts. Can take a very long time.
MartinN6 said:
... mmh
I miss the step "fastboot oem unlock" between 7. and 8. (before flashing TWRP) to open the bootloader
Your step "3. Enabled OEM unlock from developer options" is just the requirement to open the bootloader!
You have to open the bootloader with the adb prompt "fastboot oem unlock" after booting to bootloader!
1. open bootloader
2. reboot system !!!
3. reboot to bootloader
4. flash TWRP (custom recovery)
my advice - back to start ...
please look here for the last factury image and flash the whole image as described
-> https://developers.google.com/android/images
Click to expand...
Click to collapse
ohhh I felt its optional. I indeed do that "fastboot oem unlock" and it said it was successful. I just felt its optional and it did not had any effect on my phone, so I did not included that in the steps I performed above. Sorry my bad.
NLBeev said:
Select Transfer files.
When you boot after flashing LOS the forced encryption flag is set.
When the internal memory was decrypted.... the encryption process starts. Can take a very long time.
Click to expand...
Click to collapse
My phone is bootlooped (stuck on google logo). I am not even able to get into bootloader since my volume down key is screwed. I got screwed only after wiping data and before flashing LOS. Now I am trying to understand how your comment makes sense.
Mahesha999 said:
My phone is bootlooped (stuck on google logo). I am not even able to get into bootloader since my volume down key is screwed. I got screwed only after wiping data and before flashing LOS. Now I am trying to understand how your comment makes sense.
Click to expand...
Click to collapse
The possibility that the N6 is busy with encrypting and not looping (hopefully).
Other ideas:
When connected to a PC and adb environment is ok. Try the command: 'adb reboot bootloader'
Repeatedly while booting. In a dosbox it's easy to repeat a command with arrow up/down.
Keep start and vol up pressed and see if recovery comes up.
The screwed vol down.
Try to get a bit isopropanol/alcohol under the volume button to clean. Use a needle.
Instead of keeping the button down keep both vol.buttons down; maybe you are lucky.
Hi OP
May I ask:
if the bootloader was unlocked before you tried this time or stock with bootloader locked?
When you wiped did you wipe internal storage too or left it unchecked in TWRP?
NLBeev said:
The possibility that the N6 is busy with encrypting and not looping (hopefully).
Other ideas:
When connected to a PC and adb environment is ok. Try the command: 'adb reboot bootloader'
Repeatedly while booting. In a dosbox it's easy to repeat a command with arrow up/down.
Keep start and vol up pressed and see if recovery comes up.
The screwed vol down.
Try to get a bit isopropanol/alcohol under the volume button to clean. Use a needle.
Instead of keeping the button down keep both vol.buttons down; maybe you are lucky.
Click to expand...
Click to collapse
I tried doing all that with volume button. Finally imported circuit fom ebay.com and got it working.
Was able to Install lineageOS 15.1 successfully, but the experience wasnt that smooth due to disabled CPU
cores. I tried installing elementalX on lineageOS through their official app. But seems that I am back again in bootloop. I asked
the detailed question here. Can you please have a look?
Mahesha999 said:
Can you please have a look?
Click to expand...
Click to collapse
Trials with kernels and wiping/formatting may cause issues, because LOS forces encryption every time it's installed.
When you want to use LOS don't change the kernel and use the built-in kernel.
When the phone is not smooth, you may want to decrypt your Shamu and use a custom rom, like Nitrogen OS (Pie). A decrypted phone is necessary than.
NLBeev said:
Trials with kernels and wiping/formatting may cause issues, because LOS forces encryption every time it's installed.
When you want to use LOS don't change the kernel and use the built-in kernel.
When the phone is not smooth, you may want to decrypt your Shamu and use a custom rom, like Nitrogen OS (Pie). A decrypted phone is necessary than.
Click to expand...
Click to collapse
Ok didnt get you well.
How can I decrypt? Any official link.
Also installing Nitrogen OS means wiping out LineageOS?
Also didnt get "A decrypted phone is necessary than".
Do you mean decrypted phone is what is needed.
Also does that means there is simply no custom kernel compatible with LineageOS 15.1 for Nexus 6? and I have live with only two cores?
Sorry for too many questions... ;\
Mahesha999 said:
How can I decrypt?
Do you mean decrypted phone is what is needed.
Click to expand...
Click to collapse
A decrypted phone is only needed when you want to install a Pie rom like Nitrogen OS.
A new custom rom implies you will loose LOS.
There's nothing wrong with LOS, it worked well on my Shamu, but I used the built-in kernel and didn't care about the kernel and cores
For now. Try to get LOS working and use the built-in in kernel.
Decrypting your phone can be done with TWRP. You need to format everything including the sdcard.
But when you stick to LOS forget about decryption.
NLBeev said:
Trials with kernels and wiping/formatting may cause issues, because LOS forces encryption every time it's installed.
When you want to use LOS don't change the kernel and use the built-in kernel.
When the phone is not smooth, you may want to decrypt your Shamu and use a custom rom, like Nitrogen OS (Pie). A decrypted phone is necessary than.
Click to expand...
Click to collapse
After watching some videos and some googling, I realized that its not about the kernel actually which turns off cores but its hotplug mpdecision. I installed kernel audiutor and enabled all cores of my Nexus 6. Also I realized that max frequency of my active cores were something 1958 MHz. I just increase it to max 2649 MHz and rebooted. My Nexus 6 is going super smooth now. Also ran geekbench4 benchmarks.
These are the benchmarks.
Before changing CPU stuff
================================================
Benchmarks 1
-----------------------------------------------------------------------------------------------
Single core: 593
Multicore: 997
After changing CPU stuff
================================================
Benchmarks 2
-----------------------------------------------------------------------------------------------
Single core: 818
Multicore: 1009
Benchmarks 3
-----------------------------------------------------------------------------------------------
Single core: 1069
Multicore: 3029
I feel that two cores were still offline during benchmark 2. When I checked after benchmark 2, they were off in kernel adiutor CPU monitor. I re-enabled them and I reran the geekbench. I ended up getting benchmark-3 which are quite good and in fact above average for Nexus 6. For 5-10 minutes now, all cores are active.
I then googled and realized that mpdecision restarts after every reboot. So I have to disable mpdecision on every reboot to enable all cores. Initially I was not getting meaning of two ON/OFF switches on kernel adiutor's interface. They were "Apply on boot" and "mpdecision". Now I have "Apply on boot" switched ON and "mpdecision" switched off. That means on every reboot, all my cores will be up at full frequency right?
Also that means more power consumption. So I have done certain things to compensate. Enabled dark mode so that Nexus's quad HD AMOLED will consume less power. Also installed Franco kernel's Servicely app which allows app and services to put on sleep when screen is off. I am also planning to use Nexis 6's always in battery saver mode. I am ok as long as it performs fast (with two core off, battery saver mode was useless, now it seems like very normal). Its just that only top and bottom orange bars/strips in battery saver mode annoys me.
One more thing I will love to have to save battery. In MIUI, there is per app setting for what to allow when app is in background as can be seen here: http://nine-faq.9folders.com/articl...-background-restriction-on-the-xiaomi-devices On my poco f1, I keep almost all apps "No background activity mode". Only handful have "No restriction". This is letting me extend battery to days straight. Is similar possible on lineageOS say through some apps or setting.
Also do you feel my config all fine? Latest lineageOS + All cores running at full speed + Power saving settings explained above? Is this perfect for performance and battery life? Should I disable encryption for further performance?
(Will be testing battery life soon for few days.)
(Just to add things implicit to me: I wont be installing any social media app on this, I keep data and location off always. I will be using Nexus 6 mostly for reading in chrome, pdf, word and youtube.)
Mahesha999 said:
. . .I realized that its not about the kernel actually which turns off cores but its hotplug mpdecision. Also installed Franco kernel's Servicely
Should I disable encryption for further performance
Click to expand...
Click to collapse
I think you have done well. You've found the cause of performance issues and made your Shamu smooth again.
Dark mode is important for the battery life.
Decrypting will raise performance mainly when writing to internal storage. For daily use you won't hardly notice a difference. Your phone is running smoothly now. So there's no need for.
I was very excited to install this update that released today, but after installing it, I can't sign in to my phone. When it boots up, it flashes the homescreen wallpaper, not the lockscreen wallpaper for a second or two then the screen turns black. If I hold the power button I can view the power settings (reboot, silent, airplane mode, shut down) and also if I double press the power button, which my camera shortcut, it opens the camera. Aside from these actions, I can't do anything.
My method to installing this rom was this:
Download the rom from xiaomi.eu website
use the built in updater where I select a rom on my phone and it automatically boots to recovery for me (I'm using TWRP)
Let it do its thing, and boot up, then when it boots the errors occur.
I tried wiping cache and dalvik, but no change.
Did I miss something? Is there something I should have done differently when updating my phone? Is there a special procedure in upgrading Android versions? (1.1.2.0 is first Android Pie version on my phone)
Thank you very much.
Edit 1: I have flashed a second time, this time flashing cache, dalvik, and data. I was able to get into MIUI and set up my device, but after I rebooted the phone for a separate reason, I am experiencing the same errors as before.
Edit 2: Not 100% sure because I switched ROMs, but I probably could have gotten it working by wiping /system as well.
Hello, same thing here.
Clean install and same problem... very sad
DaniloFerracini said:
Hello, same thing here.
Clean install and same problem... very sad
Click to expand...
Click to collapse
Yep same here. I tried it again, wiping data partition and same issue. Can't downgrade because rollback protection too. I guess I'll try out Pixel Experience??
DaniloFerracini said:
Hello, same thing here.
Clean install and same problem... very sad
Click to expand...
Click to collapse
Hey, by the way, what launcher are you using? This seems to be a problem with just the lock screen so maybe there is a weird interaction happening between the launcher and the lock screen. I was using Rootless Pixel Launcher.
Edit: one more question: did you do the same thing as me where I first flashed without formatting data, then you flashed a second time, that time formatting the data? I'm thinking it could also be just because we flashed it incorrectly the first time, future flashes are gonna be messed up.
Where's the download I can find only 10.1.1.0
AquaticPossum said:
Hey, by the way, what launcher are you using? This seems to be a problem with just the lock screen so maybe there is a weird interaction happening between the launcher and the lock screen. I was using Rootless Pixel Launcher.
Edit: one more question: did you do the same thing as me where I first flashed without formatting data, then you flashed a second time, that time formatting the data? I'm thinking it could also be just because we flashed it incorrectly the first time, future flashes are gonna be messed up.
Click to expand...
Click to collapse
I make a dirty flash and clean flash, nova launcher and stock launcher, both dont work
kekkojoker90 said:
Where's the download I can find only 10.1.1.0
Click to expand...
Click to collapse
https://sourceforge.net/projects/xi...ulti_MI8_V10.1.2.0.PEACNFI_v10-9.zip/download
DaniloFerracini said:
Hello, same thing here.
Clean install and same problem... very sad
Click to expand...
Click to collapse
Try this : https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
You must have a valid custom recovery
Edit : the recovery method won't work... It's a problem with the rom. Just switch to another version....
https://xiaomi.eu/community/threads/miui-10-0-10-1-stable-release.47170/page-23 see the last posts about that
my phone also dead after install the last pie my phone stuck on a black screen
tried downgrading the miui to oreo and the phone did not work well the phone reboot after 30 sec
and after that happened I backed to pie version again but the same problem stuck on a black screen I don't want to lose my data what can I do?
there is possible to back the oreo version and restore that data from twrp backup? the apps work well or not?
almog250 said:
my phone also dead after install the last pie my phone stuck on a black screen
tried downgrading the miui to oreo and the phone did not work well the phone reboot after 30 sec
and after that happened I backed to pie version again but the same problem stuck on a black screen I don't want to lose my data what can I do?
there is possible to back the oreo version and restore that data from twrp backup? the apps work well or not?
Click to expand...
Click to collapse
You shouldn't downgrade :/
kekkojoker90 said:
You shouldn't downgrade :/
Click to expand...
Click to collapse
Even with xiaomi.eu rom ?
Otarie004 said:
Even with xiaomi.eu rom ?
Click to expand...
Click to collapse
You can downgrade from Pie to Oreo with EU rom and TWRP, the phone boot up normaly but some processes say stop working.
I had same problem yesterday. I recommend wipe system before reinstalling Oreo rom and waiting a fixed Pie rom
kekkojoker90 said:
Where's the download I can find only 10.1.1.0
Click to expand...
Click to collapse
This is the Xiaomi.eu ROM which is based on China Stable.
AquaticPossum said:
I was very excited to install this update that released today, but after installing it, I can't sign in to my phone. When it boots up, it flashes the homescreen wallpaper, not the lockscreen wallpaper for a second or two then the screen turns black. If I hold the power button I can view the power settings (reboot, silent, airplane mode, shut down) and also if I double press the power button, which my camera shortcut, it opens the camera. Aside from these actions, I can't do anything.
My method to installing this rom was this:
Download the rom from xiaomi.eu website
use the built in updater where I select a rom on my phone and it automatically boots to recovery for me (I'm using TWRP)
Let it do its thing, and boot up, then when it boots the errors occur.
I tried wiping cache and dalvik, but no change.
Did I miss something? Is there something I should have done differently when updating my phone? Is there a special procedure in upgrading Android versions? (1.1.2.0 is first Android Pie version on my phone)
Thank you very much.
Edit 1: I have flashed a second time, this time flashing cache, dalvik, and data. I was able to get into MIUI and set up my device, but after I rebooted the phone for a separate reason, I am experiencing the same errors as before.
Click to expand...
Click to collapse
This stable ver has many problems. It's hasnt stable yet. Even when you could turn the screen on, if you use the 3 buttons as default, everything is normal, but if you use fullscreen gestures and reboot your phone, you will stuck in black screen again. Many friends and me have the same black screen problems. So my advice is you should stay where you are waiting for a real "stable" ver.
For all who want to use FSG in version 10.1.2.0 I would recommend the following workaround:
a) Startup freshly installed system
b) Select navigation bar as preferred method and finish setting up the phone
c) Download Magisk v18.0
d) Reboot into TWRP and flash Magisk v18.0 zip
e) Reboot to system
f) Download the free application "Fluid Navigation Gestures" and setup the same Gestures as in Stock mi8
g)Optional: In Fluid NG, choose "Hide Navigation Bar"
It doesn't have the exact same feeling as stock but is pretty close and I think it's valid as a meantime workaround.
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
Oxygen 9.5.9 is out.
Use Oxygen Updater if needed.
Animaitons are even faster wtf, lol.
Great update
velvethammer said:
Animaitons are even faster wtf, lol.
Great update
Click to expand...
Click to collapse
If I want to retain TWRP & Magisk after the update, is my procedure correct?
1. Reboot to TWRP
2. Flash 9.5.9
3. Flash TWRP
4. Reboot TWRP
5. Flash Magisk
6. Reboot system
storytellerz said:
If I want to retain TWRP & Magisk after the update, is my procedure correct?
1. Reboot to TWRP
2. Flash 9.5.9
3. Flash TWRP
4. Reboot TWRP
5. Flash Magisk
6. Reboot system
Click to expand...
Click to collapse
or
1. Download update and flash via Local Storage in Settings > System > System Update > click on Gear Icon (that way you can still use your phone while its installing and you won't miss calls or texts)
2. Once Done and Installed DO NOT REBOOT
3. Open Magisk and Click Install > Install > Install to Inactive Slot (After OTA)
3.5 Reboot...
4. (Optional if u want to install TWRP at the moment) Open Magisk and Install TWRP Installer (Do Not Reboot)
5. Go Back to Magisk click Install > Install > Direct Install
5.5 Reboot...
Done!
My bootloader is unlocked, but I am not rooted. Downloaded with oxygen updater, but installation fails at 86% each time.
Sent from my GM1917 using Tapatalk
---------- Post added at 10:02 PM ---------- Previous post was at 09:33 PM ----------
Ok downloaded the full update and it installed fine.
Sent from my GM1917 using Tapatalk
I'm loving this update. It does seem snappier, and the reddish screen tint I was experiencing has been fixed. Also, I noticed that when using gesture navigation, Gboard has been moved up so that the symbols and enter key aren't cut off by the rounded lower corners. This is my first OnePlus device and I'm impressed at their attention to detail.
Yep, this update Rock's!??
velvethammer said:
Animaitons are even faster wtf, lol.
Great update
Click to expand...
Click to collapse
I find that even with animation scale set to .5 in developer settings I was really happy with the phone.
But playing around after the update I found a setting in accessibility that allowes for announcing to be turned off completely and I'll tell you what besides a blink of screen change its for sure the quickest phone I've ever used. Haven't used Samsung since gs7 so that's not much to say. Very happy with updates and phone. 1st OP device and wow.
I didn't recieve any update.
Is it out for model GM1911?
Auto brightness still sucks ass, autofocus seems to be a bit better, need some more testing.
Everything else seems very smooth. Keep those updates coming, 1+.
don't notice any differences. especially with the camera in pro mode as advertised. I think they add the same statements every update lol
paysen said:
Auto brightness still sucks ass, autofocus seems to be a bit better, need some more testing.
Everything else seems very smooth. Keep those updates coming, 1+.
Click to expand...
Click to collapse
Before the update my auto brightness was very slow to dim at night.... Now it's faster... What's your problem?.... Maybe I will notice something...?
My vibration for texts isn't as strong as it used to be on this update. Has anyone else notice this?
Bradl79 said:
or
1. Download update and flash via Local Storage in Settings > System > System Update > click on Gear Icon (that way you can still use your phone while its installing and you won't miss calls or texts)
2. Once Done and Installed DO NOT REBOOT
3. Open Magisk and Click Install > Install > Install to Inactive Slot (After OTA)
3.5 Reboot...
4. (Optional if u want to install TWRP at the moment) Open Magisk and Install TWRP Installer (Do Not Reboot)
5. Go Back to Magisk click Install > Install > Direct Install
5.5 Reboot...
Done!
Click to expand...
Click to collapse
i dont get why people say not to reboot
just update via the local updater
reboot - let the update finish installing
then reboot-bootloader and boot twrp, flash twrp, magisk and reboot.
unless you dont have access to a computer.
virtyx said:
i dont get why people say not to reboot
just update via the local updater
reboot - let the update finish installing
then reboot-bootloader and boot twrp, flash twrp, magisk and reboot.
unless you dont have access to a computer.
Click to expand...
Click to collapse
They said no reboot so that you can preserve twrp if you are away from a computer. Its a lot slow to have to boot twrp using adb each time.
Easier method is to not reboot, and flash Twrp retention script.
mlock420 said:
Before the update my auto brightness was very slow to dim at night.... Now it's faster... What's your problem?.... Maybe I will notice something...?
Click to expand...
Click to collapse
It was alternating between "way too bright" and "way too dark" in my bedroom when the light's are turned off. Sometimes you just scroll a website and the auto brightness dims the display, because the display seems to block the sensor.
paysen said:
It was alternating between "way too bright" and "way too dark" in my bedroom when the light's are turned off. Sometimes you just scroll a website and the auto brightness dims the display, because the display seems to block the sensor.
Click to expand...
Click to collapse
Got ya....I too have noticed that?
mlock420 said:
Got ya....I too have noticed that
Click to expand...
Click to collapse
I just use it (auto brightness) in daytime atm, have to readjust very often though. As soon as it is getting darker, I use it only manually. No surprises then
paysen said:
I just use it (auto brightness) in daytime atm, have to readjust very often though. As soon as it is getting darker, I use it only manually. No surprises then
Click to expand...
Click to collapse
Yeah I don't use auto brightness all that much... No biggie
I managed to get all the other updates with a German VPN, but this one is still not showing. I don't want to use any third-party tool or download zips, which is why I prefer to use the built-in OTA downloader.
Anyone was able to Root Note 9 Exynos android 10 ?
i have tried dr.ketan as well as forcedecrypt/magisk 20.2 all combos and stuff ,it results in bootloop.
if anyone is able to root please write steps thanks!
EDIT :- METHOD TO ROOT N960FXXU4DSLB (ANDROID 10) for Exynos version.
i got so many briks today trying different methods to root android 10 latest update, please dont use TWRP recovery posted here which is latest v3.3.1 for Q that is the main issue, dont use dr.ketan root.zip either again bootloop.
SIMPLY FOLLOWS these steps:-
1. Flash android 10 DSLB with ODIN with CSC (Not home_CSC again bootloop).
2. Now it will start the device,do the normal setup.
WAIT UNTIL SIM CARD MANAGER popups (if this popups we have OEM Unlocking option appear, as we have already enabled that before), or you can manually go there and see you should get service provider signels.
and then goto the settings > about > software > tap 7 times build version, then goto developer options, OEM should be enabled itself and then ebale usb debugging.
3. Switch of phone,goto download mode (BIXBY + VOL DOWN + USB Cable plugged in)
4. use odin 3.14 and flash geiti's Twrp-3.2.3-0-crownlte.tar
5. boot to TWRP > allow modifications (important) > Wipe > format data > yes and then boot to recovery again.
6. now transfer the files to internal storage or if you have microsd u can skip this.
files - magisk-20.2.zip , RMM-State_Bypass_Mesa_v2.zip , No-Verity-Opt-Encrypt-6.0.zip.
7. flash RMM-State_Bypass_Mesa_v2.zip
8. flash No-Verity-Opt-Encrypt-6.0.zip
9. flash magisk-20.2.zip
10. flash again RMM-State_Bypass_Mesa_v2.zip.
11. reboot system, it will boot if not it will shut down and reboot itself, resetup again and you are rooted now.
Magisk 20.2 bug. Try with Magisk 20.1
i fixed it, i even ripped all device today when here was only download mode saying goto smartswitch nothing was working, follow steps above you are good to go!
Following these steps helped me get a working TWRP but there are some weird things going on:
- after I set up a pin there's no lockscreen asking me for the pin
- if I try to log into my Samsung account I get a "processing failed" pop up
- when I try setting up some biometrics like iris scanner it keeps asking me for a pin (not the same as the one I did set up earlier)
- if I restart my phone I end up with a bootloop
Any idea what's going on?
XGamer404 said:
Following these steps helped me get a working TWRP but there are some weird things going on:
- after I set up a pin there's no lockscreen asking me for the pin
- if I try to log into my Samsung account I get a "processing failed" pop up
- when I try setting up some biometrics like iris scanner it keeps asking me for a pin (not the same as the one I did set up earlier)
- if I restart my phone I end up with a bootloop
Any idea what's going on?
Click to expand...
Click to collapse
after flashing twrp > format data and reboot to recovery
try flashing it in order
https://www43.zippyshare.com/v/8NH3aUn0/file.html
https://www43.zippyshare.com/v/IdZPt02e/file.html
https://www43.zippyshare.com/v/hiKinhVp/file.html
BytesReverser said:
A
1. Flash android 10 DSLB with ODIN with CSC (Not home_CSC again bootloop).
2. Now it will start the device,do the normal setup.
WAIT UNTIL SIM CARD MANAGER popups (if this popups we have OEM Unlocking option appear, as we have already enabled that before), or you can manually go there and see you should get service provider signels.
and then goto the settings > about > software > tap 7 times build version, then goto developer options, OEM should be enabled itself and then ebale usb debugging.
3. Switch of phone,goto download mode (BIXBY + VOL DOWN + USB Cable plugged in)
4. use odin 3.14 and flash geiti's Twrp-3.2.3-0-crownlte.tar
5. boot to TWRP > allow modifications (important) > Wipe > format data > yes and then boot to recovery again.
6. now transfer the files to internal storage or if you have microsd u can skip this.
files - magisk-20.2.zip , RMM-State_Bypass_Mesa_v2.zip , No-Verity-Opt-Encrypt-6.0.zip.
7. flash RMM-State_Bypass_Mesa_v2.zip
8. flash No-Verity-Opt-Encrypt-6.0.zip
9. flash magisk-20.2.zip
10. flash again RMM-State_Bypass_Mesa_v2.zip.
11. reboot system, it will boot if not it will shut down and reboot itself, resetup again and you are rooted now.
Click to expand...
Click to collapse
thank you I have been tring to root android 10 since the Dec 20th I kept doing these steps but it wasn't working for me the main issue was twrp I was using 3.3.1 for Q and for Pie none of them were working I changed twrp to 3.2.3 now it is working perfectly thank you again
but you should upload those files so no one would use a wrong file
anyone has a solution for TWRP? now I have rooted my phone but one small problem after the first autoreboot after installing these files data encryption comes back so after that auto reboot if you go to TWRP you'll need to format data again then you can make modification
I need twrp so I can restore my data and I already tried to restore data before first and then install magisk , RMM bypass and no verity encryption then flasshong RMM bypass again but then it wont boot it will stuck at samsung logo (not first logo)
XGamer404 said:
Following these steps helped me get a working TWRP but there are some weird things going on:
- after I set up a pin there's no lockscreen asking me for the pin
- if I try to log into my Samsung account I get a "processing failed" pop up
- when I try setting up some biometrics like iris scanner it keeps asking me for a pin (not the same as the one I did set up earlier)
- if I restart my phone I end up with a bootloop
Any idea what's going on?
Click to expand...
Click to collapse
I faced that same problem and it is caused by No Verity file you flashed
Solution is
1. Reflash Android 10 with odin (All files) (flash reguler CSC not HOME CSC)
2. Do the above steps in order as @BytesReverser mentioned But skip step 8 and 10
you'll have root access but you will still have one problem after you reboot your phone if you want to install anything or want to make modification with TWRP then you need to format your data again cause after first reboot data encryption reactivates it self
Thats right it still stays but i have took backup using smart switch now, will restore later cuz even fstab removed the forceencrypt still it stays encrypted
Sorry root success, but fingerprint stop working after root!
I can no longer log in to the samsung account. why?
Try this method Root Note 9 with Magisk on Android 10 (Q) without Custom Recovery
BytesReverser said:
after flashing twrp > format data and reboot to recovery
try flashing it in order
https://www43.zippyshare.com/v/8NH3aUn0/file.html
https://www43.zippyshare.com/v/IdZPt02e/file.html
https://www43.zippyshare.com/v/hiKinhVp/file.html
Click to expand...
Click to collapse
Help please
I followed this steps and i´m stuck in boot screen
Got the TWRP 3230, tried with your Magisk file and the version 20.3
Need help to root your Note 9.
Any new method with TWRP without problem?
nothing but adds on those links no matter where i click :S
Zer0De8th said:
Try this method Root Note 9 with Magisk on Android 10 (Q) without Custom Recovery
Click to expand...
Click to collapse
Go to this link and works for me.[emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
inamie said:
Go to this link and works for me.[emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
which method works for you? twrp?
Am getting error :/
TWRP file please?
inamie said:
Go to this link and works for me.[emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
The method from the link works for me as well. But be aware that you will not be able to install TWRP afterwards. You will only have the rooted N9 on Q that works fine.