Hey gang, I've been reading through the sticky on the PRI issue. I was running Damageless v2 for a bit, now trying out the latest 2.1 Eris-based Fresh ROM. The PRI version shows 2.11_002. My question is this... what problems are people having with these Eris based PRI's? My phone seems to be just fine, or am I missing something that should be working better? I read mention of SprintTV not working in the thread, but I don't use that app (and it's not even on Fresh). What do I gain by fixing the PRI? Thanks guys.
Dave
When the official Sprint update comes and you get a new ROM off of that, you will have problems with it not identifying the network correctly.
You are better of doing it. I would say that you NEED to. It should be essential.
Gotcha
Thanks for the reply to clear that up. Definitely don't want the phone to break on the official updated ROM.
I intentionall broke my PRI to keep MNS working. Resetting put me back to 170, which doesn't work with it. I've noticed no problems using the 2.11_002 PRI.
Not the same thing but a similar question. My PRI is currently 1.68_003, should I attempt to get my PRI updated to 2.10_003 & would I accomplish this via the way Avalaunch directed here?
gu1dry said:
Not the same thing but a similar question. My PRI is currently 1.68_003, should I attempt to get my PRI updated to 2.10_003 & would I accomplish this via the way Avalaunch directed here?
Click to expand...
Click to collapse
As I understand, there's only one person who has the 2.10_003 PRI.
Related
Hi guys im still very new to flashing and ive googled it a few times and couldnt come up with anything. So here goes:
I flashed to adp 1.5 the newest one out and did the radio update first etc. Then after some reading realized it doesnt have myfaves. So i need to go back to the JF Rc33 untill cupcake officially is modded for the RC version.
I was worried about the radio update, if i do a wipe and then update to 1.42 (or 1.43 i cant remember) will it screw up anything since i did the radio update to upgrade to adp 1.5.
Sorry if im not making sense let me know and ill do my best to explain better?!?!
really do search carefully before you post. somebody has posted a very detailed downgrade guide on the second/third page.
i think the new radio works with old builds. even if the radio is not compatible, you won't get a bricked phone anyway.
That and not having the [email protected] 5 app on your phone is not going to stop you from calling those 5 people for free. I'm actually glade jf1.5 doesn't have it on there i could never stand it
Im sorry i read quite a few of the radio threads and googled most of the keywords i could. I'll take a look again so much info here i easily could have missed it.
I didnt know that those 5 people are regardless of the app. So if i wanted to change them do i just do it online at the tmobile website?
is there any danger then for using adp instead of the RC besides i guess some of the messaging apps arent there?
xenoaurora said:
I didnt know that those 5 people are regardless of the app. So if i wanted to change them do i just do it online at the tmobile website?
Click to expand...
Click to collapse
Yep.
xenoaurora said:
is there any danger then for using adp instead of the RC besides i guess some of the messaging apps arent there?
Click to expand...
Click to collapse
Nope.
now im just guessing through trial and error but i believe that if you go to the new damage rom then you WILL NOT be able to go back to any roms that will change the PRI because i and others have been noticing that when getting the damage rom and we dont like it and want to wait for a faster stable version we try to go to the previous version and it freezes on boot screen, and in fact i just tried this with a few eris build that have been reported to change PRI and even the modded version of damage and that's what my phone has been doing any one else try and notice this or can confirm this?
rulyskull said:
now im just guessing through trial and error but i believe that if you go to the new damage rom then you WILL NOT be able to go back to any roms that will change the PRI because i and myself have been noticing that when getting the damage rom and we dont like it and want to wait for a faster stable version we try to go to the previous version and it freezes on boot screen, and in fact i just tried this with a few eris build that have been reported to change PRI and even the modded version of damage and that's what my phone has been doing any one else try and notice this or can confirm this?
Click to expand...
Click to collapse
I have been on the new v2r2 and gone back to 1.5 and damagev1 2.1. My pri is the same. It changed last night but was able to get it back to the right one using the MSL fix.
rulyskull said:
...because i and myself have been noticing that when getting the damage rom and we dont like it...[/B]
Click to expand...
Click to collapse
Multiple personality much?
Wasney said:
Multiple personality much?
Click to expand...
Click to collapse
my bad meant others lol thanks for pointing that out
Last night when all the PRI issues popping up, I was a flashing fool trying to simulate what was going on!
And I can tell you that the only thing that affected it was the ERIS builds!
I should say it was the Eris build and user error!
You gotta wipe after everything, if ya did it do it again!
Have you read the sticky threads on how to fix the issue???
if not, do it...thanks!
redram38 said:
I have been on the new v2r2 and gone back to 1.5 and damagev1 2.1. My pri is the same. It changed last night but was able to get it back to the right one using the MSL fix.
Click to expand...
Click to collapse
you have? so this is probably a different error but does your phone have the with google on the back? because mine doesn't and i know that the with google has a higher sense version (by like .55) and they fixed some problems with the ones without with google when changing sense so what im thinking now is that its not the pri its something different and going to be a pain to find out
Roman G said:
Last night when all the PRI issues popping up, I was a flashing fool trying to simulate what was going on!
And I can tell you that the only thing that affected it was the ERIS builds!
I should say it was the Eris build and user error!
You gotta wipe after everything, if ya did it do it again!
Click to expand...
Click to collapse
see i did this at least 8 times and still has this issue
The cause of the change of the PRI is not Damages latest ROM.
I was one of those that had to get their MSL to reset the phone, but I went
and re flashed Damages latest and the PRI stayed good.
So I'm pretty sure is not his.
There is people testing around trying to find which was the ROM that caused
it, but not sure if they have found out yet.
Okay this is what I did!
I am rooted and running a stock sprint ROM, this morning I flash this damage 2.0, bluethooth audio still does not work, but everything else was working great though. I nandroid back to 1.5!
Fast forward to this evening and all the problems everyone else has, and damage new version, I figure I will flash again to try it out! Then everyone starts talking about the PRI, so I jump in and start flashing other ROMS to try to get a different PRI#(Mine is 1.70_003).
So I go to the eris leak and flash PRI, it is still the same, but I have unknown operator and no sprint on my lock screen. Just for ****s and giggles I decide to flash back to the newest damage build without a wipe and what do ya know!
Now I have unknown OP and my PRI has changed to 2.11_002!
So now I am going to wipe and try to flash the newest damage build and see if it changes back!
I am wondering somewhere along the way some of you did not wipe first before flashing all these ROMS!
So it seems not doing a wipe causes this to change and stick for some unknown reason!
I am now back to rooted but stock and I still am stuck with the same bad PRI 2.11_002.
That was lastnight!
So this morning I did the PRI fix and got back to 1.70_003, and downloaded the legend leak ROM, did a wipe and flashed and verified my PRI was 1.70_003, then I nandroided like I did before without a wipe back to stock with root and my PRI is the same, so it is without a doubt related to the ERIS leak, and I also think that not wiping first has something to do with it as well!
I KNOW WITHOUT A SHADOW OF A DOUBT THE ERIS LEAK CAUSES THIS!
AND THAT IS REALLY THE ONLY ONE THAT WOULD AS THE PROBLEM DID NOT POP UP UNTIL THIS CAME OUT!
rulyskull said:
you have? so this is probably a different error but does your phone have the with google on the back? because mine doesn't and i know that the with google has a higher sense version (by like .55) and they fixed some problems with the ones without with google when changing sense so what im thinking now is that its not the pri its something different and going to be a pain to find out
Click to expand...
Click to collapse
yes, it has with google, but I still changed to the bad PRI last night for some reason. I got back the right one using the fix and it has stayed there even though I have had 3 diff Roms on my phone today, one being the new Damage v2r2. I am on v1 right now due to needing apps2sd. The only thing I did diff last night was forgot to wipe when flashing from one rom to the next once. I somehow think that is part of the issue.
You also have to remember that alot of builds that came out after the Eris leak were for the most part based on or contained part of the Eris leak!
So even if it did not say Eris leak it prolly had aspects of it in!
Roman G, I dont know if you are aware of this yet, but only way to get your old PRI 1.70_003 is to get the MSL and do a phone reset.
Flashing a RUU or any other Rom won't do the job.
MjPayne said:
Roman G, I dont know if you are aware of this yet, but only way to get your old PRI 1.70_003 is to get the MSL and do a phone reset.
Flashing a RUU or any other Rom won't do the job.
Click to expand...
Click to collapse
I not sure if your aware of this yet, because obviously you have not read anything I have posted, but I have done this 4 times already!
Thanks for the advice though!
I went back to my nandroid backup after installing damage's rom and I still don't have protected apps in the market. At least one other person has reported this so I know it's not just me.
I tried running the RUU back to a stock 1.5, still no protected apps.
I tried the pri fix that everyone is talking about. Called Sprint to get my number and followed the steps. Everything seemed to work ok but still no protected apps.
Anybody got any ideas?
I am wondering if there will be any issues returning my phone to sprint with the flipz01 PRI and this thread seems the best place to ask.
trying to clean sand from under my screen I blew out the microphone and can not use voice. I used Flipz tool to flash back to a stock ROM, however I noticed today that for PRI it says Flipz01. Sprint has already ordered me a replacement phone, but when I do give this phone back is there any way Flipz PRI can come back and penalize me?
Thanks in advance!
How do you update the PRI to reflect the current version vs. Flipz_01.
Lappie2010 said:
How do you update the PRI to reflect the current version vs. Flipz_01.
Click to expand...
Click to collapse
From the FAQ if you haven't found the answer yet. There is a MSL thread in the general section now with a easy and legal way to get it.
http://forum.xda-developers.com/showpost.php?p=6006877
from what I was told flipz is just the 170 prl in disguise. If you want the 2 something prl you have to flash damge's beta 5 rom and it will change it to that. Then nandroid back to your old rom you were using. I did that recently and it worked. I changed it from the 170 to the 2 something so I can tether.
doeboy1984 said:
from what I was told flipz is just the 170 prl in disguise. If you want the 2 something prl you have to flash damge's beta 5 rom and it will change it to that. Then nandroid back to your old rom you were using. I did that recently and it worked. I changed it from the 170 to the 2 something so I can tether.
Click to expand...
Click to collapse
But doing this method might take some things out of the market and not all sprint apps with work. Tv and navigation do work though.
If you want sprints newest PRI then you have to flash the newest RUU. But you will lose root.
What is the number for the Sprint RUU PRI?
JusticeAA said:
From the FAQ if you haven't found the answer yet. There is a MSL thread in the general section now with a easy and legal way to get it.
http://forum.xda-developers.com/showpost.php?p=6006877
Click to expand...
Click to collapse
I did this yesterday and while it removes flipz custom pri, it does not upgrade the pri to the current one. I have the 1.70 pri and im not about to run the RUU just to upgrade it.
Lappie2010 said:
How do you update the PRI to reflect the current version vs. Flipz_01.
Click to expand...
Click to collapse
make a nandroid back up and go back to a 1.5 rom run pri update and then nandroid back to the 2.1 rom. (might be able to pri update from 2.1 I haven't tried it)
I have noticed that most of the roms put out lately claim they are based on the official ruu yet many people still have the audio loss problem and when they bite the bullet and install the real official ruu from sprint their problem disappears.
If all these so called "official 2.1" roms were really official would the audio loss problem not have disappeared in them too?
Also, if they are truly official why does the thread on "2.1 rooting status" even exist?
cali310 said:
I have noticed that most of the roms put out lately claim they are based on the official ruu yet many people still have the audio loss problem and when they bite the bullet and install the real official ruu from sprint their problem disappears.
If all these so called "official 2.1" roms were really official would the audio loss problem not have disappeared in them too?
Also, if they are truly official why does the thread on "2.1 rooting status" even exist?
Click to expand...
Click to collapse
In the 2.1 RUU, there is a ROM file, just like every other ROM you've ever flashed. The RUU updated the HBOOT, so if you run it, it updates a lot more than just a normal ROM flash does. The 2.1 rooting status thread exists for the people who ran the actual 2.1 RUU. It's an HBOOT root status thread.
As for the other question, I'm not entirely sure. I was under the impression that all the devs were still using the leak from about a week before the official RUU.
The audio issue is random, i for one have never had it once yet.
same here, not on any rom.
cali310 said:
I have noticed that most of the roms put out lately claim they are based on the official ruu yet many people still have the audio loss problem and when they bite the bullet and install the real official ruu from sprint their problem disappears.
If all these so called "official 2.1" roms were really official would the audio loss problem not have disappeared in them too?
Also, if they are truly official why does the thread on "2.1 rooting status" even exist?
Click to expand...
Click to collapse
(joking)
jesus fu*king christ , Really? I'm gonna go get a beer and get where your at
(joking)
Ruu and rom are totally different things and I don't know about the audio loss thing because I also have never had it. And you do got a point about the rom thing but if you read flipz he basically tells you that because of the new system.img that His "fixes" may not work right (not word for word)
I've never experienced the sound rape either.
I knew I was going to get blasted for those questions but I figured why not...at least it got me the answer as to why these official roms don't solve the problem.
I am one of those w/ the audio problem and tried a couple of the "official" releases that didn't fix the prob and I never saw a good explanation as to why posted anywhere. Now I have.
If someone can explain, what in the Hboot could it be that fixes the audio problem people are having with the official roms minus the new hboot?
cali310 said:
I knew I was going to get blasted for those questions but I figured why not...at least it got me the answer as to why these official roms don't solve the problem.
I am one of those w/ the audio problem and tried a couple of the "official" releases that didn't fix the prob and I never saw a good explanation as to why posted anywhere. Now I have.
If someone can explain, what in the Hboot could it be that fixes the audio problem people are having with the official roms minus the new hboot?
Click to expand...
Click to collapse
Yeah it's ****ed up I apologize even though I did say joking twice. I don't know if it's the hboot though. whats your stats? pri prl and so fourth
thatguythatdid said:
Yeah it's ****ed up I apologize even though I did say joking twice. I don't know if it's the hboot though. whats your stats? pri prl and so fourth
Click to expand...
Click to collapse
No need to apologize. Words on a screen aren't going to bother me.
As for the info you requested. I'm trying fresh 2.1.1 again.
firmware = 2.1-fresh
baseband = 2.42.01.04.27
pri = flipz_01
prl = 60664
cali310 said:
No need to apologize. Words on a screen aren't going to bother me.
As for the info you requested. I'm trying fresh 2.1.1 again.
firmware = 2.1-fresh
baseband = 2.42.01.04.27
pri = flipz_01
prl = 60664
Click to expand...
Click to collapse
wait try fresh 2.od with the audiofox before you do also the radio you have is it from the leak or the official rom?
thatguythatdid said:
wait try fresh 2.od with the audiofox before you do also the radio you have is it from the leak or the official rom?
Click to expand...
Click to collapse
I tried both the fixes on 2.0d a while back. The radio is from the leak.
cali310 said:
I tried both the fixes on 2.0d a while back. The radio is from the leak.
Click to expand...
Click to collapse
here is one from the actual sprint released ruu
thatguythatdid said:
here is one from the actual sprint released ruu
Click to expand...
Click to collapse
Thanks. I threw it on a little while ago. We'll see what happens.
markus_del_marko said:
The audio issue is random, i for one have never had it once yet.
Click to expand...
Click to collapse
i will second that. it is random, on my first hero i had the audio issues all the time, on my refurb ive flashed the same amount of roms and never ran into an audio issue yet. its random phones that it happens to i believe, mind you that the first hero i had i got on launch day, ive only had my refurb 2 months or something like that
The issue is caused by audio drivers in the kernel not resetting. we do not have the source for .29 kernel so there is no fix. we dont know why this effects some people and not others. cyanogen has worked on the issue and he does not have fix. many other forums have reported this issue with no fix. i chatted with a google engineer and he does not have fix. there is no fix that we know of except replacing the kernel with an older version that works. Since the audio drivers do not reset it does not allow anything to read them. so it continues resetting and resetting and this causes the cpu to be pegged by the constant retry and retry
recompiling the kernel seems to have fixed it. im thinking when toast compiled the OC kernel he changed some things that fixed it.
now lol at this thread. we did not make the official rom. google,sprint,and htc did. "official" means that everyone on the network receives the update. there are gonna be problems.
cali310 said:
Thanks. I threw it on a little while ago. We'll see what happens.
Click to expand...
Click to collapse
Did this work for you
derekstory said:
Did this work for you
Click to expand...
Click to collapse
Too early to tell. I put it on this morning and have only used the phone once.
The audio issue is random, i for one have never had it once yet.
Click to expand...
Click to collapse
Same here, no problems
-------------------------------------
Sent from my HERO200
I used the 1.47.651.1 ROOT method. I haven't Nand unlocked. I updated profile and PRL and i have baseband 1.39.00.05.31. I can turn 4g on but all it does is scan. Prior to update 4g was available. Is there something i am missing?
you might want to update your radio and wimax. Also, there are some others who have had similar problems in the Q and A forum so you might want to check there to see if there is a solution.
thanks i looked through Q&A...........my network even goes so far to say connecting to SPrint then goes back to scanning.....hmmm Anyone else have suggestions?
i have the same problem and haven't yet found a fix. I'm not sure what the problem is. This all happened after I updated to the latest Wimax from Calkulin's post... I wish I hadn't done that.
dallastx said:
thanks i looked through Q&A...........my network even goes so far to say connecting to SPrint then goes back to scanning.....hmmm Anyone else have suggestions?
Click to expand...
Click to collapse
I also had the same problem until I used the following thread. As long as you were successful in getting the engineering HBoot on the Evo. My Evo is now rooted with stock 1.47. You can install any Rom you like, but I did this one because I love the sense interface. Here Is the link that helped:
http://forum.xda-developers.com/showthread.php?t=715915
timkdodson said:
i have the same problem and haven't yet found a fix. I'm not sure what the problem is. This all happened after I updated to the latest Wimax from Calkulin's post... I wish I hadn't done that.
Click to expand...
Click to collapse
After rooting with the 1.47.651.1 ROOT method since i couldn't get wimax i just went back to stock shipped rom and lost root but then used unrevolked oringinal to at least get 4g,wifi tethering, and super permissions for other programs. Until a easier guide comes out at least im back the way i bought it with super permissions. Cant flash roms but to much of a headache loosing 4g and having to run 30 commands.
If you have issues with wifi tether or 4g like i did and give up for now run exe below and go back to stock and root with original unrevoked.
Link to original Evo stock rom before OTA
http://forum.xda-developers.com/showthread.php?t=685835
Link to unrEVOked original to apply to Stock Rom
http://unrevoked.com/
Filename: RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_rele ase_171253.exe