PATCH — Focused 1.9.0 update to 2.3.340

[sephtin]

What will happen if we are on Focused 1.9.0 for 2.3.15 and we patch up to 2.3.32 will that ROM still work or should i use "928Droid X Official OTA 2.2 Froyo 2.3.15 "Back to Stock" first then use the patch?
I am trying to work my way up to this patch.

If you want to apply the leak (2.3.320) or the OTA from Verizon (2.3.340), then the best way to do it, is to .sbf back, and install either of those cleanly (The OTA is a patch, so you can only install it if you have a clean 2.3.15 /system.).

Note: My patch is essentially a driver update, that's specific to the 2.3.3xx version. If you don't have the leak, or the OTA, then you don't need/want it.

It doesn't add/change anything in Focused.. it's specifically to update Focused (LEAK VERSION) for the latest 2.3.340 patch which wasn't available when 1.9.0 was released.

 

[Inkarnit]

What will happen if we are on Focused 1.9.0 for 2.3.15 and we patch up to 2.3.32 will that ROM still work or should i use "928Droid X Official OTA 2.2 Froyo 2.3.15 "Back to Stock" first then use the patch?
I am trying to work my way up to this patch.

If you want to apply the leak (2.3.320) or the OTA from Verizon (2.3.340), then the best way to do it, is to .sbf back, and install either of those cleanly (The OTA is a patch, so you can only install it if you have a clean 2.3.15 /system.).

Note: My patch is essentially a driver update, that's specific to the 2.3.3xx version. If you don't have the leak, or the OTA, then you don't need/want it.

It doesn't add/change anything in Focused.. it's specifically to update Focused (LEAK VERSION) for the latest 2.3.340 patch which wasn't available when 1.9.0 was released.

So then it's kinda like 1.9.1? Where's the changelog? This is BS.

 

[sephtin]

haha sorry i'm dumb. So if I'm already on .340 and installed 190 leak, i should still apply this patch right?

You can apply this patch, yes.

 

[sephtin]

haha sorry i'm dumb. So if I'm already on .340 and installed 190 leak, i should still apply this patch right?

Yes, it updates .320 portions our the Rubix rom to .340 including the system info. Hopefully market will work..lol

The market will work EXACTLY as it does for those on the 2.3.340 OTA after the patch.

 

[Inkarnit]

haha sorry i'm dumb. So if I'm already on .340 and installed 190 leak, i should still apply this patch right?

Yes, it updates .320 portions our the Rubix rom to .340 including the system info. Hopefully market will work..lol

The market will work EXACTLY as it does for those on the 2.3.340 OTA after the patch.

I can confirm this. My market showed 199 results for porn before the patch and 199 results for porn after the patch

 

[sephtin]

If your on ota .15, why don't you flash or ota the .340 update and be done?

So I can just flash this update file Download the Official 2.3.340 OTA Here - Android Forums and it should work?
My question is " once I flash if I am on a ROM made for 2.3.15 will it still work or should i do something ahead of time?

Installing the leak (2.3.320), or the OTA (2.3.340) is really a question for one of the thousands of existing threads on the subject... including the one you linked.

Some things you'll want to know ahead of time:
The update.zip (the OTA 2.3.340) doesn't replace files, it patches them. So, to apply it your /system directory must be a pristine stock motoblur 2.3.15 versions... otherwise when the OTA patch checks the versions of the files, it will find something that isn't the right version and the patch will fail.
The BEST way to apply the OTA is to .sbf back and apply it (either via the update.zip, or via Menu> Settings> About Phone> System updates.

GL!

 

[sephtin]

I can confirm this. My market showed 199 results for porn before the patch and 199 results for porn after the patch

...








... 10 char

 

[thelionelking]

Although, I believe drod stated that his future versions will be released specifically for 2.3.3xx only..

So we need to update to this version anyway if we want any of drod's future work? That makes me sad...

 

[Inkarnit]

Although, I believe drod stated that his future versions will be released specifically for 2.3.3xx only..

So we need to update to this version anyway if we want any of drod's future work? That makes me sad...

What? Why? Why would a dev continue developing ROMs for an outdated version? The OTA brings people to .340, so everyone should get up to .340 in order to get the latest and most up-to-date ROMs. You have a few options on how to get there, but there's no reason to stay on 2.3.15 except for having a full sbf which, I believe, will be resolved soon, and may in fact already be resolved with that .320 full sbf.

 

[thelionelking]

Although, I believe drod stated that his future versions will be released specifically for 2.3.3xx only..

So we need to update to this version anyway if we want any of drod's future work? That makes me sad...

What? Why? Why would a dev continue developing ROMs for an outdated version? The OTA brings people to .340, so everyone should get up to .340 in order to get the latest and most up-to-date ROMs. You have a few options on how to get there, but there's no reason to stay on 2.3.15 except for having a full sbf which, I believe, will be resolved soon, and may in fact already be resolved with that .320 full sbf.

That's exactly why... I don't like flashing without a safety net. I do hope the .320 full sbf works with .340 but until confirmed, I don't want to take the leap. Usually drod makes everything so easy for those of us that are lazy by just making his new versions flashable over the last version. Even though sbf'ing is not that much of a pain, I never look forward to it...

 

[sephtin]

Although, I believe drod stated that his future versions will be released specifically for 2.3.3xx only..

So we need to update to this version anyway if we want any of drod's future work? That makes me sad...

What? Why? Why would a dev continue developing ROMs for an outdated version? The OTA brings people to .340, so everyone should get up to .340 in order to get the latest and most up-to-date ROMs. You have a few options on how to get there, but there's no reason to stay on 2.3.15 except for having a full sbf which, I believe, will be resolved soon, and may in fact already be resolved with that .320 full sbf.

So, when 2.3.9 came out, ROMs were created based on that version. Then 2.3.13, and 2.3.15. ROMs were updated for those versions. ROMs that were designed for 2.3.15 would install over someone's 2.3.9, etc. Everyone was happy.

However, Moto.. in their infinite wisdom made changes with the 2.3.3xx versions, that makes them not play well AT ALL with previous versions. So now, you can't create a ROM for 2.3.340, and have it "just work" with people on the 2.3.15 version.

Now ROM devs have to create new versions of each ROM they put out. Drod having three or four different ROMs he's working on (Blurry, Fuzzy, Focused, DX_Fission(?))... would have to keep up with 6-8 different releases.

I can't speak for drod on this... but from what I know-
--A good portion of his testers are now on 2.3.340.
--If he dev's for 2.3.340, then it's possible it could be backported to 2.3.15, but it would be very unlikely that it would be supported. (If it's broken, upgrade).
...

So to answer the question:
"So we need to update to this version anyway if we want any of drod's future work?"

Probably not. If drod doesn't make it available for 2.3.15, I could probably throw together a backport.. but I'm sure he will if there's enough interest in it... BUT, I wouldn't expect it to be tested or supported like the 2.3.3xx versions will be. (??).

 

[dadsterflip]

Kernels on .320 and .340 are both the same. .340 was just compiled later on as stated by p3droid. Both are the same. Nothing different.
If you were on the leak and brick. He also stated that since both are the same you can sbf to. 320 then. 340 sbf system update and works perfectly. People have done it. After you sbf to. 340 you are officially back on the official ota train.

Sent from my DROIDX using DroidForums App

 

[sephtin]

Kernels on .320 and .340 are both the same. .340 was just compiled later on as stated by p3droid. Both are the same. Nothing different.
If you were on the leak and brick. He also stated that since both are the same you can sbf to. 320 then. 340 sbf system update and works perfectly. People have done it. After you sbf to. 340 you are officially back on the official ota train.

Sent from my DROIDX using DroidForums App

"Kernels on .320 and .340 are both the same."
Link? Preferably from a Motorola source (developer, changelog, ??)? Thanks!

 

[thelionelking]

So we need to update to this version anyway if we want any of drod's future work? That makes me sad...

What? Why? Why would a dev continue developing ROMs for an outdated version? The OTA brings people to .340, so everyone should get up to .340 in order to get the latest and most up-to-date ROMs. You have a few options on how to get there, but there's no reason to stay on 2.3.15 except for having a full sbf which, I believe, will be resolved soon, and may in fact already be resolved with that .320 full sbf.

So, when 2.3.9 came out, ROMs were created based on that version. Then 2.3.13, and 2.3.15. ROMs were updated for those versions. ROMs that were designed for 2.3.15 would install over someone's 2.3.9, etc. Everyone was happy.

However, Moto.. in their infinite wisdom made changes with the 2.3.3xx versions, that makes them not play well AT ALL with previous versions. So now, you can't create a ROM for 2.3.340, and have it "just work" with people on the 2.3.15 version.

Now ROM devs have to create new versions of each ROM they put out. Drod having three or four different ROMs he's working on (Blurry, Fuzzy, Focused, DX_Fission(?))... would have to keep up with 6-8 different releases.

I can't speak for drod on this... but from what I know-
--A good portion of his testers are now on 2.3.340.
--If he dev's for 2.3.340, then it's possible it could be backported to 2.3.15, but it would be very unlikely that it would be supported. (If it's broken, upgrade).
...

So to answer the question:
"So we need to update to this version anyway if we want any of drod's future work?"

Probably not. If drod doesn't make it available for 2.3.15, I could probably throw together a backport.. but I'm sure he will if there's enough interest in it... BUT, I wouldn't expect it to be tested or supported like the 2.3.3xx versions will be. (??).

Sounds fair. drod's roms have been superb so whatever the decision will be is cool to me!

 

[ericsch333]

Kernel version
2.6.32.9-gca645b6

I was on .320 and flash .340

My 2.3.340: 2.6.32.9-g55626e1

Regarding flashing from .320 to .340... there is a "system" flash from .320 to .340, but I don't know of a way to get from the .320 kernel to the .340 kernel. ?
Probably not a big deal.. but who knows (wish we had a changelog.

yeh me to (changelog) well maybe the full sbf for .340 will get leaked and then we can update the kernel.