I was flashing the new OTA from adb, and it failed at 70%.
Stock image, locked bootloader, not TWRP, not rooted
Now on bootup, I see nothing but the google logo.
I can reboot to bootloader/recovery mode, but can't flash anything since I hadn't unlocked the bootloader. Any way to proceed? Can I flash another bootloader that will let me unlock from fastboot?
Bootloader can only be unlocked after allowing it in the developers options. Perhaps you can boot into TWRP from the bootloader, fastboot boot xxx. Where xxx is the name of the TWRP IMG. You may be able to side load the OTA that way and flash it. I'm not 100% sure of that though.
Larzzzz82 said:
Bootloader can only be unlocked after allowing it in the developers options. Perhaps you can boot into TWRP from the bootloader, fastboot boot xxx. Where xxx is the name of the TWRP IMG. You may be able to side load the OTA that way and flash it. I'm not 100% sure of that though.
Click to expand...
Click to collapse
How do I push TWRP to the device? I can't flash recovery (it's still stock).
You don't. If you've got fastboot working, just type, fastboot boot (the name of the TWRP IMG) and it should boot on the device.
Sent from my Nexus 6 using Tapatalk
Larzzzz82 said:
You don't. If you've got fastboot working, just type, fastboot boot (the name of the TWRP IMG) and it should boot on the device.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was getting errors when trying to boot from the twrp image. But I figured out that I can boot to recovery, select update from adb, and get adb running again.
I was able to reflash the OTA, looks like it's working now.
I guess the lesson for today is that I should just leave the bootloader unlocked.
Thanks for the help
Excellent!
Sent from my Nexus 6 using Tapatalk
Javi_in_1080p said:
I was errors when trying to boot from the twrp image. But I figured out that I can boot to recovery, select update from adb, and get adb running again.
I was able to reflash the OTA, looks like it's working now.
I guess the lesson for today is that I should just leave the bootloader unlocked.
Thanks for the help
Click to expand...
Click to collapse
That's the 1st commandment! Leave the bootloader unlocked.
Sent from my Pixel XL using Tapatalk
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.
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
[email protected] said:
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
Click to expand...
Click to collapse
Type: fastboot boot (path goes here)
You can drag and drop the twrp img into the command window. This will ensure you have the correct path
[email protected] said:
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
Click to expand...
Click to collapse
Follow this instruction
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
mingkee said:
Follow this instruction
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Click to expand...
Click to collapse
That link doesn't really solve the OP's issue. I have the same issue. BUT - your link did show me that I can BOOT the .img file, I can't flash the .img file. I've verified the bootloader is unlocked by the fastboot getvar command.
I'm not sure what to do next. Installing OpenGapps causes a boot loop and the only thing I can do at this point is a factory reset with the OEM recovery since in the boot loop adb is unresponsive.
joesee said:
That link doesn't really solve the OP's issue. I have the same issue. BUT - your link did show me that I can BOOT the .img file, I can't flash the .img file. I've verified the bootloader is unlocked by the fastboot getvar command.
I'm not sure what to do next. Installing OpenGapps causes a boot loop and the only thing I can do at this point is a factory reset with the OEM recovery since in the boot loop adb is unresponsive.
Click to expand...
Click to collapse
The instruction shows how to flash recovery.img with TWRP though I have no clue how to do it.
I got that error the first time I did it, it was because of a misspelling of the command.
If you already unlocked the bootloader, while in fastboot, you only type "fastboot boot" + "path to twrp img on computer" OR instead of typing out the path, you may drag and drop the file into the command window.
Once it boots to twrp, flash twrp from within the booted img. That ensures you have permanent twrp.
If you were able to unlock your bootloader, the only thing stopping you from loading twrp is improper spelling and path to the img. Almost every error I have seen is from not following the directions.
Vseprz said:
If you already unlocked the bootloader, while in fastboot, you only type "fastboot boot" + "path to twrp img on computer" OR instead of typing out the path, you may drag and drop the file into the command window.
Once it boots to twrp, flash twrp from within the booted img. That ensures you have permanent twrp.
If you were able to unlock your bootloader, the only thing stopping you from loading twrp is improper spelling and path to the img. Almost every error I have seen is from not following the directions.
Click to expand...
Click to collapse
OK, just so I understand correctly, the proper sequence of events is to use fastboot to boot TWRP (which I can do) then, once in TWRP, I can then flash the twrp .zip file, right? Does anyone know if the LG's bootloader overwrites the recovery partition upon boot (in other words, do I have to boot straight to recovery after I flash to ensure it sticks?)
Sorry for the obtuse questions, I've got a lot of experience with Samsung flashing back in the KK and LP days, but not MM.
Thanks in advance!!
joesee said:
OK, just so I understand correctly, the proper sequence of events is to use fastboot to boot TWRP (which I can do) then, once in TWRP, I can then flash the twrp .zip file, right? Does anyone know if the LG's bootloader overwrites the recovery partition upon boot (in other words, do I have to boot straight to recovery after I flash to ensure it sticks?)
Sorry for the obtuse questions, I've got a lot of experience with Samsung flashing back in the KK and LP days, but not MM.
Thanks in advance!!
Click to expand...
Click to collapse
So you have flashed 20i which overwrites twrp with the stock recovery.
You then go through the steps for unlocking the boot loader.
After the boot loader is unlocked, you may boot into twrp with the fastboot boot command.
When that boots into twrp, flash twrp from within that to have it stick.
Have a question and maybe someone can help. Me getting carried away installed twrp from external partition. Now i cannot boot into recovery. Tried flashing using flashify and twrp manager. but flashify does not install after reboot and there is no option for h811 in twrp manager. Anyway to fix this?
Sent from my LG-H811 using Tapatalk
Vseprz said:
So you have flashed 20i which overwrites twrp with the stock recovery.
You then go through the steps for unlocking the boot loader.
After the boot loader is unlocked, you may boot into twrp with the fastboot boot command.
When that boots into twrp, flash twrp from within that to have it stick.
Click to expand...
Click to collapse
Yes, that's exactly the steps I do. I've flashed 20i. I used fastboot to boot into twrp. I then "install" the twrp zip file. Says it flashes with no issues. I then reboot the phone. Still has stock recovery.
I've confirmed my bootloader is unlocked with the fastboot getvar all. I've also tried all three versions of twrp available (.1, .2 and .3) and still doesn't work. Yet twrp works fine if I boot it.
joesee said:
Yes, that's exactly the steps I do. I've flashed 20i. I used fastboot to boot into twrp. I then "install" the twrp zip file. Says it flashes with no issues. I then reboot the phone. Still has stock recovery.
I've confirmed my bootloader is unlocked with the fastboot getvar all. I've also tried all three versions of twrp available (.1, .2 and .3) and still doesn't work. Yet twrp works fine if I boot it.
Click to expand...
Click to collapse
How did you confirm you have stock recovery? Did you use adb reboot recovery? Or did you use hardware keys to boot to it? Because if you use hardware keys you still get the initial confirm factory reset. You just have to accept then it boots to twrp.
---------- Post added at 10:44 AM ---------- Previous post was at 10:22 AM ----------
99problemz said:
Have a question and maybe someone can help. Me getting carried away installed twrp from external partition. Now i cannot boot into recovery. Tried flashing using flashify and twrp manager. but flashify does not install after reboot and there is no option for h811 in twrp manager. Anyway to fix this?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
If boot loader is unlocked you should load twrp from fastboot.
Vseprz said:
How did you confirm you have stock recovery? Did you use adb reboot recovery? Or did you use hardware keys to boot to it? Because if you use hardware keys you still get the initial confirm factory reset. You just have to accept then it boots to twrp.
---------- Post added at 10:44 AM ---------- Previous post was at 10:22 AM ----------
If boot loader is unlocked you should load twrp from fastboot.
Click to expand...
Click to collapse
Hahaha now that's funny!! I bet I've been through 50 blog posts on various sites to try to figure this out. Having successfully installed Viper I didn't want to take the chance and pass that confirm wipe factory question.
I feel like a complete tool. Seriously, thank you for taking the time to respond to me!
joesee said:
Hahaha now that's funny!! I bet I've been through 50 blog posts on various sites to try to figure this out. Having successfully installed Viper I didn't want to take the chance and pass that confirm wipe factory question.
I feel like a complete tool. Seriously, thank you for taking the time to respond to me!
Click to expand...
Click to collapse
I'm glad it all worked out! :good:
finding I have to re-flash with flashify each time
using twrp-2.8.7.1, I get only the first reboot from there with hardware keys letting me into twrp after accepting the first factory reset prompt and denying the second. After that cant do it again unless I re-flash. Same thing happens if I flash it from within twrp. Can use terminal, su, boot recovery and I am in., or ADB/fatsboot Primarily worried about a soft brick condition. H-811, v1 20i stock, unlocked bootloader and rooted. DE-bloated,
Any Ideas, Thanks
jdoebean said:
using twrp-2.8.7.1, I get only the first reboot from there with hardware keys letting me into twrp after accepting the first factory reset prompt and denying the second. After that cant do it again unless I re-flash. Same thing happens if I flash it from within twrp. Can use terminal, su, boot recovery and I am in., or ADB/fatsboot Primarily worried about a soft brick condition. H-811, v1 20i stock, unlocked bootloader and rooted. DE-bloated,
Any Ideas, Thanks
Click to expand...
Click to collapse
You drop the twrp file
In fastboot folder open command prompt and flash twrp first just rename it simply to recovery.img while in the fastboot folder
Type fastboot flash recovery recovery.img
Or just fastboot flash recovery.img
Then it should boot you into twrp
Once booting into twrp flash the supersu zip in your internal sd
Once you have root and reboot all you have to do is use flashify app and download twrp from the app and flash it Twrp sticks from there.
Sent from my LGMS631 using XDA Free mobile app
Tried to install TWRP on my XT1097. The bootloader is unlocked and I'm running stock Marshmallow (XT1095). When I flash in the bootloader, it says SUCCESS, but when I boot into recovery, I get the dead Android and No Command. Is there something resetting the recovery or could it be that I didn't flash the partition when I upgraded to 6? I tried both fastboot and mfastboot. Same result. Thanks for the help.
RangerLG said:
Tried to install TWRP on my XT1097. The bootloader is unlocked and I'm running stock Marshmallow (XT1095). When I flash in the bootloader, it says SUCCESS, but when I boot into recovery, I get the dead Android and No Command. Is there something resetting the recovery or could it be that I didn't flash the partition when I upgraded to 6? I tried both fastboot and mfastboot. Same result. Thanks for the help.
Click to expand...
Click to collapse
After you flash twrp don't reboot. Open recovery right away.
If you reboot before starting twrp the old recovery comes back.
Sent from my XT1095 using Tapatalk
AGISCI said:
After you flash twrp don't reboot. Open recovery right away.
If you reboot before starting twrp the old recovery comes back.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thanks. That worked.
I thought rooting would be the same as my 7 pro so I ran
Code:
fastboot flash boot magsik_boot.img
Now whenever my phone boots up it goes straight to the bootloader. Selecting Recovery Mode or Start both boot back into the bootloader.
Is there any way to reset my boot image?
can"t access through adb either?
My phone won't turn on now https://forum.xda-developers.com/t/...artition-when-the-phone-wont-turn-on.4433849/
But I don't believe adb would have worked since I was in the bootloader. Is there a way to use adb while in the bootloader?
UniquePhillip said:
My phone won't turn on now https://forum.xda-developers.com/t/...artition-when-the-phone-wont-turn-on.4433849/
But I don't believe adb would have worked since I was in the bootloader. Is there a way to use adb while in the bootloader?
Click to expand...
Click to collapse
You could then flash original boot.img for your current software.
Maybe you can extract the original boot partion from payload.bin and flash it back.
UniquePhillip said:
I thought rooting would be the same as my 7 pro so I ran
Code:
fastboot flash boot magsik_boot.img
Now whenever my phone boots up it goes straight to the bootloader. Selecting Recovery Mode or Start both boot back into the bootloader.
Is there any way to reset my boot image?
Click to expand...
Click to collapse
Firstly. Why did you flash it?
You should only boot images, that way you won't end up like this.
All you need to do is boot the original image. Not the patched one that obviously didn't work.
In the future. Just type fastboot boot then the name of the image.
Once you're in, open Magisk and click direct install.