Related
Help! After installing Firefirefire not loaded, the animation is loading and everything. In fastboot flashing betrayed recovery type error downloading boot.img failed. Who does not want to be defined in kfu. Hangs in the boot animation. Drivers removed cleanly and raised again, no result (
sorry for my english
Solved!
Can you reboot using fastboot reboot command.
Try
fastboot reboot. If it reboots, then change the mode of booting to normal using kfu.
Sent from my Amazon Kindle Fire using Tapatalk
I can not change to fastboot, it says error: device offline or waiting device
would try to use kfu option 1 - bootmode normal
if it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
a second pwr off/on will bring you back to normal
if this is not the case check your device manager - the kf uses 2 drivers
one for adb and one for fastboot - about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
Animation is loading normal mode. name in the Device Manager android composite adb interface. After waiting device, nothing happens
it seems your kf is in fastboot mode - the composite driver is for normal and recovery mode - try to update the driver to android adb interface - then the kfu command should work
adb status: Online (sometimes)
adb rooted: No
boot status: unknown
If I choose to act kfu, it says error: device not found
By some miracle I managed to run the light. But the internal memory for applications, downtrodden, buggy. Fff and put cwr, wrote downloading boot.img Filed, root is. Something with the memory I think. What should I do? than flash? Different kfu, does not help. I wanted to put gscript, but it is put into the internal memory, and then total space 0 and Apps 30mb, and where the SD, then 5gb total space
So, this is my first attempt at rooting a device and so far it's gone pretty well despite several hiccups along the way. My current problem is the inability to boot into a custom recovery. I'm running the stock 4.4.2 ROM, have root access per towelroot, have SU installed and updated from SuperSU, and have unlocked the boot loader via the motopocalypse exploit in it's .apk format. Booting into fastboot, I am able to verify I have unlocked the boot loader (Status Code 3.) Now, I have several custom recovery files downloaded and have attempted, including ClockWork Mod offical touch and non, and unofficial versions of TeamWin Recovery Project. All four of these yield the same results, namely, I cannot access them.
The steps I preform are:
(1. Turn the device off
(2. Boot into AP fastboot by holding down the volume + and - buttons, turning on the device, and selecting AP Fastboot as prompted
(3. Run the command "fastboot flash recovery <filename>.img"
(4. Have the following returned:
> sending 'recovery' (8228 KB)...
> OKAY [ 0.640s]
> writing 'recovery'...
> OKAY [ 2.180s]
> finished. total time: 2.820s
(5. Run the command "fastboot boot <filename.img>"
(6. Have the following returned:
> downloading 'boot.img'...
> OKAY [ 0.640s]
> booting...
> Command restricted
> FAILED (remote failure)
> finished. total time: 0.730s
(7. Run the command: "fastboot continue" to regain access to my phone
Also, when I boot into the boot selector and select the recovery option, it will show the "Warning, your warranty is void" prompt, flicker, then show the prompt again, which I presumed to be the phone flashing back the stock recovery, which I hadn't had previous success accessing fully either, and then continue to boot normally. Because of that, I used RootBrowser on my device and proceeded to move the "recovery-from-boot.p" file from it's /system home to /storage/emulated/0/Download in the case that I needed it again in the future.
Moving said ".p" file yielded no different result in the aforementioned fastboot commands. However, when I boot into recovery on the device itself via the boot selector, it will hang (let it run for five minutes at one point) at the "Warranty Void" screen, then restart into AP Fastboot after holding the power button, at which point I am unable to turn on the device and need to run the "fastboot continue" command to be able to access my device again. I will also need to run said command every time I want to restart my phone.
Copying said ".p" file back caused the device to again hang at the "Warning: Bootloader Unlocked" screen before I held down the power button which cause it to run AP Fastboot, at which point I could run the "fastboot continue" command and access my phone again.
Suffice to say I'm in a bit of a pickle and am a little lost as to how to get myself out of it. Any help would be greatly appreciated!
- J
The recoveries you should be using are here( TWRP for kitkat second from the bottom works the best) you can either fastboot flash or use rashr/ flashify available on the play store...
We cannot teach people anything; we can only help them discover it within themselves.
4502
I used the TWRP2710-RAZR_M-KITKAT.img and used the Fastboot command to flash it. My phone still isn't liking fastboot commands except for a few, but rebooting into recovery from the boot selector menu now works like a charm. Thank you!
- J
So, now I have the TeamWin Recovery Project functioning, however now I'm unable to flash any ROM. I've wiped the whole device using the advanced wipe feature, attempted to flash an official version of Cyanogen mod (namely 10.2-something,) and an official version of PacMan Rom. Both give me a failed error message whenever I try to flash them. I've just downloaded a fresh nightly from http://forum.xda-developers.com/showthread.php?t=2735565 from 25.08.2014 and I'm going to see if that does the trick. If that doesn't work, much as I'm anticipating, do you have any suggestions? (Also, would I be better off starting a new thread as this is pretty much a secondary issue?)
- J
Never mind! I was actually able to have a friend show me how to properly wipe a device before flashing a custom ROM and now it's functioning properly. Thank you again for your help!
In case someone else has this issue, how I wiped was first a Factory Data Reset, then an advanced wipe for the Cache and the Dalvic, then flashed the ROM and GAPPS, then wiped the Cache/Dalvic again, then actually rebooted the system and it started right into Cyanogen mod.
Yep, I tend to wipe each one(FDR & system+dalvic+cache) 3 times tho I don't think that's really necessary I just wanna be sure it got it all... Happy you got it all working
We cannot teach people anything; we can only help them discover it within themselves.
Let me know if this post belongs somewhere else.
My Mi A1 is stuck in a bootloop as a result of trying to install magisk 14.4. At the moment I can boot it into fastboot mode, but not into recovery mode. In fastboot I can execute the command
fastboot devices
that returns the hex number followed by "fastboot." However, it does not respond to any other fastboot commands, e.g.
fastboot reboot
fastboot oem device-info
I have been attempting to flash the stock rom without success as follows:
in win10 32-bit environment:
fastboot responds as above. I cannot install the MiFlash-2017-7-20 version. Windows complains. I conclude that version must be a w10 64-bit app, although it doesn't say so.
win10 64-bit
MiFlash-2017-7-20 installs and runs, but does not see the device. Apparently, the adb drivers are at fault. I have turned off signature enforcement and tried installing various versions of the adb drivers. The device manager shows them as installed, but reports that they cannot start.
Centos 7 linux
Adb drivers install. "Fastboot devices" reports correctly. All other fastboot commands fail, i.e. they hang. I tried installing the tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image using the linux shell script provided, but that just hung also.
Is this phone well and truly bricked at this point? Is there any other recovery available?
I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.
Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works
GalihBK said:
Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works
Click to expand...
Click to collapse
As he said, he can't execute fastboot commands so that isn't a option.
@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.
The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps
Edwin Hamal said:
I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.
Click to expand...
Click to collapse
1. I tried this method to boot into EDL with no luck. Is there any other way?
C:\Downloads\xiaomi mi a1 root>adb reboot edl
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
2. On my win10 32-bit installation I am able to run MiFlash-2017045. It reports the device. I attempted to flash this image:
tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794
It completed and reported "success" however it did so in only 7 seconds, so it must not actually have succeeded. In any case the phone still will not boot.
3. However, I distrust MiFlash 20170425 because it comes from an androidmtk.com site and the processor is Qualcomm, not Mediatek. So I attempted to install MiFlash2017-07-20. However, that program will not install on my win10 32-bit installation. There is a Windows msg saying it cannot be installed, but does not give a reason. I suspect it is a 64-bit program. So, I installed MiFlash2017-7-20 in a win 10 64-bit installation. The program does run, but it does not see the device. I suspect that the adb drivers do not install correctly. I did turn off signature enforcement and the drivers appear to install, but the device manager reports that the drive cannot start.
The tissot images include bourne shell scripts to install, so I installed the adb drivers on my Centos box. Fastboot reports the device, but just as in win10 no other fastboot commands work. So, even though I did try to execute the install_all.sh script, it just hung on the first "fastboot getvar product" command.
So, I do not have a way to flash the stock rom.
_mysiak_ said:
@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well
Click to expand...
Click to collapse
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.
dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Use fastboot commands manually. Mi flash tool is very buggy. Many time it doesn't work.
_mysiak_ said:
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.
Click to expand...
Click to collapse
Did the command:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot getvar product 2>&1 | findstr /r /c:"^product: *tissot" ||
"Missmatching image and device"
So this is a little interesting. However, I don't think that the image is actually the wrong one, but that the script cannot get the device info since both "fastboot getvar product" and "fastboot oem device-info" fail on a timeout.
zazzy24 said:
The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps
Click to expand...
Click to collapse
When I do that it just keeps going back to the "no command" screen. I think the recovery image is either damaged or gone.
yuoip said:
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.
Click to expand...
Click to collapse
1. & 2. It sounds like you don't have installed fastboot drivers (install them manually via device manager) or phone isn't connected in fastboot mode (make sure there is a picture with fastboot written on the phone).
3. this IS the recovery mode, just press power + volume up again to show the menu
4. you won't see ADB devices in fastboot or recovery mode, unless you enable ADB sideload from recovery
Device Manager shows:
Android Phone
yuoip said:
Device Manager shows:
Android Phone
Click to expand...
Click to collapse
Wrong drivers then, it should say Android bootloader interface. Reinstall them correctly.
1. I did the manual install, but I don't see anything labeled "fastboot driver."
Device manager now reports:
Android Phone
Android ADB Interface
Android Bootloader Interface
Android Bootloader Interface
Android Composite ADB Interface
However, all these entries have a warning symbol on them. The Device status for each is:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Is one of these the fastboot driver? Apparently not, since the behavior of the fastboot command hasn't changed.
When I try using the fastboot command the A1 shows "Fastboot" with the rabbit character and the sick robot.
I should mention that in the Centos environment I have installed the android-tools package, which include adb and fastboot drivers and tools. The behavior of the fastboot command there is the same.
So, this leads me to believe that the problem is the A1, not the windows or linux environment, but I don't know enough to know for sure. Also, I would assume that if the fastboot drivers were not installed, the command "fastboot devices" would fail, but it doesn't.
3. At the "no command screen" if I do press and hold the power button and then the vol. up button it boots right back into the "no command" screen. There is no menu.
4. With no recovery menu I can't set any options.
Uninstall/remove everything with android name in it, disconnect phone, reconnect phone in fastboot mode. Make sure that there is only one item under Android Phone - Android Bootloader Interface. You should not see 4 devices - do you have Android emulator running or anything else connected?
When in recovery, do not hold power + volume up, just press it briefly. Sometimes it takes few tries to show the menu, but I can assure you that it's there.
Yes! You're right. The recovery menu is indeed there. I didn't know that it had to be a short press to bring it up. Thanks.
Device manager now shows only one "Android Bootloader Interface" entry. I am not running any emulator.
So now what do I do? Do I need to flash the tissot... image? The fastboot command still behaves as before.
Quick Google search suggests to avoid using USB 3.0 ports. So..maybe try another ports on your PC..?
I unlocked my bootloader. Unlike any other moto g5 plus device it shows bad key on startup. I entered into fastboot mode and tried to flash twrp recovery. I get FAILED (data transfer failure (Unknown error)) msg every time. I tried to enter recovery mode both by pressing button and enter command. What should I do now. I really need to install twrp recovery.
Screen Shots :
https://photos.app.goo.gl/ZixyDYUwG8egLT8U8
https://photos.app.goo.gl/PFPHQ2S21b7hwBhj6
https://photos.app.goo.gl/ek7yNoF7HBQJtAme9
1) Are you using the original USB cable, or a high quality data cable?
2)Have you tried using other USB ports on your computer and do you have the latest minimal ADB/fastboot (https://forum.xda-developers.com/showthread.php?t=2317790 ) or the Google ADB tools? https://developer.android.com/studio/releases/platform-tools If you're on Windows 10 or 8.1, do you have driver signature enforcement disabled? https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
3)Bad key or N/A on boot is normal when your bootloader is unlocked. If you want to hide that, you could try to flash a custom logo.bin via fastboot (or TWRP if you get it working).
Hello,
yesterday I accidentally entered fasboot mode by pressing the button combination on boot.
My phone is now stuck in fastboot mode and I can't figure out how to get out.
I've installed fastboot and the appropriate drivers on my computer (W10), but if I try 'fastboot reboot', the phone boots straight into fastboot mode. I tried formatting the cache and rebooting, but still got the same result. If I switch off the phone by holding the power button and then turning it on again (tried with every button combination), it only boots into fastboot. I even tried letting the phone run out of power, but when I charged it a bit and switched it on again, it went to fastboot again.
My phone is unlocked and rooted and has Havoc OS installed.
Any help is greatly appreciated.
Have you tried fastboot continue? You may want to spam that command for good while.
It should be written on the screen how to get out of fastboot mode, press and hold power button to shutdown the device. How exactly can't you boot to the system?
XDHx86 said:
Have you tried fastboot continue? You may want to spam that command for good while.
Click to expand...
Click to collapse
Haven't tried it before.
After typing it, I get an error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: 00000050)
finished. total time: 0.316s
What is located at 00000050?
I probably have to reinstall something, I'm just not sure what. Recovery/Bootloader/OS ?
XDHx86 said:
It should be written on the screen how to get out of fastboot mode, press and hold power button to shutdown the device. How exactly can't you boot to the system?
Click to expand...
Click to collapse
Yes, it says to hold the power button. This switches the phone off, but after starting it again it automatically goes into fastboot.
Thanks for your replies, Slllingy
Slllingy said:
Haven't tried it before.
After typing it, I get an error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: 00000050)
finished. total time: 0.316s
What is located at 00000050?
I probably have to reinstall something, I'm just not sure what. Recovery/Bootloader/OS ?
Yes, it says to hold the power button. This switches the phone off, but after starting it again it automatically goes into fastboot.
Thanks for your replies, Slllingy
Click to expand...
Click to collapse
Your device is bricked as it can't load or authenticate the boot image, you need to unbrick it.
Flashing the stock image should work. Of course don't forget to backup your data through TWRP.
I downloaded the stock firmware from ASUS, but it's a zip file and the only .img contained is boot.img.
I tried erasing all the partitions (chache, data, system, boot, recovery) and flashing the stock boot.img (from ASUS) and the lastest TWRP recovery img (specific to my phone).
I no longer get the "Failed to load image from partition..." error, but after fastboot reboot the screen turns off, then it turns on, warns me that my bootloader is unlocked, shows the android logo, then the asus logo, then it turns off again, then on again, briefly shows the androif logo and goes straight into fastboot. Basically the same happens when I manually switch the phone off and turn it on or with fastboot continue.
I can not access my reccovery.
Where can I find a sytem.img file to flash with fastboot?
Or is there any other way to unbrick my phone?
Thanks again, Slllingy