[Q] maybe bricked with visonary. Please help - G2 and Desire Z Q&A, Help & Troubleshooting

Mod Edit: Threads posted in the wrong fora will be closed! READ BEFORE POSTING!~TheRomMistress
I try temp root my G2 with visonary and all works good. Then try to perm-root but when the phone reboot itself it freeze on htc logo.
I can get to hboot, fastboot and recovery (original ones) but the phone is post ota and S-ON.
So I try adb on recovery but tell me "device offline".
Then try factory reset but nothing new.
Then try to reflash the ota update from recovery, this work but after reboot no more than htc green logo.
Then try to flash original PC10img.zip but say "main version is older".
There is some solution?

Oh dear not sure if there is a fix you may actually be bricked. Good thing is as your still s-on and the phone won't boot returning it under warranty should be easy, they won't know what you did to brick it.
Wait for someone else to confirm what I said first though.
If you had completed the process and had s-off before this happened then you could have fastboot flashed a new recovery and then a new rom.
Basically what happens sometimes is when attempting perma root (by either method, yes rage too!) your rom corrupts causing you to "boot loop". only benefit of rage is more often than not you will also be left s-off so you can save it.

The phone is under warranty untill 27 september 2011 but I'm not in US and the warranty is valid only in US.
I've throw away my money. I've used the phone only for one hour.
If someone have a phone with screen cracked or similar but with good mainbord please tell me.

oops... lol... that sucks... hope you figure it out and didnt brick a phone with not even an hours use...
wrong forum tho.

toggy said:
I try temp root my G2 with visonary and all works good. Then try to perm-root but when the phone reboot itself it freeze on htc logo.
I can get to hboot, fastboot and recovery (original ones) but the phone is post ota and S-ON.
So I try adb on recovery but tell me "device offline".
Then try factory reset but nothing new.
Then try to reflash the ota update from recovery, this work but after reboot no more than htc green logo.
Then try to flash original PC10img.zip but say "main version is older".
There is some solution?
Click to expand...
Click to collapse
why did you flash the OTA?there was no need to that is why you get the error message about main version is older. you should have tried that before the OTA if you wanted that to fix it but that is not solution.
warranty is 1 year world wide so again that is the only possible solution.
if you were stuck at that you should have asked for help before trying your own things if you are a "noob" to this.
what you can try is go into htc recovery and wipe data and leave your battery out after that for awhile then rename the ota you had used to update and rename that and reflash it. there are many root guides up there, typically use those.
and last but not lease please post in the correct sub forum
this is development.

You might be able to downgrade from the OTA by using a hex editor to fool the G2 into thinking the original is not older. The instructions are here:
http://forum.xda-developers.com/showthread.php?t=831398&highlight=downgrade+ota
I don't know if this will solve your problem, but I think it will.
Edit: I see your ADB is not working. You'll need that. It might just be that when you upgraded, the drivers are now the incorrect drivers. This has happened to me. Try downloading the SDK and getting all the drivers. A different one might work.

Is Possible to have shell in original recovery??

How is this the right thread? Q/A, maybe?
Sent from my HTC Vision using XDA App

1) Should've used rage.
2) Should've posted in Q&A.

Tried an RUU???

Related

Bricked Desire?! :(

Hey guys I'm really desperate right now...
I don't know what to to, I can't boot my Desire, I can't get into recovery, just fastboot is working. I'm always stuck on the splashscreen.
To begin with the story, I rooted my Desire months ago, flashed a new rom from time to time and everything worked fine. So yesterday I wanted to try out RCMix S CM7 where the FAQ said i need S-OFF.
So this also worked quite fine. But then I got problems partitioning my SDCard (dont know what why or so, my Desire didnt recognize it anymore)
Today I tried again but I made it even worse, now I can't boot my Rom anymore and I can't get into Recovery. So what should I do? I searched the internet for hours now and tried nearly everything.
I tried to flash an official RUU, in fact this one: RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Becaus the others were too "old". But when I tried starting this one it couldnt detect my desire. USB connecion error.
But still it seems it flashed a new hboot because now I am S-ON again.
Then I tried to flash a Stock ROM via fastboot, which first failed because it wasn't signed and the second one failed because android-info.txt and android-product.txt were missing.
I tried to flash the recovery again but it's still stuck on the splashcreen.
I don't know what to do anymore... could you PLS help me? Or is my Desire now bricked??
What can I do, or try...?
greets patrick
scroach said:
Hey guys I'm really desperate right now...
I don't know what to to, I can't boot my Desire, I can't get into recovery, just fastboot is working. I'm always stuck on the splashscreen.
To begin with the story, I rooted my Desire months ago, flashed a new rom from time to time and everything worked fine. So yesterday I wanted to try out RCMix S CM7 where the FAQ said i need S-OFF.
So this also worked quite fine. But then I got problems partitioning my SDCard (dont know what why or so, my Desire didnt recognize it anymore)
Today I tried again but I made it even worse, now I can't boot my Rom anymore and I can't get into Recovery. So what should I do? I searched the internet for hours now and tried nearly everything.
I tried to flash an official RUU, in fact this one: RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Becaus the others were too "old". But when I tried starting this one it couldnt detect my desire. USB connecion error.
But still it seems it flashed a new hboot because now I am S-ON again.
Then I tried to flash a Stock ROM via fastboot, which first failed because it wasn't signed and the second one failed because android-info.txt and android-product.txt were missing.
I tried to flash the recovery again but it's still stuck on the splashcreen.
I don't know what to do anymore... could you PLS help me? Or is my Desire now bricked??
What can I do, or try...?
greets patrick
Click to expand...
Click to collapse
If fastboot is working you should be pretty much safe. It seems like you got an usb brick. Try this thread: http://forum.xda-developers.com/showthread.php?t=691187
My Suggestion ... Create a Goldcard beofre doing anything.. once done you can put PB99IMG.zip into ur SD card and it will flash automatic once you goto fastboot... but Goldcard is a must for this.. if you dont knw search how to create goldcard.
For Goldcard
http://www.addictivetips.com/mobile...gold-card-for-htc-desire-without-hex-editing/
or
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
Pat, is your phone branded ?
Flash the correct RUU for your phone (one that came with your phone originally), it does not really matter how old it is. after you done that your should get back to stock you can re-root it and then load the firmware you want.
if you don't know what your phone came with originally. then you will need a goldcard to get back to stock
@paul.c: nope it isn't branded
@dennis.l: I can't! I tried some of this list: http://forum.xda-developers.com/showthread.php?t=695667
The old ones with 1.15 and 1.21 started, but didn't work because it said they are too old or something like that.
RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe
Then I tried the newer one with FroYo, but this one throw and error saying it can't even find or connect to my phone.
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
So what I've read so far I definitely need a goldcard right?
But all those manuals say I have to boot up and activate USB Debugging Mode... but I cant boot up a rom. The only thing that is working right now is fastboot.
Is it possible to make a goldcard without booting up? Or do I have to get a working Desire to make the goldcard?
I haven't got a cardreader either but seems I've got to get one.
Right now I'm not at home so can just try it in the evening.
scroach said:
@paul.c: nope it isn't branded
@dennis.l: I can't! I tried some of this list: http://forum.xda-developers.com/showthread.php?t=695667
The old ones with 1.15 and 1.21 started, but didn't work because it said they are too old or something like that.
RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe
Then I tried the newer one with FroYo, but this one throw and error saying it can't even find or connect to my phone.
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
So what I've read so far I definitely need a goldcard right?
But all those manuals say I have to boot up and activate USB Debugging Mode... but I cant boot up a rom. The only thing that is working right now is fastboot.
Is it possible to make a goldcard without booting up? Or do I have to get a working Desire to make the goldcard?
I haven't got a cardreader either but seems I've got to get one.
Right now I'm not at home so can just try it in the evening.
Click to expand...
Click to collapse
You don't need goldcard for unbranded phones.
Even Unbranded phone requires goldcard to be able to flash any RUU...
So I prefer you create goldcard.. and yehs you can create goldcard without booting..
If you have anyone with android mobile.. goto market and search for goldcard helper.. and insert you memory card in that phone.. and run the goldcard helper.. it will give you the reverse CID .. whcih you can use to create goldcard... but you will require a card reader for sure..... just try your luck with your current phone.. just plug in the phone and run the Goldcard tool.. and check if your phone is detecting
THANK YOU GUYS SO MUCH!!
You saved my life! xD
I made a goldcard as you said with the help of a friend and his desire. Then I put it my phone and suddenly I could flash the newest Stock ROM
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
So everything went great, I've got root again, a working stock rom and I'm able to start recovery mode again.
THANK YOU VERY MUCH!
paul.c said:
You don't need goldcard for unbranded phones.
Click to expand...
Click to collapse
I'm glad to hear that. Sorry, it seems that I have to learn more.
scroach said:
THANK YOU GUYS SO MUCH!!
You saved my life! xD
I made a goldcard as you said with the help of a friend and his desire. Then I put it my phone and suddenly I could flash the newest Stock ROM
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
So everything went great, I've got root again, a working stock rom and I'm able to start recovery mode again.
THANK YOU VERY MUCH!
Click to expand...
Click to collapse
Anytime Bro
I recently experienced a similar problem. And all the stuff you described wrong with your phone is the same on mine.
What I want to know is how to get back to stock and all that? A step by step guide would be very much apreciated..
I tried following this guide:http: //forum.xda-developers.com/showthread.php?t=691639
but as I try to enable my sdcard it get an error:
"The program can't start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem".
I recently installed the JDK and just downloaded the newest android SDK to work with.
Besides I'm considering whether I'm doing this right. I do have to use the CMDprompt right? and direct it to my androidsdk/tools directory?
I'm pretty much new to messing around with my phone through the CMD though. Please be gentle when you describe any methods that might work..?
Regards,
Me
Hammerbak said:
I recently experienced a similar problem. And all the stuff you described wrong with your phone is the same on mine.
What I want to know is how to get back to stock and all that? A step by step guide would be very much apreciated..
I tried following this guide:http: //forum.xda-developers.com/showthread.php?t=691639
but as I try to enable my sdcard it get an error:
"The program can't start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem".
I recently installed the JDK and just downloaded the newest android SDK to work with.
Besides I'm considering whether I'm doing this right. I do have to use the CMDprompt right? and direct it to my androidsdk/tools directory?
I'm pretty much new to messing around with my phone through the CMD though. Please be gentle when you describe any methods that might work..?
Regards,
Me
Click to expand...
Click to collapse
Adbwinapi.dll was moved to the platform-tools dir in the android sdk and the sdk path in Windows hasn't be updated. In win xp right click my computer, go to system then click the system variables button. Find "path" and change it to point in to the "platform-tools" folder... Note I'm not at my pc so I can't remember 100% what tab the system variables button is on
Sent from my HTC Desire using XDA Premium App
Hammerbak said:
I recently experienced a similar problem. And all the stuff you described wrong with your phone is the same on mine.
What I want to know is how to get back to stock and all that? A step by step guide would be very much apreciated..
I tried following this guide:http: //forum.xda-developers.com/showthread.php?t=691639
but as I try to enable my sdcard it get an error:
"The program can't start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem".
I recently installed the JDK and just downloaded the newest android SDK to work with.
Besides I'm considering whether I'm doing this right. I do have to use the CMDprompt right? and direct it to my androidsdk/tools directory?
I'm pretty much new to messing around with my phone through the CMD though. Please be gentle when you describe any methods that might work..?
Regards,
Me
Click to expand...
Click to collapse
Stumbled into the same problem. Just download it from the internet.
hi,
rage is right, better declare environnement variable, right click comupter - select properties - windows select advanced and you should see variable environnement. just add the path where adb is installed... mine is the following defaut path(C:\Program Files\Android\android-sdk-windows\tools) + (C:\Program Files\Android\android-sdk-windows\platform-tools) should add the in the user environ... name = path variable= the 2 path separated by a ;
Well I got desperate and I think that I've totally bricked my phone. I was going to a family arrangement and I didn't know the way so I was hoping that flashing the original RUU, would make me able to use the phone and the navigation in it, while starting the phone in fastboot would help. Seems it didn't. The RUU I tried to install seems it was a wrong one (here to say that I tried flashing it through the installer on my pc), but this was stated pretty late in the installation process.. where the guide told me to install a proper one.
My phone is now totally unresponsive. It won't even charge. When I hold the power button it just vibrates once and then nothing else happens.
Is it bricked? If so, does anyone know what my chances are with my warranty? Now that I've had it rooted and stuff, does my warrenty then expire and can they "track" the rooting part if I hand in it to their support?
Best of regards,
Me.
Hammerbak said:
Well I got desperate and I think that I've totally bricked my phone. I was going to a family arrangement and I didn't know the way so I was hoping that flashing the original RUU, would make me able to use the phone and the navigation in it, while starting the phone in fastboot would help. Seems it didn't. The RUU I tried to install seems it was a wrong one (here to say that I tried flashing it through the installer on my pc), but this was stated pretty late in the installation process.. where the guide told me to install a proper one.
My phone is now totally unresponsive. It won't even charge. When I hold the power button it just vibrates once and then nothing else happens.
Is it bricked? If so, does anyone know what my chances are with my warranty? Now that I've had it rooted and stuff, does my warrenty then expire and can they "track" the rooting part if I hand in it to their support?
Best of regards,
Me.
Click to expand...
Click to collapse
only guessing but if NOTHING turns on or boots, as in you just see a black screen then there is not going to be a way for any one to know the phone was rooted
try taking it back on warranty
I thought the same thing myself. Since it's unable to boot into the "recovery" menu by holding down "power + volume down" I guess it's not rooted anymore anyhow. During the RUU installation I noticed that it was installing a new "image-something" which I'm guessing means that it was writing over the root and recovery after which the installation failed.
Anyhow I'll try that and hope for the best. Thanks
Hammerbak said:
I thought the same thing myself. Since it's unable to boot into the "recovery" menu by holding down "power + volume down" I guess it's not rooted anymore anyhow. During the RUU installation I noticed that it was installing a new "image-something" which I'm guessing means that it was writing over the root and recovery after which the installation failed.
Anyhow I'll try that and hope for the best. Thanks
Click to expand...
Click to collapse
Are you able to recognise the phone in adb at all?
From what I know it's very rare to completely brick unless you are flashing hboots or radios.

[Q] Problem with Desire Z

Hi folks,
i´ve a problem with a Desire Z from a friend.
Every time when the phone boots, it stops at the HTC Logo.
I think it´s bricked
Is there any possible to flash the Rom (like Odin on Samsung Android Phones)
Thanks
If you power the phone off, then holding down the volume button, press the power button. Does the Hboot screen come up?
Also, you don't give a heck of a lot of info. Is the phone rooted, and/or S-Off? If not, then no, you can't flash a custom ROM.
But you may be able to flash the official ROM from Hboot.
the H Boot screen is this with "bootloader, reboot" and something with the 3 androids ?
when its that, i come into the hboot screen .. i did try the "factory reset" but it hangs on the 3 androids at the middle of the screen
EDIT: The Phone is not rooted, S-on stands there
but how can i flash a official ROM ?
i found one, but it recognize the phone
Since you are not rooted and S-On, you need to use the official ROM that matches your carrier ID (CID).
What ROM did you try?
If you want help, you need to supply as much information as possible. Not just "I tried a ROM".
Seeing as the phone is unrooted, it's unlikely that it's bricked from a user error.
At a guess, it's a Hardware issue, there's a thread here about it.
I had this same issue with my phone, it started freezing completely, and I had to do a battery pull to restart and it would just hang at the htc logo.
Seeing as you don't have clockwork mod though, you won't be able to see the Cache mounting errors, though you should be able to run the adb commands to find the name of your eMMC card if you have adb installed.
-Nipqer
redpoint73 said:
Since you are not rooted and S-On, you need to use the official ROM that matches your carrier ID (CID).
What ROM did you try?
If you want help, you need to supply as much information as possible. Not just "I tried a ROM".
Click to expand...
Click to collapse
okay, it´s a free phone without branding.
where can i read the CID !?
Nipqer said:
Seeing as the phone is unrooted, it's unlikely that it's bricked from a user error.
At a guess, it's a Hardware issue, there's a thread here about it.
I had this same issue with my phone, it started freezing completely, and I had to do a battery pull to restart and it would just hang at the htc logo.
Seeing as you don't have clockwork mod though, you won't be able to see the Cache mounting errors, though you should be able to run the adb commands to find the name of your eMMC card if you have adb installed.
-Nipqer
Click to expand...
Click to collapse
Where can i get adb mode ? the hboot or at the HTC LOGO !?
I have this problem too but i rooted and s-offed. What should i do now. Same things as him.
Nipqer said:
At a guess, it's a Hardware issue, there's a thread here about it.
Click to expand...
Click to collapse
Its possible, but also highly speculative. Damage to the ROM, or the ROM missing may also cause the same issue (stuck on boot splash).
bboy2000 said:
I have this problem too but i rooted and s-offed. What should i do now. Same things as him.
Click to expand...
Click to collapse
You're in (possibly) better shape then the OP. Try flashing any known good ROM from Hboot/recovery. Preferably a rooted ROM, if you want to stay rooted.
But its possible you may have something more going on than a bad ROM file, like mentioned in post #5 above.
i couldn´t find a tutorial how to flash the desire Z im H-Boot mode ?
can u give me a tutorial !?

[Q] RUU restore for warranty fails: error 140. Anyone can help?

Hi guys,
I own a Fastweb branded desire and back key isn't working anymore.
So I'm tring to restore the branded official rom for warranty.
I got s-off and root and my gold card is in.
I've flashed the old modaco r6 rom to avoid main version is older and flashed downgrade hboot(alpharev) too.
When I start the ruu hboot 0.75 and old radio are flashed properly, but I still have custom splash and cwm recovery also system is untouched.
Ruu stops with error 140 bootloader problem.
I'm still able to flash custom roms and I can s-off again, but I really don't know what to do.
Any help?
Thanks.
Best regards.
Jus
You're in the wrong section dude, read the rules.. all questions go to q&a section
This sections is set aside for development only
Sent from my HTC Desire using XDA App
Sorry mate, is there a way to change section?
jussy,
I had exactly the same problem so I'll answer even tho this is the wrong thread. You have to start first by extracting the zip file from the RUU. Run the RUU until it gets to the first screen then leave it there (don't close it).
Go to Start -> Run and type %temp%.
Find the temporary folder folder that's just been created (sort based on date) and find a file called 'rom.zip'. Copy this file into another location and close the RUU.
FreshNClean said:
jussy,
I had exactly the same problem so I'll answer even tho this is the wrong thread. You have to start first by extracting the zip file from the RUU. Run the RUU until it gets to the first screen then leave it there (don't close it).
Go to Start -> Run and type %temp%.
Find the temporary folder folder that's just been created (sort based on date) and find a file called 'rom.zip'. Copy this file into another location and close the RUU.
Click to expand...
Click to collapse
Thanks for replay.
I've extracted rom.zip and renamed to PB99IMG.zip. tried to flash it in fastboot.
Flash process start but stops before finishing leave me in the same situation as before. If I want to flash it again gives me main version is older.
I've s-off it 10 times today and made many try.
EDIT: I've also tried to flash via fastboot commander the .img files in rom.zip but after that I could only access fastboot.
Now I've flash a generic ruu to make it boot.
Tbh mate I'm not sure how to change it lol.. mayb delete and repost in q&a..
Just beware of flames coming your way lol
Sent from my HTC Desire using XDA App
jussy said:
Thanks for replay.
I've extracted rom.zip and renamed to PB99IMG.zip. tried to flash it in fastboot.
Flash process start but stops before finishing leave me in the same situation as before. If I want to flash it again gives me main version is older.
I've s-off it 10 times today and made many try.
EDIT: I've also tried to flash via fastboot commander the .img files in rom.zip but after that I could only access fastboot.
Now I've flash a generic ruu to make it boot.
Click to expand...
Click to collapse
Dude, don't flash the zip, just put it in the root of your SD, then switch phone off, hold vol down button and reboot into recovery, your phone will recognize the pb99img.zip and some options should come up. Follow the on screen instructions and you should be unrooted in 15 mins max.
Traced from a Reflex S Desire
3f1f37 said:
Dude, don't flash the zip, just put it in the root of your SD, then switch phone off, hold vol down button and reboot into recovery, your phone will recognize the pb99img.zip and some options should come up. Follow the on screen instructions and you should be unrooted in 15 mins max.
Traced from a Reflex S Desire
Click to expand...
Click to collapse
Sorry for my bad english but what you said is what I've done.
1-root and s-off.
2-flash downgrade hboot(alpharev).
3-put PB99IMG.zip (extract as said from my branded ruu) on sd card root.
4-boot power + vol down.
5-It starts, step 1 goes well then at the end of step 2 screen became black and came back with 0.75 hboot s-on and if I try again it gives me main version is older.
So I can only reboot, reflash a rom and s-off it again.
Never ending loop...
Thanks anyway.
You are using wrong RUU.use the RUU with 5.11.05.27 , I am on mobile so can't give you the exect link.I will post it tomorrow for you, if you can't find.
And it is better to create a goldcard if you havent yet
Sent from my HTC Desire using Tapatalk
jhonybravo4u said:
You are using wrong RUU.use the RUU with 5.11.05.27 , I am on mobile so can't give you the exect link.I will post it tomorrow for you, if you can't find.
And it is better to create a goldcard if you havent yet
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
I've got my gold card already in.
Sadly there's only one ruu for my carrier.
I can flash a generic froyo ruu but it's not good for warranty.
I can't really help in terms of your issue.
If I remember right, I booted into the bootloader and switched on fastboot, then ran the RUU EXE making sure my phone was connected to my pc.
It eventually came right.
Saying that, after I got the stock ROM back on, my phone went ape (and to this day I have no idea why). Random restarts. Freezing. It was crazy. I had to upgrade the RUU for it to stay on properly. Was really weird.
There are so many threads about rooting for warrantee purposes, perhaps search them or go through thier instructions, cause I'm sure someone may have had the same issue.
Wish I could help you though.
mr_norris said:
I can't really help in terms of your issue.
If I remember right, I booted into the bootloader and switched on fastboot, then ran the RUU EXE making sure my phone was connected to my pc.
It eventually came right.
Saying that, after I got the stock ROM back on, my phone went ape (and to this day I have no idea why). Random restarts. Freezing. It was crazy. I had to upgrade the RUU for it to stay on properly. Was really weird.
There are so many threads about rooting for warrantee purposes, perhaps search them or go through thier instructions, cause I'm sure someone may have had the same issue.
Wish I could help you though.
Click to expand...
Click to collapse
It seems you didn't got the problem.
Thanks anyway.
I did it!!!!
Thanks to this guide http://forum.xda-developers.com/showthread.php?t=821809
and all of you.
So many thanks.
Sorry guys I got an other problem...
Now this is the second time I bring it to assistence (last time was for vol down) and when they give it back to me it was updated to froyo.
I'm facing problem with 1.15=>1.21 OTA, installation is aborted due to status 7 (if some one can help I'll post the full error message).
Unfortunetly the ruu I've used is the only one from my carrier.
Will they know that my phone was updated by them and I'll lose my warranty?
Any idea about fixing status 7?
Many thanks.
Best regads,
Jussy

[Q] Rooting gone wrong?

Hi all
I have done a search to try and find the answer for this but I dont seem to be able to find a solution.
I am in the process of trying to flash my HTC Wildfire that I have just bought.
Now it came with S-OFF so i started by trying to use unrEVOked tool. This got so far but couldnt find the device root.
So following the guide
form.xda-developers.com/showthread.php?p=27139372
I trying to put it back to 2.1 instead of 2.2.1
This was successful HOWEVER, the touch screen doesnt work.
So in my attempt to try and fix this I am told to just flash it.
But I cant continue, I cannot get unrEVOked to find the device anymore.
I can tell the phone to do anything different as the screen doesnt work.
I have tried to recover it using a recovery image however it keeps failing and telling me "Remote not allowed"
I had turned on USB debugging but I fear the setting may have been removed when I put the other, older ROM on.
Anyone got any ideas what I can do?
heavy_metal_man said:
take the rom.zip out of the ruu by following this guide http://forum.xda-developers.com/attachment.php?attachmentid=486701&d=1294753279 , rename it pc49img.zip boot into bootloader and try flash it from there.
Click to expand...
Click to collapse
try this
Thank you, I will get an SD card and try this later
I followed this guide, However when it was in HBOOT when it was searching it did not load PB99IMG and it didnt look for a PB99IMG.
Also in HBOOT it says Touch Panel - Fail if this helps?
Edit again
I changed the name to PC49IMG.zip which seems to be what it looks for but this doesnt work either?
May be I should leave it to more experienced people here. I never had any issue when I rooted my phone. Cant help you more than this.
Sent from my HTC Wildfire using XDA
Try my guide, it's in my sig

[Q] Help needed with Desire Z

Hello,
I tried to help out a friend with rooting a Desire Z. He used the guide on http://forum.xda-developers.com/showthread.php?t=1178912. He was still on stock and everything and the guide pointed to that to do first.
According to him everything went fine untill he got at point "I - 4a) Manual Downgrade". After reviewing the files he had used it seemed to me that he had used the G2 version of PC10IMG.zip instead of the Desire Z version (could see it when inspecting how large the file was)
He told me that all other steps before (the temp rooting etc etc) was no problem. And after he rebooted his phone the install of PC10IMG started. After the first reboot however the phone stuck.
The situation now is a follows:
* phone does not boot. It gets stuck at the white screen with green HTC letters/logo and then does nothing
- S-ON
- Phone does boot into Hboot (version HBOOT-0.82.0000)
- RADIO-26.02.01.15_m2
- eMMC-boot
I can get into Fastboot and can send commands thru adb to the phone. However commands that try to flash result in a FAILED blabla signature. Probably since its S-ON status
SDcard is recognized (finally) and I managed to make it accept a stock rom. Many other .zips fail. System says no image or wrong image when searching for them.
I suspect the phone has a wrong bootloader (?) and will only accept G2 roms (wich would not be right since its a Desire Z (?)).
Things I tried so far:
* flash a stockrom: It did do something (saw the blue "loading" bar in the bootloader). After it's done it verifies and returns to the bootloader. The I reboot but it still hangs at white screen with green letters HTC/logo
* tried to flash other roms by putting then on the SD. Gives message no image or wrong image
* tried with adb with fastboot. Nothing is accepted.
Is this phone beyond DIY repairs? Advice or tips would be greatly appreciated (since this crap costed me already a full saturday and sunday)
Many thanks in advance!
(PS: I should have the basic knowledge about rooting, adb and such. Also I rooted my own desire Z succesfully already)
use THIS RUU directions will be there
now DOWNGRADE AGAIN which you already know
then follow either THE XDA WIKI or THE CYANOGEN WIKI or STRAWMETALS PDF GUIDE
demkantor said:
use THIS RUU directions will be there
now DOWNGRADE AGAIN which you already know
then follow either THE XDA WIKI or THE CYANOGEN WIKI or STRAWMETALS PDF GUIDE
Click to expand...
Click to collapse
Thanks a lot for your reply!
I tried what you suggested 3 times and this is the outcome:
The program starts up fine. Checks the phone with no errors. After a few install screens the phone reboots into a black screen with silver letters HTC (same as seen with adb/fastboot I think?). It starts wiping userdata. Then it says "busy sending"; goes all fine.
The it gets to the point sending "signature" (not sure if I translate correct. I have a dutch version or at least the install was in dutch).
And after a while I get:
ERRORCODE: 130 (model-ID error)
Get right updateapplication and retry
during install it said I had image version 1.00.000.0 and asked if want to update to 2.16.531.6
Anymore advice or sugestions I could try?
Thanks in advance for your answer!
[EDIT]
Seems I can go into some kind of recovery mode (choosing recovery from menu >> gives black screen with greenish icon >> gives red triangle
at that screen I do volume + and power and it gives me a menu in wich I can choose update from SD. Not sure if that can help me in any way? Maybe there is some .zip I can install and reset everything back to factory or something?
Tried already to select something there but gives an error:
(in yellow line) E: Can't mount /cache/recovery/command
Sounds serious tome
Then you'll need the ruu for your model phone, got to HTC.com, find support, look for desire z, then find downloads, follow same steps as before
Sent from my Nexus 7 using xda premium
demkantor said:
Then you'll need the ruu for your model phone, got to HTC.com, find support, look for desire z, then find downloads, follow same steps as before
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Tried quite a lot of RUU versions but everytime the same damn message:
ERRORCODE: 130 (model-ID error)
Get right updateapplication and retry
Tried to get unlocked bootloader with the tool from HTCdev but that gave me a message ERROR[191]: ROM not supported
Anything else I can try out? (going to try and see if I can get something of a rom thru a goldcard but my hopes dwindle by the minute
Thanks in advance for any help/advice
[EDIT]
After hours and hours of reading I can only think of 2 things myself:
1. somehow the emmc is defunct (broken or totally messed up beyond flashable)
2. it has a wrong radio version (= bricked beyond DIY repairs as far as I could read)
Therefor I descided to contact a company that can JTAG the phone and restore it to its glory. What is a reasonable price for such?
If anyone else has still some tips I'll keep watch of this thread
You can't use an older version of the software/firmware so you would need the latest from HTC, if the phone already has the latest installed then you would need a gold card to change the cid. Problem is, as far as I know, you need to at least a functioning adb access to make a gold card.
Being its hard to the version that you were running the state your phone is in, my guess you are at the latest ota, so if there was a ruu that came out for it that wasn't an ota then that will probably be the only one that works. Its a long shot, but you could call HTC (don't mention rooting just say you picked up the phone at it was like this) and ask for a link to the latest ruu so you can try and fix it, even if you're past warranty they should point you in the right direction
Sent from my Nexus 7 using xda premium
demkantor said:
You can't use an older version of the software/firmware so you would need the latest from HTC, if the phone already has the latest installed then you would need a gold card to change the cid. Problem is, as far as I know, you need to at least a functioning adb access to make a gold card.
Being its hard to the version that you were running the state your phone is in, my guess you are at the latest ota, so if there was a ruu that came out for it that wasn't an ota then that will probably be the only one that works. Its a long shot, but you could call HTC (don't mention rooting just say you picked up the phone at it was like this) and ask for a link to the latest ruu so you can try and fix it, even if you're past warranty they should point you in the right direction
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks a lot for your advice Demkantor
According to my friend he checked for OTA updates a few days ago (was his motivation in the first place to unroot and flash a custom since he was pissed that his great device didnt get much love anymore from updates and after seeing my Desire working on a custom hehe)
I checked out the RUU versions and also read that they kinda only work if it essentially updates the device (checked the site http://shipped-roms.com/index.php?category=android&model=Vision.
Tried a lot from there but only the WWE versions (CID of gsm was one of those numbers that indicated the gsm is unbranded)
For the sake of it I did make a goldcard and tried to use the extracted rom from an RUU. No luck. It sees it, sends it but fails at checking after that and returns to Hboot. Had a hope that the downgrade (step before perm root) was kinda succesful...
Gonna give it one last try with one of the none WWE versions with the lastest version number to see what it does.
I'll keep you posted!
PS: Damn I wished Gigabyte would make phones! I bet they'd put in some kind of recover rom in case the **** hits the fan hehe

Categories

Resources