n00b questions about Froyo and root - EVO 4G Q&A, Help & Troubleshooting

With Sprint announcing that they will be releasing Froyo within the next week or so, I am wondering what that means for my phone since it is rooted and running a custom ROM (BakedSnackbeta9.7). Could someone give me a brief "It means that..." for me?

It means the devs will have better access to HTC's code, which in turn will help them with some of the issues plaguing current froyo rooted roms (lack of 4g etc.)

It means, just like with any other update, don't accept the OTA if you want to keep root. There will be a new root process eventually, but why chance it? Just like with 2.1, the rooted roms will be better than stock.
Sent from my PC36100 using XDA App

and for now it means little as long as you dont take the OTA. I would expect to see the 2.1 rom devs moving to 2.2. I believe the Bakedpastries is the same dev as backedsnacks so you will likely see the 2.2 version replace the .1 version of the rom in the near future should you choose to flash it.

Related

Quick Root Question for a T-Mobile(uk) Hero

Hi Guys,
I am eager to try the 2.1 for my Hero which has had some 3G issues due to T-Mobile Network issue which still has no sign of being fixed.
Anyhow, my question is, if I made gold card and rooted my Stock Hero to a rooted 2.1 version, when the official one is finally released, can I go back to a stock 2.1 again?
Really want to try out the 2.1 but well over another month it seems to go on T-mobile.
yes
Yes, but it will prob unroot it,
Hi, If you root and install a custom 2.1 rom, when you update to the official t-mobile ROM, you WILL NOT BE ABLE TO ROOT AGAIN.
So be careful as custom roms often get things (just like the 2.1) a lot earlier than official upgrades. Especially from t-mobile as they seem to take ages before releasing them . Hope this helps.
twiztedvvv said:
Hi, If you root and install a custom 2.1 rom, when you update to the official t-mobile ROM, you WILL NOT BE ABLE TO ROOT AGAIN.
So be careful as custom roms often get things (just like the 2.1) a lot earlier than official upgrades. Especially from t-mobile as they seem to take ages before releasing them . Hope this helps.
Click to expand...
Click to collapse
This is still assumed, the root access may still be there through the old methods. But we don't know until it is released. I would let someone else test it first.

Upgrading to Official Froyo

Hey Guys,
When the official Froyo update comes out soon for EVO 4G phones, will I have a problem since I have installed Fresh Evo on my phone? I haven't performed the "full" root NAND method. I just used unrevoked.
Thanks for your help!
You may want to wait until Flipz freshens it up and provides an update that way (it usually doesn't take long after release)...if you want to run the official one, run the RUU and go from there to ensure you have no problems.
I personally havent used the unrevoked method, but I would assume that you would still need to unroot to get the official update. Someone correct me if I am wrong...
Plus we have amazing devs. My hero had 2.1 way before the official update! I guess it's all dependent on when they get the code though.
Alright, cool! Thanks for the info!
Some people will wait for one of the devs to cook up something in case the update breaks root when the official release comes out. No different from iPhone jailbreaks eventually they find away to defeat it.
Sent from my PC36100 using XDA App

[Q] Official Verizon HTC incredible Froyo Update (Coming tomorrow)

Engadget states that Verizon is going to push the official 2.2 Froyo update tomorrow for all HTC incredible users.
IF this is true I have a few questions. I'm currently rooted and running Sky Raider 3.0 RC2. I did a nand backup of my old original 2.1 Stock sense rom. If i revert back to that, can I just check for updates and apply the new stock 2.2 Froyo rom that is pushed from verizon?
Thanks,
ej_424
It is true. Unlike previous rumors, VZW employees were told today (this afternoon) and it shows on their bulletin screens now.
That and sometime between 1pm and 2:30pm they updated the support page.
So who's gonna jump in and who's gonna wait?
Please answer my question on how to go about updating. I'll jump in but want to knwo what process i have to take. Is there a chance that I wont be able to re-root if i go with the OTA update?
why go through the trouble of unrooting and going back to stock just to receive an update "officially" thats already been rooted and simplified here in 2 threads?
mb02 said:
why go through the trouble of unrooting and going back to stock just to receive an update "officially" thats already been rooted and simplified here in 2 threads?
Click to expand...
Click to collapse
Honestly.. It's pre-rooted, and is almost positively the exact same as the official OTA.. why bother?
ej_424 said:
Please answer my question on how to go about updating. I'll jump in but want to knwo what process i have to take. Is there a chance that I wont be able to re-root if i go with the OTA update?
Click to expand...
Click to collapse
Honestly there is so much information out there. Do what I did when I first got my Incredible. Do a search, and read, read, read. Mind you when you're done your head is going to be spinning. But that is the best way to get all the information you need.
To answer your question.
it was said along time ago that accepting the 2.2 OTA may cause you to not be able to re-root.
now, unrevoked forever takes S-OFF and with this you can accept the 2.2 OTA and still keep root, it was permanent, but with the new release of S-ON there is absolutely no reason not to use S-OFF, then un-root, if you want the "official" 2.2.
I thought that SkyRaider 2.5.2 and 3.0 were built off of the previous leak of FroYo 2.2...am I wrong? I love SkyRaider Vanilla, so I don't get giving that up for an "official" OTA? Maybe it is for some, but I don't see what else you'd really get that you don't have yet that was built into the 2.2 ROM's...
Mods will probably move this to Q and A,
But, you have to provide more info as what radio you are on, hboot.., etc. There are several threads started providing info as to how to prepare yourself...
I mean, the leak OTA has been ripped apart and placed all of this forum. The only thing you can get from verizon will be the satisfaction of a cool Blockbuster app and more vzw crapware, but hey if its what you want
RMarkwald said:
I thought that SkyRaider 2.5.2 and 3.0 were built off of the previous leak of FroYo 2.2...am I wrong? I love SkyRaider Vanilla, so I don't get giving that up for an "official" OTA? Maybe it is for some, but I don't see what else you'd really get that you don't have yet that was built into the 2.2 ROM's...
Click to expand...
Click to collapse
Skyraider pre2.0 was based off an evo port, yes. 2.0 and onward is based off the leak, hence the necessity of the radio upgrade.
Gotcha. That's what I thought, as when I installed SkyRaider 2.2, I remember getting an email saying "thanks for registering your Nexus One" or something like that... Thank you for confirming, much appreciated!
Your recovery image must be stock as well. There are several threads that provide the needed file to return the DInc back to 100% stock/pre-root (just make sure S-OFF is applied first).
Mandatory OTA?
I read the pdf files from Verizon's website on the expected 2.2 OTA, and it says it is MANDATORY. That the only options it gives you are install and DELAY install. That it will keep bugging you every 30 minutes til you do !
I have used Unrevoked3, and Unrevoked Forever and love the phone as it is now (particularly the wifi tether). I want to avoid the OTA but do I HAVE to accept it? If I do, I hope I can reload the version I got with Unrevoked3.
(I assume that Verizon will, in their new version make you PAY to wifi tether)
Any info on this?
Thanks
charlier26 said:
I read the pdf files from Verizon's website on the expected 2.2 OTA, and it says it is MANDATORY. That the only options it gives you are install and DELAY install. That it will keep bugging you every 30 minutes til you do !
Click to expand...
Click to collapse
I'll be pissed if thats the case. gotta do everything all over again. But if we're already @ 2.2 shouldn't it recognize that and not force the OTA to even appear on our phones?
I'm still pretty new to this so sorry if I sound like a complete outsider lol
For those of us who've rooted, forever'd, upgraded radio, and installed some leaked version of Froyo already -- if/when we get prompted to update the phone should we accept or deny it?
With the OTA update will be a radio update as well. And if they attempt to install over the same version won't that be the same as manually attempting to update it twice which equals brick?
Or will the update detect an upgraded radio already and skip that step?
Hackenstein said:
For those of us who've rooted, forever'd, upgraded radio, and installed some leaked version of Froyo already -- if/when we get prompted to update the phone should we accept or deny it?
With the OTA update will be a radio update as well. And if they attempt to install over the same version won't that be the same as manually attempting to update it twice which equals brick?
Or will the update detect an upgraded radio already and skip that step?
Click to expand...
Click to collapse
IIRC, you will only be prompted if you have sock recovery installed. As for the OTA, it includes updates to the radio and HBOOT. The update doesn't check to see if you already have an upgraded radio because, in theory, no consumer should have it yet.
najaboy said:
The update doesn't check to see if you already have an upgraded radio because, in theory, no consumer should have it yet.
Click to expand...
Click to collapse
If this is the case, there will be a whole lot of bricks out there, right? I thought I read that if you flash a radio twice you're bricked. Maybe not with S_Off.
PIYIRIO said:
If this is the case, there will be a whole lot of bricks out there, right? I thought I read that if you flash a radio twice you're bricked. Maybe not with S_Off.
Click to expand...
Click to collapse
Not a 100% sure but I think its only if you flash a radio.diff twice you get brick.
Never the less just don't have the updated radio with old builds and stock recovery and all should be fine.
Sent from my ADR6300 using XDA App
Nope
PIYIRIO said:
If this is the case, there will be a whole lot of bricks out there, right? I thought I read that if you flash a radio twice you're bricked. Maybe not with S_Off.
Click to expand...
Click to collapse
That applied because the prior unrEVOked hack was simply a diff ... it patched. So if you apply the patch to the patch, THEN you brick. Flashing a wholesale radio (while higher on the danger scale) is not the same.

Upcoming Update

If and when the Gingerbread update gets pushed out, how will us custom ROMmers be notified? Will we receive notifications asking us to download the update and then have to deny it? Will we have to unroot then upgrade? I wasn't around for the 2.2 update so I am a little curious as to how this all works on the Evo. Feel like such a noob right now but I really don't feel liking bricking my Evo due to an act of stupidity.
Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.
You aren't going to need to do anything, other than NOT take the OTA. The only thing you will need to do is wait from 2-10 hours after the update is out in the wild for the devs to get their hands on it and give us a fully rooted build to flash. It does not take long around here. There is absolutely no need to unroot and take the OTA. Who knows, if you did that you may not even be able to root again. So basically all you're going to need to do for the update is wait for the devs, and then flash a rom as usual. Maybe some new radios or something too, who knows.
I'm more concerned about when they will push the damn update. *Supposedly* it's Q2, but I'd bet if that's true, it will be late Q2.
r916 said:
Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.
Click to expand...
Click to collapse
Sure, lots of people say "wait for a rooted version of the update," but all I want to know is, is it POSSIBLE to safely upgrade even if you are rooted? Would flashing the stock update remove ClockWork recovery?
yes i was rooted before 2.2 and i was having a crazy day, long story short i accepted the OTA not paying attention and it got me a weird reboot then i was unrooted and on 2.2 i had to wait for a root method for it. but i heard of some people having their phone glitch in crazy ways, also that first OTA sprint rolled out had a bug that was bricking some phones
RileyGrant said:
If and when the Gingerbread update gets pushed out, how will us custom ROMmers be notified? Will we receive notifications asking us to download the update and then have to deny it? Will we have to unroot then upgrade? I wasn't around for the 2.2 update so I am a little curious as to how this all works on the Evo. Feel like such a noob right now but I really don't feel liking bricking my Evo due to an act of stupidity.
Click to expand...
Click to collapse
Developers will simply make new roms, and then you can flash the "update" of that rom. it'd be the same way of flashing CM7 nightlies.
Or just make sure you are s-off, take the update, install it. Then install SU from recovery and you are good to go. Thats the whole point of s-off (other than flashing PRI, NV, and Radios of course)
rugedraw said:
If you rooted with Unrevoked and have Unrevoked Forever, then theoretically you should be able to flash the update and still be s-off to flash a rooted rom over the update. You'd have to push the custom recovery back onto the phone, though. However, I wouldn't be the guinea pig for the theory myself. I'd keep 2.2 until a rooted 2.3 rom is available and then flash that. No one knows what will happen if you flash the OTA update as no one has is or knows what's inside of it.
Once it starts being pushed out, it will just be a matter of time before some posts a thread either:
a) crying because the update broke their root.
b) gloating because the update did NOT break their root.
Basically, don't accept it. Play it safe and wait. We've been on 2.2 for well over half a year, so 1 more day isn't going to kill anyone.
Click to expand...
Click to collapse
To make it simple, the result of accepting the OTA would either:
A- luckily do nothing
B- "Break" your phone and not be able to re-root
r916 said:
Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.
Click to expand...
Click to collapse
You are correct!
Theoretical question... If you're on a custom non-stock ROM (Myn or CM or whatever) and you accept the OTA, what would happen to the ROM? I don't think it would revert you back to the stock ROM because that ROM isn't on your phone anymore. I can't imagine CM would continue to work since it's not Sense. Would a Sense-based ROM (assuming you reinstalled all the Sprint bloatware) continue working with all the customizations even though you don't have root any more? Or does the OTA rewrite the entire ROM? Or would you just screw up your phone unpredictably?
I'm certainly not going to try this myself, but I'm curious as to what would happen.
phsteve said:
Theoretical question... If you're on a custom non-stock ROM (Myn or CM or whatever) and you accept the OTA, what would happen to the ROM? I don't think it would revert you back to the stock ROM because that ROM isn't on your phone anymore. I can't imagine CM would continue to work since it's not Sense. Would a Sense-based ROM (assuming you reinstalled all the Sprint bloatware) continue working with all the customizations even though you don't have root any more? Or does the OTA rewrite the entire ROM? Or would you just screw up your phone unpredictably?
I'm certainly not going to try this myself, but I'm curious as to what would happen.
Click to expand...
Click to collapse
The OTA update would include the new stock 2.3 rom in it. It would wipe whatever you have on your phone (regardless of whether it is Sense or not) and install the OEM Sprint 2.3-based rom that all will eventually be on all new Evos when HTC ships them out.

[Q] BaconBits and the new OTA

Sorry if the title is a little nebulous. I have a G2 that's been S-OFF'd and has cyanogen's BaconBits but not a full CM. I'm getting bugged to install the OTA update which, I'm pretty sure is a Bad Idea without some prep beforehand. My Google-fu and xda search skills are apparently failing me, because I'm sure someone has the scoop.
Can someone point me to a thread or tutorial? If the best answer without having to do full CM is to just decline the OTA, I'm good with that - just tell me how to shut it up! I'm using wireless tether and some other root-required things so I don't want a 100% stock Gingerbread.
Thanks,
Brad
What do u mean "not do a full CM"? You can't just flash part of a rom. And baconbits isn't to be used passed CM 6.1 I believe
Sent from my HTC Vision using XDA Premium App
What I meant by "not a full CM" was BaconBits. I had pretty much assumed there was no BaconBits moving forward, so I think my immediate goal is to just keep what I have. Is there a way to "turn off" the update nagging?
Brad
How the hell are you even getting updates? Which rom exactly are you using? And unless you don't want root anymore you should definitely not install it. But know that just incase you accidentally do install it there is an exploit now. But I would probably verify that you really have s-off and root access and reinstall your rom.
I currently have the stock ROM with S-OFF and cyanogen's old "BaconBits" add-on, released prior to anyone creating custom ROMs. I'm considering one of the stock-but-rooted Gingerbread roms, but for now, I just want to block updates. Suggestions?
Brad
Same here..I'm fully stock rooted with s off and tp wake mod only..I don't want to upgrade bc none of the updates are really stock( all these pure stock ones all have things removed or other tweeks)..I like my phone the way it is and just want to not get bugged for updating..what do?
I'm pretty sure if you edit the build.prop to say HTC Vision instead of T-Mobile G2 the update notifications will cease. Use something like Root Explorer to navigate to /system and then edit the line that says "ro.product.model=T-Mobile G2". It'll be like the 15th line down.
I can't guarantee it'll work but it's worth a try.
Why don't you just get the stock rooted update from here in the dev section? That'd be just as easy and then you'd actually have the update as well.
Stock Gingerbread OTA
Yeap.. I found that thread after some searching and upgraded, upgraded the radio, did the gps fix, fix permission.. and its working fine no wipe no nothing. Only thing Im missing is my track pad wake. Also to the op.. I think if you uninstall the app updater with uninstaller for root you wont get bugged for the update any longer.
Also even after upgrading to 2.3.4 it was still telling me there was an update.. I had to update the radio for it to go away..so maybe a radio update is all youll need op
i have a similar question. i'm also on stock 2.2, never did any OTA's and also have baconbits (flashing LED when message waiting, etc.)
what i would like to know, if i update to gingerbread, will i be able to install baconbits over gingerbread or not? i just want to keep a stock rom.
thanks!
konoplya said:
i have a similar question. i'm also on stock 2.2, never did any OTA's and also have baconbits (flashing LED when message waiting, etc.)
what i would like to know, if i update to gingerbread, will i be able to install baconbits over gingerbread or not? i just want to keep a stock rom.
thanks!
Click to expand...
Click to collapse
Baconbits if for 2.2 only; as it was abandoned when CM nightlies started. You might try Pershoot's kernel with stock 2.3 or just go all the way and get CM7.
Sent from my T-Mobile G2 using xda premium
Well, in the final analysis, I decided to go "all in". I realized after looking through the wiki that I had "label S-OFF" and not "radio S-OFF", and figured this could be an issue later on. So, I followed the instructions to get "radio S-OFF" and then tried to update my Clockwork recovery to the latest 3.x version; it didn't work (wouldn't boot into recovery). So, I tried an older version of 3.x (the one I had prior was a 2.5 something), and that did work.
Since I then had a fresh, fully rooted device as an starting point (with nandroid backup, of course), I decided to go for the gusto and install CM7. I had the foresight to do a Titanium Backup of my apps, but what I forgot to do was save my call log and SMS messages. So, I decided to exercise that nandroid backup; restored my 2.2 with BaconBits, saved the SMS and call log, then restored my CM7 that I had just saved 30 minutes before, and restored the SMS and call log. All of it worked like a champ.
So, I'm jammin' on the CM7, it's faster and better than my 2.2 with BaconBits, so I'm happy. I'll probably leave it like this until CM8, if there is such, and if it runs on G2.
Brad

Categories

Resources