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
Related
I have a question I've been trying to resolve looking through the threads and have been unable:
I have a g1 that's rooted running android 1.5, and from what I can tell its either on the official t-mobile firmware or the developers firmware... I want to upgrade to android 1.6 mostly just for the text to voice and the voice navigation in google maps. I don't really want to load custom roms though... Is there anyway to load into android 1.6 and keep root, but have everything else the standard firmware?
developer.htc.com/adp.html
You can grab the official ADP1v1.6 firmware and write that to your device for a stock-but-root system image. (note: stupid people will tell you that it doesn't have root. They are incorrect, it most definitely DOES.)
lbcoder said:
developer.htc.com/adp.html
You can grab the official ADP1v1.6 firmware and write that to your device for a stock-but-root system image. (note: stupid people will tell you that it doesn't have root. They are incorrect, it most definitely DOES.)
Click to expand...
Click to collapse
It just gives the impression of not having root by flashing the stock recovery (which many people consider root for some reason)
oh lovely, after following those steps. The radio went fine the phone rebooted fine, but after the recovery image, the phone hangs on the android screen for a long time, and then pops up with continues force close error messages. I also can no longer boot into recovery it gives me a picture of a phone with an exclamation point.
Anyone have any ideas?
oh n/m. That exclamation point screen was in fact the recovery screen, it was different before i installed this. I formatted the memory card and wiped the data, and that seemed to do the trick, I'm up and running in 1.6 developers build. thanks guys =-)
Yeah, when I read your previous message I was about to suggest that...
Newbie-ish question
Hey all,
I know this sound a bit amateur, but I was just wondering if it were possible to flash the same G1 Dev Rom onto my Rogers HTC Dream running the newest "perfect" firmware. I would imagine that the HTC one is officially signed so the phone wouldn't have any trouble accepting this...can anyone confirm? I just wanted to make sure before I go ahead and do anything as I'm new to the whole Android thing. Thanks!
n64_ali said:
Hey all,
I know this sound a bit amateur, but I was just wondering if it were possible to flash the same G1 Dev Rom onto my Rogers HTC Dream running the newest "perfect" firmware. I would imagine that the HTC one is officially signed so the phone wouldn't have any trouble accepting this...can anyone confirm? I just wanted to make sure before I go ahead and do anything as I'm new to the whole Android thing. Thanks!
Click to expand...
Click to collapse
You're right. You're definitely an amateur
1) There is *no such thing* as a "G1 Dev". There is an "Android Dev Phone 1" (aka "ADP1"). G1 and ADP1 are both HTC DREAM, as is the thing that was sold by robbers (although the robbers-crippled dream has some minor differences).
2) Though signed, it still won't write onto your phone since it is signed with a DIFFERENT SIGNATURE.
3) If you *did* manage to write it, you would be effectively bricked since the ADP1 kernel won't boot on the robbers-crippled-dream. At this point, it *might* be possible to write the same firmware that you already have on it again to fix the brick, but since nobody has gotten to this stage, it is unknown.
Haha glad I didn't go ahead and do anything stupid, then! Thanks for enlightening me!
Cheers
n64_ali said:
Haha glad I didn't go ahead and do anything stupid, then! Thanks for enlightening me!
Cheers
Click to expand...
Click to collapse
Don't worry, because of the incorrect signature, you couldn't have hurt it even if you tried.
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
For those who didn't dare to try... I got Froyo running on an AT&T version. All you need is to follow this guide: http://www.androidspin.com/2010/05/...-nexus-one-its-like-it-never-happened-almost/
Flash the ERD79 Release, update to EFE27. Then run the Froyo update through Stock recovery. 3G works fine, radio updated (I think?) and everything is fast.
thanks for your post. but the issue that most ATT N1 users are facing is updating to 2.2/Froyo from their non-rooted, bootloader-locked. devices.
vexingv said:
thanks for your post. but the issue that most ATT N1 users are facing is updating to 2.2/Froyo from their non-rooted, bootloader-locked. devices.
Click to expand...
Click to collapse
I think that rooting and unlocking the bootloader it's the way to go now, since like everybody has done it.
poorg said:
I think that rooting and unlocking the bootloader it's the way to go now, since like everybody has done it.
Click to expand...
Click to collapse
Translation:
"Everybody's doing it, come on. What are you, chicken?"
/peerpressure
I'm one that hasn't rooted, yet. Party due to my phone is less than two weeks old and I don't want to void the warranty just yet.
I just went from KangoRama to full wipe to Froyo...
Having owned several HTC phones, there's no way I'm voiding my warranty
Lot of trouble for nothing, if you are already rooted and have Amon's recovery. Just install Paul's Rooted Froyo and you've got the same thing, except with root.
rooting doesnt void hardware warranty
Experienced it
Froyo using AmonRa recovery - WORKS!
Followed some success off CM's forums in getting Froyo up and running on an AT&T N1. In fact it's been pretty error free (short of a couple apps not behaving with 2.2) and to top it off, no wipe needed.
Paul over on Modaco's site managed to pop up an image that is rooted and works with AmonRa's recovery. All I did was copy the zip to the SD card, ran recovery, flashed from SD, and voila! Froyo without having to painstakingly reinstall all my apps. No issues with 3G so far, but like all stock roms, there's no indication of running HSDPA unless you go into the about phone option in settings.
So far cooling off the hot day with some Froyo here.
Paul's Original Post on Modaco
Edit: And yes, if you didn't boot unlock your phone and want 2.2, then your only choice is waiting for the OTA to eventually hit you... when it goes public instead of press-only.
Are you able to view large images on your browser?
I know I'm not :S
http://forum.xda-developers.com/showthread.php?t=687256
update
I followed the guide and went from erd79 to ere27 but when trying to update to froyo my N1 would not boot completely. Ran adb logcat and watched the log and it looped running the same stuff over and over again.
x986123 said:
For those who didn't dare to try... I got Froyo running on an AT&T version. All you need is to follow this guide: http://www.androidspin.com/2010/05/...-nexus-one-its-like-it-never-happened-almost/
Flash the ERD79 Release, update to EFE27. Then run the Froyo update through Stock recovery. 3G works fine, radio updated (I think?) and everything is fast.
Click to expand...
Click to collapse
Yep, flashed the rooted version of FroYo, works great. Love it!!
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
Hi All, I just got my Nexus one off ebay and it appears its not rooted as i do not see the padlock icon and i also cannot run the nexus torch.
What im looking to do is revert back to the stock software and than do all the OTA updates myself.
Can someone help me with this ? Im not looking to root though.
Im running the ATT version of the Nexus one.
Thanks all for your help.
To be root or not
if you do not see the padlock, then you are root!!
hi, yes i know and i do not see the pad lock so i have a unrooted phone. Im trying to find out how i can install the stock software this way i can do the OTA updates myself.
Thanks
If there's no padlock and you're sure it's not rooted... why do you think it's not already stock?
Well its running gingerbread and i wanted to go back to froyo and than OTA the updates myself
If its not rooted, root it! What version you on currently?
Sent from my GT-I9000 using Tapatalk
Im on the Nexus one ATT version, running the most recent gingerbread OS.
2.3.6???
Sent from my GT-I9000 using Tapatalk
If it is, try root using this... http://apachejava.blogspot.com/2011/06/root-nexus-one-gingerbread-234.html
My dad using my nexus one, so i dunno much... So, is your bootloader unlock, if it is, then go ahead with the link above... Then S-OFF using BlackRose...
Sent from my GT-I9000 using Tapatalk
Check this!!
Might help you.
http://answers.unity3d.com/questions/56512/downgrading-google-nexus-one-from-android-gingerbr.html
If you don't see the padlock it means the bootloader is still locked. If you don't have the SuperUser app then you are more than likely NOT rooted. Sounds like a stock phone if you ask me. Why do you want to roll back to Froyo then update? Sounds like you are already where you want to be. It sounds like a case of reaching around your ass to scratch your elbow. Heh. If you try to OTA update it and it says you are up to date, I would suggest leaving it alone or just root it! Good luck!
Sent from A VAN DOWN BY THE RIVER!
zinner526 said:
Well its running gingerbread and i wanted to go back to froyo and than OTA the updates myself
Click to expand...
Click to collapse
Why? Is there a problem with what is currently installed? If it's working fine, then I would expect downgrading to a previous version and applying the updates would just get you back to where you are now. I'm not criticizing, just trying to understand what you're looking to achieve
If you mean stock as in "original" that isn't Froyo either. The Nexus One originally came with Eclair (2.1). If you don't have root, I'm not sure if you can downgrade or how safe it would be. I've seen mixed results with downgrading. The only way to do a complete flash would be with an unlocked bootloader or root + custom recovery.
If you don't want to root or unlock the bootloader, why not just do a full wipe and use the version you have on it? You could also root it temporarily to restore to an unrooted Eclair or Froyo, then apply the updates.
Thanks Narbir, I'm going to try this. Does it matter I have AT&T ?
I hope So. I m usng Voda uk. Don't really brother me by that.
Well the phone reboots often for no reason so i thought if i started from the factory installed software and go forward it would help.
How hard is it to root to install enclar and than go forward ? Unless someone has another idea for the reboot issue ?
Install the latest stock ROM in PASSIMG format (complete ROM, all the partitions). No need to go back to Eclair or Froyo.
Prepare for the possibility of it not helping at all, and your phone HW being faulty. If you have ADB set up - you can run "adb bugreport" after the crash, and look for "ARM9 has crashed" line in the log dump that comes. If you'll see them - no amount of ROM switching will help.
Not to sound pedantic, but you seem a little confused (OP). Why don't you start by reading the FAQs regarding rooting and unlocking the bootloader, and understanding the ROM installation processes.
Couple of fundamentals to get you started:
1. The padlock (or absence of) is no indication of whether you are rooted or not. It merely indicates whether your 'bootloader' is unlocked or not, which is a completely separate concept from rooting.
2. Easiest method of seeing whether you are rooted is to see if you have the 'SuperUser' app in your app drawer.
If your objective is to install a stock/default ROM, search for a 'PASSIMG' for the latest available firmware for your device. Search these forums or Google it. The procedure is fairly straightforward and only involves putting the file on your SD card - and will restore your phone to a stock usable state.
If you're interested in custom ROMs, the fastest way to get started is to use SuperOneClick to root (Google, please). Then go to the market and download ROM Manager and just follow the instructions!