i had a nexus one and was able to unlock the bootloader but i think i updated it to 2.3.4 and then tried to install CWM, which didn't work. i then discovered the antenna was not working correctly so i had to exchange the phone for another new one. once i get my new nexus one i was still thinking about installing CM7 and i just want to get some things straight about 2.3.4 and installing clockworkmod recovery.
will i be able to install CWM after i update my nexus one to stock 2.3.4? if not what is the highest stock build i would be able to do it with?
concerning the radio, if it is not possible to update to 2.3.4 and then install CWM i guess i'd have to update the radio by itself right?
You can unlock the bootloader and install cwm, or you can revert to an earlier version of Android, root, and then install cwm...
so i guess it's not possible to root and install CWM on 2.3.4? what's the latest version of android i would have to revert to for rooting and installing CWM?
There is no exploit for 2.3.4, so there is no easy root...
To downgrade, you have to do the passimg with a shipped image, and the most recent is FRG33. However, once rooted you can update all the way to 2.3.4 and keep root, if you do things in the right order...
You could also update to 2.3.3 and root and update to 2.3.4 keeping root - but the end result is the same...
You can also root 2.3.4 after unlocking the bootloader and flashing a custom recovery. From there, you would need to flash one of the su.zip files floating around (you may need a specific one for Gingerbread), which should remove the stock recovery checks (what replaces the custom recovery when you boot a stock install) and should add the necessary files for root access.
the first nexus one i received was on 2.2.1 so i guess if i plan on installing CM7 i should just keep in there and not bother upgrading anything (maybe the radio only)? just want to make sure where i stand so someone could help me accomplish these things. i know how to unlock the bootloader and i think i'll be fine installing CWM so what order should i:
unlock the bootloader
upgrade the radio (i guess i don't have to do this if i upgrade to 2.3.4)
install CWM
root
upgrade to 2.3.4
install CM7
i'm just making sure i know what i'm doing before i get my replacement nexus one and while i have attempted searching for answers i haven't been able to find the specific order or answer to my question. if anyone can correct any mistakes or assumptions i've been making please let me know.
If you are unlocking the bootloader, there is no need to root the current android install. The whole point of rooting the phone is so you can get the custom recovery on there so you can load CM on the phone. Since you are unlocking the bootloader, you can load the custom recovery using fastboot, then boot into it, wipe the phone and flash CM (and gapps).
And if it is a replacement, it will most likely be running the 5.08 radio, which seems to be the best one for Gingerbread.
So it would be:
Unlock bootloader
flash clockworkmod
boot clockworkmod (select the bootloader screen and then recovery, don't reboot)
wipe phone
flash CM and gapps
reboot
????
profit
DarkKnight62 said:
unlock the bootloader
upgrade the radio (i guess i don't have to do this if i upgrade to 2.3.4)
install CWM
root
upgrade to 2.3.4
install CM7
Click to expand...
Click to collapse
You don't need to upgrade to 2.3.4 unless you want to upgrade the radio and hboot. Of course, you can upgrade them without updating the OS, though upgrading them with OS will be safer.
ok, now that i know that installing CM7 will root my phone if i do it by unlocking the bootloader and installing CWM i am wondering if my phone will be rooted once i restore my nandroid backup that i will make (of stock 2.3.4 android) right before i install CM7?
No. Root is separate from unlocking your bootloader and whatever recovery you are running. Root is at the OS level. Most custom firmwares come pre-rooted. That is, they contain the software needed to allow you to escalate your priveledges to root level. Stock firmwares, do not have this additional software, and anytime you get an update for stock, it will replace everything you had with your previous install, which will make you lose root if you had it.
So, if you install CM7, it will be rooted, but if you restore your stock 2.3.4, it will become unrooted (because it was unrooted when you made the backup).
What is your final plan for software on the phone? Stock 2.3.4, stock 2.3.4 with root, CM7? What is the point of restoring your nandroid of 2.3.4?
Related
I've been doing a lot of reading and searching but still can't find a definite answer...
My understanding is that I need to root the device to flash a custom rom
But from the instructions for noobs, they don't usually specify that I have to root
I assume that rooting is a pre-requisite for everything...but then some roms advertise that they are rooted (for example, LeoFroYo)
So it the rooting process tied to the rom itself and I have to root everytime I flash a new rom (if the rom is not rooted)? Or is it universal like HSPL on WinMo?
Rooting is per rom. What is required to flash a custom rom is having an unlocked bootloader and a custom recovery image. From there you can flash a pre-rooted rom.
The root instructions assume that you're gonna keep using the stock version with root abilities added on top. Whereas if you're using flashing something like CM, that already has root and OS tweaks.
FaJu said:
Rooting is per rom. What is required to flash a custom rom is having an unlocked bootloader and a custom recovery image. From there you can flash a pre-rooted rom.
The root instructions assume that you're gonna keep using the stock version with root abilities added on top. Whereas if you're using flashing something like CM, that already has root and OS tweaks.
Click to expand...
Click to collapse
Thanks! So does that mean when I get my phone out of the box, I have to root it once over the stock rom before I can flash any custom rom?
You need to root the phone originally and flash a custom rom. The "pre-rooted" means the rom is rooted. So if you flash that rom then you wont lose root. If you flash an un-rooted rom then you will lose it. So go through the steps and unlock your bootloader then flash a custom recovery image. Then decide which rom you wanted and flash it. All the custom roms are rooted.
futango said:
You need to root the phone originally and flash a custom rom. The "pre-rooted" means the rom is rooted. So if you flash that rom then you wont lose root. If you flash an un-rooted rom then you will lose it. So go through the steps and unlock your bootloader then flash a custom recovery image. Then decide which rom you wanted and flash it. All the custom roms are rooted.
Click to expand...
Click to collapse
That explains it. Thanks for your answer
one more question:
I take it as when bootloader is unlocked, there's no way to lock it again? Not even flashing the stock boot image?
No, once you unlock the bootloader, it stays unlocked.
Just to be clear here you don't _have_ to "root your phone once"
On _most_ phones you need an exploit to be able to get to the bootloader, this exploit is often referred to as rooting. After the exploit you generally have superuser access until you reboot, on some phone this may allow you to get at the bootloader and write anything you want there (E.G. an OS that give you superuser access at boot time)
However the N1 lets you issue the command "fastboot oem unlock" that unlocks the bootloader, from there you can flash a recovery image that will allow you to flash the main OS without having access to Google's release signing keys. Hence you _could_:
1. Bootloader unlock
2. Flash Custom recovery
3. Flash Custom OS
Without ever actually having "root" access, it just happens that most Devs prefer having root access available in both recovery and any custom rom they cook up.
Hi rooted my wildfire with unrevoked. Now i would unroot it to update with OTA and, I hope before Xmas, with Froyo.
In Superoneclick thread i read:
"Some devices have a NAND lock. SuperOneClick will only give a Shell root until you remove this lock.
The following phones can use unrevoked to remove this lock:
[...]
- HTC Wildfire (HTC Buzz)"
If i'll install Superoneclick on my Wildfire rooted with unrevoked (and i think with nand unlock), will I be able to unroot in order to install OTA and then re-root?
Froyo still didnt hit WildFire, you can use this tool to download the OTA update manually
http://forum.xda-developers.com/showthread.php?t=786352
You can unroot by simply installing a corresponding RUU firmware (ie stock). This reflashes recovery, removing root.
However, I would strongly recommend you stayed away from returning to stock; we can't root stock 2.2 yet (not that it's even out yet). If you want to taste Froyo, simply flash Wildpuzzle, Cyanogen or Openfire (Wildpuzzle is closest to stock).
Furthermore, to reply to your post's question directly; there is no point in installing SuperOneClick. If you're already rooted, you can flash ROMs all you like, but without an AUFS kernel or similar, you still can't live write to system. There is no point to adding more root tools, to simply unroot, wait for Froyo, and then to not be able to reroot. If what you're wanting to do is update your Eclair OTA, so you don't have to wipe it but still get the update, then just OTA it in it's current state, and if needs be, unrevoke it again. There's little rigmarole necessary. Personally, the OTA does very little, though as I run custom like most on here, I get the latest Eclair build in my Wildpuzzle.
Do you have to change the N1 RECOVERY to enable ROOT?
No.
You can root with superoneclick (http://forum.xda-developers.com/showthread.php?t=803682) or unlock your bootloader and root it by hand (http://forum.xda-developers.com/showthread.php?p=13446089)
Ferran
Excellent! Just what I wanted to hear!
C64c said:
Do you have to change the N1 RECOVERY to enable ROOT?
Click to expand...
Click to collapse
Actually, it's the opposite: You have to root to change recovery, unless you unlocked bootloader.
Unless something has changed in the past few days, you DO need to change recovery to root. The only way to root stock GRJ22 is to flash SU.zip, and you can only do that with non-stock recovery.
GnatGoSplat said:
Unless something has changed in the past few days, you DO need to change recovery to root. The only way to root stock GRJ22 is to flash SU.zip, and you can only do that with non-stock recovery.
Click to expand...
Click to collapse
Yes, correct. But how are you going to flash a custom recovery without root?
As was said before, if you are on GRJ22, you only have two options to root:
1) unlock the bootloader, install a custom recovery and flash ChainsDD's Superuser update;
2) downgrade to Froyo by flashing one of the leaked Froyo shipped ROM (FRG33 or FRG83) via the bootloader, root that and update to Gingerbread the proper way...
I agree, you need root before you can flash a custom recovery.
Your option #2 is what I used. I downgraded to Froyo, then upgraded to 2.3.3, then rooted with Gingerbreak, installed custom recovery using clockworkmod app, and THEN upgraded to 2.3.4 with stock recovery folder removed which allows you to install SU.zip.
It's a few extra steps over unlocking the bootloader, but it doesn't take long and may be worth doing to not have to unlock the bootloader.
GnatGoSplat said:
I agree, you need root before you can flash a custom recovery.
Your option #2 is what I used. I downgraded to Froyo, then upgraded to 2.3.3, then rooted with Gingerbreak, installed custom recovery using clockworkmod app, and THEN upgraded to 2.3.4 with stock recovery folder removed which allows you to install SU.zip.
It's a few extra steps over unlocking the bootloader, but it doesn't take long and may be worth doing to not have to unlock the bootloader.
Click to expand...
Click to collapse
Yup. Sounds good.
Or, you can just unlock your bootloader and never have to worry about losing root ever again... and besides, I haven't heard of any individual saying that HTC refused warranty service because of an unlocked bootloader...
My bootloader has been unlocked for months!
hey guys,
i have a nexus one 2.3.3 when i try to update to 2.3.4
it says (ERROR status 7) in the bootloader. can anyone help?
thanks.
Have you done anything to the phone's original software? Custom kernel, rooting, custom recovery, etc?
The error 7 basically means that the signature checks don't match and it doesn't upgrade to prevent bricking your phone.
Yes. I rooted and used to have cm7
Does it matter?
If you are already rooted, just flash a rooted version of 2.3.4. It can be found here.
http://forum.xda-developers.com/showthread.php?t=1061648
And yes, when you root the phone, you change the signature of the install, so the upgrade fails. It makes sure the signature matches, otherwise you could end up with a broken phone. (If it didn't check for signatures, it could apply the partial update to a froyo or eclair version, and prevent the phone from booting.)
If you really want the OTA update, you would have to remove everything you did to root the phone and flash the update... and unless you unlocked the bootloader, there currently isn't a way to root 2.3.4.
bassmadrigal said:
If you are already rooted, just flash a rooted version of 2.3.4. It can be found here.
http://forum.xda-developers.com/showthread.php?t=1061648
Click to expand...
Click to collapse
You really should specify that the ROM you are pointing to is not a stock ROM, and any further OTA's will not install on that ROM.
bassmadrigal said:
And yes, when you root the phone, you change the signature of the install, so the upgrade fails.
Click to expand...
Click to collapse
NOT true at all. Rooting has no impact on whether you can receive and install OTA updates.
Here are the main things that will prevent an OTA from installing:
1) a custom kernel;
2) if you remove pre-installed applications from the /system partition
3) if you flash a de-odexed ROM (...that is why the ROM you linked to is not really a stock ROM.)
Rooting makes not difference at all.
bassmadrigal said:
If you really want the OTA update, you would have to remove everything you did to root the phone and flash the update...
Click to expand...
Click to collapse
NOPE.
If you have a stock ROM, all you have to do is make sure you have a stock kernel, and have all the pre-installed applications in your ROM. Nothing else.
If you have a de-odexed "stock" ROM, rooted or not, there is no way you can flash an OTA update (unless you de-odex it, repack it, and then flash it...)
I read on a number of sites that people were getting the Status 7 error due to them rooting and only rooting.
The first time I rooted my phone I put CyanogenMod on there, so I never had any experience with trying to get OTA updates.
But thanks for the info, I will store it and remember it for future reference.
bassmadrigal said:
I read on a number of sites that people were getting the Status 7 error due to them rooting and only rooting.
[snip]
Click to expand...
Click to collapse
I suspect it is because they "rooted" by flashing a "stock" ROM like the one to which you linked. Although it looks stock and, for the most part, behaves like a stock ROM, it is not, as it is de-odexed. If someone want to flash a stock Gingerbread ROM, they need to flash one like the first link in this thread: http://forum.xda-developers.com/showthread.php?t=968396
That ROM is not de-odexed. To get root, you just need to flash the superuser zip over top, and you have a rooted-but-otherwise-totally-stock ROM, which will receive and install all OTA updates.
got nexus one back last week and was wipe ndput back to stock.
Build number GRJ22. Went to unlocker and cannot find this build version listed.
Figured it has build not listed from the older versions.
any idea whr I can get this to superboot phone
thanks
Lookq like last Superboot was for GRI40, so no GRJ22 yet.
http://android.modaco.com/topic/298...i40-rooting-the-nexus-one/page__hl__superboot
You can try that way:
PASSIMG to downgrade to FRG33, so you're back to 2.2, then root and upgrade; as described here http://forum.xda-developers.com/showpost.php?p=13762825&postcount=17
I think you can find too pre-rooted stock 2.3.5 ROM, so you need to downgrade, root , flash custom recovery, and flash a pre-rooted up-to-date stock ROM
You could also just flash Superuser 2.6.3.2 update.zip in recovery, which will get you root, and from there make changes in build.prop by setting ro.secure=0.
I suspect they're just looking to use Superboot to unlock the bootloader, and don't really care about the insecure bootloader...
Superboot doesn't unlock bootloader, all it does - it runs insecure boot that allows root ADB shell.
OK, to better state my thoughts:
I suspect that this is just a means to an end (i.e. root), and that achieving ro.secure=0 isn't part of the big picture...
Ah, now I understand what your point, and agree.