Hi Guys,
So I have successfully S-OFF'd my device using rumrunner, and I was then using the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2358781 in order to flash my device to a Google Play Edition device.
It worked fine for the commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip
and then I got the expected error message. I then entered the same command again as instructed, but this time I got the message "waiting for device" which didn't go away.
I've tried rebooting my phone a few times, and I can no longer get any fastboot.exe commands to work, I just continuously get the "waiting for device"message. adb.exe still works correctly, so after rebooting my phone I can use adb to boot into fastboot (I know that's not the only way, I'm just saying it to demonstrate that adb appears to be fine) but after that no fastboot.exe commands work anymore.
My phone is running Software version 3.62.401.1. My Hboot I was very sure used to be 1.55 but now after that failed "fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip" it now shows as HBOOT 1.54.
Thanks guys, any help would be immensely appreciated.
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
SaHiLzZ said:
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
Click to expand...
Click to collapse
Trying another fast boot package didn't work, but a different computer did. Now I'm all set and ready to go thanks!
Just for the record, on the first computer my phone no longer showed up when I put in fastboot devices. I guess for some strange reason there's now a problem with the drivers on the first computer? I thought perhaps reinstalling HTC Sync would help that apparently not.
Anyways, that problem is solved until I want to do this again and want to use the first computer again.
I have two H811, mine and my wife's. I managed to root and install TWRP fine on mine via adb/fastboot with no problems but I can NOT get my PC to see the other H811. I can see it in the LGUP app just fine. I see it in device manager just fine. But, from the cmd box, I get nothing when I type "adb devices" or "fastboot" devices. Dev options are enable, OEM unlock checked and USB debug works because I can see it in my file explorer. I've rebooted both devices a bunch of times after disabling and reenabling stuff. Still, nuthin'.
Any suggestions?
EDIT -- After much muckin' about with reinstalling devices and drivers, I finally got adb to see the H811. Fastboot still doesn't see it though.
EDIT 2 -- It dawned on me that I have to be in the bootloader (I think) before I can use fastboot. At least fastboot sees the H811 and I can issue commands to the device. However, I can't flash anything to it.
After all the above stuff, I FINALLY got to flash SuperSu! Seems there's been some changes in the latest command verbage in fastboot. Since I've been using it, it's always required something like "fastboot flash recovery recoveryimagename.img" With the latest version, the word "recovery" is no longer required. Once I got it up and running, I flashed TWRP using Flashify. YMMV
hi, here goes my problem:
i had flashed stock oreo firmware (posted here on xda) together with a magisk-patched bootloader, all done via fastboot. my bootloader is unlocked, the device drivers on my win10 pc were working back then and i was able to boot the bootable twrp img.
i also had used one magisk module, namely app systemizer. but after updating it and rebooting, something went wrong (probably fault of magisk or the module), and i can't boot into system, it always gets stuck o the M logo.
i've still got fastboot, my pc correctly detects the phone is in fastboot and connected, and the phone sees the connection too. i am able to send commands like reboot, but whenever i try to tell it to boot a boot.img from my pc (stock img, magisk patched img, or twrp img), it always either gets stuck on loading the file, or straight up says that it failed - (remote: unknown command). the same happens with commands like erase and flash.
can anyone help me get it working again?
thanks
Hey.... I experienced the same thing yesterday.
Have you got it fixed cause this thread is 10 days now.
The solution was to go to the recovery and factory reset and the phone will work. Weirdly, it still had root and magisk app worked without a hitch. I restored all the apps and started working from today morning.
None of the commands were working in Fastboot mode, cant send files or execute something. Someone here has to explain this or we have to revert it back to stock image (which will kaput the root of course) and then try the flashing and see if it will work out.
After busting my head for 6 plus hours i am back again with the phone with root. I installed 4 modules and used the latest Magisk.
Tommylee567 said:
Hey.... I experienced the same thing yesterday.
Have you got it fixed cause this thread is 10 days now.
The solution was to go to the recovery and factory reset and the phone will work. Weirdly, it still had root and magisk app worked without a hitch. I restored all the apps and started working from today morning.
None of the commands were working in Fastboot mode, cant send files or execute something. Someone here has to explain this or we have to revert it back to stock image (which will kaput the root of course) and then try the flashing and see if it will work out.
After busting my head for 6 plus hours i am back again with the phone with root. I installed 4 modules and used the latest Magisk.
Click to expand...
Click to collapse
i got it fixed the same way.. my issue was caused by a bug in the shell app systemizer module, i reported it to the dev.... still really strange that it'd render fastboot unusable
No Solution
I still didn't find a solution to the fastboot problem in Windows. but using Linux system (present i have Manjaro linux installed) had solved it as i entered the commands step by step and flashed it.
And still I am having partial letters missing in reply I get from fastboot commands.
Ex: fastboot boot boot.img i will get something like suffix-slo:not found..... etc with missing letters on the screen.
So using the fastboot flashing script for Moto phones i flashed a stock firmware and started fresh with a good ol' stock boot.img file and still the fastboot commands work here and there. After few times of rebooting it works well. Then goes back to the same problem.
I don't know what is the matter with it but I learned my lesson of backup and never am gonna miss that step out (at least I had Titanium Backup done before the first shot).
BTW, i found what was the problem in Magisk module. It froze up in the Magic Charging Switch module. So re-flashed everything and back to normal.
Rooted and Magisk running well again.
I hope there won't be any flashing necessary soon for me :laugh:
I have what seems the same problem: "fastboot boot twrp.img" fails, either hanging on downloading, or simply failing with "remote: unknown command". I am also rooted with Magisk, no modules.
The kink is that on a different PC, it works fine. As far as I can tell, same software setup: Minimal ADB and Fastboot 1.4.3 + drivers installed by Motorola Device Manager 2.5.4 on both (Win10) PCs. So I'm not inclined to factory reset.
Frustrating.
edhaswell said:
I have what seems the same problem: "fastboot boot twrp.img" fails, either hanging on downloading, or simply failing with "remote: unknown command". I am also rooted with Magisk, no modules.
The kink is that on a different PC, it works fine. As far as I can tell, same software setup: Minimal ADB and Fastboot 1.4.3 + drivers installed by Motorola Device Manager 2.5.4 on both (Win10) PCs. So I'm not inclined to factory reset.
Frustrating.
Click to expand...
Click to collapse
Do you guys now if the error occur on a AMD "Ryzen" CPU?
I have both Amd and Intel desktops and on the intel works just fine on ever try, on the amd cpu I have no sucess till now.
btotta said:
Do you guys now if the error occur on a AMD "Ryzen" CPU?
I have both Amd and Intel desktops and on the intel works just fine on ever try, on the amd cpu I have no sucess till now.
Click to expand...
Click to collapse
In my case the non-working machine is a new Ryzen build, while the one that works is an older Intel. Shouldn't matter, but hmm...
edhaswell said:
In my case the non-working machine is a new Ryzen build, while the one that works is an older Intel. Shouldn't matter, but hmm...
Click to expand...
Click to collapse
Yeah, I think the same, but the problem it's with the USB drivers on the Windows 10 for ryzen. If you run windows 7 with the USB drivers from AMD will work normally.
I have done some research about it and find some guys that manage to install the drivers from windows 7 on windows 10, but for me just broke everything and I have to format the PC.
Tommylee567 said:
I still didn't find a solution to the fastboot problem in Windows. but using Linux system (present i have Manjaro linux installed) had solved it as i entered the commands step by step and flashed it.
And still I am having partial letters missing in reply I get from fastboot commands.
Ex: fastboot boot boot.img i will get something like suffix-slo:not found..... etc with missing letters on the screen.
Click to expand...
Click to collapse
I have similar issue with the same error message.
But in my case, the issue shows up on Ubuntu Linux. It works fine on another PC with Windows 7. Both are using fastboot r28.
The issue still persists even after re-stock, I still need to use Windows 7 (for any fastboot operation). Both PCs are Intel.
I also had a lot of errors with fastboot, which used to work perfectly some time ago. I too was frustrated and was searching for it. Just as a test case, I decided to use an older version of platform tools and voila all fastboot commands ran smoothly without a single error. I was getting all kinds of errors with platform-tools_r28.0.1-windows (downloaded directly from https://developer.android.com/studio/releases/platform-tools.html). I used older version 27.0.1 and everything working perfectly. I use win 7 x64 (intel). Maybe this will help some of you, or maybe I was just lucky and fastboot version is not the issue but something else, but as long as older version is working for me, I will be using it.
Cheers.
anonyo said:
I used older version 27.0.1 and everything working perfectly. I use win 7 x64 (intel).
Cheers.
Click to expand...
Click to collapse
linux r27.0.1 doesn't work for me. I don't think any version would work for my linux pc.
Was the final fix for this to just factory reset? I'm tempted to try booting to the recovery image on my home machine first but didn't want to mess with it if there's no point.
Update: since recovery was still accessible (Lineage OS recovery), I was able to ADB sideload TWRP, which then allowed me to push a new OS.
I have had this same problem since I got the phone. Fastboot works on my ryzen desktop, doesnt work on intel laptop. both are running latest linux mint
Hi all,
First of let me start by saying I have a Mi 9T and I know that it has its own forum, but I didn't find a solution to my problem there, so I thought I'd ask in this forum as well, since the devices look a lot like each other but here are more people.
So my problem is I got stuck in a bootloop which I can't seem to get out of. I can boot into fastboot mode and adb fastboot AND Miflash recognize my device, so I'm able to flash things, but the bootloop still stays.
I started on global rom, and then installed twrp. Then I flashed the latest 9.7.25 ROM from mi-globe for MI 9T. It booted up fine, but my TWRP was removed and I couldn't install it anymore like the first time. For some reason I did a factory reset then. And tried to flash a new ROM by using MiFlash. It said it was succesfull, but it only took 1 second and it didn't automatically boot (it stayed in fastboot mode). I tried again and it said anti-rollback error.
So that didn't work, so I tried flashing boot.img, recovery.img and system,img seperately by using adb fastboot. That worked and it booted normally. I went through the startup configuration like selecting wifi network and gmail,etc. But after trying to set a fingerprint, the screen went completely black but the phone was still on. I could reboot it normally, but when the lockscreen came up or I tried to use fingerprint scanner it went black completeley every time.
I was desperate, so I used 'fastboot erase system -w' in adb fastboot, which is a factory reset apparently. Then I flashed the 3 .img files like I did before, but this time it didn't boot, but went into bootloop.
I also tried 'fastboot boot twrp.img' which also didn't get me into twrp, it just goes to bootloop again.
So to summarize: I CAN get into fastboot and adb fastboot and miflash DO recognize my device, but I can't get out of bootloop no matter what I flash.
Does anyone know a solution for this problem? I would be very thankful.
I also don't understand why flashing or booting TWRP doesn't work, while it worked the first time. I also don't understand why flashing the 3 .img files doesn't work this time, like it used to work the first time.
Btw my anti getvar is 1.
Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working
DaveHTC200 said:
Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working
Click to expand...
Click to collapse
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?
Rapydax said:
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?
Click to expand...
Click to collapse
I've not had your issue but that was causing the flash tool to just carry out the task in 1 second, which isn't possible
i have the same situation here. did your issue solve?
EDIT3:
Resolved! I changed the usb port on my computer... Weird problem as adb worked fine over the old port. What I say about having relocked the bootloader below is wrong. I just assumed I had because my system said so and I didn't see the scary letters at startup. Leaving this here in case it helps future idiots.
Excuse me if this is a dumb question. I'm not too familiar with how this is exactly supposed to work.
I tried to update and messed up (of course) so I had to do a full reset which relocked my bootloader. Now I have a locked device on the latest software but I can't see the device in with `fastboot devices` anymore. Thus I can't unlock the bootloader again.
I'm running the apt installed version of fastboot on ubuntu.
EDIT:
I did find the oem unlock toggle in settings but it's greyed out.
EDIT2:
`lsusb` is also recognizes nothing in when the device is in fastboot mode.