Tried various cables and still nothing. Any ideas on what I can try? I have flashed the device with no issues in the past so idk why this is happening now.
Related
So I know there's a lot of posts here with a similar situation and I tried to find a solution but I'm at my wit's end.
I recently tried updating my KF using the Cyanogenmod built in nightly update system. When it rebooted after downloading I got stuck in this boot loop for TWRP. It shows the "teamwin" logo, then the screen flashes and it's back to the logo again.
I can connect via adb but unfortunately my device is unauthorized. Obviously, since I'm stuck at this logo I can't authorize it manually on the KF.
I definitely have the latest version of adb as I just downloaded/installed it from the SDK manager seconds ago. I installed all the drivers and added the blurps of code to the Google USB driver and the adb_usb.ini. I tried deleting the adbkey files and restarting adb. I tried different USB cables and different USB ports on my computer. All this to no avail.
Anyone have any ideas besides buying a fastboot cable? That's the only thing left that I can think of to do.
bump
Guess I'll try getting that fastboot cable...
I had the same problem. The only solution that worked for me was buying a fastboot cable and then re-flashing the TWRP recovery img.
tawpa said:
I had the same problem. The only solution that worked for me was buying a fastboot cable and then re-flashing the TWRP recovery img.
Click to expand...
Click to collapse
Yep, I just received mine and did the same.
Even though I can enter fastboot mode on the watch, a "fastboot devices" on the PC doesn't show the device.
Nothing has changed on the PC (drivers, USB cable, etc) since it last DID work.
This has happened previously but I could always get around the problem by simply entering recovery mode and then re-entering fastboot mode.
Now (because of a bad flash) my recovery mode has reverted back to the VERY basic one that only has 5 possible selections.
None of the menu entries provide direct reboot to fastboot mode (which if formerly did).
So, my "trick'' mentioned above no longer works.
A separate issue is that the version of software I (accidentally) flashed is known the be unable to pair thru bluetooth to the phone.
I LOVE this watch, but they are getting harder and harder to find a replacement (if I can't get this one recovered). SO PLEASE try to help.
Boowho??
I'm sorry to revive this post, but the issue is pretty much the same as the above issue. It boots up normally, isn't visible in bluetooth, shows up as Gear Live in device manager, shows up as "unauthorized" in Restore Tool, will not reboot into fastboot using either the tool or the command prompt, and doesn't show up when manually put into recovery/reboot. I have read every post I can find (many of them multiple times), did everything I can to my drivers, and bashed my head into the wall too many times to count. Any help and/or advice is greatly appreciated.
Hey!
So i'm making this post after battling over 4 days with my friends old oneplus 3t.
All started maybe year ago when my friend asked me for help because his oneplus had suddenly gone into a bootloop kind of state (he told me that the phone was in his pocket working fine and when he tried to use it next time it started acting up.) Before i could even help him he had already bought new iphone, so the oneplus stayed in his drawer until last week when i remembered it and started to try to fix it.
So first thing that i noticed was this message "The dm-verity is not started in enforcing mode and may not work properly", the message eventually went away and i got to a recovery mode and thought that this is gonna be easy, hooked the phone to pc and started adb and tried to sideload the official rom from oneplus site, but everytime i tried it went to maybe 47 %or 66% and failed eventually. So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
Downloaded Oneplus 3T unbrick tool v3.0, and qualcomm drivers (turned windows driver signature off) everything went great and the green text came in oneplus unbrick tool and i proceeded to start the phone in excitement and the circling bootlogo started and it just stayed there, nothing, and after while shut down.
Things tried now:
-Sideloading (many times with different roms) no success.
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
- Unbricktool v3.0 (Works like a charm everytime, but phone doesent still boot to os) no success
-recovery (wiped cache and all data many times) no success
My friend never flashed anything to this device, he doesn't even now how to do this kind of stuff.
Phone not dropped even once, is in a perfect condition and has all the original stickers even.
I have grown obsessed to fixing this phone, so any help is greatly appreciated :laugh:
onlyoneplusproblems said:
So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
Click to expand...
Click to collapse
I haven't personally ever had to use the unbrick tool, so I can't help too much with the core problem. But what I can say, is that the steps I've quoted above (trying to flash recovery partition, etc.) are going to fail by design, since the bootloader is locked. This is the very purpose of the locked bootloader. The expected result is "remote: not allowed".
And as far as I am aware, you have to have a working OS and have "OEM unlocking" first toggled on, in the phone Developer settings. Otherwise (again, by design) the "fastboot oem unlock" command is going to fail.
Spontaneous failure of the phone to boot to OS, and dm-verity warning, to me probably indicates the OS has become corrupt/damaged. The damage is showing as a change to the system, therefore the dm-verity warning. Normally, I would tell you to flash the stock recovery image. But of course you have already tried that. Probably difficult to determine for sure. but spontaneous failure, and failure to flash recovery image (multiple times) may indicate a hardware failure such as bad emmc.
(I couldn't find this exact problem on the forums, forgive me if I overlooked it)
I tried booting my mom's old phone, an HTC Desire 626G, but it is stuck in a bootloop. When I try to enter recovery mode (by pressing power + volume down), it just enters the loop again.
I can however enter what I think is the bootloader menu, giving me three options: recovery, fastboot or normal boot. Fastboot freezes the phone, the other two options just start the bootloop. I've never installed a custom ROM.
I disassembled the phone, un- and replugged the battery to no avail. I tried ADB but I never enabled USB debugging in the first place, so that doesn't work either.
Do you have another idea that might work?
dulfried said:
(I couldn't find this exact problem on the forums, forgive me if I overlooked it)
I tried booting my mom's old phone, an HTC Desire 626G, but it is stuck in a bootloop. When I try to enter recovery mode (by pressing power + volume down), it just enters the loop again.
I can however enter what I think is the bootloader menu, giving me three options: recovery, fastboot or normal boot. Fastboot freezes the phone, the other two options just start the bootloop. I've never installed a custom ROM.
I disassembled the phone, un- and replugged the battery to no avail. I tried ADB but I never enabled USB debugging in the first place, so that doesn't work either.
Do you have another idea that might work?
Click to expand...
Click to collapse
Bro You need to flash the factory firmware using a pc with that fastboot mode.....
The existing firmware might have been got corrupted or the storage might have been damaged, since its an old device(which is very rare),
To do so u can find many articles on the internet very easily,
brokenbrain939 said:
Bro You need to flash the factory firmware using a pc with that fastboot mode.....
The existing firmware might have been got corrupted or the storage might have been damaged, since its an old device(which is very rare),
To do so u can find many articles on the internet very easily,
Click to expand...
Click to collapse
Thanks a lot, I'm finally able to communicate with my phone via PC now. Booting still doesn't work but now I can at least format the storage and hopefully flash the factory ROM.
Ok just like many of us, I have had trouble getting fastboot to work on my ROG 2 even though ADB worked fine.
Well getting annoyed I couldnt use fastboot I tired to flash omnirom from TWRP. Well that has locked me out of anything besides fastboot. Recovery doenst work anymore, and of course cant get into rom.
Ive tried using many of the suggested ADB variants all without success. I am also using the side port on the device.
Any suggestions?
When trying on another computer I do get a the usb connection sound but even on this computer (old ADB) it doesnt show any devices in fastboot.
Is there anything Asus offers that would flash automatically from the bootloader or something?
The phone even shows up in device manager (as Android) but PS and CMD cant talk to the bootloader.
Bump