Develop Bugs

Rooting issues...HELP!

OK, I also have a Moto Droid, and its MUCH easier to root those phones. But now I have a Evo 4G as well, and want to root it for what its worth.
Problem:
I follow Toasts guide to rooting (part 1) (sorry, cant post links yet)
I follow the steps exactly. Copy over the PC36IMG.zip file to the SD card, and boot into HBOOT. It scans the file like it should, then says "Main Version is older!, Update Fail!"
I cant get past this point no matter what I try.
HBOOT-0.79.0000
I have ADB set up and everything recognizes everything else just fine, but this is where I am getting stuck. Any ideas?

I think post #2 in toasts thread has new links to uncorrupted files. The pc36 zip should be 172mb on your had.
Sent from my PC36100 using XDA App

chevycam94 said:
OK, I also have a Moto Droid, and its MUCH easier to root those phones. But now I have a Evo 4G as well, and want to root it for what its worth.
Problem:
I follow Toasts guide to rooting (part 1) (sorry, cant post links yet)
I follow the steps exactly. Copy over the PC36IMG.zip file to the SD card, and boot into HBOOT. It scans the file like it should, then says "Main Version is older!, Update Fail!"
I cant get past this point no matter what I try.
HBOOT-0.79.0000
I have ADB set up and everything recognizes everything else just fine, but this is where I am getting stuck. Any ideas?
Click to expand...
Click to collapse
Dont think this is the right place for this, but it sounds like you have the newer software on your phone and need to follow the 1.47 rooting method.

Yeah, I have the new 1.47 software. I followed 3 different rooting methods that say they work with the new OTA release, which is what I have.

Belongs in Q&A.
You have the 1.47 update, so toasts method won't work, do some looking around before posting.

You have the newer bootloader, so you must use the newer root method.
http://forum.xda-developers.com/showthread.php?t=718889
Or you can try Simpleroot:
http://forum.xda-developers.com/showthread.php?t=720565

Sirchuk said:
Belongs in Q&A.
You have the 1.47 update, so toasts method won't work, do some looking around before posting.
Click to expand...
Click to collapse
I have done LOTS of looking around, searching posts, multiple sites, and I finally had to post about it. I spend more time on droidforums, so its a little different.

Step 4 of the SimpleRoot app, doesnt seem to work. It says Starting Part2, but never does anything. Does that part usually say that, or should it be doing something?

Phone Will Not Root - PC36IMG problem?

I installed the PC36IMG on the root of my SD card...now when I go into the updating, it says, "Main Version is Older! Update Fail! Do you want to reboot the device? Yes or No"
Why is this happening? Do I need an updated version of some sort??
I have tried rooting this phone using 4 different guides...both versions of the 3 Click method (regular and OTA edition), then some YouTube videos...direct from the author of the 3 Click Method guide. I get the same message every single time.
What am I doing wrong? What is going on? Please help. Thanks in advance!

Perhaps you should properly read and follow this thread:
http://forum.xda-developers.com/showthread.php?t=690762
and this one: http://forum.xda-developers.com/showthread.php?t=701835
They should give you all the info you need step by step to rooting your phone.
Or you can use this as well when you are ready: http://forum.xda-developers.com/showthread.php?t=715915

Thread moved to Q&A.

Badious said:
Perhaps you should properly read and follow this thread:
http://forum.xda-developers.com/showthread.php?t=690762
and this one: http://forum.xda-developers.com/showthread.php?t=701835
They should give you all the info you need step by step to rooting your phone.
Or you can use this as well when you are ready: http://forum.xda-developers.com/showthread.php?t=715915
Click to expand...
Click to collapse
This is essentially the same guide that I used for the other 4 or 5 guides I tried. None of these is working. It will not recognize the file on my SD card.

nbakid2000 said:
This is essentially the same guide that I used for the other 4 or 5 guides I tried. None of these is working. It will not recognize the file on my SD card.
Click to expand...
Click to collapse
Those instructions for rooting will only work if your running pre 1.47 software. Based on the error your mentioning your most likely on version 1.47. The easiest way to root if your on this software version can be found here: hxxp://forum.xda-developers.com/showthread.php?t=720565
replace xx with tt, I still cant post links.

I used that Simple Root as well, which takes you back a software version. You have to find another ROM if you want to be on 1.47... I initially used this one just to get on 1.47, but there are many other better options out there.
http://forum.xda-developers.com/showthread.php?t=715915&highlight=stock+root

also take note of this:
Note: This process will only work if you already have the engineering HBOOT. (If you have NAND unlocked, you already have it and can proceed confidently.) If you'd like to check the actual version, you can boot into HBOOT and look near the top of the screen: it should say HBOOT-0.76.2000, not 0.79.0000. If you have 0.79.0000, you will need to do Toast's Part 2 first before starting here.

I had the same problem. I had 1.47 and tried everything I could. Used Simpleroot OTA on Windows XP with no luck. Everything went smoothly until step 4, when I got the same error. Went home and used Simpleroot on my Win 7 machine and worked like a charm. It seems the problem was simply that I was using XP, although I have a bevy of cellular drivers that could have been interfering as well.
Try going to the link below on a Windows 7 machine and follow the instructions carefully. Make sure you have .net 4 and HTC sync installed beforehand. Both are linked in the forum post.
forum_xda-developers_com/showthread_php?t=720565
(replace _ with .) Sorry, apparently I can't post links yet.

Unfortunately I don't have a Windows 7 machine.
I only have XP and Vista. The OTA Simple Root says, "Not Allowed Access / Denied Permission" or something when it tries to write to the card in the very first step.
This sucks.

[Q] Official Update Not Working

Hey guys, I should have posted this about a month (maybe even longer) ago, but I've been dealing with some health issues and couldn't be bothered. First off I have a rooted phone (with S-OFF) but I like keeping the stock sense build. I upgraded OTA to 2.2 some time ago, then there was an OTA update a few months after that (which I was able to install without any problems after I replaced a couple of files that had gotten modified), now this newer OTA update refuses to install.
It tells me it needs to reboot to start installing so I click the button to reboot and it counts down, but it never reboots. Is it somehow detecting that my phone is rooted? I would like to have the most up to date OTA update installed on my phone at all times so any help or ideas would be great (also I'm sorry if this has been covered before, I did search but I've been afk for a bit so I might have missed some things).
- DeeBG

Read this thread, it tells you how to get back to 2.2 stock, then download the latest Unrevoked to root again and obtain s-off...

RMarkwald said:
Read this thread, it tells you how to get back to 2.2 stock, then download the latest Unrevoked to root again and obtain s-off...
Click to expand...
Click to collapse
Blah I have to go back to 2.2 stock? Oh well, it's not the worse thing in the world (I already had to do it once) and those are great instructions (plus I've wanted to have the latest version of Clockworkmod installed for a while and using Unrevoked means I won't have to mess with the payload/su/etc files). Thanks!

I also thought of something (kind of late though). I was using a custom kernel, which might have been the issue too. But I went ahead and re-enabled S-On, however now for some reason my phone is checking for errors on my SD card (no idea how long it will take, or why it's doing that), but does anyone have a link for that 17.7mb file of the 3.26.605.1 update? I found the full RUU, but it's huge and I rather just upgrade than possibly wipe everything out (and I don't know when my phone will have the OTA ready again). Thanks for any help!

Is it necessary to update or downgrade then upgrade the OS?
sent from my Ultimate 2.33 Incredible

bigsapz said:
Is it necessary to update or downgrade then upgrade the OS?
sent from my Ultimate 2.33 Incredible
Click to expand...
Click to collapse
That seems to be what that linked thread says, but I don't believe that is correct (that's why I am looking for that 17.7mb OTA file). I was able to install the first 2.2 update (aka 2.2.1) without issue after I restored some files that were altered (either by rooting or installing the wireless tether app that's hosted on Google Code). However this OTA update (aka 2.2.2) isn't popping up again for me to install, so I am going to see if I can extract just the upgrade data from the official RUU. I have to wait until later tonight because I need my phone to be operational for another few hours but I'll post back with results (and files if need be =).

Yeah I tried the RUU update and as expected it did a total wipe... bringing back system via nandroid and will try something else.
Edit: http://forum.xda-developers.com/showthread.php?t=969973 <= using Jay's thread, which is much like the post that was first given to me in this thread. Not re-enabling S-ON seems to be the problem... lesson learned, don't try shortcuts unless you know what you are doing (and I've been afk from the "Dinc Scene" too long for that =p.
Edit 2: Up to date and 100% working!

[Q] Downgrade from 1.84.666.2

I stupidly updated my Bell Desire Z to 1.84.666.2 the other day. Looking for a way to downgrade to a version that can be rooted.
Found this thread, but it's for a previous update.
http://forum.xda-developers.com/showthread.php?t=905261
Love this phone but I really want to dump Bell's extra software and Sense.
Please, any helpful input is appreciated!

How far through that guide did you get, what error message? I did 1.84 -> 1.34 to get S-OFF & root.

Following the tutorial got me temp root access but was unable to boot the firmware. I suppose I need to make a goldcard but that tutorial has a few broken links. Anyone want to give me a resource that explains what is going on in that tutorial a little more deeply? I remember reading in a previous forum that 1.8 update could be rolled back.
I'm on a Bell DZ too...
[J]

You will need a goldcard if you don't already have SuperCID via gfree, and you can't find an earlier ROM/RUU that matches your CID.
Sent from my HTC Vision using XDA Premium App

I'm getting stuck at step 11. I get to the white bootloader screen and without doing anything the phone does and SD check, looks for PC10DIAG.zip, etc, then finds PC10IMG.zip and checks it. Then I get bumped out to the bootloader list of FASTBOOT, RECOVERY, FACTORY RESET, SIMLOCK and IMAGE CRC.
It's unclear what to do from there. The tutorial says I'll get a prompt to update and restart, but I don't.
Also, the tutorial says I'll need a goldcard (which I created) but no where in the tutorial does it say what to do with it...
I got a goldcard using Gold Card Tool. Just do a google search of "easy goldcard".

I've managed to iron out that issue. I had made a mistake when making the goldcard.
Problem now is that when I get to step 11 the phone says "Model ID incorrect!" then "Update Fail!".
Any ideas?

Where are you getting your PC10IMG from?

From the guide I linked earlier. (http://forum.xda-developers.com/showthread.php?t=905261)
I downloaded the full RUU and renamed the extracted rom.zip.

I had goldcard issues (broken links) so I got the rom that matched my current region. I then did the temp root, modded the version info and let the phone try the update. Once I got it all sorted it worked as is said in the guide. I don't know if the goldcard tool worked or not, I think not as I wanted to change the Asian phone to WWE but had to go down to Asian 1.34 then go S-OFF and then go WWE. Maybe an extra step but it worked.

How do I find a rom that matches my current region?
The desire z was purchased from Bell Mobility in Canada and is now being used on Rogers.

This thread may be of help to you: http://forum.xda-developers.com/showthread.php?t=1029821

Thanks for that link! I basically did as the guy said and used the link to the 1.34.666.1 rom you linked in that thread. Only difference was I uploaded it to the SD and the issued the command adb reboot bootloader. This time no errors and the update worked!
So now I guess I just go ahead with a normal root of a 1.34.666.1 DZ?
Weird thing is the guy in that other thread said he got S-Off from doing this update... On my phone it's still S-On.

All you have done is put a rom on the phone that allows S-OFF, I can't see anyway you could get it in a stock rom?!

DVDWSN said:
Thanks for that link! I basically did as the guy said and used the link to the 1.34.666.1 rom you linked in that thread. Only difference was I uploaded it to the SD and the issued the command adb reboot bootloader. This time no errors and the update worked!
So now I guess I just go ahead with a normal root of a 1.34.666.1 DZ?
Weird thing is the guy in that other thread said he got S-Off from doing this update... On my phone it's still S-On.
Click to expand...
Click to collapse
You should now be able to follow this guide to get S-OFF (as above, I don't see how flashing a stock ROM would do this automatically): http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision

So after downgrading I had S-ON. But I just finished the rest of the rooting process in the guide I linked in my original post and got root!
What a process. That must have taken 12 hours or more. I should really post a new guide with more complete info.
Thanks for the help guys!

Now that I have root and S-Off downgrading from 1.84.666.2 to 1.34.666.1 using the processes DVDWSN did. Now I thought I could go back to 1.84.666.2 using OTA like I upgraded the first time. But when I try to do OTA, I get the message I do not have any new version. What gives?

If you are trying to downgrade do not touch OTA updates lol. Anyways, what you want to do is temp root your phone so you can 'spoof' the radio version the an old one thereby allowing you to flash a radio that can be manipulated. If you aren't sure what to do then try following this guide.

[Q] Bootloader - Bypassed when trying to flash Stock Image

Hi all, I followed Prototype7's method for gaining root and S-OFF via Tacoroot. I then proceeded to install Revolutionary with the CWM recovery.
I am now trying to go back to stock following CondemnedSoul's method, but whenever the PG32IMG.zip update installs, it skips [3] Bootloader and says "Bypassed". It also says "Bypassed" for [7] TP.
The update will say "Complete...", I can boot the phone once and use it normally, but every subsequent attempt to reboot the phone results in boot loops!
What am I doing wrong? Is there some way to flash the bootloader separately? Does my SD card need to be reformatted? Thanks in advance...

swenpro said:
Hi all, I followed Prototype7's method for gaining root and S-OFF via Tacoroot. I then proceeded to install Revolutionary with the CWM recovery.
I am now trying to go back to stock following CondemnedSoul's method, but whenever the PG32IMG.zip update installs, it skips [3] Bootloader and says "Bypassed". It also says "Bypassed" for [7] TP.
The update will say "Complete...", I can boot the phone once and use it normally, but every subsequent attempt to reboot the phone results in boot loops!
What am I doing wrong? Is there some way to flash the bootloader separately? Does my SD card need to be reformatted? Thanks in advance...
Click to expand...
Click to collapse
Did you flash a new radio? Can you tell us what radio you are on (settings > about phone > baseband version).

I did nothing more than the instructions given in the links I posted. To gain root via the tacoroot method I had to flash the 1.09.01.0312_vivow_Radio_PG32IMG.zip after flashing the initial RUU. But note that my radio and everything else, except the bootloader, was successfully updated using the stock image provided by CondemnedSoul.

swenpro said:
I did nothing more than the instructions given in the links I posted. To gain root via the tacoroot method I had to flash the 1.09.01.0312_vivow_Radio_PG32IMG.zip after flashing the initial RUU. But note that my radio and everything else, except the bootloader, was successfully updated using the stock image provided by CondemnedSoul.
Click to expand...
Click to collapse
I didn't use tacoroot (I rooted before it was needed), so I'm not 100% familiar with it. You'll probably have to wait for someone more familiar with it. I was just suggesting something that I've read about other users doing that tripped them up. Good luck with it, you shouldn't have to wait long for someone more helpful to come along.

Thanks for your effort.
Anyone able to help me on this?

Not sure what the [7] is, but the bootloader gets bypassed by Revolutionary's custom hboot so it can't be overwritten by an RUU or OTA, which is why you don't lose S-OFF unless you manually overwrite the hboot partition.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:49 AM ---------- Previous post was at 07:43 AM ----------
As for your issue, reflash the .0312 (or .0320, that's the one from the ICS leak) radio, the one from CS's image isn't an upgrade even though it probably is version .0622 or something like that, HTC has some weird version naming scheme that they don't even follow half the time.
Sent from my SCH-I535 using Tapatalk 2

prototype7 said:
Not sure what the [7] is, but the bootloader gets bypassed by Revolutionary's custom hboot so it can't be overwritten by an RUU or OTA, which is why you don't lose S-OFF unless you manually overwrite the hboot partition.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:49 AM ---------- Previous post was at 07:43 AM ----------
As for your issue, reflash the .0312 (or .0320, that's the one from the ICS leak) radio, the one from CS's image isn't an upgrade even though it probably is version .0622 or something like that, HTC has some weird version naming scheme that they don't even follow half the time.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! Flashing the new radio (.0312) seems to have fixed the problem, so far no bootlooping anymore.
By the way, I was on a .1111 radio after flashing the stock image. I would have wrote that sooner, but did not know until I had reflashed the phone once again where I could look at the baseband version, since it was bootlooping.
This is not a necessity, but... I was wondering how a person would flash the stock bootloader and turn it back to S-ON? Just in case I decide to sell my phone in the future, it would be "all stock".

swenpro said:
Thank you! Flashing the new radio (.0312) seems to have fixed the problem, so far no bootlooping anymore.
By the way, I was on a .1111 radio after flashing the stock image. I would have wrote that sooner, but did not know until I had reflashed the phone once again where I could look at the baseband version, since it was bootlooping.
This is not a necessity, but... I was wondering how a person would flash the stock bootloader and turn it back to S-ON? Just in case I decide to sell my phone in the future, it would be "all stock".
Click to expand...
Click to collapse
There's a guide in the general section, basically you have to flash the RUU, then extract the hboot and manually write it to the partition, it's fairly easy to do, easier than rooting it.
Sent from my SCH-I535 using Tapatalk 2

Thanks again! There are so many sections to this forum I had never noticed that sticky. Appreciate the help.

My silly n00b Question(s)
prototype7 said:
There's a guide in the general section, basically you have to flash the RUU, then extract the hboot and manually write it to the partition, it's fairly easy to do, easier than rooting it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Ok, i can't figure out what a sticky is, nevermind where to find the one you reference... Sorry.
I love XDA, it helped me root my dInc2 replacement, and that one's replacement (both after the previous phone's charge port died), and i just love it, BUT i've never had to use it except these two times, so i haven't figured out the forum stuff - like stickies - especially since i usually use NoScript normally and i don't really understand the general vs Q&A distinctions between groups of threads...
In any case - i haven't been able to find the sticky you referenced, and my searches have failed to find recent instructions regarding manually flashing the Hboot -- everything i found had download links that didn't work, except CS's stock ROM (as mentioned by the OP in this thread) - and now i've got that installed on my phone-to-send-back, so i've have successfully returned the ROM to a stock 2.3.4 GB using CS's post here on XDA, and from what i can tell/remember, flashing the HBOOT to stock (.97) will put it back exactly how it was when i got it last year - as i had to downgrade the OS but i don't think i had to touch the HBOOT (i got this phone in late March 2012)
So i'm now trying to rectify the issue that i don't know where to get the Hboot to manually flash, and, even if i had the file, i haven't found out if there is a ADB over TCP-IP that works when your USB/charge port has basically disconnected itself from the motherboard.
I was hoping that someone here might be able to help me either find the hboot file or extract what i need from CondemnedSoul's RUU (as seems to be described in prototype7's post), and give me the commands i need to do the manual flash...
If i could also get ADB over TCPIP advice, that would be awesome, but the former would be a good start...
Verizon has started to nag me for not returning the old phone sooner...
Thank you!
Also - thanks to Prototype7 for his awesome guide to s-off methods/rooting the Dinc2 -- was a life-saver for rooting the new phone so i could make use of my clockworkrecovery backup... (after some boot-looping horror, when i got an error during the update of the radio using the tacoroot method -- i restarted again from a different windows machine and it worked fine - i think the issue was the drivers on the other machine -- i'd used it to root the earlier phone, and i think it had weird drivers or something)

wntrequinx said:
Ok, i can't figure out what a sticky is, nevermind where to find the one you reference... Sorry.
I love XDA, it helped me root my dInc2 replacement, and that one's replacement (both after the previous phone's charge port died), and i just love it, BUT i've never had to use it except these two times, so i haven't figured out the forum stuff - like stickies - especially since i usually use NoScript normally and i don't really understand the general vs Q&A distinctions between groups of threads...
In any case - i haven't been able to find the sticky you referenced, and my searches have failed to find recent instructions regarding manually flashing the Hboot -- everything i found had download links that didn't work, except CS's stock ROM (as mentioned by the OP in this thread) - and now i've got that installed on my phone-to-send-back, so i've have successfully returned the ROM to a stock 2.3.4 GB using CS's post here on XDA, and from what i can tell/remember, flashing the HBOOT to stock (.97) will put it back exactly how it was when i got it last year - as i had to downgrade the OS but i don't think i had to touch the HBOOT (i got this phone in late March 2012)
So i'm now trying to rectify the issue that i don't know where to get the Hboot to manually flash, and, even if i had the file, i haven't found out if there is a ADB over TCP-IP that works when your USB/charge port has basically disconnected itself from the motherboard.
I was hoping that someone here might be able to help me either find the hboot file or extract what i need from CondemnedSoul's RUU (as seems to be described in prototype7's post), and give me the commands i need to do the manual flash...
If i could also get ADB over TCPIP advice, that would be awesome, but the former would be a good start...
Verizon has started to nag me for not returning the old phone sooner...
Thank you!
Click to expand...
Click to collapse
This is the guide I was referencing: http://forum.xda-developers.com/showthread.php?t=1466295
For ADB over TCPIP, I use ADBWireless off the market, but instead of using the adb connect command with the info it shows, use your phone's IP address shown under About phone>Status (I think that's where it is).

prototype7 said:
This is the guide I was referencing: http://forum.xda-developers.com/showthread.php?t=1466295
For ADB over TCPIP, I use ADBWireless off the market, but instead of using the adb connect command with the info it shows, use your phone's IP address shown under About phone>Status (I think that's where it is).
Click to expand...
Click to collapse
YOU ROCK. - thanks for the quick reply.
I read the guide you referenced - but the links are down, so i'll add a reply and see if that thread's OP can re-upload. If that seems to still be the correct way to un-root/S-on, then i'll see what i can do..
I had a bunch of questions, but i think I figured out the answers... i just need to go home from work and actually try out following those directions...

wntrequinx said:
YOU ROCK. - thanks for the quick reply.
I read the guide you referenced - but the links are down, so i'll add a reply and see if that thread's OP can re-upload. If that seems to still be the correct way to un-root/S-on, then i'll see what i can do..
I had a bunch of questions, but i think I figured out the answers... i just need to go home from work and actually try out following those directions...
Click to expand...
Click to collapse
See my reply in that thread, gave you updated links.