Ok, my nexus 7 this morning had just randomly started to not respond to any touch. I restarted the device by turning it off and on again with the power button, and it stuck at Google logo. I can go into bootloader, but not recovery. If I try to go in to recovery, it gets stuck at Google logo again.
The device is stock, didn't even unlock it. Fastboot devices returns the serial number, fastboot oem unlock pops up the screen if I want to proceed, at which point I click no because I don't want to wipe the drive yet. I've tried Nexus Root Toolkit to boot into temporary custom recovery to make a back up, but doesn't work. NRT live log is as follows
-----------------------------------------------------------------------------------------------------------
Information: Rebooting your device into bootloader mode...
fastboot reboot-bootloader
Information: Rebooting your device into bootloader mode...
adb reboot bootloader
Information: Checking Fastboot Status
fastboot devices
Information: Retrying.. Checking Fastboot Status
fastboot devices
05864603 fastboot
Fastboot Status: Device Connected
Information: Booting modified boot.img to enable running privileged commands...
fastboot boot "D:\Android Development\Nexus Root Toolkit 1.7.2\data\Modified_Boot\modified_boot_razor_5.0.1_Information: Waiting for your device...
adb wait-for-device
LRX22C.img"
-------------------------------------------------------------------------------------------------------------
and then times out.
Since i couldn't connect it with my computer with USB debugging on, the drivers might not have installed correctly, although I did try installing the drivers with NRT. Currently my laptop doesn't recognize the device. It does make sound when I connect the device, but it doesn't show up in device manager at all.
Any pointers please?
Hi,
I'm attempting to convert my Ouya to a regular Android device and I'm starting to work with the various manuals that exists
in the 'development' section of the forum.
I've performed the following steps:
1. installed the ADB drivers on Windows 7
2. connected the Ouya to the computers and fix the device manager to detect is as ADB driver.
3. checked that the device it detected (using "adb devices" command).
4. executed the 'adb reboot bootloader' command.
at this point the Ouya (with a wired keyboard connected) rebooted and the TV turned black (but it still detect the HDMI).
5. checked if the device is connected in fastboot, using the command: fastboot devices.
6. executed the command: fastboot boot OuyaCWMrecovery6.0.3.2.img
and it stuck in: 'downloading 'boot.img' ...'
Anyone knows what the problem is?
Anyone?
Please!!
section51 said:
Hi,
I'm attempting to convert my Ouya to a regular Android device and I'm starting to work with the various manuals that exists
in the 'development' section of the forum.
I've performed the following steps:
1. installed the ADB drivers on Windows 7
2. connected the Ouya to the computers and fix the device manager to detect is as ADB driver.
3. checked that the device it detected (using "adb devices" command).
4. executed the 'adb reboot bootloader' command.
at this point the Ouya (with a wired keyboard connected) rebooted and the TV turned black (but it still detect the HDMI).
5. checked if the device is connected in fastboot, using the command: fastboot devices.
6. executed the command: fastboot boot OuyaCWMrecovery6.0.3.2.img
and it stuck in: 'downloading 'boot.img' ...'
Anyone knows what the problem is?
Click to expand...
Click to collapse
section51 said:
Anyone?
Please!!
Click to expand...
Click to collapse
Did you try the oneclick install in the android development page?(http://forum.xda-developers.com/showthread.php?t=2350900) Then after that, update your recovery to the latest and then install this.... http://forum.xda-developers.com/showthread.php?t=2692836
jcgagtv699 said:
Did you try the oneclick install in the android development page?(http://forum.xda-developers.com/showthread.php?t=2350900) Then after that, update your recovery to the latest and then install this.... http://forum.xda-developers.com/showthread.php?t=2692836
Click to expand...
Click to collapse
I've used both links that jcgagtv699 sent me and I was able to install the OuyaCWMrecovery6.0.3.2.
From there I've upgraded the version to 6.0.4.8 and start installing the Ouya Bootmenu (http://forum.xda-developers.com/showthread.php?t=2692836)
and after it was installed successfully I get a menu when the ouya is loaded:
Normal boot
Alternate boot
Recovery
Failsafe
Bootloader
but the problem is that on matter what option I choose I get a RED screen with 'install from zip file'.
Help please!!!
Sounds like you only have the Bootmenu installed. From here you need to install cm11 at the "install from zip file" point.
Trying to follow the steps to boot into TWRP using this method:
http://forum.xda-developers.com/smartwatch-3/development/lwx49k-rooting-easy-t3107501
I am able to boot into fastboot and my screen shows "Running Fastboot" but when I issue the command fastboot boot "<filename>" I just get < waiting for device > on my PC.
Any idea what is getting stuck? I factory reset the watch hoping that would solve the issue but no luck. ADB works fine.
You need to load the drivers for fastboot. What os do you have?
hello
recently i tried to install android wear 2.0 and i did it and downgrade to 1.5 and everything was perfect and i didn't have any problem with it.
but today i tried reinstall it again so i unpair my watch and i enable dev option and enabled adb debugging and tried adb devices and it showed my device :
and then i enter adb reboot bootloader and my watch went to fastboot menu
and then i didn't enter fastboot oem unlock because i unlocked it last time.
so i opened flash-all on my computer and it stuck on < waiting for device >
i tried fastboot devices and i got nothing, fastboot can't recognize my watch.
so anyone can help me ?
(for adb i use this:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
)
behdad_es said:
hello
recently i tried to install android wear 2.0 and i did it and downgrade to 1.5 and everything was perfect and i didn't have any problem with it.
but today i tried reinstall it again so i unpair my watch and i enable dev option and enabled adb debugging and tried adb devices and it showed my device :
and then i enter adb reboot bootloader and my watch went to fastboot menu
and then i didn't enter fastboot oem unlock because i unlocked it last time.
so i opened flash-all on my computer and it stuck on < waiting for device >
i tried fastboot devices and i got nothing, fastboot can't recognize my watch.
so anyone can help me ?
(for adb i use this:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
)
Click to expand...
Click to collapse
Use the Menu in bootloader mode to reboot to bootloader while it is waiting for device. That should get flash-all. bat to just run.
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
try upgrade your android sdk on your pc
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful
i am trying to flash twrp there is no folder called adb i have installed the 15 second adb and all so i have got this minimal adb flashboot and i tried with that and got this ---- FAILED (remote: Flashing is not allowed in Lock State). i have granted all usb and oem unlocking. please help with this
Phone shows unlocked during the boot?
I had the same Problem,after a Factory Reset works for me.
I am on Miglobe-Rom Miui10 8.6.28.
Minimal ADB is enough.
Or use this from Attachment.
Unpack with Win.zip and copy Twrp in this Folder.
Conect the Phone with your Pc ,boot into Bootloader and click "cmd-here.exe"
Use this Command
fastboot flash recovery twrp-3.2.1-3-whyred.img
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
gamebenchjake said:
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
Click to expand...
Click to collapse
Have you fixed your app to run on Magisk-SU ?
otonieru said:
Have you fixed your app to run on Magisk-SU ?
Click to expand...
Click to collapse
Hey Otonieru,
Not yet, but I've got one of the engineers working on it - hopefully it'll be up in the next 30 days or so
Same problem here after updating my gcam was not working was enabling hall again but it is not booting into twrp
Redmi Note 5 pro
So my Bootloader is locked,
My phone stuck in MI recovery idk how.
I cant install MIUI via fastboot. Im stuck ..
Can anyone please help me here not sure how to proceed further.
If you have made sure that you have all the drivers installed and still have not solved, you need to use an Intel-based PC / notebook and use a usb 2.0.
”Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful”
i did that but it is showing failed（too many links）and "press any key to reboot" showing on my phone's fastboot screen
Fastboot boot recovery.img flashing problem on Redmi note 5 pro
My bootloader is unlocked and my oem as well as usb deb is on. After i connect my phone in fastboot mode to my pc. The cmd shows fastboot devices but when it comes to fastboot boot recovery.img flashing device get disconnected. Plzzzzzz let me know a solution for this. A solution for this will be highly appreciateable.