yashsingh1/xdaforums huggingface dataset:
[Off-topic] Zardos66:
How about some bacon Vodka
[Off-topic] b0dge:
I like bacon Coke...
[Off-topic] b0dge:
Also...
[Off-topic] captainstu72:
mmm bacon.

I was annoyed yesterday - I was going to make bacon sandwhiches for lunch - the bacon had gone green :(
[Off-topic] Shum97:
Even Mojo is hoping to get a taste of the latest bacon product. It is Baconnaise.

What could be greater than bacon flavored mayonnaise.
[Off-topic] M_T_M:
Me and Bacon had a great weekend...we went to San Antonio...where I ate him :eek:
[Off-topic] backslide311:
mmmmmm, Bacon is meat candy :)
[Off-topic] backslide311:
http://bacontoday.com/bacon-flavored-diet-coke/:eek:
[Off-topic] JimJam707:
http://bacontoday.com/the-people-of-canada-choose-bacon-over-sex/

:D Dem canadians.
[Off-topic] MacaronyMax:
ahahaha :D ^^^ im part canadian :D id much rather the other thing :D :D

because

i like-ish bacon

:p
[Off-topic] chopper the dog:
Had bacon and garlic pizza last night. mmmmmmmmmmmmmmmmmm.

long live bacon.

good day.
[Off-topic] htc fan89:
Bacon goes on anything and still taste awesome

Sent from my X10a
[Off-topic] kareeem:
Turkey bacon is alright (can't eat pig bacon) :)
[Off-topic] NYCHitman1:
I LOVE BACON!! :p
[EVO 4G Android Development] l33tlinuxh4x0r:
NONE of THIS SEEMS TO BE WORKING :(

IF YOU ARE ROOTING FROM STOCK YOU CAN KEEP YOUR PRI!!! USE THE FOLLOWING PC36IMG.zip WHEN DOING PART 2 AND YOU WILL BE GOOD TO GO!!! Confirmed working! USE my mtd-img and flash away,

NEED MIRRORS

http://www.mediafire.com/?k7jdy6botn13xzg

NEED MIRRORS

http://www.mediafire.com/?z957ozf9sb44at5 newer and updated to 2.2

We are still working on extracting the PRI and putting it on previously rooted phones.

OLD:

I found it here... http://xdaforums.com/showthread.php?t=746705

I'm working on making an update.zip it is in the nv.img file. Currently I am working on making a zip to restore 1.34_003 from calkulins cosmetic fix so i can test my zip to update the PRI.

HOPE that this helps everyone that wants the new PRI just give me time or if you are a better hacker than me just do it and upload it (give me credit) or post in this thread.

Below is a restore for calkulins cosmetic PRI hack. Now to work on flashing 1.40_003!
[EVO 4G Android Development] frettfreak:
What would having an updated PRI give us?
[EVO 4G Android Development] Beejis:
Alright, good work! Can't wait till you get this going!
[EVO 4G Android Development] l33tlinuxh4x0r:
Supposedly better reception but nobody really knows. For me it will just be that I have EVERYTHING up to date.
[EVO 4G Android Development] Noxious Ninja:
If this is legit, I'm finally going to root my phone. Fingers crossed...
[EVO 4G Android Development] l33tlinuxh4x0r:
I am working on it... Supposedly nobody has been able to flash a nv.img file yet but I am going to try to extract the PRI from it. I have a couple of things that I am going to try.
[EVO 4G Android Development] davidlightle:
There are some other threads about this as well, and I'm interested in having this resolved, too, as it's one of those last things that bugs me about being rooted.

The NV.img I believe stands for non-volatile, so the settings that don't get wiped through an OTA or a factory reset.

However, an NV.img has been provided with several of the RUUs, if not all of them. I'm not sure why the 1.40 wouldn't have come back if this is all that was necessary.

In addition, it appears that the only time the PRI changed (from 1.40 to 1.34) was when an rcdata.img was present which has led to the thought that rcdata is at least part of the solution.

The next complicated part is in how to get these images (nv.img and rcdata.img) in and out of the phone. There could be a way to pull them through fastboot, as I know wimax was able to be done that way, but I don't know that nv or rcdata are partitions themselves. The listing I have seen shows rcdata (and maybe even nv) as an "other" type with no size.
[EVO 4G Android Development] nugzo:
Is it that important that you would wait to root for an updated PRI? I dont understand the reasoning... Do you know something we dont about the PRI? Thanks.
[EVO 4G Android Development] AssassinsLament:
NV.img doesn't change the PRI. In fact, it's in the RCDATA.img, that is why we haven't been able to fix the PRI. None of the updates have included an RCDATA.img.
[EVO 4G Android Development] Sporkman:
this ok to flash on CM6 ?
[EVO 4G Android Development] Noxious Ninja:
Nah, I am just somewhat paranoid. :/
[EVO 4G Android Development] davidlightle:
Just as a note, the PRI version string can be found in the nv.img; but as Assassin said, it is tied to the rcdata somehow.

Edit: In fact, I wonder if rcdata doesn't stand for "radio control data" since the PRI is related to control of the radio somewhat.
[EVO 4G Android Development] nYdGeo:
I'm not able to be of assistance in developing this fix for the PRI issue that a ton of folks with rooted Evo's are having, but am very excited to learn that someone may have found a way to get that info out of the nv.img and create an update.zip file to fix it.

As someone that remembers PRI from back in the ISDN days, I know that its not going to make or break anyone's radio, but I do believe that having the correct PRI information that is optimized for the radio in use and the (in this case CDMA) network configuration could have obvious effects on the overall network performance.

I tried everything I knew of to access that nv.img file in the hopes of doing just what you are attempting, but could not. Even if I had, this environment is outside of my expertise.

I wish you the best of luck, and look forward to flashing that zip!
[EVO 4G Android Development] Doward:
Surely one of the updates must have - otherwise, how have the usual non-rooters gotten updated to 1.40 PRI?
[EVO 4G Android Development] davidlightle:
Actually stock phones come with 1.40 PRI and the NAND-unlock moves it to 1.34.
[EVO 4G Android Development] Doward:
Ahhh... that makes a lot more sense, then.

And also explains why flashing any of the stock RUUs doesn't change your PRI.
[EVO 4G Android Development] nYdGeo:
Correct. Almost every NAND unlock root process uses an image based on the leaked Eris image, which is said to be where that older PRI comes from.
[EVO 4G Android Development] nukedukem:
I think 1.40 comes with every phone from the factory and the reason there is no update with that PRI is because that RUU was never leaked, it was all done internally at HTC. I'm not entirely sure about that though, just my understanding.
[EVO 4G Android Development] l33tlinuxh4x0r:
well if it is true that we can't get the PRI from nv.img then sorry guys for the false hope. :(
[EVO 4G Android Development] rjmjr69:
Dont give up I didnt see anyone say for sure they even know where it is. KEep going with your work
[EVO 4G Android Development] bigupurself7:
Don't download something unless you know what it does. This does not do anything yet!
[EVO 4G Android Development] YoungAceAtlanta:
Ok now im confuse.. so PRI 1.40 is the PRI we all suppose to be on and not 1.34?
[EVO 4G Android Development] Sporkman:
duh that's why i was asking lol
[EVO 4G Android Development] l33tlinuxh4x0r:
Sounds like it is in the rcdata.img which is not in any of the updates except for the root update. However I do have another non rooted phone that I could, should be able to dump the pri from. I'm thinking a full DUMP of everything but I will have to wait till tomorrow when my friend brings it back.
[EVO 4G Android Development] sgt. slaughter:
1.40 is the current up to date PRI while 1.34 is older one that you get stuck with when you root. there are many threads that discuss this and what it is supposed to do.

The PRI is the Primary Rate Interface or (Product Release Instruction), which is a telecommunication standard for carrying multiple voice and data transmission between a network and a user. It contains the settings for different configuration items on the phone that can be network specific, but not necessarily subscription specific (standard CDMA channels, slot cycle index, default PRL). It also contains information that works hand in hand with the PRL, in that the PRL is the "Master List" of preferred roaming carrier's towers and the PRI helps determine, along with geographical information, the priority of any tower that you will roam on at a given time in any given area - kind of like a subset of the PRL.
[EVO 4G Android Development] sgt. slaughter:
How do you plan on doing a full dump of the phone exactly? I was under the impression that no one had figured out how to do that fully yet?
[EVO 4G Android Development] l33tlinuxh4x0r:
Not sure yet a lot of googleing ahead and a bunch of trial and error. I'm thinking that maybe a dd of / or a cp of / or something that will grab all of the dev partitions. I'm hoping that the PRI is loaded into ram or a dev point somewhere.
[EVO 4G Android Development] n1gh7m4r3:
Not to dampen your hopes, but everything i have read is that these files write to non volatile memory inside the radio
[EVO 4G Android Development] l33tlinuxh4x0r:
if this is so if we dump the radio wouldn't we get the PRI with it???
[EVO 4G Android Development] n1gh7m4r3:
sounds reasonable but idk, i do know some of the top devs have been looking into it such as toast, omj, joeykrim, and majrep, so i am sure they have thought of it, just not sure they have figured out how to do so, the current thinking is that we need the rcdata.img file that works with the new nv.img file that we do have, toast has an idea, that he posted in the irc channell, a few of us might try it, but possible brick out of the deal, as well as i have emailed htc, waiting to see what there response on the issue will be
[EVO 4G Android Development] sgt. slaughter:
just for those that do not look around much before posting stuff you should check out

http://xdaforums.com/showthread.php?t=694034&page=11

some info on what has been tried and thought of, and also that a user did unrevoked, and then simpleroot and somehow still has the 1.4pri. waiting to hear back form them currently though to answer one of the questions from joeykrim
[EVO 4G Android Development] l33tlinuxh4x0r:
I'm going to take eng-PC36IMG.zip and remove the PRI then flash it after that I am going to do a ##786# and format and hopefully it blows out the PRI wish me luck! Also Maybe I could make an updated version that is already 2.2 once rooted.
[EVO 4G Android Development] posguy99:
No, none of the Evo's unlocks have anything to do with the Eris. The older PRI comes from the engineering ROM for the Evo that was leaked prior to the phone's release.
[EVO 4G Android Development] infamousjax:
standing behind this project 100%, let know how if you need a labrat.

fingers crossed & subscribed.
[EVO 4G Android Development] l33tlinuxh4x0r:
I found a way to root a phone and not downgrade the PRI!!! just delete the PRI, rcdata.img from the PC36IMG.zip and you should be good to go. Be sure to check every PC36IMG.zip that you flash.

For clarification it has to be an unrooted phone.
[EVO 4G Android Development] Philosuffer:
So, what do we do exactly?

Factory reset? Then remove rcdata.img from PC36IMG's and do the whole root and NAND unlock process again?
[EVO 4G Android Development] sgt. slaughter:
Not doubting you got something here, just surprised this hasn't been figured out earlier really if thats all it took.

Will be nice to pull the PRI out now that your rooted with 1.4 and make it to where those that are already rooted can fix theres from 1.34
[EVO 4G Android Development] sgt. slaughter:
pretty sure if your already rooted your stuck with 1.34 less someone can extract 1.40. Even doing a factory reset doesn't restore your pri back.
[EVO 4G Android Development] zonyl:
If you have a stock 2.1 phone. If you have already unlocked the NAND it appears that the original 1.4 was overwritten and thus you wouldnt be able to dump it. I believe they are going to try and find someone with a 2.1 phone and remove that file and have them dump it for the rest of us to use with NAND already unlocked.
[EVO 4G Android Development] l33tlinuxh4x0r:
Exactly But if someone can root a phone with 1.40_003 then we can dump the PRI and use that to update all of ours.
[EVO 4G Android Development] sgt. slaughter:
Well snap I thought you were talking earlier like you just did this to yours. Didn't know we were still talking theory here.
[EVO 4G Android Development] wfrandy:
Have you actually tried this, or is this just speculation?

Isn't the engineering PC36IMG.zip signed, my understanding was that if you edited it then it would no longer flash properly. Could possibly even brick the phone.

If you haven't actually proven this works it would be a good idea to say so in your post.
[EVO 4G Android Development] davidlightle:
I believe you're right on that. I sent a message to Toast for a process similar to l33tlinuxh4x0r that I believe could work, but hasn't been tested.

My process is to use a custom recovery to flash the eng hboot, but NOT the rcdata.img basically. This should achieve the PRI 1.40 with eng HBOOT, full NAND-unlock with root, unless I missed something. Then we could grab the rcdata from the phone to upgrade others'.
[EVO 4G Android Development] smw6180:
Folks, it says '[WIP]'. That means it's a work in progress.
[EVO 4G Android Development] wfrandy:
True, but my point is if someone says "I found a way to root a phone and not downgrade the PRI!!!" without mentioning it is just a theory, or work in progress, someone may take it literally and brick their phone. Don't get me wrong, I am in full support of the search for a fix, just saying we should be careful because not everyone will see the (WIP).
[EVO 4G Android Development] smw6180:
True enough. But I'll counter with, 'people shouldn't mess with things they don't understand'. ;)
[EVO 4G Android Development] sgt. slaughter:
Yeah but posting that you found a way to do something WITHOUT any question mark sounding like you solved the problem is wrong.

Unless you actually preform the theory/speculation thought yourself then it should be noted so in any post.
[EVO 4G Android Development] sgt. slaughter:
90% ppl that root there phones have no idea how the root happens on the inside.

Even with the WIP in the title, anyone that says something thats speculation or theory should be sure make sure it comes across as such so other dev's or members do not mistake it for reality/fact.
[EVO 4G Android Development] l33tlinuxh4x0r:
I thought that It was signed too but all I did was extract it, delete the file and recompress it with zip on linux. To my suprise it worked. Now I just need a test subject to flash it to a Non rooted rootable phone.
[EVO 4G Android Development] sgt. slaughter:
In that case CALLING ALL TEST SUBJECTS......
[EVO 4G Android Development] BAleR:
Man i hope we get this working my 3g sucks my phone is rooted w/N.U. or ells i would try it
[EVO 4G Android Development] pongoface:
I am sure that i am a dummy but does anyone have the sprint 1.47 update downloaded to the phone. Not the shipped rom version. So if i sent my phone back to 1.36 rom then used the official 1. 47 upgrade to phone on the phone itself. Wouldn't that give me the 1.40 pri since that is how it was flashed originally to the phone. Then you could try the fix by leavingout the rcdata. Just a thought but i am probably wrong.
[EVO 4G Android Development] l33tlinuxh4x0r:
There is currently no way to restore the PRI until someone dumps it. So downgrading and then upgrading will not work :(
[EVO 4G Android Development] infamousjax:
We need a test phone that's currently unrooted correct?
[EVO 4G Android Development] sk63:
That's because the engineering hboot doesn't check for keys the same way the release version does, at least I think that's the case.
[EVO 4G Android Development] l33tlinuxh4x0r:
If that is true then all we need to do is get someone with the key to sign it. I know that one of the other devs has to have it.
[EVO 4G Android Development] sk63:
Someone has the release keys? That's kinda huge if they since would mean that they, in terms of how it would appear to any phone, would be Sprint and could release rooted roms without needing to find an exploit.
[EVO 4G Android Development] wfrandy:
That is the problem, from what I have gathered, no one has HTC's signing key's.
[EVO 4G Android Development] pongoface:
didnt i read elsewhere in another thread of a member with his phone and his wifes phone that did the unrevoked 3 then simple root and kept his 1.40pri. Someone that knows him should get him to dump his pri from his phone.
[EVO 4G Android Development] Geniusdog254:
I doubt it. It's an HTC private key. If it leaked then people could do whatever they wanted to any HTC bootloader that used it
[EVO 4G Android Development] l33tlinuxh4x0r:
http://www.mediafire.com/?k7jdy6botn13xzg <-- that is my pc36img.zip
[EVO 4G Android Development] Tilde88:
Which is rooted with 1.4 pri?

/wish
[EVO 4G Android Development] pongoface:
Before I try, Now doesn't the stock shipped rom 1.47 include the updated pri and after I return the phone to stock, I know I will still have 1.34pri. But if I do ##786# then hit menu then reset won't I have 1.40pri. Has anyone tried this after returning their phone to stock?
[EVO 4G Android Development] sgt. slaughter:
Nope you'll be on 1.34 still im pretty sure. Since theres no firmware out there with the rcdata.img file containing 1.40pri on it. if im not mistaken the rcdata.img file is what downgraded the pri upon full root and since pri hasn't been upgraded since release of phone no firmware has a new rcdata.img file and no way to return pri back even if full reset.
[EVO 4G Android Development] pongoface:
I am just asking because I was one of the newbies/fools that took the 1.47 ota and lost root. My pri before the june 28th update was 1.34 and after the update was 1.40. So my pri must have been flashed/changed during that update. That is why I asked earlier in the thread if anyone had the official 1.47 ota download from sprint/htc not the exe one. I am beating a dead horse lol. I am underthinking the whole pri issue is all. Many of you devs are much smarter than I when it comes to this. Just throwing in some think tank crap obviously lol.

Edit: I know had 1.40_003 after the 1.47 sprint ota update because when I rerooted the second time I was like wtf my pri changed back to 1.34_003. This is how I justified to myself about losing root. Well at least I have the better pri now lol.
[EVO 4G Android Development] pongoface:
LOL and to top it off 3 days ago I returned my wifes 1.47 unrooted 1.40pri phone back to Best Buy because she wants the #@$@#$ epic 4g. I could have been some help here and a test dummy. Darn it!
[EVO 4G Android Development] sgt. slaughter:
Well thats news to me that they changed the PRI with the OTA update. If thats the case then it should be in the .exe somewhere for sure.
[EVO 4G Android Development] l33tlinuxh4x0r:
my pc36img just does not flash a pri so whatever pri you have you keep.
[EVO 4G Android Development] sgt. slaughter:
I coulda sworn the sprint update app the actual .exe was floating around here somewhere for the OTA release. If the OTA did update the PRI then having the actual one instead of the RUU would have the PRI file in it or whatever is in it that updates the PRI at the least bit.
[EVO 4G Android Development] jpwhre:
i know this may be a stupid question, but coming from a wm platform to android I have to ask. I know it may be a catch 22 idea as I am just starting to learn android and is not as simple as making a cab with a file and an provxml but I know that an unlocked wm can have the stock rom dumped with qpst and even pull the prl file from that, is there a way to do that with android that doesn't require root which changes the pri to 1.34? an other thought is, has a full ruu been posted/leaked of a stock rom that would contain the img with the pri in it that could be ported to the root files for rooting to give us the pri1.40?
[EVO 4G Android Development] Doward:
I can check this tomorrow - I've got the original RUU exe of the .32 release, then I can do the OTA to .47 and check the PRI version.

If the OTA does have the PRI update, I'll report back.

It'll be tomorrow before I can, though, as I need the phone tonight and I'm heading out with some women to party it up tonight!
[EVO 4G Android Development] davidlightle:
I've checked all 4 OTA RUUs (both 1.32, the 1.47, and the 2.2) and none contain an rcdata.img. The only thing that has rcdata.img is the eng PC36IMG.zip for nand-unlock.

So the only thing you need from eng PC36IMG.zip is the eng HBoot, NOT the rcdata.img.
[EVO 4G Android Development] l33tlinuxh4x0r:
Good News everyone:

People that are rooting from stock can keep their PRI. Just use my PC36IMG.zip

It has been confirmed.
[EVO 4G Android Development] pongoface:
Dont bother I do not think that the pri is in the ota now.
[EVO 4G Android Development] l33tlinuxh4x0r:
The stock pri 1.40_003 is currently only available stock. We are working on getting it back.
[EVO 4G Android Development] adeyo:
what?? how?? ...with full root? my friend has never fully rooted, just unrevoked and then unrevoked 2 (maybe 3?) ...needless to say, he has been flashing roms and has 1.40...as do i, but i haven't rooted yet. (don't have the time, waiting for something that looks good to me to do it).

so, how does one do this and how have you confirmed it??

thanks for all your work on this, btw!!
[EVO 4G Android Development] pongoface:
Sweet, so Are you going to get the people that confirmed this for you to give their dump so we can have the new pri in a new pc36img.zip hehe
[EVO 4G Android Development] l33tlinuxh4x0r:
That is the next step we just need to figure out how to dump it.
[EVO 4G Android Development] c0t0d0s2:
Dumb question: It's not in any of the images that nandroid-mobile.sh grabs, is it? IS it somewhere you could grab in mtd6?

I figured it was worth a shot asking at least.
[EVO 4G Android Development] l33tlinuxh4x0r:
Looks like none of my work is successful oh well it was worth a try but we do have hope http://xdaforums.com/showthread.php?p=7558702&posted=1#post7558702 says that they have it working but i cant get it to work. :(
[EVO 4G Android Development] ranmasaotome510:
yea to bad i couldn't understand a word he said :). hopefully he either gives a step by step. or someone translates what he said.
[EVO 4G Android Development] Noxious Ninja:
When you say that none of it is working, does that include the new PC36IMG.zip? Or is that part at least working? Your current wording in the first post of the thread is somewhat confusing.
[EVO 4G Android Development] l33tlinuxh4x0r:
it works but for some reason you dont get nand unlocked.
[EVO 4G Android Development] sirsycho:
Sorry but I'm new here, just got my EVO a week ago and it's my first android but I've been doing A LOT of reading.

As I understand it, you aren't going to be able to flash your UNSIGNED PC36IMG. This is because you are still running the 0.79.0000 HBOOT. To flash any ROM you want you need the ENG HBOOT and you only get that with Toastcfh's Part 2 PC36IMG (which includes the rcdata.img).

I could be way off here, as I said, I'm new... but I don't see how you can save your PRI using what we have available to us now.
[EVO 4G Android Development] AssassinsLament:
First off, if you change the PC36IMG.zip in any way, you lose the HTC signature. Thus you wouldn't be able to have the bootloader flash the PC36IMG.zip file. The reason you can flash whitlack's PC36IMG.zip file is because by flashing Toastcfh's PC36IMG.zip, that unlocks the NAND and it allows you to flash non HTC PC36IMG.zip's. So there is no way to remove the rcdata.img from toast's PC36IMG.zip without making HTC's signature invalid.
[EVO 4G Android Development] kyleblakepeters:
Mind the noobish question, but in regards to the signed key...could it be bruteforced?
[EVO 4G Android Development] posguy99:
Sure. How many lifetimes do you have?
[EVO 4G Android Development] kyleblakepeters:
Yea, I just saw the size of the key, and that won't be happening.
[EVO 4G Android Development] SleepyS40:
Is it at all possible to do a system dump on a non rooted phone?

Swyped from your backyard
[EVO 4G Android Development] n1gh7m4r3:
Lols OCD much? .... Of course thats why i need it too ....