For those who do NOT like to delve into the Dev area often and may have not seen this
http://forum.xda-developers.com/showthread.php?t=886903
go ahead and be daring...I myself like to wait until atleast a Beta.
Good stuff, thanks. I've been longing to root this phone, but I refuse to do it without a factory .zip which I can flash to restore defaults. Too many people have various issues after rooting, just don't want to take that chance. Can't wait to see what CM puts out though.
what issues? You make a nandroid to go back to
Sent from my Nexus S using Tapatalk
allen099 said:
Good stuff, thanks. I've been longing to root this phone, but I refuse to do it without a factory .zip which I can flash to restore defaults. Too many people have various issues after rooting, just don't want to take that chance. Can't wait to see what CM puts out though.
Click to expand...
Click to collapse
I'm completely with you on this,need that safety net before any modding of any kind.
xspyda said:
I'm completely with you on this,need that safety net before any modding of any kind.
Click to expand...
Click to collapse
Make a nandroid backup.
So to clarify, if I do the following ...
1) factory reset
2) unlock bootloader
3) root phone
4) make nandroid backup
I can then restore the nandroid backup at any time and phone will be completely stock, recovery, bootloader and all exactly as it is now with no sign of modding whatsoever?
I haven't had a lot of time to read into this so not sure as yet what's involved in the above steps but in a nutshell am I on the right lines? Theres a lot of confusing (and conflicting) info out there!
Thanks.
mprziv said:
Make a nandroid backup.
Click to expand...
Click to collapse
While I understand what you're saying, it seems like some people are having issues even after injecting root. I can live without Titanium or drocap2 for a few days longer while Google drops the official restore...although I do want tethering asap.
allen099 said:
While I understand what you're saying, it seems like some people are having issues even after injecting root. I can live without Titanium or drocap2 for a few days longer while Google drops the official restore...although I do want tethering asap.
Click to expand...
Click to collapse
?? You can already tether on stock. Also, I haven't heard of anyone having problems just from rooting the phone, in fact, all you're really doing is unlocking the bootloader and installing an apps to give you su permissions. Like the others said, you can always nandroid back to stock and relock the bootloader if you want to.
The major things wrong with the CM7 alpha on the NS are the Camera and Wifi and other things you would consider major
Cam and wifi work on alpha2.
irishrally said:
Cam and wifi work on alpha2.
Click to expand...
Click to collapse
Once it hits beta ill grab it up but until then im way happy with what i got now
guys come on. This is a dev phone. This is what Nexus is about. Why not flash? Cyanogen is the most consistant and top quality Roms. I love the stock just as much as the next guy, but I didn't buy this phone to be boring. Just flashed CM7 and all is good. updates should make it even better!! Let the fun begin!!
yungfresh said:
guys come on. This is a dev phone. This is what Nexus is about. Why not flash? Cyanogen is the most consistant and top quality Roms. I love the stock just as much as the next guy, but I didn't buy this phone to be boring. Just flashed CM7 and all is good. updates should make it even better!! Let the fun begin!!
Click to expand...
Click to collapse
I'm all for that sure but not until I have a simple and sure fire way of returning absolutely everything to stock, out of the box condition.
Im personally waiting for Amon_RA to release his NS recovery
and ya, the whole not having a sure fire way to go back to stock is a downer.
Google needs to release the stock ROM in its entirety
I'm sure they'll do that soon... or at least I hope they will. Only then will the fun begin for me!
Just wondering, why do you guys need a surefire way to return to stock? Just reflash stock rom and relock bootloader.
ikon8 said:
just reflash stock rom and relock bootloader.
Click to expand...
Click to collapse
Is it really that simple though? My understanding is that the only available 'stock' rom is not in fact stock, rather its an adapted rom as Google have yet to release the actual one?
I want to be able to return to normal in case I want to return the phone.
ikon8 said:
Just wondering, why do you guys need a surefire way to return to stock? Just reflash stock rom and relock bootloader.
Click to expand...
Click to collapse
you cant reflash the stock recovery over CWM either....so when they release the stock ROM officially all you would have to do is re lock the bootloader and flash the rom and it will overwrite EVERYTHING
i was a hardcore CM user on my N1 , flashed nightlies every day but i just dont see anything in CM for the NS that would make me jump right into an alpha
slowz3r said:
when they release the stock ROM officially all you would have to do is re lock the bootloader and flash the rom and it will overwrite EVERYTHING
Click to expand...
Click to collapse
That sounds like just what I'm waiting for. Wonder when it will come. Until that time I guess we just have to be patient.
xspyda said:
That sounds like just what I'm waiting for. Wonder when it will come. Until that time I guess we just have to be patient.
Click to expand...
Click to collapse
Im sure it is on the servers, just a matter of time before someone manages to find it...they always do
Related
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.
This is just a simple question.,
Will you unroot for the official 2.2 or won't you?
Already did.
Sent from my PC36100 using Tapatalk
you should have started the thread as a Poll..
Nope, I'll wait for a rooted version.
Hell no, whats the point of rooting if you do the official update. There is a reason im rooted, and not looking to lose it anytime soon.
tyrnight said:
you should have started the thread as a Poll..
Click to expand...
Click to collapse
It was suppose to be started as a poll but i hadn't finished the questions yet before people started posting lol wow guess people are laying in wait....
Nope. Will wait for rooted, fully working version.
I ain't rooted so I'm getting the update as soon as I can get my greedy little hands on it.
nope i wont be unrooting
I will not lose my wiimote bluetoof!!!
why do people make such a big deal about the ones who update and lose root? If you didn't update and lose root then good for you but some people like to try the official update before the chefs update and customize, i for one can't blame them. We all paid for these phones, some more then others and if they want to upgrade then let them. I'm seriously thinking about doing the update and i will start a donation fund for whoever can root the new build. It's my choice and comeone will eventually root it anyway so whats the big deal???
Young_e said:
someone will eventually root it anyway
Click to expand...
Click to collapse
that is likely but certainly not guaranteed, just sayin..
not worth the risk for me
Anyone who is rooted should have Froyo already. It would be absolutely moronic to unroot for it.
TheBiles said:
Anyone who is rooted should have Froyo already. It would be absolutely moronic to unroot for it.
Click to expand...
Click to collapse
whatever what if someone wants 2.2 with sense then what?
Young_e said:
whatever what if someone wants 2.2 with sense then what?
Click to expand...
Click to collapse
then you donate to damage and treve, or you flash avalaunch's froyo..
nebenezer said:
then you donate to damage and treve, or you flash avalaunch's froyo..
Click to expand...
Click to collapse
or i could update to stock froyo and donate to someone to root it
nebenezer said:
that is likely but certainly not guaranteed, just sayin..
not worth the risk for me
Click to expand...
Click to collapse
you are absoulutely right, but the evo getting rooted in the first place wasn't guranteed and nothing is really guranteed my friend lol. But with the devs here at xda and all the new phones shipping with froyo once it gets released i'm sure it will be rooted soon enough
None of the Froyo ROMs out there have 4g, which I use every day.
I'll probably wait a couple of days to see if somebody posts a rooted version, and if not, I may un-root for the stock update. But then if I lose root, I also lose Titanium Backup, so I'd have to set everything up from scratch, which I hate.
pbarrett said:
None of the Froyo ROMs out there have 4g, which I use every day.
I'll probably wait a couple of days to see if somebody posts a rooted version, and if not, I may un-root for the stock update. But then if I lose root, I also lose Titanium Backup, so I'd have to set everything up from scratch, which I hate.
Click to expand...
Click to collapse
This. I miss 4G on this CM6 ROM, which is otherwise awesome.
AppBrain is a less effective approach to restoring apps, but it beats starting from scratch.
pbarrett said:
None of the Froyo ROMs out there have 4g, which I use every day.
I'll probably wait a couple of days to see if somebody posts a rooted version, and if not, I may un-root for the stock update. But then if I lose root, I also lose Titanium Backup, so I'd have to set everything up from scratch, which I hate.
Click to expand...
Click to collapse
i actually didn't think about losing titnium backup damn i might not update after all i would hate losing all my apps and ****
Hey guys I just got my vibrant back and I was wondering if I should root it, or just wait for froyo to release?
Sent from my vibrant while I'm working. I love my job
Joshochoa187 said:
Hey guys I just got my vibrant back and I was wondering if I should root it, or just wait for froyo to release?
Sent from my vibrant while I'm working. I love my job
Click to expand...
Click to collapse
Rooting isn't hard at all. You should go ahead & root now
+1 on the root now. While your at it install a custom rom and you will love your phone. Odds are you can get the Froyo update right here before it hits OTA anyways.
Yeah I've rooted my vibrant before I had to get a new one. It is easy but I would probably have to un root it to update right?
Sent from my vibrant while I'm working. I love my job
I don't understand what waiting would do. What you should NOT do is get the Froyo update from T-Mobile, as there is a chance that they will push an update that breaks your ability to root with 2.2 and you will have to wait even longer.
I recommended you root now, install Rom Manager, go to this thread:
http://forum.xda-developers.com/showthread.php?t=813001
Download Fusion 1.1 to your SDCARD (I have a folder called ROMS) and go to Clockwork, reboot into Recovery, Reinstall Packages, Install ZIP from SDCARD, choose Bionix 1.1, wait, and then see what that phone is really capable of.
Using Fusion 1.1 makes me not mind waiting for Froyo.
Yeah you are right it's just I haven't got to comfortable w/ flashing roms just yet. Looks a bit hard I guess I will just keep watching the videos on it till I feel like I can do it
Sent from my vibrant while I'm working. I love my job
Flashing roms is super easy as long as you're using ones flashable through rom manager. I must warn you it's very addictive. The only thing I would say is make your you backup in case something goes wrong and avoid Voodoo until you've flashed a few times and feel more comfortable. Great thing is there is tons of support here. I suggest you try Bionix Final.
Well guys I'm pretty convinced I think im going to do it I'm going to look into it thanx alot for your input
Sent from my vibrant while I'm working. I love my job
I should still be able to root even tho I did the recent ota right?
Sent from my vibrant while I'm working. I love my job
Joshochoa187 said:
I should still be able to root even tho I did the recent ota right?
Sent from my vibrant while I'm working. I love my job
Click to expand...
Click to collapse
Yes you can.
Joshochoa187 said:
Well guys I'm pretty convinced I think im going to do it I'm going to look into it thanx alot for your input
Sent from my vibrant while I'm working. I love my job
Click to expand...
Click to collapse
Dooo eeet!
Yes, it's daunting at first to flash a new ROM, but I just did it for the first time a few weeks ago and it was simple and easy. Just read up as much as you can and then write up a "roadmap" on all the steps you need to take, before, during, and after. It removed a lot of headaches for me because I planned it all out and had all the software ready in case anything went wrong (Odin, stock ROM, etc.). If there are any gaps in your understanding or questions about a process, ask them here before you flash!
I would root it and load a custom ROM, waiting for official OTA update to Froyo is like playing a Russian roulette now. Look what a simple update that was suppsoed to address GPS and other issues did to your fellow TMO users.
As always, there will be people who wouldn't even know that you can root the device to make it your own, so they will always run stock, and complain to TMO when they click MobiTV app and never use it, but have to cough up 10 bucks a month for it (it is just an example).
If you came here you know that you can do something to your phone besides waiting for Froyo, take a full advantage of what is offered in the dev section, and don't forget to support the developers if you like the work they do
Ok I'm reading the thread you posted how do I preform nandroid back up?
Sent from my vibrant while I'm working. I love my job
Joshochoa187 said:
Hey guys I just got my vibrant back and I was wondering if I should root it, or just wait for froyo to release?
Click to expand...
Click to collapse
If you are going to root, you might as well just do it.
Froyo could easily be 2-3 months down the road yet.
you need ROM manager...
it took me forever to find a how-to on this exact thing.
You have to be rooted in order to accomplish this:
1. root (obviously)
2. download ROM manager
3. open ROM manager and click on 'Flash ClockworkMod Recovery' and pick your phone.
4. click 'Backup Current ROM'
5. Let it do it's thing... it's going to reboot and run in recovery then reboot again.
6. You are done!!
To recover, you have to boot into clockwork recovery and click restore then pick the date file you made to recover to that date!
** If any of this is wrong, please call me out!!
Yeah, I started doing all this before I even discovered ROM Manager and ClockworkMod Recovery. Those tools definitely make everything so much easier.
Make sure you have the following software tools:
ADB
Odin
Rom Manager (w/ ClockworkMod Recovery installed)
Titanium Backup
Also, make sure your phone is not hardware locked before you begin. Try the standard procedure to enter Recovery Mode; if your phone is hardware locked, run the flashable fix (found in the dev forum) so that you have some way of recovering from a soft brick.
From my experiences, rooting has always been the fastest way to get updates. Those rollouts take forever.
Just rooted and installed fusion 1.1 it's great thanx for the tips guys
Sent from my SGH-T959 using XDA App
Joshochoa187 said:
Just rooted and installed fusion 1.1 it's great thanx for the tips guys
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Way to go!
Sent from my bionix powered Vibrant
lol. i was waiting for a froyo release, i flashed my g1 a bunch so flashing wasn't a big deal, but i was happy with the phone stock for a bit and didn't mind waiting. but i rooted after a week. was flashing smaller things like ji2 gps, getting rid of bloatware, changing bootup/shutdown, etc. a couple weeks later. and a couple weeks after that i started flashing roms.
moral of the story? just root and start flashing now, it's a long wait.
Yes, I know. Why do I want to unroot? Well, the AT&T Nexus One is stuck on 2.1 update 1 and the baseband of the phone is unlocked.
How can I return to bone stock so that I receive all OTA updates. I'm good with what google pushes out and really don't want to fool with homebaked updates.
Thanks!
Read my signature, follow "unroot/restore" guide.
Your bootloader has been unlocked, not baseband. So follow the guide for unlocked bootloader. Use FRG83G ROM straight from HTC.
Thanks. Doing this now.
Actually, do I just follow the "fastboot" method and that's it?
Yes. Having unlocked bootloader makes things easier...
Jack_R1 said:
Yes. Having unlocked bootloader makes things easier...
Click to expand...
Click to collapse
How so? I'm not really certain I am good with the method in the FAQ. I'm not familiar with adb and fastboot. In fact, I have no idea how to do these methods.
I am googling and reading as much as I can, but it's a bit intimidating. Any video walkthrough or idiot proof document that shows exactly what to type, etc?
Sorry, I'm just not as into this as most here (but I'm very eager to learn).
ericshmerick said:
How so? I'm not really certain I am good with the method in the FAQ. I'm not familiar with adb and fastboot. In fact, I have no idea how to do these methods.
I am googling and reading as much as I can, but it's a bit intimidating. Any video walkthrough or idiot proof document that shows exactly what to type, etc?
Sorry, I'm just not as into this as most here (but I'm very eager to learn).
Click to expand...
Click to collapse
Try and follow these instructions, I think it may be the easiest way for a beginner. It doesnt unlock boot loader but it roots your phone and gets 2.3 on it. Good luck
http://forum.xda-developers.com/showthread.php?p=11087674#post11087674
arastamon said:
Try and follow these instructions, I think it may be the easiest way for a beginner. It doesnt unlock boot loader but it roots your phone and gets 2.3 on it. Good luck
http://forum.xda-developers.com/showthread.php?p=11087674#post11087674
Click to expand...
Click to collapse
Thanks.
The phone I have already has an unlocked boot loader (there is an "unlocked" lock image below the nexus image upon reboot).
I believe returning to stock is as easy as downloading a factory N1 image, re-naming it to update.zip (or is it passimg.zip?) and running it from the boot loader...right?
I'm actually afraid to do this for fear of bricking this thing. All I want to do is go to a stock version of Android from the current 2.1-update1 Build EPE54B rom that came with this N1 so I can OTA up to the current 2.2.2 (or whatever) official google version is out. I'd like to go OTA from here on out, which the phone will not do now (stuck on 2.1 and saying "your software is up to date").
Is it as easy as what I suggested or am I a mega-noob?
Sorry for giving you the wrong info, I miss read the thread. I havent ever unrooted would hate to give you the wrong advice on the proccess. Sorry Im not more help
Since you are rooted and nervous about bricking your phone you can do this.
Flash a custom recovery if there is not one already on the phone via rom manager. Then in rom manager back up your rom (nandroid) . There is even a stock rom in rom manager that you can download and install all in rom manager. That will put the default recovery back as well. The phone will then the OTA's to the latest one.
Or you can just flash any other rom etc. It is really hard to actually brick the phone.
Sent from my Nexus One using XDA App
Thanks. Downloaded the Rom Manager, and guess what? The phone isn't rooted (I don't know anything about it .... just received it used from eBay).
The boot loader is definitely unlocked though and it's stuck on 2.1.
I will figure out the one-click root and go from there. Is that the best advice?
ericshmerick said:
Thanks. Downloaded the Rom Manager, and guess what? The phone isn't rooted (I don't know anything about it .... just received it used from eBay).
The boot loader is definitely unlocked though and it's stuck on 2.1.
I will figure out the one-click root and go from there. Is that the best advice?
Click to expand...
Click to collapse
I would go that route if I was you. It is very quick and simple and noob friendly. You could also use the guides the other posters put up to learn some things as well.
Not sure why your phone is "stuck" at 2.1 in the first place. But yeah rooting/rom manager should do the trick quickly and easy.
Turns out I was able to install superuser, so it's rooted. Not sure why Rom manager complained about it not being rooted.
This is a pain in the ass so far. I will just try to flash to a ~light~ 2.3 ROM. Don't want a bunch of battery draining stuff. Recommendations?
Also, I still want to go to bone stock so I can get google OTAs. Oh well. Maybe I'll figure it out one day.
ericshmerick said:
Turns out I was able to install superuser, so it's rooted. Not sure why Rom manager complained about it not being rooted.
This is a pain in the ass so far. I will just try to flash to a ~light~ 2.3 ROM. Don't want a bunch of battery draining stuff. Recommendations?
Also, I still want to go to bone stock so I can get google OTAs. Oh well. Maybe I'll figure it out one day.
Click to expand...
Click to collapse
The 2.3 ROMs aren't really "ready" yet, and I don't know if I would really recommend them to a new user. Very buggy. If you can get ROM Manager to work (which should be as easy as installing it from the Market if you have root), then go to "Download ROM" and find your way to CyanogenMod 6.1.1. It will ask you if you want to install gapps as well, and you should select yes.
Once a phone has been unlocked and had custom roms installed on it, there's no way to ever go back to completely stock with OTA updates unfortunately. CyanogenMod is probably the cleanest and most supported rom you can find, but another would be Enomther's (http://forum.xda-developers.com/showthread.php?t=614427).
PrawnPoBoy said:
The 2.3 ROMs aren't really "ready" yet, and I don't know if I would really recommend them to a new user. Very buggy. If you can get ROM Manager to work (which should be as easy as installing it from the Market if you have root), then go to "Download ROM" and find your way to CyanogenMod 6.1.1. It will ask you if you want to install gapps as well, and you should select yes.
Once a phone has been unlocked and had custom roms installed on it, there's no way to ever go back to completely stock with OTA updates unfortunately. CyanogenMod is probably the cleanest and most supported rom you can find, but another would be Enomther's (http://forum.xda-developers.com/showthread.php?t=614427).
Click to expand...
Click to collapse
Thanks. Well, I'm a total idiot. My passion.zip was passion.zip.zip. Nonetheless, the FAQ .zip original image file was "older than the currently installed version."
I'm done. I'm just going to play in the rooted 2.3 world. Currently downloading CyanogenMod's latest nightly for passion.
So, I am curious. Does this file I'm downloading update the radio and everything else? I'm certain the firmware versions for the radio, etc, are outdated.
Thanks.
EDIT: On second thought, is there a large reason not to go with a nightly? The latest stable version is two months old...I want clean and fast with minimal battery drain, etc.
You can always go back to stock and get the OTAs from Google. Only thing you can't do is relock the bootloader. ALWAYS can do it.
Sent from my Nexus One using XDA App
ericshmerick said:
EDIT: On second thought, is there a large reason not to go with a nightly? The latest stable version is two months old...I want clean and fast with minimal battery drain, etc.
Click to expand...
Click to collapse
The only reason not to go with the nightly build is stability. CM7 isn't ready for general use yet, and there are a lot of problems still. Last time I used it the phone app was almost completely unusable and would lock up whenever someone called. It doesn't hurt to try it out though. You can always flash something else if it's not stable enough for you.
albundy2010 said:
You can always go back to stock and get the OTAs from Google. Only thing you can't do is relock the bootloader. ALWAYS can do it.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Nope, this isn't true. Once the signed boot loader is replaced, there's no more OTA's. You can get the notification that an update is available, but they wont install. Once the clockwork or ra_recovery are installed, OTAs will never work again. There is currently NO way to go back to 100% stock on a Nexus One.
Jesus. I'm going to jump off a bridge.
I successfully installed the STABLE CM6 update (radio update, google apps). My GD N1 keeps rebooting.
WHERE can I find a stable 2.2.2 or 2.2.1 stock ROM and end this madness. All I want to do is use this phone. It's currently possessed.
(I'm beginning to think it's defective...)
ericshmerick said:
Jesus. I'm going to jump off a bridge.
I successfully installed the STABLE CM6 update (radio update, google apps). My GD N1 keeps rebooting.
WHERE can I find a stable 2.2.2 or 2.2.1 stock ROM and end this madness. All I want to do is use this phone. It's currently possessed.
(I'm beginning to think it's defective...)
Click to expand...
Click to collapse
its not defective and at this point its just a matter of time until you fix it.
If you still want to be stock, ignore below and follow the links to restoring the stock rom above.
a) do you have a custom recovery installed? (i.e a nice navigable menu) if not flash one from a terminal/shell (on your desktop) in fastboot mode (power+trackball to start the phone, choose fastboot)
b)since you dont have much to lose, wipe everything after rebooting into recovery mode.
c)flash any ROM that works with your phone. (the LCD nexus ones need a different version I think)
When you install a stock rom it overwrites the custom recovery everytime it boots. It always does this. The unlocked boot loader is irrelevant the OTA's.
He or anybody else can flash a stock rom and get the ota.
Sent from my Nexus One using XDA App
ericshmerick said:
Jesus. I'm going to jump off a bridge.
I successfully installed the STABLE CM6 update (radio update, google apps). My GD N1 keeps rebooting.
WHERE can I find a stable 2.2.2 or 2.2.1 stock ROM and end this madness. All I want to do is use this phone. It's currently possessed.
(I'm beginning to think it's defective...)
Click to expand...
Click to collapse
Try this: http://www.shipped-roms.com/downloa...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
Here's the reply an Acer representative posted on Acer ANZ Facebook page:
"the A501 update has two more security patch integrated hence the slight delay on the update. The date is very likely to be tomorrow, that the first batch of users are going to receive FOTA update notification. Australia & New Zealand are amongst the first countries with the updates made available. Appreciate your understanding and hopefully the update will be with you shortly.".
This was posted around 3.30 PM of the 09/19 (UTC).
Just remember...
DON'T RUSH TO APPLY IT OR YOU'LL LOSE ROOT!
Wait for the devs to modify the OTA and take out the new bootloader and recovery...
This is like the millionth time I've read that 3.2 is unrootable... LoL Repetita iuvant
chiasottis said:
This is like the millionth time I've read that 3.2 is unrootable... LoL Repetita iuvant
Click to expand...
Click to collapse
Considering how many idiots have flashed it and then come in here crying about it, it bares repeating.
So, in your opinion, is everyone that flashed the 3.2 an idiot or just those that are now crying about it?
mac4402 said:
So, in your opinion, is everyone that flashed the 3.2 an idiot or just those that are now crying about it?
Click to expand...
Click to collapse
Very good question. I updated fully knowing I would loose root, however I have full confidence that the devs will work it out.
Sent from my A500 using xda premium
mac4402 said:
So, in your opinion, is everyone that flashed the 3.2 an idiot or just those that are now crying about it?
Click to expand...
Click to collapse
The ones that are crying about it, obviously.
After searching on this forum and others, I updated to 3.2, at the time I could not find anything stating that you couldn't root it, but also nothing saying you could. I did however see a few posts from people doing previous upgrades saying that they managed to maintain root. At the time I realized there was a risk I wouldn't be able to root it, but it seemed likely I would. I also figured that if I couldn't root it, at least I could always flash back to 3.1 and root that.
Unfortunately I was wrong on both counts. Since that time I, and others, have made sure that anyone who asks is very aware of the risks so that others don't make the same mistake that I did.
I'm not really complaining though, I do have full confidence that 3.2 will be rooted in time, and while I enjoy having a rooted tablet, and use many applications that require it, not having root is not a deal breaker for me. and I still enjoy the tablet (though I must say the ads are drivng me nuts!)
I guess this is what I get for being an early adopter.
Looks like that was true. Downloading now on my A501...
I'm calling it "Acer Payback" for originally giving us the most easy to root device I've ever seen
Besides, anybody who roots and installs a custom recovery should know...Never take an OTA factory update, or at least be cautious about doing it.
One poster on another forum, was advised by Acer Support to do a factory reset to roll back to factory
I'm no rocket scientist, but doesn't that involve using that pinhole by the rocker?
Anybody try this yet? Results?
Not sure about what your question means... Update wouldn't install ("update not valid" error), so I did a Factory Reset: Settings -> Privacy -> Factory Reset (backup your internal SD as it'll be formatted). After that the update completed fine.
First impressions: snappier; some stuff (like keyboard) looks crispier on screen; more stable networks; new movie editor; etc.
Definitely a huge improvemente over 3.0.1.
So guys.. could anyone say what should i do to take safe OTA update while i have rooted a501 HV hc3.2 CWM? What are steps to do this not bricking our tab?
As guys said i could wait for way to root stock rom.
This is a judgement call. Basically, if you're happy being rooted, and you're running a custom rom with 3.2, I really see no need to revert back to stock, unless you have a lot of funky issues.
Personally, I wouldn't look forward to setting things up all over again, then having to wait till the devs com eup with another root, which may not be as easy as before. Not to mention I would lose ad-hoc support along with a couple of root required apps.
But if you have issues, then by all means, run the OTA.
If it ain't broke, don't fix it.
Moscow Desire said:
if you're happy being rooted, and you're running a custom rom with 3.2, I really see no need to revert back to stock
Click to expand...
Click to collapse
Reality call: not everyone wants to flash a custom rom. I've been flashing roms on WinMo, then Android for years and I've come to the conclusion that, no matter what, stock is better. The only time custom may be preferable is once the device isn't anymore updated officially.
As a side note, please notice that we A501 users were still running 3.0.1 prior to this update and, as you know, that ROM was terrible. This is why I preferred updating immediately (and having, finally, a device that works well) without waiting for root and other mods, which I can live well without.
You could download the FOTA and modify it to remove the new bootloader and recovery and get it rooted, like ezterry did with the A500 version. Maybe try contacting him on exactly what to modify...
chiasottis said:
Reality call: not everyone wants to flash a custom rom.
Click to expand...
Click to collapse
No reality call needed . If you had looked at the guys post, he/she is running Honey Villain3.2, which I believe is a custom Rom. The post was wether or not there was a need to revert back to a non-rootable factory rom, without taking a chance of things going bad.
I really couldn't tell you about 3.0. It lasted about 20 minutes after I bought my 501. To say that "3.0 was a terrible Rom", and then say "Stock is better", is a contradiction in itself.
Flashing any rom, should be a personal choice, of course there are pro's and con's which each person has to decide. And they should do their homework beforehand.
So really, there is no need to get "snippy"
But then again, there are always trolls about
Moscow Desire said:
No reality call needed . If you had looked at the guys post, he/she is running Honey Villain3.2, which I believe is a custom Rom. The post was wether or not there was a need to revert back to a non-rootable factory rom.
Click to expand...
Click to collapse
Ops! Didn't see that post; I thought you had come here to instruct us to discard stock in favor of custom. Sorry.
Moscow Desire said:
So really, there is no need to get "snippy"
Click to expand...
Click to collapse
I didn't get "snippy". I'm just tired to read, every single time there's some problem, "flash a custom" as the only solution. It wasn't your case, though, sorry.
No problemo.
But as you say, flashing is not a cure for everything. But for those of us who like to tweak things, it's nice to know we have that choice.
I just wish people would read about these things, before they get themselves in trouble.
Or the best is "I rooted, now what?"
Or, "I didn't see my exact model, but I flashed one that was close".
yea thats what i meant. I had rooted my device cuz 3.0.1 was awful. Again, i have to roll back to 3.0.1 since i have instaled 3.2 ( some factory default ??) Or what? And as you gays said Id like tu be sure before i start doing anything in this subject.
miszi said:
i have to roll back to 3.0.1 since i have instaled 3.2 ( some factory default ??)
Click to expand...
Click to collapse
Yes, you must go back to stock to update.