It's the holidays which means helping to fix others' devices.
I've got a family member's TF300T that gets to the ASUS boot screen but just spins forever. The bootloader hasn't been unlocked and I think it's on JB but I don't have any way to tell which version of the stock ROM it is. I've spent the last hour reading through posts on multiple forums but haven't found anything that works.
I've tried accessing recovery by holding vol down but no luck. It just hits that boot screen and spins. I've installed the standalone drivers as well as the ASUS Sync utility but I can't get adb to see the device. I know the keyboard dock has some problems and doesn't work 100%, but I think the USB port is okay because the owner uses a mouse on it. There's an amber light next to the charging port that is blinking. I'm not really familiar with this device so I tried connecting my Win 10 machine (a T100 coincidentally) with a regular microUSB to that and with the charging cable but neither worked.
Is there something I might be missing or anything else I should be trying with this device?
rileysmith said:
It's the holidays which means helping to fix others' devices.
I've got a family member's TF300T that gets to the ASUS boot screen but just spins forever. The bootloader hasn't been unlocked and I think it's on JB but I don't have any way to tell which version of the stock ROM it is. I've spent the last hour reading through posts on multiple forums but haven't found anything that works.
I've tried accessing recovery by holding vol down but no luck. It just hits that boot screen and spins. I've installed the standalone drivers as well as the ASUS Sync utility but I can't get adb to see the device. I know the keyboard dock has some problems and doesn't work 100%, but I think the USB port is okay because the owner uses a mouse on it. There's an amber light next to the charging port that is blinking. I'm not really familiar with this device so I tried connecting my Win 10 machine (a T100 coincidentally) with a regular microUSB to that and with the charging cable but neither worked.
Is there something I might be missing or anything else I should be trying with this device?
Click to expand...
Click to collapse
You said you held vol down. Hold vol down and power button together from off state. Maybe that's what your doing though. That should take you to boot loader.
Sent from my HTC One M8 using XDA Free mobile app
purple patch said:
You said you held vol down. Hold vol down and power button together from off state. Maybe that's what your doing though. That should take you to boot loader.
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, sorry, that is what I meant. No luck getting into the bootloader.
rileysmith said:
Yeah, sorry, that is what I meant. No luck getting into the bootloader.
Click to expand...
Click to collapse
There's a thread about 3 down from yours, see if that helps. Appears the issue is more common than I thought. It's by mgs333
Sent from my HTC One M8 using XDA Free mobile app
purple patch said:
There's a thread about 3 down from yours, see if that helps. Appears the issue is more common than I thought. It's by mgs333
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
I've read that one and a dozen others. Unfortunately unlike just about everyone else who has had it get stuck, I can't get access to anything that'll let me wipe, flash, or really do anything so I'm sort of dead in the water until I can.
I'm familiar enough with Android that I'm pretty confident in getting it working when I do, but until then I'm a bit lost.
rileysmith said:
I've read that one and a dozen others. Unfortunately unlike just about everyone else who has had it get stuck, I can't get access to anything that'll let me wipe, flash, or really do anything so I'm sort of dead in the water until I can.
I'm familiar enough with Android that I'm pretty confident in getting it working when I do, but until then I'm a bit lost.
Click to expand...
Click to collapse
I've never tried, but look up nvflash. It may help as your stock. Sorry but I'm no more help, someone else may answer, but bit slow around here these days lol.
Sent from my HTC One M8 using XDA Free mobile app
Thanks. I'll look into it some more.
I glanced over it briefly in my earlier research but it seemed like it might not work in my situation.
I got it. This thing has been used in a pretty dusty work environment and I cleaned it up. I think the volume down button was being prevented from working. After cleaning I got right into the bootloader and wiped it. After that it started right up.
rileysmith how you do it?
Related
I'm rooted running Leedroid and a very odd occurrence happened tonight. The volume level started decreasing by itself until it hit vibrate and then the phone just became unresponsive. I pulled the battery and now no matter what I do the phone won't power back on again. if I press power or hold volume down and power, it vibrates 5 times and shows a solid green light, still doesn't turn on. Even if I hook up the USB cable same thing, only exception is that it immediately starts vibrating 5 times without pressing any buttons. I also left it on the charger for a while and swapped out batteries and nothing changes. Has anyone experienced this same issue?. I'm thinking maybe it's a hardware error and possibly bricked.
UPDATE ... I took the SD card out and let it sit for about 30 mins and then it powered up fine. This is very odd indeed. I don't know what could have been the problem.
My wife had this happen to hers after she shut down the phone and it would not boot back up properly. Trying to boot would either give five vibrates and green led or three vibrates and a red led iirc depending on if I tried a normal boot or hboot. Was on irc with attn1 trying a number of different things, as I was able to get adb to recognize the phone when booting into recovery even through the screen was blank, with no success, and finally just had at&t send a replacement.
I did try swapping another sd card but didn't try booting with no card installed so I don't know if that would have helped in my case though I am certainly curious now after reading your post. Wish I could get the phone back to test now. lol
Any solution to this? My phone is stuck like this now.
jznomoney said:
Any solution to this? My phone is stuck like this now.
Click to expand...
Click to collapse
I had one go this route too. I think its a corrupt boot partition (or some other critical partition in the built-in flash ROM). I could not get it to boot to anything usable at all. I ended up filing a warranty claim and got a new one. Hopefully your's is still covered, or you have insurance, otherwise, your best bet is send it back to HTC for repair. They are actually pretty reasonable from what I hear, but you'll be without a phone for awhile.
I did a rma straight from HTC since I didn't have the insurance from at&t on it. They said it was the motherboard that died and replaced it.
shawn1224 said:
I'm rooted running Leedroid and a very odd occurrence happened tonight. The volume level started decreasing by itself until it hit vibrate and then the phone just became unresponsive. I pulled the battery and now no matter what I do the phone won't power back on again. if I press power or hold volume down and power, it vibrates 5 times and shows a solid green light, still doesn't turn on. Even if I hook up the USB cable same thing, only exception is that it immediately starts vibrating 5 times without pressing any buttons. I also left it on the charger for a while and swapped out batteries and nothing changes. Has anyone experienced this same issue?. I'm thinking maybe it's a hardware error and possibly bricked.
UPDATE ... I took the SD card out and let it sit for about 30 mins and then it powered up fine. This is very odd indeed. I don't know what could have been the problem.
Click to expand...
Click to collapse
it sounds like something is going on with you data partition and sd card format. i recomend booting in to clockwork mod recovery and wiping all data and cache partitions as well as dalvik and then re-installing the ROM of your choice. id also recomend backing up your SD card and reformatting that as well, and if none of that works. i think its time to try a new rom
I have this issue!!!! The EXACT same thing happened to me! I can't resolve it .. if i turn it on like normal, it flashes orange and vibrates 3 times. If i hold vol + down and turn it on, solid green and vibrates 5 times/ black screen. Help!
Chronei said:
I have this issue!!!! The EXACT same thing happened to me! I can't resolve it .. if i turn it on like normal, it flashes orange and vibrates 3 times. If i hold vol + down and turn it on, solid green and vibrates 5 times/ black screen. Help!
Click to expand...
Click to collapse
Try and take out the SD card for 30 min
Sent from my HTC Desire HD using XDA Premium App
I tried that and it did not work. I tried both the sim and sd card. I still need help. This is the only post on the internet I found that reproduced the issue -- and if this EXACT issue I have is happening to someone else, there has to be a way to fix it.
If my volume+up button worked, I could boot it to recovery. I need a way to do this without the use of the volume+up.
jznomoney said:
I did a rma straight from HTC since I didn't have the insurance from at&t on it. They said it was the motherboard that died and replaced it.
Click to expand...
Click to collapse
How much did they charge you?
And if anyone fixes my issue, I will donate $50 if you find me a resolution that works for me.
Chronei said:
How much did they charge you?
And if anyone fixes my issue, I will donate $50 if you find me a resolution that works for me.
Click to expand...
Click to collapse
Try to run the ruu .exe file from your computer
Sent from my HTC Desire HD using XDA Premium App
Chronei said:
How much did they charge you?
And if anyone fixes my issue, I will donate $50 if you find me a resolution that works for me.
Click to expand...
Click to collapse
HTC didn't charge me anything since it was a hardware failure. Your inspire will still be under warrenty since it hasn't been a year yet. Just call htc support and they will create the rma. You will just have to pay shipping to them. It took about 10 days round trip.
an update .. i can run droid explorer with it turned off, but plugged in usb and it detects it. I tried rebooting/rebooting to recovery via droid mgr but same thing happens. But it's a good sign pc detects it .. anything I can do?
I really need this fixed. If you can find a resolution, I'll donate $50
Chronei said:
an update .. i can run droid explorer with it turned off, but plugged in usb and it detects it. I tried rebooting/rebooting to recovery via droid mgr but same thing happens. But it's a good sign pc detects it .. anything I can do?
I really need this fixed. If you can find a resolution, I'll donate $50
Click to expand...
Click to collapse
Ok thats good news that it can read it. Connect it to the computer and run that file.
http://www.filefactory.com/file/b50...60.19_26.06.04.06_M_release_166557_signed.exe
XAviierG said:
Ok thats good news that it can read it. Connect it to the computer and run that file.
http://www.filefactory.com/file/b50...60.19_26.06.04.06_M_release_166557_signed.exe
Click to expand...
Click to collapse
Hmm, I don't think i can execute files with droidexplorer, can you ? Or run it with windows?
Chronei said:
Hmm, I don't think i can execute files with droidexplorer, can you ? Or run it with windows?
Click to expand...
Click to collapse
Run it with windows
Sent from my HTC Desire HD using XDA Premium App
Error 170 - usb not connected. But it shows up in droid explorer and "adb devices" check! Perhaps to use RUU you have to be at least in recovery menu or something .. I feel like this should work, though. Any thoughts?
Chronei said:
Error 170 - usb not connected. But it shows up in droid explorer and "adb devices" check! Perhaps to use RUU you have to be at least in recovery menu or something .. I feel like this should work, though. Any thoughts?
Click to expand...
Click to collapse
Hmm its working with adb?
Sent from my HTC Desire HD using XDA Premium App
XAviierG said:
Hmm its working with adb?
Sent from my HTC Desire HD using XDA Premium App
Click to expand...
Click to collapse
Yes -- works with adb
Chronei said:
Yes -- works with adb
Click to expand...
Click to collapse
Did you try and reboot into recovery or bootloader with it?
Sent from my HTC Desire HD using XDA Premium App
Hello all \o
So, I have a sensation, on which I was running the hyperSensation rom, (s-off, root etc).
Anywho, a friend of mine borrowed it for a little while, and before he gave it back to me, he did a factory reset on it.
Now, the phone appears dead. It won't turn on, I get nothing when plugging it to my computer or charger.
What's wrong? Is there anything I can do?
Apologies if anything is unclear, but I'm not a pro at this
Any help is greatly appreciated!
I believe that your going to have to reflash the Rom.
Sent from my HTC Sensation 4G
So it won't turn on at all? Have you tried removing battery placing battery back, pressing power and volume down at the same time to boot into recovery. If that works and you have done a backup you can restore this way. Go to recovery, backups/restore and restore your backup Rom this way. Have you tried this? Hope this helps. I've restored this way before when I've gotten in a bind. But hopefully you do have a backup. Give it a shot and see if this works for you.
Sent from my HTC Sensation 4G using xda premium
Thanks for quick replies!
yes, I have tried those things, power+vol down does nothing. Plugging it to my computer doesn't do anything, it's like I haven't plugged it in at all,, nothing =\
kentaur85 said:
Thanks for quick replies!
yes, I have tried those things, power+vol down does nothing. Plugging it to my computer doesn't do anything, it's like I haven't plugged it in at all,, nothing =\
Click to expand...
Click to collapse
Sounds like a brick buddy, might have to send it in to HTC or get a replacement.
put the battery out for 10 minutes!
kentaur85 said:
Hello all \o
So, I have a sensation, on which I was running the hyperSensation rom, (s-off, root etc).
Anywho, a friend of mine borrowed it for a little while, and before he gave it back to me, he did a factory reset on it.
Now, the phone appears dead. It won't turn on, I get nothing when plugging it to my computer or charger.
What's wrong? Is there anything I can do?
Apologies if anything is unclear, but I'm not a pro at this
Any help is greatly appreciated!
Click to expand...
Click to collapse
Tell your friend he/she owes you a phone. And get a Nexus 7 to compensate you for your "pain and suffering". Did your friend pee on it?!
Back to the issue at hand. Do you have another battery to test out the phone? OR when you plug the phone in and hold the power button down (for 10 seconds) does the LED flash at all?
Does your computer recognize the phone at all when plugged in?
Sounds really bad. Try a new battery if that doesn't work and suggestions don't work sounds like you need a replacement. What the heck did he do to your phone, and why?? I'd say he owes you a new device! That's for sure! Why was he messing with the internal part of the device anyway?
Sent from my HTC Sensation 4G using xda premium
You should have a try at this solution : Sensation Unbrick provided by Dexter93. Do read, understand and follow the guide and probably your phone will boot from the death.
Don't mess with Ubuntu version, take the 10.04 for 32bit, it's mandatory to succeed.
Thanks again for all your suggestions and tricks!
I tried pulling the battery for 10 minutes (more like 30, but does that matter?)
The LED does not flash at all when connected to the computer or not (holding power for over 10 sec).
Unfortunately I don't have a spare battery or anyone with a sensation I can try with, but I've been looking around and they don't cost much, so I might just buy one and hope it's that.
That unbricking thing seems a bit over my level, but if all else fails, I might give it a go.
Thanks again all
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Use heimdall n hold the volume buttons n enable flash bootlaoders
Sent from my SGH-T959V using xda app-developers app
@karose465 How old is the phone? If less than a year (doubtful), it should still be under warranty. Or you may be eligible for upgrade pricing: Fore example, "Customers with a Classic plan (two-year contract) are eligible for our lowest upgrade price on a new phone when at least 22 months have passed since their last phone upgrade. A new two-year contract is required to take advantage of best upgrade pricing. Of course, you can always upgrade a phone at any time, regardless of how many months have passed since your contract began."
For more info on Heimdall, just Google Heimdall Android.
Anyone with a sidekick contract ends earliest next march..
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.
RicAndroid said:
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.
Click to expand...
Click to collapse
I think for him and myself, the biggest problem is being unable to get the phone to stay in download mode. For some reason, the battery won't charge and the phone itself continously turns off and on when plugged in. So the charge isn't holding, therefore nothing will stay on/open.
Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium
gamingwiz said:
Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium
Click to expand...
Click to collapse
I did some forum searching and found this. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=1477838
Thanks ill check into that
Sent from my HTC Glacier using xda premium
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576
---------- Post added at 04:33 PM ---------- Previous post was at 03:41 PM ----------
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576
Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium
EpicLordPhone said:
Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Power Button Repair relating to Boot Loop
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
my Sidekick 4G is very old and just now went into bootloop... i googled the word and came across this forum.
As quoted above by previous poster that a power button repair was needed... I figured that I had nothing to lose, it being so old, I smashed the crap out of the Sidekick 4G on its power button. Lo and Behold, it booted into the system successfully.
SO... if no one has any qualms about smashing the crap out of their power button... give it a shot. It worked for me.
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app
EpicLordPhone said:
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app
immorality said:
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
Hmmm thanks, I might just try that!
Sent from my Amazon Kindle Fire2 using xda app-developers app
Mines stuck in a boot loop too.
I don't know if my Sidekicks problem is related to this or not. I rooted it and flashed it over to Glorious Overdose v5 on May 22nd this year and it's been running great. At least it was until last Friday, Sep 13. I was having trouble connecting to the WiFi at my house so I rebooted the phone. When it started to come back up a female voice started saying, "VooDoo lagfix has been disabled." "Converting /data and /system partitions." "Conversion time estimated 10 minutes."
I let it do it's thing and that's all it's been doing all weekend. I can get into recovery mode, I've tried restoring the phone from my backup with no success. I've even tried running through the process of setting up GOv5 again and it says it's successful, but the phone never boots up. It just stays in the same blasted bootloop and saying the same things over and over again about VooDoo. I've checked the VooDoo logs and there is an error file for the 13th and the logs following say "conversion." Can someone point me in the right direction as to what I can do to get my phone working again? Everything I've tried to research so far hasn't worked.
v5 hold both volume button, the track button and power button. Should put you into recovery mode. If not, you will have to put phone into download mode. You do this by taking out battery, then pluging into computer. When you reinsert battery hold volume down and power, if I remember correctly, and your download screen should come up. From your cp manually unroot it. Then it should be fixed, and just reroot it. I hope this was helpful
Sent from my SGH-T839 using xda app-developers app
No idea what I'm doing, precisely, but...
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.
LathyrusRoots said:
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.
Click to expand...
Click to collapse
And almost a year later I log in and see this. Your most welcome. I haven't been working on phones for awhile but if I remember right, some models can be powered on by plugging the phone into a power source and when the phone vibrates or has a sign of life unplugging the unit. Some cables don't work and sometimes doing this via a computer can power up a device. Other than that, the other more dangerous way is to short out the pins on the bottom of the unit. I don't remember the pins but you can google a charge port diagram to help. I don't recommend doing this unless you have absolutely no other choice. Incidentally, this is why a phone will power itself on when a battery is put in and no other button is touched. The port is wet and corrosion has caused a link on the power pin and believe its pin 3. A simple cleaning with 90%+ rubbing alcohol solution will fix if cleaned quick enough.
Hey Guys,
a friend of mine just bricked his HTC-OneS and I'm here to help him get it back to life
He installed the latest PacMan Rom and everything was awesome.
All over sudden the Phone didn't boot up anymore.
It can be charged via USB, so maybe one can do something over USB
Windows-PC doesn't recognize the Phone he says...
As far as I remember its an HTC One s ville c2 (is there anything like this)
Due to the Fact that I'm a Motorola User, I have no idea where to start trying to recover his Phone...
Please Help me do it
do you know how to use some adb/fastboot commands? run fastboot oem getcid in the bootloader.
hold down volume down and power to go into the bootloader.
I would try to get into the bootloader first. That would provide a gateway to possibly fixing his (or her) phone.
Hope to get into bootloader, will get hands in his phone in monday.
Coming from Motorola i'm used to a factory tool where i can flash official Firmware via PC. Is there anything like this for HTC phones?
If not first thing i would try is flashing a New recovery system via fastboot to have sth to work with. Anyone agree with this plan?
Sent from my XT925 using xda app-developers app
I don't think I've ever seen a tool like that. I think the best bet would be to get into recovery, mount and try to flash a new rom (C2 roms in this case).
esok44 said:
Hope to get into bootloader, will get hands in his phone in monday.
Coming from Motorola i'm used to a factory tool where i can flash official Firmware via PC. Is there anything like this for HTC phones?
If not first thing i would try is flashing a New recovery system via fastboot to have sth to work with. Anyone agree with this plan?
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Yes, go to androidruu.com, look for villec2 and click on it. The latest RUU should work unless he is carrier branded. Then you will need to use a carrier RUU.
Got hands on his phone and it doesnt do anything...
No bootloader nothing.
Only thing that happens is that it recognizes its on a wallplug...
Sent from my XT925 using xda app-developers app
Anyone got an idea?
The little charging LED is red, is it possible that there is some kind of battery driver missing, so the phone won't charge anymore and the battery is empty?
and is there an option to solve this?
esok44 said:
Anyone got an idea?
The little charging LED is red, is it possible that there is some kind of battery driver missing, so the phone won't charge anymore and the battery is empty?
and is there an option to solve this?
Click to expand...
Click to collapse
Really sounds like it is hard bricked.
I could mention things that you have already most likely tried.
Holding power down for 30 seconds
holding power down for 10 seconds under bright light so the front sensor registers (prevents messing up your phone while in your pocket)
when plugged in computer, does device manager show it as "qhsusb_dload" (bricked)
Hold power down and volume down for 10 seconds. release power button and continue holding volume down.
From replies from manufacturer that people post here, often they replace the battery and (motherboard?) Seems like something happens and a sudden battery discharge messes up the works.
tivofool said:
Really sounds like it is hard bricked.
I could mention things that you have already most likely tried.
Holding power down for 30 seconds
holding power down for 10 seconds under bright light so the front sensor registers (prevents messing up your phone while in your pocket)
when plugged in computer, does device manager show it as "qhsusb_dload" (bricked)
Hold power down and volume down for 10 seconds. release power button and continue holding volume down.
From replies from manufacturer that people post here, often they replace the battery and (motherboard?) Seems like something happens and a sudden battery discharge messes up the works.
Click to expand...
Click to collapse
Thank you for your response
So quick question, due to the fact that the Phone is hard bricked, can i send the Phone back in, and get things fixed, cause the Phone was s-off and rooted before, so warranty is void.
Is there any way they could find out about it? Like a blown fuse or anything?
esok44 said:
Thank you for your response
So quick question, due to the fact that the Phone is hard bricked, can i send the Phone back in, and get things fixed, cause the Phone was s-off and rooted before, so warranty is void.
Is there any way they could find out about it? Like a blown fuse or anything?
Click to expand...
Click to collapse
Your guess is as good as mine. There was one guy who posted here, that they did fix it, and when they sent it back they had turned back on security, or S-on. So they obviously knew and didn't care. One of those ymmv. I kind of doubt he did anything wrong and it is a defect. People post on here with completely stock w/ same symptoms.
tivofool said:
Your guess is as good as mine. There was one guy who posted here, that they did fix it, and when they sent it back they had turned back on security, or S-on. So they obviously knew and didn't care. One of those ymmv. I kind of doubt he did anything wrong and it is a defect. People post on here with completely stock w/ same symptoms.
Click to expand...
Click to collapse
Thank you dude, will give it back to him and tell him, that he should send the phone back, cause it seems like this is a common problem
Greetz Esok
Hey guys,
Earlier on, out of nowhere, my nexus 5 become totally unresponsive.
Screen is black and won't turn on
Usual methods of accessing bootloader fail (holding down vol +/- and power)
No response from the phone in terms of plugging it into a PC
--------Do however get a response from the computer; comes up as "Qualcomm HS-USB QDLoader 9008 (COM3) in the "Ports" subsection of my Device Manager
Phoned Google, they seem to think the phone is still turned on, and is therefore not Hardbricked (I have my doubts)
Phone is unlocked, rooted and running Android L (Huge mistake, I know)
-------Installed Android L Months ago without any trouble whatsoever, so no connection to now, surely?
Can anyone help, please? Google will replace it, but there are some irreplaceable images on my phone that I stupidly don't have backed up. Right now, I'd be happy with having the phone replaced and scraping as much data off it as I can, but I know, if I can't, its through my own stupidity of not having it backed up.
Thanks,
Nick :/
I'm afraid it's dead and you can't recover anything off it.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I'm afraid it's dead and you can't recover anything off it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately, I think you're right. I just don't understand what caused it, one minute it was working fine, the next it was dead.
Gonna see if I can get a connection through adb, not holding my breath, but I might be able to get something from it. If not, then back to google it goes.
Ser Nick said:
Unfortunately, I think you're right. I just don't understand what caused it, one minute it was working fine, the next it was dead.
Gonna see if I can get a connection through adb, not holding my breath, but I might be able to get something from it. If not, then back to google it goes.
Click to expand...
Click to collapse
I had a device do the same thing. It was on and everything running fine and then just went dead. Luckily it was still under warranty. The Qualcomm error you get said it all to me. Adb isn't going to work but try it anyway. Who knows, maybe you'll get lucky.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I had a device do the same thing. It was on and everything running fine and then just went dead. Luckily it was still under warranty. The Qualcomm error you get said it all to me. Adb isn't going to work but try it anyway. Who knows, maybe you'll get lucky.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The first google search of the Qualcomm thing pretty much told me it'd Hard Bricked itself, I just hoped that perhaps I'd get lucky and it'd sort itself out or I'd find a solution.
It doesn't always come up as that though, sometimes it comes up as unrecognized device, which, I suppose isn't much better.
Thanks for your help anyways
You need a blankflasher to get back your bootloader. It's corrupted!