Related
Hey guys,
I have really been reading and learning alot since rooting my phone and flashing the MoDaCo rom. Im tempted to go back to RUU get the update and try to root again but I think its smarter for me to just wait on a updated MoDaCo ROM with the update in it. But I have a couple questions I hope someone can answer just in general.
1. Would going back to RUU to get the update, re-rooting and re-flashing MoDaCo hurt my app2SD that is already set up? Meaning I would have to re format the SD and apply all my apps back after im done.
2. Is it possible to go back to RUU, get the update, re-root and re-flash the MoDaCo ROM and not have any issues afterwards, and still have the update?
3. Whats the major benefit of updating at all. I mean after root and MoDaCo ROM, im having no issues with my phone whatsoever. But seems like everyone is updating so am I missing something key that my hero needs to have?
Thanks in advance for any answers. Im loving this android stuff. I can see myself learning alot from all of you.
swaze said:
Hey guys,
I have really been reading and learning alot since rooting my phone and flashing the MoDaCo rom. Im tempted to go back to RUU get the update and try to root again but I think its smarter for me to just wait on a updated MoDaCo ROM with the update in it. But I have a couple questions I hope someone can answer just in general.
1. Would going back to RUU to get the update, re-rooting and re-flashing MoDaCo hurt my app2SD that is already set up? Meaning I would have to re format the SD and apply all my apps back after im done.
2. Is it possible to go back to RUU, get the update, re-root and re-flash the MoDaCo ROM and not have any issues afterwards, and still have the update?
3. Whats the major benefit of updating at all. I mean after root and MoDaCo ROM, im having no issues with my phone whatsoever. But seems like everyone is updating so am I missing something key that my hero needs to have?
Thanks in advance for any answers. Im loving this android stuff. I can see myself learning alot from all of you.
Click to expand...
Click to collapse
This is basically the same situation I am in. I reflashed MoDaCo not realizing that it resets the software version back to 1.29.651.1, so there's really no point to updating in the first place if you want to run the Current 1.1 MoDaCo ROM, which also breaks the Voicemail app. If I were you, or if I hadn't already gone through the process, I'd just wait for the updated MoDaCo ROM that includes the Sprint Maint Rel update. I think he said he'd probably have it ready by the weekend or Monday (11/23). Right now I'm not sure if I'll keep what I have for a few days until the patched ROM is ready, or restore the nandroid backup I made right after applying the Sprint upgrade and rooting, or go back to stock again and not apply the update and reinstall MoDaCo 1.1.
Gambit727 said:
This is basically the same situation I am in. I reflashed MoDaCo not realizing that it resets the software version back to 1.29.651.1, so there's really no point to updating in the first place if you want to run the Current 1.1 MoDaCo ROM, which also breaks the Voicemail app. If I were you, or if I hadn't already gone through the process, I'd just wait for the updated MoDaCo ROM that includes the Sprint Maint Rel update. I think he said he'd probably have it ready by the weekend or Monday (11/23). Right now I'm not sure if I'll keep what I have for a few days until the patched ROM is ready, or restore the nandroid backup I made right after applying the Sprint upgrade and rooting, or go back to stock again and not apply the update and reinstall MoDaCo 1.1.
Click to expand...
Click to collapse
What do you mean break the voicemail app? I don't think I am having any issues with my voicemail. Can you tell me what that is you are referring to?
BTW, if you do decide to nandroid and root, will you just not flash a new ROM or use the stock ROM instead?? My main reason for using MoDaCo's ROM was for app2SD, i definately don't want to go back to apps on the internal memory now.
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
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
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
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.