Database Users

Android Update 1.5?

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.

Rooting the New Update for Leaked 2.1

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

ROOT - Official Verizon 2.1 OTA Upgrade - Eris

Thought that this would need to be created since the upgrade has begun. I have 2 Eris Droids on my account and 1 has received the update but not the other. It is possible that because the other has the v3 leak already maybe it will not update until there is an update beyond 2.1. I am in the Washington DC Metro area. Which has a HUGE Verizon base.
I am committed to finding the root for this. I will work on it myself and report any progress. If anyone else wants to contribute their findings...feel free...

Save for future use...1
Still have not achieved anything as of yet...

Save for future use...2
Save for future use...2

Save for future use...3
Save for future use...3

No one on any of the leaks has received the OTA update. Its possible they never will, as it has been stated the leaks have a higher HBOOT than the OTA. OF course if you ask the people on the VZWSupport on twitter they all claim that the leakers will receive it before the end of the OTA period. But since no one, as far as I know, on a leak has received it I will believe it when it happens. Just my 2 cents

I agree with you on that. Its our penalty for circumventing the VERIZON way...LOL

This thread is a bit superfluous, it has been confirmed you can root the OTA update the same way you could root 1.5:
http://forum.xda-developers.com/showthread.php?t=681648
However, the leaked RUU updates changed the HBOOT version, where the OTA update did not. This means leakers are SOL, at least for the time being...

sorry wrong post lol

DEAd thread.
Version 3 of leak is almost identical (minus a few missing files that are not needed) to the OTA.
OTA users can root via 1.5 method.
Search function FTW.

jcase said:
DEAd thread.
Version 3 of leak is almost identical (minus a few missing files that are not needed) to the OTA.
OTA users can root via 1.5 method.
Search function FTW.
Click to expand...
Click to collapse
Are you sayign Version 3 leaked can be rooted?

No, he is stating that if you went from 1.5 stock to 2.1 OTA you can root using the same method as the 1.5 -> 2.1 root.
If you have any of the leaked versions you cannot root yet.

Gervin said:
Are you sayign Version 3 leaked can be rooted?
Click to expand...
Click to collapse
No. v3 changed the hboot version.

I am using a rooted version of 1.5 right now, I keep getting the message from Verizon if I want to update to 2.1 OTA.
Anyone know if could allow that update to download and would it work? Lets assume it does not work would it ruin my phone? Or worse case I just re-flash my phone back to rooted 1.5?
Reason I am using rooted 1.5 over any of the current rooted leaked 2.1 roms is the bluetooth is not working with my new car I picked up last weekend I am very curious to find out if the problem with bluetooth is a bug in 2.1 leaked versions or is also present in the official over the air version too.
Btw 1.5 rooted bluetooth works just fine. And my friend Droid and my wife blackberry work just fine so I know my car bluetooth is not the problem.

not only do people with the leak
not have to worry about getting the update, they also have to worry about losing their 3g, which is what happened to me when the official verizon ota update hit. lucky for me, the local store didnt know i root and ordered me a replacement since i was under warrantee. i think my rooted phone and verizon kept trying to push the ota update back to each other freezing up my 3g speed.

Sprint 2.27.651.6 OTA -DO NOT INSTALL

Now After weeks of hard work regaw finally rooted the Official 2.27.651.5 ruu update yesterday Intrustions HERE http://forum.xda-developers.com/showpost.php?p=6686395&postcount=1
Well it seems sprint is hard at work to patch the exploit to regain root. They are pushing 2.27.651.6 OTA (over the air) update today. do not download or install untill it has been verified safe, it is beleived to be a patch to fix the root exploit.
This is just a friendly warning.
UDATED INFO-----------------
Pleased Do not get the RUU from either sprint or htc as this has been updated to the new version, if you do you will most likely lose root
Android info on rom
ModelID: HERO20000
CIDNUM: SPCS_001
MainVer: 2.27.651.6
it is still listed as 2.27.651.5

nfinitefx45 said:
Now After weeks of hard work regaw finally rooted the Official 2.27.651.5 ruu update yesterday Intrustions HERE http://forum.xda-developers.com/showpost.php?p=6686395&postcount=1
Well it seems sprint is hard at work to patch the exploit to regain root. They are pushing 2.27.651.6 OTA (over the air) update today. do not download or install untill it has been verified safe, it is beleived to be a patch to fix the root exploit.
This is just a friendly warning.
Click to expand...
Click to collapse
I figured this would be for EVO only to fix their SDcard issues.

it is only for the EVO. only update for heros that ive heard of is the gsm heros getting updated to 2.1 and thats it.

Just checked for firmware update, No Update Available.
Why is this posted here OP, is there something you know that this will be pushed to us Hero owners too?

I did the RUU then root fix, after starting up i got notified about an update also. So hmmmm. Maybe something in the update makes the system think it's an evo.

smstutler said:
I did the RUU then root fix, after starting up i got notified about an update also. So hmmmm. Maybe something in the update makes the system think it's an evo.
Click to expand...
Click to collapse
You need to do the optional Cert stuff at the bottom of the guide to disable OTA updates.

Well there are reports that Sprint HERO customers have recieve a notification of an update. So I figure better safe then sorry to atleast post the info....
Besides I'd rather be wrong on this then to not post anything and have people updating to find out it was true.
If they want to remove my post then that is fine. Also I posted this hear for any new hero owners that may have just started exploring the options to root there Hero's
Have a great day, and hopefully I am wrong about the update.

The sprint community forums has confirmed that there is an update available directly from HTC. There are posts at various android forums that is confirming an EVO update this morning to fix the sdcard issue also patches the root exploit. Most people are saying that this OTA update for the Hero patches root as well.

I can confirm that there is an update for the HERO today also, "System Upgrade 2.27.651.6 (3.17 MB)" has come up on my HERO

ok, well that proves me wrong. sorry about that. in any case, does anybody know what the update does?

kashb91 said:
ok, well that proves me wrong. sorry about that. in any case, does anybody know what the update does?
Click to expand...
Click to collapse
Probably patches root.

I find it hard to belive hero has had a root exploit less than 24 horus and sprint already has a patch for it.

The hero uses the same exploit as the EVO and the EVO patch today gets rid of root. Putting two and two together means that this update was probably really easy for them to push out.

No official list out yet but with 3.17MB, there's gotta be more than just regaining root. I would hope anyway. There's so many other useful things they could update.

Just renamed system/etc/security/otacerts.zip TO /system/etc/security/otacerts.zip.bak using root explorer.
That should hold em.
http://forum.xda-developers.com/showthread.php?t=694572

On the How to Root Sprint 2.1 Release thread, someone updated to the 2.1 RUU from Sprint website today and it put the .6 version on (or at least updated immediately) and they lost root. However, the team is trying to see if they can gain it back or at lease roll back to the .5 version.

Kcarpenter said:
I find it hard to belive hero has had a root exploit less than 24 horus and sprint already has a patch for it.
Click to expand...
Click to collapse
The exploit is based off of the EVO exploit, which was announced last week. Due to the similarity it may be more believable.

I just update the info on the first page I have downloaded and extracted both from sprint and htc and it is confirmed to be the new version

http://community.sprint.com/baw/com...-update-available-for-htc-evo-4g-and-htc-hero
Sprint says it only fixes the SD Card issue and the "Security Vulnerability" on the Evo, so obviously the Hero update was just patching root.
I find it really ... annoying.. that all they did was concentrate on patching root.... That should be SOOO far down on their priority level.

And hopefully, my comment will be seen by a lot of people, albeit a rude one, but my thoughts none the less...

[Q] How can I stop OTA from trying to download (and erroring) when I'm on leaked 2.2?

I haven't seen anyone else with this problem yet, so sorry about the new thread.
I have a Droid X that came straight from Verizon with 2.1, and was delivered a the day the official OTA for 2.2 went live. I always intended to run the leaked version of 2.3.15, but out of curiosity I went to the update page on the phone and asked it to check for an update just to see what it said.
It of course said that an update was available and then started a countdown saying it was going to begin the update momentarily. I hit the button to cancel the immediate update and then proceeded to go through all the steps that ended up with me having a phone running the leaked, rooted 2.3.15 version. It was supposed to be the DeOdexed version, but because I never formatted the system during the update the Odexed files remain. THAT I know how to fix.
My problem is that apparently because I "started" the OTA update process, Verizon wants to STILL update, even though I am already running the leaked 2.2. So multiple times a day now a little window pops up telling me "Download of update failed" and there is nothing I can do but back out of the window. I can't stop the update process anywhere, and if I go to the "Check for updates" window again it says "update in progress"
Anyone have any ideas short of clearing everything and starting all over again (which I will do if I have to, but this seems like an interesting unique problem that some of you might want to know about or tackle.)
Thank you

Look on your sdcard for a folder named "cache" and delete it. That MIGHT fix it. This is just a guess.

couldnt find it. any other ideas?

How about you SBF back to the 2.1 and then update to OTA 2.2 and check this thread out here for - OTA 2.2 Deodex'd

dr154 said:
How about you SBF back to the 2.1 and then update to OTA 2.2 and check this thread out here for - OTA 2.2 Deodex'd
Click to expand...
Click to collapse
so if i downloaded the 2.2 ota update in rom manager i can still sbf down to 2.1? just wanna make sure its ok before i brick my phone. lemme know thanks

Hey man, I'm completely a guide-following noob here, but I've got to tell you...I'm not sure you can do that.
I know the OTA changes the bootloader, which means if you sbf back then the efuse will be triggered and brick you. I'm not sure how far the update has to go before it makes that change. It doesn't sound like it's done anything on yours, but I'd ask some more knowledgeable people here first

tdrake2406 said:
so if i downloaded the 2.2 ota update in rom manager i can still sbf down to 2.1? just wanna make sure its ok before i brick my phone. lemme know thanks
Click to expand...
Click to collapse
If you have the official OTA 2.2 then no you can't downgrade back to 2.1 though the means of SBF because OTA 2.2 changes the kernel and baseband of the device which are not compatible with 2.1.
Question to everyone worried about receiving the OTA 2.2 and keeping the leaked 2.2, your getting better performance from the OTA 2.2 then the leaked 2.2 version, just my thought.

if only someone had the answer!!!!!