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
Related
I know the update was a security fix but am looking for a method to root while remaining as completely stock as humanly possible. I've never rooted before and am still completely stock now.
Best case scenario would be to gain root while leaving everything stock, boot loader, recovery, etc.. maybe even try one of them nice roms for the first time (i hear cyrogen is the best and yes I probably misspelled that)
Thanks
Sent from my Nexus One using XDA App
Same question
There's a couple of tutorials about this in another thread.
If I were you i'd follow one of them and also install a custom recovery. Then play around all you like with rooted roms, stock, custom or otherwise. Once you have a custom recovery you can flash anything. The only down side is that you won't be able to install any OTA roms. But to be honest they appear on XDA in a format you can use on custom recovery way way before you ever receive an OTA notification anyway.
Then if you're sure you only want a stock but rooted rom, then install that and then finally flash the stock recovery back.
However if you're sure you don't want a custom recovery and only want root, you can follow the first half of the same tutorials.
I myself have an unlocked bootloader, but if I didnt, I would root, install a custom recovery and never look back. If anything ever happened to my device i'd just flash the stock recovery and stock firmware and send it back.
Ok, thanks!
That's good information but I'm unsure if I want to unlock at the moment. Thanks but I'll wait a little longer to see if a solution comes out that this my needs.
Sent from my Nexus One using XDA App
viper2g1 said:
That's good information but I'm unsure if I want to unlock at the moment. Thanks but I'll wait a little longer to see if a solution comes out that this my needs.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
No, thats the point. You dont need to unlock to root OR put a custom recovery anymore. See here for example:
http://forum.xda-developers.com/showthread.php?t=710842
So you can root, put on a custom recovery, try different roms and then go back to stock, rooted or not, without unlocking the bootloader at all.
I see what your getting at, that's what I was looking for but wasn't sure it was working for FRF91 the last few posts in that thread indicated an unlocked boot loader last time I looked.
I thought the update was to fix the security hole that allowed that
Sent from my Nexus One using XDA App
I have read a lot of comments on the guide of how root the nexus without unlocking the bootloader and searched in other places but couldn't find an answer to my question...
I've got at&t version nexus unrooted and I updated it to FRF91 OTA.
can I use this guide to root it without unlocking the bootloader?
If I can, how do I do it? some people wrote that I need to use Passimg.zip
but I think It's for T-mo version only because at&t's version doesn't have the erf79 (I hope I wrote it right).
anyway I'm really confused. can someone please explain?
thanks
I've got at&t version nexus unrooted and I updated it to FRF91 OTA.
can I use this guide to root it without unlocking the bootloader?
Click to expand...
Click to collapse
Me too - same question... I didn't see any tuts for rooting FRF91 w/o unlocking the bootloader.
RashaMatt said:
Me too - same question... I didn't see any tuts for rooting FRF91 w/o unlocking the bootloader.
Click to expand...
Click to collapse
they should work in the same way as it did for FRF83 or FRF85B.. you could always try without harm
RashaMatt said:
Me too - same question... I didn't see any tuts for rooting FRF91 w/o unlocking the bootloader.
Click to expand...
Click to collapse
this link: forum.xda-developers.com/showthread.php?t=717870
is a guide of how to downgrade from FRF91 to FRF85 in an unrooted nexus.
that way you can use this tut and root it w/o touchnig the bootloader
EPE76 to frf85B
Hi,
I am back from frf91 ota to EPE76 by applaing passimg.zip. My question is how can I move to frf85B ? I've tried to download universal frf85B, change name to update.zip and go to recovery, but I only see exclemation mark. Please advise. Thank you.
Hey guys!
I received and installed the new Android 2.2 update over OTA. But I lost my root access. I tried rooting with Unrevoked: no success. So I'm asking if anyone knows how could I root my wildfire now.
Please help
Reading really seems to be a problem around here.
http://forum.xda-developers.com/showthread.php?t=882192
You can't root the OTA, htc updated the hboot, so wait until unrevoked release an updated version.
I think you'll have to downgrade to an older RUU and root to flash a custom froyo, but I think the new hboot prevents this.
Leaves me wondering why you guys waited for official froyo and then decide to root lol.
Sent from my HTC Wildfire using XDA App
kevin2516 said:
You can't root the OTA, htc updated the hboot, so wait until unrevoked release an updated version.
I think you'll have to downgrade to an older RUU and root to flash a custom froyo, but I think the new hboot prevents this.
Leaves me wondering why you guys waited for official froyo and then decide to root lol.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
For example, I waited for the official FroYo for stability. I had my phone rooted, and I had installed RUU sometimes too (1.37 or 2.10 cn), and then Unrevoked, because they can be rooted. So I didn't think that now, I couldn't root the official froyo, so I tried it as I had already tried RUU's and succesfully rooted.
Some people is saying that there were a lot of adverts/advices saying not to install RUU's or OTA's because then they can't be rooted. But I'm relatively new on this so I didn't even see those posts. There are a lot and I didn't read all of them, so I didn't know.
When I saw official FroYo was out I decided to install it to then flash Jacob's kernel and being root. Before that, I had finally went back to stock 2.1, rooted and OC, because custom roms are often unstable.
Now, I'm waiting resigned to be able to root it and forget this nightmare of being enclosed in this ROM.
EDIT: And yes, the new hboot prevents downgrading...
Do you get now the reasons?
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.
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.
nope_okay said:
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Click to expand...
Click to collapse
You need to replace CWM with the standard HTC recovery (you simply need to extract the recovery.img file from a RUU/ROM.zip file) and then relock the bootloader before the OTA will install correctly.
At hboot 1.16 and rooted all you should have to do is install Cwm and than you can flash custom ROM's..... Not sure what your problem is.
Sent from my anus using xda crap
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
nope_okay said:
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
Click to expand...
Click to collapse
Instead of trying to install the OTA update for Sense 3/2.3.5 why don't you flash the stock, rooted version of 2.3.5/Sense 3 ROM that I posted in the Dev section. With the unlocked bootloader and CWM you can flash this ROM and then manually flash the boot.img in that ROM's zip file and you should be good to go.
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
nope_okay said:
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
Click to expand...
Click to collapse
Here is the 2.3.5/Sense 3.0 stock, rooted ROM built directly from the OTA you were trying to install. You would flash it in CWM just like you did for CM7.
http://forum.xda-developers.com/showthread.php?t=1430535
Thanks for the link, will come in handy when I want to go back to a 'stock' setup... wasn't very impressed with CM7 so I then tried the Virtuous Affinity ROM (2.3.5/S3.5) - fantastic. Thanks again for your help!
G
Hi, If I have a rooted phone, how do I update the rom? I have the stock rom. I guess you have to download the update and install it like you would any rom, but would this format my phone?
Astralogic said:
Hi, If I have a rooted phone, how do I update the rom? I have the stock rom. I guess you have to download the update and install it like you would any rom, but would this format my phone?
Click to expand...
Click to collapse
If you have a rooted stock rom, you will be able to receive update notifications from Sony and you can update using the offical methods.
However, the update will install the new stock rom without root, as this is not supported by the manufacturer.
There are some tricks to maintain root during an update, but there is no guarantee it will work.
(search xda forums)
FYI, for the current 4.3 stock release for V and T, there is a "one-click" root method.
Check this .
.
arturiu said:
If you have a rooted stock rom, you will be able to receive update notifications from Sony and you can update using the offical methods.
However, the update will install the new stock rom without root, as this is not supported by the manufacturer.
There are some tricks to maintain root during an update, but there is no guarantee it will work.
(search xda forums)
FYI, for the current 4.3 stock release for V and T, there is a "one-click" root method.
Check this .
.
Click to expand...
Click to collapse
I can't update whilst rooted, the update fails to install. I would need to unroot before updating via the official method.
Astralogic said:
I can't update whilst rooted, the update fails to install. I would need to unroot before updating via the official method.
Click to expand...
Click to collapse
SuperSU has an option to remove root from your rom.
You can try that and see if the rom update works.
updating rooted phone
Astralogic said:
I can't update whilst rooted, the update fails to install. I would need to unroot before updating via the official method.
Click to expand...
Click to collapse
sir
get any required stock ftf files from xda link and flash that on flash tool to your rooted phone
there must be no problem.try