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.
Related
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?
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,
I know this has been discussed in several ocassions, and I have read several threads but none of them answer my question.
I am wondering if I root my HTC One and keep the device with the stock rom (I only want to root for some apps that needs su) will I be able to get OTA updates?
If not, if I also do S-OFF will I be able to? Please keep in mind that I do not want to flash a custom rom, where then the answer I believe would be to unroot and apply the OTA.
Thank you
buzmay said:
Hi,
I know this has been discussed in several ocassions, and I have read several threads but none of them answer my question.
I am wondering if I root my HTC One and keep the device with the stock rom (I only want to root for some apps that needs su) will I be able to get OTA updates?
If not, if I also do S-OFF will I be able to? Please keep in mind that I do not want to flash a custom rom, where then the answer I believe would be to unroot and apply the OTA.
Thank you
Click to expand...
Click to collapse
No, and youll need a custom kernel with disabled write protection for the root to stick, which will not allow OTA's to work. if you really want root, download a custom stock rom
IINexusII said:
No, and youll need a custom kernel with disabled write protection for the root to stick, which will not allow OTA's to work. if you really want root, download a custom stock rom
Click to expand...
Click to collapse
But what about S-OFF not even with it it would work? I am confuse because I saw a guide here in XDA saying the following:
Rooting stock ROM
What you need to know before rooting stock ROM:
You can "un-root" it easily.
As long as you won't change any files on system partition, you still will be able to download and install official OTA updates.
Download Rooting Tools
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of Rooting Tools (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device. Your device has now SuperUser.apk, su binary and busybox installed.
So is this not true?
Link to this guide:
http://forum.xda-developers.com/showthread.php?t=2265618
buzmay said:
But what about S-OFF not even with it it would work? I am confuse because I saw a guide here in XDA saying the following:
Rooting stock ROM
What you need to know before rooting stock ROM:
You can "un-root" it easily.
As long as you won't change any files on system partition, you still will be able to download and install official OTA updates.
Download Rooting Tools
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of Rooting Tools (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device. Your device has now SuperUser.apk, su binary and busybox installed.
So is this not true?
Link to this guide:
http://forum.xda-developers.com/showthread.php?t=2265618
Click to expand...
Click to collapse
Having S-off won't effect OTAs but having a custom recovery will. Best to go all stock, rom and recovery to receive the OTA updates. You can root after.
Note: Do the S-off procedure before you update. If your hboot gets updated, you're outta luck.
farang4u said:
Having S-off won't effect OTAs but having a custom recovery will. Best to go all stock, rom and recovery to receive the OTA updates. You can root after.
Note: Do the S-off procedure before you update. If your hboot gets updated, you're outta luck.
Click to expand...
Click to collapse
Ok, but now for instance I do have 4.2.2 so if I root and then there is an update 4.3 then what? I am interested in being only root and being able to get the updates. So every time an OTA comes I shall unroot and then root? This option is not as optimal as I would have though it would be.
Thanks
buzmay said:
Ok, but now for instance I do have 4.2.2 so if I root and then there is an update 4.3 then what? I am interested in being only root and being able to get the updates. So every time an OTA comes I shall unroot and then root? This option is not as optimal as I would have though it would be.
Thanks
Click to expand...
Click to collapse
As long as you have a stock recovery and rom, you should be able to receive OTAs on a rooted phone. Not %100 certain though.
Note: An OTA update could break the root and other mods you made to the rom and cause some other issues.
farang4u said:
As long as you have a stock recovery and rom, you should be able to receive OTAs on a rooted phone. Not %100 certain though.
Note: An OTA update could break the root and other mods you made to the rom and cause some other issues.
Click to expand...
Click to collapse
But how can I have a stock recovery and be root? Dont I need a custome recovery to root?
buzmay said:
But how can I have a stock recovery and be root? Dont I need a custome recovery to root?
Click to expand...
Click to collapse
You need custom recovery to run the rooting process. After your system is rooted you can then flash back to the stock recovery. You should still have root access but I could be wrong. Download "Root Checker" from the play store, run it to see if your device is still rooted. You still need a stock recovery to receive OTA updates though.
The reason you need stock recovery is that you can't install an official update with custom recovery. The type of recovery you have doesn't affect root access.
The reason you have to keep your system files perfectly stock is that an OTA is a patch, meaning it doesn't necessarily replace entire files but mainly snippets of code. If the system files are not stock, it can't do this properly. So it checks /system before running and stops if things are not perfectly stock.
You can get OTAs being rooted, you just can't install them unless you have stock recovery and a fully stock rom.
If you're stock on 4.2.2 right now, you can't s-off, so don't worry about that.
You don't have to flash a custom rom, but you can flash a stock rooted rom. With OTAs, you play the cat-and-mouse game. Can I root it? Did the HBOOT update and kill current S-OFF procedures?
If 4.3 does come out, all you would have to do is wait for a few days for a dev to cook a stock rooted 4.3 rom. AT&T always lags with updates, yet I have a fully functioning 4.2.2 M7 with LTE and no AT&T bloat all thanks to the devs who cook stock rooted roms.
I'm currently S-OFF, Stock Firmware (as shipped, except for hboot, recovery).
And I'm running BadBoys 1.1
I don't want to flash "Modified Firmware" (this time).
What do I need to do let the OTA update come in normally?
I assume I need to flash Stockish ROM (with or without root).
Do I need to relock?
I know there is unmodified firmware as well. I might go that route too.
But I want the most "Official" way to let the firmware be updated. I want to hold off on Harman Firmware just yet.
If a Stock RUU (that included OTA firmware) existed, I'd definitely just use that. I know about the Harman RUU.
I've never personally taken an OTA.
I think all you need is a stock rom and stock recovery.
Not sure if you need to re-lock being s-off.
Btw the unmodified firmware is pulled from the OTA zip.
BD619 said:
I've never personally taken an OTA.
I think all you need is a stock rom and stock recovery.
Not sure if you need to re-lock being s-off.
Btw the unmodified firmware is pulled from the OTA zip.
Click to expand...
Click to collapse
Yeah, I know. I ended up doing just that. Being crazy anal for nothing.
I learned my lesson on my old EVO 4G about accepting OTA's.
I lost root for a while until a new method opened up.
Patience is everything.
Since you're S-off you can just install the stock Android recovery, then accept the OTA. You'll retain S-off but lose root. You can then root again by installing a custom recovery and flashing the SU binary in recovery. Honestly, though, Captain Throwback's firmware will get you where you want to be without the hassle of doing everything I listed above.
Sent from my HTC device
Yes, and no...for Sense enhancements, you get to check them out first without waiting for a stock rooted rom or a custom rom running the same base. Matter of preference, I guess.
AarSyl said:
Yes, and no...for Sense enhancements, you get to check them out first without waiting for a stock rooted rom or a custom rom running the same base. Matter of preference, I guess.
Click to expand...
Click to collapse
Right. I personally prefer to wait for a stock rooted ROM based off the latest update, and separately install the corresponding firmware package.
Sent from my HTC device
Magnum_Enforcer said:
Right. I personally prefer to wait for a stock rooted ROM based off the latest update, and separately install the corresponding firmware package.
Sent from my HTC device
Click to expand...
Click to collapse
Meh...to each his own. It depends on what the update contains for me. For example, I had no interest in waiting for a stock rooted Sense 5.0 rom when it was finally released for the LTE.
Sent from my 831C using Tapatalk