.32 users, you might not know it, but you have a small problem...

[mcp770]

Awesome reply thanks! Coming from blackberry I'm surprised there is no way to wipe the phones bootloader and all and install a truly full system loader and all. Last question would be if gingerbread chimed out at some point as say 3.0. Since it stands to reason all new phones will be manufactured with 3.0 do you think something will become available as a full phone setup image to fix all components rather than just patches like these supplemental updates? Surely a new ui won't have 2.2 base files required?

 

[sephtin]

Awesome reply thanks! Coming from blackberry I'm surprised there is no way to wipe the phones bootloader and all and install a truly full system loader and all. Last question would be if gingerbread chimed out at some point as say 3.0. Since it stands to reason all new phones will be manufactured with 3.0 do you think something will become available as a full phone setup image to fix all components rather than just patches like these supplemental updates? Surely a new ui won't have 2.2 base files required?

I see this as being totally up to moto... but honestly, with thier take ont he whole locked bootloader... gl with more opening of anything. :S

 

[mcp770]

Well with all that said I honestly felt the risks were explained prior to the first leak and I did it anyway in the hopes that the community as a whole would figure out a solution. I still believe the people working on cracking the kernal will succeed at done point and people are trying their best. If that means sitting on rubix 1.9 I can live with it given the rom is light years better than stock. Motorola will have to realize the brick returns could be eliminated if they just give up locking down open source software. TBH may have misled some but honestly the term"leak" says it all. There are three ends to this game. 1. Community will overcome. 2. With lte coming online you're sol as the 3g phones dwindle into memory and you live with the newest rom you can till upgrade. 3. Say its stolen for insurance replacement or purposely brick and return the phone to store taking you chances. I loaded the leak so honesty is my choice till renew or fix is found. But in the end noone is truly screwed...except maybe moto.

 

[Tanium]

noob reply

Well I seen this so here it is.
over on p3's site.
A few posts down below his. 34 patch post.

Ok a person uploaded a full back up from a brand new phone.
thing is this phone had the new bootloader.
But was running. 15
So people we're posting thank you along with other info
Just something to check out.
Look into this info.
There was no way of going back but then how could .15 be loaded.
I seen it as this guy somehow got a new phone with the new bootloader.
That had 1.5 installed.
So this back up would allow the load of 1.5 because it was made with the
new bootloader.

Edit http://www.mydroidworld.com/forums/...tloader-30-04-w-system-version-2-3-151-a.html

 

[Greg_droid]

Some people are saying that a .34 sbf will fix it, because it might not look at kernel. I hope this is true, but I am worried it might not be. Although there is evidence that it is true (the full .32 sbf will work on a .34 ota user, even though the kernels are different).

The easiest and most surefire way to get .32 users back on the OTA track is to have them revert back to .15, then OTA to .34, then install the rom they want. P3Droid says he has a way back, someone needs to ask him to release it already....

Might the easiest way be, as you suggest, to sbf .34 when that full sbf comes out? that's only a matter of time. why are you rep pried it won't work?

 

[CD95YJ]

Really I think both ways would work to get leak users back to stock but why would you want the extra work of flashing 2 full sbf's (2.3.15 & 2.3.34) when you could just flash 1?

Sent from my DROIDX using DroidForums App

 

[droidxchat]

Some people are saying that a .34 sbf will fix it, because it might not look at kernel. I hope this is true, but I am worried it might not be. Although there is evidence that it is true (the full .32 sbf will work on a .34 ota user, even though the kernels are different).

The easiest and most surefire way to get .32 users back on the OTA track is to have them revert back to .15, then OTA to .34, then install the rom they want. P3Droid says he has a way back, someone needs to ask him to release it already....

Might the easiest way be, as you suggest, to sbf .34 when that full sbf comes out? that's only a matter of time. why are you rep pried it won't work?

I'm worried it won't work because...

The reason people are saying the kernel might not be checked by sbf is because the .15 sbf worked on a few dif kernel builds. But does the sbf actually ignore kernel? Or does it accept a few specific kernel releases?

But the fact that the .32 sbf works on .34 is more evidence that it ignores kernel, so a full .34 sbf will probably work for .32 users

Sent from my DROIDX using DroidForums App

 

[djdlite512]

Breathe easy. TBH released this:

TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader

Shows these guys can be trusted. Patience is the key.

 

[P3Droid]

Some people are saying that a .34 sbf will fix it, because it might not look at kernel. I hope this is true, but I am worried it might not be. Although there is evidence that it is true (the full .32 sbf will work on a .34 ota user, even though the kernels are different).

The easiest and most surefire way to get .32 users back on the OTA track is to have them revert back to .15, then OTA to .34, then install the rom they want. P3Droid says he has a way back, someone needs to ask him to release it already....

Might the easiest way be, as you suggest, to sbf .34 when that full sbf comes out? that's only a matter of time. why are you rep pried it won't work?

I'm worried it won't work because...

The reason people are saying the kernel might not be checked by sbf is because the .15 sbf worked on a few dif kernel builds. But does the sbf actually ignore kernel? Or does it accept a few specific kernel releases?

But the fact that the .32 sbf works on .34 is more evidence that it ignores kernel, so a full .34 sbf will probably work for .32 users

Sent from my DROIDX using DroidForums App

What are you talking about, you have no clue what so ever, this is just pure bull and not how the update or the sbf files works at all.

You are a fountain of misinformation and lies.

To anyone reading this, there is zero truth to this information and it should be taken with less than a grain of salt.

 

[droidxchat]

more naysay from p3droid without actually addressing a single point. thanks for finally releasing a fix to a problem you caused, but if my posts were wrong why did you have to release a fix at all?

 

[CD95YJ]

@droidx - I think what you fail to realize is that as with everthing modificaton related, p3 and tbh stated to go to 2.3.32 at your own risk. Now honestly they didn't even have to put out the files to get everyone to stock, they could have sat back and watched as everyone smashed their phones for a replacement as the only way to get one back to stock for gingerbread, but they are a bunch of stand up guys and got us all back to stock. I for one will trust tbh and p3 any time.

BTW did you ever flash 2.3.32? If not why is this such a big deal to you? I flashed it and even paid for the tbh app from the market, they fixed things like they said they would because they value their customers and are true to their words... case closed.

Sent from my DROIDX using DroidForums App

 

[droidxchat]

My intention was never to put the blame on anyone. Only to point out that there was a problem and that p3 needed to release the fix that he said he had and thankfully did end up releasing. Go back and reread, I said that multiple times.

I never went to .32.

Sent from my DROIDX using DroidForums App

 

[CD95YJ]

@ droidX - "my intention was never to place blame". Um in both this thread an the other one you started you did exactly that, and even in a sense called out p3. I don't know the guy from adam, but I know his work to be quality and his word to be honest.

Sent from my DROIDX using DroidForums App

 

[droidxchat]

I did place blame, because it was his fault. But like I said my overall intention was not to place blame but to get him to release the fix and to make people aware that they need a fix, that they have a problem. One which will be resolved if they apply the fix he released.

Sent from my DROIDX using DroidForums App

 

[mcp770]

I did place blame, because it was his fault. But like I said my overall intention was not to place blame but to get him to release the fix and to make people aware that they need a fix, that they have a problem. One which will be resolved if they apply the fix he released.

Sent from my DROIDX using DroidForums App

I installed the leak fully aware of the risks. I didn't feel mislead in any way and have only been a droid user for one month. You are launching some kind of personal attack and it really isn't welcome. Also they did release what they hope are the fixes as promised and I am running them along with Rubix. Keep it to yourself or pm p3droid.