Hope this helps.
1. Install android sdk and use the included install manager in the sdk to install the latest google usb drivers and platform tools (platform tools include fastboot and adb). Make sure adb and fastboot directory is in your Path variable as well.
2.Download latest stock image for Nexus 9 from google: https://developers.google.com/android/nexus/images?hl=en
3.Download latest twrp (here is the latest right now 10/6/2015): http://forum.xda-developers.com/nex...recovery-twrp-2-8-2-0-touch-recovery-t2944788
4.Download either a stock boot image with the no- forceencrypt flag set or a kernel with the no-forceencrypt flag set
a.I use the elementalx kernel (10/6/2015): http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657
b.A stock kernel for the MRA58K build with the no-forceencrypt flag set can be found here (boot.zip): http://forum.xda-developers.com/nexus-9/general/marshmallow-factory-images-available-t3218290/page3
5.Download the latest supersu that works with nexus (beta now) : http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
6.Make sure you have usb debugging enabled and ability to unlock bootloader (android developer options menu on nexus).
7.Unzip the 6.0 stock image into a folder and open a command window in the folder.
8.Type the following:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot oem unlock
c.flash-all, now wait a few minutes while the stock image flashes
9.At this point your nexus will reboot. Once you’re started, up you need to again enable usb debugging and the ability to unlock your bootloader in the android developer options menu. Now type the following to flash TWRP:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot flash recovery twrp.img (or whatever the image filename is from the twrp download).
10.Important: now make sure you boot DIRECTLY into TWRP via the button combination (power and volume down), a fastboot command, or the fastboot menu. If you don’t TWRP will be deleted and you’ll need to reflash using the last step.
11.Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
12.Now type adb push supersufile.zip /sdcard/supersufile.zip, make sure you’re typing from the correct directory.
13.Install supersu via the install menu on TWRP.
14.You now need to install a kernel with the no-forceencrypt flag set:
a.If you want to install a custom kernel (like elementalx), type adb push elementalxfile.zip /sdcard/elementalxfile.zip, make sure you’re typing from the correct directory. Then use TWRP to install the zip from your sdcard.
b.If you want to install the modified stock boot.img then unzip the boot.zip, boot back into the bootloader and type: fastboot flash boot boot.img. Make sure you do NOT boot back into the android OS before doing this step or you'll have to reflash twrp.
Reboot and you’re good to go.
Didnt work for me.
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
typo
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Fda979 said:
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Click to expand...
Click to collapse
Fixed. Thanks.
Sent from my Nexus 9 using Tapatalk
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
I flashed the latest supersu and the latest elementalx kernel.... been running it since about an hour after elementalx kernel for 6.0 final was posted....... everything seems to be working fine. Are you sure? Maybe i'm having no problems with supersu because i'm using elementalx? let me know the reason, i'll check it out on my tablet and see if i can reproduce, and if so i'll modify the guide. But after about a day and a half use, i've had no issues. thx for quality checking.
gt
Am I missing something?
can I not just do a wipe and flash the img with twrp like a custom rom? Edit: Got it working. For me it was much easier to use this as opposed to the android sdk, because it would not detect my version of java. From there I followed your instructions, mostly. Putting the files you posted inside the directory the mini adb client allowed the flash-all command to work. From there I followed chainfire's instructions on the latest SU. Everything seems to be running smoothly. Thanks for the initiative, OP :good:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
dkryder said:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
Click to expand...
Click to collapse
Of course update binaries. Choose normal method.
Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
I was facing same issue, then updated fastboot(android-sdk) and flash-all script worked fine for me.
That should work as well. That sequence of commands should work with any fastboot version. Just make sure to flash the vendor.img, some scripts don't use that as it's only used for the Nexus 9.
Why so complicated? I just installed @wug's NRT toolkit(on a Venue8 pro) and it did everything for me. Now im on rooted stock 6.0 with disabled encryption. Only thing i needed to do is to flash latest super su beta 2.52, that's it.
Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
i did all this, no worries and no error messages
i did fastboot reboot
now I am in a weird loop of
- google screen
- your device is corrupt
- google screen
- twrp (it flashes quite quickly, error messages on mounting everything and last line says something about renaming and something about stock rom)
loop
any ideas ?
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Verttex said:
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Click to expand...
Click to collapse
yes, that seems to have been it
flashing TWRP seems to have been the problem so I have left everything as stock until root etc works on the stovk kernel
thanks for your help
Nice guide.
I install Busybox from Play, I assume that's needed? Everyone else doing this?
- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
added link to the latest beta supersu. thx.
All of these steps worked for me, but my battery doesn't charge right I don't think. It says battery life is at 3,745%. It runs out somewhere around 3,000%. Any ideas on how to fix that?
Alright so I went to dirty flash a new ROM update but TWRP errored out so I was unable to. I went to update TWRP (I was 2 versions out of date) and it flashed without a problem. However now I can no longer boot into recovery or quickboot but my ROM loads just fine. What the hell is going on?
I actually did NOT correctly flash TWRP. I am still on the older version and still cannot boot into it
flash twrp from fastboot.
1) reboot into bootloader
2) open a terminal inside the folder where you downloaded the recovery .img file
3) type into terminal: fastboot flash recovery recoveryfilename.img
4) reboot into recovery holding power and vol -
I cannot boot into fastboot or the bootloader.
Fixed by flashing older version of TWRP with the app inside of android.
I was flashing TWRP
I couldn't boot into system after flashing..
This is what I did:
1. fastboot boot recovery.img
2. Swipe to allow modifications in twrp
3. Flash TWRP installer zip
4. Reboot into partition B
5. Reboot bootloader
6. fastboot boot recovery.img
7. Swipe to allow modifications in twrp
8. Flash TWRP installer zip
9. Then I rebooted into recovery to check if recovery boots and it did.
But afterwards couldn't boot back into system. It was again booting into recovery.
I booted into recovery using fastboot boot, that's why it might won't boot into system. Is there a command to boot into system after above procedure?
Files used: https://m.youtube.com/watch?v=tRcYUMBgvaI
? How to Root Mi A1! Unlock Bootloader, TWRP Recovery ... - YouTube
By Dhananjay Bhosale
Kindly also suggest source of files you used, if you know another working method.
I have the same problem. Meanwhile, flash the stock fastboot images.
Why do you want to have TWRP installed? I am following these steps each month (fastboot ROM was always out sooner than my OTA) without any issues.
1. flash stock ROM via fastboot
2. fastboot boot twrp-3.1.1.img and don't allow system modifications or you won't be able to apply OTA
3. install magisk 15.1
4. reboot to system
If first boot takes more than 2-3 minutes, hold power off button until phones restarts, second start will take the usual time.
I also don't allow any modifications from TWRP, and just boot to TWRP when I need to. I do not install TWRP.
Sounds like you'll have to do a miflash of the rom, then try not installing TWRP and not allowing any modifications in TWRP to system. Just use TWRP to flash Magisk.
Here we go !
TWRP Official for MOTO E 4 mediatek version
Disable dm verity.zip to avoid bootloop to disable verified boot
Stock Recovery in case you lost it somewhere during flashing other recovery that is corrupted or unstable or interrupted process resulting bricked device
To flash boot use : booting to fastboot mode
Enter fastboot devices to confirm adb connection
Now copy file to same adb folder all files
Use code : fastboot flash recovery ***filename***.img
Now with TWRP Official you can flash zip for
Magisk or Super Su pro
Stock boot image flash using flashify to use boot here https://forum.xda-developers.com/attachment.php?attachmentid=4360095&d=1513222799
:good:
So I let the latest OOS open beta 8 auto install via OTA. After the reboot, I lost twrp and magisk, so I went back to fastboot and wanted to boot into twrp, but I used the wrong command
Code:
sudo fastboot flash boot twrp-fajita-3.3.0-2.img
The word "flash" should not have been there! So this command overwrote boot_a. So I switched to slot B, and wanted to boot into twrp, but STUPIDLY used the same wrong command again!!
Now I can't seem to boot into system at all, and am stuck at recovery. I've tried a bunch of things, including flashing both boot_a and boot_b with a boot.img extracted from the open beta 7 via SuperR's Kitchen, but I'm still left in this state where if I fastboot boot twrp-fajita-3.3.0-2.img in order to flash the open beta 7 zip, it reboots only to oneplus recovery.
If I fastboot boot twrp-fajita-3.3.0-2.img in order to flash the open beta 7 zip, followed by the twrp zip, and with or without magisk, a reboot brings me back to TWRP, but where it does not ask for my encryption password and hence all my filenames show up as encrypted. Only if I fastboot boot twrp, then it gives me the option to type in my password and successfully decrypts the files.
Any idea how I can fix this?
SOLUTION: I think it was because I was trying to flash back open beta 7 after installing open beta 8 OTA. So after I found the download zip for open beta 8, I extracted the boot.img, flashed the boot.img to boot, flashed open beta 8 zip, and I could reboot and get into system. Phew!
Try flashing the latest Stock ROM via TWRP.
Yeah, like he said. Download the OB8 and flash it via TWRP.