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.
Related
Can i root my froyo 2.2 keep the stock rom and receive OTAs? I basically want to have root without any modded rom's and be able to get OTA updates.
as long as you have the stock recovery you're ok for OTA
OTA updates will remove root, so you'll have to re-root.
You need stock recovery to apply OTA's and custom recovery to root.
Is your bootloader unlocked?
________________________
N1 w/ XDA App
I searched forum for that solution, but without results.
It would be nice to have tutorial for this.
Sent from my Nexus One using XDA App
No my bootloader is locked
So then you'll be able to use an OTA but you'll lose root. With a locked bootloader that would be bad. Best to not use OTAs and instead rely on pre-rooted updates posted here. Of course you may need a custom recovery for that.
Sent from my Nexus One using XDA App
In regards to stock recovery, where can i get a copy of it. I wanted to return to stock recovery to get the OTA so i don't have to perform manual updates. I currently have Amon's recovery.
C64c said:
In regards to stock recovery, where can i get a copy of it. I wanted to return to stock recovery to get the OTA so i don't have to perform manual updates. I currently have Amon's recovery.
Click to expand...
Click to collapse
The "security fixes" in FRF91 include patching the exploit used to gain root with the bootloader locked.
So, if you revert to stock recovery and then install the FRF91 OTA - you will not be able to regain root unless you go back to a previous passimg, update to FRF85B and then install a repacked, pre-rooted FRF91 through custom recovery.
Basically, you can't have root on a fully stock FRF91 OTA
So to get root we now need to void our warranty? That's annoying.
No
From FRF91 you need to PASSIMG back to an earlier build, then update to 85B. The root with locked bootloader method works from there.
Then, as stated above, you can use a re-packed update to FRF91 to keep root. You just can't use the OTA to FRF91 and keep root.
________________________
N1 w/ XDA App
Can I meet up and get you to do this, willing to pay. Have a rooted running frf50, tried everything to het this loaded, no luck?
Been all over the forums and in order to flash Amans recovery, Modaco requires a rooted device and superboot. Well, we know superboot isn't available for FRF91 yet and to flash requires root.
How the heck does anybody flash a recovery image without root?
The goal here is to get root and and this point don't really care if the bootloader is locked or unlocked. Just need root access to run certain apps.
Was planning to boot into recovery, then run the passion update for root access, but this is a catch 22.
If you do a search... yadda yadda....
You must downgrade to frf83/5? i forget the exact number. There's at least 3 different posts on general...
fark it, start here, and then SEARCH.
http://forum.xda-developers.com/showthread.php?t=717870
I was in the same boat as you. I flashed the RA Recovery and although it said it was flashed successfully, when I booted into recovery, i saw the stock recovery. Was on FRF91. So took a gamble and flashed the latest superboot from modoco. Cant remember if it was FRF83 or FRF85B and then reflashed RA recovery. It worked
Once in RA recovery I wiped and flashed a cooked ROM.
Already tried EPE76 and was screwed lol. Ran the universal update back to FRF91. Looks like I'm going to have to downgrade again unless there's another solution. Would like to know how to flash a recovery rom without root.
Big_O said:
Already tried EPE76 and was screwed lol. Ran the universal update back to FRF91. Looks like I'm going to have to downgrade again unless there's another solution. Would like to know how to flash a recovery rom without root.
Click to expand...
Click to collapse
Well I was on FRF83 then recieved the FRF91 OTA from Google.
As there was no FRF91 superboot on Modaco i flashed the FRF83 version.
I also kept the universal update in my SD card just in case but it went smooth for me.
This bites. There's no clear cut guide how to root. Just bits and pieces of information and a complex labyrinth of instructions. Most of the info is outdated and requires a downgrade, then upgrade, then recovery. The recovery requires root and the whole goal is root lmao. It's no wonder there are almost daily posts of guys trying to root and/or unlock bootloaders but nobody knows how to explain the procedure. The stickies have dead links, and everyone says "hit the search button" and not one person has created a sticky for rooting instructions on the FRF91. I actually downgraded to EPE76 and got stuck due to the inability to upgrade to anything except back to FRF91 AT&T stock.
It would be nice is someone actually took a few minutes to explain a working procedure how to downgrade, upgrade, and use recovery to gain root. Really don't care about the bootloader. Somebody will get rich with paypal donations and I'll be the first to donate.
Big_O said:
This bites. There's no clear cut guide how to root. Just bits and pieces of information and a complex labyrinth of instructions. Most of the info is outdated and requires a downgrade, then upgrade, then recovery. The recovery requires root and the whole goal is root lmao. It's no wonder there are almost daily posts of guys trying to root and/or unlock bootloaders but nobody knows how to explain the procedure. The stickies have dead links, and everyone says "hit the search button" and not one person has created a sticky for rooting instructions on the FRF91. I actually downgraded to EPE76 and got stuck due to the inability to upgrade to anything except back to FRF91 AT&T stock.
It would be nice is someone actually took a few minutes to explain a working procedure how to downgrade, upgrade, and use recovery to gain root. Really don't care about the bootloader. Somebody will get rich with paypal donations and I'll be the first to donate.
Click to expand...
Click to collapse
just read the sticky for rooting without unlocking bootloader in the android dev section
its up to date. if you unlocked your bootloader, the outdated root guides are fine to use even now. you need to ensure you flash a custom rom so the recovery isnt replaced on reboot
Hi All,
Was just looking into the prospect of rooting and I came across a post that basically responded to a guy asking whether subsequent OTA/Official updates would revert the root. the response was:
this might well happen. To be sure that this won't happen, don't update, or wait for a rooted version of the update to be released
Click to expand...
Click to collapse
It's the bit in bold that's got me wondering. I have my Nexus running stock ROM but rooted (with locked bootloader). I have the problem with the WiFi which 2.2.1 claims to fix.....and I just wasting time thinking that this update might get released as a rooted version so I can just install and not worry about losing root?
Any help gratefully received.
Cheers
1. Already released as a rooted version (check the ROM section)
2. Really easy to root with rageagainsthtecage ...
Right I can ask you the question then......with the rageagainstthecage root method, is there anyway to install the update without flashing a new ROM...I'm ok with stock.
If you're rooted - install custom recovery and install pre-rooted ROM.
Or try to apply the stock update through stock recovery, if you have it.
Wiggz said:
Right I can ask you the question then......with the rageagainstthecage root method, is there anyway to install the update without flashing a new ROM...I'm ok with stock.
Click to expand...
Click to collapse
Just install the OTA - it will unroot you.
then root with "rage"
check out modaco, he's got frg83 completely stock with root. just flash using custom recovery. I didnt do a wipe so everything stayed the same just updated to 2.2.1 and yes it seems the wifi issue was fixed.
Just get the stock rooted from geo411m's rom!
http://forum.xda-developers.com/forumdisplay.php?f=559
The links here will also do it in 2 steps from custom recovery:
http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=8419658&postcount=194
The geo411m link is a deodexed ROM and the one in the link above is not deodexed. Either way you get the fixes of the newer version.
Going forward, think of it this way with future updates:
If you apply the OTA, intending to lose root and then re-root, you always run the risk that all avenues of rooting (other than unlocking the bootloader) have been closed by the new ROM.
If you apply an update repacked for custom recovery, you don't have to worry whether the root exploit you used last time will still be valid.
nexusdue said:
Just install the OTA - it will unroot you.
then root with "rage"
Click to expand...
Click to collapse
Thanks for that - honestly not sure why I didn't think of it
Ahh found a flaw in my plan.....it seems that verification fails on my Vodafone Nexus One (UK). I'm guessing there isn't an upgrade path from Vodafone's Froyo update to this yet. Suppose I'll have to wait for Voda's 2.2.1
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?
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.