Technically this is about the New Padfone Infinity (A86), but I'm not sure where else to turn...
So I forgot to charge my phones battery over night, so the next morning it was turned off, I put it inside the station, it booted, but when it got to the lock screen, Android nicely shut down the phone...
From that point on I haven't been able to turn on the device:
-No screen
-No recovery
-no fastboot
-No vibration
-Nothing
So first thought, a dead battery right? But when I connect it to my PC, it's recognized as an Unknown Device...
I tried pretty much every Asus driver/Google Driver that I could find, but nothing...
Does anyone have any suggestions?
After reconnecting the battery it's recognized as QHSUSB_BULK. A Google search tells me that this is a Hard Brick, any advice which tutorial I should use since there are several...
Related
I've seen many posts about this but none of them actually has a solution that worked for me.
I have a Sensation XE, I don't know the cause of the problem exactly, but I had it on recovery and it discharged (deep discharge).
Now whenever I try to turn it on, the red led on the left top corner turns on, sometimes the device vibrates, but the screen stays off.
I tried to go into bootloader but with no luck, same for recovery.
The charging orange led does light up when the device is plugged in, and I've checked the battery, it's functional. I even tried another battery just to make sure.
I tried to charge it overnight, and I tried to charge the battery on it's own, with no luck.
One thing I found right before I post this is charging the phone with the battery out!
Now I don't know how that might help as the device doesn't boot with no battery, but I tried it anyways just to make sure I haven't left anything to chance, and it didn't work.
This thread might come in handy for other people with the same situation.
Windows 7 recognizes the device when plugged in as "Android ADB Interface" but when I use "adb devices" it doesn't show anything.
I tried the Sensation Unbricking Project, the terminal always said "Bricked device found on." but it doesn't give me the next line "sdX", I think it doesn't recognize the device.
In the video when the device is plugged in, Ubuntu immediately recognizes it and it even opens up the device's files, that does not happen with my device.
I don't remember exactly my bootloader information, but I think my HBOOT version is 1.27, not sure about that.
I have bootloader unlocked with S-ON, and I had a custom ROM running for over 3 months when all this happened.
I hope you have all the info you need to help me, if not just ask me, any help would be much appreciated.
Thanks in advance.
Hi,
long story short: I connected my Z5C to a bad (apparently, I don't want to test ) charger and now I have some strange issues. Is there any change that my h/w isn't fried?
Full story: As I said I connected my Z5C (newest CyanogenMod provided here) to a charger and it instantly did a hard reset. Afterwards it did turn on and continued to work for some time. As I was on the road at that time I could not charge it elsewhere and later that day it ran out of power. When I tried to charge it with a known good charger some days later, it did not boot. I suspect the boot process to healthd or whatever draws this cool animation takes more power than my working but small charger provided.
It did charge at my laptop, especially when I put it into fastboot mode.
Now thats where I am stuck; the phone won't turn off completely and keeps rebooting when I turn it off (via os menu or hard reset, no chance).
I can charge it after it runs out of power (managed to charge to 100%), but it won't charge if I unplug and replug it. It is not recognised by a pc after I reconnect it one or two times (checked with device manager and lsusb), only chance to get to fastboot or flash mode again is drain the battery to 0%. It does show a loading animation and I can boot into android from there. Battery drain in Android seems to be a little higher than usual (100 to 0 after 2 1/2 days of pure standby without any radio stuff on).
I have already reflashed the original Sony firmware and erased everything that came to my mind (cache, data....).
Any hope that I did not kill some piece of hardware?
Thanks for your answers, any help appreciated
tell me more about your z5c's software, why you mentioned Cynogenmod? did you flash it with cynogenmod?
seems to me that z5c was running on custom rom and did not support fast chargers and bricked your device!
if that so, try flashing it using flashtool with original stockrom.
i don't wana go in to details however there is possiblity that battery.sys file is corrupt and atleast I was never able to fix my LT18i when it got bricked and battery status use to become zero in 2 seconds and android keep rebooting, later it got silent for good! no charge no nothing and i still have the device sitting. I was running it on coconut (cynogenmod) when all this happened!
Thanks for your reply.
The charger was no kind fast charger, just a common 12V to USB adapter with an output of 800mA (when it worked). I was running CM 13 when I connected it to the bad charger, but as I mentioned I have since then reflashed it with Stock ROM. No real improvement.
I have continued trying and I found out that the device seems to believe it is still connected via usb.
Code:
cat /sys/class/power_supply/usb/present
gives me "1" with nothing connected, can you check if this is normal?
The file is -rw-r-- r--, would changing its value change anything or is it just some kernel thing (can't check, don't have root permissions now as I flashed Stock ROM)?
Also after I charged it on my PC today it still shows me the notifications for USB connection and adb (I can add a screenshot if necessary), also looks like it still believes to be connected.
It seems I found the solution: I was playing a bit with a USB-OTG adapter (the ones to connect regular usb devices like keyboards or storage to your phone). After I connected a USB keyboard I tried (just for fun) if the Linux "Magic" SysRq hotkeys were enabled. So I did press Alt-Print-o, which is the Linux hotkey for "turn off now". It did not turn off, it also stayed off (no instant reboot). After I started the phone again it also properly turned off via the power menu!
I will have to test whether the charging issues are fixed, too, but as far as I can tell the problem seemed to be something software-related
Sadly did not work for long. I think I will go for official repair, think this is still cheaper than buying a new phone (after completely killing it with some DIY "repair" attempt). This annoying brick simply does not turn off, no matter what I do (apart from draining battery to 0%). Guess its my fault, still to afraid to try that broken charger again.
Hey there. I found a bit old phone in my house, Huawei G730-U10 with MTK6582. Here's problem:
Phone won't turn on at all (no reaction) with battery in and USB out.
With battery in and USB in (connected to charger or PC, no matter what), at first it turns on red led that stays still, and after some time it starts vibrating with interval of about 10 seconds and PC sees it for 2 secs (it connects and after 2 secs - disconnects), then everything repeats. I assume it's bootlooping, but there's no anything on screen (it doesn't even turn on, full darkness). This continues even after taking out USB, only way to stop it - take out battery and place it back.
With battery out and USB in, red led starts blinking with very quiet beeping (very very very quiet).
As you could guess - recovery, fastboot and other things aren't working.
I've checked main board, everything is ok, connected and working fine.
I think there's problem in ROM (not firmware ROM, but ROM that's read-only memory). Something's wrong, maybe there's wrong preloader (or there's no preloader at all), maybe boot partition is damaged, I don't know.
Service center tried to fool me on buying new board for 100$ (althrough it costs 40 on aliexpress), I think they didn't even look at it, so I can't trust them.
I don't need suggestions like "try to flash new rom", you think I didn't try? How is this possible if I can't make PC to see phone for more than 2 secs? Flashtool isn't working even without battery mode.
Do you have any ideas?
Thanks for help.
Hello. Yesterday at midnight i was on my computer and i had my phone next to me charging (to the wall plug) i double taped the screen to check the time and after some seconds the phone crashed, usually when my battery is below 10%-20% it can do the same thing because i haven't ever changed battery, so it's 4 years old with many charge cycles in it, but it was 100%. When my device crashed after it's first attempt to boot crashed again, the second attempt was extremely long (probably about 2 minutes), it booted to the lock screen but then it crashed again after 5-10 seconds when the phone was on the lock screen, after the crash it booted into the "Fastboot Mode" with the message "Welcome to Fastboot Mode for bootloader unlock" at the latest line of how to exit fastboot by typing a command "fastboot reboot" to exit. I was almost sure that i needed some kind of software to perform that and i decided to remove the battery instead. After re-attaching the battery i holded the power button and nothing, my phone doesn't even show the LG logo anymore. At first i thought that the battery was probably dead so i decided to connect it to the wall plug again to verify that (you can connect the lg g5 to the charger without battery and it will show a battery warning icon, but it wouldn't boot.) but the phone showed no life. I'm starting to think that i damaged it somehow by pulling out the battery. Stressed out i decided that it's dead and i called it a day. The next day, after i woke up i picked up my phone and i realized that it wasn't as cold as it should be for a dead device, i felt the screen being slightly warm, and decided to connect it to my pc. After i connected it to my pc, it showed some kind of life by playing the win10 device connect sound and i saw it in the device list as "Qualcomm HS-USB QDLoader 9008 (COM6)"
And here is where i need help from the community.
Is there anything that i can try?
Is it somehow bricked?
Is it time to buy another phone? If yes how can i retrieve the 2-Step Factor Authentication from (Google (all connected here), Steam, Microsoft etc.)
Is it worth spend money on repairs? (Mostly for the 2FA and Contacts)
Any help will be appreciated.
Thanks.
Hello I wanted to ask you because we use the same phone
my device is strangely wiggling in games pubg even at low settings and overall it is but the stranger
When I plug the phone into the charger while playing the game, the performance increases for about 40 45 seconds.
Hey, so i dont know much about these stuff but my phone was dead and I charged it for a bit then turned it on, when it turned on it was at 10% then I decided to turn it back off because it charges a lot faster when its turned off, it was charging through my pc because I was not home and this time when I turned it off I think it didnt take as long it would usually take but im not sure, when it did turn off my pc like had a popup for installing new drivers for "QHSUSB_BULK" , and when i checked my phone, the charging indicator wasn't on and nothing happened when i unplugged and plugged it back(usually it shows how much charge is in it), i thought i could recover it with fastboot but it didnt boot into fastboot either, and when i read more about it people say the phone is bricked but honestly i didnt do anything with the software for it to get bricked, or is it just a dead battery and i have to boost it
Please help asap because i have to go out of station for some office stuff and most of the information is on my phone
Also sorry for my English im not really good at it
[UPDATE]: Now I left it to charge in the original charger and now when I connect it to my pc nothing happens for 10 seconds then it shows "Device descriptor request failed"
Thanks