Yes, I have read every single thread about this issue and I have tried all steps including downloading new drivers, removing old USB drivers, ...
Yesterday I unlocked my Bootloader using this thread: http://forum.xda-developers.com/showthread.php?t=1064793
Everything went fine and when I boot up my tab I can see the unlocked lock.
According to the thread the next step was following this thread: http://forum.xda-developers.com/showthread.php?t=1079781 (How to get root on 101.v)
I booted my tablet by holding down the Power Button and the Volume Down button. I selected the USB icon and in the left corner I see
"Fastboot USB download protocol"
Bootloader version: P7100BUKC8
Baseband version: P7100BUKDF
Lock state: unlocked
Everything goes well up to the step where I have to type adb push skitzandroid-10-1v-root.zip /sdcard/ in the Command line. When I type this, I get a message: "Error: device not found"
In the aformentioned thread someone else has a similar problem. One person asked if he was still in fastboot? Aren't you supposed to be in fastboot to root your device? He also asks if Clockworkmode is loaded. Doesn't this step come after rooting your device?
When I just open command and type fastboot devices I get a message saying: 'fastboot' is not recognized as an internal or external command, operable program or batch file. When I type "cd "C:\android-sdk-windows\tools"" and then "fastboot devices', it does work and I get a message saying: [serial number] fastboot. Does the fastboot devices command only work if you have a specific folder selected?
This is all so confusing
Thanks for any help
Thanks for the help
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!
Hello,
I accidentally flashed a Stratos firmware on my Amazfit Pace 1. Blame on me !
But since I cannot unbrick it.
I can boot in fastboot bootloader thank to thread https://forum.xda-developers.com/smartwatch/other-smartwatches/amazfit-boot-fastboot-directly-t3546829,
but I cannot boot into recovery with command :
> fastboot boot Amazfit-mod-recovery.img
downloading 'boot.img'...
FAILED (remote: ED: The command is not allowed.)
finished. total time: 0.063s
Can anybody provide help ?
Thanks in advance
The error message is because bootloader is locked. If you don't have root access nor unlocked bootloader, I guess the only option is trying to use Ingenic's "cloner" tool to flash the firmware directly (use option 2 instead of 1 to enter "force erase"). You should flash an old firmware with unlocked bootloader first, check if serial number is OK (if now, fix it using the info in the thread about fixing a null SN) then update.
PS: Do NOT enter "force erase" without having everything set up correctly because the watch won't leave this mode until you flash it.
lfom said:
The error message is because bootloader is locked. If you don't have root access nor unlocked bootloader, I guess the only option is trying to use Ingenic's "cloner" tool to flash the firmware directly (use option 2 instead of 1 to enter "force erase"). You should flash an old firmware with unlocked bootloader first, check if serial number is OK (if now, fix it using the info in the thread about fixing a null SN) then update.
PS: Do NOT enter "force erase" without having everything set up correctly because the watch won't leave this mode until you flash it.
Click to expand...
Click to collapse
Thanks @IFOm
the problem I have is that the swatch boots, then reboot, and finally fall into error screen. So I have little time to act with adb.
iznogoud! said:
Thanks @IFOm
the problem I have is that the swatch boots, then reboot, and finally fall into error screen. So I have little time to act with adb.
Click to expand...
Click to collapse
On Windows use:
Code:
adb wait-for-device & adb shell reboot bootloader
and on Linux/macOS:
Code:
adb wait-for-device; adb shell reboot bootloader
and watch will enter fastboot mode as soon as adb is detected (you can type the command and adb will wait for the device, as the words say, then issue the second one).
adb shell does not work, I get following message :
- exec '/system/bin/sh' failed: Exec format error (8) -
using port=5555
enter fastboot using this method https://www.youtube.com/watch?v=ZlXoeq30vM0 and check the correctness of the serial number and the bootloader lock
iznogoud! said:
adb shell does not work, I get following message :
- exec '/system/bin/sh' failed: Exec format error (8) -
using port=5555
Click to expand...
Click to collapse
Your system is messed up... You can go to fastboot mode manually, then try to flash the correct kernel (boot.img) and recovery from fastboot... this my fix your serial number and show locked status as unlocked again. If everything fails, your last resource is the cloner tool I mentioned a few comments before.
Hi everyone,
I've searched a lot, but haven't found anything. I'm afraid my phone can't be rooted by Magisk because the bootloader is locked. Hopefully someone will tell me I'm wrong?
I followed a fastboot guide (enable OEM unlock, USB debug) and was attempting the command prompts via ADB fastboot folder.
"adb devices" shows me my device ID, however the next step - "adb reboot bootloader" - just reboots. And the following step ("fastboot devices") yields nothing.
From what I can tell, my phone has a locked bootloader and there's no way to unlock it. This is why the ADB fastboot command doesn't work for me.
Furthermore, there's no way to install Magisk without this function. I read something about downloading the original firmware for my phone, but I haven't found the firmware anywhere online.
Appreciate any help you guys can offer. Thank you!
Eric
Bump - please anyone / any ideas?
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...