Database Users

[Simplified] [Root Method] [Titan] [Marshmallow 6.0] Without Modifying boot.img

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?

Phone reboots by TWRP / ADB flashing and modifying

SM-A310F (Galaxy A3 2016) is rooted and runs currently with 6.0.1
My phone will reboot everytime if i trying to flash my created custom rom and / or trying to delete some files by adb over shell (from system). Same happed with 5.1.1
Phone is correctly rooted and latest TWRP is installed. Backup/Restore works perfectly but no flashing files which contains system files. Can someone help. I want to test my custom rom before deploying to XDA
Any help is much appreciated.
JX

Jerome-X said:
SM-A310F (Galaxy A3 2016) is rooted and runs currently with 6.0.1
My phone will reboot everytime if i trying to flash my created custom rom and / or trying to delete some files by adb over shell (from system). Same happed with 5.1.1
Phone is correctly rooted and latest TWRP is installed. Backup/Restore works perfectly but no flashing files which contains system files. Can someone help. I want to test my custom rom before deploying to XDA
Any help is much appreciated.
JX
Click to expand...
Click to collapse
i have same problem. did you solve?"

not at all. Trying to find a solution. I think an other root method is needed, cause you can't modify system in /
Switching back to 5.1.1

vipersinu2 said:
i have same problem. did you solve?"
Click to expand...
Click to collapse
Problems are solved. If you had installed 6.0.1 by default, use the latest TWRP via Odin, after that, whithout rooting first.
Boot into TWRP, flash latest Update-SuperSU, reboot. You are able to delete Systemfiles without reboot, also activate Adaware.
JX

How to root my SM-A500M Android 6.0.1?

Hi!
I've just updated my android from 5.0.2 to 6.0.1 using a firmware from sammobile and lost the root I had previously (super user).
I tried installing from cf-root using the version they already have for 5.0.2 and at first it seemed to have worked, since it started to show my phone device's status as custom, and also to show kernel's status at the black start screen with the logo samsung.
Then, I tried changing an app into a system file using Link2SD and the app vanished instead of working again. When I get to install the .apk again, it shows as an update (of something that is not running anywhere) and don't ask any new permission.
I guess the problem is because of the root I used, but I'm not sure. My mobile is dual sim (brazil's trend...) and the app I'm trying to hide is Cerberus (I have the pro version, disguised, but want to make it "blended" as it was before the Android update).
I did the unroot with the SU app, but my device is still showing as a "custom" one at the system's about (the kernel's status is not appearing at initialization tho).
I want to know what to do to fix that and how to properly root the new android marshmallow. If not possible, I even consider downgrading my phone to the previous android until the root is available (security from thieves first, unfortunately!).

Same Here
Doen anyone know if there is other variant rom we can use in a500M

Wait for CF-AutoRoot
Some A5 variants have received the root file for Android 6.0.1 Marshmallow
CF-AutoRoot: https : // autoroot.chainfire. eu/

nicolaycarlos said:
Same Here
Doen anyone know if there is other variant rom we can use in a500M
Click to expand...
Click to collapse
I use the 5.0.2 root version in marshmallow and it's working fine for me with xposed and everything else

ToDream said:
Some A5 variants have received the root file for Android 6.0.1 Marshmallow
CF-AutoRoot: https : // autoroot.chainfire. eu/
Click to expand...
Click to collapse
Not the A500M, yet.

Option 1: Flash CTR o TWRP with Odin. Then, flash SuperSU.zip from recovery.
Option 2: Flash CF-AutoRoot (Lollipop version) with Odin.
PS: If you want more options antitheft, you can use Xposed and GravityBox or Advanced Power Menu modules to disable the Power-Off menu when the screen is locked.
Good Luck

So I can use your "Option 1" to root my device with 6.0.1 even if it's a 5.0.2 method? (I just want to make sure to not brick my phone).

{HELP} How To Root Samsung J500H With Lastest Android version 6.0.1

Can Anyone Tell me how to Root J500H 2015 3G 8GB latest Marshmellow 6.0.1 Installed Any Way to Root this Phone??

Humayun Butt said:
Can Anyone Tell me how to Root J500H 3G 8GB latest Marshmellow 6.0.1 Installed Any Way to Root this Phone??
Click to expand...
Click to collapse
Cf auto root perhaps

Not Working Any Method
SpamMachine said:
Cf auto root perhaps
Click to expand...
Click to collapse

Hi! One way is to use custom recovery to root your Galaxy J5. To root with custom recovery you will need a computer running Windows OS (didn't work with Linux distros using Wine) and download Odin from samsungodin.com. Then you will need a TWRP-recovery, the link is here:
https://eu.dl.twrp.me/j53gxx/twrp-3.1.1-1-j53gxx.img.tar.html
In Odin, click on the AP button and select your downloaded recovery file, boot your phone to download mode (Pwr+VolumeDown+Home), connect your phone with computer and start the installation process. It will usually take less than five seconds.
Once you installed the recovery, you will be able to easily root your phone. I recommend SuperSU as your SuperUser app. The link to official SuperSU is below:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Boot into recovery (Pwr+VolumeUp+Home) and install SuperSU and that's it, your phone should now be rooted. If you consider any problems, feel free to ask for more help!
Regards,
Patrik.

[GUIDE] How to get Magisk Root & Xposed on Oreo 8.0 (STOCK)

I'M NOT RESPONSIBLE IF YOUR DEVICE BRICKS, SD CARD DAMAGES OR NUCLEAR WAR STARTS.
Rooting method described below will work on Oreo-running devices ONLY (confirmed on build OPN27.76-12-22 and on OPNS27.76-12-22-9).
Please follow all steps very carefully and make sure you downloaded correct versions of all .zip files mentioned in my instruction!
ROOT (SafetyNet test will PASS!)
1. Download all files listed below:
- twrp-3.2.3-0-addison.img (CLICK)
- Magisk-v17.1.zip or newer if availabe (CLICK)
- f2fsfix-2018.9.2.zip (CLICK)
2. Flash TWRP using Fastboot:
Code:
fastboot flash recovery twrp-3.2.3-0-addison.img
3. Flash Magisk-v17.1.zip (or newer if available).
4. Go to TWRP/Settings and open Terminal.
5. Run both of following commands:
Code:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
6. Flash f2fsfix-2018.9.2.zip
7. Reboot (it is crucial in case of installing Xposed afterwards).
8. Optional but recommended: update your Magisk Manager to the latest version (CLICK).
9. Open Magisk -> Modules and update f2fs-loopback-bug-workaround module to the newest version (can be done only via Magisk Manager only if new version of f2fs-loopback-bug-workaround module is available).
10. Enjoy rooted Oreo.
UPDATE 03.10.2018
If you flashed everything as described in OP and noticed that you got stuck in boot, go to TWRP again and:
1. Uninstall Magisk using latest Magisk uninstaller.
2. Flash Magisk 17.1.zip AGAIN (yes.).
3. Flash f2fsfix-2018.9.2.zip
4. Enjoy rooted phone.
PS. I do not know why device does not start after first flashing to be honest, but these four steps above are confirmed by several users (and by me).
UPDATE 03.10.2018
XPOSED (be careful: Xposed for Oreo is still in BETA distribution and flashing it will break your SafetyNet!)
1. Open Magisk Manager -> Downloads.
2. Download Xposed Installer (the one from the screen below):
https://image.ibb.co/byLUuK/Xposed_Framework.png
3. Let Magisk install it.
4. Reboot.
5. Open Xposed Installer (you will see orange exclamation mark, don't worry).
6. Reboot once again.
7. Voila.
Hit THANKS if I helped!
Credits:
- @topjohnwu
- @rovo89
- @Artim_96
- @VR25

@rafikowy ah, so basically the problem was with dm-verity and forced encryption? That makes sense. So it would basically also work if you'd not extract the boot.img from the OTA zip and mod it with Magisk manager with both enabled and flash that (might be easier than flashing normal Magisk and then make the changes), so you'd basically just flash the img and the module zip in TWRP.
Well, if no bigger bugs appear I might try the Oreo OTA and root tomorrow. Don't think it will be here on its own till then, even if it's already the official rollout (Indian and brasilian users seem to get it officially)

First magisk manager did not want to open, but a reboot solved. thanks

So, Lenovorola is still "undecided" in regards to patching F2FS.
I wonder why...

Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?

Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
Only a Soak test is available, the link is in the thread in the ROM section. And yes, it doesn't seem to update your bootloader, it was already successfully testet to go back to 7.1.1

Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
Look at
https://forum.xda-developers.com/mo...se-attempt-t3812530/post76991120#post76991120

not work - moto z play - oreo soak
Unfortunately it does not work. : (TWRP prompts for a PIN to decrypt data.) How to select cancel and install Magisk on installation f2fs-loopback-bug-workaround-2018.1.31.zip displays an error that does not detect magisk or is incompatible. How do I format the date everything is installed but the phone does not turn on... Any idea?

Sorry but, if verity is enabled, that means you are unable to modify /system files?

Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
You can go back, problem is you will lose IMEI by going back to Nougat.

huma_dawii said:
You can go back, problem is you will lose IMEI by going back to Nougat.
Click to expand...
Click to collapse
I gone back to 7.1.1 Nov patch and everything is OK with my IMEI. Just flash 7.1.1 Plus ROM with TWRP. One issue what I have - In can't mount OEM partition in TWRP.

Could someone provide a TWRP backup of the 8.0 Soak? I've modified the system partition and this method stoped working. All the 8.1 roms have a so bugged camera, I don't wanna go back to them

Camarda said:
Could someone provide a TWRP backup of the 8.0 Soak? I've modified the system partition and this method stoped working. All the 8.1 roms have a so bugged camera, I don't wanna go back to them
Click to expand...
Click to collapse
Here are system and boot from 8.0 soak test. Just unrar it adn put to TWRP folder with your backups.

St.Noigel said:
Here are system and boot from 8.0 soak test. Just unrar it adn put to TWRP folder with your backups.
Click to expand...
Click to collapse
I've restored the backup, but I'm still unable to boot with magisk. Don't know what is wrong now

Camarda said:
I've restored the backup, but I'm still unable to boot with magisk. Don't know what is wrong now
Click to expand...
Click to collapse
1. Restore backup
2. Flash Magisk 15.3
3. Flash this https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
4. Flash this https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
5. Go to the terminal in TWRP and run two commands:
- mm
- f
Reboot.
That's all. You don't need to run commands from OP.
IF I help you - you can buy me a beer )))))

Can i go back to 7.1.1 and relock bootloader ??
Hi,
Can anyone help me, i have updated to Oreo (Soak Update) and now i wanna go back to Nougat 7.1.1 NPNS26.118-22-2-12 and re-lock bootloader, is it possible ?? if yes guide me
thanks in advance

LovinVEVO said:
Hi,
Can anyone help me, i have updated to Oreo (Soak Update) and now i wanna go back to Nougat 7.1.1 NPNS26.118-22-2-12 and re-lock bootloader, is it possible ?? if yes guide me
thanks in advance
Click to expand...
Click to collapse
Nope. It's impossible for now. You can`t go back to full stock, because you'll lose your IMEI with flashing full 7.1.1 FW with RSD or fastboot.

St.Noigel said:
1. Restore backup
2. Flash Magisk 15.3
3. Flash this https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
4. Flash this https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
5. Go to the terminal in TWRP and run two commands:
- mm
- f
Reboot.
That's all. You don't need to run commands from OP.
IF I help you - you can buy me a beer )))))
Click to expand...
Click to collapse
Did everything, but still stuck at bootanimation. Only boots if I unninstall magisk.

Camarda said:
Did everything, but still stuck at bootanimation. Only boots if I unninstall magisk.
Click to expand...
Click to collapse
If you have bootanimation - just wait few minutes

St.Noigel said:
If you have bootanimation - just wait few minutes
Click to expand...
Click to collapse
Just waited for 30 minutes. It wont boot