Related
Hi!
Glass was working well and one day, I start the glass as usual and they are stucked in a "glass is updating" loop, forever..
I have wait a whole night letting them charging but nothing happend.
So I had a look on this thread and tried to flash XE12 factory image but I can't see my device with adb, neither with fastboot devices command with a manual fastboot start (camera+power button).
My problem is a bit different as the one in the thread above because I didn't try anything special before being stucked in this "updating loop".
I don't know what is my version of glass (XE12, XE16, etc...), I can't set the debug mode because of that infinite loop, and I don't know either if manual fastboot works well or not.
I'm on mac, get the adb and fastboot via google glass sdk after updating it and I have followed the factory reset process provided by google but I can't see my device as I said.
Does anybody have an idea about what could be wrong / what could I've done wrong?
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.
I was about to flash a recovery image to my son's generic tablet, but I issued a fastboot reboot command from adb and it now won't boot past an android splash screen. I've pulled the battery. I've tried holding the volume up key for booting to recovery. Nothing. No joy. I don't think it's possible to brick a device just by sending a reboot command. I'm assuming it's just stuck looking for a reboot recovery file of a different name. Then again, a boot loop is as good as bricked. Any suggestions?
lil_bono said:
I was about to flash a recovery image to my son's generic tablet, but I issued a fastboot reboot command from adb and it now won't boot past an android splash screen. I've pulled the battery. I've tried holding the volume up key for booting to recovery. Nothing. No joy. I don't think it's possible to brick a device just by sending a reboot command. I'm assuming it's just stuck looking for a reboot recovery file of a different name. Then again, a boot loop is as good as bricked. Any suggestions?
Click to expand...
Click to collapse
Nevermind... after a few groundings of the battery cables, it has come back from the dead. Thanks for playing
lil_bono said:
I was about to flash a recovery image to my son's generic tablet, but I issued a fastboot reboot command from adb and it now won't boot past an android splash screen. I've pulled the battery. I've tried holding the volume up key for booting to recovery. Nothing. No joy. I don't think it's possible to brick a device just by sending a reboot command. I'm assuming it's just stuck looking for a reboot recovery file of a different name. Then again, a boot loop is as good as bricked. Any suggestions?
Click to expand...
Click to collapse
I feel that I should update folks on the latest details. As it turns out, this tablet is a Chinese 'allwinner' made by Eken. It's not just hanging because of my actions. Apparently these devices do not follow proper GPL. It doesn't respond to many fastboot commands at all. Once I issued the command to boot into fastboot, and it gets into fastboot mode, it stops responding. You can not issue any commands to bring it out of fastboot either! Not something I would recommend people invest in, no matter how cheap. It also has software that I would consider malware attached to the Android browser. It literally tells you that it will track you and throw advertisements whenever it wants. Garbage.
As the title states, my phone is stuck in a bootloop, and only fastboot works. Trying to go into recovery or rescue mode results in going back to the bootloop instead of actually going to rescue/recovery mode. Any fastboot commands result in `waiting for device` even though it shows the device in `fastboot devices`.
Is there anything I can do to try to get it to work again?
I have gotten it into recovery mode before and was able to factory reset it, however when I plugged it in the phone crashed and went back into a bootloop, and now loading into recovery mode does not work.
Also if it's any help, I previously had the device rooted with magisk, I powered it off and when I powered it back on it went into a bootloop (I did not make any changes like installing/updating magisk plugins prior to shutting it down).
Update to this: I was able to install graphene os via command line.
Hey, dear community,
First of all: I'm using Linux. The Version of Fastboot is 33.0.3p1-android-tools. The device I thought I'm experienced enough to install Lineage OS on is the Asus Zenfone 8. Yes, I asked google - for hours. And I think I am really ****ed now.
Cause the Smartphone (Asus Zenfone 8) was not cheap. And it does not boot anymore. I don't get in Recovery mode anymore. And I'm not able to connect via Fastboot anymore.
But let's start at the beginning.
I was pissed, cause my smartphone forced me to use google. Even if I skipped the Google-Part in the setup, it forced me to agree to send Google information. And I read it. They (quote: may) send Google **a lot** of data. Data I don't want to share - and I don't need to share IMHO! I didn't like to use such a intransparent Device anyway - but this convinced me to try this thing named LineageOS.
I thought about myself I am not a bloody beginner. I mean, I use Linux as my daily driver - for years. And my phone (Asus Zenfone 8) was in the list of supported devices - so I had to try it. I thought if I just install these tools, adb and fastboot, and do these things in the wiki carefully, step by step, what could happen?
And it worked. It worked to unlock device, to connect via adb, to connect via fastboot. It worked to flash the vendor_boot image, It worked to flash the recovery image. But then, just before I wanted to start with the "Installing LineageOS"-part, and therefore boot into recovery mode - it didn't work. I was stuck in the bootloader. I am. still.
There are the options "START", "Restart bootloader", "Recovery mode" and "Power off". No matter what I try to enter, the device restarts (at least it looks like) - It shows "Powered by android", and then the bootmenu again. And again. And again.
When fastboot was still connected, I tried to flash the images again. I even tried to boot directly into the recovery image using `fastboot boot image.img`. But it did not work. And then, the device even stopped showing up when I ran `fastboot devices` - it disconnected.
"Power off" is the only option, wich still appears to work (when not plugged in).
What should I do? Is it even still possible to do something? Please help me.
PS: It would be nice if you tell me, wether the tools or guides you recommend to me work on Linux, in a Windows VM or only Windows Bare Metal. I will do everything to bring my phone back, but it safes a lot of time, not to try using a tool in Windows VM if it only works bare metal anyway.
May be this thread could help you
https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/
Thanks, but my phone does not get into fastboot mode anymore, therefore I cannot connect to my phone via fastboot to flash new images.
Schaukelstuhl said:
Thanks, but my phone does not get into fastboot mode anymore, therefore I cannot connect to my phone via fastboot to flash new images.
Click to expand...
Click to collapse
I had the same problem. Only bootloader with no device showing with "fastboot devices".
Luckily I tried another cable. An Apple USB C cable behind a hub (screen) got fastboot working. Then I flashed android 13 beta.
And I am sure the other cable worked before with ADB and fastboot.
Try other cables and USB ports... Good luck!