Related
Guys today I came here with a simplified rooting method for titan running marshmallow 6.0 that doesn't need boot.img modification
Note -You need to have bootloader unlocked and custom recovery like twrp installed on your device before proceeding
Unlock bootloader here
Flash the custom recovery of your choice using auto flash script included in separate attachment
1) Download and rename recovery file as recovery.img and put into the folder of auto flash script.
2) Reboot your device into bootloader mode and connect to PC using USB cable [You shold have latest motorola device manager installed and your device should indicate usb connected on bootloader screen]
3) Now open 'auto flash recovery script' folder and run auto_flash_recovery.bat file
4) Now custom recovery is installed on your device
Steps for rooting-
1. Download BETA-SuperSU-v2.62-3-20151211162651.zip and place it in root of your internal sd card (other supersu version does not work on titan running official marshmallow)
2. flash BETA-SuperSU-v2.62-3-20151211162651.zip using twrp recovery
3. wipe delvick cache and cache (optional)
4. reboot device
5. If you want to use stable super su version i.e. UPDATE-SuperSU-v2.65-20151226141550.zip or any version like any supersu beta except BETA-SuperSU-v2.62-3. download and flash it over BETA-SuperSU-v2.62 after rooting.
6. If you have previously rooted your MM running device using SuperSu-v2.52 with modified boot.img, You need to flash stock boot.img first and reboot then follow this guide (step 1-5)
#BETA-SuperSU-v2.62 will do all required modification by its own script automatically.
Note- Dnt flash any other supersu version or SuperSU-v2.65 alone on unrooted device. you will get bootloop. Do a backup of your rom before any rooting operation.
In case if u stuck on bootloop flash this update UnSu script via twrp, wipe delvick and cache and reboot. this script will remove any supersu file installed in your device thus fully unrooting ur device that will recover you from bootloop
Thank you! It's working!
Perfect, It's working!
Working,great
Sent from my XT1068 using Tapatalk
Where can we get the stock boot.img for Marshmallow?
If u r running stock mm, then ur boot.img is also stock.
i think it's not necessary to root again if i already rooted with modified boot image does that make any difference
mandar91 said:
i think it's not necessary to root again if i already rooted with modified boot image does that make any difference
Click to expand...
Click to collapse
It is recommended to use stock boot.img
gauravrai said:
It is recommended to use stock boot.img
Click to expand...
Click to collapse
BUT currently i m on cm 13
Failed Root with XT1064 6.0
Everything ran smoothly installing the zip from TWRP, but on reboot: no SuperSU; no root. Now warnings or errors came up in the TWRP text during root.
MotoG 2014 XT1064
System: 24.41.34 titan_retuaws.retuaws.en.US retus
Kernel version 3.4.42-gef77327
TWRP-3.0.0-0-titan
Installed zip: BETA-SuperSU-v2.62-3-20151211162651.zip
Device is unlocked. Status Code 3
Update to 6.0 was with OTA after flashing the stock rom using XT1064_TITAN_RETUAWS_5.0.2_LXB22.99-24.12_cid9_CFC.xml.
The phone was previously 5.0.2 Rooted.
I did not lock the bootloader during the process.
The OTA to 6.0 went smoothly.
Followed the above instructions to the letter....
The only thing odd I did was uninstall the SuperSU App on the phone before flashing TWRP and starting this Root operation.
Has anyone gotten this to work on XT1064? Or any other root method on stock 6.0 and XT1064
fidorulz said:
Has anyone gotten this to work on XT1064? Or any other root method on stock 6.0 and XT1064
Click to expand...
Click to collapse
This will work on all Moto devices running stock marshmallow.
Root Moto G2 running on Official 6.0 Android Marshmallow Without (modified boot image)
https://youtu.be/9_9vkJvzWcU
Every time i remove system apps it boot loop any work around for this in marshmallow.. In lollipop removing system apps can normally booted up without any problem..
I successfully rooted my stock marshmallow on XT1068. I had softbricked it previously by using a newer version os SuperSu (I hadn't located this post yet, so I didn't recover from it with you script. I reflashed stock).
So, many many thanks.
In the end, my successful steps were
- flashboot flash recovery twrp-3.0.2-0-titan.img
- reboot into recovery
- install BETA-SuperSU-v2.62-3-20151211162651.zip from TWRP
- wipe dalvik & cache
- reboot device
wildingol said:
I successfully rooted my stock marshmallow on XT1068. I had softbricked it previously by using a newer version os SuperSu (I hadn't located this post yet, so I didn't recover from it with you script. I reflashed stock).
So, many many thanks.
In the end, my successful steps were
- flashboot flash recovery twrp-3.0.2-0-titan.img
- reboot into recovery
- install BETA-SuperSU-v2.62-3-20151211162651.zip from TWRP
- wipe dalvik & cache
- reboot device
Click to expand...
Click to collapse
Now over 2.62 supersu u can also flash any upgraded version like stable or any latest beta.
Sent from my XT1068 using XDA-Developers mobile app
Confirmed working on TWRP 3.0.0.1, stock Marshmallow 6.0 from OTA updates. Every other SuperSU got stuck on unlocked bootloader screen.
Thanks!
gauravrai said:
Guys today I came here with a simplified rooting method for titan running marshmallow 6.0 that doesn't need boot.img modification
Note -You need to have bootloader unlocked and custom recovery like twrp installed on your device before proceeding
Unlock bootloader here
Flash the custom recovery of your choice using auto flash script included in separate attachment
1) Download and rename recovery file as recovery.img and put into the folder of auto flash script.
2) Reboot your device into bootloader mode and connect to PC using USB cable [You shold have latest motorola device manager installed and your device should indicate usb connected on bootloader screen]
3) Now open 'auto flash recovery script' folder and run auto_flash_recovery.bat file
4) Now custom recovery is installed on your device
Steps for rooting-
1. Download BETA-SuperSU-v2.62-3-20151211162651.zip and place it in root of your internal sd card (other supersu version does not work on titan running official marshmallow)
2. flash BETA-SuperSU-v2.62-3-20151211162651.zip using twrp recovery
3. wipe delvick cache and cache (optional)
4. reboot device
5. If you want to use stable super su version i.e. UPDATE-SuperSU-v2.65-20151226141550.zip or any version like any supersu beta except BETA-SuperSU-v2.62-3. download and flash it over BETA-SuperSU-v2.62 after rooting.
6. If you have previously rooted your MM running device using SuperSu-v2.52 with modified boot.img, You need to flash stock boot.img first and reboot then follow this guide (step 1-5)
#BETA-SuperSU-v2.62 will do all required modification by its own script automatically.
Note- Dnt flash any other supersu version or SuperSU-v2.65 alone on unrooted device. you will get bootloop. Do a backup of your rom before any rooting operation.
In case if u stuck on bootloop flash this update UnSu script via twrp, wipe delvick and cache and reboot. this script will remove any supersu file installed in your device thus fully unrooting ur device that will recover you from bootloop
Click to expand...
Click to collapse
VIDEO TUTORIAL:-
https://www.youtube.com/watch?v=9_9vkJvzWcU
Work !
---------- Post added at 12:43 AM ---------- Previous post was at 12:42 AM ----------
Work thanks
i Tried this on Xt1072 Moto G 2nd Gen 2014 LTE and had to use the UnSu first as per the instructions and for the reasons described in red. I was also stuck in bootloader with that horrible message that says your bootloader is now unlocked! Now the issue is I seem to be stuck on the Motorola hand stitched by peter crawley boot screen? I saw someone aske dhow long this lasts? I had to use an OTG usb flash drive to get my files on to the damn phone for some strange reason phone and pc having massive communication issues, not playing very nicely with each other????? wtf? anyway I got okays and successful messages when in TWRP 2.8.5.0 I just dont understand why there seems to be such a huge problem with getting this f"£$%^&*g phone sorted.
Nexus 5 rooted and flashed with the beautiful elemental x kernel, why cant we get elementalx for moto g? its absolute genius! now someone tel me what the hell is going on here, when will I ever have success with this damn phone? I hate bloat and it only has 8GB plus the sd card which is configured as internal storage, could this be what the problem is?
hi guys i have 6.0 b525 bootloader unlocked and i have coustom recovery i just need root file ty
xzero21 said:
hi guys i have 6.0 b525 bootloader unlocked and i have coustom recovery i just need root file ty
Click to expand...
Click to collapse
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Check chapter 8: Getting root
Though actually needed steps are
1. Flash 1.zip (It makes SuperSu to install in system-less mode to make it able to boot on our phone)
2. Flash normal SuperSu.zip (newest stable version)
3. Reboot phone
4. Phone bootloops few times and then boots normally
5. You're Done!
keikari said:
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Check chapter 8: Getting root
Though actually needed steps are
1. Flash 1.zip (It makes SuperSu to install in system-less mode to make it able to boot on our phone)
2. Flash normal SuperSu.zip (newest stable version)
3. Reboot phone
4. Phone bootloops few times and then boots normally
5. You're Done!
Click to expand...
Click to collapse
just take 1zip ?
fares1444 said:
just take 1zip ?
Click to expand...
Click to collapse
Yes and SuperSu you can find here https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
And better take back-up before flashing, just in case
Alternatively, you can use Magisk to root your phone (just flash the zip through TWRP and it's done).
This is a guide for people who want a rooted MIUI. It will keep stock recovery and system partitions untouched to allow MIUI OTAs to install without problems. It will also pass Google's safety net test so bank apps keep working. The best of both worlds really
Requirements:
- Unlocked bootloader
- Windows PC
- fastboot (present in the miunlock app folder)
- Latest TWRP (download here)
- Latest Magisk (download here)
Steps:
- Install latest Magisk app
- Put latest Magisk zip on your device storage (SD)
- Shut down device
- put latest twrp.img in miunlock folder
- Connect phone to PC
- Press volume down and power button to boot to fastboot mode
- Open "Command Prompt" on your PC
- Type: (without quotes)
----- "cd C:\Users\[your name]\Desktop\miflash_unlock-en-2.3.803.10" . (or wherever the folder is)
----- "fastboot devices"
----- "fastboot boot twrp.img"
- In a few seconds, TWRP will boot on your phone. DO NOT swipe to make changes to system.
- In TWRP, flash the Magisk zip
Enjoy root
Disclaimer: I will not be help responsible for any damage or loss caused by following those steps.
Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g
kn1g said:
Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g
Click to expand...
Click to collapse
Same as my question. Let say system partition won't touch by root, but twrp is installed over the Mi stock recovery. Will it install Eta?
This guide DOES NOT flash TWRP. Stock recovery remains so OTA updates work.
The only thing that is touched by this guide is the "Boot" partition to install magisk. You can restore stock "Boot" using magisk manager's uninstall option at any moment and be 100% stock again.
Ok, but is Xposed etc. possible?
kn1g said:
Ok, but is Xposed etc. possible?
Click to expand...
Click to collapse
I haven’t tried but should work.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
It is really works! Thank you!
gonna check this cause i wanna root the phone but keep enjoying updates
I just rooted my Note 4 Qualcomm by this method, so far so good. Really easy and dummy-proof tutorial
I bump this because it worked. Quite easy, clean and fast. Thanx!
I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?
masri.razak said:
I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?
Click to expand...
Click to collapse
Wrong...u need to boot twrp not to install. Read the OP for steps.
Dadovvv said:
Wrong...u need to boot twrp not to install. Read the OP for steps.
Click to expand...
Click to collapse
Well... That's I mean, boot TWRP using adb
After have TWRP, how can i get update via OTA?
it successfully worked for Redmi Note 4 global beta/stable MIUI9.2
even installed camera api 2 using magisk module
Just a quick question. I've TWRP right now with SuperSU. So I'll remove SuperSU, flash Magisk in TWRP. All good till now, but I'd want the stock recovery, a flash-able zip maybe. How can I get it? From where?
**[EDIT]**
Okay. One can get it from fastboot ROMs available at MIUI website (here), extract the pack and get recovery.img.
Installed successfully on miui 9.2.1.0 stable
Now when a new update for magisk is released, how should i update it??
I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
I'd like to keep the phone untouched but I need to change emojis and with Xposed I can use Youtube in background.
Giacomo_ITA said:
I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
Click to expand...
Click to collapse
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)
Baxeisindi said:
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)
Click to expand...
Click to collapse
Do you mean this?
When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
Click to expand...
Click to collapse
Giacomo_ITA said:
Do you mean this?
Click to expand...
Click to collapse
Yes, I hope it works, anyway at the next update I will reroot it in a few minutes.
The following process is what I have been successfully doing in the last year to keep my Moto G5 Plus on the most up-to-date stock ROM but rooted with Magisk.
The high level process for OTA update and rooting is different from the case where the phone has never been rooted and where the phone is already rooted with this method.
Requirements
1. Unlocked bootloader (https://forum.xda-developers.com/g5-plus/how-to/unlock-bootloader-lenovo-motorola-moto-t3581133).
2. Fastboot tools installed on a PC (https://forum.xda-developers.com/showthread.php?t=2588979).
3. TWRP recovery for the Moto G5 Plus: twrp-3.2.1-0-potter.img (https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html).
4. TWRP recovery for the Moto G5 Plus: twrp-3.1.1-0-potter-decryptdata.img (https://forum.xda-developers.com/g5-plus/development/unofficial-twrp-3-1-0-0-moto-g5-plus-t3576575).
5. Magisk and Magisk Manager (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
6. Magisk Module - F2FS Loopback Bug Workaround: f2fs-loopback-bug-workaround-2018.1.31 (https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875)
7. Micro SD card installed in the Moto G5 Plus.
Items 3. and 4. may no longer be necessary once the official version of TWRP supports decrypting data on the Moto G5 Plus (https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1153).
Phone has never been rooted (stock ROM installed)
1. Apply any pending OTA update and verify it succeeds
2. Turn off the phone
3. Boot into fastboot mode (volume down + power)
4. Connect the phone to a computer via USB.
5. Boot into TWRP recovery without flashing with the following command (ignore data decryption): fastboot boot twrp-3.2.1-0-potter.img
6. Take a backup of boot and recovery with TWRP (use external storage)
7. Reboot into fastboot mode (Reboot > Bootloader)
8. Connect the phone to a computer via USB
9. Flash TWRP recovery with the following command: fastboot flash recovery twrp-3.1.1-0-potter-decryptdata.img
10. Reboot into recovery
11. Allow TWRP to modify the system partition and prevent the rom from restoring the stock recovery
12. Root the device by installing Magisk using TWRP.
13. Install the f2fs-loopback-bug-workaround-2018.1.31 Magisk module.
14. Reboot into system.
15. Install Magisk Manager and verify Magisk is correctly installed
16. To install extra Magisk modules is recommended to reboot in TWRP (Magisk Manager > Modules > Reboot Recovery) then install the modules from there (for example, Busybox, Dolby Atmos® Classic (Lenovo_A7000), Youtube Vanced, Tethering Enabler, etc.)
Phone has been rooted with this method before
1. Boot into TWRP recovery (Magisk Manager > Modules > Reboot to Recovery).
2. Restore any boot and recovery images previously created with TWRP (stored on the external storage).
3. Continue with instructions explained in Phone has never been rooted (stock ROM installed).
omino said:
The following process is what I have been successfully doing in the last year to keep my Moto G5 Plus on the most up-to-date stock ROM but rooted with Magisk.
The high level process for OTA update and rooting is different from the case where the phone has never been rooted and where the phone is already rooted with this method.
Requirements
1. Unlocked bootloader (https://forum.xda-developers.com/g5-plus/how-to/unlock-bootloader-lenovo-motorola-moto-t3581133).
2. Fastboot tools installed on a PC (https://forum.xda-developers.com/showthread.php?t=2588979).
3. TWRP recovery for the Moto G5 Plus: twrp-3.2.1-0-potter.img (https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html).
4. TWRP recovery for the Moto G5 Plus: twrp-3.1.1-0-potter-decryptdata.img (https://forum.xda-developers.com/g5-plus/development/unofficial-twrp-3-1-0-0-moto-g5-plus-t3576575).
5. Magisk and Magisk Manager (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
6. Magisk Module - F2FS Loopback Bug Workaround: f2fs-loopback-bug-workaround-2018.1.31 (https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875)
7. Micro SD card installed in the Moto G5 Plus.
Items 3. and 4. may no longer be necessary once the official version of TWRP supports decrypting data on the Moto G5 Plus (https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1153).
Phone has never been rooted (stock ROM installed)
1. Apply any pending OTA update and verify it succeeds
2. Turn off the phone
3. Boot into fastboot mode (volume down + power)
4. Connect the phone to a computer via USB.
5. Boot into TWRP recovery without flashing with the following command (ignore data decryption): fastboot boot twrp-3.2.1-0-potter.img
6. Take a backup of boot and recovery with TWRP (use external storage)
7. Reboot into fastboot mode (Reboot > Bootloader)
8. Connect the phone to a computer via USB
9. Flash TWRP recovery with the following command: fastboot flash recovery twrp-3.1.1-0-potter-decryptdata.img
10. Reboot into recovery
11. Allow TWRP to modify the system partition and prevent the rom from restoring the stock recovery
12. Root the device by installing Magisk using TWRP.
13. Install the f2fs-loopback-bug-workaround-2018.1.31 Magisk module.
14. Reboot into system.
15. Install Magisk Manager and verify Magisk is correctly installed
16. To install extra Magisk modules is recommended to reboot in TWRP (Magisk Manager > Modules > Reboot Recovery) then install the modules from there (for example, Busybox, Dolby Atmos® Classic (Lenovo_A7000), Youtube Vanced, Tethering Enabler, etc.)
Phone has been rooted with this method before
1. Boot into TWRP recovery (Magisk Manager > Modules > Reboot to Recovery).
2. Restore any boot and recovery images previously created with TWRP (stored on the external storage).
3. Continue with instructions explained in Phone has never been rooted (stock ROM installed).
Click to expand...
Click to collapse
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Sure, to be on the safe side, either flash stock ROM then apply all OTA updates as you suggest. Otherwise, one can take a backup of the system partition too. I am not sure why OEM would be modified... but if that is the case, I guess it can be backed up as well.
As a side note, OTA updates from Motorola are downloaded to the following folder: /data/data/com.motorola.ccc.ota/app_download
It is always a good idea to back up the ROM to SD card before applying it, especially for full upgrades (which contain all partitions). That way, it is easy to flash the latest working ROM.
As for the Magisk modules, I had your same experience. It's just my preference to install them through TWRP.
Wolfcity said:
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Wolfcity is right. From my own experience ANY use of TWRP (i.e., booting or flashing) modifies the OEM partition and prevents OTA from succeeding.
Your method does not work. Followed it, backed up right before attempting update in case it failed.... allowed update, it restarted into twrp immediately and then stuck in a twrp bootloop, recovered to backup and I'm still stuck in a boot loop to twrp.
ctwftp said:
Your method does not work. Followed it, backed up right before attempting update in case it failed.... allowed update, it restarted into twrp immediately and then stuck in a twrp bootloop, recovered to backup and I'm still stuck in a boot loop to twrp.
Click to expand...
Click to collapse
You can't update with twrp installed. If you can get into fastboot mode flash full stock rom incl. recovery and boot via fastboot.
Read my previous post.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
You can't update with twrp installed. If you can get into fastboot mode flash full stock rom incl. recovery and boot via fastboot.
Read my previous post.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I see. His method specifically mentions installing TWRP and being able to update, guess he was wrong.
I ended up having to flash twrp and then was able to load my backup. It booted and said update failed and continues to work fine now. So there is no way to install updates with TWRP installed?
ctwftp said:
I see. His method specifically mentions installing TWRP and being able to update, guess he was wrong.
I ended up having to flash twrp and then was able to load my backup. It booted and said update failed and continues to work fine now. So there is no way to install updates with TWRP installed?
Click to expand...
Click to collapse
No. You have to be on untouched stock firmware incl stock recovery to capture OTA.
Sent from my Moto G5 Plus using XDA Labs
Still need to load up both twrps?
Bump:
Just wondering the status, do we still need to load up both twrp to get this going? or is the latest sufficient?
https://dl.twrp.me/potter/twrp-3.2.2-0-potter.img.html
Thanks,
TimelesslyPrecise said:
Bump:
Just wondering the status, do we still need to load up both twrp to get this going? or is the latest sufficient?
https://dl.twrp.me/potter/twrp-3.2.2-0-potter.img.html
Thanks,
Click to expand...
Click to collapse
As the latest official TWRP has the decryption issue fixed it should work. Imo this guide won't work, a complete flash of stock is needed as I wrote before.
Sent from my Moto G5 Plus using XDA Labs
For some reason I could not get a backup of system and boot...
Ended up noticing a few issues with aosp, so flashed to lineage. Pretty smooth so far.
Been out of the game for awile, but it's coming back.
How G5 plus could be rooted.
Here is in details and with all files on one place how to root stock Android Pie for SM-G955F device.
Please if you don't know what are you doing, better avoid this straight forward process because I presume you already knows it.
Also...it will work on ALL Pie firmware versions.
Download on your SDcard all files attached here and...
Rooting process goes as follows.
1. Flash stock firmware G955FXXU4DSBA_G955FOXM4DSBA_DBT and wait for welcome screen on device and reboot in download mode again
2. Flash latest TWRP recovery
3. Enter in TWRP recovery and allow file modifications, then
3a. Format data from recovery...reboot recovery again and repeat procedure from above
4. Install from TWRP no-verity-opt-encrypt-samsung-1.0.zip from link below.
5. Reboot recovery
6. From recovery install Magisk-v18.1(18100).zip
7. Now restart and configure your device as you need.
8. Install latest Magisk app and open app, and within app, install all necessery files
9. Now you are rooted
Install Viper4android
To prepare before, please with Root explorer app rename file audio_effects.conf in audio_effects.conf.BAK, located in folder Vendor/etc
1. Install latest busybox
2. Install ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk from here
3. Reboot device and go into TWRP
3a. Install FUSION KERNEL from link below ( one of the fastest kernels I have ever seen)
4. Install Viper drivers as usuall
5. Reboot device
Viper4android is installed.
In Settings check in Sound and vibrations menu if Viper is your default sound module, if not, select it.
.
THANK YOU NOTE GOES TO ALL DEVELOPERS WHO BLESSED US WITH THEIR WORKS !
.
MAGISK
https://www.xda-developers.com/how-to-install-magisk/
FUSION KERNEL with permissive mode
https://www.leorom.cc/index.php/fusion.html?t=1553420049699
TWRP S8+
https://forum.xda-developers.com/galaxy-s8+/development/recovery-twrp-galaxy-s8-exynos-t3594756
VIPER4ANDROID
https://forum.xda-developers.com/showthread.php?t=2191223
I do not take any responsibility for possible errors or damaged devices caused by lack of someones knowledge.
.
Does anyone tryed it?
Will try tomorrow!
Thanks!
Just followed your steps and my phone is rooted now!
keunhuvac said:
Just followed your steps and my phone is rooted now!
Click to expand...
Click to collapse
Excellent !
Btw, i use viper module in magisk manager and it works fine!
keunhuvac said:
Btw, i use viper module in magisk manager and it works fine!
Click to expand...
Click to collapse
Same here, works fine with Magisk Module ?
keunhuvac said:
Btw, i use viper module in magisk manager and it works fine!
Click to expand...
Click to collapse
Thank you for that info. I didn't tryed module rather then install standalone app. Anyway, good to work on both ways.
tin2404 said:
Here is in details and with all files on one place how to root stock Android Pie for SM-G955F device.
Please if you don't know what are you doing, better avoid this straight forward process because I presume you already knows it.
Also...it will work on ALL Pie firmware versions.
Download on your SDcard all files attached here and...
Rooting process goes as follows.
1. Flash stock firmware G955FXXU4DSBA_G955FOXM4DSBA_DBT and wait for welcome screen on device and reboot in download mode again
2. Flash latest TWRP recovery
3. Enter in TWRP recovery and allow file modifications, then
3a. Format data from recovery...reboot recovery again and repeat procedure from above
4. Install from TWRP no-verity-opt-encrypt-samsung-1.0.zip from link below.
5. Reboot recovery
6. From recovery install Magisk-v18.1(18100).zip
7. Now restart and configure your device as you need.
8. Install latest Magisk app and open app, and within app, install all necessery files
9. Now you are rooted
Install Viper4android
To prepare before, please with Root explorer app rename file audio_effects.conf in audio_effects.conf.BAK, located in folder Vendor/etc
1. Install latest busybox
2. Install ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk from here
3. Reboot device and go into TWRP
3a. Install RZ KERNEL PIE from here
4. Install Viper drivers as usuall
5. Reboot device
Viper4android is installed.
In Settings check in Sound and vibrations menu if Viper is your default sound module, if not, select it.
.
THANK YOU NOTE GOES TO ALL DEVELOPERS WHO BLESSED US WITH THEIR WORKS !
.
MAGISK
https://www.xda-developers.com/how-to-install-magisk/
RZ KERNEL with permissive mode
https://forum.xda-developers.com/ga...t/kernel-rz-kernel-samsung-galaxy-s8-t3893139
TWRP S8+
https://forum.xda-developers.com/galaxy-s8+/development/recovery-twrp-galaxy-s8-exynos-t3594756
VIPER4ANDROID
https://forum.xda-developers.com/showthread.php?t=2191223
I do not take any responsibility for possible errors or damaged devices caused by lack of someones knowledge.
.
Click to expand...
Click to collapse
what about OEM unlock, I must turn on??
jackherer72 said:
what about OEM unlock, I must turn on??
Click to expand...
Click to collapse
https://forum.xda-developers.com/sitesearch.php?q=oem unlock
Hello, you have solution for root samsung s8 + g9550zhu4dSg2 ?