All,
I'm coming from a nexus environment where I've been able to do fastboot boot twrp-2.6.3.1-ghost-4.4.img rather than fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img since I'm hoping to keep the stock recovery while installing supersu. It complains about "(bootloader) Command restricted" with the MotoX even though my bootloader is unlocked. Is this typical of Moto devices? Do I actually need to flash twrp, then supersu and then the stock recovery if that's the final result I want? FWIW, I want SU on it but I'd like to also receive future OTA updates w/o too much dorking around of at all possible.
thanks peterb
Are you using mfastboot or just regular fastboot?
I fastboot twrp no problem. I did however mfastboot the system.img . But to answer your question twrp will ask you if you want to root when you go to reboot.
Fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img is the command, when you flash do not reboot the device to the system but boot into recovery instead, you should be good to go and twrp should ask if you wish to root, if not just download the flashable supersu zip
Sent on my Moto X
I understand that you should flash if you want to have TWRP installed on your phone but that's not what I want. I'd like to just boot into TWRP, install the SuperSU.zip and then boot back up as normal leaving the stock recovery in place so that I will continue to get OTA updates. I get that this is likely not the norm but it's what I did with my N4 to get SuperSu so that I could update boot.prop for flashing a hybrid radio. Doing this made it easier to get the phone back to OTA ready w/o having to flash the stock recovery back.
I found a couple of posts in the N4 where the fastboot command failed and you needed to start using the "-c" command. I was wondering if this was the problem I was running into. The argument for -c is a bit cryptic so I worry that the one I found is likely N4 specific:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Basically what I'm wondering is if anyone has been able to just boot into TWRP w/o actually flashing it to the recovery partition.
If this is not possible then I'll flash TWRP, root and then flash the stock recovery back on since I did get the stock 4.4 image from Motorola.
thanks peterb
flashallthetime said:
Fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img is the command, when you flash do not reboot the device to the system but boot into recovery instead, you should be good to go and twrp should ask if you wish to root, if not just download the flashable supersu zip
Sent on my Moto X
Click to expand...
Click to collapse
Interested in this as well, for booting kernels. Device support has been hit-or-miss for me in the past.
And folks, he's asking about fastboot's ability to launch an image _without_ flashing. This is a somewhat esoteric/advanced use.
I'm interested in this too even though I have a locked Moto X.
I didn't know this was possible, huh. As for our device, it'll probably help if we can figure out what that -c command means.
Sent from my Moto-X (GSM DE) using the xda-developers app
thehockeydude44 said:
I didn't know this was possible, huh. As for our device, it'll probably help if we can figure out what that -c command means.
Sent from my Moto-X (GSM DE) using the xda-developers app
Click to expand...
Click to collapse
If I'm remembering right, google took the ability to boot a recovery without loading one away in 4.2. We tried to do this on the HTC 1 Google edition when we pulled its partitions to make a system dump. It failed.
OTA fails when the device is rooted, even if you have the stock recovery.
The OTA zip checks the system partition. If there is any single modification, it fails.
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Yea, this is the other way to do it. It's just a bummer if one can't use the flexibility to just boot into recovery. Note that I still seem to be able to boot into custom recovery on my Nexus 4 that's running KitKat. I'm curious about the comment about not getting an OTA with su installed. I know that with a modified build.prop and radio, the N4 wouldn't update but I could adb sideload successfully once I put build.prop back and the stock radio on. I figured the OTA would just unroot and then I'd have to do the process again.
Anyway, this was my plan B, just would have preferred to boot recovery.
peterb
waiflih said:
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Click to expand...
Click to collapse
if u want to "unroot" to take otas, u can just flash stock system
waiflih said:
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Click to expand...
Click to collapse
I am interested in this as well. How do we get a copy of the stock recovery to reflash?
Also, I have had rooted stock and custom recoveries and have received OTA's before (but they were on Nexus devices).
droiddog said:
I am interested in this as well. How do we get a copy of the stock recovery to reflash?
Also, I have had rooted stock and custom recoveries and have received OTA's before (but they were on Nexus devices).
Click to expand...
Click to collapse
you can take it from the the file used in rsdlite, according to you fw version
The only reason I want the stock recovery is because I think you can't remotely lock or erase your device on a custom recovery. Does anyone know anything to the contrary? Thanks.
So I have a T-mo rooted Nexus 6 running stock rom and kernel presently. I would like to decrypt the phone as I've heard/read I will see an improvement in both performance and battery life. So first question is what would be the best/easiest method to do this and second will I lose root and have to re-root after decrypting. Thanks in advance for any help.
Basically you will have to flash a different boot image that disable the encryption flag.
This will require you to completely wipe your device and start over. Yes, you would have to re-root but if you know how to flash a stock no-encrypt image then rooting is easy and simply requires you to flash the current SuperSU zip from recovery once you are all set up.
Basically follow the long version of this guide. Technically you don't need to flash completely stock and couold just follow the guide in the next section but if you have to factory reset anyway I would want to start fresh:http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
But use this no-encrypt boot image instead that matches the stock google rom you flash:http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Once that is done you can flash recovery (or simply boot into TWRP temporarily if you want to keep the stock recovery) and flash Supersu.zip from here and then you're rooted again. I think you could also flash TWRP in the first step above when you are going back to stock but I usually do it at the end for some reason:http://forum.xda-developers.com/showthread.php?t=1538053
Thank you so much
To start: 5.1.1 (LMY48M), rooted, with TWRP for recovery
For every 5.x update so far, this has been my procedure using fastboot:
Flash boot.img
Flash radio.img
Flash system.img
After successfully updated, I'd use WugFresh's Nexus toolkit to root and flash TWRP.
I'm a fan of not needing to flash userdata.img, as I don't think that should be necessary given that the OTA wouldn't wipe installed apps and such.
I've read other threads about using fastboot to upgrade and am concerned about the boot warnings, which seem to require a custom kernel to circumvent. My question is: will the above approach still work? Do I need to flash any other files? If I need to flash a custom kernel, where do I get it, how do I flash it (is it just a custom boot.img?), and at which point in the flash sequence should I apply it?
Secondly, has anyone tried gaining root through the Nexus toolkit once upgraded to 6.0?
I'm looking for recommendations so I don't spend hours trying to unbrick my device. Thanks!
You'll also want to flash the 6.0 bootloader and why are you using the toolkit to flash twrp when you can flash it in fastboot along with the rest of the files?
Ah OK, I'll flash the bootloader image as well. Anything else to be concerned with? The toolkit has a feature to root + flash twrp as a feature, so I just use that.
Do the bootloader first, then reboot the bootloader before you flash anything else. There are instructions floating around here some where or you can google nexus 6 flash factory images. You don't have to flash user data as this will format all you data/ apps.
Just download the latest SuperSu zip (2.50) and put it on your SDcard. If you flash as you suggested and then boot directly into recovery, you will still have TWRP. If you don't flash the stock recovery.img to replace TWRP, it will replace on first boot anyway, unless you root imeediately, but you are probably booting to use the toolkit, which replaces recovery only to have to use the toolkit to flash recovery anwyay.
So do your flashes, boot straight into recovery, flash the supersu zip on your sdcard. Done.
Hi Nexus 6 Community
Im new to own a Nexus 6 but Im an "enthusiastic flasher" per say. I've being looking around with no luck so I was hopping someone will point me to the right direction:
Usually whenever I flash anything on my previous phones I like to flash TWRP again in case of boot loops or something flashing bad that could delete or corrupt my custom recovery. I'm rooted and installed the latest TWRP through fastboot, but as I previously said, I would like to have a flashable zip to ensure my recovery will be installed and have a higher chance of not being locked out of my phone.
Or I'd notice you can flash images through TWRP, will this re-install my recovery using the TWRP .img file?
I really appreciate all for your help, thanks
Once you boot into twrp for the first time it patches /system to prevent the stock rom from replacing it unless you choose the "keep system mounted as read-only." This option is only offered to you if you boot into twrp with an untouched /system. And as for worrying about being locked out of your phone, as long as you have an unlocked bootloader you can always use a google factory image to get back to stock w/o a custom recovery.
I'd assume no one's made a flashable zip for twrp because reflashing it wouldn't accomplish much of anything if you already have twrp to flash it in.
Is there a guide to installing a custom recovery and ROM to the XT1096 now after the official bootloader unlock? I just did it and wanna play around with new ROMs now.
Before you do anything with your phone, download and keep the stock firmware for it, in case something goes wrong, or you lose signal:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
I guess there's only stock 5.1 for the XT1096 (Verizon?).
You will also need ADB and Fastboot to flash custom recovery or stock firmware.
The Moto X 2014 is called Victara, this is the TWRP custom recovery for it:
https://dl.twrp.me/victara/
You flash it in Bootloader Mode, using Fastboot, like this:
fastboot flash recovery twrp-3.0.0-0-victara.img
(This is just an example, you might want to flash a different version, or recovery)
Then you boot into recovery immediately after flashing it, so it doesn't get overwritten by the stock firmware.
Then you can copy the ROM and Gapps zip files to the phone, and flash them by tapping Install in TWRP.