I am running a JF build
2.6.27-00392-g8312baf
[email protected] #2
Build number
CRB43
I got an system update popup this morning, and after pressing more info I get,
"Please install this update from Google. It contains a security fix."
It is 884 kB in size so not much there.
Where can I find the file on the phone to grab and toss up here?
Its not in the SD root like I thought.
-Nik
If you installed it you probably don't have root anymore...Do you still have root and did you install it? Also when you go to settings>about. Does it say CRC1 somewhere?
I was very suspicious about it, since the JF builds are using the public keys. SO no I have not installed it yet.
-Nik
Suggest you don't until people find out what it actually does.
I don't plan on it, where can I find the URL.
Also is there a way to diable the update popup's?
As I recall it was in some log file somewhere. I'll post it when I find it.
-Nik
how did you even get an ota update? ur running a jf build which means ur phone is rooted. rooted phones shouldnt be able to get ota's. or am i wrong here.
tribalb said:
how did you even get an ota update? ur running a jf build which means ur phone is rooted. rooted phones shouldnt be able to get ota's. or am i wrong here.
Click to expand...
Click to collapse
You are correct
That is weird that you got some update, OTA. Are you 100% sure you were successfully on JF's build with root?
This is really strange...
I too got the update notification today. Clicking the "more info" button shows:
Android Update 1.5
Downloaded and verified
2.0MB
Yet I have a rooted JF build. Kernel version 2.6.27-00392-g8312baf
Build number CRB43...
It's JF's UK build and I have full root access..
I'm pretty sure it shouldn't be possible for the official Google update here to be verified, unless Google have used the JF private key to sign it. But that's not possible, right? I mean, are they trying to push this to people's phones to remove root access? Is the private key that's used to sign all these releases, generally available?
Maybe it's an oddity caused by something I've done. Eg I was using the Haykuro build before. I then moved to using the JF Updater to install his latest UK version...
I obviously haven't installed this official Google version yet, in case it removes root access!
Tom
This gets more interesting as it goes.
I just took a look over at T-Mobile's Forums and found this:
http://forums.t-mobile.com/tmbl/board/message?board.id=AndroidDev&thread.id=6975
It seems that they renamed CRB43 to CRC1.
"The latest G1 software update includes permissions fixes and other bug fixes"
I assume it will be taking away root, but I find it VERY interesting that they managed to get this to the rooted phones.
I'm looking more into this, and I just emailed a T-Mo rep/friend I know. I'll keep you posted on what she says.
Same thing
I am getting prompted this morning for a System update, however I have a rooted JF 1.51, CRB43, 1.5 already. It keeps popping up, very annoying, I'm afraid to turn my phone off.
It seems this is what its all about http://www.ocert.org/advisories/ocert-2009-011.html
-Nik
So, has anyone installed this and if you have do you still have root?
-Nik
akapoor said:
You are correct
That is weird that you got some update, OTA. Are you 100% sure you were successfully on JF's build with root?
Click to expand...
Click to collapse
Yep, its rooted. I have had it rooted since the day I got it
-Nik
they are putting this out hard. I do not have root just a stock cupcake g1. And I have gotten this 6 times today after saying install later
I have an adp...and I lost root access with this update! I just flashed harry_m's kernel and it was all better!
Hmm I wonder if TMobile can query the phone and ask it its firmware rev...
-Nik
Nikropht said:
It seems this is what its all about http://www.ocert.org/advisories/ocert-2009-011.html
-Nik
Click to expand...
Click to collapse
Wow, I don't blame them at all for pushing this so hard, this patches the OS so that one-time program permission grants at installation does not leave you vulnerable to what's basically spying on a user's mic/camera at a later time. Unless I'm reading it wrong...
http://jf.andblogs.net/ look here for your answer as to why your getting the updates
If I'm not mistaken the update is geared towards Dev. phones because I read somewhere that the security update and other small stuff was for App. Developers so if your running a ADP version that is probably why your getting the OTA, I could be wrong though, can someone running a U.S. version or other that is not ADP comfirm this.
I could be very wrong but I don't think its a T-mobile thing. I just got my g1 yesterday, unlocked. I'm on ATT and kept getting it so I let it update. I haven't rooted yet and hadn't had the phone for more than a couple hours but didn't notice anything different. Hope i just didn't make it harder for me to root the phone.
Related
Since the 2.1 new update was released, I figured it would be a higher version number than our leaked 2.1. That means we could hboot it to our phones to update.
But wait, could some developer root this update (maybe in a similar to the way they rooted 1.5 to 2.1 root) so the leaked 2.1 people could hboot to this new update for 2.1 except it would be rooted.
Sorry if that was confusing.
Here's where the update was found:
androidforums.com/htc-droid-eris/55898-you-dont-need-root-new-leak.html
As far as I understand it, the reason that 2.1 OTA can be installed for users running leaked 2.1 is because it has a higher subversion number and it is SIGNED. That is the tricky part. Because your SPL / HBoot is S-ON, meaning that it will only install signed zips, you are still unable to install a rooted 2.1. The reason that the exploit worked on 1.5 is because the PB00IMG.zip IS a signed package, but the versioning only puts it ahead of 1.5, not Leaked 2.1 or OTA 2.1. Once the PB00IMG.zip is installed, it turns S-OFF so that unsigned (e.g. rooted) packages. From what I have read in other posts, devs are moving toward trying to find exploits in the new 2.1 OTA for users who have already upgraded without root. I would personally recommend doing the 2.1 OTA and hanging tight for the next exploit.
Thank you man. So, would it not be possible to turn S-OFF in this new update? I understand that would require going in and tampering with the files, which could break the signature on the package, possibly?
Precisely, if you change one bit of a signed file, the signature changes completely. As I understand it, the PB00IMG.zip file that is used to root 1.5 phones was "stumbled upon" already signed by HTC. For any future rooting for people with 2.1, this file is unusable because the versioning of this convenient package is older than what leakers and official 2.1 adopters have. It is impossible to modify the 2.1 update without breaking the sig. We now have to hope that devs can find an exploit or broken code in the new 2.1 update that allows for rooting by another means.
If you are desperate, feel free to try to socially engineer Verizon. That has met with considerable success from some other early adopters. If not, play the waiting game. In the mean time, feel free to upgrade to the OTA 2.1 leak. It fixes some things like Google relogin.
shickfaced said:
Precisely, if you change one bit of a signed file, the signature changes completely. As I understand it, the PB00IMG.zip file that is used to root 1.5 phones was "stumbled upon" already signed by HTC. For any future rooting for people with 2.1, this file is unusable because the versioning of this convenient package is older than what leakers and official 2.1 adopters have. It is impossible to modify the 2.1 update without breaking the sig. We now have to hope that devs can find an exploit or broken code in the new 2.1 update that allows for rooting by another means.
If you are desperate, feel free to try to socially engineer Verizon. That has met with considerable success from some other early adopters. If not, play the waiting game. In the mean time, feel free to upgrade to the OTA 2.1 leak. It fixes some things like Google relogin.
Click to expand...
Click to collapse
So, I installed the first 2.1 leak. Can I install this new one that just came out in the last couple days? Sorry, guess I'm not seeing the answer here
If we were able to find a way to modify the update to include root with a valid signature, we would also be able to modify the version number to a higher number than the current 2.1 leak. I'm pretty sure upgrading to the "official" 2.1 won't hurt our chances of finding root, it'll just make the wait less buggy
jearl75:
Yeah, you can install the new leak over the old one, no worries.
so should us people on the first 2.1 leak upgrade to the newest one or stay on the first one??
theboo7 said:
so should us people on the first 2.1 leak upgrade to the newest one or stay on the first one??
Click to expand...
Click to collapse
I reckon that depends on if you're experiencing the Google login bug or not. My wife's Eris with the first leaked 2.1 is not. And if you are experiencing that bug, which is more hassle...logging into Google repeatedly, or rebuilding your phone (apps, contacts, etc) from scratch??
Dangerous Dave said:
I reckon that depends on if you're experiencing the Google login bug or not. My wife's Eris with the first leaked 2.1 is not. And if you are experiencing that bug, which is more hassle...logging into Google repeatedly, or rebuilding your phone (apps, contacts, etc) from scratch??
Click to expand...
Click to collapse
its not that bad since i rarely restart my phone, i guess my real question would be would it make it longer until i get root? or are devs trying to root the NEW 2.1 instead of the old 2.1
I apologize if this gets old, but I am trying to be cautious so I don't brick my phone...
I downloaded the following leaked 2.1 version a few weeks ago, and have this installed:
Baseband version: 2.40.00.01.22
Kernel version: 2.6.29-5898f66b / [email protected] #1
Build number: 2.19.605.1 CL12345 test-keys
Software number: 2.19.605.1
I have a problem installing the new version of Google Maps. Phone dial can be sluggish and/or unresponsive at times, but it is manageable. Overall, the installation of the leaked ROM went fine, and I feel like I am pushing my luck if I try to download the latest ROM. Does anyone know if the latest release addresses the issues above? I am not experiencing any of the login issues to Gmail that others are experiencing.
My question is this: Should I just leave well enough alone and wait for the OTA at this point?
Thanks for any suggestions.
mdeavers said:
I apologize if this gets old, but I am trying to be cautious so I don't brick my phone...
I downloaded the following leaked 2.1 version a few weeks ago, and have this installed:
Baseband version: 2.40.00.01.22
Kernel version: 2.6.29-5898f66b / [email protected] #1
Build number: 2.19.605.1 CL12345 test-keys
Software number: 2.19.605.1
I have a problem installing the new version of Google Maps. Phone dial can be sluggish and/or unresponsive at times, but it is manageable. Overall, the installation of the leaked ROM went fine, and I feel like I am pushing my luck if I try to download the latest ROM. Does anyone know if the latest release addresses the issues above? I am not experiencing any of the login issues to Gmail that others are experiencing.
My question is this: Should I just leave well enough alone and wait for the OTA at this point?
Thanks for any suggestions.
Click to expand...
Click to collapse
I Know that when I installed the new Leak, the dialer lag was MUCH improved, as was the phone signal and general stability, Gmail doesn't make you log back in every reboot, and on my phone my "get more HTC widgets" link is fixed. But I heard on others phones it wasnt. It Does wipe all your apps even though its 2.1 -> 2.1. But Just like last time the SD card is untouched.
The installation process is exactly the same. I recommend it.
EDIT- Actually I just noticed the build you have installed is test keys signed and to my knowledge only the root rom was test key signed. This being the case if you want to keep root I would flash a custom cooked ROM... Since your lucky enough to have the chance to do so... Sigh..
Wait, test keys signed means what exactly? My Eris reads that but I only installed the two leaks AFAIK?
Does it just mean signed by HTC?
thawkth said:
Wait, test keys signed means what exactly? My Eris reads that but I only installed the two leaks AFAIK?
Does it just mean signed by HTC?
Click to expand...
Click to collapse
So you only installed the 2.1 non-root Leaks??? I may be mistaken, but both times I flashed the leaks, 2.1a +2.1b, both had builds signed with release keys... I was under the impression that only the 2.1 leak+root was signed with test keys.
Shed some light developers?
Whitepaint said:
So you only installed the 2.1 non-root Leaks??? I may be mistaken, but both times I flashed the leaks, 2.1a +2.1b, both had builds signed with release keys... I was under the impression that only the 2.1 leak+root was signed with test keys.
Shed some light developers?
Click to expand...
Click to collapse
You are exactly correct: Both of the leaked 2.1 roms have release keys, while the 1.5->2.1 root rom (and any rom based on that upgrade) will have test keys.
my girl has a rooted 2.1 with release keys. download Grdlocks ota rom
ahjee said:
my girl has a rooted 2.1 with release keys. download Grdlocks ota rom
Click to expand...
Click to collapse
Interesting...can you post the software version/info from your phone settings?
ahjee said:
my girl has a rooted 2.1 with release keys. download Grdlocks ota rom
Click to expand...
Click to collapse
Thats most probably because Grdlocks ota rom is based on just that, the 2.1 ota leak, not the 2.1+root rom. The Beauty of custom roms...
Sorry no one has been clean on this before:
The 2.1 leak was leaked from HTC by riverrunner. We actually don't care about the hboot version, radio version is the main thing updaters look at (we've found that out since root).
The 2.1 update that had root built in was also an HTC leak. It contained SU. That was the difference. We didn't do ANYTHING to get root. ABSOLUTELY NOTHING. It was leaked by someone at HTC. Simple enough. So, we CANNOT redo this, becuas we did NOTHING.
Hope this clears it up. Thanks!
zifnab06 said:
Sorry no one has been clean on this before:
The 2.1 leak was leaked from HTC by riverrunner. We actually don't care about the hboot version, radio version is the main thing updaters look at (we've found that out since root).
The 2.1 update that had root built in was also an HTC leak. It contained SU. That was the difference. We didn't do ANYTHING to get root. ABSOLUTELY NOTHING. It was leaked by someone at HTC. Simple enough. So, we CANNOT redo this, becuas we did NOTHING.
Hope this clears it up. Thanks!
Click to expand...
Click to collapse
I'm glad this was finally publicly admitted. I got kind of tired of the devs going around pretending they actually did something besides getting lucky with a leak.
12134567890
just buzzing in that my phone just received an OTA update notification.
its currently on 2.1 leak V3.
A: anyone else get the notification?
B: anyone apply it and check for rootability
i refuse to apply the update
No update for me yet. Been checking. But nothing yet.
If you do apply it, follow these instructions courtesy of bftb0 before you do http://forum.xda-developers.com/showthread.php?t=642135
Thanks for the link
refthemc said:
If you do apply it, follow these instructions courtesy of bftb0 before you do http://forum.xda-developers.com/showthread.php?t=642135
Click to expand...
Click to collapse
You could just call verizion and find out what the ota update there tell you
iornslave said:
just buzzing in that my phone just received an OTA update notification.
its currently on 2.1 leak V3.
A: anyone else get the notification?
B: anyone apply it and check for rootability
i refuse to apply the update
Click to expand...
Click to collapse
Why would you refuse to update, if you are on the 2.1 ota you can root.
tonyb81 said:
Why would you refuse to update, if you are on the 2.1 ota you can root.
Click to expand...
Click to collapse
he would not be able to by the 1.5 root method, bc the leak already wrote over his bootloader. so his only hope to root is http://forum.xda-developers.com/showthread.php?t=711535
Anyone know if the update would be received on a rooted 2.1 ROM as long as the otacerts.zip and systemupdater.apk files are restored?
fritzel67 said:
Anyone know if the update would be received on a rooted 2.1 ROM as long as the otacerts.zip and systemupdater.apk files are restored?
Click to expand...
Click to collapse
In theory, as long as your build number still reads 2.36.605.1. Might not work correctly, though, if it's trying to patch files.
i did get the update
i did accept the update
it does remove root
but i was able to easily get root after it
just adding that i only had the first part of the rooting process done
i didnt have a custom rom or recovery
Androidforums is following this here.
http://androidforums.com/htc-droid-eris/111235-anyone-receive-12-8mb-ota-update-today.html
So far the build number and software numbers are bumped and the Heroc baseband (the latest 2.42.01.04.27 that Sprint has) is installed.
Hopefully we can get a logcat of the update so the devs can pick it apart and find out how it ticks.
Another user had posted a day or two ago on Androidforums that a VZW rep had told him an OTA was going to be pushed out to resolve audio issues. A few people wrote him off but it looks like they may have been right.
Users are reporting that Hboot is not affected.
Stonent said:
Users are reporting that Hboot is not affected.
Click to expand...
Click to collapse
I don't know about other Android (or HTC phones), but VZW/HTC have never put a bootloader update into their OTAs for the Eris. (Probably too risky from a customer standpoint - a problem with flashing the bootloader will definitely cause a brick.)
For root users, most of whom are using ROMs that defeat OTA updates, there would be little risk. For leakers, who don't have a friendly bootloader in the first place - well, can the bootloader get any worse than it already is?
There is a chance that the recovery partition will be different (VZW/HTC did that during the 2.1 OTA update)- and right now, that is the only glimmer of hope for the leakers wanting root.
We need to find out if the recovery partition got changed ASAP - at the moment, that is the big risk.
If anybody captures the URL for the download, please post it up.
bftb0
Yeah I didn't figure they'd mess with Hboot.
Has anyone captured this so we can install and not wait for the OTA? I have two Eris phones, one on Leak v.2 and one running the RUU 2.1 (upgraded from Leak v.3)
Firmware 2.1
Baseband 2.40.00.01.22
Kernel 2.6.29-564a4a15
[email protected] #1
Build 2.26.605.4 CL 140744 release keys
will I get the OTA? If not, how would I go about getting a rom to get the update?
I tried renaming otacerts.zip.bak back to otacerts.zip but apperently I'm not smart enough to...
What does this update do, if anybody knows?
Specifically does it fix the silent bug?
Neither here, nor Androidforums has had anyone capture the log file yet.
It's driving me crazy to know what's in this update. So far all I know is the build number is updated, and a new baseband.
Right now, my Aria is updated to the official 2.2 update ( I downloaded the update through the phone)
I want to root my phone now, so I went researching around here about the rooting process, and found this helpful guide.
However, I also read something about after updating to 2.2, I can't root my phone.
So right now I want to ask whether I can root my phone by following the steps in that guide? Or will it cause problems to my phone?
zsaberstar said:
Right now, my Aria is updated to the official 2.2 update ( I downloaded the update through the phone)
I want to root my phone now, so I went researching around here about the rooting process, and found this helpful guide.
However, I also read something about after updating to 2.2, I can't root my phone.
So right now I want to ask whether I can root my phone by following the steps in that guide? Or will it cause problems to my phone?
Click to expand...
Click to collapse
Sorry, but if you took the official Froyo 2.2 OTA, then chances are you will not be able to root your phone at this time. This update modified your HBOOT boot loader and the root exploit that Unrevoked uses has been fixed and prevents rooting.
zsaberstar said:
Right now, my Aria is updated to the official 2.2 update ( I downloaded the update through the phone)
I want to root my phone now, so I went researching around here about the rooting process, and found this helpful guide.
However, I also read something about after updating to 2.2, I can't root my phone.
So right now I want to ask whether I can root my phone by following the steps in that guide? Or will it cause problems to my phone?
Click to expand...
Click to collapse
How did you download the HTC ARIA Froyo 2.2 OTA update? To my knowledge this update has not been released.
Aww... that sucks. Anyway thanks for helping.
I was meddling around the settings of the phone and found a check for update button, clicked it and a message appeared stating a new update is available, then I downloaded it.
rayott said:
How did you download the HTC ARIA Froyo 2.2 OTA update? To my knowledge this update has not been released.
Click to expand...
Click to collapse
zsaberstar said:
I was meddling around the settings of the phone and found a check for update button, clicked it and a message appeared stating a new update is available, then I downloaded it.
Click to expand...
Click to collapse
HTC released Froyo 2.2 OTA update for international versions of the Aria, i.e. non-AT&T branded Aria.
Today I received an OTA system update version 1.82.405.1 on my HDZ.
Does anybody here received or installed it??
And what kind of update is it?
I'm affraid of losing root again, similar like what happend with version 1.72.
I feel like I'm stating the obvious here, but NEVER EVER install an OTA if you have root! I'm sure you know this now from your previous experiance, but just to save you trouble incase you didn't know. As for the update, I'm not sure what it contains, but it seems like an older update as the newest version of virtuous is based on 1.85.72.2.
EDIT: Also suggest reading this if you haven't already: http://forum.xda-developers.com/showthread.php?t=875099
Thnx.
But I've read it's safe to flash an OTA update once you've rooted your phone with the Gfree method.
I now running a stock 1.72 rom, rooted with Gfree / psneuter.
In that case I'm not sure, but I wouldn't try it until it's been confirmed to be ok. And while I'm sure you have you're reasons, but why not try out the likes of virtuous? It's pretty much stock sense but with added features and improved performance, and as I said it's also on the latest RUU.
Taking an OTA will *definitely* reduce you to "stock", so even if its safe, it isn't worth it.
Be aware that it *IS POSSIBLE* for an OTA UPDATE to modify your partition 7 and take away radio s-off. The only reason why people tend to say that its safe is ONLY because they never actually HAVE done that.
still i am curious about the content.
i dont need root anymore. DZ is perfectly fine without.
I don't think applying and offical OTA while rooted on a non stock rom is a good idea. If your willing to take the risk, or don't care about loosing root or getting it back if lost. Then try it out. Be the guinea pig because it doesn't look like you will take the advise of the forum you posted anyways.
Sent from my CM7 powered G2
whats in the update then??
Yeah I'd like to now too
Just checked, I get the update too....
I don't have s-off or root so I think I am going to download it.
It s 17MB,
Sent from my HTC Vision using XDA App
Install the new full ROM,then you don`t loos root and S-Off
http://forum.xda-developers.com/showthread.php?t=960149
OTA 1.82
romdroid. said:
whats in the update then??
Click to expand...
Click to collapse
yes, it is a 17 Mb package. I got it and installed it. (nothing to lose, I have no root, I do not need it, my DZ is PERFECT without it. I have been tweaking and **** before on WinMo, but not now...)
It said it is camera improvements and other small bugfixes.
All I saw is a different sms counter on the icon, it's white numbers on a black circle, nothing special.
I had a busy day, had no time to play around.
The firmware remains 2.2.1.
I will follow up if I find out anything else.
Update: the mentiones sms counter is for a voicemail of course ))) my fault
I've read the album/gallery bugs are fixed. No need to rescan pictures anymore.
found this on another forum
Improve system performance and Camera feature enhancements.
Click to expand...
Click to collapse
if any1 got the full release notes , pls post...
wanna know of the sms notification bug is solved!! thats the only thing i hate
No use as the updates are usually non-important and if they are, someone will extract it and you can flash it by itself without the risk.
HTC hasn't yet released official release notes for this update. As already said it should improve camera, system performance, fix some bugs and also improve htcsence.com -functionality.
htc 1.82.405.1 update
I just updated using the OTA update to 1.82.405.1 on my htc desire z (I have stock android).
But now the touch screen is horizontaly mirrored.
Meaning if i click on home the search button is clicked.
If i touch the icons on the left side, the right side icon registers the click.
Only center of the screen is safe
Let me know if anyone else has this issue after the recent updated.
Hopefully there is a solution out there.
UPDATE:
I did 2x hard resets which didnt help.
However a soft reset did the trick and every thing is back to normal.
maus010 said:
But I've read it's safe to flash an OTA update once you've rooted your phone with the Gfree method.
I now running a stock 1.72 rom, rooted with Gfree / psneuter.
Click to expand...
Click to collapse
If you already have root/S-OFF, then it's only "safe" once the new release has been verified by the devs as not causing anything bad to happen with your root/S-OFF. e.g. in theory there could be a new OTA released that will permanently lock you out of root/S-OFF.
When the 1.72 OTA first came out, it wasn't rootable for quite a while, so folks with root who accepted the OTA lost their root for some time.
Damn, I am getting the feeling the new update drains the battery faster than 1.72,
phone was about empty at 11pm yesterday, it was plugged in until 8 am...
done nothing the entire day actually...
notification-bug seems to be fixed (yes, new counter for sms/mails/etc) and best part: no jumping screen, when writing sms!!! at least till now...
Hi guys,
Just recieved a nexus s i purchased on ebay (LOVE IT!) coming from a Galaxy S i used to use odin for flashing the latest roms
But one of the things i wanted from having the nexus s was getting updates quick, and what i thought was OTA updates.
i have just gone into "about phone" checked for updates and there are apparently none available. details below
Android Version = 2.3.1
Baseband Version = I9020XXJK8
Kernel version = 2.6.35.7-gf1638a [email protected] #1
Build number = GRH78
so my question is, how do i get to the latest official FW, i thought it would be as easy as clicking check updates, but obviously not
Cheers guys, i have searched btw, and im lost completely
The full ROM to upgrade you to 2.3.4 is available here: http://forum.xda-developers.com/showthread.php?t=1061445
That should work for any previous build I think - if not use the 2.3.3 ROM and then run the update to 2.3.4.
of course assuming your running stock you could try a checkin and wait for the OTA to reach your handset........
as im on 2.3.1 at the moment, wouldnt there be an OTA already waiting to update to 2.3.3 if the 2.3.4 update has not yet been pushed to this perticular handset?
ascottuk said:
as im on 2.3.1 at the moment, wouldnt there be an OTA already waiting to update to 2.3.3 if the 2.3.4 update has not yet been pushed to this perticular handset?
Click to expand...
Click to collapse
Yup - should be........how long have you had the phone?
recieved yesterday, so i have been using it for just over 24hours,
im probably being impatiant
ascottuk said:
recieved yesterday, so i have been using it for just over 24hours,
im probably being impatiant
Click to expand...
Click to collapse
yeh, once your SIM and handset get registered with Google's servers (which can take a few days) you should get the OTA. if your impatient like me just run the updates manually...
moon-unit said:
yeh, once your SIM and handset get registered with Google's servers (which can take a few days) you should get the OTA. if your impatient like me just run the updates manually...
Click to expand...
Click to collapse
is there anyway to check if my bootloader is unlocked?
i take flashing manually is just a case of downloading the relevent ota rom, and putting it on the SD card, then start the phone in recovery?
ascottuk said:
is there anyway to check if my bootloader is unlocked?
i take flashing manually is just a case of downloading the relevent ota rom, and putting it on the SD card, then start the phone in recovery?
Click to expand...
Click to collapse
boot your phone up while holding onto the volume up button as well and it should load up a screen with a green droid which will show your bootloader state whether it's LOCKED or UNLOCKED.
Place the rom in the root directory of your sd card then boot in recovery and install zip from sdcard.
ok checked and its locked, so am i still able to flash from sd?
ascottuk said:
ok checked and its locked, so am i still able to flash from sd?
Click to expand...
Click to collapse
It depends. If you are looking at staying "stock" then go see the sticky thread for 2.3.4, there is a full ROM version that you can install. It's signed by Google, so the stock recovery will install it. No need to unlock your bootloader
if you wanted to flash zip's (such as the superuser zip update to gain root access) that where signed by other sources, then you would need to unlock the bootloader and replace the recovery with something like Clockwork
Matridom said:
It depends. If you are looking at staying "stock" then go see the sticky thread for 2.3.4, there is a full ROM version that you can install. It's signed by Google, so the stock recovery will install it. No need to unlock your bootloader
if you wanted to flash zip's (such as the superuser zip update to gain root access) that where signed by other sources, then you would need to unlock the bootloader and replace the recovery with something like Clockwork
Click to expand...
Click to collapse
many thanks for all your help, appreciate it alot
you have been thanked!
ascottuk said:
many thanks for all your help, appreciate it alot
you have been thanked!
Click to expand...
Click to collapse
before you update, i'd love to get a dump of the phone on 2.3.1 that i could use please.
MarkusPO said:
before you update, i'd love to get a dump of the phone on 2.3.1 that i could use please.
Click to expand...
Click to collapse
BTW, i'll receive my Nexus S today.
Before i start unlocking, rooting etc. i'd like to dump my system/bootloaders for emergency.
I know that it's not really necessary but how do i do it.