*Bootloader Unlock Research* Cheesecake Clarification

Search This thread

projektorboy

Senior Member
Sep 3, 2010
417
95
Phoenix, AZ

projektorboy

Senior Member
Sep 3, 2010
417
95
Phoenix, AZ

phydo

Senior Member
Apr 11, 2010
494
97
Lebanon, NJ
Don't try it on the Bionic unless the devs come out with a Bionic specific version. There are enough differences between the hardware (especially the kernels) that that you could brick the hell out of your Bionic by trying it.

If there was a droid 3 version the daring could look at that. Honestly if I'd booted my bionic in the last 4 months I'd try changing it.

Sent from my Galaxy Nexus using Tapatalk 2
 

Steve125

Senior Member
Aug 19, 2010
191
38
The 904 update was leaked via cheesecake a couple weeks ago on rootzwiki

Sent from my Eclipsed DROID BIONIC using xda premium
 

draexo

Senior Member
Let me know if you get it. I don't even use my bionic anymore. If you don't I'll install drop box and give it to you

Sent from my Galaxy Nexus using Tapatalk 2

I got it somewhere else. But I have no idea what I am doing with it. Other than it seems to work.

There are so many servers. Why can there not be a simple script (simple for me the unlearned) that just checks each once?

---------- Post added at 04:15 PM ---------- Previous post was at 04:04 PM ----------

Let me know if you get it. I don't even use my bionic anymore. If you don't I'll install drop box and give it to you

Sent from my Galaxy Nexus using Tapatalk 2

I got it somewhere else. But I have no idea what I am doing with it. Other than it seems to work.

There are so many servers. Why can there not be a simple script (simple for me the unlearned) that just checks each once?

This may seem quite silly, but I can host it as well!

Here is the link to the file I downloaded and then hosted.

http://*******/8sCyl

Ok, ad.fly not supported. Here is a direct link.

http://droidrepo.info/the-repository/viewdownload/11-droid-tools-for-multiple-moto-devices/64-cheesecake-apk-v2
 

twinkyz1979

Senior Member
Feb 1, 2011
452
86
****
Samsung Galaxy S24 Ultra
I got it somewhere else. But I have no idea what I am doing with it. Other than it seems to work.

There are so many servers. Why can there not be a simple script (simple for me the unlearned) that just checks each once?

---------- Post added at 04:15 PM ---------- Previous post was at 04:04 PM ----------





This may seem quite silly, but I can host it as well!

Here is the link to the file I downloaded and then hosted.

http://*******/8sCyl

Ok, ad.fly not supported. Here is a direct link.

http://droidrepo.info/the-repository/viewdownload/11-droid-tools-for-multiple-moto-devices/64-cheesecake-apk-v2

can someone please use a normal link?

---------- Post added at 05:06 AM ---------- Previous post was at 05:03 AM ----------


never mind i got one
 
Last edited:

projektorboy

Senior Member
Sep 3, 2010
417
95
Phoenix, AZ
Any possibility that this Cheesecake app could be updated to run on the ICS leaks? Or is there something inherent in the ICS builds that would prevent this no matter what?

Cheesecake relies on the fact that you're on a system build that is eligible for an OTA. ICS Leak versions are essentially "invisible" to the OTA servers because of that. The OTA .ZIP files are built to only update if a certain system version is present, so Cheesecake doesn't work.

From what I understand, Cheesecake merely does simple spoof and server alteration to make your phone look like it should receive a leaked .zip file. Because new ZIP files won't flash over the leaks anyway, it ends up being pointless.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    3
    3
    So I got up to 10 posts just so I could post this in the dev forums because this has really been bugging me. I love flashing, customizing and doing **** to my phone because it's my property. Up until this point I found out how to do all the stuff I wanted to just by reading and a little trial and error (hence the lack of posts) but this topic (C Block and Verizon) has me a bit annoyed to say the least. I'm a lawyer (well technically a law school graduate waiting on my NY Bar Exam results that should be out Nov. 4th) and as such I have a significant amount of free time on my hands. Now I've read through some of the C Block rules promulgated by the FCC and yeah as discussed it does seem to hinge on "reasonable" and let me tell you, most all laws do (it's a pain in the ass but that's what gives us lawyers work). I've worked for 4 different federal court judges in the Eastern District of NY and I know how federal court works. I (and I'm hoping that there are some other lawyers out there willing to do this) am offering my services pro bono (that means for free) to get the ball rolling against Verizon. If people effected by this (us 4G phone owners on Verizon, got to have standing in federal court to bring a suit and we do) can jump on this stuff before the FCC (who's probably bought off by Verizon and other companies) determines what "reasonable" is without the input of end users we might (and I stress MIGHT) have a shot at forcing Verizon to unlock the bootloaders. Again, this is just an idea because I'm bored and need to keep my legal skills sharpened. I post this here so that perhaps I can find other people to join together because there's no way in hell I could do it all by myself. The first step would be going back through FCC and court rulings to determine what "reasonable" is in similar situations and the process moves on from there. I just wanted to throw my two cents in as this community (among others) has helped me tremendously and has allowed me to do (nearly) whatever I want with MY property. I just thought that since I'm no dev it'd be nice to try to give back in a way that uses my skill set.
    3
    The provisions aren't really specific, so there's ruin for some lawyering. I'd make the argument that if Verizon/Motorola prevents the app from functioning this is the same as preventing the app from being used

    Sent from my DROID BIONIC using XDA App
    3
    P3 flashed it and it does absolutely contain a bootloader update.

    The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.

    HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
    There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.


    The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.

    There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays! ;)

    Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.

    WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!

    Thanks to those who got the file and thanks to P3Droid for guinea pigging.

    Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things! :D


    So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.

    So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.