Hi guys,
i installed the TrickDroid 2.0.0 ROM Google Edition 4.3 on my HTC One on wednesday this week, everything seemed well and worked.
Yesterday i connected it to the charger before i went to bed (original HTC charger).
Today i woke up and the green LED was on (indicating the battery was fully loaded) as usual.
I grabbed the phone but cant turn it on, the green LED stays on even after disconnecting from the charger.
Long holding the power button or even power+volume down semms not to work.
When i connect it to the computer windows makes this "something was connected on USB" sound but no device pops up in windows explorer.
I don't even know if the device is on, i cant call my self up, because i put it in plane mode before going to bed :/
Do you know this issue? What can i Do?
I can't use fastboot, it always says it's "waiting for device"
Any suggestions?
BTW: I unlocked it with the developer certificate from HTC - if it matters
Hi Again,
so the problem has disappeared magically.
I tried to hold down power and volume down again and after 5 seconds the green LED went out and the device booted up again.
I tried it like 10 times before that and it didnt work.
So Problem's solved ... i guess.
Thanks anyway!
Hello
Recently i've bought an broken screen Xperia Z, for repair it (i got it like $300 bucks cheaper) and i was ready to buy the screen, but i battery was drained and i could not test it right, when i connected to the charger, it started red light, vibrate, then 3 continuous vibes, read on the internet, OK BATTERY DRAINED, i left it charge THE WHOLE NIGHT, and when i woke up in the morning it was orange (charging), later in the day it was green (charged) but when i disconnect it, it wont turn on anyways, when i connect it to a pc, it goes blue light (wich later i read it was fastboot mode). i read for making a repair with PCC, but it didnt fixed it, then i flashed it with Flashtool, with the latest software (wich had the Sudden death issue fixed) no luck. it wont boot. for it to boot, i have to connect it to PC and with fastboot run "fastboot continue", but most of the time, it reboots and goes redlight and vibrate 3 times then reboot, so i press the power button and it enters fastboot mode (if connected to PC) or loads charging if connected to wall charger, but it reboots again and goes to redlight vibrate reboot, sometimes it stay charging or in fastboot mode, but only "works" if connected in the USB.
when it stays in fastboot, i do "fastboot continue" and it loads the OS, and it works (well, the things i can do with a broken LCD/Touchscreen, i put my sim card and could call it, and it works, but i cant pick up the call). i can explore the phone memory etc. but if it reboots or if i disconnect the USB, it will almost always turn off. i havn't found a solution (or idea) of what can happen, i dont know if its normal since it has broken lcd/touchscreen or it definitely have a huge problem,
any ideas?
thanks in advance!
Maybe the battery is damaged, and the phone knows it and boots into some sort of safe mode to spare internal damage? When the is has booted you can take screenshots with adb if you have usb debugging enabled. Maybe try see if the os says the battery is damaged?
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
heavy_metal_man said:
Maybe the battery is damaged, and the phone knows it and boots into some sort of safe mode to spare internal damage? When the is has booted you can take screenshots with adb if you have usb debugging enabled. Maybe try see if the os says the battery is damaged?
Click to expand...
Click to collapse
Well, actually it doesnt seem the battery is damaged, fisically looks ok and it holds charge, i cant debug because usb debugging comes off by default when flash stock software.
blackknigt said:
Well, actually it doesnt seem the battery is damaged, fisically looks ok and it holds charge, i cant debug because usb debugging comes off by default when flash stock software.
Click to expand...
Click to collapse
Correct me if i am wrong but does the xperia z not support usg-otg and mhl? You could rig the phone up to the tv with a mhl-hdmi cable and maybe use a usb mouse to select things, and enable usb debugging?
Sent from my Nexus 7 using Tapatalk 4
Nice idea, now i need to find who in this country (DR) have that adapter
i ordered the LCD screen assembly for repair it myself, but im still concerned about this, as i dont know if it will boot up anyways
my phone right now isnt booting. but as i cant see images i dont know what is it showing.
i noticed the touch screen is working indeed. (when booted, it plays sounds when tapping)
i will wait till the lcd assembly arrives. any ways, any other ideas on what may happen?
the ex-owner of the phone said it started like that when it fell and broke the lcd.
OK now, i've installed the LCD, the phone works, its ON, BUT the Volume Up button and the Power Button does not work when the phone is ON,
the Vol UP button seems always be pressed cause when i press the power button for some seconds, the Phone restarts and not power off or lock/unlock
Service tests: None of these buttons where recognized.
any ideas on any hardware fixes i could try?
I FIXED IT!!
dissasembled the phone, took out the side button flex cable and the volume up button on the flex was dirty, so it was having a false contact. (wich made the button always be pressed)
I took out the yellow tape and cleaned with alcohol and a needle (its so freakin small) and put the tape again and assembled the phone and voila! IT WORKS OK!!
Yes the vol up button pressed means u get fastboot. Now that you fixed the problem and repaired the phone enjoy. Btw nice job getting it up and running.
[email protected] Z
I have a standard SM-N700 Galaxy Gear and had it running null. All seemed fine until one night after a notification tried to come to the watch, the screen flashed white and the watch appeared to shut down. Since then, it hasn't been able to turn on for anything. Below is the steps I've taken to try to recover my smartwatch...
Tried using multiple power supplies, no response (one power supply even caused the charging dock to become a little warm)
Tried holding power for 10 seconds, no response.
Tried repeatedly holding/pressing power (I heard sometimes this can help clear a softlocked device), no response.
Opened the watch and disconnected the battery. When the watch was reconnected, it vibrated once as if it was going to turn on, but didn't do anything further. Repeated attempts at removing the battery had no response, not even a vibrate.
Tried connecting the watch to my PC, the computer beeped that a device was connected and reported that there was no driver for "sec s5pc210 test b/d". I checked and the standard Samsung USB Drivers are installed. Tried other USB cables and USB ports, either the computer gives the beep of a malfunctioning USB device, or beeps as if something connected, but then the device seems to disappear.
I've read some resources that suggest that either the watch is completely fried, or somehow during an update to Gear Manager, it corrupted or damaged the bootloader of the watch, and after the watch attempted to reboot, it failed and got stuck in the condition it is in now. Based on these resources, there's supposed to be a way using Odin to flash a proper bootloader to the device, but since it does not appear to stay connected for more than an instant, and when it does connect it appears as this "sec s5pc210 test b/d" device, the tools I've tried to flash the bootloader have failed.
I really don't want to have to replace this device. Having a Samsung watch that still runs plain Android is not something I want to give up.
Hello,
I'm attempting to use hardware key combinations in order to boot into Fastboot mode, e.g.. Power + volume up & power + volume down.
The phone is unresponsive. But the phone boots normally when only pressing the power button.
I've read the tutorial about launching Fastboot through a PC connection here: https://forum.xda-developers.com/rog-phone-2/help/howv-to-phone-fastboot-mode-screenshots-t3966727
But in this case, that wont be an option since my display doesn't work, hence there's no way to accept ABD-permissions when prompted on the phones' screen.
I was initially trying to pull all the data from the phone through ADB. When I realized I hadn't accepted my PC's ADB permissions on my ROG Phone, I had to rethink..
So I thought I could plant my PC's RSA-key (for accepting ADB) in my ROG Phones storage through Fastboot, just pushing the file.
I was dumbfounded when I discovered my ROG Phone 2 to be the only android device I've owned, which seemingly doesn't allow for a raw manual boot into Fastboot? CAN THIS REALLY BE THE CASE?
Any input would be highly appreciated
EDIT: I've ordered an USB-c hub for inputting kb+m & HDMI, which should allow me to accept the permissions. Although some of the data I'm trying to reach are time sensitive, any second rescued would be of value!
Similar problem
Hello,
I have a similar problem. My display is broken but the phone seems to still work. I bought an USB-C hub, but when I connect the phone to the TV (via the side USB port) it only shows a white "Asus rog" logo for a few seconds and then vanishes. When I click the mouse the logo reappears again for a few seconds.
Did it work with the hub you got? Do you have an other idea? I need the data that ist sadly still on the phone.
Thank you for your help.
Kraid13 said:
Hello,
I have a similar problem. My display is broken but the phone seems to still work. I bought an USB-C hub, but when I connect the phone to the TV (via the side USB port) it only shows a white "Asus rog" logo for a few seconds and then vanishes. When I click the mouse the logo reappears again for a few seconds.
Did it work with the hub you got? Do you have an other idea? I need the data that ist sadly still on the phone.
Thank you for your help.
Click to expand...
Click to collapse
I did work with the usb-c hub. Never saw any white ASUS ROG logo, I'm not sure what's going on with your phone. Also I later replaced the screen third-party, since ASUS charges a lot of money and insists on factory reseting the phone. So you could always do the latter if nothing else works. Send me a PM if you want the display I got.
My phone went to an endless bootloop after a botched attempt to install TWRP. I tried hard pressing the power button to no avail, and I can't access fastboot either. That's why I removed the back cover and disconnected the flex cable from the battery on the phone's motherboard.
Later on, I reconnected my phone's battery after my shift ended, then I tried to flash my stock rom through SP Flash Tool + bypass tool python script and it went through with a success. However, this time, my screen seems to be completely dead but my phone is still showing some signs of life (short vibration when pressing the power button, but since then it seems that it takes a few seconds more from pressing the power button to turn it on. ) I reconnected and disconnected everything to see whether or not I missed out something but the issue still persists.
The computer reads the device as "Android ADB interface" and the adb console reads it as *device id* unauthorized when I ran adb devices command. There's no notification light whenever I plug it into the charger.
Is my screen dead, or is my motherboard toast? I need to know as I don't want to spend money to buy a replacement LCD only to know that the motherboard's dead. I don't really care about the IMEI as I'm just going to use it as an authorization device for work. I can just always connect to Wi-Fi. Please advise.
One problem after another, so it seems.
Turns out I already unbricked the phone, but the thing is that my display's backlight got busted for some reason. Unless I shine a flashlight through it, I won't know what's in the screen. I'm currently on the way to get a replacement screen, and a new battery cover.
I guess this will be the last Xiaomi device that I'll ever get. This is the only time that I experienced such flimsy build quality since the LG G4.
Maybe you have destroyed a lil cable or something.