Database Users

flash back to old radio?

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.

Why cant any rom i flash boot?

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!

ANOTHER PRI PROBLEM!!!!!!(but with going to other roms after new damage)

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!

Full Revert from DamageControl2.0

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

???

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.