Related
Hi all, this is a last ditched effort at maybe saving my phone. I did an update on my SU and for some unknown reason it rebooted my phone. It then loaded up my rom until the kernel settings loaded then rebooted once again. I then tried to go into recovery to flash a backup and it booted me straight into my unlocked fastboot. I then tried to reboot once again in hopes I could fast navigate into twrp through rom manager, once in I was prompted that I no longer had root. I then decided to start over from scratch and load a recovery in fastboot. Once I had everything good to go I plugged everything in and instead of recognizing my phone as a drive, HTC manager popped up instead. I then updated my drivers to see if maybe that would fix the problem with no luck. I am at a loss at this point. I would greatly appreciate any help you guys can offer.
grimzen said:
Hi all, this is a last ditched effort at maybe saving my phone. I did an update on my SU and for some unknown reason it rebooted my phone. It then loaded up my rom until the kernel settings loaded then rebooted once again. This is completely normal, you should have just rebooted the phone and been done I then tried to go into recovery to flash a backup and it booted me straight into my unlocked fastboot. Again totally normal, thats the bootloader use the vol to move down and choose recovery and hit power this will boot you to TWRP I then tried to reboot once again in hopes I could fast navigate into twrp through rom manager, once in I was prompted that I no longer had root. I then decided to start over from scratch and load a recovery in fastboot. Why ? Once I had everything good to go I plugged everything in and instead of recognizing my phone as a drive, HTC manager popped up instead. You should not have Sync installed only the drivers I then updated my drivers to see if maybe that would fix the problem with no luck. I am at a loss at this point. I would greatly appreciate any help you guys can offer.
Click to expand...
Click to collapse
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
clsA said:
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
Click to expand...
Click to collapse
I was doing a SU update. It restarted into a loop that boots about 1 min after the splash screen then resets. I've tried to redownload root through SU app as I can no longer connect through usb but it reboots to soon. I used Rom Manager to try and get into recovery as a second alternative.
grimzen said:
I was doing a SU update. It restarted into a loop that boots about 1 min after the splash screen then resets. I've tried to redownload root through SU app as I can no longer connect through usb but it reboots to soon. I used Rom Manager to try and get into recovery as a second alternative.
Click to expand...
Click to collapse
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
flash in recovery
use adb push UPDATE-SuperSU-v1.86.zip /data/media/0
to get the file on the phone
Reboot to bootloader / fastboot USB
and from command line on pc
fastboot erase cache
fastboot reboot
I cant understand why people using those ROm manager apps to install stuff. And you said it rebooted after you update your SU. Then i tink you pressed reboot into recovery instead of NORMAL. Am i wrong?
clsA said:
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
Click to expand...
Click to collapse
bihslk said:
I cant understand why people using those ROm manager apps to install stuff. And you said it rebooted after you update your SU. Then i tink you pressed reboot into recovery instead of NORMAL. Am i wrong?
Click to expand...
Click to collapse
I no longer have a recovery to be able to flash anything. When I try to load into recovery it just boots right back into fastboot. I was just using rom manager to boot into recovery after I couldn't get into recovery through fastboot, not to flash anything. I was updating Super Su through the actual app itself. it seemed to be downloading something when it rebooted itself and I lost root, recovery and the ability to connect to my computer.
grimzen said:
I no longer have a recovery to be able to flash anything. When I try to load into recovery it just boots right back into fastboot. I was just using rom manager to boot into recovery after I couldn't get into recovery through fastboot, not to flash anything. I was updating Super Su through the actual app itself. it seemed to be downloading something when it rebooted itself and I lost root, recovery and the ability to connect to my computer.
Click to expand...
Click to collapse
I have updated SuperSU many times and never got any problem so there is something you did. Are you on custom or stock rom?
Are you s-off / unlocked bootloader?
bihslk said:
I have updated SuperSU many times and never got any problem so there is something you did. Are you on custom or stock rom?
Are you s-off / unlocked bootloader?
Click to expand...
Click to collapse
My bootloader is unlocked and i'm running Viperrom. I've never gone through the process of s-off but for some reason it says it at the top of my fastboot screen...not sure if that's normal or not.
grimzen said:
My bootloader is unlocked and i'm running Viperrom. I've never gone through the process of s-off but for some reason it says it at the top of my fastboot screen...not sure if that's normal or not.
Click to expand...
Click to collapse
Ok. I think you need to reflash recovery again.
Boot into bootloader and fastboot usb
then download TWRP recovery from here http://techerrata.com/browse/twrp2/m7 and pick 2.6.3.3-m7.img
put it into your fastboot folder and flash it "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img and hit enter
now try to reboot into recovery. When there Wipe Dalvik and Cache and reboot. If recovery ask you to root your device then accept it and reboot.
Remember to connect phone to right USB port not 3.0. Use 2.0 port and try annother cable also.
bihslk said:
Ok. I think you need to reflash recovery again.
Boot into bootloader and fastboot usb
then download TWRP recovery from here http://techerrata.com/browse/twrp2/m7 and pick 2.6.3.3-m7.img
put it into your fastboot folder and flash it "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img and hit enter
now try to reboot into recovery. When there Wipe Dalvik and Cache and reboot. If recovery ask you to root your device then accept it and reboot.
Remember to connect phone to right USB port not 3.0. Use 2.0 port and try annother cable also.
Click to expand...
Click to collapse
I've tried a few different cords and all 3 ports I have still nothing but the HTC manager thing. It will recognize it but only for a split second while booting up but it says HTC BUTTERFLY as the drive and i'm not sure if that's a problem or not but it won't recognize it at all through fastboot.
you cant boot up. if it doesnt recognize it in bootloader mode then i dont know.
Try restart PC. Maybe you have several adb at same time. Adn uninstall htc sync if not but keep drivers
bihslk said:
you cant boot up. if it doesnt recognize it in bootloader mode then i dont know.
Try restart PC. Maybe you have several adb at same time. Adn uninstall htc sync if not but keep drivers
Click to expand...
Click to collapse
Ok will try that now. thanks so much for the help.
I hadthe same problem after flashing a kernel. I repeatedly tried the bootloader (audiodown key + power button) until it started. Recovery was not available, in the red triangle screen press audio up key,got the system recovery screen, wipe cache, reboot the system and then try installing Twrp recovery. It worked.
Sent from my HTC One using xda app-developers app
jpaulpra said:
I hadthe same problem after flashing a kernel. I repeatedly tried the bootloader (audiodown key + power button) until it started. Recovery was not available, in the red triangle screen press audio up key,got the system recovery screen, wipe cache, reboot the system and then try installing Twrp recovery. It worked.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I'm not familiar with the red triangle screen is there a way to boot into it?
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
grimzen said:
I'm not familiar with the red triangle screen is there a way to boot into it?
Click to expand...
Click to collapse
bihslk said:
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I think @jpaulpra was telling him to reflash stock recovery
then boot to it and do clear cache.. then reflash twrp
When I got into bootloader, I lost the Twrp recovery. So when I selected recovery I got the screen with a "triangle and exclamation mark". If you leave it will reboot the system after couple of minutes. But if the audio up key is pressed, it will show a system recovery screen, where cache can be wiped
Sent from my LT26i using Tapatalk
bihslk said:
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Basically all I'm trying to do now it's find a way to get my computer to recognize my phone as a drive. When I go into viper settings and go to advance menu (with the short time I have before boot loop) there is an option to mount drive. When I select the option to do so it hands on splash screen and I have to hold power button to recycle back on. Once back in it's no longer selected. I've never seen a boot loop go pay the flash screen. Is this normal?
Pretty SOL with my son's Nabi2
I'm having a issue with my sons Nabi2 pretty similar. I messed up bigtime guys I rooted it and started messing aroung with the system files. Then didn't get a boot afterwards, wiped everything from twrps system, data, the whole shabang! Even lost my root! and access to on board flash cause I've been trying to recover using twrp with absolutley no luck. I still have the original stock unrooted backup saved to my pc from when I first installed twrp. Can someone please help me? I'm really out here trying to reach out for some help. didn't even know where to post this. Thank you guys. Note to moderators: If this is the wrong place to post this then please point me to the right direction and I apologize.
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
jggrnaut said:
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
Click to expand...
Click to collapse
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
berndblb said:
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
Click to expand...
Click to collapse
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
jggrnaut said:
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
Click to expand...
Click to collapse
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
berndblb said:
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
Click to expand...
Click to collapse
Well it has gotten worse and I think I have lost fastboot now. I downloaded the CWM from part 1 above and flashed it in fastboot. I typed fastboot reboot and now I am stuck in a bootloop still. It says "The device is unlocked" at top of Asus splash screen for about 15 seconds, screen turns black and the goes back to Asus splash screen.
I tried holding power and volume key to get back to fastboot but no luck. Any ideas?
Wow! You are really having some bad luck there!!
First the failed firmware update and now this.... Please post the commands you used to flash CWM.
I have no explanantion for this since you did not even boot into CWM.......
Unless..... the bad firmware flash left a command behind calling the stock recovery to do something (which in your case did not work anyway since it just looped) and now the bootloader tries to execute the command which is not "understood" by CWM. But that still does not explain why you cannot boot into the BL anymore......
Can you turn it off by long pressing power? Try every which way to get into fastboot. Without it there is not much you can do I'm afraid.
Try the restart pin hole (I believe it's on the left side of the tablet near the top) in conjunction with Volume Down, try leaving it alone for a while, try timing the button press somewhat differently - anything to get you into the BL again...
I feel very sorry for you, mate!!
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
jggrnaut said:
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
Click to expand...
Click to collapse
I don't know what happened before - maybe you were doomed since the bad firmware flash - but that last step sealed the coffin.
Using Wipe Data from the bootloader with a custom recovery installed is asking for trouble. Never ever do that.... Sorry, it's a brick. [emoji24]
I recently unlocked and rooted my nexus 6, installed twrp for back up. Then I wiped before making a back up. No I have no os on phone. Is there a fix or am I screwed?
Try using fastboot to flash factory images
Just grab a factory image and flash it.
Remember wiping a device does just that. Wipes it clean
The thing is, I can boot into recovery, but my phone does not show up on my laptop. So I am not sure how to load a factory image. Thx in advance for all the help.
If it doesn't connect while in recovery, uninstall/reinstall drivers.
Doogadoo said:
The thing is, I can boot into recovery, but my phone does not show up on my laptop. So I am not sure how to load a factory image. Thx in advance for all the help.
Click to expand...
Click to collapse
Boot in to recovery, choose reboot system, TWRP will say, no OS installed are you sure? answer yes / swipe, TWRP will ask/say your device is not rooted, do you want to root it? Swipe to confirm.
Reboot your phone, pressing power and volume down, choose recovery mode again, your phone should show up on your lappy.
If not, re-install drivers - adb/fastboot as mentioned before.
For some more info and factory image:
http://https://developers.google.com/android/nexus/images
I was following instructions on rootjunky.com for unlocking and rooting. I successfully unlocked bootloader with sunshine app. Then I flashed TWRP and got it running. But TWRP didn't have the swipe to allow changes to system partition on startup, so I thought I needed to flash system image per the rootjunky video. I figured it couldn't hurt even if it wasn't needed. so I flashed the 10 parts of system image per video and then tried to get to recovery but just saw little dead android flash on screen every few seconds. I have tried holding all combinations of buttons but after unlocked bootloader warning comes up I get lying down android that says "No command" that flashes briefly every few seconds. Am I totally screwed?
All the messages in the command prompt window while flashing all 10 of the system chunks looked nominal ("sending system ... OK ... writing system ... OK", and my batch file looked just like the one in the video.
Any help is appreciated.
Wait. I gave up too soon. Looks like I can get back to fastboot. Somehow TWRP got messed up. I just reflashed TWRP. Whew! Looks like system flash was bad. I'll try flashing system again.
No joy. I have TWRP now, but still can't get system running. When I try to reboot to system from TWRP it comes back to TWRP. I had verified md5sum of system before flashing, so I know that file downloaded ok. Also, adb doesn't see phone when in recovery. I'll keep trying stuff.
Update: I double checked the mda5sum on the system image zip and it was (still) good. Then I re-extracted the ten image chuncks and re-flashed. Now I can boot to system from bootloader and all is as it was before this misadventure. Almost. If I power down phone and then power up I get the dead android with the "No command" message. It just comes on and stays on rather than flashing, so that's an improvement. From there I can get back to the bootloader and then select "Start" to boot up the phone. I can live with that, but it's an annoyance. If anyone has any suggestions to how to make it boot up by itself from power on I'd love to hear them.
Reflash your phone with Verizon Software Update http://www.verizonwireless.com/support/knowledge-base-116673/ and then flash TWRP (fastboot flash recovery twrp.img)
It does't affect your unlocked bootloader.
Thanks, Aptahar, but I have a new theory. I started a new thread here http://forum.xda-developers.com/droid-turbo/help/device-encryption-question-issue-t3283333.
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.