Ok this is how i got the current pri. I used whitslack idea but used the latest ruu zip files that were extracted from the 2.2 froyo update and replaced the recovery and eng-bootloader updated my phone by putting it on my sd card. Once that was done and booted back up granted i did not have su cause i don't know where to find the most current version. I then turned phone off booted into recovery and flashed dc 3.5. I then rebooted and then installed root explorer and deleted stuff i do not use. I then dialed ##786# did factory reset u must have msl code. Once it booted into recovery and wiped data/cache i also deleted dalvik-cache and then rebooted phone it did hands free activation and updated prl and then it checked for firmware update. And once i went to about phone and software information i saw i had pri 1.40.003. I do not know if this will work for you but i did for me.
*EDIT* If someone does try this could u check after the update using the PC36IMG and see if just that updates the pri. Thank you
Ok i will provide links to the files i used but if u lose root or brick your phone i not responsible.
Thank you to dc dev team for a great rom and whitslack for the idea on the PC36IMG idea. And xda for a great forum
Here is the link to dc thread. http://forum.xda-developers.com/showthread.php?t=745659
Here is the link to the PC36IMG i used http://www.megaupload.com/?d=YVHC5NY2
and finally here is a video of it for proof http://www.youtube.com/watch?v=CWLwP4XsPrk
Punctuation was invented for a reason. *head explodes*
mjohnson4580 said:
Ok this is how i got the current pri used whitslack idea but used the latest ruu zip files that were extracted from the 2.2 froyo update and replaced the recovery and eng-bootloader updated my phone by putting it on my sd card once that was done and booted back up granted i did not have su cause i dont know where to find the most current version i then turned phone off booted into recovery and flashed dc 3.5 rebooted then installed root explorer and deleted stuff i do not use then dialed ##786# did factory reset u must have msl code. once it booted into recovery and wiped data/cache i also deleted dalvik cache rebooted phone it did hands free activation and updated prl and checked firmware. once i went to about phone and software information i saw i had pri 1.40.003. i do not know if this will work for you but i did for me
Ok i will provide links to the files i used but if u lose root or brick your phone i not responsible.
Thank you to dc dev team for a great rom and whitslack for the idea on the PC36IMG idea. And xda for a great forum
Here is the link to dc thread. http://forum.xda-developers.com/showthread.php?t=745659
Here is the link to the PC36IMG i used http://www.megaupload.com/?d=YVHC5NY2
and finally here is a video of it for proof http://www.youtube.com/watch?v=CWLwP4XsPrk
Click to expand...
Click to collapse
and you had pri 1.34 prior to doing this?
Yes i had 1.34.003 pri before this
so let me get this straight, im currently rooted and full nand unlocked, and i have pri 1.34. All i gotta do is flash the linked PC36IMG.zip, Lose root. And ill still retain engineering Recovery? that way when i get into the "somewhat" official rom, i can do all teh necessary programing and updating, so that i can flash back to DC Rom, and get my PRI to be the latest?
i need clarification.
Thats the way I am understanding this. I'm very tempted to try it, if nothing else to just to help the cause.
i wouldn't do it.
I just don't see how it works.
He never said he still had nand after updating.
He only has 10 posts he might just be trying to make us delete everything on our phones. But I am going to try it anyway and hopefully not loose root permanently. I will post back with my findings.
Upon inspecting his file it looks like he has nand unlocked unless he is trying to screw with everyone and renaming files to throw us off well here is the moment of truth i'm gonna flash it.
I would be good to get toast's input on this thread.
l33tlinuxh4x0r said:
He only has 10 posts he might just be trying to make us delete everything on our phones. But I am going to try it anyway and hopefully not loose root permanently. I will post back with my findings.
Upon inspecting his file it looks like he has nand unlocked unless he is trying to screw with everyone and renaming files to throw us off well here is the moment of truth i'm gonna flash it.
Click to expand...
Click to collapse
i'm staying on this thread and refreshing to see status
l33tlinuxh4x0r said:
He only has 10 posts he might just be trying to make us delete everything on our phones. But I am going to try it anyway and hopefully not loose root permanently. I will post back with my findings.
Upon inspecting his file it looks like he has nand unlocked unless he is trying to screw with everyone and renaming files to throw us off well here is the moment of truth i'm gonna flash it.
Click to expand...
Click to collapse
Let me know bro, I have been following your post all day and was just getting ready to flash when I saw your post lol. I'll be refreshing this page every 5 mins lol.
I went ahead and took the plunge, so far everything looks legit. I'm currently doing the hands free activation atm
ranmasaotome510 said:
i'm staying on this thread and refreshing to see status
Click to expand...
Click to collapse
L33t is trying it again as we speak, first attempt was a no go, but he said he missed a step or two, so we are still waiting for his results
Subscribed. If this works I'll ****.
Thanks.
I thought that the rcdata.img was not on any of the ota roms. Hmmm
pongoface said:
I thought that the rcdata.img was not on any of the ota roms. Hmmm
Click to expand...
Click to collapse
it must be...people are claiming that from 1.32 to the OTA 1.47 their pri goes up to 1.40 (unless they are lying )
kinda quiet now. Hope all is well with the 2 guinea pigs. Crosses fingers.
It won't work unless he has the extracted "rcdata.img" from a stock phone that hasn't flashed the "rcdata.img" from the eng-PC36IMG. We wouldn't need to flash the whole PC36IMG, just the rcdata.img. If your bootloader is unlocked you can create a PC36IMG zip with only the rcdata.img and it will flash only that and leave all else in place. If you notice, while you flash the rcdata.img it says...custom radio listed as the partition being flashed....I've flashed the PC36IMG in many different forms and the 1.40 PRI is no where in any of what's on this Forum. As others have said...we need the extracted rcdata.img from a non-flashed, eng-rcdata.img phone....
adeyo said:
it must be...people are claiming that from 1.32 to the OTA 1.47 their pri goes up to 1.40 (unless they are lying )
Click to expand...
Click to collapse
But isn't whitslacks method based off the stock 1.47 rom in which he replaced the hboot and recovery just like here. You would assume that the pri would be updated using that method.
there is no rcdata.img in his pc36img.zip so it doesn't look like he extracted it and it does not look like he put in the faked one either so this might actually be legit if it works still waiting for my phone to boot up.
Related
ok, i thought the 1.47 OTA would download to my sdcard...it didn't. But i wasn't quite convinced it was on the device so i clicked "install update" w/ the sd card pulled...as soon as it began i pulled the battery. Now, whenever i boot it automatically goes straight to the black update screen (with the hard drive icon) trying to install the OTA !!!
How can i stop this and boot normally back into 1.32??? w/o forcing the 1.47 update!!
(i am unrooted btw) THANKS FOR ANY TIPS!!
adeyo said:
ok, i thought the 1.47 OTA would download to my sdcard...it didn't. But i wasn't quite convinced it was on the device so i clicked "install update" w/ the sd card pulled...as soon as it began i pulled the battery. Now, whenever i boot it automatically goes straight to the black update screen (with the hard drive icon) trying to install the OTA !!!
How can i stop this and boot normally back into 1.32??? w/o forcing the 1.47 update!!
(i am unrooted btw) THANKS FOR ANY TIPS!!
Click to expand...
Click to collapse
I could be wrong but i dont think there is a way to stop it if unrooted. in good news even if you let it update to 1.47 you can still root (just dont go to 2.2) so not sure why you would want to stay at 1.32
omegasun18 said:
I could be wrong but i dont think there is a way to stop it if unrooted. in good news even if you let it update to 1.47 you can still root (just dont go to 2.2) so not sure why you would want to stay at 1.32
Click to expand...
Click to collapse
thanks. i hadn't backed up everything yet. also, i had unrevoked so i hope this doesn't drop my pri down to 1.32 from 1.40 (i guess i lose free tethering too)...other than those things, i was just about to root and get froyo!
so, you don't think i can boot into recovery and wipe something before it completely installs upon reboot??
adeyo said:
thanks. i hadn't backed up everything yet. also, i had unrevoked so i hope this doesn't drop my pri down to 1.32 from 1.40 (i guess i lose free tethering too)...other than those things, i was just about to root and get froyo!
so, you don't think i can boot into recovery and wipe something before it completely installs upon reboot??
Click to expand...
Click to collapse
Not without root. Whatever is trying to run is almost certainly on /system, which is not writable without root access. Just let it go and root after that.
Also, NEVER PULL THE BATTERY WHILE THE SYSTEM IS FLASHING! That's a real good way to end up with a half-written (bricked) ROM.
Just let it update to 1.47 and then use Simple Root or whitslacks method to gain root again. Then flash back to 1.32 if you so desire. As mentioned before, do not allow it to update to 2.2 as there is not yet a method to gain root for the OTA 2.2.
Furthermore, check the dev forum for the PRI issue. They need someone with an unrooted OTA 1.47 with a PRI 1.40_003. You could be everyone's hero.
Sent from my PC36100 using XDA App
SilverZero said:
Not without root. Whatever is trying to run is almost certainly on /system, which is not writable without root access. Just let it go and root after that.
Also, NEVER PULL THE BATTERY WHILE THE SYSTEM IS FLASHING! That's a real good way to end up with a half-written (bricked) ROM.
Click to expand...
Click to collapse
wow...thanks!!! i hope i didn't screw anything up! i'm letting it finish up now...EHHH...THIS IS WIERD??? this time i was just going to let it flash and so i went ahead and plugged in my usb, but instead of flashing it went to the boot animations and back to my phone????...i'll check to see if i screwed anything up??
**EDIT: wow, it prompted me to install the update again, looks like i am back. I will try cancelling installation this time... (it gives me a discard update option) i click yes, it says "this will wipe the update from your phone" ....so I guess all is well!!!!
adeyo said:
wow...thanks!!! i hope i didn't screw anything up! i'm letting it finish up now...EHHH...THIS IS WIERD??? this time i was just going to let it flash and so i went ahead and plugged in my usb, but instead of flashing it went to the boot animations and back to my phone????...i'll check to see if i screwed anything up??
Click to expand...
Click to collapse
It probably tried to flash, found nothing there, and removed the instructions from the boot process. So you may have gotten away with it. Check your software version in Settings - About Phone to see where you ended up. Also, is your SD card still out of the phone? It may be waiting to spring back on you when you put it back in, but just let it go anyway if that's the case.
sombdy said:
Just let it update to 1.47 and then use Simple Root or whitslacks method to gain root again. Then flash back to 1.32 if you so desire. As mentioned before, do not allow it to update to 2.2 as there is not yet a method to gain root for the OTA 2.2.
Furthermore, check the dev forum for the PRI issue. They need someone with an unrooted OTA 1.47 with a PRI 1.40_003. You could be everyone's hero.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
everyone's hero?? haha...that PRI thread is why i was trying to download the 1.47 OTA in the first place anyway, i am still at 1.32 now. do you have a tip as to how i can help them??
SilverZero said:
It probably tried to flash, found nothing there, and removed the instructions from the boot process. So you may have gotten away with it. Check your software version in Settings - About Phone to see where you ended up. Also, is your SD card still out of the phone? It may be waiting to spring back on you when you put it back in, but just let it go anyway if that's the case.
Click to expand...
Click to collapse
ahh...maybe you are right? maybe it was a phantom flash anyway b/c i never put my sd card back in, also, i did delete that update.zip that was on there anyway...so i'll see if anything happens when i put the card back in. my settings show 1.32 still
**UPDATE: no attempt to reload/reboot system with update after sd card is in. Looks good!
Then you're the **** of the walk!
now, should i root and then go straight to 2.2 or go to 1.47 first?? what is the best way to keep my PRI 1.40_003 intact????
adeyo said:
now, should i root and then go straight to 2.2 or go to 1.47 first?? what is the best way to keep my PRI 1.40_003 intact????
Click to expand...
Click to collapse
I don't think you can, that's why there's a bounty out for it. When you root, your PRI will change to 1.34 because you have to use the engineering ROMs. Correct me if I'm wrong.
You don't want to just upgrade to 2.2 OTA . . . unless you WANT to block root until somebody finds a way to root Froyo on the Evo.
PRI aside, you should probably root from 1.32, no reason to go up through 1.47 and you'll avoid the "Main Version is Older" problem.
SilverZero said:
I don't think you can, that's why there's a bounty out for it. When you root, your PRI will change to 1.34 because you have to use the engineering ROMs. Correct me if I'm wrong.
You don't want to just upgrade to 2.2 OTA . . . unless you WANT to block root until somebody finds a way to root Froyo on the Evo.
PRI aside, you should probably root from 1.32, no reason to go up through 1.47 and you'll avoid the "Main Version is Older" problem.
Click to expand...
Click to collapse
great, thanks! i will root and go straight to 2.2. I guess there is no known way to keep PPI 1.4 and actually root. ...it just gets to me that unrevoked users can keep PRI 1.40 and full rooters can't...there should be some way!
adeyo said:
great, thanks! i will root and go straight to 2.2. I guess there is no known way to keep PPI 1.4 and actually root. ...it just gets to me that unrevoked users can keep PRI 1.40 and full rooters can't...there should be some way!
Click to expand...
Click to collapse
I wasn't aware of that, but the reason is probably that Unrevoked users can't flash any ROMs that would update the PRI anyway.
SilverZero said:
I wasn't aware of that, but the reason is probably that Unrevoked users can't flash any ROMs that would update the PRI anyway.
Click to expand...
Click to collapse
oh...what ROMs wouldn't update the PRI? My friend is an unrevoked 2?3? user and i know he has tried a few different ROMs ...one of them being DamageControl, most recently. He has also tried a few different kernels.
***EDIT: Here are the steps he took:
1) Started w/ Unrevoked 1
2) OTA'd 1.47
3) Unrevoked 3 from 1.47 (then was able to flash froyo rooted roms
4) He still doesn't have nand access, but he flashed the following roms: Fresh (most recent), Burnt Droid, the odexed Stock "FINAL" by netarchy, and DamageControl. Burnt droid didn't take, but neither did DamageControl at first, but now works fine. His recovery is ClockworkMod.
Hey all,
Attention Read all before doing anything!
So I followed the ##786# and updated my PRI. Worked flawlessly, might need to do it a few times to work.
However my bootloader updated...and I could no longer ADB to my phone...So I re did my root, which restored me from 2.2 to 1.36..or which ever toasts Root version was for. It also took a bunch of trys...had to manually install superuser, then restored my rom.
gotta love NAND backup.
Anyway, any ideas? was im being stupid and doing something wrong? or does PRI .4 screw the bootloader?
ChiefSpoonS said:
Hey all,
Attention Read all before doing anything!
So I followed the ##786# and updated my PRI. Worked flawlessly, might need to do it a few times to work.
However my bootloader updated...and I could no longer ADB to my phone...So I re did my root, which restored me from 2.2 to 1.36..or which ever toasts Root version was for. It also took a bunch of trys...had to manually install superuser, then restored my rom.
gotta love NAND backup.
Anyway, any ideas? was im being stupid and doing something wrong? or does PRI .4 screw the bootloader?
Click to expand...
Click to collapse
Yeah if you read them right you would have known you didnt have to load any files just do a ##786 wipe and be done with it. might take a few trys. But good catch READ READ READ then read it again
I did that. And I got .4 pli. My bootloader changed to .70 and and stopped working...wanted to know if that was isolated or not
Sent from my PC36100 using XDA App
ChiefSpoonS said:
Hey all,
Attention Read all before doing anything!
So I followed the ##786# and updated my PRI. Worked flawlessly, might need to do it a few times to work.
However my bootloader updated...and I could no longer ADB to my phone...So I re did my root, which restored me from 2.2 to 1.36..or which ever toasts Root version was for. It also took a bunch of trys...had to manually install superuser, then restored my rom.
gotta love NAND backup.
Anyway, any ideas? was im being stupid and doing something wrong? or does PRI .4 screw the bootloader?
Click to expand...
Click to collapse
To clarify, in case someone stumbles across this and does this. Were you Rooted before running ##786#? Did you run Unrevoked forever? What method did you do to re-root your phone?
Thanks
I was full rooted prior by toasts method of Root & nand unlock.
I was on Hboot V .76
I never did unrEVOked Forever.
I did ##786# to update PRI from .36 to .4
Hboot changed to .79
I could no longer ADB.( i dont know if its a result of .79 or a coincidence)
I was looking through the forums, a post suggested redoing the 2nd part of Toasts Root(nandroid unlock) That just fubared my phone even more ha ha.
So I re did Step one, then Step two of Toast. However that did not work. I eneded up using this thread http://forum.xda-developers.com/showthread.php?t=741294 then manualy updating Superuser.apk from here http://forum.xda-developers.com/showthread.php?t=682828
Hope that helps!
ChiefSpoonS said:
I was full rooted prior by toasts method of Root & nand unlock.
I was on Hboot V .76
I never did unrEVOked Forever.
I did ##786# to update PRI from .36 to .4
Hboot changed to .79
I could no longer ADB.( i dont know if its a result of .79 or a coincidence)
I was looking through the forums, a post suggested redoing the 2nd part of Toasts Root(nandroid unlock) That just fubared my phone even more ha ha.
So I re did Step one, then Step two of Toast. However that did not work. I eneded up using this thread http://forum.xda-developers.com/showthread.php?t=741294 then manualy updating Superuser.apk from here http://forum.xda-developers.com/showthread.php?t=682828
Hope that helps!
Click to expand...
Click to collapse
Hmmm... This is really odd. I am wondering how many other people this has happened to. I did the same update, ##786# without having unrevoked forever (something about putting my phone in a state that CAN NOT be returned to stock). I still have 0.76 hboot. I'm wondering if it is due to the ROM you were on. I know people are getting mixed results with different ROM's. Actully some are getting mixed results on the SAME roms. I had to run the update twice, for some it worked first try, others had to do it 5-10-20 times to work...
I'm waiting for this for a couple of days. Till its ironed out.
Sent from my PC36100 using XDA App
Ok, so this is a big problem for me. I recently got a new evo (little bro broke screen, so i got a replacement) and i instantly tried to root it. I am on hardware 0003 with hboot .79 running version 1.47. As you can see, I have gotten to 2.1 successfully. I started at 3.29 so this was pretty easy.
But now I have a huge problem. My hboot won't let me flash the pc.zips. I name them correctly, and it loads the zip, and even checks it, but just dumps me back at the menu with no error warning or anything. This is a really big problem. I can't even get back to froyo now.
So I downgraded to hb .79 software 1.47 using the rage against the cage and flashing misc method before the pc.zip. This took a few tries for the zip to update as well.
Then i used the flash exploit to try to root eclair. Everything went great. But my pc goes to checking, and then dumps me back at the menu.
Plz help me
Dk
I had the same issue hboot would search but than drop me back at main menu. This pc36 file woorked for me found it in another post let me know if it works.
View attachment PC36IMG.zip
jdh10475 said:
I had the same issue hboot would search but than drop me back at main menu. This pc36 file woorked for me found it in another post let me know if it works.
View attachment 438729
Click to expand...
Click to collapse
Thanks jdh. I. Will test in the morning. Could you tell me what is in the pc36img.zip? This would be very helpful for me to know what the he'll I am flashing. Does this fox the problem for pc.zips after it, or what? Any more info?
Did you make sure you have plenty of space on your SD card and that you still have S=OFF? I would also try the eng bootloader (.76) since it comes with S=OFF by default
I do have space, but I don't have s-off. I have just run the flash exploit though, so I think that gives me a chance to flash the eng build and then turn s-off. Correct me if I am wrong. I am just trying to root. Again, s is still on
dkdude36 said:
I do have space, but I don't have s-off. I have just run the flash exploit though, so I think that gives me a chance to flash the eng build and then turn s-off. Correct me if I am wrong. I am just trying to root. Again, s is still on
Click to expand...
Click to collapse
The flash exploit still works? I figured they would have fixed that by now, thats a pretty big security hole lol
ya, if you can get the # root prompt you should be able to flash the mtd-eng and then Toast's pc36img. Once you have root his part 2 guide should tell you how to do everything.
Edit: ignore that about the flash exploit, I forgot you said you downgraded lol
Hah ya I think that might be the problem. I did downgrade to the1.47, but I think something is broke. I will wipe, and do netarchy's method of deleting two files in 1.47 and then doing toasts part two (wow, fail htc. Only two files?) and report back. I will also check md5 which I have not yet done.
HBoot 76.200
not working. i am starting to get sort of annoyed. i can't even get back to froyo.
i am going to pm steelh. if he doesnt help, i am going to go to toast. unless anybody has any other suggestions of people i should ask before going straight to the root master
Invoke the OTA updates. About 3 times until you get to 3.29.
(Assuming s-off)
Then everything will work and you can flash whatever you want.
as i said before, s is not off. i am trying to get it off. it is much harder to do in 3.29, so i tried in 1.47 and i am stuck now. no otas. i am giving it another shot right now. thanks for trying
You need to downgrade farther. Go to 1.32
Make sure the s-off file is on your sdcard before you do so. You will lose USB until you upgrade back to 3.29
thanks for the suggestion. where can i find a 1.32 pc36im.zip so i can try it? i'm not even sure if it will accept it. could you post a link? i have rooted 1.32 before, so this should be a breeze
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?
Ok, I rooted with unrevoked a long time ago. Broke my screen and need to unroot. I followed the unroot unrevoked guide as closely as I could, but the rom in the link was not found. So I downloaded a different ruu.zip of factory rom, don't ask me which one, because I can't find the link anymore, but currently here is where I stand. Hboot kept saying that the img was older or something, and wouldn't flash. So I did a stupid thing and pushed the zip with clockwork. So now I'm running s-on with clockwork recovery and a stock unrooted rom. So, I tried the next thing, downloaded an 3.7 ruu .exe and tried to run that from windows, but it gives me an hboot usb connection error f*ucking **** 1 thing after another.
This is the unrooting guide I used http://forum.xda-developers.com/showthread.php?t=780141
I got s-on, and tried that pc36img but it wouldn't work, originally. Before I went on to screw things up.
I've been at this for hours, something that should have taken 10 minutes if I wasn't an idiot, or bad links, or what ever. Can someone tell me or point me in the right direction, of what to do here, preferably not to a 2 year old thread with outdated links? What should I do?`
A List of android stock RUU zips with radio, pri, recovery all in one would be great, but I give up on trying to find that, its buried or does not exist.
I found this list http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs but its just the rom not everything.
So here is where my phone stands
S-ON
Hboot .97
Clockwork recovery 2.5.0.7<<<<<<
Android version 2.2.2
Build number 4.54
PRI 1.90_003
Angrychair420 here is a stock RUU that I know is good you should be able to run the RUU from windows.
http://geekfor.me/evo/ruu/evo_ruu_1326511/
thanks, that says its img version 1.32.651.1, assume thats safe to use. I assume thats andoid 3.26 which is what came on my phone. Ugh I'm in over my head. Why did my screen have to break, i was totally happy with CM7 and everything the way it was.
what if I wipe my data and caches, remove SD card, put on a PC36IMG.zip and boot the phone into hboot, will it still give me the older version error?
edit: the link you gave me gives me the same error as the other ruu.exe:
The ROM Update Utility cannot update your android phone
Please get the correct ROM Update Utility and try again
Possibly but I did have to return mine for repair and I know that using it as a .exe file trough windows I had no problem. Not sure about making it into a PC36IMG.zip file though I have not tried it that way.
Angrychair420 said:
thanks, that says its img version 1.32.651.1, assume thats safe to use. I assume thats andoid 3.26 which is what came on my phone. Ugh I'm in over my head. Why did my screen have to break, i was totally happy with CM7 and everything the way it was.
what if I wipe my data and caches, remove SD card, put on a PC36IMG.zip and boot the phone into hboot, will it still give me the older version error?
Click to expand...
Click to collapse
It might. There are 3 PC36IMG files in the first "My Links" link in my signature. You can try them in order if you'd like, if you get the "main version is older" message, but if the first two don't work, the last one definitely will.
Thanks cpt, about to give them a try. Sigh man, this is frustratingly harder than rooting :-D If it was as easy as doing the s-on and copy the pc36img.zip to the root of sd and booting into hboot and DONE, I would of been having a much better day.
Try the latest RUUs from this link man:
http://www.filefactory.com/f/acf0b850b0f70d7b/
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
You can also try this
http://www.goodandevo.net/2011/03/how-to-unroot-your-htc-evo-4g.html
I appreciate the help guys. I will keep posted. You know how much it sucks to slide on a touchscreen thats broken? lol
partyman1971 said:
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
Click to expand...
Click to collapse
Yes, that's the first RUU.exe I tried. said this RUU can't update
ok i got a pc36img.zip installing from hboot right now.
edit:dang main version is older error. Trying a wipe then hboot then pc36img.zip
Same outcome, main version is older.
partyman1971 said:
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
You can also try this
http://www.goodandevo.net/2011/03/how-to-unroot-your-htc-evo-4g.html
Click to expand...
Click to collapse
yes, they are basically the same method I used in my OP from xda forums.
On to captain_throwbacks second ruu.
Just to make sure, this all isn't in vain, and make you all hate me, after applying one of these successfully, my recovery should go back to factory and no longer be clockwork, right? or wrong, because I'm starting to think I am. But won't taking your device in for service with clockwork be a dead giveaway that it was rooted.
I think I'm just going to go get a new phone for a $100 deductible at this point. and replace the screen my self on my old one and keep it as a backup/test device. Thanks for all the help, but I am surrendering :-D hopefully I can reroot this thing again with unrevoked, since my hboot is still .97 and fix the screen my self.
It generally doesn't matter if its rooted. I've never unrooted since launch day. And I've had 3 screen replacements, 3 speaker rwolacements , a bezel replaced, and camera lens cover replaced (last time, I dropped it off with ICS), about to go get my 4th screen (just cracked it again lol).
Sorry for your experience/frustration.
sent from AOKP heaven
well last stupid question i promise, since i still have clockwork isntalled, i can just restore my CM7 backup, but how do i get s-off back, re unrevoked it i assume?
If your'e worried about the warranty thing, just flash a stock rooted rom, or use a phone repair service. i see three or four repair places on craigslist (granted, that you live in a large city).
yeah no worries. Got it back to S-OFF, and CM7 back on it, just going to fix the screen my self, ordered one for $15.
thread can be locked, deleted, or what ever.
Seriously. Dude, isn't there a sprint store near you?. Just take it in. Put a stockish rom on it if you're that worried about it. They should replace it for free.
sent from AOKP heaven