Unaltered Desize Z won't boot anymore... - G2 and Desire Z Q&A, Help & Troubleshooting

Hi!
I have 2 Desire Z devices here. One rooted with CM7 running just fine, and one untouched, with the original Froyo/Sense ROM. and here's the problem:
Out of nothing the phone won't boot anymore and is stuck at the HTC-Logo screen.
I can still boot into (the original unaltered) hboot and fastboot.
When I select Facrory Reset from hboot, I think it does flash the recover image, but that won't boot either.
Selecting Recovery in hboot just displays an icon in the middle of the screen (a phone with a yellow warning sign in front)
I find guides on how to backup and restore for rooted phones all over the place, but I'd like to keep that device in original condition. Just want it working again.
So maybe there's a way to flash a working recovery rom through fastboot?
Maybe we can do some diagnosis using ADB in hboot?
Oh, and it's probably too late but backing up the contacts (and other data) would be great
Any help really appreciated!
Thanks!
Daniel

Sounds like you might be suffering from the 'bad' emmc problem.
There's information on the error here http://forum.xda-developers.com/showthread.php?t=1039504
In short, the internal memory card gets corrupted and cannot be written too, if you do have this problem there is nothing you can do, but get a replacement.
-Nipqer

Thanks! I'll contact HTC...
Still I can still connect to USB on the bootloader, do you think I have a chance of dumping my data partition so I can try to recover things later?

if you know how to do a dump I'd say its worth a shot. The emmc (i think) can still be read, just not written to.
-Nipqer

I don't know how to dump using fastboot. I found a way to upload an image to the phone, but I can't download.
Can anyone point me to a guide on how to dump Data using ADB/Fastboot?

Is there any way to get a shell in the bootloader and access the filesystem?

You might be able to use adb shell in recovery mode, but seeing as you don't have clockwork mod it may not work.
Give it a go anyway.
-Nipqer

No it doesn't work just like that...
I couldn't find any USB drivers that workes (not from the sdk and not from HTC Sync). The drivers from PDANet installed correctly though.
adb doesn't recognize the device, but it is recognized in Windows' device manager.
fastboot works though, but it can't download anything, right?
I'm not sure if it doesn't work because of the driver or if it's just not supposed to work with the normal launcher.
I guess I should just tell the guy his contacts are gone... I doubt it helps to put a note in, "please restore my contacts if possible", when I send it to HTC.
I just hope my device won't break the same way... But at least I have clockworkmod on it and I do regular backups and have everything synced to Exchange, so it won't be that much of a problem for me...
Thanks for all the help!

Related

USB error, cant do nothing with it

This is a strange problem, I cant tell when it started but it did all of a sudden. When I try to connect my phone to my computer it all of a sudden does not recognize the device (it shows under USB in device manager as unknown device). This happens on my laptop and stationary one (XP and Windows Home Server). On my work computer and my girlfriends laptop (Windows vista) nothing happens at all. The only thing happens is my phone shows notification about HTC Sync (doesnt show the "mount SD card" option). I cant install modaco 2.x since it says it isnt signed when I try to run update.zip from "home+power" mode.
Anyone knows a solution? I really want to flash either modaco or the official HTC rom.
latiszm said:
This is a strange problem, I cant tell when it started but it did all of a sudden. When I try to connect my phone to my computer it all of a sudden does not recognize the device (it shows under USB in device manager as unknown device). This happens on my laptop and stationary one (XP and Windows Home Server). On my work computer and my girlfriends laptop (Windows vista) nothing happens at all. The only thing happens is my phone shows notification about HTC Sync (doesnt show the "mount SD card" option). I cant install modaco 2.x since it says it isnt signed when I try to run update.zip from "home+power" mode.
Anyone knows a solution? I really want to flash either modaco or the official HTC rom.
Click to expand...
Click to collapse
have you instaled HTC Sync + the Android SDK? Drivers are included, also ensure you have gone to settings > Application Settings > Development.. and selected USB Debugging in the handset
if you have done the above you should be able to...
Sync your device
Do a nandroid backup
Root your device
and flash, flash, flash
hope this helps
Thing is, all those stuff is checked. The strangest thing is that the phone doesnt even ask me if I want to mount the SD card (to make the phone like a card reader). I successfully flashed the generic rom again (so my phone is not rooted etc etc) but it still cant connect to any computer through USB (except from when in bootloader (back+power). Its really starting to bugging me since I cant transfer music to the phone anymore I tried a hard-reset, flashed a generic rom (the new one) and formatted the SD card (the phone can read and write to/from it without problems).
I've got the same problem for quite some time now and still no answers...! :-(
It seems very few people on these boards know of our exact problem and i've never seen a solution. Also not from the many people on these boards I consider guru's. :-(
I'm at a total loss here...
I will call HTC Sweden today and see if they can help me solve this issue. I will get back to this thread as soon as Ive been speaking to them. This is starting to really bugging me.
First of all, I would try reformatting your SD card on the phone itself via Menu-> SD card & Phone Storage. If you need anything on the card, you'll have to stick the SD card in adaptor and attach it to your PC directly.
Secondly, by the sounds of it you haven't flashed Cyanogens recovery image, or your HBOOT is wrong, if you are getting a problem with the signature on Modacos image. Either flash Cyanogen recovery, or follow the instructions found on another thread for restoring your HBOOT to an earlier version.
Regards,
Dave
foxmeister said:
First of all, I would try reformatting your SD card on the phone itself via Menu-> SD card & Phone Storage. If you need anything on the card, you'll have to stick the SD card in adaptor and attach it to your PC directly.
Secondly, by the sounds of it you haven't flashed Cyanogens recovery image, or your HBOOT is wrong, if you are getting a problem with the signature on Modacos image. Either flash Cyanogen recovery, or follow the instructions found on another thread for restoring your HBOOT to an earlier version.
Regards,
Dave
Click to expand...
Click to collapse
I have tried to format the SD card already, didnt help.
What would the hboot have to do with the SD card mounting? I got the original hboot .0004 or somehting like that (never touched it).
This is the complete infor from my HBOOT screen (power+back).
HERO CVT SHIP S-ON
HBOOT-1.76.0004 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.06.18
Jul 3 2009,15:22:21
Should I update something? And how would that help me get USB connection to work outside fastboot? Since its only working in fastboot and not in the android system itself?
Answer from HTC:
If you are getting the 'USB Device not recognized' error in XP, then your device has a faulty USB port. You need to call our repair line to gte it booked in for repair. That really is all there is, once the hardware dies and starts giving that error, there generally is no hope apart from replacing the USB socket or the whole motherboard. best regards, HTC Europe Support
Would have been nice if they could include in this message where I should turn etc?
I had the same error when I flashed my unit with wrong radio image (newer version) without flashing system and boot images. Then I reflashed those as well and everything worked ok.
frcko said:
I had the same error when I flashed my unit with wrong radio image (newer version) without flashing system and boot images. Then I reflashed those as well and everything worked ok.
Click to expand...
Click to collapse
Is there any update.zip containing all those updates? and would it void my warranty? ex, would HTC be able to see any difference to the hboot etc?
Any guide you could point me to on how to update all those things?
See the following threads with people who have the same problems:
http://forum.xda-developers.com/showthread.php?t=556335
http://forum.xda-developers.com/showthread.php?p=4550938
I see more and more people with this problem!

Lost SD and USB support

Hello,
I have tried attempted to root and flash a new ROM on my phone and now I seem to have lost SD and USB support. it does not recognize any of the SD cards i put it (doesn't realize theres an SD card inside) and does not recognize any USB plugged in.
I have HBOOT .80 and i THINK i got the root correct (lotsa problems along the way so i'm not sure), but i was able to flash a ROM (NexTSENSE) so i think it worked. now, i saw a thread about fixing USB support but that required SD support. and reading that made me feel like i was royally screwed. in any case, any suggestions? I think USB support is still kinda there since I can get it to recognize it in the boot menu. but when i try to do it in recovery and use the flash rom .bat, it says device not found.
it would seem that the main concern right now is that i can't get it to see my SD cards. any of them, even after reformats and whatnot.
i can't connect to HTC Sync or anything of the of the sort. usually when i charge the phone, you get the charging notification but i don't even get that now. sounds like a driver problem but i can't see what is wrong. my computer doesn't even recognize the phone as a device every now and then
Hope i provided sufficient information. New to android scene so don't be too hard on me please =O but yea, any suggestions are welcome. thanks in advance
edit: usb support... ever so slightly back. aka, it charges now. probably was drivers on my lappy getting funny after moving between bootloader and recovery and all that fun stuff
You have the usb brick issue. Check out the thread on that. Also once you are up and running again, root using unrevoked or the fake flash method. All information is available in the dev forum.
ok, i've done some reading and this is what i've found so far. my phone is stuck in USB debug hence no USB support and somewhere along the way, SD support was disabled. from what i see, the fix is to
first:
reload the step1 of root to get back to 1.15 and basic root access.
second:
from there, i can re-enable SD support using the command:
fastboot oem enableqxdm 0
third:
apply USB-Brick fix found in post 1 of thread
and then i should be able to reload ROMs as usual. is this correct?
and where exactly do i put in the command to re-enable SD support? this is what has be confused right now. along with the commands for the USB fix
i am using the tinycore method so i just have the step1.sh. and then in the same console, can i enter that command? should i do it after a reboot? or load back into bootloader to do it. (bootloader or fastloader)
OOOOK. sorry about the continuous posts. putting new info up so it isn't exactly a bump right?
in any case, i used the androidSDK tools and ran the fastboot from there and i think i re-enabled my SD correctly. i was then able to run the USB-brick fix found on modaco forums. all done and done. nowww, since i just went through half the root process (step1.sh with tinycore), do i need to finish it? or since i had already rooted before, is it all done now?
I'm not 100% sure about that as I haven't had to fix the usb brick for ages now!
Download and install titanium backup from the market. If it works fine, then you are rooted. If not, root woth unrEVOked or fakeflash.
All the older root methods that require usb during the root process leave you open to the usb brick again.
Hi fatpandas..
Is your phone ok now? Actually my phone also have a problem like yours last week..until now,i can't fix it..if now your phone ok,can u share with me..thnks in advance..
@csyrix
sorry to hear about your situation. after just being there, i can tell how horrible it is. good news is, if you really have the same problem, then it is definitely fixable.
now, i don't know what method you used to flash yours the first time but from what i've seen, they're mostly the same. what you wanna do first is do that step1 thing where you have a temporary ROM installed. (1.15?) same process as usual.
then you'll need to run 'fastboot oem enableqxdm 0' with phone plugged in while in FASTBOOT (back button + power button thing)
in case you don't know where to put that in, you wanna run that in your command prompt (computer) while operating in the tools folder of the android SDK. (thank god for my limited computer knowledge cuz all the instructions i found just say, "run this command" and like hell if most know how/where)
in any case, the end result will be you having completed step1 and having re-enabled SD support. then turn off phone.
then get the fix from this thread
move that to your SD card (micro SD adapter) and turn back on your phone into bootloader. go to the recovery menu and hold volume up + power to bring up menu and hit the apply: update.zip.
then all should be well. i then moved on to step2 to make sure i had rooted properly. may not be necessary but i remember reading that rooting a rooted device isn't a problem so i just felt the need to do it to be safe.
that should be it. the link provided actually has all the instructions anyways (i hope mine are a bit more clear), but if not, that link should be able to fill in the holes. g'luck sir

HELP-phone no longer connects to the network or wifi

Hi, still a noob here. I was preparing for the procedure of going back to RUU to allow for the latest OTA update, and something must have gone wrong. I wish I had taken better notes. I was running the x3tremeSense122412 ROM, happy with it.
I did many backups before doing anything else (nandroid - both CWM and TWRP, Titatnium...), then connected the phone to load the older boot.img...For some reason, I first took the SD card out, connected to the computer and overwrote the boot.img file with one from a stock ROM.
Reaizing this was stoopid, I tried to fix it by rewriting the boot.img from the x3treme release. No luck.
So I tried to go back to the various backups, but the phone still does not work.
I also tried to connect it by USB, and am having another problem: adb works (ie adb devices returns the phone ID number), but fastboot does not (gets stuck in 'waiting for the device'). Any hint??
Thanks in advance!! :crying:
R: HELP-phone no longer connects to the network or wifi
fdafan said:
Hi, still a noob here. I was preparing for the procedure of going back to RUU to allow for the latest OTA update, and something must have gone wrong. I wish I had taken better notes. I was running the x3tremeSense122412 ROM, happy with it.
I did many backups before doing anything else (nandroid - both CWM and TWRP, Titatnium...), then connected the phone to load the older boot.img...For some reason, I first took the SD card out, connected to the computer and overwrote the boot.img file with one from a stock ROM.
Reaizing this was stoopid, I tried to fix it by rewriting the boot.img from the x3treme release. No luck.
So I tried to go back to the various backups, but the phone still does not work.
I also tried to connect it by USB, and am having another problem: adb works (ie adb devices returns the phone ID number), but fastboot does not (gets stuck in 'waiting for the device'). Any hint??
Thanks in advance!! :crying:
Click to expand...
Click to collapse
Try to reinstall the phone driver. When you are in fast boot try to locate the htc sync manager driver from the pc
Sent from behind you..
Problem solved
IT"S THE BACK COVER!!
Turns out while I was working on the phone, I kept the back cover off the phone so I could easily access the SD card.
Well....the back cover must contain either an antenna, or be part of the loop for one.
The moment I reconnected the back cover, WiFi came back and the signal on the phone is much stronger.
I now understand why the cover has spring contacts.
I hope this helps someone else - took me two hours of messing around to figure this out!
Now, on to the fastboot problem.

[Q] Touchscreen broken, how to restore backup

Hi, everyonem
I have a LG G3 D855P. It is currently running the CM12 from April 21st. I have a bug where it would get stuck at the boot screen. So I reflashed a few times, and was able to boot.
Problem is: I dropped it today and the glass cracked. The LCD is fine, but the digitizer does not work. I tried to turn it on, and I'm again stuck at the boot screen. I would like to restore a backup I have in my SD card. The problem is that this new TWRP recoveries only work with the touchscreen, and I can only operate a tiny 0.5 cm strip on the bottom. So I cannot restore my backup.
Can anyone help me out here? Is there a way to restore the backup using a computer? Or any combination of keys that would allow me to control TWRP using my HW buttons? I simply cannot understand why they did not implement a way to control TWRP using the HW keys, just like in the original android recovery...
I appreciate any help you guys can provide me!
Thanks,
You could try getting a USB OTG and try plugging a mouse into it but i doubt it will work
Best if you go get it repaired first and then do it
itsbighead said:
You could try getting a USB OTG and try plugging a mouse into it but i doubt it will work
Best if you go get it repaired first and then do it
Click to expand...
Click to collapse
My fear is spending the $ to get the screen repaired and then finding out that something else is broken. That's why I would like to restore a previous backup just to check if it boots, before sending it to repair.
Thanks for your response anyway, but I doubt the TWRP recovery would have the drivers for the usb mouse to work. I do have a usb otg cable at home, will test that later on today.
augusto.med said:
My fear is spending the $ to get the screen repaired and then finding out that something else is broken. That's why I would like to restore a previous backup just to check if it boots, before sending it to repair.
Thanks for your response anyway, but I doubt the TWRP recovery would have the drivers for the usb mouse to work. I do have a usb otg cable at home, will test that later on today.
Click to expand...
Click to collapse
I would suggest you do this. Boot TWRP and if your lucky MTP mode might be enabled and you can copy your TWRP backup off it, if it is on your internal sd card
After doing that Boot into Download Mode and Flash the factory firmware. You can reroot and restore you TWRP backup after your screen gets repaired. I know for a fact that after they fix the screen they will do service tests using the service menu of the phone and they will know if you rooted and have TWRP installed
By knowing that you rooted they will immediately cancel warranty
itsbighead said:
I would suggest you do this. Boot TWRP and if your lucky MTP mode might be enabled and you can copy your TWRP backup off it, if it is on your internal sd card
After doing that Boot into Download Mode and Flash the factory firmware. You can reroot and restore you TWRP backup after your screen gets repaired. I know for a fact that after they fix the screen they will do service tests using the service menu of the phone and they will know if you rooted and have TWRP installed
By knowing that you rooted they will immediately cancel warranty
Click to expand...
Click to collapse
Hey, thanks for the suggestions! After a few hours trying, I was able to restore my backup using ADB SHELL TWRP RESTORE And with the first backup that I had made, still with the original ROM/firmware, the phone booted up just fine. So now I can pay to fix my screen with peace of mind
Thanks everyone who helped. If anyone finds this topic and wants to do what I did, it is simple:
Boot your phone into TWRP
Make sure you have all drivers properly installed in your windows PC
Go to the Android SDK folder, open command prompt
type: adb devices, it should then list your device as " recovery"
type adb shell twrp restore YOURBACKUPPATH
In my case, I did a few " adb shell ls" before finding my backup folder.. Also, I had to download proper LG drivers in my PC and point windows to the correct driver in Device Manager. Good luck everyone!

Unable to access Bootloader, Recovery, ADB...

Hi,
I posted a response to this thread (http://forum.xda-developers.com/htc...pably-bricked-help-guys-t3462553#post68743293) but haven't received any replies.
I have a M8 which had previously been running the latest LeeDroid ROM and decided to try converting to GPE.
I downloaded the ROM, flashed the suggested firmware and then flashed the ROM. Things appeared to be going smoothly as the ROM booted up, but before I could get into the OS I got a message stating my data was encrypted and would need to reset.
I reset multiple times but got no further, as it turned out the partition (or data) was corrupt. A thread on here suggested formatting the partition in TWRP but when I tired this, I got an error.
Since then the phone does not boot, the screen stays black, I cannot force it into Recovery or Bootloader and ADB cannot see the device.
However, when I plug it into the PC I get the normal notification beep, and then Windows starts listing drives in My Computer/This PC.
In total there are ~21 drives, most of which 'require formatting' (although I suspect this is just Windows not recognising the filesystems) a few of them are readable and contain various android system files.
My assumption and I could be wrong, is that I've somehow wiped the Boot partition, which is why nothing seems to work...
My question is, since I can see the internal drive, can I 'ghost' a copy of a Stock device onto it? And will doing so allow it to boot?
I have both Linux and Windows at home so either could be used to do this if anyone knows how...
Thanks in advance,
Nick
TL;DR - Bricked my phone converting to GPE, PC only sees it as a storage device, can I 'copy' a Stock image and rebuild the partitions to save the device?
plz help me . I am too in a similar situation. no adb, bootloader,recovery. when i plugin the device so many partitions shows up on pc
update:
i could get into bootloader using this method. Certainly saved my nerves

Categories

Resources