Hi everyone!
Something is seriously messed up with my HTC Desire Z.
I downgraded my phone as described here:
http://forum.xda-developers.com/showthread.php?t=1178912
and rooted it like this:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I then installed ROM Manager, flashed clockworkmod recovery 3.0.0.5 and flashed Virtuous Unity ROM.
So I've got in Bootloader:
Vision PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
Radio-26.03.02.26_M
eMMC-boot
Everything worked without any problem - so far. After a few days (and no changes) the phone application of HTC crashed endlessly and I had to enter my PIN code (to unlock SIM) again and again. So I decided to flash a new ROM to fix this problem and this is where my real problems beginn. The ROM update to Cyanogenmod 7 failed.
First what I still can do:
- I can still enter the bootmanager and use fastboot from the computer.
- I can still access cwm recovery but only with errors.
- I can still flash some ROMs (like MIUI) via recovery without any errors, but it changes nothing.
Now what I can't do:
- I can't use adb, the device doesn't show up.
- CWM recovery shows the following errors at startup:
Can't mount /cache/recovery/command
Can't mount /cache/recovery/log
Can't open /cache/recovery/log
Can't mount /chache/recovery/last_log
Can't open /cache/recovery/last_log
- I can't boot up my phone, it ends with the HTC screen (waited for a long time >20min).
- I can't flash a newer or older recovery using fastboot (tried a few):
sending 'recovery' (3624 KB)... OKAY [ 0.624s]
writing 'recovery'... FAILED (remote: image update error)
- I can't perform a RUU. After clicking through all the warnings and starting the update process RUU wants to restart the bootmanager at the beginning of the procedure. This ends with the HTC Screen and RUU brings a connection error after a minute or two. I tried different RUUs.
- I can't manually flash the PC10IMG.zip. The bootmanager brings the errors:
SD Checking...
Loading...[PC10DIAG.zip]
No image!
Loading...[PC10DIAG.nbh]
No image or wrong image!
Loading...[PC10IMG.zip]
No image!
Loading...[PC10IMG.nbh]
No image or wrong image!
But it loads the PC10IMG.zip anyhow and brings the "parsing...[SD ZIP]" screen with possibility to start update now. After pressing volume up to start flashing ends with error "Fail-PU" at the first entry (Bootloader) and below it says "Partition update fail!". I tried different PC10IMG.zip's.
- I can't do a NANDroid restore in cwm. It says:
Erasing boot before restore...
Error while erasing boot image!
I also formatted the miniSDHC card, did wipes in cwm and performed a full wipe using SuperWipe from the forum here. I hope I didn't forget anything...
I really don't know what else I can do. I would be so thankful if anyone has an idea or solution for me! Thanks in advance!
Sounds like you have the bad emmc chip, in which case you'll have to get a replacement.
Here is more info on the error.
-Nipqer
Thx Nipqer for your quick answer and your hint!
So I will send it in. But what should I tell them what I've done? I know they find out anyway but what did you tell? You just wrote "my phone doesn't boot" or the full history?
Thanks for your advice!
greets
well can you flash stock rom possibly? Any chance you can get it going long enough to unroot?
I didn't send it back to HTC, as I bought it from a local importer.
Most people have had no issues with rooting, as its a hardware issue so it's HTC's responsibiltiy to replace it anyway.
-Nipqer
So you have a dead eMMC. Can you get the phone replaced? If so, before you send it in - would you like to be a guinea pig? You have the engineering hboot - do you know how to use fastboot?
Hi, thx for the answers!
well can you flash stock rom possibly? Any chance you can get it going long enough to unroot?
Click to expand...
Click to collapse
Using a RUU didn't work and flashing the PC10Diag.zip from the downgrade page (this should be stock) failed too. Is there another way?
I didn't send it back to HTC, as I bought it from a local importer.
Click to expand...
Click to collapse
So the local importer replaced the phone without sending it to HTC or the responsible service center first?
Can you get the phone replaced?
Click to expand...
Click to collapse
I hope so but I'm not sure, as it's easy for HTC or the service center to recognise that I bricked it by flashing/unrooting and there's no more warranty.
If so, before you send it in - would you like to be a guinea pig?
Click to expand...
Click to collapse
Here I'am!
You have the engineering hboot - do you know how to use fastboot?
Click to expand...
Click to collapse
Yes, but I'm no expert. If I'm in bootloader the command fastboot devices shows my phone, so little experimenting should be possible. What should I do?
remo.sp said:
I hope so but I'm not sure, as it's easy for HTC or the service center to recognise that I bricked it by flashing/unrooting and there's no more warranty.
Here I'am!
Yes, but I'm no expert. If I'm in bootloader the command fastboot devices shows my phone, so little experimenting should be possible. What should I do?
Click to expand...
Click to collapse
Disclaimer: Please be aware that following this procedure could permanently brick your phone; so if you don't fancy having a potential paperweight, you don't have to do this.
Could you run the following commands?
fastboot oem reinit_nand
fastboot oem rebootRUU
fastboot erase system
fastboot erase userdata
and tell me its' output?
Mhhh ok then I prefer to send it in first. Maybe I'm lucky and I get a replacement. But if not, I will definitely try these commands.
I'm in Switzerland and I have to send it to the responsible service center. What do you think should I tell them that I most likely get a replacement?
Basically same stuff here. DZ:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MIVROP-0425
RADIO-26.10.04.03_M
can get into fastboot. If i try to go to recovery, device shows htc boot screen, the boot screen with green pictogram, and then switches off, vibrating about six times in a row.
reinit_nand - Command error
rebootRUU - device gets stuck (previously it did load into that mode, but stopped after some time)
erase system - not allowed
erase userdata - same
erase cache - gets stuck (freezes)
As far as I get, bad emmc here? everything was fine till couple of days before - at first freezes and reboots, afterwards - stuck at boot forever.
sam_banshee said:
Basically same stuff here. DZ:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MIVROP-0425
RADIO-26.10.04.03_M
can get into fastboot. If i try to go to recovery, device shows htc boot screen, the boot screen with green pictogram, and then switches off, vibrating about six times in a row.
reinit_nand - Command error
rebootRUU - device gets stuck (previously it did load into that mode, but stopped after some time)
erase system - not allowed
erase userdata - same
erase cache - gets stuck (freezes)
As far as I get, bad emmc here? everything was fine till couple of days before - at first freezes and reboots, afterwards - stuck at boot forever.
Click to expand...
Click to collapse
Well there's your problem - your hboot is S-ON and it's not an engineering hboot. See if you can update it.
Unfortunately, all the methods to update hboot to ENG I located require working adb. Would appreciate if you point me to one with fastboot.
I did try flashing official RUU. If I use .exe process gets stuck at rebooting into update (rebootRUU). If I use PC10IMG.ZIP on SD card - update gets stuck at flashing boot - it saz "updating" and no changes for minutes, and nothing changed after reboot. Can't boot into recovery also.
As far as I understood from reading around, this is probably caused by corrupted emmc chip.
sam_banshee said:
Unfortunately, all the methods to update hboot to ENG I located require working adb. Would appreciate if you point me to one with fastboot.
I did try flashing official RUU. If I use .exe process gets stuck at rebooting into update (rebootRUU). If I use PC10IMG.ZIP on SD card - update gets stuck at flashing boot - it saz "updating" and no changes for minutes, and nothing changed after reboot. Can't boot into recovery also.
As far as I understood from reading around, this is probably caused by corrupted emmc chip.
Click to expand...
Click to collapse
Yes, it is caused by a corrupt eMMC. I'm just trying to see if there's a way out of it. I have a couple of ideas.
This is why I wish I was in physical possession of a bad eMMC phone then I could work and work at it.
This is why I wish I was in physical possession of a bad eMMC phone then I could work and work at it.
Click to expand...
Click to collapse
My phone (DZ with eng hboot and corrupt emmc) is now in repair. We'll see if they do it under warranty or how much I have to pay for it. If it's to much I maybe can send you the phone via airmail. But for now I just have to wait...
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.10.04_03M
eMMC-boot
fastboot oem reinit_nand: ... INFO[ERR] Command error !!!
fastboot oem rebootRUU: ... OKAY [ 2.936s] -> reboot
fastboot erase system: erasing 'system'... -> stuck
fastboot erase userdata: erasing 'userdata'... -> stuck
---------- Post added at 12:20 PM ---------- Previous post was at 12:02 PM ----------
remo.sp said:
My phone (DZ with eng hboot and corrupt emmc) is now in repair. We'll see if they do it under warranty or how much I have to pay for it. If it's to much I maybe can send you the phone via airmail. But for now I just have to wait...
Click to expand...
Click to collapse
i'm also in switzerland, please keep me up to date.
Hey!
I've got my phone repaired under warranty conditions. They changed the motherboard. Just told them what happend (freeze, battery remove, no more booting).
CH related info: Bought phone by digitec and sent it to Arvato Teleservice.
Related
I've been fighting this for hours over the last couple of days....
I rooted my phone (ebay-purchased T-mobile G2) a few months ago with the Cyanogenmod guide (http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting), got Clockworkmod on using Rommanager and (almost) everything was good.
Recently, the entire phone crashed and seemed to get stuck in a boot loop. I booted into CWM recovery (v3.0.2.4). CWM gave me these errors every single time:
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
"E:Can't open /cache/recovery/log"
"E:Can't mount /cache/recovery/last_log"
"E:Can't open /cache/recovery/last_log"
I tried to just reflash CM7 that I loaded onto the SD card via windows, always wiping data and cache first. The install would start, and then abort with "E:Error in /sdcard/update.zip" and "(Status 1)". Eventually one of the versions of CM6 started to actually install with the progress bar, but then would abort with "assert failed: write_raw_image" and "(Status 7)". Googling pointed to CWM possibly being the problem, saying updating to 3.0.2.5 would fix it. I haven't found a download for that, and because I'm stuck with boot loops, I can't get to Rommanager.
I tried using fastboot to flash the same version of CWM, but it comes up with "Failed (remote: not allowed)". Googling hints that installing stock ROM (PC10IMG?) would fix it, but I can't get that to flash or fastboot on.
I don't have a NAND backup, but I do have a CWM backup that I can't fully restore from because it always says "Error while formatting /system!". Haven't found a fix for that.
I am able to connect with ADB, but I've tried checking for the eMMC serial to see if I have a culprit chip (http://forum.xda-developers.com/showthread.php?t=1081243), and it doesn't return a value.
This thread OP is actually almost the exact same thing as I've been through except the last part about loading with hboot, which I can't get to work. And I've tried with the sd card mounted and unmounted.
I'm stumped, as most of the solutions are just "reflash ROM" or "reflash recovery" and I can't get either to work. At this point, I don't think I care if I end up rooted/customROM or stock. Any help is appreciated a hundred fold.
S-Off
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.0226_M
eMMC-boot
Hey,
Sorry, I have had the same exact problem. Spent a week+ working non stop, following every tutorial on the forums to try and fix it. I've had zero luck. good thing it was in warranty for me, I just sent it in and got a new one. just enjoying my non-rooted G2 now. I hope there is a fix for this somewhere, It has been happening quite a bit.
That's a bit discouraging. I wish I had the knowledge of the topic to even understand what the actual problem is, unless it's multiple smaller problems that I'm dealing with. It doesn't seem like a full-brick situation, but I guess it is.
Re: warranty - was it through HTC or the carrier? And how did you convince them to accept it? They usually say that rooting voids warranty, eh?
Tmobile told me rooting voids Htc 1 year warrenty but still have 129.
deductable through asurion for 5. a month.
I called Asurion to verify.
Sent from my HTC G2 using XDA Premium App
just curious but why doesn't fastboot work? otherwise you could try to recover via fastboot:
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot reboot
Here is a thread about the error
Its most probably a hardware issue, so there's nothing you can do about it except return it.
Also, fastboot probably doesn't work cause you don't have eng hboot?
-Nipqer
http://forum.cyanogenmod.com/topic/20898-easy-way-to-flash-eng-hboot-new-80416-radio-and-cwm-3024/
That PC10IMG worked great for me. All you need is S-OFF.
Once you get eng hboot, use fastboot to flash the recovery.img from your last working nandroid backup. Might want to do 'fastboot erase recovery' just before 'fastboot flash recovery recovery.img' just to give a clean slate.
Once you get in CWM you can format system, data, cache and restore from nandroid.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!
killerbee12345 said:
just curious but why doesn't fastboot work? otherwise you could try to recover via fastboot:
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot reboot
Click to expand...
Click to collapse
"fastboot erase boot"
"Failed (remote: not allowed)"
Nipqer said:
Here is a thread about the error
Its most probably a hardware issue, so there's nothing you can do about it except return it.
Also, fastboot probably doesn't work cause you don't have eng hboot?
-Nipqer
Click to expand...
Click to collapse
starting to seem more and more like it's hardware. i don't have an Eng HBOOT, but I am S-OFF. Cyanogen wiki says that should be enough, but I'm still stuck, so maybe.
onelikeseabass said:
http://forum.cyanogenmod.com/topic/20898-easy-way-to-flash-eng-hboot-new-80416-radio-and-cwm-3024/
That PC10IMG worked great for me. All you need is S-OFF.
Once you get eng hboot, use fastboot to flash the recovery.img from your last working nandroid backup. Might want to do 'fastboot erase recovery' just before 'fastboot flash recovery recovery.img' just to give a clean slate.
....
Click to expand...
Click to collapse
tried that PC10IMG.zip and it actually recognized it as soon as I got into HBOOT. but then I came up with the Partition Update Fail message.
Any tips on convincing HTC to warranty it anyway?
tatsuha said:
"fastboot erase boot"
"Failed (remote: not allowed)"
starting to seem more and more like it's hardware. i don't have an Eng HBOOT, but I am S-OFF. Cyanogen wiki says that should be enough, but I'm still stuck, so maybe.
tried that PC10IMG.zip and it actually recognized it as soon as I got into HBOOT. but then I came up with the Partition Update Fail message.
Any tips on convincing HTC to warranty it anyway?
Click to expand...
Click to collapse
This may be a shot in the dark, but have you tried reformatting your SD card? Back it up, format, and just put that PC10IMG.zip I linked earlier on it. Maybe it's a problem reading from the source that causes the write to fail.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!
onelikeseabass said:
This may be a shot in the dark, but have you tried reformatting your SD card? Back it up, format, and just put that PC10IMG.zip I linked earlier on it. Maybe it's a problem reading from the source that causes the write to fail.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!
Click to expand...
Click to collapse
Hadn't gotten a chance to do much during these last few days, but I finally sat down with the G2 again. I had already tried formatting, but it was a quick format, I'm fairly certain.
I tried with full reformats on both the SD cards I have (the 8GB Sandisk that came with the phone and an older 2GB Kingston). One recognized the PC10IMG, but had the same partition update fail. The other didn't even recognize the file.
If this ends up being unrecoverable, does anyone have any advice for a shot at the HTC warranty? or is there no chance that they would miss the fact that it's rooted? >_>
Hi All,
Sorry another n00b making a n00b thread.
I bought a second hand desire very cheap under the understanding that "stopped booting one day" - so first thing first, if it is bricked, so be it.
Currently it only gets as far as the white HTC screen.
Now, when booting with PWR + Vol Down:
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
RADIO-5.17.05.23
Obviously the PO has been playing around given the unlocked bootloader. I can get into fastboot fine. fastboot devices shows the Serial of the device.
So following the Troubleshooting guide here I attempted to flash a Recovery image as per recommendation. It shows sending and writing recovery.img OK, and the two progress bars display on the phone in line with that. However, when rebooting (fastboot oem gencheckpt), I still can't get into recovery - it goes back to the HTC screen again. Same with fastboot reboot-bootloader if it matters.
***EDIT - kept looking on this forum and it seems as if this bootloader would be write protected against RUU updates? So you can probably disregard what was here. I'll keep looking around, but if anyone has advice feel free!
If I'm missing something silly here, feel free to abuse me while you tell me what it is. Just thought I'd check to see if I'm on the right track or I've failed miserably.
Thanks.
Download the HBOOT downgrader from alpharev.nl (and the stock HBOOT, too).
Flash the
1. stock HBOOT,
2. the downgrader
3. then the RUU of your choice (2.3.3/2.2 depends on you).
As you said, you can get to fastboot, it'll work.
You'll get a stock, unrooted device, but you can root it later on.
davebugyi said:
Download the HBOOT downgrader from alpharev.nl(and the stock HBOOT, too).
Flash the
1. stock HBOOT,
2. the downgrader
3. then the RUU of your choice (2.3.3/2.2 depends on you).
As you said, you can get to fastboot, it'll work.
You'll get a stock, unrooted device, but you can root it later on.
Click to expand...
Click to collapse
Thanks for that - I flashed these in this order from fastboot and then rebooted - I can see that it has taken effect due to seeing "AlphaRev Unlock" now, however, can't get the RUU to go - gets to Rebooting to bootloader, phone reboots and gets stuck in a bootloop (I suppose - HTC screen, black screen, and so on). Eventually it gives up and gives [171] USB CONNECTION ERROR. "Reboot Bootloader" from the fastboot menu does the same thing.
I actually have an Atrix so this is not my daily driver, so nothing too urgent, or in fact tragic if it is a hardware issue. I do appreciate any help though all the same!
Hmm - can be the cable, the drivers.
Even some people said, that using win7 64Bit will get you this error.
I'd check first the drivers. Maybe you have USB Brick as well - search the Dev Thread for a fix - basically 2 commands.
I was just reading up on the USB brick actually, as you say doesn't seem like too much effort anyway.
I am using Win 7 x64 in fact... I will copy all the necessaries to a USB stick and use a WinXP box at work just to make sure. Thanks again!
OK, update -
Same result on a WinXP machine trying to flash via RUU.
When I try fastboot oem enableqxdm 0, I get:
partition_read::Too many bad blocks(out of range)
It does say OK after that though?
If I try to flash a mtd0.img via fastboot (I assume I can't use an SD card given I can't boot) with SuperCID as the CID (either hex edited or with the script) I get:
sending 'misc' (640KB) OKAY
writing 'misc' (640KB) ... FAILED (remote: image update error)
It's late here so I'll search more in the morning, but any guidance would be appreciated.
Should I be erasing the misc partition before attempting to flash mtd0.img? If that's where I've gone wrong I'll kick myself, but thought I should confirm before I break the phone more.
Update:
I grabbed the rom.zip from the temp folder, renamed it to PB99IMG put it on a MicroSD and let the phone do its thing. It worked, in that it performed the update, but Radio_v2 failed - so I assume this means either I have a branded handset that has nothing on the outside (how do I check?) or there is a hardware fault?
Of course, I have S-ON now because everything else worked...
radio failure means you're kinda fu*cked IMO... I mean I know a user who kept trying a RUU who eventually undid the radio fail but ermm.. yeah usually it means a real brick
I figured that might be the case. Given the bootloader was already unlocked when I received the phone, one can assume the previous owner actually knew what they were doing and had already tried to fix it and come to the same conclusion.
I'll update the thread if I manage to fix it, but if anyone else stumbles across this due to similar circumstances, looks like you have your answer.
PS: bortak your troubleshooting thread was an amazing help.
Thanks to all!
yeah just try the RUU a couple of times (like 10 or something) and see what happens.. if you're lucky you might get a break..
or what you could do is flash the 2.3.3 RUU, hope it works, and if you do get stuck in splash HTC will cover you warranty!! just tell them you try to upgrade and it broke!
Hello,
my HTC desire has been rooted for like 8 months or so, with Oxygen 2.3.2 ROM installed. Yesterday i had my first problem, my apps began to freeze, and it ended up that my hole phone were froozen. I pulled my battery in and out, nothing happened.
I went into recovery and made a factoery reset, and wiped everything i could (i have read, that it was a good idea) and when i turned my phone up again, i realised that i had deleted my ROM on the phone...
So again... i went in to recovery and tryed to flash my ROM again, but i ran into a problem:
Code:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
after i googled and tryed for like an hour and a half, i got it fixed with
Code:
cd C:\android-sdk-windows\platform-tools
fastboot oem enableqxdm 0
fastboot oem eraseconfig
and as i remember i took my batteri out again, and placed my memery-card into my computer, moved my ROM (oxygen 2.3.2) over again. So i tryed to get into recovery, but now it wont get in there, after i press the POWER-button on "Recovery" it just stocks on the HTC load screen, i left it that way the hole night, and when i woke up, nothing was happened...
i pulled my battery out, and now i got some problems just booting up to fastboot/hboot to.
so the problems now:
problems getting into RECORVERY
Sometimes problems booting to HBOOT/FASTBOOT
If you need any information, please tell me so
PS: Im sorry if my english is kind of bad
You should try flashing a new recovery image via fastboot once you get there. That worked for me when i couldnt enter recovery.
Sent from my HTC Runnymede using XDA App
according to....
EvertorN said:
You should try flashing a new recovery image via fastboot once you get there. That worked for me when i couldnt enter recovery.
Sent from my HTC Runnymede using XDA App
Click to expand...
Click to collapse
according to: theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted i need to get into the phone and download an app, and i dont got a ROM installed, i kind of deleted it in a way
magnuskahr said:
according to: theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted i need to get into the phone and download an app, and i dont got a ROM installed, i kind of deleted it in a way
Click to expand...
Click to collapse
I assume you are S-OFFed so just download a recovery.img file of your recovery, boot into fastboot and flash via fastboot utility your recovery.img file like 'fastboot flash recovery path\to\recovery.img'
Goodluck!
USB functions are working? (Mount/debuging)
alexei_kom said:
I assume you are S-OFFed so just download a recovery.img file of your recovery, boot into fastboot and flash via fastboot utility your recovery.img file like 'fastboot flash recovery path\to\recovery.img'
Goodluck!
Click to expand...
Click to collapse
I'm S-ON, will this help:?
http://forum.xda-developers.com/showthread.php?t=1275632
"I'm S-ON, I can't boot recovery, and my phone doesn't boot "
This is a bit of a worse situation, as you cannot flash system critical parts such as the recovery image and just restore a backup. This unfortunately means that you will lose all of your data when you attempt to fix the phone.
[STEP1]- Make sure that you have a goldcard. If not, create one from the tutorial.
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
[STEP3]- Download the latest WWE RUU from here
[STEP4]- Run the RUU and wait for completion WARNING: DO NOT, BY ANY CIRCUMSTANCES INTERRUPT THE PROCESS - THIS WILL MORE THAN LIKELY END UP WITH A BRICKED PHONE - NOT EVEN IF GOD HIMSELF TELLS YOU TO DO SO, OR IF THE US PRESIDENT THREATENS YOU WITH THERMO-NUCLEAR WAR
[STEP5]- Once the phone is booted, you are now returned completely to stock. You will need to re-root again, and I'd recommend S-OFF
Click to expand...
Click to collapse
name.vic said:
USB functions are working? (Mount/debuging)
Click to expand...
Click to collapse
i dont remember, im in school and was stupid enough not to take the desire with me, i will test later when i come home
What is the hboot version?
name.vic said:
What is the hboot version?
Click to expand...
Click to collapse
Again, when i come home i will tjeck it
so in about 4 hours
My freind got the Desire too, and it's as old as mine, and we rooted our phones from the same tutorial.. so i gesh we got the same hboot version??
here is his hboot (as i remember, i got the same) HBOOT-0.93.0001
magnuskahr said:
I'm S-ON, will this help:?
http://forum.xda-developers.com/showthread.php?t=1275632
Click to expand...
Click to collapse
Are you sure you are S-ON? Because you can't perform these
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Click to expand...
Click to collapse
if you are S-ON...
Post here your phone specs while in hboot...
last i checked i was on S-ON, i dont know if that were those commands which helped me (but it think it was)
but i will make sure about it, when i get home
now writing what is on the fastboot screen:
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
TOUCH PANEL-SYN0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
name.vic said:
USB functions are working? (Mount/debuging)
Click to expand...
Click to collapse
My pc is making a sound when i connect it, but it wont find the hdd, but i can run
Code:
fastboot oem boot
and the phone boots and stucks and the android-skatbording-screen
i just ran
Code:
fastboot reboot
the phone shut down, and i cant turn it on... any ideas?
magnuskahr said:
i just ran
Code:
fastboot reboot
the phone shut down, and i cant turn it on... any ideas?
Click to expand...
Click to collapse
SLCD brick?
Try to pull the battery, power on + back (this will get you into fastboot), wait about 10-20 seconds, then connect it to usb. In fastboot utility type 'fastboot devices' and see if it detects your phone. If it does, run an RUU.
Jep i tryed pull the battery out, i can still not turn it on
magnuskahr said:
Jep i tryed pull the battery out, i can still not turn it on
Click to expand...
Click to collapse
If you are SLCD bricked you won't see anything on your screen. Read the previous post I wrote...
i guess that "fastboot utility" is cmd right??
if that so, nothing happend
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message <bootrom> [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
ragus15 said:
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
Click to expand...
Click to collapse
Try this ruu its the newest officially signed ruu, so it will work with s-on. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Trygon said:
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Click to expand...
Click to collapse
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
cmlusco said:
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
Click to expand...
Click to collapse
Holy cow, props on the quick reply. You're pretty much confirming my fears. I've tried a few combinations of battery and usb connections, but there's no vibration nor ADB signal.
I can't say I've ever seen a stock utility behave this way, so user beware. It's also worth noting that I have no history on this phone's modifications - Just that it was S-ON and locked when I got it, in bootloops between kernel and ROM, and attempting to access recovery looped it too.
cmlusco said:
Try this ruu its the newest officially signed ruu, so it will work with s-on. Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
Click to expand...
Click to collapse
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
ragus15 said:
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
Click to expand...
Click to collapse
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
cmlusco said:
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
Click to expand...
Click to collapse
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
ragus15 said:
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
Click to expand...
Click to collapse
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
cmlusco said:
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
Click to expand...
Click to collapse
I have tried fastboot erase recovery followed by the flash and still get the white HTC image. I am not able to boot the os... i get white HTC splash image over and over, and the USB driver that tries to mount to my desktop in the bootloop is not Android 1.0, it is CMDA technologies. I have no idea what that is or if that has to do with the previous frawg/straight talk flash attempts.
Following on from this problem:
http://forum.xda-developers.com/showthread.php?p=39472437
Phone has been working fine after install of AOKP (http://forum.xda-developers.com/showthread.php?t=1642443).
Until I swapped SIM cards to try EE vs. GiffGaff for service and running costs.
I switched SIM card back and phone started boot loop.
HTC screen then AOKP screen with Unicorn head, then phone resets and starts loop again.
So tried booting without SD card and SIM get to home page for a few second and then reboots.
So tried wipe data/factory reset and wipe cashe partition, now get as far as first page of new android user, then reboots.
With power button and - key I get:
vision pvt eng s-off
hboot- 0.76.2000 (PC1011000)
microp-0425
radio-26.03.02.18_M3
eMMC-boot
Suggested next course of action? As I assume AOKP and/or Android is damaged.
I have read most of the boot loop topics, but do not seem to cover this version of boot loop (So new topic). Do not want to go any further until I was sure I would not make things worse.
Ive heard a couple people complain about similar things before but truthfully the reason why doesnt make too much sense to me, do you mind capturing a logcat?
also may be interested in reading through THIS PAGE if you havent already. also will find info on logcats here if youre unaware
my guess is there is a corrupt partition somewhere as after doing some wiping you still have a bootloop
to fix it youll be best of starting with a full wipe and format, either by formatting all partitions in 4ext recovery,
flashing a superwipe script, or the aio nullifier script (both linked in the thread above)
or booting into fastboot and wiping from there
fastboot erase system -w
or do all those, im a bit ocd when it comes to wiping so i would
if this fails then it could be within a firmware partition, like radio or hboot, this seems unlikely to me as
there shouldnt be an write to these at all, but your situation is uncommon and a bit strange so
if you want flash a new radio and or hboot via fastboot OUTLINED HERE or go to the 30th thread and flash a PC10IMG.zip
good luck!
I'm facing a similar bootloop and can't figure out why
@demkanator
Can you please have a look at my thread?
http://forum.xda-developers.com/showthread.php?t=2214813
Re: [Q] Desire Z bootloop with JB roms
Can you post a logcat? Also will you boot into your bootloader and write down EVERYTHING on that screen here?
Sent from my Nexus 7 using xda premium
Requested information
demkantor said:
Can you post a logcat? Also will you boot into your bootloader and write down EVERYTHING on that screen here?
Click to expand...
Click to collapse
I only have clockwork recovery 5.0.2.7 on phone, not sure I can put on or use 4ext recovery, flashing a superwipe script, or the aio nullifier script.
I have wipe data/factory reset which got this result
"Formatting /data
Formatting /cache
Formatting /sd-ext
No app2sd partition found. Skipping format of /sd-ext.
Formatting /sdcard/.android_secure
Data wipe complete."
Also did wipe Dalvik Cache:
"Dalvik Cache wiped"
At this point phone will still do reboot loop.
But on booting into fastboot and wiping from there fastboot erase system -w. Phone now sits on HTC screen.
Though I can still get to clockwork recovery and Hboot/Fast boot.
Again here I will stop so as not to make anything worse.
Here information you asked for:
System Info
SN-HT0AJRT03242
LCD-S0
Touch Panel-ATEMEL224_20aaY
Commit-97743036
OS Ver.01.34.707.3
IMEI-352212040170091
CID-11111111
eMMc-unknown 2223MB 4554751sectors
IMAGE CRC:
hboot: 0x6570C0DB
boot: 0x70A9908C
recovery: 0xB983BB96
system: 0x61EF2FF9 (THIS was result before I did fastboot erase system -w")
system: 0x0 (Is result after fastboot erase system -w")
With ADB running I plug USB into phone, phone boots to clockwork recovery menu (Which I can move up and down menu with -/+).
Note: I use the menu for about 25 seconds and regardless of any pressing - or + before screen go's blank. But orange LED on (I assume charging?).
I type: "adb devices"
I Get "HT0AJRT03242 recovery"
I type: "adb logcat > logcat.txt"
File saved has just "/sbin/sh: exec: line 1: logcat: not found"
You are missing the first bit of info in hboot, can you please add this, lines starting at
Vision pvt.....
Also is fastboot working?
Sent from my SGH-T839 using Tapatalk 2
More information
demkantor said:
You are missing the first bit of info in hboot, can you please add this, lines starting at
Vision pvt.....
Also is fastboot working?
Sent from my SGH-T839 using Tapatalk 2
Click to expand...
Click to collapse
Booting phone (Holding power + -Key) I get:
Vision PVT ENG S-OFF
HBoot-0.76.2000 (PC1011000)
MICROP-0425
EMMc0-boot
Aug 20 2010, 16:51:01.
Hboot screen shows "HBoot USB PLUG", when I select FASTBOOT from menu screen displays "FASTBOOT USB".
But with phone on this screen displaying "HBoot USB PLUG" or "FASTBOOT USB", I type "adb devices" and get nothing but text "List of of devices attached" nothing after that.
But if I repeat "With ADB running I plug USB into phone, phone boots to clockwork recovery menu (Which I can move up and down menu with -/+)."
I type: "adb devices"
I Get "HT0AJRT03242 recovery"
adb will only work in recovery and in os (so long as debugging on etc)
in fastboot mode use fastboot, similar but different
HERE ARE SOME TIPS ON FASTBOOT i suggest to study them as they can be just as handy as adb
but for now try to get into fastboot mode and type this is cmd
Code:
fastboot devices
if you see yours good, if not read the linked thread
then go with
Code:
fastboot oem check_emmc_mid
see if it says samsung or sandisk
the above is goo information to know, so check it out and respond back.
but i believe you will find your fix HERE
read and ask questions if needed
good luck!
Contining understanding
demkantor said:
adb will only work in recovery and in os (so long as debugging on etc)
in fastboot mode use fastboot, similar but different
HERE ARE SOME TIPS ON FASTBOOT i suggest to study them as they can be just as handy as adb
but for now try to get into fastboot mode and type this is cmd
Code:
fastboot devices
if you see yours good, if not read the linked thread
then go with
Code:
fastboot oem check_emmc_mid
see if it says samsung or sandisk
the above is goo information to know, so check it out and respond back.
but i believe you will find your fix HERE
read and ask questions if needed
good luck!
Click to expand...
Click to collapse
Typing "Fastbook devices" shows my device.
Typing "fastboot oem check_emmc_mid" I get:
"<bootloader> Manufacturer ID, MID=45
<bootloader> eMMC should be unkonwn
OKAY [ 0.000s]
finished. toal time: 0.016s"
Trying to understand why this happened and what was damaged, but seem next stage is to re-do and clear old install (You link above)?
Could I just put Android 4 rom back on at this point, if that was only damage? or better to check and other parts of install?
These are the guides I originally used to setup Android.
http://wiki.cyanogenmod.org/w/Install_CM_for_vision
http://forum.xda-developers.com/showthread.php?t=1642443
Well I don't like that lit says unknown but there really isn't much more you can do @ this point. I would just flash one of those PC10IMG.zips and if it works flash a new ROM, you'll either have a working phone or be in the same place you are right now
Good luck!
Sent from my Nexus 7 using xda premium
Trouble ahead?
demkantor said:
Well I don't like that lit says unknown but there really isn't much more you can do @ this point. I would just flash one of those PC10IMG.zips and if it works flash a new ROM, you'll either have a working phone or be in the same place you are right now
Good luck!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
PC10IMG.zip on SDCARD booted Hboot and get:
SD Checking
Loading...[PC10DIAG.zip]
No Image
Loading...[PC10DIAG.nbh]
No Image or Wrong image!
Loading...[PC10IMG.zip}
No Image
Loading...[PC10IMG.nbh]
No Image or Wrong image!
There seem to be alot of PC10IMG.zip am I using wrong one? If so do you have a link for HTC Desire Z version?
Use one of the two that I made, dont use others, I linked them to you earlier, the instructions on how to flash is there as well.
The reason you are getting this message though is you either didn't name it right, its not on root of SD, SD is not formatted properly, etc
Sent from my Nexus 7 using xda premium
Up and running.
demkantor said:
Use one of the two that I made, dont use others, I linked them to you earlier, the instructions on how to flash is there as well.
The reason you are getting this message though is you either didn't name it right, its not on root of SD, SD is not formatted properly, etc
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for your help, from a person who just about understand which way up to hold phone
After following your links and all stages and then reinstalling Android Open Kang Project builds for HTC Vision, phone working again (For the moment).
But still trying to understand why this happened, as switching SIM cards should not do this.
So one I had finished setting up phone again I when back to some of your previous questions and comments.
re-tried "fastboot oem check_emmc_mid" result:
"<bootloader> Manufacturer ID, MID=45
<bootloader> eMMC should be Scandisk
OKAY [ 0.016s]
finished. toal time: 0.016s"
Which is different from last time (and was something you did not like before). Let me know I can make any other checks that might help someone else out of the same problem?
Can't say for sure why this happened but you had a severely corrupt partition on the emmc and phone wasn't even reading its id. Changing the sim shouldn't do this and it could have been some kind of coincidence but I've heard others say the same thing before so.... Your guess is as good as mine.
Glad its all working!
Sent from my Nexus 7 using xda premium
Try reflashing the baseband changer.zip and then the simunlock.zip after changing the SIM Cards.