Hi All,
First of all I'm not a native english speaker and I'm a noob in this stuff o rom's .
I recently bought a phone and on update it to JB 4.1.1 with Sense 4+ . Everything went ok and the phone apparently was working ok.
The next day I just noticed that the bluetooth was not 100% because I had some cuts in the sound when connected to a bluetooth headset. Because of this I looked for another OTA update and it found one that said somethink like "General System Improvement" or something like that.
I've installed it but this update didn't went till the end since I get stucked on the "red sign" indicating some fail. I try to reboot the phone but apparently he was dead.
After a lots of tries and key combinations I was able to enter the boot mode and choose to restore to factory mode, but apparently it was not successful. Then I tried and option to check for CRC of img files I think (not sure because don't remeber). It check for 3 images files showing the CRC code, then I think the phone get stucked on one because I still have the waiting message but nothing else happens.
I pressed power button again trying to reboot the phone but since then then phone died completly. The only sign of life is when I connect to the PC windows emits the sound of detecting something but gives an error related to the drives.
Sometimes I get a message saying that a ARX device was found but not anymore.
Tried almost everything that I could read on this forum but nothing seems to work...I think the phone is looping on the boot or doesn't have any battery...not sure.
I've tried some RRU but they fail to find the phone saying not connected or not detected.
Any help will be greatly appreciated, Thanks
Johny
Sent it back for warranty repair as soon as you can this is a known fault as it happened to me recently.
Similar problems: http://forum.xda-developers.com/showthread.php?t=2075862
Getting out of APX mode
Your bootloader isn't locked right? Or were you ever rooted? If the answer is no, just send it to HTC and your warranty will do the rest.
Sent from my HTC One X using xda app-developers app
Related
Hi,
I was flashing a new CM7 theme on my 2 weeks old DZ (with CM7 RC 2 running fine) but the phone got stuck at the CM bootscreen. I tried rebooting multiple times by repeatedly pushing the power button and holding it. After a few failed attempts I pulled out the battery, and after putting the battery back in and trying to power it on the phone did nothing. No matter which buttons I pushed or held in.
I tried plugging it in to the power adapter, but the Power LED's don't even go on (neither the orange or the green one). The battery was at approx. 60% when I rebooted into recovery to install the theme zip, so there should be enough power left in the battery.
When I plug the DZ onto my PC (Windows 7 OS, with eclipse and Android SDK installed and working), the PC looks for a QHSUSB_DLOAD driver. I tried looking for the device through ADB but it doesn't see it.
Please help me guys, I've had the device for only two weeks now.
PS: I'm a noob
Oh dear, that doesn't sound promising. Good luck!! We feel for you.
Anyone knows what steps to undertake to maybe revive the phone. I don't think it's totally dead since it's somehow still being detected by my PC. I just can't find that so called QHSUSB_DLOAD driver.
If I can just somehow get it to connect to ADB then I might be able to get into Hboot or recovery.
Have you checked http://developer.android.com/sdk/win-usb.html ?
Perhaps, donno for sure, it could help you
HLeenders said:
Have you checked ***** ?
Perhaps, donno for sure, it could help you
Click to expand...
Click to collapse
I hadn't, but already had these drivers on my PC. And before it got bricked my DZ connected fine with the PC (I flashed it using ADB and had setup Hboot and recovery). My PC just can't seem to find any drivers for this so called QHSUSB_DLOAD. It doesn't matter wich folders I choose to look for drivers. Nothing is available through internet either.
im having the same problem ... i tried several times but no luck... no LED... but u shud try pulling off the battery then put it in then press volumeUP+power button ..it will vibrate and red LED will start blinking .. i dont knw wat is it .. i connected it to PC ....windows asked for qualcom MSM driver .... i dont knw wat to do ..nd how to get bootload loader bak :S
if it does this, send it back to HTC.
the eMMC chip has failed (an unfortunately reasonably common situation, happened to me twice so far)
They'll fix it regardless of what roms you had on it etc. (unless you've done some hardware mods) i sent it in with cyanogen mod and s-off, they fixed it anyway
hope this helps!
Lol, I thought my topic died.
Since you guys revived it, might as well tell you what happened. I contacted T-Mobile and sent the Desire Z in for repair and it got repaired for free since I'd only had for two weeks back then .
After I got it back I rooted it and restored a NAND backup and everything 's been working fine since then.
they repaired it or they replaced it ?
desirezbilal said:
they repaired it or they replaced it ?
Click to expand...
Click to collapse
They repaired it.
ok thats great
i have 1 stupid question, can you tell me did they open your phone or not
noboby solved this problem?
Basically, this: http://forum.xda-developers.com/showthread.php?t=1384415
No one responded to that thread because it was in the wrong forum.
I got the "Phone -- ! -- PC" screen, and was attempting to fix it before getting this black screen of death.
Galaxy Nexus GSM
Rooted, Codename ROM, don't think there is a Kernel in there
Carrier: Virgin Mobile
Edit: I won't be able to respond for a couple hours as I'm going to work. Any and all help is much appreciated.
Original post from above thread below:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
What i with my little (almost nothing experience in android) would do its going to another computer with no drivers installed, would download the toolkit and install those drivers, then plug the phone and see what happen, im sure its not bricked since the computer recognice it.. I did lot of stuff with blackberry and there was a lot of ways to recover a phone like that... From here if the toolkit recognice it in any way.. Then you could try to do some of those steps.. As far as i tried doing all kind of stuff to my phone, toolkit its for much the Best Tool and way to do anything to your phone or at least for starters like me
Sent from my Galaxy Nexus using xda premium
But the computer doesn't actually recognize it. The "detection" sound it makes is for an unresponsive device. It won't charge, won't be recognized, and no matter what combo I use, it doesn't turn it.
I played dumb, called Samsung, and now I'm going to send it in. Thanks for the help though.
sometimes my screen goes blank and I have to pull the battery and everything comes back to normal
Hello,
I wanted to debrand my htc wildfire s, and after many unsuccessful attempts (main version older) following other tutorials on the forums, I finally went to this one:
http://forum.xda-developers.com/showthread.php?t=1162971
Followed it step by step, everything was as expected until the flash in the end finished and the phone, instead of booting, entered boot loop.
Now when I try to boot it or to enter bootloader, the backlight turns on for a second, turns off after that, then again turns on for a second, off... and etc. It doesn't even show the HTC screen. When I turn it off and connect it to usb - it charges.
I am already assuming the worse, but if anyone has any ideas, it will be great, as this is my girlfriend's phone and I can already see the tears in her eyes when she understands the phone is dead... :'(
Can you get the phone into hboot?
Pull battery,
then put it back in,
then hold volume down and press power while still holding volume down
If luck is on your side you should be in hboot
Unfortunately I have tried that already - still the same backlight on / off / on ... loop. :-/
Try battery out, back in, connect USB, then try to boot into bootloader. See if your PC picks it up. If it does try to issue the fastboot command "fastboot reboot recovery" and see if it goes.
Also does it vibrate when its having its flashy seziure?
sent from my android powered beast!
Hi,
Thanks for the suggestion. Tried that also - unfortunately - no vibration (qualcom diagnostics seems to not be the case - unfortunately).
Connecting it to usb brings the orange "charging" light for a 5-10 secs, after that the phone tries to boot and enters the bootloop again.
I think after 5 HTC phones, I will finally have one matching my avatar... :'-(
Hmm. Does the PC pick it up at all?
sent from my android powered beast!
No, it doesn't
I am probably going to go buy a new identical phone today afternoon...
try going into recovery, wipe data and cache and try again the process
simaka said:
No, it doesn't
I am probably going to go buy a new identical phone today afternoon...
Click to expand...
Click to collapse
Whoa, I wouldn't be so hasty. Try taking your old one to a service first, it'll cost you a lot less
@johnnyspritz
I am thinking about sending it back to repair, the phone is still under the 2 years warranty. However if they find a way to read the contents of the boot or system partition (JTAG?), they might have some arguments against applying the warranty :-D
Hi Simaka,
Like you my phone is in the same boot loop....
Can't access to Bootloader, no HTC Logo.
I have try to contact HTC, but the mail they send me was out of context ....
If you find any solution, please share it ;-)
Hi, for sure I will. For now I will try to return it in the shop where I bought it as it is still s-on and locked bootloader, so they might agree to take it back. I checked the possibility to buy JTAG connection equipment, but it amoints to 150€ with shipping, plus probably a month or 2 of troubleshooting...
One interestimg thing to note is that during the procedure described on the link above the current rom version in misc.img before editing it was 9.9.9.9
I believe this was a way of artificially imposed restriction so any attempt to update would fail...
Sent from my HTC Desire using xda premium
Phone is bricked due to radio malfunction. Idk if there is a way to fix it but other than that ur bricked
Hi, I had a phone call from HTC.
They cannot say if its broken, I have to send it to the support.
I also got phone call from my service - they are looking into it
Sent from my HTC Desire using xda premium
Just a final update, i got a new phone that was easy to unlock boot. The end
Sent from my HTC Desire using xda premium
Hello,
I know booting issues are possible when opening the bootloader and messing with kernels and rom flashing but that's not my case and I couldn't find a post that helped me so I hope someone can help me out on this.
I am a member of the HTC User Trial program and I'm currently testing the 3.09.401.100 Jelly Bean ROM, all stock, not rooted, never opened the bootloader or flashed any firmware besides official HTC RUU when OTA came out late (UK device, always last to get official OTA )
Last night I left my phone on before I went to sleep and it had low battery. This morning I tried to turn it on and it didn't work so I thought that the battery went out. Naturally, I plugged my phone to the charger and the red led didn't light red to indicate charging for a 30sec-1minute period, than it flashed red a few times and afterwards it lighted up red as if the phone was charging. I've left the phone turned off to charge for about 3.5 hours (even after the led turned green, just to get it really fully charged).
Now, when I try to turn the phone on, it get's stuck in the "HTC ONE" bootscreen with the beats audio logo at the bottom.
Long press on the power button reboots the phone but the issue repeats and the phone does not boot past the boot screen with the logo.
Couldn't attach my HBOOT photo so here's a link: https://www.dropbox.com/s/oxk8yz19ew0gi6s/hboot.jpg
Same
I'm having the same problem with an unlocked bootloader
sound weird...
you aways could try to do a factory reset from the bootloader, but should be considered a last resort since you memory will be wiped clean
Bram89 said:
sound weird...
you aways could try to do a factory reset from the bootloader, but should be considered a last resort since you memory will be wiped clean
Click to expand...
Click to collapse
Contacted HTC with this issue and they are not familiar with it as well. They have asked me to send a bugreport using ADB and told me that a factory reset may be required.
I will update if anything new pops up.
What is the starting of your device's serial number? if you don't mind (eg: mine are HW251XXXXXX)
Vcek said:
What is the starting of your device's serial number? if you don't mind (eg: mine are HW251XXXXXX)
Click to expand...
Click to collapse
HT23Y******* - Do you think it's related to my specific issue?
As for the problem itself, since I have all my important data backed up, I have done a factory reset and it sorted things out. No other solution from HTC in the meanwhile.
IdanK said:
HT23Y******* - Do you think it's related to my specific issue?
As for the problem itself, since I have all my important data backed up, I have done a factory reset and it sorted things out. No other solution from HTC in the meanwhile.
Click to expand...
Click to collapse
The problem is that I think that this leaked OTA was meant for some devices only (it contains "goldfish" libs not "endeavor") and 3 devices on this forum have reported incompatible hardware issues with the new hboot.
Are you sure you flashed boot.img from bootloader ? and how did you get into user trial program or where you randomly chosen ?
Vcek said:
The problem is that I think that this leaked OTA was meant for some devices only (it contains "goldfish" libs not "endeavor") and 3 devices on this forum have reported incompatible hardware issues with the new hboot.
Are you sure you flashed boot.img from bootloader ? and how did you get into user trial program or where you randomly chosen ?
Click to expand...
Click to collapse
I got the update directly from HTC as I'm a member on the User Trial program, no flashing what so ever, just plain OTA download & install.
I was chosen to participate in the User Trial program because I'm also a member on HTC Elevate and they asked users to join the program for testing One X software update.
ok long story short...i was playing on my tablet and i got a notification saying that i needed to update to the new lollipop so in the middle of the install it says there is an error and shuts off. i try to turn it on and it doesnt go past the google logo. i read online and someone said try pushing the volume down button and the power button until a screen pops up...i did that and it doesnt matter which option i choose it takes me back to the google screen. ive called everyone including google to see if a tech support person could help me and there has been no luck with out having to pay for it....the google guy said what probably happened is that ive wiped the OS off the tablet. and i was wondering if there is a way to fix this. ive downloaded the root tool kit but am pretty much lost when it comes to something that percise. the tablet is fully charged but its almost like my computer wont reconize it when i plug it in to do anything with it.. HELP
Goofygirl0928 said:
ok long story short...i was playing on my tablet and i got a notification saying that i needed to update to the new lollipop so in the middle of the install it says there is an error and shuts off. i try to turn it on and it doesnt go past the google logo. i read online and someone said try pushing the volume down button and the power button until a screen pops up...i did that and it doesnt matter which option i choose it takes me back to the google screen. ive called everyone including google to see if a tech support person could help me and there has been no luck with out having to pay for it....the google guy said what probably happened is that ive wiped the OS off the tablet. and i was wondering if there is a way to fix this. ive downloaded the root tool kit but am pretty much lost when it comes to something that percise. the tablet is fully charged but its almost like my computer wont reconize it when i plug it in to do anything with it.. HELP
Click to expand...
Click to collapse
If you'd searched a bit, you'd have found out that it means your motherboard is screwed, and the only solution is to replace it. But if you have to pay for it, don't let Asus cash in on their deliberate scam - knowingly putting out a buggy update that potentially bricks their device, then turn around and solicit repairs at ridiculous prices. They break it, they should fix it. The point is that they don't even know what or why and thus choose to dodge responsibility by insinuating it's your fault.
Similar thing here. I was sending a text late at night. Sent it and put it down. Next morning tablet was stuck on Google logo and nothing seems to fix it. Tried adb commands to restore. WugFresh Toolkit failed. Disappointed with both Google and Asus.
losmolinos1098 said:
Similar thing here. I was sending a text late at night. Sent it and put it down. Next morning tablet was stuck on Google logo and nothing seems to fix it. Tried adb commands to restore. WugFresh Toolkit failed. Disappointed with both Google and Asus.
Click to expand...
Click to collapse
I have the same problem.
I updated from Kit Kat to Stock Lollipop and the device worked fine then today when I turned it on it would not boot past Google Splash. Will not boot into recovery. I can get into Fastboot mode but my attempts to flash a stock 5.0.2 from google have failed. I have a Nexus 7 2013 wifi Model "Razor" and flashing it in fast boot is not resolving the issue. Just boots to "Google" and stays. From what I have found this is very common on a 5.0.2 update and needs a RMA? is that correct?
FASTBOOT MODE
PRODUCT NAME - flo
VARIANT - flo 16G
HW Version - rev_e
BOOTLOADER VERSION - FLO-04.04
CARRIER INFO - None
SERIAL NUMBER - XXXXXXX(Filtered out)
SIGNING - yes
SECURE BOOT - enabled
LOCK STAT - unlocked
Thanks,