So I plugged my phone (R800x) in last night to charge it. When I woke the next morning it was dead, the green light was off though it was still plugged in. I held down the power button and I got the short vibrate but nothing after that, if I continue to hold down the power button it just repeats the short vibrate. I replaced the battery with one that was fully charged and same result. Now when I plug it in to the charger the green light has short fast flashes. When I plug it into my pc I get a steady green light and it comes up as a S1 boot device. Now the bootloader is unlocked and it's rooted, no custom rom or kernel was installed. My question is, is it bricked some how, or did it just die on me? I took it into the VZW store and they are sending me a new one, but I would prefer to keep this one as the BL was already unlocked on it.
Also I tried to put it in fastboot mode but only get the green light, not a blue light.
Bootloader unlocked and you set the to automatic update. I think a flashtool might fix it..
Sent from my R800i using XDA App
http://forum.xda-developers.com/showthread.php?p=14774409
So use this tutorial....will this work on the R800x
---------- Post added at 11:01 AM ---------- Previous post was at 10:05 AM ----------
So flashtool fixed it...thank god....now when i power on the phone it starts the ota update....how do i turn off automatic updates
Related
Ok, I switched up from the Epic, and that thing was almost impossible to brick. Every time I tried to install new ROMS, kernels, whatever, if it failed, I was always able to get it into download mode, Odin the stock ROM, and I was back and working.
I'm not a ROM newb, but this was the first time trying something with the E4GT. For this phone, I was trying to install one of the pre-rooted kernels, and the process failed. I let odin say it failed and unplugged the phone, pulled the battery and tried to get it into download mode again (Vol down + Power) but all I get is the Blue LED, nothing else. Screen and buttons don't light up, no USB recognition (with many various cables.) The most I get is the blue LED.
So, is it totally screwed?
If I can't get something going, I am just going to have the store replace it. (Good rapport with the SM, since it's not working at all, I will likely have her replace it with a new handset today.)
I'd rather not waste a perfectly good phone though if it isn't totally screwed.
Any suggestions?
You probably arent screwed try this and do it step by step
Turn phone off plug your usb into the comp FIRST hold vol down first then power "keep holdin them" galaxy s logo may appear twice before entering dload mode!!
Then you should be in dload mode hit volume up then connect your usb cord to phone
then open odin
also try plugging in your usb cord to epic first with the battery out hold vol down and power then put battery in real fast after that may help into download mode
Side note see if your battery shows charging on front screen when you, plug usb in , im curious to see if you did the same thing i did, oh yes you can hard brick it easily i did two days ago... but i flashed a aTAT GSM rom, over the cdma phone which is a pemabrick instantly, i lost all usb recognition for good!!
---------- Post added at 12:57 AM ---------- Previous post was at 12:54 AM ----------
I forgot to mention try the 3 button combo for dload mode that the gt i9100 uses hold VOL DOWN, @ HOME BUTTON @ POWER all at once its worth a shot after i flashed the gsm tar file i had to use the atat download mode ,method for their galaxy s device
---------- Post added at 12:59 AM ---------- Previous post was at 12:57 AM ----------
Theres no way you dont have dload mode,unless you flashed a kernel from a gsm rom, are you certain it was one of the kernels for the epic touch 4g, your probably just having a hard time gettin the button config right for dload mode
nope, doesn't work. I tried everything you said above, and it does nothing more than light the blue LED.
I was trying to flash the deodexed-rooted-busybox-EG30.tar, but it didn't get to that point in Odin.
I think this is one of the first non-gsm kernel true bricks...
In a flashing video, one of the ACS guys said if a flash didn't take and you are having issues, pull the battery and let the sit an hour or two with out power. Maybe push power button to try to drain the phone completely. Then try reflashing. Sounds a little wishful to me but maybe he knows something I don't.
Google Samsung epic 4g jig and try to find the documentation for making one. It's only a micro usb plug and a 301K resistor jumping pins. Maybe that will get you into download mode.
reply
take it to a service repair center, dont mention flashing tars, just say u did a kies update on windows 7 64 bit and it crashed they are wll aware that kies wasnt optimized for windows 7 at some point and theyve seen alot of these crashes, just act like you have no idea and no nothing about android, theyll take it right into the back try to flash the tar then, if they cant get it into odin, theyll simply throw a new motherboard in.. tel em its your only phone , they wont let u leave without it working..
thats what theyre paid to do they have parts, they wont charge you and if you dont have insurance theyll add it on the spot..
took me 25 min and i walked out with a working epic.
Then when u get it id leave it be.. or have someone else do the kernal flashing.
---------- Post added at 01:51 AM ---------- Previous post was at 01:48 AM ----------
Theyre have been more bricking with this perticular phone than i have ever seen with samsung before... Not sure why, but mine was by mistake, i had taken a bad tar file for a gt i9100 atat phone that was renamed eg30.tar so i got screwed by an asshole!!
---------- Post added at 01:54 AM ---------- Previous post was at 01:51 AM ----------
That makes sense, kinda like when you replace a part on a vehicle that was throwing a bad code it wont fix the issue until you pull the batt cable and turn on your lights to fully drain your computer brain!!
---------- Post added at 01:57 AM ---------- Previous post was at 01:54 AM ----------
When mine was bricked i still had download mode, but had to use home with the 3 button combo to get into it, but i had no usb recognition, I still think you have download mode regardless, just some reason you cant get into it!!
It can be tricky, i know on tmobiles vibrant you had to plug in usb cord with batt out and do the button combo then put battery back in and it forced it into download mode!
I left the battery out all night last night, and held the buttons down for about 30 seconds without battery in to see if that drained the capacitors in the phone and still nothing.
Just going to have the manager at the Advanced Exchange store replace my device. I know her personally, so she will likely just swap with a New in box handset since it's totally out.
Hello XDA wizards.
Today was a sad day. After leaving my Pixel C not used for a couple days, the device is not booting (altough it seems it's powered up). Lights bar is on (all colors) and when double tapped all bars go green.
Holding power button for 15 seconds helped before (reboot) but now it does nothing. PWR, VOL UP + VOL DWN buttons combination and plugging/unplugging charger does not work either.
Any ideas?
VR
Have the same thing happen to mine. But after 10 time trying, it will wake up or restart to normal. Then same thing happens again once it goes to sleep.
I've never had this occurring before I updated to OTA 7.0.
The screen would also get stuck in in a weird way too, as if two window mode was used.
I factory reset it and still same thing. About to call Google when I get home from work today.
Multiple battery drains to 0% and full charge cycles did not help. More information that may help with troubleshooting:
*Magnetic cover was used since the device was bought
*Problem started occurring after a long (week or so) time of not using device (battery drained to 0%, then fully charged. Once device went to sleep I can't "wake it up")
*Locked in landscape mode
*Can't get into any other mode bootloader/download/factory reset
*No "beep" sound (after 30sec) nor notification
Thanks in advance
Does a PC recognize it when plugged in? If so, try the Nexus Root Toolkit to see if that will let you reboot the device.
I know that feel bro.QAQ
Recently, I bought a pixel c two days ago .
I upgrade it to Android 7.0.
After I place it there for a short period of time(1-2minutes),it can't wake up after screen off.
I am going to change a new pixel c from Google store.
Let see will this problem still happen in Android 6.0 or after I have changed a new devices.
Sorry for my bad English
Sent from my IM-A870 using XDA-Developers mobile app
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
bluestang said:
Does a PC recognize it when plugged in? If so, try the Nexus Root Toolkit to see if that will let you reboot the device.
Click to expand...
Click to collapse
No, my computer can't recognize pixel c.
The screen is black but the back light is lighted up.
Sorry for my bad English
Sent from my IM-A870 using XDA-Developers mobile app
I'm sorry for resurrecting this thread but due to the fact that I just got back from deployment I decided to give Pixel C one more chance.
bluestang said:
Does a PC recognize it when plugged in? If so, try the Nexus Root Toolkit to see if that will let you reboot the device.
Click to expand...
Click to collapse
No. PC does not recognize the tablet (tried both Windows & Arch)
More info:
*last flashed ROM Dirty Unicorns 10.0
Hi,
my M8 doesn't turn on anymore. Already tried to change the battery, already tried to start it with VOL+ vor a couple of minutes, tried VOL+ and VOL- for a couple of minutes - nothing. I can't get into bootloader, i can't boot the phone - BUT:
- After connecting the phone to the PC a device "Qualcomm HS-UB QDLoader 9008 (COM10)" shows up
- When putting the charging cable only half the way in the charging LED turns on for 1-2 seconds and then off again
- When trying to do the VOL+ and Power method the charging LED turns on very short every 10-15 seconds as long as i hold the keys
Is it completely dead? Or can i try to flash something with qualcomm tools from here? Its a non-provider phone (HTC_102 i think) and the android variant.
The last thing i did was htcdev unlock after i got it from htc repair where they replaced the motherboard. i installed twrp and then miui7 and after this viperrom and leedroid. With miui it turned on but not every time (i don't know why) but after leedroid it doesn't even get into bootloader.
I don't think this is rom related and more of a hardware issue but maybe you have some ideas. The phone seems to be dead anyway, so let's try something.
Thanks
Dacoco said:
- When putting the charging cable only half the way in the charging LED turns on for 1-2 seconds and then off again
- When trying to do the VOL+ and Power method the charging LED turns on very short every 10-15 seconds as long as i hold the keys
Click to expand...
Click to collapse
What color charge LED?
Orange
Dacoco said:
Orange
Click to expand...
Click to collapse
I have the same issue. Same indicators. Just happened after charging overnight phone seems completely dead. Tried everything. (Light trick, Volume Up & Down w/ Power)
For the most part, if you've charged the phone for several hours, and all your are getting is orange/red LED (I would call it red, but maybe I'm not remembering it correctly) and the button combos don't work, its probably bricked.
Try holding power+Vol up for a minute or so (it will sometimes take that long to reboot, in certain circumstances). Also try Power+Vol up+vol down (but it sounds like you did already).
Also try the button combos with or without the charger attached and plugged in. In can think of at least one user, that had success with the charger plugged in, when they had lost all hope.
Basically, the device will come up with the Qualcomm Download message on your PC anytime the phone is not powered on. So it can be an emmc failure, or a dead battery. You can try replacing the battery, but that can just end up as a disappointment (which looks like may be the case for the OP). Or you can even have the Qualcomm message come up, if the charge is too low. I've had that happen once, gave me a heart attack. Red LED, and no response to button combos. I let it sit on charger for a few hours, then holding power+vol up for a minute made it boot, much to my relief.
---------- Post added at 03:51 PM ---------- Previous post was at 03:49 PM ----------
Dacoco said:
Orange
Click to expand...
Click to collapse
I would have been more hopeful if it was a green LED, appearing for a second when you connected the charger. That would have made me think maybe the charge port is just loose.
Same problem
having the same problem and i have noticed that when I plug it to pc then I shows qgusb dloader and when I press power button or any other button combination then I stop showing as qgusb dloader it appears as device is unplugged and then if I replug it then it won't show anything nor led neither qhusb..But after 10 min or so if I plug it then it again shows led and qhusb and I have also noticed one more thing that if I plug it in charger then led just blink for some microseconds but when I plug it to pc led blinks several times dim solid for 2 3 seconds is there any hope?
I reached this stage by installing unknown ROM .
By the way I have one more HTC one M8 but its from different career (at&t) and it's also rooted and custom rom installed but its in very bad condition just working but i m thinking about replacing motherboard or battery so i can fix it it this idea succesfull ?
narshi shukla said:
I reached this stage by installing unknown ROM .
Click to expand...
Click to collapse
What do you mean "unknown"? Do you mean, you can't remember exactly which ROM you flashed?
I presume you don't mean you flashed something, without knowing what it is.
Do you remember anything about the ROM?
What carrier version of the M8 are you talking about?
S-on? If so, its hard to brick this phone with s-on.
Hello All,
I have the exact same issue ...
It started by showing messages like "android core/services has/have stopped". I rebooted, then there was no mobile network connection -> No IMEI.
I had no worries, that happened also in the past and I could solve it with a dirty flash.
Then I went to Recovery, dirty flashed my ROM (Android Revolution), phone rebooted and started building application cache.
At some point, it started, then some more caching and ... boom, blackout.
It doesn`t respond to anything. No power+volume combination, anything.
I have even opened it up and removed the battery connector.
Without battery, when I connect it to the power source, via USB, the RED light turns on for a second and the Off. ..
Also, when connected to the PC, it is identified as : " Qualcomm HS-USB QDLoader 9008 " .
Are there any repair possibilities, besides motherboard replacement ?
Thank you in advance.
dachriss_13 said:
Hello All,
I have the exact same issue ...
Click to expand...
Click to collapse
Please don't post the same question to multiple threads. One place is enough. It makes it confusing to those trying to help you, and it's therefore against forum rules.
Understood, won`t happen again.
Thank you.
Hi,
First my phone is a H815, bought on amazon, bootloader unlocked since it was possible, and running on Freedom rom.
Yesterday night it ran out of battery and now it wont boot.
I tried of course to remove the battery and charge it over night.
When power it on, thereis the LGlogo as usual, but then the screen turns off and nothing happens. Sometimes I can see the beginning of the boot animation before the screen turns off.
When the screen turns off, I have to remove the battery before I can boot it again, but it never starts.
I tried to boot on recovery mode (TWRP) by pressing pwr + vol- but after I select "Yes" twice the screen turns off again.
Last thing, when I connect it to my PC in Update mode (vol+ then plug) I see Download Mode, then screen turns off. I managed to get to the S/W screen once but the screen still turns off after a certain amount of time.
This is very weird I don't know what to do
I just saw on another topic that several people had the same issue.. that sucks so much
Its a hardware issue try to have it warantied by lg. Or replace motherboard
---------- Post added at 11:19 AM ---------- Previous post was at 11:18 AM ----------
Lol several try hundreds. Im not bein a smarta$$ this is a majpr hardware defect. Im sure there are thousands that havnt reported it or not xda members.
mm if it keeps on on bootloop hardware if it just turns off then battery.?
Like raptor said. Could be batt if it just shuts off. G3 were noted for this also. I got on3 in my posesion doing it
My battery might be dead, is that what your are trying to say ? How can I verify this ? Even pluged it doesn't boot.
sometimes the batteries just die give out kick it if all else fails order a cheap battery and try.
if not send to lg for waranty
Ok now even if I remove the battery and put it back, nothing happens when press the power button, nothing as well when I hold vol+ and plug it to the PC.
So after flashing a new 7.0 rom on the phone, I updated it via OTA. When it finished, instead of rebooting the phone, it led to a black screen. I have tried turning it on and opening bootloader/recovery but nothing has worked so far. When I charge the phone the white LED above the screen starts blinking and if I plug the phone to my pc and keep pressing the power button, it connects/disconnects from the PC every 20 seconds, so I know the phone is not completely dead. I don´t know what to do anymore, please help.
Its a hard brick you many of us have done it and for now there is no solution. If you check the other threads someone has claimed they figured out a way to boot in to bootloader to revive the phone I think the website is aryktech or something similar but haven't seen verification. Other than that its a paperweight.
---------- Post added at 07:28 AM ---------- Previous post was at 07:25 AM ----------
http://www.aryk.tech/2017/07/moto-z-play-unbrick-solutions.html?m=1
I had that problem on a OnePlus 3t. The battery was so low it would constantly try to boot when you plug it in. I put it on a turbo charger and left it. Eventually the battery got enough where I could get into recovery and boot.