Develop Bugs

[Q] Rooting Evo with New Firmware

I know this has been asked a hundred times. Just wanna check on the best method for rooting with my software configuration.
Software #: 3.70.651.1
Hardware Version:.0003
I am pretty familiar with adb and rooting Heros via CMD so if I could use a method like that, it would be great. So in essence if its possible to RUU back to an older rom version to root that way, I would prefer.
Thanks.

the hboot version you have will determine which method you can use to root your phone...since you have a hardwear version 0003 and sfotware 3.70 i am assuming you have hboot 2.02 or 2.10
check your hboot to make sure by going into bootloader...
here is the guide for root with hboot 2.02 or 2.10 http://forum.xda-developers.com/showthread.php?t=829045
if you have a different hboot let me know and i will direct you to the proper thread to root

firmware too new?
I am trying to root my EVO 4G HBoot 2.16.0001 and after running unrevoked I keep getting a message "firmware too new". I've already done the factory reset and it hasn't helped. Any ideas?

aviwas said:
I am trying to root my EVO 4G HBoot 2.16.0001 and after running unrevoked I keep getting a message "firmware too new". I've already done the factory reset and it hasn't helped. Any ideas?
Click to expand...
Click to collapse
omg not again.... facepalm
YOU CANNOT ROOT THE NEWEST OTA! There are over 60 threads about this, if you would have taken 10 seconds to look, you would have found your answer. And FYI, you dont need to revive an 8 month old thread...

aviwas said:
I am trying to root my EVO 4G HBoot 2.16.0001 and after running unrevoked I keep getting a message "firmware too new". I've already done the factory reset and it hasn't helped. Any ideas?
Click to expand...
Click to collapse
Get in line like everyone else with 4.22 or 4.24 waiting for a new root method.

aviwas said:
I am trying to root my EVO 4G HBoot 2.16.0001 and after running unrevoked I keep getting a message "firmware too new". I've already done the factory reset and it hasn't helped. Any ideas?
Click to expand...
Click to collapse
As everyone else has said, you will have to wait until a developer or person in general finds out a way to root the latest firmware. No root method for now, though there is a temp root method in the Android Development forum for the HTC EVO 4G

sitlet said:
omg not again.... facepalm
YOU CANNOT ROOT THE NEWEST OTA! There are over 60 threads about this, if you would have taken 10 seconds to look, you would have found your answer. And FYI, you dont need to revive an 8 month old thread...
Click to expand...
Click to collapse
Atleast it looks like he searched. People like you ruin xda. Most of us members were just like him but when people like you talk that way, it turns the new members away
Sent from my PC36100 using Tapatalk

I'm usually a patient person, but, even, I am getting a little annoyed by all the (what seems obvious to us) questions about rooting hboot 2.16 and gingerbread.

Crossrocker said:
Atleast it looks like he searched. People like you ruin xda. Most of us members were just like him but when people like you talk that way, it turns the new members away
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I'm interested into the research that you did that brings you to this conclusion. Or is it just an opinion? Because, in my opinion, people like you ruin xda. See how easy that is?

Children!
Sent from my PC36100 using XDA App

github said:
I'm interested into the research that you did that brings you to this conclusion. Or is it just an opinion? Because, in my opinion, people like you ruin xda. See how easy that is?
Click to expand...
Click to collapse
He's got a good point..

github said:
I'm interested into the research that you did that brings you to this conclusion. Or is it just an opinion? Because, in my opinion, people like you ruin xda. See how easy that is?
Click to expand...
Click to collapse
All I'm saying is that instead of being intimidating, be kind. He brought up an old thread about rooting new firmware(maybe he searched using tapatalk?). If he would have made a new thread in dev section then a little flaming is pretty much required
Sent from my PC36100 using Tapatalk

Atleast it looks like he searched. People like you ruin xda. Most of us members were just like him but when people like you talk that way, it turns the new members away
Click to expand...
Click to collapse
Well IMO people like YOU ruin xda.
And no, he didn't do a search. If he did, he would have found the 60 or so threads that answered his question. And if for some reason he didn't find his answer, he didn't need to revive an 8 month old thread that has nothing to do with his question.

samah said:
As everyone else has said, you will have to wait until a developer or person in general finds out a way to root the latest firmware. No root method for now, though there is a temp root method in the Android Development forum for the HTC EVO 4G
Click to expand...
Click to collapse
Wait... WHAT???

samah said:
No root method for now, though there is a temp root method in the Android Development forum for the HTC EVO 4G
Click to expand...
Click to collapse
No there isn't.

Sounds like now might be a really good time to sell my evo.....
If anyone is interested, shoot new
A pm.
Sent from my PC36100 using XDA App

Confirm that I bricked my phone please?

... before i shell out for another phone because I'm an idiot.
Anyway, I'd been doing some reading and had a thin history of rooting with my G1 which went rather well.(in that I never bricked it)
I did the same with my phone now, the G2. I got it when it first came out, got comfortable with it and finally decided to root it. I guess I didn't do enough research because I used Visionary to root and I believe I am now bricked. I have been up and down the forums for a solution or even a confirmation that I'm bricked for the last 4 hours. I kid you not. I even went into different phone sections in case I found something that could help but zilch.
So yell at me for not doing enough research and reading before i started rooting, but don't yell about this same question being asked over and over again.
Anyways, I can only get to the first white "HTC" screen and freezes.
I can get to HBOOT and that says:
Vision PVT SHIP S-ON
H-Boot-0.02.0000
Microp-0425
Radio-26.03.02.26_M
cMMC-boot
HBOOT
If I try to go to recovery it goes to that little black phone with the red traingle.
If I try to go to factory reset it goes to a green circle with a load bar that just looks like it's working but then it goes back to the white HTC screen and stays.
I have SDK and even though my computer recognizes that an Android 1.0 device is attached, when I "adb devices", nothing is listed.
So what's my diagnoses pros?
Thanks for any help or any response at all in advance.
Dea.

Its not looking good my friend, what exactly have you done to your phone so far?
If it is stuck in a boot loop and you have S-on the only possible thing you can to do fix it is flash the stock PC10IMG, but this will only work if you had the pre-OTA rom on your phone 1.19 and I really doubt that you did. If you had the wifi calling app you had the OTA 1.22 rom not the 1.19 rom. Trying to flash the stock PC10IMG onto your phone if it had the OTA rom 1.22 will cause it to do exactly what is happening now.

There's a file called "pc10img.zip" (the default firmware) that can be placed in the root of your SD, and should automatically be detected and offer to start flashing. I think this is how I recovered my phone which was in a similar state. Someone here could probably link you to the proper file (I'm sure there's different versions for DZ and G2). Good luck...I think you can probably save it.
I'm pretty sure mine was doing the same thing yours is, and I'm happily rockin' CM7 now, and loving it more than ever.

@joemm, Well I had 1.22 on there since I remember having wifi calling. I know you advised me not to but I might look into the PC10img.zip just because it can't get much worse than this honestly.
@hexapus, thanks for the advise. I'll have to look for my sdcard adapter first though. can't seem to find it at the mo'.
And when it does its sd card check on HBOOT, by the way, it says that all the files it wants to load, it says "No image!"

dealunae said:
And when it does its sd card check on HBOOT, by the way, it says that all the files it wants to load, it says "No image!"
Click to expand...
Click to collapse
Thats because its looking for the file named PC10IMG.zip, this is the only file name it will load and it must be on the root of your sdcard.
Check your PM i will message you right now.

This is a link to a page containing instructions for a manual update to 1.22 and a link to the update.zip. Maybe this will work if all else fails by applying the OTA update again.
http://www.talkandroid.com/20232-tutorial-manually-update-t-mobile-g2-remove-google-goggles/

You might be able to hex edit the pc10img.zip so it thinks its version 1.22.
Sent from my T-Mobile G2 running Cyanogenmod.

I also had this same issue, in that I tried visionary and had the same issue. I took mine to the tmobile store and let try to fix it, which they couldn't, and when they asked me what happened I said I was uninstalling an app that was a live screen because it was acting werid. Because I was still under warrenty they help me get a new one sent to me.
Worked out for me, now I read and read and read more. I am rooted via rage and gfree but still run stock.
Good luck
Sent from my T-Mobile G2 using XDA App

Well, everyone, after further button pushing, it looks like I can get into stock recovery. Should I do a wipe and flash a manual update of 1.22? The only reason I ask at this point is that if I try to do this, fail and then try to get it replaced, they might see that I tried to root and not replace it. (I have insurance as well btw.)

dealunae said:
Well, everyone, after further button pushing, it looks like I can get into stock recovery. Should I do a wipe and flash a manual update of 1.22? The only reason I ask at this point is that if I try to do this, fail and then try to get it replaced, they might see that I tried to root and not replace it. (I have insurance as well btw.)
Click to expand...
Click to collapse
The link I gave to you above has some great instructions on applying the manual update again. In my opinion its your best option at this point. BTW I have insurance too. I'm always worried that I might lose my phone!

It won't let you apply the 1.22 update zip because it is not a full rom, people have tried before and it doesn't work, but I guess like you said what have you got to lose.
Sent from my HTC Vision using XDA App

joemm said:
It won't let you apply the 1.22 update zip because it is not a full rom, people have tried before and it doesn't work, but I guess like you said what have you got to lose.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
joe, check out the second part of that link I provided above. The part about those with the google goggles fix. Do you think that would be a good second choice? I don't know if the OP knows how to do a fastboot flash, but it seems like it is more comprehensive. Do you think that it would reverse the effects of the Visionary perm root attempt?

EdKeys said:
joe, check out the second part of that link I provided above. The part about those with the google goggles fix. Do you think that would be a good second choice? I don't know if the OP knows how to do a fastboot flash, but it seems like it is more comprehensive. Do you think that it would reverse the effects of the Visionary perm root attempt?
Click to expand...
Click to collapse
At this point for him I don't see how its gonna hurt to try, but in my experiences in this forum I have not seen anyone able to flash the update 1.22 .zip after being stuck in a S-On Bootloop. Its either gonna work or it wont let him flash it at all, so I really cant see how it could hurt to try. As far as the 1.19 rom it wont let him flash it because it will give a error that the main version is older.

EdKeys said:
The link I gave to you above has some great instructions on applying the manual update again. In my opinion its your best option at this point. BTW I have insurance too. I'm always worried that I might lose my phone!
Click to expand...
Click to collapse
yea. It's how I realized I could still get into recovery. Thanks for the link. I'm at work right now so I won't be able to work on it till later but Wish me luck!

dealunae said:
yea. It's how I realized I could still get into recovery. Thanks for the link. I'm at work right now so I won't be able to work on it till later but Wish me luck!
Click to expand...
Click to collapse
OK, good luck! I hope that it, or something else, eventually works for you. Keep us updated....

So ended up getting a new phone. An htc g2. (sigh) I still really want to to root but am not officially terrified. ha. Looks like a lot of research and reading is in my future.

dealunae said:
So ended up getting a new phone. An htc g2. (sigh) I still really want to to root but am not officially terrified. ha. Looks like a lot of research and reading is in my future.
Click to expand...
Click to collapse
Lol... no need aha. If you have the basic concept of rooting you should be fine. Of course u just follow each step for rooting. Wish u luck
Sent from my HTC Vision using Tapatalk

You didn't fix the old one? The pc10img fix almost certainly would have cleared it all up.
Sent from my HTC Vision using XDA App

[Q] downgrade 2.3 to 2.2

Anyone got anything on downgrading from the latest 2.3.3 to 2.2 ? time to root!!lol

Tekn010933 said:
Anyone got anything on downgrading from the latest 2.3.3 to 2.2 ? time to root!!lol
Click to expand...
Click to collapse
as far as i know there is no way to do it. the only way i can think of that might remotely work is to use the ruu but i have no experience with it and have no idea if it will work/brick your phone. i would recommend googling it extensively before attempting the ruu method

nvm i lied dont attempt the ruu it wont work.
http://androidforums.com/evo-4g-all-things-root/370216-how-downgrade-2-3-3-a.html
^^^ read that the first post after the op explains it all

PhxkinMassacre said:
nvm i lied dont attempt the ruu it wont work.
http://androidforums.com/evo-4g-all-things-root/370216-how-downgrade-2-3-3-a.html
^^^ read that the first post after the op explains it all
Click to expand...
Click to collapse
Thanks, already did the RUU earlier from diffrent angles and unsuccessful. Thanks will read on the thread..

No. Nope. Negative.
Needed 10 characters to post, but I figure the repetition wouldn't hurt either.

[Q] revert back to 2.2

got my htc evo 4g and came with gngrbd 2.3 I have s-on can someone please give me a detailed description on how to revert to 2.2 or throw me a link.
thank you!

You can't the new hboot won't allow downgrading and ps put in Q and A nexttime
Sent from my PC36100 using XDA App

you have to download hboot, nv, pri, wimax flash them one at a time. than install a 2.2 rom

enigma7820 said:
you have to download hboot, nv, pri, wimax flash them one at a time. than install a 2.2 rom
Click to expand...
Click to collapse
Wrong. You can't flash back from 2.3.3 & S-ON at this time. Don't spread false information.
OP: Please search next time. Wrong forum, and question has been answered numerous numerous times.
Flame on.
HTC EVO: The new budget device.

github said:
Wrong. You can't flash back from 2.3.3 & S-ON at this time. Don't spread false information.
OP: Please search next time. Wrong forum, and question has been answered numerous numerous times.
Flame on.
HTC EVO: The new budget device.
Click to expand...
Click to collapse
You called the hell out of it git. I'm leaving this forum in two weeks. Thank god.
Sent from my Xoom using XDA Premium App

evo with s-off
I have been able to get my evo with gingerbread and s-off below are the pics for any non-believers. yes I am new to this but willing to assist however possible even if I need to ship off my phone to get everyone a working root.

ry8785 said:
I have been able to get my evo with gingerbread and s-off below are the pics for any non-believers. yes I am new to this but willing to assist however possible even if I need to ship off my phone to get everyone a working root.
Click to expand...
Click to collapse
How did you do it?

I had it rooted and had problems with a rom so I flashed a factory rom back on it and it updated to the GB OTA but I never turned the s-on. Of course that was before I knew we couldn't get a working root. I have tried everything possible I can think of to get it rooted again. This is why I said if need be I would send to a dev to see what they can do with it since it does have s-off.

thats cool. From what i've read today they are super close

1ShEiTaN1 said:
thats cool. From what i've read today they are super close
Click to expand...
Click to collapse
Where did you read this info?

a couple threads on xda and a couple twitter feeds-something about achieving a temp root (dont know too much about that)

ry8785 said:
I have been able to get my evo with gingerbread and s-off below are the pics for any non-believers. yes I am new to this but willing to assist however possible even if I need to ship off my phone to get everyone a working root.
Click to expand...
Click to collapse
No one is going to argue you on this one. There are countless threads of people being s-off. So long as they rooted at some point.

ry8785 said:
I have been able to get my evo with gingerbread and s-off below are the pics for any non-believers. yes I am new to this but willing to assist however possible even if I need to ship off my phone to get everyone a working root.
Click to expand...
Click to collapse
That's like bragging that I can get into my apartment. Sure, I have a key to the door, which helps.
If you were S-OFF before GB, there's no problem. If you weren't S-OFF and you updated, there's no solution yet.

GB 2.3.3 almost rooted

So I was reading a post about someone who was potentially able to downgrade hboot 2.16 hw4 2.3.3 to hboot 2.10 via bootloader and a PC63IMG.zip that had 3.70 in it. So I tried on my 2.3.3 s-On evo and sure enough it failed. It wouldnt work because it was an older version. So, I extracted the PC63IMG.zip and replaced the hboot 2.10 with hboot 2.16 (renaming hboot 2.16 to hboot 2.10) from the post in the dev section. I used winrar and with normal compression rezipped the files and signed in android kitchen. it actually loaded the files and went through checking them, but once check it kicked me back to the main menu of the bootloader with no error or messages. I tried the same with the file with no compression when zipped and signed and i got an error stating that it was a wrong file. and didnt even pass the check. So have I stumbled upon something simple and useful? Can someone help me look into this further and maybe it will get us somewhere. Or am I a dumb?

Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.

androidsupra said:
Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.
Click to expand...
Click to collapse
What? I never said anything about porting. I was trying to find a simple way to Root my Evo running 2.3.3. Still no luck but I was hoping what I found may be something someone has not yet tried. Its simple but I was suprised that it looked like it passed the bootloader check. I did not receive any errors, but at the same time could not downgrade.

Once you got back to the hboot menu, what version did it say you have?
If 2.10, I would think your next bet is try and run unrevoked

androidsupra said:
Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.
Click to expand...
Click to collapse
You do know the dev section is for more than ROM's. Moron. This is a post from someone attempting to find root and you show your true intelligence level.
Sent from my PC36100 using Tapatalk

spotopolis said:
What? I never said anything about porting. I was trying to find a simple way to Root my Evo running 2.3.3. Still no luck but I was hoping what I found may be something someone has not yet tried. Its simple but I was suprised that it looked like it passed the bootloader check. I did not receive any errors, but at the same time could not downgrade.
Click to expand...
Click to collapse
He wasn't serious about porting anything, common thing to do when someone posts in the wrong section (especially in development).
On my main note, any modification of an "official" PC36IMG.zip would break HTC'S signature and the bootloader would not accept the update.
Sent from my PC36100 using XDA Premium App

He's attempting to Flame I believe. Due to a lot of mis placed posts. However, I do not find this to be mis placed. It is valid, and just the fact that it tried to run is great. farther then most have gotten, and the way I see it, any good inputs/thoughts should be welcomed warmly.
Sent from my Xoom using XDA Premium App

So now what I am trying to do is download, extract, and replace the hboot from http://www.megaupload.com/?d=VSFLE9CD with the 0.76 hboot, repack, resign, and test in the bootloader. This is all really simple stuff and thats why I am wondering if it will work. Because its so simple something like this was overlooked.

HipKat said:
Once you got back to the hboot menu, what version did it say you have?
If 2.10, I would think your next bet is try and run unrevoked
Click to expand...
Click to collapse
as far has my bootloader says for now it has the latest everything unfortunately. hboot 2.16 hw4 and all that. I was surprised that I was able to get passed the check without an error doing this though and its why I posted. I have 4 minutes left on the new PC63IMG.zip downloading before I can try to mess with it.

I tried this exact same thing just last night. It did the same thing to me as well, with it returning to the bootloader menu with no error msgs. If somehow we are able to edit the PC36IMG.zip file to match the hboot version 2.16 with the 3.70 update to pass security check then we may be on to something. But I'm not sure how to resign an IMG zip with HTC's signature to pass security. Thoughts?

sivarticus85 said:
I tried this exact same thing just last night. It did the same thing to me as well, with it returning to the bootloader menu with no error msgs. If somehow we are able to edit the PC36IMG.zip file to match the hboot version 2.16 with the 3.70 update to pass security check then we may be on to something. But I'm not sure how to resign an IMG zip with HTC's signature to pass security. Thoughts?
Click to expand...
Click to collapse
I am about to attempt now after signing the zip with kitchen.

spotopolis said:
I am about to attempt now after signing the zip with kitchen.
Click to expand...
Click to collapse
You will be my hero if this works.

Damn! Same thing. I loaded up the latest update with the older hboot renamed to match the new one it replaced. rezipped with normal compression, signed PC63IMG.zip with latest kitchen, it loaded the modded PC63IMG all the way in the bootloader and passed that, then started checking the file and then just went to the main menu again with no errors.

Is it possible that it is not doing anything because it thinks im loading up the same version it is running? Could I simply change another file to make the bootloader think Im uploading a newer version so it would take the update?

I guess you guys haven't heard the news, but you can't resign the damn thing with HTC's key because we don't have HTC's keys. As many have stated the focus should be temp root, then the bootloader shall fall. Cart before the horse kids.

That sucks. Oh well can't hurt that you tried.

Otta way to think out of the box. I hope u get somewhere with this buddy. I would love to help but I know nothing. Lol. I can make lock rings. That's bout it. Good luck
Sent from my PC36100 using Tapatalk

androidsupra said:
I guess you guys haven't heard the news, but you can't resign the damn thing with HTC's key because we don't have HTC's keys. As many have stated the focus should be temp root, then the bootloader shall fall. Cart before the horse kids.
Click to expand...
Click to collapse
I know that but if you don't sign with the kitchen it wouldn't have even gotten this far correct? So its something right? Even if it doesn't work, its another thing on the list that has been tried and maybe it will lead to something else. You never know with electronics. A single random chip could be made slightly different from others and it changes everything. No way to know until you try.

Do I really need to link every post where someone has tried to mod these files, I mean really...
There is a post about every three days on this same subject, it goes on for two days and then gets locked like this one will. And on the next day somebody else posts their marvelous idea of tricking the bootloader. And the cycle continues.

androidsupra said:
Do I really need to link every post where someone has tried to mod these files, I mean really...
There is a post about every three days on this same subject, it goes on for two days and then gets locked like this one will. And on the next day somebody else posts their marvelous idea of pricking the bootloader. And the cycle continues.
Click to expand...
Click to collapse
Is that not the point of this community? Someone trying to use some other persons idea and expand on it? Who cares if it ultimately doesn't work? Its information.