Downgrade to 902 - No app or data loss

[SamuriHL]

Ok, there's a difference between going back to the OTA path and moving forward to a new OTA path. On 232 or lower, you can get BACK to the OTA path which is currently defined as being 5.9.905. With 235+, you can't FXZ back to 905, so you can't get BACK to the OTA path. The only thing you can do is move forward. Once the NEW OTA build is selected, which I currently believe will be 247 but will only be known once it starts being pushed out OTA, then either we're already on the new OTA path by virtue of already being on the correct build (e.g. 247) or we'll have to move to the correct build using the HoB. Could be a new build. Could be an older build. For those that don't think that's possible, you don't know your history. 5.5.893 was an OTA build. 5.7.893 and 5.8.894 were not, yet, they were leaked before 5.5.893 became OTA. So even though we have 247 and we think that'll likely be the OTA, it's not guaranteed....as I've said a billion and 1 times now. If 246, for example, becomes OTA, we have to downgrade which the HoB can do. We can NOT, however, downgrade below 235 due to the security. Clear now?

 

[hisself]

Not unless you have a Xoom. In which case, why the hell aren't you running Team EOS like everyone else?

I have a gTab running JB from TeamDRH.

 

[Badger1313]

Thank you Sam. That's what I thought I understood. I guess I didn't state my question very well.

 

[SamuriHL]

Linux/Mac progress update:

Menus are written and working
discover and transfer update zip is working
md5 hashing of update zip is working
install flash is working
recovery instructions are working
root is working

TODO:
boot img creation
reinstall flashing
FXZ flashing
Repair flashing

Basically at this rate I expect to have a fully function Linux/Mac HoB by this weekend that matches the windows functionality completely.

 

[master0fursinz]

here i was thinking Sam had a working copy of JB on the Bionic... I was going to say spread the love

 

[TMYINC]

Is there any way of altering the verizon update.zip or impossible since it is signed? Doing some hypothetical thinking at the moment lol

Sent from my DROID BIONIC using Tapatalk 2

 

[Just_AGuy]

Is there any way of altering the verizon update.zip or impossible since it is signed? Doing some hypothetical thinking at the moment lol

Sent from my DROID BIONIC using Tapatalk 2

Bionic has a locked boot loader. So unless you can crack the security, then you can't alter the update zip file.

 

[mranderson1]

Like the people complaining that I didn't tell them to press the power button to select the apply update option in recovery? LMAO. I fixed it for the next version but I sure as hell ain't doing a release for that. My time is going to be spent working on the linux/mac HoB which is currently functional enough to move people from one build to another and root it.

yes yes yes yes yes yes yes! cant wait for a MAC HoB! it takes times leaving my mac and loading my windows partition! dont judge me!

 

[SamuriHL]

yes yes yes yes yes yes yes! cant wait for a MAC HoB! it takes times leaving my mac and loading my windows partition! dont judge me!

Just a word of caution....I don't own a mac so I can't test it on there. So when I release it just know you may be a guinea pig. Worse case is you load up the Windows version to fix whatever damage I caused. I'm still trying to get the reinstall option to work the way I want. It's being stubborn and pissing me off at the moment.

 

[mranderson1]

Ok, there's a difference between going back to the OTA path and moving forward to a new OTA path. On 232 or lower, you can get BACK to the OTA path which is currently defined as being 5.9.905. With 235+, you can't FXZ back to 905, so you can't get BACK to the OTA path. The only thing you can do is move forward. Once the NEW OTA build is selected, which I currently believe will be 247 but will only be known once it starts being pushed out OTA, then either we're already on the new OTA path by virtue of already being on the correct build (e.g. 247) or we'll have to move to the correct build using the HoB. Could be a new build. Could be an older build. For those that don't think that's possible, you don't know your history. 5.5.893 was an OTA build. 5.7.893 and 5.8.894 were not, yet, they were leaked before 5.5.893 became OTA. So even though we have 247 and we think that'll likely be the OTA, it's not guaranteed....as I've said a billion and 1 times now. If 246, for example, becomes OTA, we have to downgrade which the HoB can do. We can NOT, however, downgrade below 235 due to the security. Clear now?

i do not get why so many people do not seem to understand this simple simple elementary idea...its like the abc song! it doesnt go CBA!

 

[mranderson1]

lol

would be my first guinea pig experiment! bring it on! lol = D

 

[SamuriHL]

Once I get it all finished. As I said, the reinstall option is being a pain in the ass right now. And then I have to put together the FXZ flash functions and the extract recovery option. Then test it by reinstalling 247 on my own phone. So it'll be probably later tonight before it's ready. No fancy installers, either. You guys and gals will get a couple zip files.

 

[hisself]

....as I've said a billion and 1 times now. If 246, for example, becomes OTA, we have to downgrade which the HoB can do. We can NOT, however, downgrade below 235 due to the security. Clear now?

So, what are the odds that the OTA will be lower than 235?? Inquiring minds want to know :huh:

 

[SamuriHL]

So, what are the odds that the OTA will be lower than 235?? Inquiring minds want to know :huh:

Zero. VZW rejected all those builds. It'll be 246 or 247.

 

[Aldroid33]

Just a word of caution....I don't own a mac so I can't test it on there. So when I release it just know you may be a guinea pig. Worse case is you load up the Windows version to fix whatever damage I caused. I'm still trying to get the reinstall option to work the way I want. It's being stubborn and pissing me off at the moment.

I have.a.dual boot iMac. Windows on one side and.Mac.OSX on the other. So if.you want I can help test.your.beast:icon_ devil: