• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

New ICS Leak .239

Yep, .239 has the keys for a release not engineering build but it won't install on anything, maybe something to run up the build # to .240 or whatever they want the OTA to be, who knows? .232 and holding for me........
 
dautley said:
Yep, .239 has the keys for a release not engineering build but it won't install on anything, maybe something to run up the build # to .240 or whatever they want the OTA to be, who knows? .232 and holding for me........
Click to expand...
What's that mean?
 
dautley said:
It means it showed up on Motorola's cheesecake (in house privet update) servers but it's not a build you can actually flash to your phone.
Click to expand...
Oh, ok, I was thinking you meant it was some sort of phantom build or something, not an actual build.

So do the other released builds go through the same process of getting released to their private server first and then released, or is this something different?
 
wildkitten said:
Oh, ok, I was thinking you meant it was some sort of phantom build or something, not an actual build.

So do the other released builds go through the same process of getting released to their private server first and then released, or is this something different?
Click to expand...

It is a phantom build of sorts as WE can't use it but it counts as a build. All of the ICS official leaks like .232 have been pulled of the Motorola servers, were not really officially suppose to have them but they are very stable betas that get kind of leaked by accident on purpose and evaluated. All of them have been much better than .905, no data drops, both CPU cores active, runs much better than any Gingerbread build. .232, .235, .238 all rock solid with everything working. The only bad thing is .235 and .238 has increased security that prevents you going back to the upgrade path. .232 will allow you to FXZ back to .905
 
dautley said:
It is a phantom build of sorts as WE can't use it but it counts as a build. All of the ICS official leaks like .232 have been pulled of the Motorola servers, were not really officially suppose to have them but they are very stable betas that get kind of leaked by accident on purpose and evaluated. All of them have been much better than .905, no data drops, both CPU cores active, runs much better than any Gingerbread build. .232, .235, .238 all rock solid with everything working. The only bad thing is .235 and .238 has increased security that prevents you going back to the upgrade path. .232 will allow you to FXZ back to .905
Click to expand...

So what in your opinion do you think it means that they didn't accidentally on purpose release .239?

Also, why prevent people from going backwards? My PC doesn't keep me from uninstalling Windows 7 and putting on Windows 95 if I want.
 
wildkitten said:
Also, why prevent people from going backwards? My PC doesn't keep me from uninstalling Windows 7 and putting on Windows 95 if I want.
Click to expand...

New version of security and encryption in .235 and .238 prevent you from ever going back to Gingerbread. .232 has the current version of security we use so its not upgraded, making it possible to FXZ back to .905

I really have no clue what .239 is/means, just speculation....
 
dautley said:
New version of security and encryption in .235 and .238 prevent you from ever going back to Gingerbread. .232 has the current version of security we use so its not upgraded, making it possible to FXZ back to .905
Click to expand...

For clarification ... with 6.7.235 and newer you can not go back to anything older than 6.7.235. This includes ICS and Gingerbread.

... Thom
 
dautley said:
New version of security and encryption in .235 and .238 prevent you from ever going back to Gingerbread. .232 has the current version of security we use so its not upgraded, making it possible to FXZ back to .905

I really have no clue what .239 is/means, just speculation....
Click to expand...

I guess I'm curious as to what your opinion is on why they make it impossible to go back to previous versions. I mean, no one would accept it if our computers couldn't have a previous OS installed on it.

And what keeps us from like reformatting our phones and putting whatever we want on it like we do computers?
 
locked bootloaders keep us from from installing what ever we want. If a phone has an unlocked bootloader we can do what ever we want to it but verizon is keeping the bootloader locked down.
 
wildkitten said:
I guess I'm curious as to what your opinion is on why they make it impossible to go back to previous versions. I mean, no one would accept it if our computers couldn't have a previous OS installed on it.

And what keeps us from like reformatting our phones and putting whatever we want on it like we do computers?
Click to expand...

Moto and Verizon did the same thing with the Razr. No opinion on why, maybe for ease of tech support?? whatever the reason, it's just the way it is. That's why locked bootloaders suck, I don' like it either. :(
 
I read (don't you love it when a post starts like that) a while back an article about locking down smartphones and not letting people revert to older versions of the OS. I wish I knew where I read it, but I vaguely remember following a link from another thread, so who knows where it was. Anyway, the Carriers are responsible for technical support of the phones and the typical lifespan for a smartphone type unit is very close to 2 years. In that two year period, it is expected that each production unit will receive (I believe the number was) an average of 5 offical updates and normally one of these is an actual upgrade to the OS as opposed to a minor update. By locking the bootloader, the vast majority of a particular model of phone, within a month of an update are running the same OS. This makes (what little bit of) support (that you might get) much easier to handle. If you have ever dealt with support for your phone and were running an older "official" OS version, the ONLY help you will get is that you need to upgrade before they can help you. Remember, with smartphones, the OS is built for the individual phone model. You cannot take the OS for the Razr and install it "as-is" on the Bionic and even get the phone to boot.

On your PC, which used to be a much more expensive piece of equipment than a phone and has a typical lifespan of 4+ years, the OS manufacturer normally handles the technical support. Yes, the equipment manufacturer in a lot of cases handles the front line of support, but will very quickly hand it over to the OS manufacturer if the problem isn't a basic setting type issue. Also, on a PC, the OS may have vendor specific crap in it, but the OS is the same as the OS on any other machine running it. In other words, if you had a Dell, a Gateway, an IBM and an HP all on the bench next to each other and one Windows installation DVD, you could intstall it on any machine you choose and it would work. Over time, even OS manufacturers discontinue support of older OS packages.

On your phone, you only get handed over to the OEM if the problem appears to be equipment related. So the Carrier supports the OS entirely. This means that you have two dozen (lets say) models of phone in thier expected lifespan in service at any time and that many OSs. If all of the phones, on average, have had 3 updates, now you have approximately 72 different OS versions possible out there. If you lock things down and force updates as much as possible, you should have only 24 OSs to support at any given time. Since your tech support staff all support multiple devices, the fewer OSs that you have at a time should mean an easier job for tech support and thus a better experience for the phone owner.

You are welcome to contrive any conclusions from the above that you like, but again it is just a replication of something that I read on-line.

Cheers,
BigRedGonzo
 
I'm not a dummy, but I havent rooted or flashed a phone in fear of bricking it. With that said, is there a hand holding step by step set of instructions that dont send you off onto link after link saying d/l this and then come back when you've done that...blah blha blah...

I'm thinking of going to ICS on my Bionic and would like that warm fuzzy before doing so.

Thanks guys..and umm any gals...
 
1) Download this file :) 6.7.232 This is the latest leak that you will be able to recovery from if something happens.
2) Copy the file to your sd-ext on your phone. Anywhere will work just remember where you copied it to. Sd-ext comes up as a D:/ or some other letter drive when you plug your phone in. It is not the MOTO drive.
3) Turn your phone off.
4) Press and hold both volume buttons and then press the power button at the same time until a menu appears.
5) Use the volume down button to move to the recovery option and then use the volume up button to select recovery.
6) When the droid with the ! shows up press and hold both volume buttons again until a menu shows up.
7) You are now in recovery.
8) Select install zip from sd card (or update from sd card or update from zip i can't remember what it says) using volume up or down and then the power button to select.
9) locate the file you copied over to your sd-ext and select it with the power button.
10) Answer yes that you want to install.
11) Let it install and then reboot.
12) When it is rebooting it will say android updating and some number of some number. Let it go till the phone starts.

Good luck and PM me if you need anymore help
 
So, I've read where you should back up, create a backup , etc.

Is that part of the above steps?
 
I don't see that in the steps above. Probably because the only method of making a backup (that I know of anyway) requires your phone to be rooted. Flashing this leak does not require a rooted phone.

If you were to take your phone and copy the contents of your internal SD card, you can ensure that you don't lose any pics or media files. You really shouldn't worry about saving app or syatem data as ICS will probably not play nicely with any GB settings. make sense?

In summation - you will lose whatever is on your internal SD card if you do not copy it out first. Hopefully if you have any music or photos you've been saving them to your external SD card.
 
Its been over 2 weeks since this dud-leak. No new leaks. No word on a soak test...

Hopefully, .238 is with Verizon for their approval before soak testing begins. Would be nice to see some signs of ICS before Sept.
 
I heard .240 is out but i would not play with it yet. You do not need to back up anything if you are just applying the update nothing will be erased, only if something goes completely wrong will your data be wiped when you restore.
 
That actually sucks. I was hoping that no new leaks meant we were close to OTA... And the little info I found is that .240 can't be rooted yet.
 
When Googling finds ONE message on .240 in the last week I have to question how valid the information is.

(With the last release of the Droid X you could not go back and you could not root after installing it. There seems to be a solution now ... six months later.)

... Thom
 
You must log in or register to reply here.
Back
Top Bottom