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
Related
Before you start flaming me, please understand I did a thurough search of the forum and found nothing conclusive. What with bricks and RUU semi solutions, its kinda scary.
Im running flipz radio, and would like to flash back to the old one in preperation for the 2.1 update. Has anyone sucesfully flashed back, and if so, how?
I do not have a nandroid containing the old radio (but from what i gather, nandroiddoesnt effect the radio?) due to an accidental sd format (dont ask)
I do have the backup recovery img from my initial root; will this help?
Thanks in advance!
mountaindont said:
Before you start flaming me, please understand I did a thurough search of the forum and found nothing conclusive. What with bricks and RUU semi solutions, its kinda scary.
Im running flipz radio, and would like to flash back to the old one in preperation for the 2.1 update. Has anyone sucesfully flashed back, and if so, how?
I do not have a nandroid containing the old radio (but from what i gather, nandroiddoesnt effect the radio?) due to an accidental sd format (dont ask)
I do have the backup recovery img from my initial root; will this help?
Thanks in advance!
Click to expand...
Click to collapse
wow i used search for radio and found this on page 2 http://forum.xda-developers.com/showthread.php?t=644004&highlight=radio
im jus kidding but anyways yes the stock update signed works correctly no bricks. just follw my instructions and hopefully get you on track for the non existent 2.1 we get today!
goodluck
Avalaunchmods said:
wow i used search for radio and found this on page 2 http://forum.xda-developers.com/showthread.php?t=644004&highlight=radio
im jus kidding but anyways yes the stock update signed works correctly no bricks. just follw my instructions and hopefully get you on track for the non existent 2.1 we get today!
goodluck
Click to expand...
Click to collapse
I thank you most kindly for your speedy response. The threads Ive read have all been inconclusive; ill review your link and report back.
Flash went perfect.
Just wanted to thankyou, and apologize for not searching as well as I should have. I guess I was a little scared and just wanted some attention? Lol jk. Mods feel free to delete, or not, as I promised a report.
Ive stuck with the new radio since its come out, and have in no way noticed better battery life or signal; if anything-worse! -89 to -95 on new radio, -75 to 85 stock. Maybe its cause Im in detroit, maybe my phone just doesnt agree with the new radio (we all know how tempermental the Hero is)
Just my personal experience. I apologize for the clutter.
And yes, lets keep our fingers crossed for 2.1..
mountaindont said:
Flash went perfect.
Just wanted to thankyou, and apologize for not searching as well as I should have. I guess I was a little scared and just wanted some attention? Lol jk. Mods feel free to delete, or not, as I promised a report.
Ive stuck with the new radio since its come out, and have in no way noticed better battery life or signal; if anything-worse! -89 to -95 on new radio, -75 to 85 stock. Maybe its cause Im in detroit, maybe my phone just doesnt agree with the new radio (we all know how tempermental the Hero is)
Just my personal experience. I apologize for the clutter.
And yes, lets keep our fingers crossed for 2.1..
Click to expand...
Click to collapse
where you running in CDMA auto PRL?
Chad
nimitz87 said:
where you running in CDMA auto PRL?
Chad
Click to expand...
Click to collapse
Lol I did all the fixes.
Even now, responding to your post voa handset, I can tell its faster. And after flashing the radio at 30%battery, and charging since my last post, ive gone up almost double.
So question is...again inconclusive threads.
Can you flash back the old radio then RUU with out issues? Given there is always a chance for a brick but to avoid issues would it be smart to flash the stock radio before running RUU??? Or is the damage already done?
Kcarpenter said:
So question is...again inconclusive threads.
Can you flash back the old radio then RUU with out issues? Given there is always a chance for a brick but to avoid issues would it be smart to flash the stock radio before running RUU??? Or is the damage already done?
Click to expand...
Click to collapse
did you not even read the god damn thread? post #4 in particular.
holy **** man people need to learn how to READ I'm on a ton of forums and reposts happen and questions asked more than once but NONE worse than this forum.
/rant.
Chad
nimitz87 said:
did you not even read the god damn thread? post #4 in particular.
holy **** man people need to learn how to READ I'm on a ton of forums and reposts happen and questions asked more than once but NONE worse than this forum.
/rant.
Chad
Click to expand...
Click to collapse
OK ass, I understand you can flash the radio back, but my question is about running RUU afterwards **** head.
Post #4 Says nothing about running the RUU just that he could flash the radio back which we know is possible with other threads out there.
Quit being so damn arrogant and try to answer the question that was asked.
/rant moron.
Someone pass me the popcorn...
Lets not get upset people.
@K; in my not so professional opinion, the RUU issues are when U'ing between a 2.1 based rom and the RUU, a 1.5 rom. If you have the stock radio and any 1.5 rom, theres simply no reason the ruu wont work
Avs radio flash worked for me,.i havent ruu'd yet but i will report back later this week a conclusive thread.
Can you flash back the old radio, RUU, and TRUELY unroot?
Tune in next time...
@the rest
Hi!
mountaindont said:
Lets not get upset people.
@K; in my not so professional opinion, the RUU issues are when U'ing between a 2.1 based rom and the RUU, a 1.5 rom. If you have the stock radio and any 1.5 rom, theres simply no reason the ruu wont work
Avs radio flash worked for me,.i havent ruu'd yet but i will report back later this week a conclusive thread.
Can you flash back the old radio, RUU, and TRUELY unroot?
Tune in next time...
@the rest
Hi!
Click to expand...
Click to collapse
Thank you.
I'm in Michigan also and definitely experience a worse signal strength.
Why would I have to flash back to. the old radio for the 2.1 (when it finally does come out )
RPerry435 said:
I'm in Michigan also and definitely experience a worse signal strength.
Why would I have to flash back to. the old radio for the 2.1 (when it finally does come out )
Click to expand...
Click to collapse
If you want the oficial update, youllhave to unroot.
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!
soooo i was unrooted 1.5 stock hero rom, then the official leak came out so i upgraded to that, is there anyway i can root now?
The RUU police didn't get here in time for this one...
You'll have to wait for a 2.1 exploit to be discovered.
tstack77 said:
The RUU police didn't get here in time for this one...
Click to expand...
Click to collapse
I think we should just post this in these topics
http://www.youtube.com/watch?v=rY0WxgSXdEE#t=0m49s
thanks, it's alright though, 2.1 is great. The only things i wish it had were lwp and friendstream, but i can cope. I guess i'll just wait.
So you have 2.1 RUU ? Then you cannot root.
haha yeah i bit the dust,
i don't think i'm missing out on that much seeing as i tried rooting before and it never worked
eagles16 said:
haha yeah i bit the dust,
i don't think i'm missing out on that much seeing as i tried rooting before and it never worked
Click to expand...
Click to collapse
You could have just downloaded fresh kitchen and rooted that way... but you're ****ed for now. Sorry dude.
READTHEFUCKINGRULES said:
3. Post only using a clear subject and message.
You're most likely to receive a helpful answer to your question if you use a short subject title that describes your problem and a message that explains in detail what your problem is and what you've tried to solve it.
Click to expand...
Click to collapse
hrm a new user must have posted and then deleted.
i did try to use the kitchen, it would get up to the point where it would go into recovery mode then just stay stuck at the HTC logo recovery screen, also when i was doing it it says pre-kitchen has identified that you are not running a stock sprint rom, even though i was completely stock 1.5.
Download ROM HERE
It seems to be a Verizon Droid Eris 2.1 Official ROM.
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe
Anyone test this on their Eris yet?
Its an ruu, I suspect of the OTA maybe. Don't flash if you are root or 1.5
what about leaked v3 ok to flash?
I'm testing it right now. I was running leak v1. Will post results when it's complete.
tereg said:
I'm testing it right now. I was running leak v1. Will post results when it's complete.
Click to expand...
Click to collapse
Ok Thanks buddy
Tried it on leak v3. I still have hboot 1.49 so no change there. Other than that, the only thing that changed was the build number. It now has release-keys instead of test-keys after it. It is the OTA, just doesn't really do much for those running leak v3 and looking to root.
Flash successful HBOOT v 1.49.0000 S-ON
Radio 2.42.00.04.12
Conflipper, I cross-posted this on android forums .com and I gave you credit for posting it. Thank you! This will help all of the folks who are stuck on earlier non-root leaks and just want to get up to the current version (but are having trouble flashing the "leak v3" zip manually).
I've verified that the rom.zip within this RUU is identical (based on checksums) to the non-root PB00IMG.ZIP known as "leak v3" (the fourth leak).
thenestor said:
Conflipper, I cross-posted this on android forums .com and I gave you credit for posting it. Thank you! This will help all of the folks who are stuck on earlier non-root leaks and just want to get up to the current version (but are having trouble flashing the "leak v3" zip manually).
I've verified that the rom.zip within this RUU is identical (based on checksums) to the non-root PB00IMG.ZIP known as "leak v3" (the fourth leak).
Click to expand...
Click to collapse
but this may give us the ablitly to regain further updates, instead of verizon not giving us leakers no mo updates
feel free to spread the word, and get this out there. Spread the word, I am sure people will want the "Official" file.
i keep on getting error about connectiviy to the phone which i have it connected and idk,
also ever other time i try it gives me your battery is less than 30% which its at 68% so idk about that either.
i couldnt get it to work. im gonna give it another redownload and see
mattv3090 said:
Tried it on leak v3. I still have hboot 1.49 so no change there. Other than that, the only thing that changed was the build number. It now has release-keys instead of test-keys after it. It is the OTA, just doesn't really do much for those running leak v3 and looking to root.
Click to expand...
Click to collapse
Your rom had "test-keys" after it before you flashed this? That means you were rooted? If so you just lost root
jearl75 said:
Your rom had "test-keys" after it before you flashed this? That means you were rooted? If so you just lost root
Click to expand...
Click to collapse
i think he meant he was already running leak 3... and not rooted.
Does this bring all the 2.1 Sense UI features to the Eris like friendstream etc?
jearl75 said:
Your rom had "test-keys" after it before you flashed this? That means you were rooted? If so you just lost root
Click to expand...
Click to collapse
LOL
Perhaps folks should try re-reading what thenestor reported up above in this very thread:
[SIZE=+1]The ROM that is bundled inside this RUU IS IDENTICAL TO LEAK-V3[/SIZE].
Don't get your hopes up if you are a leaker; this is only useful for folks who mysteriously were able to manage Leak-V1 (the first leak) or Leak-V2 (the third leak), but are somehow now unable to repeat exactly the same procedure with the Leak-V3 (fourth leak) PB00IMG.ZIP.
bftb0
tenzomonk said:
i think he meant he was already running leak 3... and not rooted.
Click to expand...
Click to collapse
All the leaks (excepting the 2nd chronological leak, the "root-ROM") were shipped with release-keys.
The root-ROM was the only one that reported "test-keys".
bftb0
bftb0 said:
LOL
Perhaps folks should try re-reading what thenestor reported up above in this very thread:
[SIZE=+1]The ROM that is bundled inside this RUU IS IDENTICAL TO LEAK-V3[/SIZE].
Don't get your hopes up if you are a leaker; this is only useful for folks who mysteriously were able to manage Leak-V1 (the first leak) or Leak-V2 (the third leak), but are somehow now unable to repeat exactly the same procedure with the Leak-V3 (fourth leak) PB00IMG.ZIP.
bftb0
Click to expand...
Click to collapse
Right! If people are on the leak and are not holding out for the slim chance of root, they should flash this. Atleast they will have an "official" release
jearl75 said:
Right! If people are on the leak and are not holding out for the slim chance of root, they should flash this. Atleast they will have an "official" release
Click to expand...
Click to collapse
What?
If it is IDENTICAL to Leak-V3; as far as the phone is concerned, how would it be any more or any less official?
I'm wondering, what do people think "Identical" means?
Coinflipper needs to "get the word out" that there is a new copy of Leak-V3 floating around; his OP reads as if this is something new, when it is not.
Wow, great news! It will encourage folks like the poster up above to rush out and unroot their phone.
Oh well, more power to them... or less, as the case may be.
bftb0
bftb0 said:
What?
If it is IDENTICAL to Leak-V3; as far as the phone is concerned, how would it be any more or any less official?
I'm wondering, what do people think "Identical" means?
Coinflipper needs to "get the word out" that there is a new copy of Leak-V3 floating around; his OP reads as if this is something new, when it is not.
Wow, great news! It will encourage folks like the poster up above to rush out and unroot their phone.
Oh well, more power to them... or less, as the case may be.
bftb0
Click to expand...
Click to collapse
First of all I said "those on a leak", didn't say leak v3. Just to bring you up to speed there are 2 leak versions before v3, hence the v3. It would be more official because this one WAS released by Verizon, whereas the leaks were not, which is why they were leaks. It is identical yes, but the build number is different, which would differentiate between leak v3 and this OFFICIAL release should you need to return your phone. Just because the support people might not be able to tell, someone can believe me. I know people who have returned there leak and been charged for a new phone because they had unofficial software on there phone, never even mentioning it. This was a month or more later, just showed up right there on there bill.
So, people who feel better having an official release (whether your on leak v1, v2, or v3) can flash this, it's official. If someone who has root can't read where it says this is for people on the leaks, if you have or ever want root don't update. Then that's their problem, not much you can do about that....
i like the rom i am using and do not want the next update from verizon. how do i got about keeping what i have and not taking the next update? i obviously don't want my phone asking me every day if i want to apply the update. do i need to trick it into thinking i already have it? if so, how do we do this?
Are you running a custom rom? If so, it shouldn't nag you for any Official OTA's.
TheGamerZ said:
Are you running a custom rom? If so, it shouldn't nag you for any Official OTA's.
Click to expand...
Click to collapse
i'm running version 2.0 of Virtuous rom. it's based off of the build that is currently on any stock Incredible. it's deodexed and stuff, but it's based off of the current build. 3.21.605.1 is the build of my current rom, not 3.26.605.1.
i have put a lot of work into getting it where it is right now and i have no desire at all to run anything different. i keep updating kernels as they get better and better, but thats it.
Hello boys and girls!
The word of the day is... "Nandroid"... Can you say it with me? "Naaaaaaandroid" Good, I knew you could! (^_^)>b
p.s. - the previous poster is correct. Any custom ROM should either A)not get the OTA update at all or B)get the OTA and prevent it from installing which will shut up that bothersome notification lol
dimebagdan65 said:
The word of the day is... "Nandroid"... Can you say it with me? "Naaaaaaandroid" Good, I knew you could! (^_^)>b
p.s. - the previous poster is correct. Any custom ROM should either A)not get the OTA update at all or B)get the OTA and prevent it from installing which will shut up that bothersome notification lol
Click to expand...
Click to collapse
i have several nandroids of my current rom from different dates, so i have that covered.
thanks. i'll wait and see what happens.
jasonb1985 said:
i have several nandroids of my current rom from different dates, so i have that covered.
thanks. i'll wait and see what happens.
Click to expand...
Click to collapse
Good deal, I'm just holding my breath for the LTE Incredible HD hehe
Sent from my ADR6300 using XDA App
FYI - There's a post on the development forum for the skyraider rom where a user says they're receiving the update message too! Sounds like not all custom ROMS block OTA's.
________________________________
Unrevoked forever
SkyRaider Sense 3.3.3
KiNgxKernel BFS (#5)
Radio 2.15.00.07.28
Here, this should help stop the nagging:
netboy3 said:
Thanks for the reference. The leaked build version seems to be working for this purpose.
To get this to work, you need to edit the /system/build.prop. find the line that begins with "ro.build.fingerprint" and change it to:
Code:
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys
Once rebooted, the nag might appear once more, but if you go to Settings->About phone->System updates you wil now get "your system is currently up to date".
Click to expand...
Click to collapse
I was getting bothered by it, since like 10am on the 8th, did this, bugged me after the reboot once, and was done after that.
Blah12543 said:
Here, this should help stop the nagging:
I was getting bothered by it, since like 10am on the 8th, did this, bugged me after the reboot once, and was done after that.
Click to expand...
Click to collapse
saw this in the skyraider sense thread. thank god for Root Explorer.
jasonb1985 said:
saw this in the skyraider sense thread. thank god for Root Explorer.
Click to expand...
Click to collapse
Yeah lol that's what I used as well.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.