Related
Hi All,
Apologies for my first post being a cry for help but im seriously screwed at the moment.
I have a UK t-Mobile Desire that came preinstalled with 2.1, and so the story of my rooting failure begins.
First of all i tried using Unrevoked 3.1 and apparently this worked, but i was no longer able to enter recovery mode at all.
Following this i tried applying the Amon Ra loader to my device. Once this was completed the phone was seemlingly working fine but i still could not get into recovery mode, it would jsut hang on the circular logo.
By now im pretty fedup with the whole thing and i decided to unroot my device using the unlocker video guide and the unmodified RUU from this site.
Now my device boots (i guess) but the screen no longer works, at all. All i want to do is restore my phone to its factory state so i can use it.
Can please anyone help a poor newbie out.
You haven't killed it, but you should have read this:
http://forum.xda-developers.com/showthread.php?t=749551
That includes a link to fix it, though it's not easy.
thanks for the response but according to the boot screen i had hboot 0.75
Your problem is SLCD. The bootloader is not relevant.
Sorry to be a complete numpty, but what process do i need to complete, there seem to be several options on that link.
thanks, i really appreciate any help
If you want to upgrade directly to Froyo just install this RUU (easy):
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
If you want to try to get Android 2.1 back then this thread (difficult):
http://forum.xda-developers.com/showthread.php?t=750852
I just tried the "easy" option and got the following error message from the Rom update utility.
ERROR[131]: CUSTOMER ID ERROR
The ROM Update Utility cannot update your android phone
Please get the correct ROM Update Utilility and try again.
You need a goldcard in the phone.
Ok, thanks for your help.
I will dissapear for an hour or two and see if i can get this fixed.
Eitherway many thanks for your help
Insert the goldcard, run the RUU, and it will be fixed.
when i try to create the goldcard i get an "error: device not found" message when running the adb ****** command
you create the gold card in your pc not the phone. i think
I am doing it on my pc, but it would seem that my pc cant "see" the desire. Im guessing that either USB debugging is off, or the phone is connected to the pc in anotehr "mode"
sigh
you make the goldcard on pc. then insert it into the phone
It must be that USB debugging is off. Does anyone know how to turn this on remotely or without seeing the screen?
Just use the goldcard you originally used with the RUU that broke your screen.
Or did you use a t-mobile branded RUU?
I dont have it
I used the tmobile branded one
When you flash an RUU you are restored to factory defaults, so usb debugging is off.
It is possible to enable usb debugging blindly if you read the other link I posted. It's difficult. Without a goldcard you cannot flash an SLCD-compatible RUU, which is the only way you can recover the phone. There aren't any branded RUUs available that support SLCD.
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.
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
Okay, so I've been searching for about a week; Google, XDA, forums, everything.
Backstory:
My friend found this wildfire at a bus stop, it had no Sim in it but an SD card (which he gave to a friend and has since been wiped).
I've unlocked and rooted a ZTE Skate (Orange Monte Carlo) for use with a GiffGaff Sim and Cyanogen. I'm quite computer Savvy and thought that I'd easily be able to do the same thing with this phone, with Google anything is possible!
Current Condition:
It's in the same state as when I got it, it doesn't have an OS. When you turn it on it just loops the 'HTC Quietly Brilliant' boot loop, holding power and Volume down boots it into a white screen with text (I think this is called HBOOT).
This is the information on this screen:
BUZZ PVT SHIP S-OFF
HBOOT-1.01.0001
MICROP-0622
TOUCH PANEL-ATMEL224_20aa
RADIO-3.35.20.10
Nov 17 2010,12:08:53
Click to expand...
Click to collapse
Plus options which I'm sure most of you are aware of.
When I select 'Recovery' it takes me to a picture of a phone with a large Exclamation mark (which is inside a triangle warning sign) over it. After a few moments I'm taken to the 'Android System Recovery' which I'm guessing is the stock recovery.
I've taken pictures of all these screens if anyone needs clarification and also of the back of the phone with the battery off (for the IMEI, etc).
What I've Tried:
I'll try make a list of everything I've tried here but I've tried a fair amount (nothing has actually effected the phone so it's still in it's original state).
Extracting the rom.zip from the RUU for the radio number of this phone and renamed it to update.zip. I then tried reading from update.zip from within 'Android System Recovery'. That didn't work, something about a signature not being valid.
Renaming the same rom.zip from 1. and renaming it to PC49IMG.zip/img so that the HBOOT screen could detect it but that was to no avail.
Running unrevoked(latest version) didn't work as the phone doesn't have an OS and every guide says to turn USB debugging on (which I can't do).
Running the RUU for this phone (which I judged from the RADIO version) didn't work either (it couldn't detect the phone).
Using ADB to push/flash recovery/boot/system and none of that has worked.
If I haven't provided some key piece of information then please let me know, I'd like to get this issue sorted as soon as possible!
Thanks in advance!
OK go to the development section and look for clockworkmod version 5.0.2.8 in pc49img format. Boot to bootloader with it on the root of the sdcard and Allow it to flash. Then flash rempuzzle or any other sense rom and your sorted pal
Sent from my HTC Sensation using xda premium
Thank you so much for the quick response!
I feel like this is getting somewhere now!
So I followed your advice and downloaded PC49IMG.zip from this post.
I copied it to the root of a clean 1GB SD card, booted the phone into Hboot which checks the connected SD card for a zip with that name, It comes up saying Loading PC49IMG.zip but then says 'No Image!'.
I know the SD card slot works and that the SD card works, am I doing anything wrong?
EDIT:
Just to keep the information on here up-to-date I've just posted in the thread I linked to earlier on in this post.
http://forum.xda-developers.com/showthread.php?t=1566677&page=4
When I try and flash recover it says:
sending 'recovery' (3324 KB)...
OKAY [ 0.962s]
writing 'recovery'///
FAILED (remote: note allowed)
finished. total time: 0.973s
Click to expand...
Click to collapse
I haven't tried removing the current recovery and putting cwm on with your alternative method because I'm scared that it won't let me write again and I'll just have no recovery and no hope for the phone!
Click to expand...
Click to collapse
This is what happened when I extracted recovery.img from PC49IMG.zip and tried to flash it over fastboot.
Please do not post Q&A in the general section.
Thread moved to Q&A
Sent from my Nocturnalized One XL using Forum Runner
E.Cadro said:
Please do not post Q&A in the general section.
Thread moved to Q&A
Sent from my Nocturnalized One XL using Forum Runner
Click to expand...
Click to collapse
Sorry mate, first post and all that. Thanks for putting it in the correct section.
DrCuddles said:
Sorry mate, first post and all that. Thanks for putting it in the correct section.
Click to expand...
Click to collapse
Fast boot will not work as that hboot does not have fastboot commands enabled pal. Give me 10 minutes to jump on the PC and I will help you out
edit: ok you definately need to use the pc49img method as your hboot does not have fastboot commands, the reason most people here can fastboot is the have revolutionary s-off, which added fastboot commands. i think either that phone came s-off or met with an xtc clip, hich has s-offed it and gave it sim unlock ect. so use the pc49img way of doing it, and keep the letters all caps, bar zip. like this PC49IMG.zip sometimes the bootloaders have a huff if its not worded right ;P
Sent from my HTC Sensation using xda premium
Thank you very much!!
DrCuddles said:
Thank you very much!!
Click to expand...
Click to collapse
did you get sorted pal? if you want i can help you find out for sure if the device was xtc clipped or not
No mate it's still as it was last night, see my previous post regarding me following your advice. That's where I'm at with the phone now
DrCuddles said:
No mate it's still as it was last night, see my previous post regarding me following your advice. That's where I'm at with the phone now
Click to expand...
Click to collapse
ok well if that fails, it could be a cid issue, but since your s-off should be easily sorted
Okay so what can you suggest for me to try next?
DrCuddles said:
Okay so what can you suggest for me to try next?
Click to expand...
Click to collapse
http://www.mediafire.com/?rxh0vn78a89123n
copy this to the root of the sdcard.
when it finds it it should say "jumping to diag", should give you 2 options, select diag. it should then come up with another 2 options of clean s58 data and device info. go down to device info first and look through it to check if the cid is 11111111.
if it is not copy it down.
then keep flicking through and it should bring you back to the clean s58data menu. clean the s58data. it should say readcid success and write cid success, or something along those lines. when it has finished reboot the device and leave it to see if it fully boots again.
this file is a leaked htc diagnostics utility, used with the xtc clip to s-off and give supercid and sim unlock. since you are s-0ff it will run and do its job, with the added bonus that it will hardcore factory reset the device wiping everything from it, hopefully fixing the bootloop in the process. if it does not then you will definately have supercid and be able to use any ruu you need to good luck and report back
I've cracked it!!!!
I was in the process of following the steps in your latest post. I was getting more frustrated because the diag file STILL wasn't being picked up by Hboot and I was at a loss.
I remembered I had an 8GB SD card not being used so I decided it was worth a try to repeat some of these steps with that in it. IT WORKED!
Hboot instantly picked up the diag utitility which makes me think that what was stopping me was that hboot doesn't like SD cards below 2GB (something I'd read about when unlocking my ZTE Skate).
So I restarted the phone with just the PC49IMG.zip on the sd card and low and behold it flashed CWM onto the recovery. Well. As anyone will tell you once you've got CWM on there then everything is nice and dandy! I flashed the latest CyanogenMod 7.2 nightly onto the phone, flashed the gapps and voila the phone is booting into CM7!!!
Thank you so much for your help in this heavy_metal_man, without you taking the time out to answer my questions I would have been lost!
Again, thank you so much. MY ISSUE IS RESOLVED!!!!
DrCuddles said:
I've cracked it!!!!
I was in the process of following the steps in your latest post. I was getting more frustrated because the diag file STILL wasn't being picked up by Hboot and I was at a loss.
I remembered I had an 8GB SD card not being used so I decided it was worth a try to repeat some of these steps with that in it. IT WORKED!
Hboot instantly picked up the diag utitility which makes me think that what was stopping me was that hboot doesn't like SD cards below 2GB (something I'd read about when unlocking my ZTE Skate).
So I restarted the phone with just the PC49IMG.zip on the sd card and low and behold it flashed CWM onto the recovery. Well. As anyone will tell you once you've got CWM on there then everything is nice and dandy! I flashed the latest CyanogenMod 7.2 nightly onto the phone, flashed the gapps and voila the phone is booting into CM7!!!
Thank you so much for your help in this heavy_metal_man, without you taking the time out to answer my questions I would have been lost!
Again, thank you so much. MY ISSUE IS RESOLVED!!!!
Click to expand...
Click to collapse
happy to hear you got sorted pal and thank you for keeping me updated
hi i was going through this post as i am facing a similar problem. my phone on pressing the power button would go to the htc screen and then switch off. i tried fastboot, pc49img and other methods and the result used to show success but my phone wouldn't boot. I tried using htc dev to s-on now my phone doesn't respond at all.
IN DESPERATE NEED OF HELP!!! :crying: :crying: :crying:
aksme707 said:
hi i was going through this post as i am facing a similar problem. my phone on pressing the power button would go to the htc screen and then switch off. i tried fastboot, pc49img and other methods and the result used to show success but my phone wouldn't boot. I tried using htc dev to s-on now my phone doesn't respond at all.
IN DESPERATE NEED OF HELP!!! :crying: :crying: :crying:
Click to expand...
Click to collapse
Can you be specific as to what's happening?
Tapped out from my sexy nexus 7
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