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.
Related
... 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
I need to bring my phone back to sprint I tried all UNROOT methods but my USB is broke and when I try to USE the PC36IMG.zip I get an error saying something like (update is older ect..) so I got the idea that if I flash a old rom before the updates and just update my phone it will unroot me but the problem I cant find a flashable rom thats old since we moved on so much since the EVO came out???
I just had to do this two days ago. You need an updated image file, it's posted in the unrooting thread in this forum. I'm on my cell so it'll take me a while to post a link. Give me a minute.
forum.xda-developers.com/showthread.php?t=780141
There's a copy of the updated file in that thread.
did you find this when you searched?
http://forum.xda-developers.com/showthread.php?t=695878
They only look for the superuser application. Flash a stock rooted rom. Remove the superuser app and you will be good to go.
Sent from my EVO using Tapatalk
DomSim said:
did you find this when you searched?
http://forum.xda-developers.com/showthread.php?t=695878
Click to expand...
Click to collapse
Your so helpful!
Sent from my EVO using Tapatalk
Unless they see his s-off in hboot.
They know to check the bootloader. Just install one of the official ruu to unroot. Simple as that. I've done it.
Official RUU
Just flash an official ruu and you will be good to go. You can find them all over the place in here.
3.70 (latest RUU)
Below is a link to the very latest RUU possible so that you're phone can be brought back to stock status without root. I would recommend flashing the S-On tool also which I'll post as the second link too. The first link is to the RUU. Good luck
Official RUU (will unroot your phone/rom)
http://forum.xda-developers.com/showthread.php?t=874091&highlight=ruus
The Unrevoked S-On Tool:
http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
EDIT: Also, I was thinking, if the above won't work due to your USB issues, maybe you could flash another rom, a sense based rom, like from Flipz or someone, and then run the "system update" program from the phone and maybe it'll update you to the latest RUU using the OTA Update program. That may solve your issues for getting the phone back to stock status without SU app and without root. Then, if that works, I would reboot the phone in to the bootloader and check to see if it says S-off or S-on. If it says S-on, you're fine and ready to go to sprint. If it says S-off, download and run the unrevoked S-on tool I posted above. Hopefully you won't need USB for it to run properly, but hey, you never know. Either way, if it does, there's got to be a way to use a S-on tool out there that doesn't need USB access. Hope this info helps you out in any way possible
EDIT #2: Read the stuff in this post to help with things if the above won't work.
http://forum.xda-developers.com/showthread.php?t=780141&highlight=ruus
When it says to connect USB and put the files on the SD Card, just use a card reader via a laptop or something to put the files on the SD Card and continue on.
I have taken my phone to sprint service centers 3 times. 2 speaker replacements, 2 screen replacements, a camera lens replacement (combined with a screen replacement, and they replaced the whole front of the phone - no more dents all around the shiny black bezel).
I always insisted they not replace the phone, as I wanna keep my 0002 HW. My phone was root with custom rom, but with a ''back to stock" theme flashed on it (thanks Virus)
My bootscreen is black (not white) with white evo 4g text, so, as soon as they turn my phone on it's obvious it's custom.
I know this isn't as helpful as previous posts, I'm just saying worst-case-scenario flash a stock theme and you'll probably be fine. I've had more than one tech tell me 'as long as you try to make it look stock, make the effort, that's good enough'.
Especially given that it's a hardware related issue, rather than a SW issue - I mean, they wont blame root access for your USB port not working.
Good luck, hope you get it sorted either way.
Sent from my PC36100 using XDA Premium App
Thread moved to Q&A.
GENEius said:
forum.xda-developers.com/showthread.php?t=780141
There's a copy of the updated file in that thread.
Click to expand...
Click to collapse
I tried that first and I can not get it to work, so I was looking for a older rom to flash then update it but cant find a old rom in a zip thats flashable!!
corelle said:
I tried that first and I can not get it to work, so I was looking for a older rom to flash then update it but cant find a old rom in a zip thats flashable!!
Click to expand...
Click to collapse
How old of a ROM are you looking for? There are plenty of 3.30 Software roms. Myn's RLS4 is 3.30 software, RLS3 is 3.29, etc. http://forum.xda-developers.com/showthread.php?p=8341836 That's a link to Myn's thread. Look in post #3, all of his older releases are linked there. Also, if you look in Myn's Signature, there's a link to OTA Supersonic 3.29, stock, rooted base rom.
With all that said, I don't think that will remedy you're 'main version older' problem. I believe it checks your hboot version, or radio versions or something. Not the actual software version. I could be wrong, but I believe that's the case. I would try a couple of the different PC36IMG's in this thread here http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu. It has all of the recent versions. If thew newest PC36IMG doesn't work, try the next older one (3.30) etc. One of them is bound to work for you. Good luck.
Some people have a 2nd Gmail account that isn't tied to any root apps incase the techs at sprint get nosey and look where they shouldn't be....
.........at 8 am today someone poisons the coffee....do not drink the coffee. More instructions will follow.
Cordially,
Future Dwight
may be late to the party, but check out some of these theres a **** load of old ROM's lol...
http://forum.ppcgeeks.com/cdma-htc-...m-database-163-2-new-roms-kernal-updates.html
http://forum.ppcgeeks.com/cdma-htc-...m-database-163-2-new-roms-kernal-updates.html
...bookmark it
When I did unroot, I restored my nandroid from before I installed ota 3.70, then unistall superuser (won't go away if you do a wipe), once your good to go, then use ra recovery to flash the official 3.70 ota, don't reboot once that completes, then flash s-on, then reboot you phone. I would recomend pulling ur sd card before taking it in, and doing a data wipe just to make sure all signs of root are gone
Sent from my Evo using the XDA app
OK so it looks like I keep getting that error code was because the files i was using was all corrupted I used (md5 checker) and it answered that for me...so I need a uncorrupted PG36IMG file!!!!
corelle said:
OK so it looks like I keep getting that error code was because the files i was using was all corrupted I used (md5 checker) and it answered that for me...so I need a uncorrupted PG36IMG file!!!!
Click to expand...
Click to collapse
Looking for an RUU?
corelle said:
OK so it looks like I keep getting that error code was because the files i was using was all corrupted I used (md5 checker) and it answered that for me...so I need a uncorrupted PG36IMG file!!!!
Click to expand...
Click to collapse
Where did you try downloading from? I've never got a corrupted one from the link I posted above. Did you try redownloading? Do you have a good internet connection?
I've been trying to flash the CDMA Wildfire's SPL (from this post: http://forum.xda-developers.com/showpost.php?p=11712773&postcount=1) onto my Alltel Wildfire. Since there's no custom recovery (yet), I traced the steps from here and modified my misc and cache partitions manually on my PC, then flashed them with flash_image. Unfortunately, it's not working.
I thought I might be doing something wrong, so I pulled out my old CDMA Hero and tried the exact same thing, but it worked on the Hero. What am I doing wrong? Is it because the rom is designed for Verizon, or did HTC just remove that update functionality? Any suggestions, hints, etc. are greatly appreciated.
EDIT: I just looked back at the post, and the rom isn't "designed" for Verizon, xHausx just said "Verizon's version of the Wildfire", referring to CDMA as opposed to GSM. My bad.
Wow. Nothing? I'm just looking for suggestions or opinions. I'm willing to try anything
Depending on how much spare time I get today, I might try reversing the stock recovery to see if there's anything in there related to flashing the bootloader. I'll post back if I find anything.
im going to try getting s off on this wildfire bee cdma. i will let you no what i find.
oostah said:
im going to try getting s off on this wildfire bee cdma. i will let you no what i find.
Click to expand...
Click to collapse
Awesome! Just thought I'd share some of my failed attempts to speed things up:
I replaced the public key with the test key in the stock recovery's /res/keys file, then tried a write_firmware_image. Didn't work.
I replaced the kernel in the boot.img with the bootloader, and set the load address to 0 ("jumpspl style"). Didn't do anything noticable (stayed on Alltel logo).
Another thing I noticed is my Bee's model number is PD0610000, and the one in the rom above is PD0611000. I don't know if there's anything significant in that, but between that and the massive difference in hboot versions, I'm afraid to try and flash that rom. Luckily, I found the alltel one here: h**p://u.115.com/file/t5f03f513d (can't link, even though I did before. hmm...). Someone would need to make some S-OFF patches, though, since it's a SHIP SPL.
I also thought about a unrEVOked forever style "radio hack" (for lack of a better term), but I'm not sure how to proceed down that road.
Good luck to ya
Isaac356 said:
Awesome! Just thought I'd share some of my failed attempts to speed things up:
I replaced the public key with the test key in the stock recovery's /res/keys file, then tried a write_firmware_image. Didn't work.
I replaced the kernel in the boot.img with the bootloader, and set the load address to 0 ("jumpspl style"). Didn't do anything noticable (stayed on Alltel logo).
Another thing I noticed is my Bee's model number is PD0610000, and the one in the rom above is PD0611000. I don't know if there's anything significant in that, but between that and the massive difference in hboot versions, I'm afraid to try and flash that rom. Luckily, I found the alltel one here: h**p://u.115.com/file/t5f03f513d (can't link, even though I did before. hmm...). Someone would need to make some S-OFF patches, though, since it's a SHIP SPL.
I also thought about a unrEVOked forever style "radio hack" (for lack of a better term), but I'm not sure how to proceed down that road.
Good luck to ya
Click to expand...
Click to collapse
i have two of these bee's i have one rooted but no recovery. so i was looking to see if i can get s off. but i should be able to spend mo time on them now.
bump for this thread. Is there any S-off available now for HTC Bee? I need it so bad. Thanks
Sorry for the near-necropost
Okay guys. It's not my main phone, so it's not a priority. But this is the only phone I have that I haven't been able to customize.
I'm very familiar with dirty root methods, I have a rooted/S-OFF'd Tb that I did by hand. If anyone knows/has the files I need to get a dirty S-off, I'd be more than happy to try and do this, and I'll post my results (best scenario, a guide) afterward.
Anyone? Please?
All the best,
-HG
motoyola said:
bump for this thread. Is there any S-off available now for HTC Bee? I need it so bad. Thanks
Click to expand...
Click to collapse
Re: bump Im looking for the same thing.
still nothin?
Any progress in rooting this? Any available RUU? Thanks!
HalosGhost said:
Okay guys. It's not my main phone, so it's not a priority. But this is the only phone I have that I haven't been able to customize.
I'm very familiar with dirty root methods, I have a rooted/S-OFF'd Tb that I did by hand. If anyone knows/has the files I need to get a dirty S-off, I'd be more than happy to try and do this, and I'll post my results (best scenario, a guide) afterward.
Anyone? Please?
All the best,
-HG
Click to expand...
Click to collapse
Do you still want to work on this phone? I have the Alltel and C Spire RUU but don't where to start.
Hi HalosGhost,
I really don't know which files you need, but I'm willing to send you whatever you told me to send you (from the phone), I'm able to have root access, and also I have a "backup" (since this "bee" doesn't have a way to backup the actual ROM) that I found in a chinese site: RUU_Bee_Alltel_WWE_1.07.671.2_Radio_1.00.00.1001_NV_Alltel_2_60_NoCNV_release_152081_signed.exe[/URL] (referenced by Isaac356, I tested and I did a successful re-flash to my cell) and I know it has the damn'd lock AKA nand lock, so I was unable (and as far as I understand, no1 has) to flash it because this one is preventing us from doing it.
If anybody has another tip I missed please say it now.
So, what you need, buddy?
NOTE: Grrr! I need it to take out the link: so I post it here: http: // u.115.com/file/t5f03f513d
PS, I missed to mention that I tried the GoldenCard creation but all I tried did NOT work
any news about this? I tried using HTCDEV to gain S-off but still no luck. It Just updated my hboot.
Is this even possible to RUU back to the old OS then root? I downloaded this file
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.02 25_2_NV_VZW1.92_release_181303_signed.exe
I want to try it but I don't want to brick my device of only 2 days old... lol
Come on! Be bold for the rest of us! Lol..I think someone said they tried it and it didn't work with s-on, however it does work with s-off.
I've also read that it fails when trying to flash the Froyo RUU over GB. It didn't brick it or anything, though.
If it does work with S-Off, in theory, if you have 2.3, you could use at XTC clip to achieve S-Off, then use the RUU to downgrade to Froyo, then root, CWM, etc. Right?
beenz said:
I've also read that it fails when trying to flash the Froyo RUU over GB. It didn't brick it or anything, though.
If it does work with S-Off, in theory, if you have 2.3, you could use at XTC clip to achieve S-Off, then use the RUU to downgrade to Froyo, then root, CWM, etc. Right?
Click to expand...
Click to collapse
I think what they are primarily looking for right now is a temp root for 2.3.3 so we can use the s-off tool. The old root exploit was patched with the 2.3.3 update, without that we can't downgrade and use the tool to achieve s-off, correct me if I'm wrong.
Whatever they do I hope they do it quick I cannot take sense for another day lol.
Yeah, I think it may fail too. I like Sense, I just want to remove the garbage that comes on this thing.
Any RUU from Verizon suck as the one mentioned above, will work on S-OFF, that's the beauty of S-OFF you don't need a file signed by HTC... with S-ON that RUU should flash since it is by HTC, it may say main bootloader is older and fail I'm not sure... I'd put it into a PG32IMG.zip and flash in hboot.. you can do this with the .3 RUU and the .4 exe
andybones said:
Any RUU from Verizon suck as the one mentioned above, will work on S-OFF, that's the beauty of S-OFF you don't need a file signed by HTC... with S-ON that RUU should flash since it is by HTC, it may say main bootloader is older and fail I'm not sure... I'd put it into a PG32IMG.zip and flash in hboot.. you can do this with the .3 RUU and the .4 exe
Click to expand...
Click to collapse
I'm actually downloading it right now, going to try and just flash it, if that fails then going to try it with GoldCard.
Let us know if it works for you.
Sent from my ADR6350 using XDA Premium App
rm2011 said:
Let us know if it works for you.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
Tried .exe method, no go. Tried regular method by renaming, no good, funny part is it doesn't even give a error or nothing when it loads it up, it just goes back to the Bootloader menu. Then i tried the Gold Card method, no go, although i did format my card, but i read that once you have a Gold Card it stays a Gold card. So unfortunately, even if i did root this phone and didn't upgrade to 2.3, because i'm getting a much needed replacement i'm doomed for 2.3 anyway. Whelp i tried.
shoman24v said:
Is this even possible to RUU back to the old OS then root? I downloaded this file
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.02 25_2_NV_VZW1.92_release_181303_signed.exe
I want to try it but I don't want to brick my device of only 2 days old... lol
Click to expand...
Click to collapse
You try this yet?
EDIT: Sorry, when I was reading this thread the only post that came up was the original. Once I replied they all showed up. Weird, but apologies.
shoman24v said:
Is this even possible to RUU back to the old OS then root? I downloaded this file
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.02 25_2_NV_VZW1.92_release_181303_signed.exe
I want to try it but I don't want to brick my device of only 2 days old... lol
Click to expand...
Click to collapse
I tried this way back before I got my xtc clip and the answer is no it will not work with s-on. It looks like its going to work and then displays a message about bootloader or something to that affect. I have it somewhere in these threads.
So here's a question off the top of my head. Probably not possible, but I'll ask anyway.
So the bootloader will only install HTC signed files, and we have HTC signed files of FroYo that the bootloader rejects. So there must be some kind of version check where it'll only flash a file with a higher version number than what's currently on the phone. If we knew where it was checking, would it be possible to modify a FroYo RUU file to report a higher version than the current GB so the bootloader thinks it's installing an upgrade instead of a downgrade?
Like I said, probably not possible, but it would seem to be logical.
ChrisDDD said:
So here's a question off the top of my head. Probably not possible, but I'll ask anyway.
So the bootloader will only install HTC signed files, and we have HTC signed files of FroYo that the bootloader rejects. So there must be some kind of version check where it'll only flash a file with a higher version number than what's currently on the phone. If we knew where it was checking, would it be possible to modify a FroYo RUU file to report a higher version than the current GB so the bootloader thinks it's installing an upgrade instead of a downgrade?
Like I said, probably not possible, but it would seem to be logical.
Click to expand...
Click to collapse
It does make sense, however the signature is generated from the contents of the file. If you change the contents of the file, it invalidates the signature and the boot loader won't load it. That is how HTC prevents you from modifying official HTC files.
ChrisDDD said:
So here's a question off the top of my head. Probably not possible, but I'll ask anyway.
So the bootloader will only install HTC signed files, and we have HTC signed files of FroYo that the bootloader rejects. So there must be some kind of version check where it'll only flash a file with a higher version number than what's currently on the phone. If we knew where it was checking, would it be possible to modify a FroYo RUU file to report a higher version than the current GB so the bootloader thinks it's installing an upgrade instead of a downgrade?
Like I said, probably not possible, but it would seem to be logical.
Click to expand...
Click to collapse
If you modified the file. It wouldn't be signed by HTC anymore.
If it is checked by md5, it can be spoofed.
http://www.win.tue.nl/hashclash/SoftIntCodeSign/
Sent from my ADR6350 using XDA App
slydweis said:
If it is checked by md5, it can be spoofed.
http://www.win.tue.nl/hashclash/SoftIntCodeSign/
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
I remember this being discussed before in the Eris forum. I can't find the thread, but I believe that the signature is somehow encrypted, and you would need the encryption key. I believe they even discussed if you could crack the encryption code, and although possible, it was not likely.
tpbklake said:
It does make sense, however the signature is generated from the contents of the file. If you change the contents of the file, it invalidates the signature and the boot loader won't load it. That is how HTC prevents you from modifying official HTC files.
Click to expand...
Click to collapse
I figured that, I just wondered if since all that would presumably need to be changed would be a single digit, if there would be any way to do it without screwing up the signature, like with a hex editor or something.
But, like I said, I figured it wasn't possible...
I have hw 003 hboot 2.10. I can enter hboot but not recovery. during normal boot phone just shows evo boot screen and boot loops. same thing when I try to enter recovery. I was s-off but after trying some methods in other brick threads I ended up with s-on.
I was using miui 2.2.3 when I turned it rebooted into recovery to make a nand and that is when the loops started. I have tried several ruu's with no luck on getting it to boot. was going to try the lastest ruu but not sure if I should.
I am flashed for cricket so there is not the option of bricking and returning to sprint for a replacement.
Edit: was not using twrp. Ar 2.3 was my recovery. As stated earlier I tried several ruu's in pc36img.zip.
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
sitlet said:
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
Click to expand...
Click to collapse
You can be bricked and still get in hboot Twrp2.0 did it to a few phones, the partitions end up screwed up and you can boot to hboot but no recovery or system not sure which partition gets borked but I think its the misc partition
We are legion, for we are many
Where is Captain_Throwback to save the day and another evo once again
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
stevovanburen said:
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
Click to expand...
Click to collapse
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
You weren't using twrp2.0 were u? If you were more than likely SOL that's one of the main reasons twrp for the evo is no longer supported even tho it works great on other devices like the kindle fire and 3vo I use it on the KF which I have running cm9 which I just got running on the evo as well now I gotta get my kernel fixed for this thing, have you tried reflashing your recovery? Or using adb to push a boot.img
Sent from my PC36100 using xda premium
evo4gnoob said:
Where is Captain_Throwback to save the day and another evo once again
Click to expand...
Click to collapse
I know. Captain has become the shaman of the Evo. He needs a special title, like Honorary Genius, or something.
sent from AOKP heaven
You guys flatter me .
I don't have any experience with MIUI, though. It's the one ROM I've never tried, but if it's an AOSP ROM, then the bootloop of death is always a possibility.
We haven't had any success rescuing anyone in that scenario, unfortunately. Flashing the ENG HBOOT will allow you to run fastboot commands, though, so that's probably the first step if you want to flash stuff through fastboot.
If you can't get adb working, then there probably isn't much hope. Since you ended up S-ON, and now without a custom recovery, I don't think there's much you can do. Perhaps others with a similar issue can chime in, but as far as I know, there's no current solution. The only way I'd know for sure is having the phone in my hands personally, but I doubt that's a possibility. I haven't personally experienced this bootloop thing, but it sounds scary .
jlmancuso said:
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
Click to expand...
Click to collapse
Ok so I have unlocked the bootloader from the htcdevelopers site and i can now use fastboot commands and have tried flashing the recovery. I see it load and write to the phone only thing is that it makes no difference. I still just get the boot loop.
Hate to say it, my friend, but I think it's the end of the road for that phone
HipKat said:
Hate to say it, my friend, but I think it's the end of the road for that phone
Click to expand...
Click to collapse
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
jlmancuso said:
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
Click to expand...
Click to collapse
I assume you're referring to this thread: http://forum.xda-developers.com/showthread.php?t=1480630
Have fun trying! Many have tried, and I think only 1 ever succeeded.
thanks captain.
capn, thanks for the link! I've had that README_EVO.docx file on my SD for god-knows-how-long and have always wondered where in the hell I got it lol (and 'why').
@jlmancuso
Good luck, but condolences as well. My $ says, if Cap'n can't fix it, it likely can't be fixed (on Evo). Seems that guy has explored every RUU, Hboot, recovery, NV, Radio, kernel etc. He could probably BUILD an Evo, HW and SW lol.
sent from AOKP heaven
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
fatalfury said:
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
Click to expand...
Click to collapse
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
EDIT: This is the thread - you'll probably want to read the whole thing, and if you have issues, maybe you can PM the guy that got it working.
The potential problem I see for you is that you're S-ON and bootloader is locked. You're probably going to have to unlock your device with HTCDev.com before you can make any headway. How were you able to write NV items to the phone? Don't you have to be S-OFF to do that?
Captain_Throwback said:
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
Click to expand...
Click to collapse
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
evo4gnoob said:
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
Click to expand...
Click to collapse
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Captain_Throwback said:
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Click to expand...
Click to collapse
use HTC dev to unlock then use your guide to downgrade then root with revolutionary then downgrade hboot ?