Hi, I recently upgraded phones and wanted to unroot my desire and return to stock so i could sell it on. I read up about it and it didn't seem to tough. I downloaded an RUU and i ran it through my phone in fast boot rather than HTC sync as my phone was running a none sense ROM. I ran it and it seemed to be working when at around 60% complete it flashed an error on my PC that it couldn't open a file and that i should download a complete RUU and try again. I have since tried several RUU's and every time its the same. Now when i turn on the device its got a fast boot screen but i cannot go any further, when i plug into the PC it goes black with error triangles in each corner.
I didnt downgrade the HBOOT first and it was using the sense one rather than stock, i guessed that this would be done through the RUU.
Any suggestions or help would be greatly appreciated.
Thanks
At what stage of the process do you receive an error? if you turn the phone on while unplugged from USB it should say FAIL by one of the categories. It is only bricked if the RADIO category says FAIL.
What hboot you are on now?
Did you downgrade to s-on?
What brand did phone had originally and what ruus have you tried?
Swyped from SGS2.
If your desire still reacts, it's not bricked. If your desire is bricked, it would not be nothing more than an expensive paperweight. So please change the thread title.
bortak said:
At what stage of the process do you receive an error? if you turn the phone on while unplugged from USB it should say FAIL by one of the categories. It is only bricked if the RADIO category says FAIL.
Click to expand...
Click to collapse
It doesn't say fail, when i turn it on its a black screen with HTC in the middle, in each corner there is a triangle with exclamation mark inside each triangle
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
kl_arnet said:
What hboot you are on now?
Did you downgrade to s-on?
What brand did phone had originally and what ruus have you tried?
Swyped from SGS2.
Click to expand...
Click to collapse
When i originally got the phone it was unbranded, HBOOT is Sense and i was still S-OFF when i tried the RUU.
Tried so far...
RUU_BRAVO_FROYO_HTC_WWE_2.10.405.2_R_RADIO_32.44.00.32U_5.09.05.30_2_RELEASE_142828
RUU_BRAVO_HTC_WWE_1.15.405.4_RADIO_32.30.00.28U_4.05.00.11_RELEASE_122704
RUU_BRAVO_HTC_WWE_1.21.405.2_RADIO_32.36.00.28U_4.06.00.02_2_RELEASE_126984
---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------
MatDrOiD said:
If your desire still reacts, it's not bricked. If your desire is bricked, it would not be nothing more than an expensive paperweight. So please change the thread title.
Click to expand...
Click to collapse
Wow your post was great, thanks.
If you cannot help, then maybe its best to not post anything at all
Wow your post was great, thanks.
If you cannot help, then maybe its best to not post anything at all
Click to expand...
Click to collapse
Instead of posting the same than the two others above me I decided to make clear that your desire is not bricked.
adamneilwilson said:
It doesn't say fail, when i turn it on its a black screen with HTC in the middle, in each corner there is a triangle with exclamation mark inside each triangle
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
When i originally got the phone it was unbranded, HBOOT is Sense and i was still S-OFF when i tried the RUU.
Tried so far...
RUU_BRAVO_FROYO_HTC_WWE_2.10.405.2_R_RADIO_32.44.00.32U_5.09.05.30_2_RELEASE_142828
RUU_BRAVO_HTC_WWE_1.15.405.4_RADIO_32.30.00.28U_4.05.00.11_RELEASE_122704
RUU_BRAVO_HTC_WWE_1.21.405.2_RADIO_32.36.00.28U_4.06.00.02_2_RELEASE_126984
---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------
Wow your post was great, thanks.
If you cannot help, then maybe its best to not post anything at all
Click to expand...
Click to collapse
unplug it from USB then turn it on, it should be in bootloader (RUU mode), and should say what failed.
MatDrOiD said:
Instead of posting the same than the two others above me I decided to make clear that your desire is not bricked.
Click to expand...
Click to collapse
It is if it's a radio fail
bortak said:
unplug it from USB then turn it on, it should be in bootloader (RUU mode), and should say what failed.
It is if it's a radio fail
Click to expand...
Click to collapse
Yeah its not plugged in when I do switch it on. Straight to the screen that I mentioned before
Sent from my GT-I9100 using xda premium
MatDrOiD said:
Instead of posting the same than the two others above me I decided to make clear that your desire is not bricked.
Click to expand...
Click to collapse
OK no problem, Thanks for that
Sent from my GT-I9100 using xda premium
bortak said:
It is if it's a radio fail
Click to expand...
Click to collapse
His phone reacts, which means: NO BRICK.
@adamneilwilson:
On the roms you listed/ tried there isn't the newest htc wwe ruu:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
MatDrOiD said:
His phone reacts, which means: NO BRICK.
@adamneilwilson:
On the roms you listed/ tried there isn't the newest htc wwe ruu:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Click to expand...
Click to collapse
OK i'm downloading now and i'll give it a try, Thank you
---------- Post added at 10:58 PM ---------- Previous post was at 10:20 PM ----------
I'm getting a USB error now so not even getting chance to try it out, its the same for the other RUU's too so its not a bad download.
If when i start my phone and plug it into a USB when i unplug it goes to a bootloader screen and says
Alpharev Sense
Bravo PVT 1 SHIP S-OFF
HBOOT-6.93 1002
MI CROP-031D
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aud 10 2010, 17:52:18
RUU
I cannot open anything and pressing any button does not do anything, when i plug back in it goes back to the black screen
To avoid the usb connection error, flash the ruu directly via the PB99IMG.zip method:
http://forum.xda-developers.com/showpost.php?p=10509780&postcount=102
@MatDrOiD - I'm pretty sure you're 99% correct in MOST cases, however this sounds like a RADIO brick.. and AFAIK the only fix is a motherboard replacement.. YES, the phone DOES turn on and responds, however from my experience it is not fixable.
bortak said:
@MatDrOiD - I'm pretty sure you're 99% correct in MOST cases, however this sounds like a RADIO brick.. and AFAIK the only fix is a motherboard replacement.. YES, the phone DOES turn on and responds, however from my experience it is not fixable.
Click to expand...
Click to collapse
thanks for clarifying... I guess the only thing to do now is to wait for google to announce ice cream sandwich and then wait for devices that will support it and buy one.... been fun with desire, at least I still have it as an mp3 player
I'd suggest you to try use PB99IMG.zip method, too...
To do that, first download the zip version of the RUU file for your phone, you should be able to find it if you do a search. After this, put the zip file to your SDCard's root folder (directly into it) and name it PB99IMG.zip.
After this, plug SDcard back to phone, turn on your phone while holding Volume Down button. HBOOT screen will come, read the zip file and ask you if you want to flash. Press Volume Up to accept and it shall flash itself.
If this one fails either, I'd recommend you to do S-OFF first, and then try again. Maybe you can have more chance with S-OFF HBOOT..
So what DOES your desire actually do atm?
BigMrB said:
So what DOES your desire actually do atm?
Click to expand...
Click to collapse
it boots, acts normal. does NOT recognize PC when connected, nor is it recognized the other way around.it drops service as soon as the screen is locked or goes dark (like when you pick up the phone or lock the screen normally). I can't flash radio or S-off, as I am still S-on and usb doesn't work. I tried PB99IMG.zip two or three times, either it does not update when using 2.2 RUU or it does reflash 2.3 RUU, but doesn't fix anything... I tried temproot with rageagainstthecage (doesn't work) and zysploit (doesn't work). I can access the phone via USB when in fastboot via fastboot and adb recognizes the phone only when connected through wi-fi. I don't know if there is anything I can do to make it work. I do not require the USB to work, even if it would be nice, I just need the phone not to drop service and drop calls every time the screen is off...
wait... your phone boots????????? If I missed you saying that then I'm sorry x1000000 it isn't bricked..
in that case it's not bricked.. have you tried the USB brick fix?
and to fix your service you could try:
in the dialpad dial *#*#4636#*#*, phone information, and play around with the preferred network types. It's a deep-sleep issue solver, so could possibly work for you too.
EDIT: oooooooooooooooooooooooh I know why I thought it was a radio brick, there's a post similar to yours, and just got confused
bortak said:
EDIT: oooooooooooooooooooooooh I know why I thought it was a radio brick, there's a post similar to yours, and just got confused
Click to expand...
Click to collapse
Easily done
Do you know how to use fastboot?
Related
I have happily had a htc desire z for just over a year. On Tuesday i bought the 'humble bundle' android apps.
I downloaded one of the apps. Cogs. Once i installed it my screen went black and didn't do anything. So after 15 minutes. I reluctantly removed and replaced my battery. From then on my phone wont get passed the htc boot screen. From then on I only assumed i have an expensive paperweight which was bricked one way or another.
It can however access the 'hboot menu' (if thats the correct term?);
When the menu loads it checks for some zip files, its too fast too make out what they are though. The menu info is as follows if it helps;
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011, 23:36:27
Options:
FASTBOOT - Takes me to another menu. Doesn't seem useful as far as i can see.
RECOVERY - It brings up the phone with the green arrow for 2 seconds then buzzes 3 times in succession and then shuts the screen off. Is that what it should do?
FACTORY RESET - This option looks like what id need, however when i select it the phone just freezes.
SIMLOCK/IMAGE CRC - From what ive read theyre not really any use.
Would anyone be able to suggest a port of call in order to recover this lifeless paperweight please?!
Any help is greatly appreciated.
Craig
wuptdo said:
RECOVERY - It brings up the phone with the green arrow for 2 seconds then buzzes 3 times in succession and then shuts the screen off. Is that what it should do?
FACTORY RESET - This option looks like what id need, however when i select it the phone just freezes.
Click to expand...
Click to collapse
Recovery should bring you to your recovery menu. What i mean is that it should start ClockworkMod or 4Ext depending on which one you've installed.
As far as i know those 2 options would allow you to get your phone back to life. I'm afraid that you're screwed without it. But my knowledge about that kind of stuff is pretty basic so maybe someone on this forum has a solution.
Good luck !!!
TenMaKo said:
Recovery should bring you to your recovery menu. What i mean is that it should start ClockworkMod or 4Ext depending on which one you've installed.
Click to expand...
Click to collapse
Sounds like the phone is still stock, so in that case it would be neither of those, and the stock Recovery.
Which brings up the valid question: this phone is stock and unrooted?
Factory reset should do the trick. If not, you might need to find the appropriate RUU file for your phone version (region, carrier) and run that on your computer with the phone connected via USB. What version of the Desire Z do you have (Canada, Euro, Asia, etc.)?
Fastboot is a special tool used with your phone connected by USB to your computer. The Fastboot menu in Hboot simply turns this feature on or off. You don't need to mess with it, unless specifically instructed to.
Unfortunately the phone is still completely stock. Didn't really fancy dabbing in rooting until the warranty ran out, which ironically is now.
The phone is not carrier locked (i.e. it's sim free).
I live in the UK, however i purchased it through a weird net site, it came with alternative languages like THAI pre-installed which suggests its an Asian import. With no option for European languages, except English of course.
Thanks for the swift replies, i'll have a quick read into RUU's, and what they actually are though. But if with the extra info you can further point me in the right direction it'd be great!
thanks
craig
EDIT: Just been rooting around on this site
shipped-roms(dot)com/index.php?category=android&model=Vision
Theres 2 RUUs there with the same radio number.
RUU_Vision_Gingerbread_S_hTC_Asia_TW_2.42.709.10_Radio_12.56.60.25_26.10.04.03_M_release_201045_signed.exe
(does the TW mean anything?)
and
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
would these be what i'm after?
The stock/shipped RUUs can be downloaded from here:
http://shipped-roms.com/index.php?category=android&model=Vision
The question is which one. You can try the Asian RUU. I'm not certain what would happen if you try to run the wrong RUU. I think (not sure) that it will just fail and give an error message for wrong version.
---------- Post added at 05:32 PM ---------- Previous post was at 05:28 PM ----------
wuptdo said:
EDIT: Just been rooting around on this site
shipped-roms(dot)com/index.php?category=android&model=Vision
Theres 2 RUUs there with the same radio number.
RUU_Vision_Gingerbread_S_hTC_Asia_TW_2.42.709.10_Radio_12.56.60.25_26.10.04.03_M_release_201045_signed.exe
(does the TW mean anything?)
and
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
would these be what i'm after?
Click to expand...
Click to collapse
Woops, cross posted as you were editing your post. WWE is world wide English. I'm guessing TW is Taiwan. Again, not sure which one you want.
Thanks again.
Right once i decipher which RUU is the correct one.
How do i need to connect my phone. Do i need to be just in the hboot menu, or ?
thanks in advance. you're a lifesaver. well.....phone saver. hopefully
wuptdo said:
How do i need to connect my phone. Do i need to be just in the hboot menu, or ?
Click to expand...
Click to collapse
Couldn't remember and had to look that one up. Put your phone into fastboot mode in order to run the RUU.
Right. I gave the WWE version a run. It was able to scan my current firmware and said it was using build 2.42.707.3 there isn't an RUU for this.
Would you think it would load the WWE fine, or result in a worse off brick?
WWE BUILD = 2.42.405.2
ASIA_TW BUILD = 2.42.709.10
would it be worth requesting an ruu for the specific build direct from htc do you think or would i be wasting my time.
Sorry for the tireless questions. I really do thank you for your effort.
Wait, what message are you getting again? It won't allow you to flash because it's the same version?
I would try the version that's on your device. I take that's the ASIA_TW RUU?
However.
What your issue would be with flashing an RUU, is the fact the phone does a version check. Now if the version is higher or equal to the one already installed, it will refuse to flash (not sure on equal, that's why you might have a chance if you flash the RUU that corresponds to your version).
So, the only way you can go around the version check is make the phone think that it's a lower version. You have to do this by editing the "misc" partition. This partition holds information such as version number, and others unique to your phone. The misc partition is edit-able, but editing it is largely accomplished by having access to the Android OS, which apparently isn't the case here. You'll only be able to accomplish this by editing the misc partition using a Jtag, and this is sub-optimal solution, to say the least.
wuptdo said:
Would you think it would load the WWE fine, or result in a worse off brick?
Click to expand...
Click to collapse
As crestofawave mentions, if it fails the version check, it SHOULD just refuse to flash the ROM. But I've heard of cases where a wrong RUU is run (or partially run?), causing the phone to be stuck in recovery. But I don't think that would put you in any worse situation than you are now. As the solution for that particular problem is flashing the correct RUU.
I don't THINK there is anything worse than that, that will happen from flashing the wrong RUU. But I personally don't know enough to answer that for certain. And I would hate to be wrong. But if I were a betting man, I'd just try to flash one of the RUU's and see what happens.
Since the WWE RUU is a lower version number than what is currently installed, I don't think you have a choice, but to run the ASIA_TW one.
The other option is to try to make a goldcard from an SD card. This will allow you to run any RUU.
---------- Post added at 02:42 PM ---------- Previous post was at 02:39 PM ----------
crestofawave said:
Wait, what message are you getting again? It won't allow you to flash because it's the same version?
Click to expand...
Click to collapse
He hasn't tried running an RUU yet.
---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------
crestofawave said:
I would try the version that's on your device. I take that's the ASIA_TW RUU?
Click to expand...
Click to collapse
He can't figure out version/region his phone is (and I haven't been able to either, just by Googling around). That's the main problem right now.
---------- Post added at 02:47 PM ---------- Previous post was at 02:43 PM ----------
crestofawave said:
What your issue would be with flashing an RUU, is the fact the phone does a version check. Now if the version is higher or equal to the one already installed, it will refuse to flash (not sure on equal, that's why you might have a chance if you flash the RUU that corresponds to your version).
Click to expand...
Click to collapse
Pretty sure you mean if the versions number (you are trying to flash) is lower than the one already installed, it will fail. Equal version should pass the check, as running the RUU is a common means of recovering an existing ROM.
---------- Post added at 02:56 PM ---------- Previous post was at 02:47 PM ----------
wuptdo said:
Right. I gave the WWE version a run. It was able to scan my current firmware and said it was using build 2.42.707.3 there isn't an RUU for this.
Click to expand...
Click to collapse
I ran a search for that version number on this forum, and got this thread:
http://forum.xda-developers.com/showthread.php?t=1434137&highlight=2+42+707+3
The download link seems to work, but at your own risk. Sketchy Chinese download site posted by a member with only 3 posts . . . is a bit sketchy.
In theory this should be the right ROM file (pass version check). Rename to PC10IMG.zip and put on your SD card. Then flash from recovery.
@redpoint73 Thanks for pointing some things out. I was somewhat busy at the time so I didn't have the time to assess the situation as well as I'd like. So, flashing an RUU of the same version does work, huh? Good to know.
So, I also looked up the version number and I found that the same file had been mentioned in some other sites, in one of which I found the same person posting it, and he's a moderator, too. Well, I don't think it helps in terms of trustworthiness, but then again, it sounds like this is your best shot.
Good luck though!
Right. With both the WWE and ASIA_TW editions it runs the RUU, all the way up too the update button. However once i click it. The RUU shows the loading bar with text saying 'rebooting to bootloader' but it just gets stuck here. The phone just hangs on the fastboot menu and doesnt let me do anything until i remove the battery again.
I'm gonna try work out how to download the other one from this rather Chinese site. If that doesn't work....
One last solution. Try extracting the exes to get the firmware. Shove it on the memory stick and load it through recovery?
cheers for the link to that firmware btw.
wuptdo said:
One last solution. Try extracting the exes to get the firmware. Shove it on the memory stick and load it through recovery?
Click to expand...
Click to collapse
I think the same thing will happen in recovery, that the extracted .zip files will fail in region and/or version number check. This is pretty much what "S-On" on your Hboot screen signifies (in addition to write protecting the Hboot, radio, and other things).
One thing you can try, is to turn an SD card into a Gold Card. Gold card will let you then flash any ROM, regardless of region or version number.
This (though a bit dated) is the best guide I know of for making a gold card:
http://forum.xda-developers.com/showthread.php?t=835777
With a gold card, you should be able to flash any RUU. The WWE ROM on the same thread is a good start point, as its the unbranded HTC ROM that was shipped when the phone was initially released (Euro version).
I've personally never had to make a gold card, I just know about the process. For some reason, it doesn't always work from posts I've read in the past. So its not a silver bullet. But for the lack of the right RUU for your phone version, it may be your best bet at this time.
Slowly downloading from that Chinese site at a whopping 10KB/s whilst having a read about gold cards. Can i make a gold card in any android phone and use a gold card in any android phone?
wuptdo said:
Can i make a gold card in any android phone and use a gold card in any android phone?
Click to expand...
Click to collapse
Really don't know. But the "easy guide" to make a gold card is from the HTC Hero forum on Modaco, so it seems there is some standardization, at least among HTC devices. The various manufacturers have very different write protections, so I'm guessing this is just an HTC thing.
apparently you can
apparently you can use any goldcard with any phone, well according to the second post on this thread anywho.
http://androidforums.com/legend-support-troubleshooting/197860-how-do-i-use-goldcard.html
now to find a willing volunteer in uni halls so shouldnt be tooooo hard to find one of these nifty new phones lying round.
Well it passes all the checks and gives me the option to install the firmware with that chinese one so im gonna give it a go once my batteries fully charged!
If it works i'll upload that link to a UK/US host so it doesn't take people in a similar situation 6 hours to download 250 Mb!
EDIT: If it works. Would it be worth rooting/S-off in order to make recovering my phone easier in the future?
Rooting your phone can only lead to benefits. You can flash Custom ROM's (You can go with Stock rooted ones if you just want to use the phone. Having root really makes the difference, there's a lot more freedom.)
To answer your question though, what is meant by "rooting" here is basically unlocking the phone. It allows us for complete control of pretty much every aspect on this phone..
Now, typically, when you "root" the phone you also get what we call a "recovery". Essentially, recovery is a utility that will allow you to control the phone's OS, essentially to install/remove or backup it, as well as other handy features. Think of it as a fail-safe toolbox, isolated from the rest of the android system. So, in many cases, it will "recover" your phone, in case of an issue. This really depends on the incident though, a recovery can't "fix" a broken eMMC chip. Don't worry though, chances of breaking your phone are very little if you do everything right.
Also, in addition to that, whilst rooting (when using the XDA Wiki Guide), you eventually get the option to flash the ENGineering HBOOT. What ENG HBOOT allows you to do is make use of the "fastboot" bridge. With it, you can perform a multitude of tasks, just like in recovery. The only difference is that fastboot is on the lower levels of the phone's building blocks, HBOOT. That means that in the case you can't run the recovery for whatever reason you could flash a new one using fastboot. It's quite useful but it is overlooked as it is considered a dangerous process, while it really isn't, if you're careful. Same goes for the rest of the rooting guide which you can find here, if you feel comfortable enough to root, that is! You don't necessarily have to flash the ENG HBOOT, so if you don't feel comfortable about it you can ignore it.
Best of luck.
Thanks for the info!
BUUT. That method failed miserably. I choose to update. The screen just sits there on updating for the first module (bootloader) and doesnt do anything.
I remove the battery and restarted a bit scared to do so. But it didnt even touch the bootloader in the 15 minutes i waited........so I have a feeling something has physically broken on the thing.
Bummer...Whether it's a soft or hard brick...we're handicapped in terms of options, considering that we have limited access. You can try running it again, and leave it for more time. Probably not going to do any better but until (and if) we can come up with something else, I don't see another option.
Hi everybody. Have desire z and faced with a problem. Just want to install virtuos on it when understood that its impossible. Device is UNLOCKED, S-ON, and thats it.
Device also with stock australian OS. Version which has hole for root is 1.32, I could downgrade device only till 1.85, because this is the earliest version of australian android for Desire z. I have no possibilities for another os installation. It says that code is wrong bla-bla-bla...
Guys, could you please help me... I want to install virtuos...
kiruxa9212 said:
Hi everybody. Have desire z and faced with a problem. Just want to install virtuos on it when understood that its impossible. Device is UNLOCKED, S-ON, and thats it.
Device also with stock australian OS. Version which has hole for root is 1.32, I could downgrade device only till 1.85, because this is the earliest version of australian android for Desire z. I have no possibilities for another os installation. It says that code is wrong bla-bla-bla...
Guys, could you please help me... I want to install virtuos...
Click to expand...
Click to collapse
it doesnt really matter where the 1.32 version is from... as you are not going to use it?
Just follow this guide here
If its complaining about CID incorrect, it just means you need a goldcard, which that guide goes through.
-Nipqer
This should get you started off on the right foot. Worked on my uk bought htc dz
HTTP://forum.xda-developers.com/showthread.php?t=1178912
Sent from my HTC Desire Z using XDA
---------- Post added at 10:07 AM ---------- Previous post was at 09:47 AM ----------
There's a CyanogenMod wiki called HTC Desire Z: Rooting. It does help figure out the rooting process in a simple manner. I know there's an excellent post on XDA but I can't find it. Google it.
And follow the process to the T and don't miss out on anything. You're gonna be fine.
On a personal note, I've tried Virtuous Unity and found it to be ridiculously slow and memory-hungry. Otherwise it's quite Sense-ible. I personally can't stand a slow phone. I'm using MIUI 2.3.23 right now from MIUI Andriod. Loving every minute and not missing Sense in the least.
Heh, guys. Didnt work.
After this step "adb reboot bootloader" in manual downgrading, the phone could boot in boot loader and started scaning for images. But after scan it said that image is missing or image is wrong! I dont know what to do... Did all of steps twice...
When tried to downgrade with fastboot, screen shows gray HTC and the phone hanged.
did you make a gold card?
also are you on gingerbread?
Yes I did.
After running this script:
# ./flashgc
There was message that my flash card is a goldcard now. Successful.
Yes, I have GB 2.3.3
kiruxa9212 said:
Yes I did.
After running this script:
# ./flashgc
There was message that my flash card is a goldcard now. Successful.
Yes, I have GB 2.3.3
Click to expand...
Click to collapse
i mainly followed this guide
http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Rooting
http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Firmware_Downgrade_(Gingerbread)
i had a problem when i tried to create a gold card using a different method as some cards just dont work... when i tried a different card it worked perfectly
my phone comes up with all those image errors still, i think its quite normal
Well, I will try the first link. The second one is absent. Also will try another flash-card. Hope it helps
kiruxa9212 said:
Well, I will try the first link. The second one is absent. Also will try another flash-card. Hope it helps
Click to expand...
Click to collapse
there is a link to the second link on the first page under exploitable firmware
looks like my post was edited for some reason ?
s..t happens again.
No results. The same... Tried downgrade from the link pointed above before rooting the phone.
and had the same "No image or image is wrong"
Change flash card, made goldcard on it too.
I was able to get temp root, but when Im loading into bootloader "..image is wrong ...bla-bla..."
Used two different flash cards for goldcard procedure and in the end of it had the same results. It didnt help. What to do.
What type of card do you use?
I can make video with all things I do to show you that everything I do is strongly by wiki.
kiruxa9212 said:
s..t happens again.
No results. The same... Tried downgrade from the link pointed above before rooting the phone.
and had the same "No image or image is wrong"
Change flash card, made goldcard on it too.
I was able to get temp root, but when Im loading into bootloader "..image is wrong ...bla-bla..."
Used two different flash cards for goldcard procedure and in the end of it had the same results. It didnt help. What to do.
What type of card do you use?
I can make video with all things I do to show you that everything I do is strongly by wiki.
Click to expand...
Click to collapse
it sounds like bootloader isnt picking up the PC10IMG on your sd card.... the CID incorrect error comes after this...
after its failed have you checked to see if the PC10IMG has transferred to your sd?
also just to check after you adb reboot bootloader in 7 you are then selecting bootloader?
Yes, the image is on sdcard, I checked.
Of course, after rebooting into bootloader I m selecting bootloader.
After that Im just waiting for searching. After few seconds of waiting the image loading starts.
SD Checking...
Loading image.....PC10DIAG.zip
No Image!
Loading....PC10DIAG.nbh
No image or wrong image!
Loading image....[PC10IMG.zip]
No image or wrong image!
either a bad download of of what ever ruu your using or your goldcard didnt work. try another method of making a gold card or using a different sd card (fat32)
also redownload the ruu that you need and put this one on your card
In my first post I mentioned that i have australian stock rom whish has 1.85 as earliest version of rom, not 1.34. I already tried to downgrade to 1.85, it works, but grant root is not possible here.
Try to reformat my flash card again...
demkantor said:
either a bad download of of what ever ruu your using or your goldcard didnt work. try another method of making a gold card or using a different sd card (fat32)
also redownload the ruu that you need and put this one on your card
Click to expand...
Click to collapse
its not getting to the goldcard stage... it should find the PC10IMG.zip & then ask if you want to upgrade after you choose yes it then checks & either continues or gives you a CID error
i had a good check the other day when i was rooting my second one...
maybe some screenshots of the terminal & the platform-tools folder would help just to check everything is where it should be
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
kiruxa9212 said:
In my first post I mentioned that i have australian stock rom whish has 1.85 as earliest version of rom, not 1.34. I already tried to downgrade to 1.85, it works, but grant root is not possible here.
Try to reformat my flash card again...
Click to expand...
Click to collapse
you need to use the 1.34 rom
PNuT. said:
you need to use the 1.34 rom
Click to expand...
Click to collapse
Yes, I know, but there is no such version of this CID It's only 1.85
Here are, screenshots and output from cmd
kiruxa9212 said:
Yes, I know, but there is no such version of this CID It's only 1.85
Here are, screenshots and output from cmd
Click to expand...
Click to collapse
neither of my phones have shown the unlocked thing at the top of your screen... whats that?
---------- Post added at 06:06 PM ---------- Previous post was at 05:35 PM ----------
PNuT. said:
neither of my phones have shown the unlocked thing at the top of your screen... whats that?
Click to expand...
Click to collapse
htcdev bootloader unlocked?
http://forum.xda-developers.com/showthread.php?t=1453066&highlight=rooting+after+bootloader+unlock
PNuT. said:
neither of my phones have shown the unlocked thing at the top of your screen... whats that?
Click to expand...
Click to collapse
UNLOCK - this is an official unlock of device bootloader from HTCdev.com site. As they say, this is an opportunity to install custom roms, but indeed i cant see any difference between locked (state by default) or unlocked.
kiruxa9212 said:
UNLOCK - this is an official unlock of device bootloader from HTCdev.com site. As they say, this is an opportunity to install custom roms, but indeed i cant see any difference between locked (state by default) or unlocked.
Click to expand...
Click to collapse
i think thats your problem... check my previous post edit... i think you need to relock it
Hi, in my impatience to get JB, I knackered things up. I forgot to put the boot img onto my sd card, ran the flasher tool detailed at the start of the big JB update / OTA thread in the general forum and now have a phone with the following:
HBOOT 1.36 / stuck on the splash screen / no access to the sdcard / is/was completely stock & unbranded. The screen I arrive at when pressing the volume don on reboot tells me in highlighted pink at the top of the one ith the three skateboarding robots that it is
***LOCKED***
ENDEAVOURU PVT SHIP S-ON
Booting into recovery gives me 3 or 4 seconds with the green arrow, a reboot and then the HTC one x beats audio splash screen.
Is it going to have to go back to HTC or can someone help me avoid that please?
Sorry for cross posts, I'm trying to get into the right place but am desperate to get this thing back and functioning.
THANKYOU - in advance for any help.
A desperate noob.
Are you sure it says locked or re locked?
Sent from my HTC One X using xda app-developers app
tomascus said:
Are you sure it says locked or re locked?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hi Tomascus! A helpful voice in the wilderness, thank you... Most definitely is states *** LOCKED ***. It was never rooted or faffed about with prior to me doing whatever I just did to it this morning. Do you think it can be sorted without going back to HTC?
Think you need to put the Boot.img in the same file as your JBflasher tool (where you put the unlock code from HTC) you cannot flash the boot.img from your SD card.
Did you make a backup? What recovery do you have?
---------- Post added at 02:02 PM ---------- Previous post was at 01:57 PM ----------
Firstly you will need to register your phone on HTC Dev
Next you will need to get the Unlock_token.bin file from the email you are sent and put it in the JB firmware flasher tool
Next you will need to put the Boot.img in the same file as above
If you can boot your phone into fastboot by pressing on the power button for 10 secs and then holding volume before it reboots you should be good to go,
try what you did again after doing the steps above and then you will be unlocked, with CWM recovery installed. The boot.img of your chosen custom rom will be installed,
then you can mount the phone via usb in recovery, put your rom on there and flash it, it should boot
---------- Post added at 02:11 PM ---------- Previous post was at 02:02 PM ----------
Also have a read of this
http://forum.xda-developers.com/showthread.php?t=1843585
Read through it, the bit you need to do via HTC Dev is below:
Unlock the Bootloader:-
Did you install HTC Sync at the start? As now you're going to need it!
Navigate your web browser to www.htcdev.com/bootloader and click register at the top, complete the registration process, making sure that you use an email address that you have access to.
Once registered make your way back to www.htcdev.com/bootloader and sign-in.
Once signed-in at the supported devices drop down select 'All Other Supported Models' and click on Begin Unlock Bootloader.
Now before we move onto anything else we're going to want the Fastboot Files, which Cursed4Eva is kindly hosting here: Fastboot Files
Once downloaded, on your PC go to the folder C:\Android and inside that folder create a new folder called fastboot, so you'll have
C:\Android\fastboot
Now the fastboot files that I linked to earlier come in a Zip file, unzip it to C:\Android\fastboot, this makes it easier to find it in CMD.
Now back @ htcdev, you've registered and signed in? Good, you've chosen All Other Supported Models and clicked Begin Unlock Bootloader, it'll ask you if you wish to continue, click yes, then the Legal Terms will pop up, just click that you acknowledge both terms and continue with 'Proceed to Unlock Instructions'.
Now click through the instructions until Step 8, ignore everything else.
Now turn off your HOX, now we'll turn on the HOX into the Bootloader, so press and hold down the Volume Down Button and whilst pressing the Power Button, continue to hold this down, the phone may vibrate and bleep a bit but continue to hold it down until you are greeted with a screen that has some options on it, Fastboot, Recovery etc... Now the touch screen wont work so we navigate using the volume buttons & Power Button, press down on the Power Button wile you have Fastboot selected, you'll enter Fastboot Mode with the options HBoot, Reboot, Reboot Bootloader & Power Down. You'll see above these options it'll have Fastboot written and highlighted in Red, leave the phone as it is, just plug it into the PC via USB and that highlighted 'Fastboot' will become 'Fastboot USB'.
Now open CMD, enter
cd \Android\fastboot
This will access the fastboot folder in your C:
Now in CMD once you're in the fastboot folder enter this command:
fastboot oem get_identifier_token
Now it'll bring up the Identifier Token. (see Image)
Now using your mouse, right click in CMD where it says
<<<< Identifier Token Start >>>>
Highlight it to where it says
<<<<< Identifier Token End >>>>>
Now on your keyboard, once you've highlighted the Identifier Token press 'Ctrl + C' to copy the Identifier Token.
Now back at the HTC Dev website, scroll down to after Step 10, where it says My Device Identifier Token:, Click in that field and either press Ctrl + V or right click and paste your Identifier Token into that field.
Now Click Submit.
You'll now be taken to a page where you'll be informed to check your emails.
Open up your emails and you'll have an email from HTC and in that email will be an attachment, this will be called Unlock_code.bin.
Click to expand...
Click to collapse
Hi and thanks again, I received my unlock token, have tried huge amounts of different things and still can't seem to get this thing working. With regards to which recovery did I have etc, I'm afraid I have no idea as the thing was stock, unbranded, never been rooted or anything. Horrible feeling it's back to HTC for this one... Cheers again though, really appreciate your help and efforts.
smudgelab said:
Hi and thanks again, I received my unlock token, have tried huge amounts of different things and still can't seem to get this thing working. With regards to which recovery did I have etc, I'm afraid I have no idea as the thing was stock, unbranded, never been rooted or anything. Horrible feeling it's back to HTC for this one... Cheers again though, really appreciate your help and efforts.
Click to expand...
Click to collapse
You are using Stuart0001's JB flasher tool?
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
exocetdj said:
You are using Stuart0001's JB flasher tool?
Click to expand...
Click to collapse
Also have you set up the fastboot file on your PC?
OK, I've somehow managed to unlook my bootloader using the HTC tool so assume this is a good thing? Anyone tell me what to do now please?
That is exactly what you wanted to do
have you got a command prompt open which is linked to your fastboot folder?
Bear with me mate i'm at work but can help
You will need to flash the attached file through fastboot commands (make sure the attached file is in your fastboot folder):
use the command
fastboot flash recovery c:\fastboot\CWMrecovery.img
You will need to replace the bit in bold above with the path to your fastboot folder if any different to mine
Hi again, I can't thank you enough for this, I've somehow managed to relock the thing now... I simply tried to re-run the flasher tool, got distracted and ended up re-locked. Arrrgh!
smudgelab said:
Hi again, I can't thank you enough for this, I've somehow managed to relock the thing now... I simply tried to re-run the flasher tool, got distracted and ended up re-locked. Arrrgh!
Click to expand...
Click to collapse
Lol nightmare!!! (concentrate lol!!! )
Can you confirm that under where it says relocked on the fastboot screen it says HBOOT 1.36?
You will need to run the flasher again (send anyone who distracts you packing lol) make sure there's a file called
recovery-clockwork-touch-5.8.4.0-endeavoru.img
in the JBFW flasher
Have you downloaded a custom rom? if so which one?
Hi, cheers for your patience, yes indeed 1.36.0000 / S-ON.
smudgelab said:
Hi, cheers for your patience, yes indeed 1.36.0000 / S-ON.
Click to expand...
Click to collapse
Have you downloaded a custom rom to use?
No mate, I haven't. Wouldn't know where to look to be honest, as I mentioned, I was just trying to keep this as stock as possible! I have CID HTC__001. All UK, unbranded if this helps...
Hi, no I haven't, this is as stock as they come, unbranded - all of that... I wouldn't know which one to use or even where to look!
smudgelab said:
No mate, I haven't. Wouldn't know where to look to be honest, as I mentioned, I was just trying to keep this as stock as possible! I have CID HTC__001. All UK, unbranded if this helps...
Click to expand...
Click to collapse
Right ok! gotcha,
it looks like you have updated your firmware without picking a custom JB rom lol! the JBFW tool was meant for anyone who wanted to install a custom rom!
You have two options,
1, Install custom recovery and custom rom or
2, Run the JB RUU which will install stock JB on your phone, This should work as you have the correct HBOOT, you can find the link here;
http://www.filefactory.com/f/7cc7b2fbdd03c031/
You will need to find the file below:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radi o_5.1204.162.29_release_298897_signed.exe
Basically you run it on your PC with the phone connected via usb and it does everything for you, You will need to connect your phone in fastboot mode (as you cant boot normally) and run the exe file, let it do its thing and your phone should boot
I am not 100% sure if is will work as I have always updated via RUU when the phone is connected booted normally, not in fastboot but it should do, if not your best bet is route 1. I will be leaving work in 15 mins, I will link you up later on Gtalk if you wish
---------- Post added at 04:49 PM ---------- Previous post was at 04:33 PM ----------
Also check your PM dude
Hi again, ok, joined premium the file factory thing as the dl is over 500mb! Just tried running it all and now the battery's at less than 30% so it won't touch it! I've plugged it in and will try again in a minute. Not overly confident as initially I was getting the messages about how A the laptop couldn't identify the last device connected and then the RUU program said the same... Will have to try later. Thanks again, I may try the gtalk route later of you're about . Gonna walk the dog and see if I can calm down now... I've asked HTC for a return envelop which will arrive tomorrow so will give it all a bit of a go tonight and then call it quits! Thanks once more for everything.
This ruu is also on htcruu.com if i'm not mistaken !
http://www.htcruu.com/Endeavor/RUU_...Radio_5.1204.162.29_release_298897_signed.exe
:thumbup:
ow and keep the bootloader RE-LOCKED its a must to run a ruu !
smudgelab said:
Hi again, ok, joined premium the file factory thing as the dl is over 500mb! Just tried running it all and now the battery's at less than 30% so it won't touch it! I've plugged it in and will try again in a minute. Not overly confident as initially I was getting the messages about how A the laptop couldn't identify the last device connected and then the RUU program said the same... Will have to try later. Thanks again, I may try the gtalk route later of you're about . Gonna walk the dog and see if I can calm down now... I've asked HTC for a return envelop which will arrive tomorrow so will give it all a bit of a go tonight and then call it quits! Thanks once more for everything.
Click to expand...
Click to collapse
Ok Il be on there from half 6ish
MarcelHofs said:
This ruu is also on htcruu.com if i'm not mistaken !
http://www.htcruu.com/Endeavor/RUU_...Radio_5.1204.162.29_release_298897_signed.exe
Thanks Marcel, will bear that in mind
:thumbup:
ow and keep the bootloader RE-LOCKED its a must to run a ruu !
Click to expand...
Click to collapse
---------- Post added at 05:47 PM ---------- Previous post was at 05:34 PM ----------
smudgelab said:
Hi again, ok, joined premium the file factory thing as the dl is over 500mb! Just tried running it all and now the battery's at less than 30% so it won't touch it! I've plugged it in and will try again in a minute. Not overly confident as initially I was getting the messages about how A the laptop couldn't identify the last device connected and then the RUU program said the same... Will have to try later. Thanks again, I may try the gtalk route later of you're about . Gonna walk the dog and see if I can calm down now... I've asked HTC for a return envelop which will arrive tomorrow so will give it all a bit of a go tonight and then call it quits! Thanks once more for everything.
Click to expand...
Click to collapse
Also is a good thing that the ruu seems to recognize the phone in fast boot u may be in business just make sure u have a bit more charge and relocked bootloader
Thanks to exocet1983 on here (and cheers to marcelhofs for looking in to ) I am now sorted, fixed, basking in the glory that is JB and the world has tilted back to it's normal axis. Thanks again for staying the ramblings of the uninitiated, very, very grateful.
Hi Dudes,
I have a big problem. I'm newby and I was tryin' to root and install custom jelly time on desire hd which has froyo 2.2. So I f*cked up the phone i think. Can somebody help me ressuret it? This is what I've done:
1. USB Debugging
2.Fastboot
Then I reboot the phone and I chose Factory reset - well to this step all was fine..
I downloaded some ADB driver which were not what I was really need ot the device manager showed MY HTC instead of ADB... an so on.
Then I downloaded the AAHK tool. And following the steps I install some file in zip through hboot menu. BUT I wasn't read that I have to have my phone S-OFF. So I install some things from AAHK, and while it was in process of installing it shows up device error, so i unplugged the cable, and in the hboot menu tried to make factory reset again. BUT this time when i done this, I was unable to connect my device again in the shell I deleted some "gold card" in which is CID. Then I was trying to recover this gold card by some other tool, but it doesn't read the CID was empty. So I have now S-ON bootloader, and can only switch my phone in the hboot menu. I was trying some RUU but the radio was different and i'm desperate now. Is there any way to recover my rom somehow, and to try the process again, I can switch it in fastbootusb but when i try AAHK it reboots the phone and fadeout the display. Can you please PM or whatever to get my phone back. I'll need step by step guide. I reisntalled my OS, because of some malware from all the hacks I tryied so I'm with clean system now and please recommend me the right ADB. Thanks in advance!
@tupacalypce
You can try and restore the your device via this method.
Boot into fastboot bootloader and confirm via fastboot devices to insure your device is there.
Now type in fastboot oem rebootRUU this should then place your phone into a black screen with a silver HTC logo.
Now go and hunt for you stock firmware (If you tell me what provider you had i might be able to help in this respect). Once the firmware is downloaded run the .exe file to start the flashing it should then flash you back to stock everything. After this boot back into fastboot and factory reset the device it should then boot.
Your best bet is to flash 3.20 ruu for HTC inspire. And pray
Op has soled the issue via my help via pm but your reply was valid.
Although that ruu wouldnt work due to cid being HTC__J15 .
What one did u use then?
@marknoll I ended up using the PD98IMG-GB5.zip file on this forum as that was the only image that had the CID matching and a higher Misc Version to that on the phone.
Good job hack
Sent from my ATRIX HD using Tapatalk
---------- Post added at 02:07 AM ---------- Previous post was at 02:06 AM ----------
I was gonna suggest that next. Lol. Thanks dude
Sent from my ATRIX HD using Tapatalk
Just helping out the community after all I still have 2 Desire HD's LOL still booting and both stocked. But just a note for you. Its always best to as for a fastboot getvar all that way you can match the CID up and make sure the Misc Version is lower then that of the RUU. Other then that @marknoll your logic was sound.
I asked for a get var. Thanks.
Sent from my ATRIX HD using Tapatalk
---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------
See? http://forum.xda-developers.com/showthread.php?t=3004469
Sent from my ATRIX HD using Tapatalk
It was a suggestion for this thread, how ever reading that thread you did very well to help that user as well. It was nothing personal though.
I know. Lol.
Sent from my ATRIX HD using Tapatalk
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
How did he acquire that cid? That is crazy
Sent from my ATRIX HD using Tapatalk
Problem solved. The phone is back and It's working Great. Thanks to hacktrix2006 Many many Thanks again mate.
Sent from my HTC One X+ using Tapatalk 2
My problem is weird , I am not a noob , On XDA Since long time but this time im stunned what's wrong after the OTA update phone keep rebooting goes to red triangle screen stays and reboots All ok , All i need is Fastboot then i can fix in 2mints , But when i try to go to bootloader it stays there for 2seconds before i select anything it restarts I am not able to select Fastboot and when i select fastboot in hurry then after going to fastboot it restarts , im Locked Bootloader was fully stocked , All i need is bootloader or Fastboot , Or a option to flash rom ... Can anyone help?
BUMP
did you tried
power off device
press Volume down and Power?
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
did you tried to download the RUU file for your device and flashed it over your PC?
wiQbold said:
did you tried
power off device
press Volume down and Power?
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
did you tried to download the RUU file for your device and flashed it over your PC?
Click to expand...
Click to collapse
I am not able to go to the bootloader for more than 2seconds how do i flash anything ? its not staying in the bootloader menu and i m not able to go to fastboot option either
only the ruu section! they are exe Files that do for you the flash process..
http://forum.xda-developers.com/showthread.php?t=2701376
BUT YOU HAVE TO KNOW which is the right for you if you don t want to tell which firmware you have
wiQbold said:
only the ruu section! they are exe Files that do for you the flash process..
http://forum.xda-developers.com/showthread.php?t=2701376
BUT YOU HAVE TO KNOW which is the right for you if you don t want to tell which firmware you have
Click to expand...
Click to collapse
RUU needs fastboot ? I can get into fastboot or bootloader option
ok, then i can t help. good luck
No one can solve this problem if anyone can I WILL SALUTE
battery is charged?
wiQbold said:
battery is charged?
Click to expand...
Click to collapse
76% and i charged it again t0 100%
This is a tough one. As you know, it keeps trying to install the update file (before you can pick any bootloader options), causing it to reboot. The only way to stop this would be to delete the file, but you have no way of doing that, if its constantly rebooting to bootloader with no fastboot access (and no OS).
Is the bootloader currently unlocked, locked or relocked?
S-on or s-off?
wiQbold said:
only the ruu section! they are exe Files that do for you the flash process..
http://forum.xda-developers.com/showthread.php?t=2701376
BUT YOU HAVE TO KNOW which is the right for you if you don t want to tell which firmware you have
Click to expand...
Click to collapse
-----------
Hello dear all,
I have a problem with my cellphone i think you can help me or give an advice how to repair it. Let me tell you a little what happened, after the last update my cell phone only loads Android Recovery through that screen i can move on to bootloader. HTC Sync is not able to detect my cell phone connected to my PC through USB port.
I am newbie into this world of cell phones but i have knowledge of computers, i hope you can give any suggestion or guidance.
thank you
did you know what your firmware is, or was? did nothing happen in DeviceManager in Windows? a unknown device or something?