Hi there,
I just sold my iPhone and got an Epic 4G and I am already rooted but I am looking to flash to a Froyo ROM. I see that you need to flash the modem as well as the rom, and you cannot back up the modem. If something happens after the flash and I need to roll back, how do I go back to 2.1?
Also, There is only 1 Froyo leak, right? Is that the DK17 that I see mentioned? Is there a chart of these build #s and what they have?
Thanks
algorhythm said:
Hi there,
I just sold my iPhone and got an Epic 4G and I am already rooted but I am looking to flash to a Froyo ROM. I see that you need to flash the modem as well as the rom, and you cannot back up the modem. If something happens after the flash and I need to roll back, how do I go back to 2.1?
Also, There is only 1 Froyo leak, right? Is that the DK17 that I see mentioned? Is there a chart of these build #s and what they have?
Thanks
Click to expand...
Click to collapse
1st: good move, such a better phone.
2nd: you can almost always return your phone to stock, AS LONG AS a) you can boot into recovery and 2) you have the proper files to flash.
Having said 2(2), you should look here. There you can find fully stock ROMs that are rooted as well as links to posts that can show you how to remove the root. Also check the developer's forum for stock roms like this DI18.
bilestoad said:
1st: good move, such a better phone.
2nd: you can almost always return your phone to stock, AS LONG AS a) you can boot into recovery and 2) you have the proper files to flash.
Having said 2(2), you should look here. There you can find fully stock ROMs that are rooted as well as links to posts that can show you how to remove the root. Also check the developer's forum for stock roms like this DI18.
Click to expand...
Click to collapse
Thanks for the help
I saw the Wiki, but what I'm confused about is the ROM version numbers floating around... i.e. DI18, DK17, DJ29, etc. Is there some sort of schema to decode these?
algorhythm said:
...what I'm confused about is the ROM version numbers floating around... i.e. DI18, DK17, DJ29, etc. Is there some sort of schema to decode these?
Click to expand...
Click to collapse
Sure is, not sure what the D stands for but the second letter corresponds to the month in which it was released. "I" meaning the 9th month of the year because it is the 9th letter of the alphabet, and so on. The digits are the day of the month it was released. The titles of the ROM's, however, appear to be linear. First 'E'clair, then 'F'royo, 'G'ingerbread, etc.
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.
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 think this would be a very useful file, because I know a lot of people are hesistant to update to 2.3.3 because of the removal of Facebook sync, but are still having issues with reception, reboots, etc. If the fixes are present in the baseband, it'd be great to be able to easily and safely update only the baseband, while staying on 2.3.2/CM7/custom ROM.
I'm not exactly sure of the feasibility on the Nexus S, but I know it was done before on the Droid when I owned that device.
According to Netarchy, the baseband update in the OTA is "patch-based", so it's not the full radio image, but rather changes to the existing one. So the full updated image would have to be created by applying these patches to the existing baseband. I'm not sure if that's possible to do off of the device, or if it needs to be extracted off a 2.3.3 device.
Anyways, I'm just putting in this request/suggestion. Please let me know what you guys think. Maybe if there's enough demand for it, a dev would undertake this
I like this idea.
Sent from my Nexus S using XDA App
Something like this?
(file deleted)
Warning! Completely and utterly untested!
It would be prudent for others to double, triple and quadruple check this. I just repackaged f182cf141e6a.signed-soju-ota-102588.f182cf14.zip after deleting everything not radio-related.
Edit:
Here's my collection of Nexus S radio images:
http://forum.xda-developers.com/showpost.php?p=11686273&postcount=14
shrivelfig said:
Something like this?
http://www.mediafire.com/?fqz11p9seawbs02
Warning! Completely and utterly untested!
Click to expand...
Click to collapse
Can i flash it from cw?
zadnica said:
Can i flash it from cw?
Click to expand...
Click to collapse
I think you have to. The stock recovery will probably refuse since it's not signed by Google.
shrivelfig said:
I think you have to. The stock recovery will probably refuse since it's not signed by Google.
Click to expand...
Click to collapse
I have a custom recovey (cw) + CM nightly build #7. Make i flash this baseband?
zadnica said:
I have a custom recovey (cw) + CM nightly build #7. Make i flash this baseband?
Click to expand...
Click to collapse
It's risky, because it's not tested yet. I think it would work, but I have little experience with Android development.
The ROM is (I think) divided into several sections, like recovery, system, boot, and radio, so flashing just the radio should not mess up anything else.
I didn't end up trying that update file posted above, as I found another method to get the 2.3.3 baseband. I've written up a little guide here:
http://forum.xda-developers.com/showthread.php?t=971239
It does require fastboot, but will surely work.
Well quick background information. I acquired my first samsung continuum 3 weeks ago, bricked it, and had to return it and get another one.
So while i waited for my new phone to arrive in the mail i was reading thread after thread and tutorials and guides to the Android OS, Samsung Continumm, Kernels, ROMS, etc.
Once my phone arrived i had a whole bunch of knowledge about it and successfully Rooted it using SuperOneClick, Flashed CWM into it, and flashed the PeanutButterJelly kernel. Yes Without messing it up again.
Well here are my questions:
1) Where can i find the official adrynalyne's rom for the continuum(yes i used the search button but didnt have much luck.
2) Is there a continuum radio file posted somewhere in the forum? people were talking about it in the forum but nobody can tell me where it is.
3) Could I constantly keep flashing kernels and roms or is there a limit to how many times i can do that?
4) If there happens to be an update from verizon, will rooting,replacing kernels and roms, take away the ability to download it.
Sorry again for the random questions, and if you tell me to use the "Search" option can you at least let me know exactly what to type in so i can find the right answer. Thanks You.
And one more thing, What is your phone set up, as in:Kernel,Rom,any mods, battery saving apps, root-only apps.
...
*sigh*
more questions...
1. The ROM is located under the android development section of our forum.
Here's a link to the ROM though: http://forum.xda-developers.com/showthread.php?t=943402
2. There is no radio file. There has been talk of it because we found out that the Fascinate radio files work with the continuum. We don't have our own though :'(
3. There is no limit besides the amount of ROMs and kernels you want to try.
4. Custom ROMs always in my experience disable the OTA updates that Verizon puts out. All you have to do though is revert back to stock and download the update if you truly want it.
Flashing ROMs and kernals will prevent you from being able to download any Verizon updates.
Sent from my SCH-I400 using XDA App
dfgged said:
...
*sigh*
more questions...
1. The ROM is located under the android development section of our forum.
Here's a link to the ROM though: http://forum.xda-developers.com/showthread.php?t=943402
2. There is no radio file. There has been talk of it because we found out that the Fascinate radio files work with the continuum. We don't have our own though :'(
3. There is no limit besides the amount of ROMs and kernels you want to try.
4. Custom ROMs always in my experience disable the OTA updates that Verizon puts out. All you have to do though is revert back to stock and download the update if you truly want it.
Click to expand...
Click to collapse
LOL at least they were easy questions and it keeps the continuum board active
Lol, sorry again, well thanks everybody for helping me out and pointing me to the right direction.
Sent from my mind
Ok so I came back to android after using an iPhone for a couple years. I had a Galaxy S that scarred me due to it's horribleness. I was into the whole custom ROM thing with it but largely have forgotten how to do all of that stuff.
Anyhow, while I bone back up on it, is anyone interested in me pulling off the 1.29.666.5 stock ROM? It seems to be a newer version than anything I see on the forum. If so, let me know how I can do it and I'll pass it along.
J
You will need to change apns-conf in htc framework, for use is it not in bell network only.
countfloyd said:
Ok so I came back to android after using an iPhone for a couple years. I had a Galaxy S that scarred me due to it's horribleness. I was into the whole custom ROM thing with it but largely have forgotten how to do all of that stuff.
Anyhow, while I bone back up on it, is anyone interested in me pulling off the 1.29.666.5 stock ROM? It seems to be a newer version than anything I see on the forum. If so, let me know how I can do it and I'll pass it along.
J
Click to expand...
Click to collapse
No its actually older. The 666 is regional (or operator), its the number after that indicated how old it is .5 is older than .12 for example. Its a 1.29 base, for 666 region, revision .5
Hey I have a bell HTC One that I already flashed..I would really appreciate it if you could find a way to upload the stock ROM in case I need to go back...
Thanks!
Interesting. So if I get this right. x.x.x.x is the way the firmware/software version is put together. so 1.29 is the base and doesn't change?
If so.. the 3rd octet. is the regional code?.. then the final one.. in my case is .7 is the revision?..
Which would mean that. 1.29.651.7 is older then 1.29.401.12?
DreadfullyDespized said:
Interesting. So if I get this right. x.x.x.x is the way the firmware/software version is put together. so 1.29 is the base and doesn't change?
If so.. the 3rd octet. is the regional code?.. then the final one.. in my case is .7 is the revision?..
Which would mean that. 1.29.651.7 is older then 1.29.401.12?
Click to expand...
Click to collapse
Yes its older latest is .12.
Okay. I don't mind doing the reading to figure out how to pull it off my device. Can someone save me a couple seconds and point me to a link that shows me how to do this...? It is a bit more complicated without and SD card correct?
Thanks,
countfloyd said:
Okay. I don't mind doing the reading to figure out how to pull it off my device. Can someone save me a couple seconds and point me to a link that shows me how to do this...? It is a bit more complicated without and SD card correct?
Thanks,
Click to expand...
Click to collapse
did you ever get a copy of this?
Rogers and Telus are now pushing .17
Sent from my HTC One using Tapatalk 2
Bell pushed out 17 as well.
Can u guys pls upload the stock radio?