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!
Related
I was running originally DamageControl Sense 2.1 ROM w/Espresso. FANTASTIC ROM!!! Like a **** i went against the cardinal rule "if it aint broke dont fix it". I decided to go to DamageControl v2.0r2. Big mistake. The speed difference was noticeable (slower sadly enough with my experience) and then I encountered the wifi issues, the sync issues, the overheating, my battery going to **** as a result. This upset me more than anything else because after the fact in searching through the thread after it was up for awhile more and more of these issues were coming up but the thread's title and most of the info on it still read 100% WORKING OMG WTFBBQ ECT!. This should have been changed. Neither here nor there. SOOOOO.... I decide to go back to DamageControl Sense 2.1 ROM w/Espresso which is what i was using before i switched to DamageControl v2.0r2. AND NOW THE BOOT LOGO HANGS. So I decided lets try Darch's v4.2.2, AND AGAIN STUCK AT BOOT LOGO. So I decided to go to Fresh again, I was using fresh 2.0 and loved it at one point so I flash the rom and O WAIT ITS STUCK AT THE BOOT LOGO. I see DamagedTrev rom and I would love for this to work. Its what Damagev2.0r2 should be. (IMHO of Course) AND IT GETS STUCK ON THE BOOT LOGO.
Here is the list of actions I have taken:
Between each flash I wipe both data/cache
Not using Apps2SD
Latest Version of RA
and as a last resort
I UNROOTED AND STARTED FROM SCRATCH!! AND STILL NOTHING.
Sorry if its a rant. I am not calling out devs. I am not ungrateful. I am not a noob. (I am just covering the possible flames) I just want an answer. Its not a single release. Its a variety of them. Nobody really came out and said it but in searching (yes again covering the flames) i can only guess it might be the PRI issue, If so please confirm.
I know you say you unrooted, but try flashing a 1.5 ROM, such as Pancake. Also, try downloading the ROM again, as I think the very first time I tried flashing the new DC, I got the same problems as you. I downloaded again, and it flashed successfully.
mrinehart93 said:
I know you say you unrooted, but try flashing a 1.5 ROM, such as Pancake. Also, try downloading the ROM again, as I think the very first time I tried flashing the new DC, I got the same problems as you. I downloaded again, and it flashed successfully.
Click to expand...
Click to collapse
ty you for your response. i went to fresh 1.5 after i re-rooted. i downloaded the rom multiple times different computers different mirrors, still no luck. I called sprint and got my msl. i did the pri fix and still got nothing but a boot logo. i know you have to give it some time and all but overnight should be more than enough lol. am i stuck? this is miserable.
tom3k said:
ty you for your response. i went to fresh 1.5 after i re-rooted. i downloaded the rom multiple times different computers different mirrors, still no luck. I called sprint and got my msl. i did the pri fix and still got nothing but a boot logo. i know you have to give it some time and all but overnight should be more than enough lol. am i stuck? this is miserable.
Click to expand...
Click to collapse
I am very curious as to how you applied the PRI fix if you can't get anything to boot, please enlighten me?
btw...
i miss my iphone. soon you might see a post for *HTC HERO FOR SALE: DIRT CHEAP!* i have never been so frustrated with a mobile device before.
Roman G said:
I am very curious as to how you applied the PRI fix if you can't get anything to boot, please enlighten me?
Click to expand...
Click to collapse
as i said i was able to unroot and go back to stock. it would let me do that. from there i did the pri fix.
tom3k said:
i miss my iphone. soon you might see a post for *HTC HERO FOR SALE: DIRT CHEAP!* i have never been so frustrated with a mobile device before.
Click to expand...
Click to collapse
I'll give ya 10 bucks for it!
Roman G said:
I'll give ya 10 bucks for it!
Click to expand...
Click to collapse
lol at this point i might pay YOU 10 bucks.
Roman G said:
I'll give ya 10 bucks for it!
Click to expand...
Click to collapse
60 that's a good price!
Roman G said:
I am very curious as to how you applied the PRI fix if you can't get anything to boot, please enlighten me?
Click to expand...
Click to collapse
So back to my original question?
tom3k said:
as i said i was able to unroot and go back to stock. it would let me do that. from there i did the pri fix.
Click to expand...
Click to collapse
up ^ to original reply
Sorry all I saw was:
"I UNROOTED AND STARTED FROM SCRATCH!! AND STILL NOTHING"
So I thought you unrooted and nothing would work still!
Can you root using the kitchen?
What is your PRI?
Lets get ya rooted first!
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
You have to use either Sprint 1.29 RUU or Fresh's 1.56 RUU. That will make it stock again.
jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
Yeah I believe I used the 1.29 RUU from the stock rom
jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
I used 1.56 RUU and went back to stock. Worked fine on mine w/ stock radio.
jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
Some people do, and some don't. There is a fix if you brick it while RUUing. However if you are wanted to go back to stock for the 2.1 "official" release you might not be able to root again. They seem to leave the door open on the first round of software, but then close the hole on the next round. Seems the case for every phone
So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.
jdgiotta said:
So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.
Click to expand...
Click to collapse
Yea give it like 24 hours after the release, someone will do a nand dump, root it and post it on here. One thing I would reccomend people stay away from would be a new version of an RUU based off of 2.1, as that would put you up a **** creek if a root isn't found. I hear lots of problems trying to .29 RUU after a .56 RUU, I'm sure the same will be said for whatever the next version is.
jdgiotta said:
So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.
Click to expand...
Click to collapse
They may, or may not close the exploit that was found in 1.5 but if so it will only be a matter of time before some of these guys who are far more talented than I find a way to root 2.1, 1.5 was not rootable when it was released. Regardless the 2.1's you will see later today will be far superior to whatever sprint ends up releasing.
You should be able to RUU without any issues. However, you might still not be able to see protected apps in the market. I used the steps in this thread to fix that:
http://forum.xda-developers.com/showthread.php?t=605028
xanadu1979 said:
You should be able to RUU without any issues. However, you might still not be able to see protected apps in the market. I used the steps in this thread to fix that:
http://forum.xda-developers.com/showthread.php?t=605028
Click to expand...
Click to collapse
This fix didn't work for me, however I was able to RUU, update to DamageControl 1.0, download some protected apps, and then upgrade to DC2.0r2 (without wiping between DC1 and DC2). This opened up protected apps and solved the black on black contact problem for me.
-obviously do so at your own risk and all-
&RoidRage said:
Some people do, and some don't. There is a fix if you brick it while RUUing. However if you are wanted to go back to stock for the 2.1 "official" release you might not be able to root again. They seem to leave the door open on the first round of software, but then close the hole on the next round. Seems the case for every phone
Click to expand...
Click to collapse
Speaking of this, I am currently rooted, but running stock 1.5(don't ask)will I still be able to get the update or do I have to be completely unrooted to do so!
Also as far as the update is concerned, I know on the droid forums there were instructions on saving the update before installation so all could get it! What is the procedure for doing so!
It seems with the current state of affairs the update could come in a minute or a day or a month, basically no one know, so it could be anytime, so I just wanna be prepared for when it drop to hand it off to the real DEV.!
Roman
Eh, you could go ahead and flash a new ROM right now if you want. A fix was found for people getting bricked from the RUU, so you're safe to use the RUU now without fear of having a permanent brick on your hands.
Roman G said:
Speaking of this, I am currently rooted, but running stock 1.5(don't ask)will I still be able to get the update or do I have to be completely unrooted to do so!
Click to expand...
Click to collapse
Good question
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.
i tried out flipz latest, just to take a glance. i didnt read carefully enough apparently, because i dodnt realize he had put an autoupdate script at bootup of sense
now im back to damage, but flipz remains under pri. am i ok, or should i revert back, and if i need to roll back, how?
don't know what issues may lurk.just to be safe I ended up doing the 1.56 RUU update, doing the full reset (once I called Sprint and got my MSL), then rooted again.
Its a custom pri he put in to the rom. I guess to help with the pri issues. I haven't had any issues with it. I can do a update profile and prl.
mountaindont said:
i tried out flipz latest, just to take a glance. i didnt read carefully enough apparently, because i dodnt realize he had put an autoupdate script at bootup of sense
now im back to damage, but flipz remains under pri. am i ok, or should i revert back, and if i need to roll back, how?
Click to expand...
Click to collapse
Gosh, use GOOGLE! .
http://forum.xda-developers.com/showthread.php?t=653735
Flipz does mention it in the first post about his rom.
Reading is fundamental.
I got the same thing going on, but I am not worried about it!
I have flashed prolly 10 more times in the past couple of days with no ill effects!
bikcmp said:
Gosh, use GOOGLE! .
http://forum.xda-developers.com/showthread.php?t=653735
Click to expand...
Click to collapse
thanks for the link, bikcmp
it really helped
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