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.
Related
I have a problem with my x10i.
I was trying to use the flash tool for 2.1 from binary's thread but I failed and it was still 1.6. It got to the point where it said [finish] and then error message in the cmd. After that I tried using SEUS to update it again, the 2.1 update was available so I tried installing it.
Here is the current situation.
After installing 2.1 from SEUS, I followed the instruction to turn the phone off/take out the usb. After turning it back on, it's been half a hour and I'm still stuck at the blank screen before the SE logo shows up. I tried taking out the battery to boot into Flash Mode but that didn't work either. I was wondering if it was because the battery is near empty, but that's not the case since I was using the wallcharger for another hour on it earlier whlie it's in the blank screen state.
Can anyone point me in a direction for fixing it?
Forgot to mention, holding the power button doesn't turn it off either. I would have to remove the battery to turn it off.
Try a re-flash... use the repair function on PC Suite
the usb cable isnt turning on the phone by connecting to it while its off. i can't boot in flash mode either .
had somewhat a prob yesterday like it, my phone did turn on again. i got an other pc installed companion suite there and repaired the firmware(said it was up to date) and then after the boot i'am @ 2.1
was the other pc a 32bit? because the first time i tried using seus was on a 32bit then i bought 64 bit computer.
I'll try running it on a 32bit computer today.
Okay, so I borrowed a PC and installed PC Companion and tried to connect the phone to the computer. However the computer didn't recognize my phone at all. Perhaps this is a problem with window 7?
I also noticed that when i take the battery out and put the usb in then the battery back in, the green LED light stays on. It stays on until the phone trys to boot itself on then the LED turns off but the screen turns on. Only thing is that the screen is still blank and never went to any of the logo screens. And while the USB is plugged in, I can't turn it on by holding power. However if the usb is not plugged in, and I take the battery out and put it back in, I can hold power and it'll blink really fast for the green LED and then the phone viberates for a quick second (like it usually does when you turn your x10 on) and then blank screen and nothing else. The reason i can tell it's on w/ a blank screen and not a screen issue is because I put the phone under the table (very little light) and I can see the screen dimly lit by the back light. These are the only 2 indication I have that the hardware is working.
My biggest guess right now is that the firmware was F'D during the flash or the loader is now a goner since I can't boot into safemode or flashmode. My other conclusion so far is that while the phone is on (confirming it being on via the backlit blank screen) the usb connection goes off. Perhaps its stuck in a loop? Can anyone tell me how I can fix this?
I did searches as well.
I came across people who said their phone was stuck so they let it drain out the battery on it's own and it unstucks. Some say they waited 4-5 minutes and it worked.
So far the longest I waited was:
3 Hours(And counting) *usb & battery is plugged in but charging green LED light is not on*
or tried to leave it alone for 8 hours without battery or usb plugged in.
I'm hoping someone has come across the same problem and had a fix or one of the DEVS might've experianced this problem while trying to test their loaders/etc?
Nothing to do with Windows 7, I and others have no issues on Windows 7 x64. Run the attached file and delete anything to do with SE and try reconnecting in flash mode whilst running SEUS. Post a screen shot of the program if you're unsure what to delete.
Okay right now I am on the 2nd computer with the 32bit OS that I tried to connect to earlier. However i was unable to find a DEVID that was registered on Nov 1. which should be the case since I have never connected my phone with this computer ever before.
I was unsuccessful at booting into flash mode as well. I would put the battery in. then hold the back button and plug the usb. However the phone would not auto boot like it does normally when you plug in the usb so I held on till it did because I thought it might be lagging, however it still didnt boot into flash mode.
I have a baddddd feeling now
Did you read my post?
this is the screen shot of the program you told me to run. It was ran on the computer that I borrowed today, it was never connected with my phone before.
Thanks for helping me ^___^
skrod said:
Thanks for helping me ^___^
Click to expand...
Click to collapse
No worries, but you'll have to post a better screenshot than that, can hardly see it.
Sorry about that, this is my first time uploading a image on xda.
I re-uploaded via imageshack
http://img525.imageshack.us/img525/1355/find.png
Yeah as you've not connected it before there is nothing there to remove, and seems like you've already tried everything. Not sure what to suggest, are you on a contract with insurance?
Nope, I got my phone in USA before it came out in NA. I had it imported via a dealer.
Got some strange bug. In the notification "menu" it often say "mtp-initialization" even though i havent connected a usb to the phone, also it sometimes think im charging the phone and it gives me the charging animation even though i aint charging it. Why is that? It doesnt matter what rom i use the problem is always there.
Another problem i have is when i turn off the phone it shows me the green battery image plus a thermometer that shows me it is overheated or something.. its always there when i turn it off and to turn it on again i have to go to the recovery and reboot it from there to make it boot up. Why?
Sent from my GT-I9100 using xda premium
me too and it's really really annoying!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! it does that every 10 secs or so!!!!!!!
I have the same issue. The common denominator is it all starts after I have charged the phone. The MTP tries to initialize even though my usb is disconnected.
When I shut the phone down, it reboots after a few minutes with MTP trying to connect.
When I pull the battery and reinstall, I get a grey battery charging icon followed by a green icon followed by a battery icon with a warning triangle and a thermometer.
Same here. Any solutions yet?
I'm having issues with MTP and my Galaxy Tab 10.1, it says MTP connected after MTP initialisation but the Tab never shows up in Windows and Kies??
Same problem here, with unrooted i9100.
I think it has something to do with the usb port. I've red somewhere that the quality is very bad and that it is very vonurable to dust.
This is sooooo annoying i just want to put music on my phone and the only way to do it is take out my external sd card and put it on.
Had this issue also recently when I watched videos for longer than usual (Only around 40 minutes). Car mode started going crazy and the device wouldn't stay powered down. I then removed the battery for a couple of hours while I was busy and when I put it in again I got the green battery image that the OP described. From my searching this seems to be a problem based around the usb port and its connector. I tried doing what others suggested in similar threads and move the metal pin up slightly but this hasn't helped.
I'll be running the device heavily again tomorrow (Video wise) so if it acts up again I'm calling samsung for a replacement/repair. This is a really ****ty problem and stranded me in the rain as I couldn't even get the device to boot for 20 minutes due to the battery image problem. I also doubt it's a problem with the battery as I replaced my Anker 1900ma battery with the stock one and the problem persisted.
Wouldn't you be able to get it fixed under warranty, expecting of course that you restock back to original state....
Sounds like a hardware fault which would definately go under warranty...
Hi,
i have a european htc flyer with LeeDroids actual custom rom (GB).
Today I drove my car, while charging it with a special 12V - Micro USB-Car Cable.
I tried google navigation and some other features and after that I chose HIBERNATE from the power-menu.
After half an hour I wanted to reactivate the device but everything I try - it simply wont start. display stays black, i tried every button (including the combination to bring it in the recovery mode). nothing works. the red light next to the power button is on (as if it is still loading).
has anyone an idea, what i can try to start the device, is it a brick? what about garantuee in this state? what should i do??
please help, thx
You need to give it time on the proper wall charger. Red indicates a completley depleted battery. I don't think you'll get what you need from a usb charging mode at this point. It could take some time to revive if you've push the battery far enough to deep discharge becasue the initial period will be used to recondition the battery at very low current.
...has been on the wall charger for hours - no effect
Can you plug it into the PC and see if it detects anything at all and if it does what is that. The other possibility is that you've somehow ended up in download mode.
I ended up in download mode on my original incredible. Not fun. See if it boots if you plug it into the pc. If so, I know how to fix it.
Sent from my HTC Flyer
nothing detected when plugged in via usb onto my pc
tried also adb shell, sais no connected device
think its really dead...
i have a flagship store in town, bring it in tomorrow -keep you posted, what the problem was/is
Let Lee know too if you haven't already just in case there is something in the code causing problems. That way he can pull it to keep other people safe.
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.
My S9+ was acting quite weird this morning. Some apps continuously crashed or wouldn't start.
So i rebooted my phone (just from the normal power button menu) and then it went completely black.
It doesn't charge (or at least, it doesn't show it charging), it doesn't respond to forced resets and the screen is completely black.
The only thing it does, is briefly show a USB device when connecting it to a PC.
I've connected it to a Linux dev computer i have laying around and i see the following device connected briefly:
VID: 0x04e8
PID: 0x1234
It stays connecting longer if i hold the power button (about 8 seconds before power cycling).
The only things i could find online were some very old threads about Samsung's DNW mode, but nothing from this decade.
I think my Flash chip might be cooked, but i hope i'm wrong.
Anyone got any experience with this?
Update
I've sent it back to Samsung for repair under warranty.
The flash chip was gone. It started corrupting writes and finally it was so far gone that it couldn't load the bootloader.
They've replaced the main board and battery (probably because they tested it and saw it was going bad), that fixed it.