Hello everyone!
I am currently having issues with my Galaxy S4. I am attempting to install twrp onto it although I am having issues. I have not made any modifications to it, it is running the stock rom and it is not rooted.
I am following this guide: https://www.xda-developers.com/how-to-install-twrp/
I installed adb and fastboot using: https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
I have not gotten any errors.
I type into command prompt:
adb devices
I then get my devices id.
I then type adb reboot bootloader
Once it finishes going into bootloader.
I type adb devices and then get nothing.
I also tried typing fastboot devices and also got nothing.
When I use flashboot flash recovery it gives: <waiting for device>
Could anyone help? I am a newbie at this.
Thank you!
Related
So I'm in the process of trying to Root my ZTE Smarttab 10 on firmware v03b.
Ive been following instructions on the following pages:
http://forum.xda-developers.com/showthread.php?t=1629630
http://forum.xda-developers.com/showthread.php?t=1473555
The instructions are spread out across those threads and my problem starts kind of early in the process.
My goal is to use ADB to boot in to the Bootloader and then use a recovery rom to use TWRP to install a rom.
What i have done:
I have installed the ZTE Drivers
I have installed the SDK tools and updated it.
Now when the tablet is running normally I can see it in ADB and is able to run the command.
ADB Reboot Bootloader
This reboots the devices to a black screen (I assume this is the bootloader) and windows recognizes that a device is there.
The problem is that when I try to see this from ADB i cannot see the device when running ADB Devices.
This makes the next step impossible as I need to use ADB to boot a recovery rom.
So I would have posted in the development treads listed above but as I dont have 10 posts (this being my first post) I cannot post in the threads above.
I'm confident that this is a driver problem and I have uninstalled and re-installed all the drivers related to this including SDK.
But no luck yet.
Where other people say they have succeeded is when in the device manager they have ADB interface and ZTE Handset ADB interface listed.
This is the state where I'm at but I still cannot see the device in ADB.
Anyone have any insight on this kind of problem and can offer any help for a solution or direction to get to the solution.
Thank you for your help and attention!
//Nagarutu
Vodafone (ZTE) SmartTab10 3.2 HoneyComb
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
matt4321 said:
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
Click to expand...
Click to collapse
Thank you for the help ! it cleared things up for me.
Now the trouble's continue.
With the firmware im on (v03b) you cannot use the fastboot flash method but only fastboot.
And they way it is supposed to be done is that you run
fastboot boot recovery.img (recovery being a twrp recovery for my device)
When its booted to TWRP i should be able to see it in ADB to be able to run the following commands to it:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
However I cannot get it to show in ADB (or fastboot) when its booted in to TWRP.
Any ideas?
I managed to solve the last bit to.
Now it was actually a driver problem, so i just updated the driver in device manager and located the ADB driver from ZTE and it worked to boot in to TWRP and then to flash the device.
Now I have CM10 installed and is smiling!
Took me 4 days but damn it its done!
Thanks for the help!
Glad you've figured it out
1a
2a
3a
4a
5a
Hello Everyone, this is one of my first posts so go easy on me.
I used the method in this thread to flash JB onto my TF201, and now i cannot boot to recovery (get the android on his back/side with the red exclamation) and fastboot shows up as a device in device manager in windows, but when i run the "fastboot devices" command with the up to date SDK nothing is listed. ADB works, but for osme reason superuser was installed as a system process and will not uninstall, and will not issue any sort of root command to anything, including ADB. any ideas?
Any help would be greatly appreciated. I have been reading the forums for several days and believe that I am completely stuck. My son rooted his KFHDX 7" and was messing with different apks. It was still working at this point.
He thought it was running slow so he put it into recovery mode (power and volume up) and chose to reset it back to factory settings. Now it just boots to the Gray Kindle Fire bootup screen. Now the ADB is not enabled, he lost his root, and the device is locked.
When I plug the device into my computer (Windows 7) it won't even recognize it. Instead it gives me MTP Devices with error. I have loaded all of the device drives and Android SDK with no luck.
The only adb functions that appear to work are:
adb devices -------> This only gives me the generic serial# 01234569789ABCDE
adb reboot -------> This will reboot the kindle but it won't go past the gray logo
adb reboot-bootloader -------> This will put me into fastboot mode
adb kill-server
adb start-server -------> This will restart the ports but has not affect on the other commands
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
However I can't use the following commands since it says my device is locked:
fastboot -i 0x1949 oem device-info
fastboot flash recovery twrp-2.8.x.x-xxx.img
fastboot boot twrp-2.8.x.x-xxx.img
I tried the 1-Click automated file and it got me all the way through until it asked me to enable the ADB debugging which I couldn't do since I am stuck at the boot screen. And I can't use a tool kit to fix it since I can't downgrade to a lower release.
Therefore I can not unlock my bootloader without downgrading which is impossible without a working system and functioning recovery. I can't root my devices without ADB enabled. And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Please help, I am trying to get this working before Christmas.
Thanks.
DadSteveo said:
Any help would be greatly appreciated. I have been reading the forums for several days and believe that I am completely stuck. My son rooted his KFHDX 7" and was messing with different apks. It was still working at this point.
He thought it was running slow so he put it into recovery mode (power and volume up) and chose to reset it back to factory settings. Now it just boots to the Gray Kindle Fire bootup screen. Now the ADB is not enabled, he lost his root, and the device is locked.
When I plug the device into my computer (Windows 7) it won't even recognize it. Instead it gives me MTP Devices with error. I have loaded all of the device drives and Android SDK with no luck.
The only adb functions that appear to work are:
adb devices -------> This only gives me the generic serial# 01234569789ABCDE
adb reboot -------> This will reboot the kindle but it won't go past the gray logo
adb reboot-bootloader -------> This will put me into fastboot mode
adb kill-server
adb start-server -------> This will restart the ports but has not affect on the other commands
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
However I can't use the following commands since it says my device is locked:
fastboot -i 0x1949 oem device-info
fastboot flash recovery twrp-2.8.x.x-xxx.img
fastboot boot twrp-2.8.x.x-xxx.img
I tried the 1-Click automated file and it got me all the way through until it asked me to enable the ADB debugging which I couldn't do since I am stuck at the boot screen. And I can't use a tool kit to fix it since I can't downgrade to a lower release.
Therefore I can not unlock my bootloader without downgrading which is impossible without a working system and functioning recovery. I can't root my devices without ADB enabled. And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Please help, I am trying to get this working before Christmas.
Thanks.
Click to expand...
Click to collapse
Unfortunately, there is no known recovery from this type of failure. I don't say that casually and wish there was a solution. The symptoms you report are both common and tell tale. The device is bricked.
I just replaced the motherboard on my hdx 8.9
It worked, I had to order a daughterboard also.
Total cost around $50 from where I got them.
Worth looking into. Watch teardown videos on YouTube and get the right tools.
Sent from my SM-N920T using Tapatalk
Too late?
DadSteveo said:
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Click to expand...
Click to collapse
Since fastboot appears to respond as expected on your device,
I'd be **very** interested in testing my long-standing theory
that 'fastboot update' __might__ work even on locked devices.
The "gotcha" is that we'd need to prepare the right package for
your Kindle. So, I gather it's an HDX 7" (3rd Gen?), i.e. "thor" model.
Do you remember what version of Fire OS you had installed?
So i'm trying to get the bootloader unlocked so i can begin to mess with the device but it just doesn't want to go into the bootloader. It goes into recovery fine and i've tried going in there that way but it doesn't work. It just boots up android. Here's what i typed into my prompt.
adb devices
adb reboot bootloader
fastboot devices
adb reboot-bootloader
fastboot devices
adb reboot recovery
fastboot devices
Thank you in advance for trying to help
Hello, I am new to this forum, I have a boot looped Samsung A51. That has been water damaged.
And when I try to use ADB and type "fastboot oem unlock" the cmd says waiting for device. Or when I type root in ADB, the cmd says unable to connect for root: closed.
So I have a boot locked phone that does not respond to ADB commands. I am wondering if the hardware is damaged? Any advice is appreciated. Thank You.
If I type adb devices, my device shows up. It just doesn't respond to any commands and I can't push any files...