Just took delivery and trying to root. Using nexus root kit successful at unlocking. But will not unencrypt or root. Being denied copying files from PC to device Also can not flash/recover to any other boot img. Is there anyway to revert back to an unencrypted image? Stock build came as LMY47D but it updated to the 5.1.1 yesterday. Also is there any known issues using windows 10 to run the toolkit?
Have you tried just doing everything the proper way following our guides?
i.e using fastboot to flash stock images, and TWRP recovery. Then use recovery to flash a kernel that doesn't force encryption. Then format userdata from recovery.
It's very easy
yeah, I hate to be that guy, but you really should avoid the toolkit and learn some very basic fastboot and adb commands.
Once you have these at your disposal, you can pretty much unbork anything on a nexus.
Related
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.
I have read so much and information seems contradictory. One thing says if you root and take custom recovery you will never be able to update your phone via OTA. But I have been updating with fastboot so is updating like that still possible? And I understand you can get back to stock to take an OTA anyway. Is that correct?
It has been said that you cannot decrypt your N6 after taking 5.xx? (can't remember which) OTA. Is it not possible to decrypt with fastboot or adb after that particular update? If I just take all the OTA's before flashing twrp and rooting will I still be able to decrypt at the 5.1.1 version if I want to? And, there are custom kernels that allow things that the stock one won't allow. Currently using a 2013 Moto X rooted and twrp on 5.1. I've been updating by flashing stock recovery and system.img from sbf files and then taking the OTA successfully. Will the N6 still work that way?
Groid said:
I have read so much and information seems contradictory. One thing says if you root and take custom recovery you will never be able to update your phone via OTA. But I have been updating with fastboot so is updating like that still possible? And I understand you can get back to stock to take an OTA anyway. Is that correct?
It has been said that you cannot decrypt your N6 after taking 5.xx? (can't remember which) OTA. Is it not possible to decrypt with fastboot or adb after that particular update? If I just take all the OTA's before flashing twrp and rooting will I still be able to decrypt at the 5.1.1 version if I want to? And, there are custom kernels that allow things that the stock one won't allow. Currently using a 2013 Moto X rooted and twrp on 5.1. I've been updating by flashing stock recovery and system.img from sbf files and then taking the OTA successfully. Will the N6 still work that way?
Click to expand...
Click to collapse
OTA checks system and kernel and if anything is changed, OTA will fail. That includes root.
Fastboot flashing a system.img, boot.img and recovery.img would be enough to unroot and get back to stock however, you would only want to OTA if the rom you wanted didn't have a factory image.
Decryption is possible on all ROMs. It's just a custom kernel (boot.img) that doesn't force encryption on boot, then format userdata to get rid of existing encryption. Of course you're modified now so no OTA.
People care so pointlessly about OTA. Advice: forget about it and fastboot flash to update, or easier yet, wait for someone to package it up into a recovery flashable zip
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.
Just had a problem after using root toolkit to attempt root on nexus 6 with marshmellow. (6.0 ), build MRA58R. After this attempt, got the message that" device is corrupted" and would not boot into system. Luckily bootloader was still unlocked and was able to flash stock image. Phone boots fine now with Boatloader unlcocked, and TWRP is gone, with no root. How do I root from here and install TWRP again without going through what happened before.
In the beginners guide to root, Chanifire's link hasn't been working and I want to be sure I do this right to avoid what happened with the toolkit. Also, my phone is setup with apps and data, and I dont't want to loose my setup.
Thanks for your help.
ccf60 said:
Just had a problem after using root toolkit to attempt root on nexus 6 with marshmellow. (6.0 ), build MRA58R. After this attempt, got the message that" device is corrupted" and would not boot into system. Luckily bootloader was still unlocked and was able to flash stock image. Phone boots fine now with Boatloader unlcocked, and TWRP is gone, with no root. How do I root from here and install TWRP again without going through what happened before.
In the beginners guide to root, Chanifire's link hasn't been working and I want to be sure I do this right to avoid what happened with the toolkit. Also, my phone is setup with apps and data, and I dont't want to loose my setup.
Thanks for your help.
Click to expand...
Click to collapse
rooting marshmallow..
1. unlock the bootloader(yours is there already)
2. fastboot flash twrp recovery.
3. flash the latest supersu in twrp recovery
4. flash a custom marshmallow kernel, any. this ones new for marshmallow, and is needed.
5. boot up.
simms22 said:
rooting marshmallow..
1. unlock the bootloader(yours is there already)
2. fastboot flash twrp recovery.
3. flash the latest supersu in twrp recovery
4. flash a custom marshmallow kernel, any. this ones new for marshmallow, and is needed.
5. boot up.
Click to expand...
Click to collapse
Thank you.
ccf60 said:
Just had a problem after using root toolkit to attempt root on nexus 6 with marshmellow. (6.0 ), build MRA58R. After this attempt, got the message that" device is corrupted" and would not boot into system. Luckily bootloader was still unlocked and was able to flash stock image. Phone boots fine now with Boatloader unlcocked, and TWRP is gone, with no root. How do I root from here and install TWRP again without going through what happened before.
In the beginners guide to root, Chanifire's link hasn't been working and I want to be sure I do this right to avoid what happened with the toolkit. Also, my phone is setup with apps and data, and I dont't want to loose my setup.
Thanks for your help.
Click to expand...
Click to collapse
how did you manage to flash stock again after corrupt. mine wont recognize adb while corrupt. please give step by step
nvm. i got it finally
You don't flash with adb, but with fastboot.
The steps are:
1. Turn on phone with pressing vol down and power.
Sent from my Nexus 6 running cyosp using Tapatalk
I just picked up a Nexus 6 to give Project Fi a shot. I figure I might as well root it before setting up all my apps and whatnot. I'm using the Nexus Root Toolkit 2.1.9 and am having some issues. I have all the drivers installed and set up correctly but I can only seem to get ADB to recognize the phone if I change the USB option to Transfer Photos (PTP). During the root process the phone temporarily boots to TWRP and it's at this point where NRT loses ADB recognition and won't finish rooting. Is there something else that I'm overlooking?
You own a Nexus, take 5 minutes to learn ADB and fastboot commands and you don't need a toolkit. To root it, all you should have to do is flash SuperSU in TWRP. But if you used some stupid toolkit to install TWRP, who knows if it worked right or is the most up to date version.
Get the latest version of TWRP (twrp-3.0.3-0-shamu.img) from here and flash it by using "fastboot flash recovery twrp-3.0.3-0-shamu.img" then reboot into TWRP, drag the SuperSU SR3 zip onto your phones storage (you can either do this from in TWRP or from normal Android), flash it and reboot. Boom, you have root.
I'm definitely no stranger to ADB and Fastboot as I've owned other Nexus devices in the past put it's been a few years. I already had NRT installed so I just went that route out of laziness lol. Thanks for the links to the latest SU and TWRP. I'll flash 'em the old fashioned way.
I ran into the same issue with NRT, but to get it to root, I just gave TWRP a password when it asked to mount (it won't do anything anyway..fail to mount), then when asked whether to "Keep System Read only", I clicked the "Never show this screen during boot again" checkbox, then swiped to allow the modification to the system partition, which will then bypass that query when it goes back to TWRP to complete the root script. I hope this helps someone in the future.
By the way, I flashed N6F26R before the root.