Related
I'm on stock .890 (rooted) and I noticed the official .906 update available on my phone today by going into system updates. It downloaded, and I had it install. The phone automatically rebooted to do the install and gets stuck at the AP Fastboot Flash Mode (s) (Boot Failure) Invalid CG Version.
If I restart the phone again, it boots into Android and I can get to my home screen, but after about 5 - 10 seconds it just reboots back into the Boot Failure screen above. I'm stuck in this loop.
The fact that it does boot back into the current .890 android, (for about 10 seconds) leads me to think this can be fixed easily? How can I stop it from trying to automatically reboot back into AP Fastboot?
Any suggestions on how to get out of this?
I have no idea how to fix this since I haven't played with my Droid yet. You could try booting into recovery and try wiping delvik cache and partition and if that doesn't work download a stock version of the rom or a custom one and flash it is what I would do. It seems like your filesystem got corrupted from the root
Sent from my XT860 using XDA
HEMItude said:
I'm on stock .890 (rooted) and I noticed the official .906 update available on my phone today by going into system updates. It downloaded, and I had it install. The phone automatically rebooted to do the install and gets stuck at the AP Fastboot Flash Mode (s) (Boot Failure) Invalid CG Version.
If I restart the phone again, it boots into Android and I can get to my home screen, but after about 5 - 10 seconds it just reboots back into the Boot Failure screen above. I'm stuck in this loop.
The fact that it does boot back into the current .890 android, (for about 10 seconds) leads me to think this can be fixed easily? How can I stop it from trying to automatically reboot back into AP Fastboot?
Any suggestions on how to get out of this?
Click to expand...
Click to collapse
I would use RSD lite to flash 5.6.890 by booting with M+Power and then AP Fastboot mode.
Atrixn00b said:
I have no idea how to fix this since I haven't played with my Droid yet. You could try booting into recovery and try wiping delvik cache and partition and if that doesn't work download a stock version of the rom or a custom one and flash it is what I would do. It seems like your filesystem got corrupted from the root
Sent from my XT860 using XDA
Click to expand...
Click to collapse
This won't work because he doesn't have root or boot/safe strap installed and you can't wipe partitions/dalvik through stock recovery.
ohhh makes sense. haha
I'm still confused about the difference between x+power and m+power
Would this be something Motofail one click could fix?
DoubleYouPee said:
I'm still confused about the difference between x+power and m+power
Click to expand...
Click to collapse
X+Power gets you to stock android recovery. M+Power gets you to the selection menu where you can boot into AP Fastboot mode to flash, or boot into BP Tools to access Bootstrap (Hash's in particular).
MerCiLeSS28 said:
Would this be something Motofail one click could fix?
Click to expand...
Click to collapse
Most likely not because he can't access the phone to connect via Charge Only nor is he able to install Boot/Safe Strap. Maybe root through ADB and push it that way? Maybe...
I was able to get into Clockwork. During that brief few seconds that it would boot back into Android, I was able to quickly use the Boot Into Recovery option. As using the hard key combinations wouldn't work, it just kept bringing me back to the AP boot failure.
Once in Clockwork, I was able to do a factory wipe and cache clears. After that, I could succesfully boot into the OS and gain access to the device without it continually trying to reboot. But it didn't help....as I tried to download and install the OTA to .906 it restarted the device to atempt the install and it brought me right back to the same boot failure loop.
My final resolution was to use psouza4's 890 update script to get back to a complete fresh stock image of .890. Once I did that, the official OTA to .906 installed perfectly. I re-rooted and was good to go.
There was probably a much simpler solution, but I didn't know it. Plus I felt better starting over from scratch anyway.
Not sure exactly what it was causing it...probably my own stupidity.
My moto x got bricked after OTA update
it had root with pwnmymoto and xposedframeowrk
now reboots after 15 seconds, and i can't even turn it off
what can i do guys?
already installed root and apps, yet i can't fix it
help me please
fellhound said:
My moto x got bricked after OTA update
it had root with pwnmymoto and xposedframeowrk
now reboots after 15 seconds, and i can't even turn it off
what can i do guys?
already installed root and apps, yet i can't fix it
help me please
Click to expand...
Click to collapse
Fastboot erase cache
shane1 said:
Fastboot erase cache
Click to expand...
Click to collapse
i tried to install stock but i can't with "adb reboot fastloader" beacuse it restarts every 10-20 seconds"
and according to http://forum.xda-developers.com/showthread.php?t=2444957
We have two (ok more but were not going into that) boot modes. First is normal, which boots regular Android, and in this case boots with system write protected. Second is recovery mode, normally it boots recovery without write protection. Our exploit will hijack recovery bootmode and boot Android without write protection.
After running this exploit, if you boot normally /system will be write protected. If you boot to "recovery", Android will boot without write protection. If you wish to edit system, you must boot into "recovery" to do so, any changes made will stick and will work in either bootmode. My suggestion is to make your changes in "recovery" and run the device day to day in normal mode, until we are certain "recovery" mode will be 100% stable for day to day use.
there is not a single drop of help with fastloader
edit: i managed to enable usb depuration by clicking several times on status/kernel version
i can run the command now, moto x responds and just Fast reboot, does not enter into fastloader
reached a dead end, now im desperated
Just put you phone into fast boot mode, power and volume down, open adb, connect your phone and type in fastboot erase cache as stated in the second post. Your phone is not bricked but its trying to flash the ota automatically. You've rooted with jcases method and that installs a custom recovery which is not recognized by the ota, you need stock recovery for it to flash.
Sent on my Moto X
flashallthetime said:
Just put you phone into fast boot mode, power and volume down, open adb, connect your phone and type in fastboot erase cache as stated in the second post. Your phone is not bricked but its trying to flash the ota automatically. You've rooted with jcases method and that installs a custom recovery which is not recognized by the ota, you need stock recovery for it to flash.
Sent on my Moto X
Click to expand...
Click to collapse
wow, finally, i was dying, now it does not reset itself.
How can i know if i have custom recovery? i though it was the normal one, wasn't aware pwnmymoto install custom recovery..
should i install stock rom anyways?
now i am downloading OTA again, now that i don't have root and pwnmymoto installed maybe it will work
will report results in 5 minutes
Thanks for the help guise
EDIT: lel no, after redownloading OTA update, it's still halfbricking with reboots.
I have recovered it again cleaning cache, but i wish to get OTA
Any ideas?
P.D all this trouble just to put 2 files into /system/ to enable Playstation mobile geez ;_;
fellhound said:
bump
Click to expand...
Click to collapse
I specifically know very little about pwnmymoto root method, my boot loader is unlocked, so I rooted the old fashion way. I know pwnmymoto hijacks the stick recovery. You may want to rsdlite back to stock, I believe there's a fxz with the latest update and root with jcases new method. Unless someone with more experience with pwnmymoto replies
Sent on my Moto X
You need to either flash the stock recovery and system through fastboot, or just RSD the whole thing (which deletes all your data). That's the only way you'll get it to accept the OTA update. Without the stock recovery, it will keep boot looping when you try to install the OTA.
Yes. Restore to stock. Threads galore. Once you boot you'll get an OTA prompt that'll work no problem.
Sent from my XT1060 using Tapatalk
http://forum.xda-developers.com/moto-x/general/moto-x-unbrick-ota-update-loader-v30-t3153725
when I did it go into bootloader but it could not go into download mode, i know how to restore back to stock rom unroot. i rooted it using towelroot then flashed wrong recovery but recovery worked, it was on 6.0.0.0 something. When I try to go into fastboot and it say "loading" top of screen and tap volume up to continue, nothing moving foward into download mode.
Please Help.
Pull battery? Enter recovery (or flash new recovery.img in fastboot). If this doesn't help, try kdz.
bravho said:
Pull battery? Enter recovery (or flash new recovery.img in fastboot). If this doesn't help, try kdz.
Click to expand...
Click to collapse
I will try it when I get home, already did battery pull, that did not do it. So I was thinking doing lg tool to update firmware then downgrade later.
Where do I can find this recovery IMG? Custom recovery or stock recovery?
Thanks for replying.
Custom : see thread from cm11, @Quarx, twrp or cwm. @shoxxy has latest twrp
Sent from my LG-D405n using XDA Free mobile app
LeonKnight12 said:
when I did it go into bootloader but it could not go into download mode, i know how to restore back to stock rom unroot. i rooted it using towelroot then flashed wrong recovery but recovery worked, it was on 6.0.0.0 something. When I try to go into fastboot and it say "loading" top of screen and tap volume up to continue, nothing moving foward into download mode.
Please Help.
Click to expand...
Click to collapse
When making this kind of post, ALWAYS include the device model you are speaking of. There are 4 different models of the LG L90. From your location, I'll guess that you have the LG-D415 model.
From what I'm reading, you are NOT in fastboot mode but Software Update Mode. You MUST zero out the LAF partition in order to enable fastboot on the device. Also, fastboot and download modes are one in the same.
And what exactly are you trying to do? If your recovery is your issue, you can go here and scroll down to post #4 and download a flashable version of TWRP which can be flashed with the recovery you already have. Once flashed, find an option in your current recovery to "Reboot Recovery". It's probably in the "Advanced" menu. This will unload the current recovery from memory and load and execute the new recovery.
You also may want to have a look at the Frequently Asked Questions - LG Optimus L90 thread.
Well I messed up big time, no os installed, But device stills works were able to see download mode with numbers beside left screen not on second screen with bars.
Able to go in Twrp but it keep saying failed when i flash stock rom (remounting problem?).
Device I battery pull and put battery in and able to see LG logo then it went into CWM recovery itself then I selected Recovery reboot from CWM leaded me to TWRP recovery.
Tried to flash using lgtool2014 but flashing stock rom bars hasn't moved kept saying replug usb and retry.
Good News! I got it to work again!
Searching many website homework endless hours and I got my phone to work again. I was not panic I had nexus 6 with me, so I had a experience previous devices rooting.
Anyway, I went through to unlock bootloader and then I reboot the phone into TWRP recovery and flashed stock.zip sucessfully, unmounting was failed. Clicked reboot phone and LG logo appears stayed for like few sec then starting seeing tmobile boot up and everything seem well. gonna root again to see if i get any of this to work.
Hi guys, I need help please!
I am using Samsung Note 3 SM-N9005 ARMv7 Lollipop 5.0. Rooted it with Kingoroot. "installed" TWRP through Flashify.
I downloaded Xposed Framework xposed-v86-sdk21-arm.zip onto my phone and installed it through TWRP in Flashify. Everything seemed fine, got the message install successful, I selected "reboot" instead of "clear cache/dalvik". Phone went into reboot...Samsung Note 3...Samsung logo...and stuck there. I understand that it takes some time for first boot, and I waited, but almost an hour and its still showing the same screen. So I tried to power off the phone, but it restarted again and stuck in the same logo screen. I tried to go into recovery mode hoping to get TWRP to do a reset or something, but no TWRP! Was only given option of "volume up - continue(to odin mode)" and "volume down - cancel(restart phone)". No option for factory reset either. So i booted odin, and tried to flash openrecovery-twrp-2.6.3.7-hlte.img.tar, got the messaged passed, phone rebooted and again stuck in Samsung logo. Tried recovery mode and still no TWRP! Please help!!:crying: :crying: :crying:
p.s. phone won't power off, only way to do it is to remove the battery.
Samsung phones stock ROMs need an special version of Xposed framework. Geez, it is on the official thread:
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Click to expand...
Click to collapse
Archy12 said:
Hi guys, I need help please!
I am using Samsung Note 3 SM-N9005 ARMv7. Rooted it with Kingoroot. "installed" TWRP through Flashify.
I downloaded Xposed Framework xposed-v86-sdk21-arm.zip onto my phone and installed it through TWRP in Flashify. Everything seemed fine, got the message install successful, I selected "reboot" instead of "clear cache/dalvik". Phone went into reboot...Samsung Note 3...Samsung logo...and stuck there. I understand that it takes some time for first boot, and I waited, but almost an hour and its still showing the same screen. So I tried to power off the phone, but it restarted again and stuck in the same logo screen. I tried to go into recovery mode hoping to get TWRP to do a reset or something, but no TWRP! Was only given option of "volume up - continue(to odin mode)" and "volume down - cancel(restart phone)". No option for factory reset either. So i booted odin, and tried to flash openrecovery-twrp-2.6.3.7-hlte.img.tar, got the messaged passed, phone rebooted and again stuck in Samsung logo. Tried recovery mode and still no TWRP! Please help!!:crying: :crying: :crying:
p.s. phone won't power off, only way to do it is to remove the battery.
Click to expand...
Click to collapse
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
io_gh0st said:
Samsung phones stock ROMs need an special version of Xposed framework. Geez, it is on the official thread:
Click to expand...
Click to collapse
Thank you for you reply. Yes, I understand that, which was why I have been trying to find the correct version. Did a few searches using my phone type and version and found a list of sdk21.zips...so i selected the latest version..
mattzeller said:
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
Click to expand...
Click to collapse
Thank you for your reply, I'll try that now.
mattzeller said:
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
Click to expand...
Click to collapse
I tried it, unchecked "reboot", flashed TWRP, power off. When I tried button combo, I can't boot into recovery. It either keep giving me the restarting loop (power on, samsung note 3..then power off, and on again..) or if i let go of the power button at note 3, it goes to the samsung logo and stuck there.
update: I kept trying, and finally got a little different response. I pressed volume up + home + power buttons, and got 3 small lines of colorful words...
Recovery booting
Recovery is not seandroid enforcing
Set warranty bit : recovery
and then the phone turns off and start again
Tried different combinations, so far only the volume up sequence showed something a little different.
Archy12 said:
I tried it, unchecked "reboot", flashed TWRP, power off. When I tried button combo, I can't boot into recovery. It either keep giving me the restarting loop (power on, samsung note 3..then power off, and on again..) or if i let go of the power button at note 3, it goes to the samsung logo and stuck there.
update: I kept trying, and finally got a little different response. I pressed volume up + home + power buttons, and got 3 small lines of colorful words...
Recovery booting
Recovery is not seandroid enforcing
Set warranty bit : recovery
and then the phone turns off and start again
Tried different combinations, so far only the volume up sequence showed something a little different.
Click to expand...
Click to collapse
If you your phone does not boot into TWRP right after you flash it it will not stick and you need to flash it again. To get into recovery is power+home+volume up
Sent from my SCH-R220
mattzeller said:
If you your phone does not boot into TWRP right after you flash it it will not stick and you need to flash it again. To get into recovery is power+home+volume up
Sent from my SCH-R220
Click to expand...
Click to collapse
Could it be the TWRP versions doesn't work on my phone?
I tried openrecovery-twrp-2.6.3.7-hlte.img.tar and also twrp-2.8.7.0-hlte-4.4.img.tar both getting the same results "recovery is not seandroid enforcing" when I pressed vol up + home + power
Archy12 said:
Could it be the TWRP versions doesn't work on my phone?
I tried openrecovery-twrp-2.6.3.7-hlte.img.tar and also twrp-2.8.7.0-hlte-4.4.img.tar both getting the same results "recovery is not seandroid enforcing" when I pressed vol up + home + power
Click to expand...
Click to collapse
That is ok, you get that when you have modified system/recovery. Means your are not fully stock. If you had full stock unrooted unmodified system and recovery that goes away, nothing to worry about. If you are still having problems follow these step exactly:
1) Pull battery out of phone then put it back in
2) boot to download mode (power+home+volume down)
3) open Odin on computer (run as admin)
4) plug phone into computer
5) Uncheck a. Reboot and f. Reset time in Odin
6) flash TWRP (TWRP.img file goes in AP)
7) after successful flash unplug phone and pull battery
8) put battery back in and boot directly to recovery (power+home+volume up)
If you let it boot normally without going into TWRP first, it does not stick
Sent from my SCH-R220
mattzeller said:
That is ok, you get that when you have modified system/recovery. Means your are not fully stock. If you had full stock unrooted unmodified system and recovery that goes away, nothing to worry about. If you are still having problems follow these step exactly:
1) Pull battery out of phone then put it back in
2) boot to download mode (power+home+volume down)
3) open Odin on computer (run as admin)
4) plug phone into computer
5) Uncheck a. Reboot and f. Reset time in Odin
6) flash TWRP (TWRP.img file goes in AP)
7) after successful flash unplug phone and pull battery
8) put battery back in and boot directly to recovery (power+home+volume up)
If you let it boot normally without going into TWRP first, it does not stick
Sent from my SCH-R220
Click to expand...
Click to collapse
Thank you very much!!! I am finally able to boot into TWRP and did a restore, now my phone is back on!! Strange though, I was doing exactly those steps earlier but not successful. Anyways, Thank you very much!! <3
Oh, since I'm here, can you give me advise on which version xposed framework I should get? (Although I don't think my phone is touchwiz, is there a way to find out/confirm? I'm a noob as you can see)
Archy12 said:
Thank you very much!!! I finally able to boot into TWRP and did a restore, now my phone is back on!! Strange though, I was doing exactly those steps earlier but not successful. Anyways, Thank you very much!! <3
Oh, since I'm here, can you give me advise on which version framework I should get? (Although I don't think my phone is touchwiz, is there a way to find out? I'm a noob as you can see)
Click to expand...
Click to collapse
Ok, now that TWRP is on there things should be easier. You are on Stock ROM, it is TouchWiz. You will need to flash a custom ROM that is deodexed. If you like the stock look, feel, and options look in the threads for your device for a stock deodexed ROM. Or you can flash CM. Depending on what version of Android you decide to run will dictate which version of Xposed you install.
Sent from my SCH-R220
I am getting a note3 and wanted to install xposed on it. the phone is running 4.3. with that version there is no need for flashing correct? simply download apk and install?
mattzeller said:
Ok, now that TWRP is on there things should be easier. You are on Stock ROM, it is TouchWiz. You will need to flash a custom ROM that is deodexed. If you like the stock look, feel, and options look in the threads for your device for a stock deodexed ROM. Or you can flash CM. Depending on what version of Android you decide to run will dictate which version of Xposed you install.
Sent from my SCH-R220
Click to expand...
Click to collapse
I am quite used to the look and functionity of the current version I am using...which is lollipop 5.0. My phone is Samsung Note 3 SM-N9005 ARMv7 international Qualcomm. I'll need to flash custom ROM and then get a "matching" xposed framework,correct? Could you please direct me as to how to get xposed framework to work please?
Archy12 said:
I am quite used to the look and functionity of the current version I am using...which is lollipop 5.0. My phone is Samsung Note 3 SM-N9005 ARMv7 international Qualcomm. I'll need to flash custom ROM and then get a "matching" xposed framework,correct? Could you please direct me as to how to get xposed framework to work please?
Click to expand...
Click to collapse
Just go to the threads for your device and flash a TouchWiz based deodexed ROM
Sent from my SCH-R220
---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------
trulosdoulos said:
I am getting a note3 and wanted to install xposed on it. the phone is running 4.3. with that version there is no need for flashing correct? simply download apk and install?
Click to expand...
Click to collapse
Correct, you would need this one:
http://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v33_36570c.apk
Sent from my SCH-R220
There is now an Xposed framework package supporting Stock (odexed) TouchWiz ROMS: http://forum.xda-developers.com/showpost.php?p=65373013&postcount=3960
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here http://bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
MDV106 said:
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
Click to expand...
Click to collapse
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
t0r3n0 said:
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
Click to expand...
Click to collapse
you can install it using Magisk Manager apk, or flash the Magisk zip file inside TWRP, your choice. I dont think either of the two menthods are risky
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
shadow87qft said:
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
Click to expand...
Click to collapse
For me, i found that fastboot was being exposed for a few seconds when it would start to turn back on after the battery dying out. I was able to send 'fastboot reboot recovery' and it didn't boot into recovery, but it booted into Android... A bit strange.