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.
Related
I just received my moto x developer version. I must be an idiot because I can't find instructions on how to root it. Every post I can find is about rooting the locked version. People talk about the fact that I don't need an exploit because my boot loader is unlocked. I get that but I don't know how to root. Can someone kindly point me to a tutorial on how to root if my boot loader is already unlocked.
Install a recovery from the dev section. Either TWRP or CWM will be fine.
Then download SuperSU
flash supersu in recovery.
Moto x - Developer edition root
gunnyman said:
Install a recovery from the dev section. Either TWRP or CWM will be fine.
Then download SuperSU
flash supersu in recovery.
Click to expand...
Click to collapse
Thanks! I'll give it a shot. Much appreciated!
There are a few threads... but to elborate on what gunnyman has said... If your bootloader is unlocked, either Dev Edition, or you have a phone from a carrier like T-Mobile or Sprint that allow you to unlock via Moto's web site then its pretty easy to flash alternate recovery, and root from there.
Steps see -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP (has links to the files you need too.) and there are threads in the General and Developer sections here too.
Same process works if you have 4.2.2 or 4.4 on your phone.
Is there a way to root the developer edition and keep stock recovery ?
Pete
Flash custom recovery, flash root package in custom recovery, re-flash stock recovery
Sent from my Moto X DE
pasta1234 said:
Is there a way to root the developer edition and keep stock recovery ?
Pete
Click to expand...
Click to collapse
You don't have to flash the custom recovery, just boot into it. Once you have the root .zip on your phone reboot into the bootloader and fastboot boot (recovery) and flash the root zip from there. You will have root and stock recovery.
The reason I'm asking is to retain the ability to recieve OTA updates ?
How does one boot into a custom recovery without loading it?
Pete
3UR0TR45H said:
You don't have to flash the custom recovery, just boot into it. Once you have the root .zip on your phone reboot into the bootloader and fastboot boot (recovery) and flash the root zip from there. You will have root and stock recovery.
Click to expand...
Click to collapse
pasta1234 said:
The reason I'm asking is to retain the ability to recieve OTA updates ?
How does one boot into a custom recovery without loading it?
Pete
Click to expand...
Click to collapse
When you enter the fastboot command, use "boot" instead of "flash" and it will just temporarily boot into the recovery without flashing over the stock partition. You can flash the root zip as normal and when you reboot your phone, the custom recovery will be gone.
As far as receiving OTAs, I'm not sure if you'll get them or not. If you go modifying things like kernel, ROM, or even things like the build.prop, chances are it won't work or will break something. The good thing about having an unlocked bootloader is that it's nearly impossible to hard-brick the device unless you're reckless.
Are you sure this works? When I try 'fastboot boot recovery.img' it gives me a "failed command" error. I kicked off another thread asking how to do this since this is what I typically do with Nexus devices. I know that fastboot now has a -c command that might help but I don't know the magic to put after -c to make it work.
If anyone has been able to 'fastboot boot recovery.img' on a Moto X, please lemme know. This would be my preferred path rather than flashing the custom recovery and then the stock recovery back.
3UR0TR45H said:
When you enter the fastboot command, use "boot" instead of "flash" and it will just temporarily boot into the recovery without flashing over the stock partition. You can flash the root zip as normal and when you reboot your phone, the custom recovery will be gone.
As far as receiving OTAs, I'm not sure if you'll get them or not. If you go modifying things like kernel, ROM, or even things like the build.prop, chances are it won't work or will break something. The good thing about having an unlocked bootloader is that it's nearly impossible to hard-brick the device unless you're reckless.
Click to expand...
Click to collapse
pboggini said:
Are you sure this works? When I try 'fastboot boot recovery.img' it gives me a "failed command" error.
Click to expand...
Click to collapse
What happens when you just type fastboot?
Sent from my XT1060 using Tapatalk
This has been said already but you can just "fastboot flash recovery twrp.img", flash your superuser zip then "fastboot flash recovery recovery.img". You are using the correct image name in the command, correct?
Yes, this was said in the thread I started but then I saw someone suggest what I'd been wanting to do. To answer the questions, if I just type fastboot it gives me the help output like it should, fastboot devices shows my device, fastboot reboot works, fastboot reboot-bootloader works, etc. Essentially, I believe that either there is a command string that I could hand to -c or this just won't work on MotoX's like it does all the Nexus devices that I've played with.
Fortunately I did hit Moto up and they gave me permission to download the 4.4 image so I do have the stock recovery.
Ryno77 said:
This has been said already but you can just "fastboot flash recovery twrp.img", flash your superuser zip then "fastboot flash recovery recovery.img". You are using the correct image name in the command, correct?
Click to expand...
Click to collapse
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
ReproOne said:
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
Click to expand...
Click to collapse
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
Thank you for the reply. I thought about taking that approach, but I was really hoping someone would have an answer on why the procedure wasn't working now. My bootloader is still unlocked.
I found this as an approach someone did on the Nexus 4 for a similar issue:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Thoughts?
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
ReproOne said:
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
Click to expand...
Click to collapse
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Thank you for those steps. I do not have an external SD card installed, so I modified it to store the recovery.img on sdcard instead.
Now I can always fastboot flash twrp and then back to stock recovery.
Thank you again!
nfinitefx45 said:
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Click to expand...
Click to collapse
You would need root to do this. Not being able to use "fastboot boot" you would just be backing up the flashed recovery. Possibly towel root temp root, but I would assume it has been patched in newest update.
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
xPhantom said:
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
Click to expand...
Click to collapse
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
neudof said:
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
Click to expand...
Click to collapse
Yes, after the OTA, just flash TWRP back through fastboot and then re-flash SuperSU to get root back.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
I just applied the update released today, and I tried to save the recovery.img file before flashing TWRP. However, it kept giving me permission denied. Do you have the recovery.img file from the update released today so I can use it for the next update?
fastboot not working
please any help on how to access fastboot on HTC one m8.
its showing black screen n fastboot mode...
wot can I do 2 annul d problem
rooting problem
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
jinal shah said:
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
Click to expand...
Click to collapse
What's the output in the terminal when you fastboot flash recovery?
rooting problem
It doesn't show any error as such.
In the command window it shows successful.
But when I click on recovery it reboots back to fast boot.
Like for a second it shows the screen which reads 'this build is only for developers'
But then instead of opening Twrp it reboots back to fast boot.
Ok, here's the rundown - I have a VZW Moto X (XT1096). I previously ran mofo on it had flashed the 5.1 img files to it and so had 5.1 rooted, but with a locked bootloader. After learning that JCase had gotten sunshine to work on it I unlocked my boot loader. I then decided that because I was worried about having the a kind of mish-mash of systems on it, i.e., 5.0 bootloader (unlocked) with hacked and modded 5.1 system files flashed from mofo, that I wanted to start fresh. I then used the XT1096 flash to stock script and flashed back to 5.0 (there were a bunch of problems and bootloops and force closes, but I am happy to report I am now on a fully stock 5.0 with unlocked BL). Following being stock I have tried to take the OTA but have been unable to do so. When I try it OTA on my device it just sits at 0%. When I tried using MDM it gave me an error message that it failed to install the update - on the device it said getjar: unlocked.
So, now that I am on 5.0 with an unlocked bootloader I am not sure how to proceed with my priorities, Root, WiFi tethering and upgrading to 5.1. My questions are this:
(1) How can I upgrade to 5.1 or does my bootloader unlock preclude that?
(2) How best can I achieve root?
(3) Once I am rooted what do I need to do in order to enable wifi tethering?
Thank you so much!
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot and flash the stock system.img and recovery.img before doing the update.
3. I don't have experience with Verizon network. I use T-Mobile on this Verizon device and I just enable WiFi Hotspot. In the APN settings, in the "APN type" field, I add the value "dun". And set everything to IPv4.
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
eksasol said:
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
Click to expand...
Click to collapse
Thank you for the reply - got the update to take and have gotten the device rooted properly.
Now I just need to enable wifi tether - anyone know what is done in the Mofo images that allows it - can i do the same here?
I am interested in this question as well. I am in the exact same boat as the OP, except I am still on a Mofo 5.1 img that is giving me issues. I'd like to flash back to stock and take the OTA. But wifi tether will be a must.
Thanks to mikeoswego we have the tethering answer.
http://forum.xda-developers.com/showthread.php?p=62379151
eksasol said:
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
Click to expand...
Click to collapse
I tried this but after I flash TWRP I can't boot to recovery. If I choose recovery from the bootloader it just turns off the phone (charging icon). If I send it adb reboot recovery I get error android "No Command."
Flashed it multiple times, tried mfastboot, no luck. Any ideas?
Edit: I feel dumb. I was using power button to try to select, it's volume up. Good to go.
GatorsUF said:
Thanks to mikeoswego we have the tethering answer.
http://forum.xda-developers.com/showthread.php?p=62379151
Click to expand...
Click to collapse
The other method (the one I used) was to install the Xtether xposed module for the 2013 Moto X - worked perfectly for me.
I feel like a complete noob for asking this in regards to my XT1096, but, how would I get rid of the unlocked bootloader warning message?
SargeStryker said:
I feel like a complete noob for asking this in regards to my XT1096, but, how would I get rid of the unlocked bootloader warning message?
Click to expand...
Click to collapse
Flashing this
http://forum.xda-developers.com/showthread.php?t=2871478
juliospinoza said:
Flashing this
http://forum.xda-developers.com/showthread.php?t=2871478
Click to expand...
Click to collapse
Thanks!
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.
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Never trust a recovery installed by a tool kit. Grab the recovery img from the site and flash it manually.
all i have now is stock recovery. whats the best way to manually install twrp
go into fastboot and flash it. you have to be in your bootloader to flash via fastboot. you put the file in the same window as your fastboot program, then type.. fastboot flash recovery recoveryname.img, and that will flash twrp. if you type fastboot boot recovery recoveryname.img then itll only boot into recovery one time, thats what your toolkit did.
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Don't use toolkits. I recommend yoiu follow @simms22's solution.
Sent from my Nexus 6 running cyosp using Tapatalk
when you have root, you can always use an app, like flashify, to flash twrp recovery. but you need to have root first.
arcane spade said:
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
Click to expand...
Click to collapse
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
jdpeck said:
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
Click to expand...
Click to collapse
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
scryan said:
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
Click to expand...
Click to collapse
well, thats how you should flash recovery. but its not the reason that we dont use toolkits. we dont use toolkits for several reasons.. 1. they mess up 2. doing it properly is just as fast if not faster 3. newbs think that toolkits are made for them to use. well, they are wrong. toolkits teach you absolutely nothing, which is the worst for beginners.
simms22 said:
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
Click to expand...
Click to collapse
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
jdpeck said:
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
Click to expand...
Click to collapse
if you skipped the recovery.img, your recovery should have stayed.. oh, never mind, i just remembered a file that you need to remove after the first boot, or itll install the stock recovery after the first reboot. its called recovery-from-boot.bak. if you remove that on first boot, youll be fine