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!
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
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)
Hey!!! I follow a threat told me how get pri back to 1.40 if doesnt change from 1.34.003 http://forum.xda-developers.com/showpost.php?p=6006539&postcount=1405
I tried this
##786# + MSL + Menu -> Reset + OK + Wait patiently = SUCCESS!
But doesnt work is still in 134.003
Any other possibility to change to 1.40.003
( I unrooted to stock rom 132.651.1 then did automatically update up to 147.651.1) Everything is fine except the PRI
That thread has nothing to do with the evo so its irrelevant. Search the evo forums and you will see that there is no going back to 1.40 if you have rooted and nand unlocked your phone. Not happening and no way around it unless sprint releases a pri update.
Sent from my PC36100 using Tapatalk
epphllps said:
That thread has nothing to do with the evo so its irrelevant. Search the evo forums and you will see that there is no going back to 1.40 if you have rooted and nand unlocked your phone. Not happening and no way around it unless sprint releases a pri update.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
The phone is Unrooted now with factory stock. Just wait with a cup of cofee and donuts. Lol Hope someone find a solution