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?
Related
Anyone!!!
Please help me, i'm entirely in despair now with my HTC N1 phone.
This place or people from XDA are my only hope, and I wish was in the right place.
Here's my concern, At the first place my POWER BUTTON is not working.
I Installed CM7.2 on my phone and it went great, I decided to install a semi-transparent status bar so I flash a .zip in it. After it reboots, it was stuck at the "X" screen.
The only thing I can do is to have a battery shock on my phone while holding the track ball, and it sends me to a white screen with skating androids.
From there I tried using the Fastboot commands but I got an error saying "FAILED <remote: not allowed>"
I'm pretty sure that "USB Debugging" is checked. And I can even erase the cache from there, but when i tried the "fastboot flash recovery file.img" or any related command like that it says "FAILED <remote: not allowed>".
When using ADB commands my phone wasn't detected. I tried all kinds of USB drivers and trick already, but got me nowhere.
Also I've seen that you cannot use ADB on a white screen, how am I going to get to a non white screen if my power button is not working?
I'm entirely helpless right not. I already went to different best cell repair shop all over our country to fix my power button, since it was the root cause of my misery but even them can't help me with that.
Please help me everyone, I'm a complete noob or even a moron on this.
I'm completely helpless right now.
I'll do anything for someone who'll help me. PLEASE!! :crying:
emeryreme said:
Anyone!!!
Please help me, i'm entirely in despair now with my HTC N1 phone.
This place or people from XDA are my only hope, and I wish was in the right place.
Here's my concern, At the first place my POWER BUTTON is not working.
I Installed CM7.2 on my phone and it went great, I decided to install a semi-transparent status bar so I flash a .zip in it. After it reboots, it was stuck at the "X" screen.
The only thing I can do is to have a battery shock on my phone while holding the track ball, and it sends me to a white screen with skating androids.
From there I tried using the Fastboot commands but I got an error saying "FAILED <remote: not allowed>"
I'm pretty sure that "USB Debugging" is checked. And I can even erase the cache from there, but when i tried the "fastboot flash recovery file.img" or any related command like that it says "FAILED <remote: not allowed>".
When using ADB commands my phone wasn't detected. I tried all kinds of USB drivers and trick already, but got me nowhere.
Also I've seen that you cannot use ADB on a white screen, how am I going to get to a non white screen if my power button is not working?
I'm entirely helpless right not. I already went to different best cell repair shop all over our country to fix my power button, since it was the root cause of my misery but even them can't help me with that.
Please help me everyone, I'm a complete noob or even a moron on this.
I'm completely helpless right now.
I'll do anything for someone who'll help me. PLEASE!! :crying:
Click to expand...
Click to collapse
You don't need to flash the recovery in this situation. Try to reboot the phone via fastboot command and issue these commands in fastboot:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase cache
Once complete, just reflash the CM 7.2 ROM again.
So this morning i tried this. Kingroot didn't complete the root, some error happened, i didn't mind since i was just testing to see if i could root my phone for the first time [i've never done it before and it seemed simple enough].
I quit the app, a bunch of errors showed up, one after the other [i didn't register what exactly the windows said, i'm pretty sure it was a google application that stopped working]. The phone turned itself off.
i booted it up again, and it showed me the AP Fastboot Flash Mode screen. i know this from previously doing a factory reset, so i tried doing it again. After it wiped all of my data and custom, i tried rebooting it.
it showed me the motorola icon, but a few seconds later, i was back at the fastboot screen. i'm pretty desperate right now since this is my only phone. i tried selecting the "normal powerup" command, it didn't work. this is my screen right now:
"hab check failed for boot
failed to validate boot image
fastboot reason: fall-through from normal boot mode
USB conected
hab check failed for boot
failed to validate boot image
boot up failed"
none of the other commands, aside from Recovery, work. it takes me to the no command screen and all of the known options once i use the power+volume up command: reboot system now, reboot to bootloader, apply update from ABD, etc.
sorry if this thread reads weird, i'm sort of freaking out right now and english isn't my main language. thanks in advance to anyone who might help!
Check here
If you have questions PM me I will try to help. I got the same problem on Monday and solved it yesterday.
History of the issue at hand:
I was running a new rom that was marshmallow based. It was running fine but lost root privileges so I attempted to boot into recovery and install the stable version of SuperSU for the device. I wiped the dalvik and cache and rebooted through TWRP recovery and the system went into a bootloop. Solution: Read XDA forums to find a way to fix the device. Went on ebay and bought a fastboot cable, waited 3 weeks, cable comes in and gets me to fastboot mode, but I am running Windows 10, creating a new problem. Solution: Partition the HDD on my computer and install Windows 7 Professional. This now fixed the driver issue. Plugged in the cable, with the new drivers installed and voila - Fastboot mode.
Seems pretty easy right? Wrong. After trying several utilites, I still cannot seem to get the Kindle to get out of the current situation it is in.
The device was rooted with the 2nd bootloader added over 2 years ago. Every ROM I have ran has been successful. Every time a new ROM was used or tried a backup was done and the device wiped properly before install. I made sure that every ROM was for my specific device (Tate).
Here is what I can do:
If I power on the Kindle, it briefly shows the logo, then the fastboot logo and goes blank
If I power on the Kindle by plugging in the factory cable and quickly entering any command (it is already typed) like "fastboot erase cache" the system will remain in fastboot with the fastboot logo on the screen. My sdk does recognize the device and states it is in fastboot.
From here I have no idea where to go. I can type any command I like, such as erase cache, recovery, system or any multitude of things and the command prompt takes it time to show the device is working on the command. However, the device remains unresponsive and has the same issues when attempting to reboot. When flashing anything the target size of the device remains unchanged at 1006632960 bytes, which seems to tell me that device is receiving the command but not writing anything to the device. This probably also means that anything that is on the device causing it to continuously bootloop or fail is not being erased or properly formatted.
All I have is fastboot and time. Time to scratch my head and wonder if the device is truly and totally bricked. i am under the assumption that if I have a working fastboot that I should be able to at least accomplish something. Even if it means reverting it to bare bones stock and starting the whole process over. I will be happy to answer any questions you all have regarding the system via here or PM.
Please assist this old man and thank you in advance for your time.
Give it a try
While I wasn't in the same weird brick scenario as you. My device would show up on my pc as fastboot and or regular adb. But, I would get no video. The solution which I have no idea why worked was to pop the back cover off. Then disconnect the battery from the mobo. Wait a few seconds. Connect it back to the mobo. After that video showed back up. Then proceeded on my way.
Not sure if what I did will help you. But. Then again I didn't think simply disconnecting the battery and reconnecting it would solve video issues.
You definitely do have a weird brick scenario. Good Luck!
Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?
you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.
hey guys follow this youtube
managed to unbrick my phone
smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..
This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!
the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus
I charged my Mi A2 overnight and woke this morning to find that it won't boot past the Mi A2 splash screen; it shows the splash screen for a few of seconds and then dies. I read advice to hold down power and 'up' keys, this just resulted in the same. I tried power and 'down' key and that got me as far as the Fast Boot splash screen, but no further (phone just continued to display that splash screen). I've tried taking the SIM out and turning it on - no change. I tried opening it up and disconnecting the battery for 3 minutes - no change. I'd be very grateful if anyone could suggest a fix. I know this is hugely unhelpful, but I can't remember what I did to the phone in terms of unlocking the bootloader and/or rooting, but I have a feeling I left it stock (I've owned the phone for a couple of years and haven't changed anything material since initial setup).
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Martinocom said:
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Click to expand...
Click to collapse
Thank you very much for your help.
Executing fastboot reboot via adb just brought me back to the Android One splash screen for a few seconds before the screen went black.
Changing the active slot to both A and B gave me the following error message:
FAILED (remote: 'Slot Change is not allowed in Lock State')
Pressing up + power when turning on just brought me to the Android One splash screen for a few seconds before the screen went black. I held those two buttons down for several minutes and the same thing kept happening: splash screen followed by black, repeatedly.
Is there anything else I can try?
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Martinocom said:
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Click to expand...
Click to collapse
Thank you.
If anyone reading knows of a way to get my phone to boot without losing my data I'd be very grateful for your help.