Related
Seems alot of this "everyone will unroot for 2.1" vs. "no one will unroot for 2.1" arguments is going on. Personally, I'd say you'd have to be a fool to unroot for 2.1. Toast has about everything but the camera working, Darch is getting an AOSP built. Even if Sprint DOES release it first, XDA will have custom ROMs up within 24 hours.
EDIT:
Yes, I made a typo on the poll.
Probably, assuming I can use one of the 1.5 RUUs to go back.
On another note, I anticipate that once the official 2.1 is released, all of the current 2.1 builds will basically dissolve and, eventually, all future development will be based on the official 2.1 release.
That's just a guess, but I think it's a good one.
Nandroid muthafucka, can you use it?
Using RA to go back to 1.5 and then doing the RUU is the only way I've gotten it to work.
Get an "Error 180" otherwise.
I'm assuming that the 2.1 update will overwrite RA the way the 1.5 RUU does.
If it doesn't, then of course restoring a Nandroid directly will be sufficient. If it does, then I'll need to go back to the 1.5 RUU, then root, then apply the backup.
abcdfv said:
Seems alot of this "everyone will unroot for 2.1" vs. "no one will unroot for 2.1" arguments is going on. Personally, I'd say you'd have to be a fool to unroot for 2.1. Toast has about everything but the camera working, Darch is getting an AOSP built. Even if Sprint DOES release it first, XDA will have custom ROMs up within 24 hours.
EDIT:
Yes, I made a typo on the poll.
Click to expand...
Click to collapse
First things first, I think the answer mostly depends on if someone tries it and reports whether they can root again afterwards or not.
If so, I believe many will unroot and upgrade.
If not, I doubt anyone here will do it.
Secondly, Toast's 2.1 build, while great(I use it daily) is not even close to the final 2.1
http://www.youtube.com/watch?v=elDD2mxE4ak
^^ Something a bit more like what we will have
Ah crap, I thought you meant you'd keep root.
jonnythan said:
I'm assuming that the 2.1 update will overwrite RA the way the 1.5 RUU does.
If it doesn't, then of course restoring a Nandroid directly will be sufficient. If it does, then I'll need to go back to the 1.5 RUU, then root, then apply the backup.
Click to expand...
Click to collapse
Potential problem being you may not be able to go back to the 1.5 RUU.
For example, if you flash Sprint's second RUU that was released, you are then unable to flash the original one.
So it may end up being you cannot go back to 1.5. Not sure how likely this is though due to the operating system version change, they may allow you to go back because some users may not like it(for some reason )
No, here at XDA some cool guy will probably make a better ROM based on 2.1
I agree that I will probably wait to see if someone can still root after the update if yes then I will probably go back and update then root again. if not then I will wait for one of the great devs here to release a rom built off the official 2.1 so I can keep root
You'd be a fool to unroot for 2.1. After you unroot, it might take weeks, months, or years to find a new exploit to root again. I say keep root and wait until our awesome devs have a rooted version up
I might unroot, but then again I don't want to wait for a root exploit ...
so I might stay rooted and wait for the devs to come out with a nice suitable ROM ...
I'm gonna wait for an root exploit before locking my phone down again with the 2.1 official. Then i'll probably try the official 2.1, not like it, and go back to an XDA 2.1
I give it about 72 hours before my curiosity gets the better of me, but only if there isn't already a viable 2.1 release here.
unroot
I would unroot for the update, simply because i have so much faith in the dev community. Im sure they will be able to root it again.
Powers16 said:
I would unroot for the update, simply because i have so much faith in the dev community. Im sure they will be able to root it again.
Click to expand...
Click to collapse
You love the dev community, yet you'll unroot in hopes they'll be able to root it?
Why not just wait for them to put up a custom ROM and keep root? I really doubt it'll take longer than a few hours, maybe a day to put out a fully working ROM
Well, i didnt say i wouldnt give them time either, ill wait about 2 or 3 days for them to make a custom rom, but i am so damn excited about the update i really am feeling like i am getting the short stick with the cdma hero on sprint. honestly the update needs to come asap.
why would anyone unroot to update? it would only take ten minutes to extract their build and just make an update.zip out of it. u flash it and its as good as sprints ruu. even better because u wont have to worry about root or upgrading to the next android version. lets not forget 2.1 isnt the end of the road for android. as soon as they start releasing updates for it. u can bet they are already working on the next build of android. but yeah i wouldnt unroot for the update. ill just get it, exstact it, make an update zip, and flash that sucker. then go back and tear it apart and start adding all the stuff sprint was to cheap or to dumb to add while removing all the bull they did add. i bet it wont take but an hour before an update.zip hits the forum after sprint releases it.
NOT going to unroot i love the custom roms
toastcfh said:
why would anyone unroot to update? it would only take ten minutes to extract their build and just make an update.zip out of it. u flash it and its as good as sprints ruu. even better because u wont have to worry about root or upgrading to the next android version. lets not forget 2.1 isnt the end of the road for android. as soon as they start releasing updates for it. u can bet they are already working on the next build of android. but yeah i wouldnt unroot for the update. ill just get it, exstact it, make an update zip, and flash that sucker. then go back and tear it apart and start adding all the stuff sprint was to cheap or to dumb to add while removing all the bull they did add. i bet it wont take but an hour before an update.zip hits the forum after sprint releases it.
Click to expand...
Click to collapse
QFMFT!
10chars
This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?
I don't think they can actually push a OTW update.....
barnacles10 said:
This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?
Click to expand...
Click to collapse
It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other potential nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found. This fully depends on whether old method is patched.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.
danknee said:
It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.
Click to expand...
Click to collapse
Couldn't have said it better myself! I would just suggest waiting until the cook of your preference updates his to include items from the official release.
And the single most important reason: No nandroid. Having a point in time backup is insanely important to me. If I ever have to return my phone and get a refurb, it's nice to know I've got a nandroid that will get me right back to where I was before I turned in my phone.
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.
jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.
Click to expand...
Click to collapse
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL
Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?
cicada said:
Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?
Click to expand...
Click to collapse
Not possible if the Hboot updates, which it probably will. Those here who tried the test leak 2.1 ruu.exe were unable to run the 1.56 ruu after.
There is an alternative to restore everything except the hboot from the 1.56 ruu here, but you cannot simply run the .exe. This method won't work if the official build has patched the ability to gain root (you won't be able to nandroid). In that case you will be stuck with official 2.1 only.
BTW, speaking from experience with the test build, ruu, hboot, etc.
Kcarpenter said:
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL
Click to expand...
Click to collapse
Open source is never a disadvantage. Ever.
Good to know, would've been awful to have to wait for new root hack just because I tried the new and shiny!
Guess I will sit back and wait for dev magic before I jump the gun.
Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
Mater of semantics, politics, and Ideaologies.
Google has a half belief here, they like open, but they protect that damn search algorithim like its a sacred scripture - Last count I think 8 people on earth knew exactly how it worked.
So the disadvantage to google would be ungodly competition if it was released. Proprietary stuff is a win if you look for profits. Again...depends on which side of the spectrum you are on. Points can be argued either way.
jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
Click to expand...
Click to collapse
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.
ramiss said:
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.
Click to expand...
Click to collapse
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!
Kcarpenter said:
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!
Click to expand...
Click to collapse
ROFL. . . you don't have unlimited text?
lol I would hope having a hero you would have unlimited data and texts
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.
yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.
Click to expand...
Click to collapse
lol! that's great.. ever since sprint gave us that free mobile to mobile in any network I do not bother checking minutes or texts. unless my bill changes.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one.
Click to expand...
Click to collapse
Why is it that people still think open source means insecure? I don't claim to know how previous rooting techniques exploit Android, but I do know that 2 Linux distros have a higher government security rating than any other operating system. I assume most weaknesses in android have to do with the recovery and/or update code, which has nothing to do with Linux.
Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
It IS when HTC bogards it from us and hordes it like cookie monster does cookies. I thought open source meant OPEN SOURCE. Ahh, who knows i probably misunderstood the whole concept
Hey guys, just curious since I havent gotten a chance to use a rooted phone yet.
-When google comes out with 2.2 froyo update, are we able to update it from a rooted rom or does it have to be under stock condition?
+1. will be going from cyan to stock again when froyo comes out. but how?
You'd probably have to wait until someone post the stock rom of froyo, and then flash that.
Or flash on of the numerous stock ROMs that already exist, and get OTA like the rest of us.
Or wait for cyan for his release which I believe will be soon after the official release.
You will have to wait until either someone posts a stock 2.2 ROM that world with rooted phones or someone like cyanogen updates.
Once a different recovery is installed on the phone, the OTA system will never work again. Not even if you go back to stock.
This is a complete non issue. The stock 2.2 rom may very well be available to flash here before you recieve the ota if its a rolling release. If not it will be a close race. BTW, The ota looks for a stock officially signed recovery to install itself with, if you do not have one the ota will fail.
jamesyb0i said:
+1. will be going from cyan to stock again when froyo comes out. but how?
Click to expand...
Click to collapse
Just out of interest (I am not making any judgements), why do you want to go from CM to stock as opposed to a CM modded version of 2.2?
Or are you just assuming 2.2 will drop before CM has time to mod it so want to get on it asap?
ill just wait for cyano to release its froyo version...
I'd be willing to bet that the features present in 2.2 will reach a version of CM before they reach any non-rooted N1. I'm just saying... we already have some of the features currently, i.e. customizable trackball notifications.
that really just depends on when google pushes the sources of 2.2 into AOSP. so chances are that a stock 2.2 will be available sooner than a cyanogen 2.2, but it will be worth the wait
3Shirts said:
Just out of interest (I am not making any judgements), why do you want to go from CM to stock as opposed to a CM modded version of 2.2?
Or are you just assuming 2.2 will drop before CM has time to mod it so want to get on it asap?
Click to expand...
Click to collapse
cos my battery life is absolutely shocking now, and things like stock weather program isn't working, cyan just watches LOST season 3 wtf lol
jamesyb0i said:
cos my battery life is absolutely shocking now, and things like stock weather program isn't working, cyan just watches LOST season 3 wtf lol
Click to expand...
Click to collapse
well obviously you're not paying cyanogen enough to address it
walie said:
well obviously you're not paying cyanogen enough to address it
Click to expand...
Click to collapse
bazinga!!!
he tasks me, he tasks me.
but naw switched to enom's for now, miss trackball unlock but allgud/ battery heaps better
PrawnPoBoy said:
You will have to wait until either someone posts a stock 2.2 ROM that world with rooted phones or someone like cyanogen updates.
Once a different recovery is installed on the phone, the OTA system will never work again. Not even if you go back to stock.
Click to expand...
Click to collapse
That's not true. I did a warranty replacement a while back and restored the phone to stock before sending it back. I used the SAPPIMG.zip method to restore the shipping ROM, recovery, and radio. After rebooting and setting up the phone, I was offered the OTA update and the OTA completed successfully. Being bootloader unlocked did not affect my ability to get OTA updates.
A little confusion here it seems and I will throw out my understanding. An ota will work if it does not have to access an officially signed recovery, if it does and does not find one it will fail. Once you have installed a custom recovery going back to the stock one will not help in this regard because it is no longer officially signed. 2.2 will require an officially signed recovery to install and everything I read says it will be seen, it will download, then it will fail to install. If this is incorrect than I look forward to learning more about this question as it keeps popping up over and over. I have yet to hear from any owner who was able to update from 2.0 to 2.1 after having installed a custom recovery, seems like there would have been many....
Okay xda, here's a hypothetical situation I'm considering:
I'm running damagecontrol 2.08.1, and I know the official 2.1 is out now. However, I hear mixed reviews. I'd much rather be running the official update, but at the same time not too sure I want to lose root. It'd be good to hop off the root train to avoid pains like this, but then I'll be impatient when Froyo comes around I suppose. Anyways, I was wondering if it were at all possible to:
1.) Backup via Nandroid my system running 2.08.1 rooted.
2.) Update to the official non-rooted 2.1
3.) Test it out, and if I don't like it, restore to my 2.08.1 rooted via Nandroid, and have root access again.
Can anyone confirm whether or not this would work? Also for those that updated, what are your thoughts on Root-vs-Non?
You figure out how to run a nandroid backup without root, after running the Sprint RUU, and you will make 27 people on this forum VERY Happy.
not me, I was smart and didn't load it...or at least i didn't "take one for the team"
colemorris said:
Okay xda, here's a hypothetical situation I'm considering:
I'm running damagecontrol 2.08.1, and I know the official 2.1 is out now. However, I hear mixed reviews. I'd much rather be running the official update, but at the same time not too sure I want to lose root. It'd be good to hop off the root train to avoid pains like this, but then I'll be impatient when Froyo comes around I suppose. Anyways, I was wondering if it were at all possible to:
1.) Backup via Nandroid my system running 2.08.1 rooted.
2.) Update to the official non-rooted 2.1
3.) Test it out, and if I don't like it, restore to my 2.08.1 rooted via Nandroid, and have root access again.
Can anyone confirm whether or not this would work? Also for those that updated, what are your thoughts on Root-vs-Non?[/QUOTE
This will not work, If you upgrade to 2.1 using official Ruu, You will lose root, and it will wipe the custom recovery image, so no more flashing anything, no more root, until someone finds the clink in the htc armour to regain root
Click to expand...
Click to collapse
I see, so that recovery menu isn't stock android recovery? Well then here's another question.
If you could get flash-rec on an unrooted phone through the ASTRO install method, could you flash a custom recovery image like 1.6.2, then do a nandroid restore from backup?
I probably sound like a mega-noob, just wanting to know why we can't do these things.
Nah, I "took one for the team" but am actually working on it. I DO have to say that the official 2.1 is DAMN fast though. Like, faster then pancacke 0.1 hehe
No but seriously, there is almost 0 lag, and the only thing that I have seen wrong is all of the apps in the app drawer
And no, the nandroid thing is NOT possible.
Hmm, thanks regaw for the answer. Is it fast enough to make waiting for a 2.1 rooted unnecessary right now? Cause damage hasn't logged in for ages, and I'm tired of all the force closes and errors I'm getting. I'm just not so sure it's worth upgrading when I may have to wait longer if I update to an unrooted. I mean, I have A2SD, DConfig, all those shenanigans that make the phone so much better. What's your take?
colemorris said:
Hmm, thanks regaw for the answer. Is it fast enough to make waiting for a 2.1 rooted unnecessary right now? Cause damage hasn't logged in for ages, and I'm tired of all the force closes and errors I'm getting. I'm just not so sure it's worth upgrading when I may have to wait longer if I update to an unrooted. I mean, I have A2SD, DConfig, all those shenanigans that make the phone so much better. What's your take?
Click to expand...
Click to collapse
Well, If you would like to do anything other than what Sprint/HTC wants you to do, I would recommend NOT upgrading, but waiting for something to come out. I know that Damageless is really busy, but I know that trevE is working on things too. They just need to finalize some stuff to get it out. While official 2.1 is fast, it doesn't have a whole bunch of things that us on custom ROMs take for granted. This is my first time on an official ROM since January, and, I do not want to keep it on for long, 1) just so I can begin developing again... and 2) so I can figure out the method of getting root back for everyone who ran the RUU.
regaw_leinad said:
Well, If you would like to do anything other than what Sprint/HTC wants you to do, I would recommend NOT upgrading, but waiting for something to come out. I know that Damageless is really busy, but I know that trevE is working on things too. They just need to finalize some stuff to get it out. While official 2.1 is fast, it doesn't have a whole bunch of things that us on custom ROMs take for granted. This is my first time on an official ROM since January, and, I do not want to keep it on for long, 1) just so I can begin developing again... and 2) so I can figure out the method of getting root back for everyone who ran the RUU.
Click to expand...
Click to collapse
Damn it Regaw I just realzied that you have more posts than me.
Any how, good luck on finding that root.
Here is this from Millworm, But it hink Eris devs proved it was fixed long ago.
http://www.milw0rm.com/exploits/9545
This one is also older, but not sure if anyone has tried it.
http://www.milw0rm.com/exploits/8678
Edit - Milw0rm must be dead.
and this, but it looks like only 2.6.30 Kernel maybe, and its just a Null Pointer exploit which is probably not suitable.
http://lwn.net/Articles/341773/
Also:
Possible way to change an MD5:
http://www.rapidleech.com/topic/2860-change-md5-hash/
Just some stuff I have looked at doing, but I am not willing to jump ship on a rooted phone.
you know I have been back and forth on whether or not to go with the official release and lose root, but during that process I loaded up Pure Hero rom which is based off the alysious (sp?) Rom but with Sense removed and man is it fast.
I have no need to lose root and this little phone is very speedy. And yes, I have tried Damage and Fresh (and a few variation based on those two) roms. Although they are decent roms, they just and turtles when compared to Pure Hero.
As far as Sense goes, I did like Sense, if you want it then do the alysious (again sp?) rom. Just that I think removing sense speeds it up, and honestly you can get all those functions through apps.
How much of a threat is the OTA/radio to future roms and rooting. I want to flash but not if it will jeopardize future endeavors....unrevoked twitter says not to...
As for the official ota that will be pushed by verizon I would not install it until unrevoked took a look at it, the leaked ota can be returned to stock and is fairly safe if you know what you are doing and have taken some time to read.
Sent from my ADR6300 using XDA App
jbizzle, MachString's right. Its safe to update to leaked OTA 2.2, and you don't lose root in the process. I recommend SkyRaider 2.0.1 once you've installed the leaked OTA 2.2 Radio and ROM as it's De-Odexed and give a much needed boost of performance w/ CityID and Footprints removed. Follow the steps to update to Leaked 2.2 and then download ROM Manager from Android Market and install SkyRaider 2.0.1 that way
Third
I am no stranger to rooting or to modified ROMs. I will tell you that I am not installing the "buggy beta" that everyone else has jumped on.
Personally, my plan of attack is to wait until unrEVOked gets the real OTA and sees if they can root it. If they can, then this is a no brainer ... avoid the "buggy beta" at all costs, install the pure ota with the proper radio, and root.
If unrEVOked cannot break it; then its a different question and up to your tastes.
jdmba said:
I am no stranger to rooting or to modified ROMs. I will tell you that I am not installing the "buggy beta" that everyone else has jumped on.
Personally, my plan of attack is to wait until unrEVOked gets the real OTA and sees if they can root it. If they can, then this is a no brainer ... avoid the "buggy beta" at all costs, install the pure ota with the proper radio, and root.
If unrEVOked cannot break it; then its a different question and up to your tastes.
Click to expand...
Click to collapse
Its actually not too buggy. I understand your perspective, but I encourage you to give the rom a try for yourself. Its reversible!
There is also a thread in the dev section outlining all of the confirmed bugs. All of which are minor, and most have been patched. There are no deal breakers here.
The only potential for failure lies within flashing the radio. Do your research on the process.
It's very usable for me.
It is very usable. I even made a Rom based on it.
Sent from my ADR6300 using XDA App
I'm actually surprised how many posts there are about the Leaked 2.2
Personally, I'd wait until the official one is released and then wait until it can be installed without the OTA. Then you preserve your root and other capabilities.
For those who can afford to mess up their phone and play with new stuff, I can understand... but a lot of people are clearly doing this that shouldn't be.
People who don't have patience, able to read and follow instructions and pull their batteries after waiting a minute or two, shouldn't be doing this.
Also, wait until the official release and try to search for help with all the leaked messages that have been posted. Will make getting real info for the real release harder to find.
Welp
Regrettably, unrEVOked just learned that the 2.2 for the EVO does remove root; and I have to assume that it will be the same for the Incredible. For those of us not willing to use the "buggy beta" this is bad news. I am sure they will be working on it, but it means sitting on 2.1 for a longer time.
I don't see how people are saying the beta is buggy. I've used it, I've used.sky raider.2.0, and I have developed and tested a Rom based off of it, jdfroyo v1
Sent from my ADR6300 using XDA App
jdkoreclipse said:
I don't see how people are saying the beta is buggy. I've used it, I've used.sky raider.2.0, and I have developed and tested a Rom based off of it, jdfroyo v1
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
No major bugs here either, but the beta does seem to drain my battery like crazy fast and the Temp was higher than normal, I just flashed back to 2.1 to see if there will be a difference.
Edit: back on 2.1 and the battery usage seems much better and cooler, on 2.2 it was around 105°F and on 2.1 around 97.7°F
Huh?
jdkoreclipse said:
I don't see how people are saying the beta is buggy. I've used it, I've used.sky raider.2.0, and I have developed and tested a Rom based off of it, jdfroyo v1
Click to expand...
Click to collapse
Really?
LEAKED Stock 2.2 ROM - **CONFIRMED BUGS**
http://forum.xda-developers.com/showthread.php?t=738634
[PATCH] Bug fixes for leaked Froyo -- Updated v3 (Fixes Gmail, Market & Superuser)
http://forum.xda-developers.com/showthread.php?t=738799
Leaked 2.2 Data Connectivity Issues
http://forum.xda-developers.com/showthread.php?t=738995
At least they changed the topic heading of the original release thread to say "Some Bugs".
I am not going to preach from the mountaintop here ... people want to go thru these fairly dangerous hurdles to install the bugged rom, they can go for it. This is 1 cliff I ain't leaping off of (at least while there is hope that the real 2.2 will be shortly released and hopefully rooted)