[Project Cheesecake] Unlocking the DEFY bootloader! - ABANDONED

Search This thread

samcripp

Retired Recognized Developer
May 20, 2010
1,048
1,774
Sanford
So we just got the Atrix unlocked, and i dont own a defy, but i think the method could work for you guys as well.

Im gonna need a few things from you guys to check servers, and once i figure out whats up i will be handing out more perfect instructions.

I would like to give credit to navalynt for creating the files use to search the test -clouds for updates.

Anyways. all i need to begin with is a build.prop from your current most up to date stock build.

i will come back in a few hours and check the thread.

also if you guys have a good irc i could use to comunicate with devs i apreciate it.

EDIT: i would like to add that im not promising anything, nor am i asking for donations or devices. i just want everyone to have an unlock.
 
Last edited:

pjgowtham

Senior Member
Apr 25, 2011
845
177
Hmm..I heard that someone told that atrix's methord wont work on defy........may be it would be wrong......
 

Gusar321

Senior Member
May 5, 2011
404
71
The Atrix uses a different bootloader, so the method of unlocking that will indeed not work on the Defy.
 

samcripp

Retired Recognized Developer
May 20, 2010
1,048
1,774
Sanford
I need a build.prop for froyo.

No one said we are going to apply the ATRIX bl. Im gonna search for a defy build.

Sent from my MB860 using XDA Premium App
 

gommers1978

Senior Member
Oct 26, 2006
640
252
I need a build.prop for froyo.

No one said we are going to apply the ATRIX bl. Im gonna search for a defy build.

Sent from my MB860 using XDA Premium App

This is the froyo build.prop from the latest 3.4.2-117 UK ROM i pulled it out of a nandroid of this official ROM.

Hope it helps.

P.S. Rename to build.prop
 

Attachments

  • build.prop.txt
    5.6 KB · Views: 300

viper.

Senior Member
Feb 10, 2010
364
76
USA
LG V30
Sony Xperia 5 IV
build 3.4.2-117. uk=2.2.1

Build prop from user gommers1978on first page is from 2.2.2 ver(3.4.2-177)
_________________________________________
Links to ginger threads

2.3.4
4 .5 .1 -134 Orange GB Blur Thread xdaforums.com/showthread.php?t=1127085
4 .5 .1 -128 Orange GB Blur Thread xdaforums.com/showthread.php?t=1116522

Android 2.3. 3
4 .5 .1 -112 Orange GB Blur Thread xdaforums.com/showthread.php?t=1106375
4 .5 .1 -85 Orange GB Blur Thread xdaforums.com/showthread.php?t=1081957


Sent from MB525 using fingers
 

Attachments

  • build.prop.txt
    5.6 KB · Views: 37
Last edited:

57op

Senior Member
Jun 9, 2011
450
297
The latest froyo version is 3.4.2-179-2, whose kernel ( 179 ) is also used in CyanogenMod.

BTW, i've attached the relative build.prop file.
 

Attachments

  • build.prop.txt
    5.6 KB · Views: 35
Last edited:
  • Like
Reactions: multiplash

samcripp

Retired Recognized Developer
May 20, 2010
1,048
1,774
Sanford
UPDATE!

i have not forgot about the DEFY. sorry ive just a bit confuse by the sbf you guys have available and the information on your system.

but i assure you once i figure out a solution for mounting the build.prop safely into my atrix i will begin testing servers.

if anyone would like to get started on doing this themselfs. you need to be on whatever is, the OFFICIAL (not leaked not made up like cm7) build for the defy.

the link is here! use the instructions loosely as of course you are using a different phone. if i had device it be easier for me to search. im working on saving money to buy one.

further this is the original project cheesecake thread that found the unlock for international users. i recommend you take a read and see how they use the difference techniques for searching.

credit goes to navalynt for the search method
 

57op

Senior Member
Jun 9, 2011
450
297
I would try, but a the moment i'm on cyanogen.
Maybe when i'll have some time...

Has anyone tried if this method works?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 24
    So we just got the Atrix unlocked, and i dont own a defy, but i think the method could work for you guys as well.

    Im gonna need a few things from you guys to check servers, and once i figure out whats up i will be handing out more perfect instructions.

    I would like to give credit to navalynt for creating the files use to search the test -clouds for updates.

    Anyways. all i need to begin with is a build.prop from your current most up to date stock build.

    i will come back in a few hours and check the thread.

    also if you guys have a good irc i could use to comunicate with devs i apreciate it.

    EDIT: i would like to add that im not promising anything, nor am i asking for donations or devices. i just want everyone to have an unlock.
    22
    So, it's done!
    Here are two file:
    flash_unlocked_recovery.zip: Flash this sbf inside CWM. It will replace your boot,recovery and devtree. If you've installed an Froyo-Rom it's possible that you can't boot because this installs a gingerbread-kernel.
    Download: http://www.mediafire.com/?jupfdktq54qxahz

    start-bootmenu.zip: Reboot into Stock-Recovery and "flash" this zipfile.
    It doesn't change anything. It just starts your already installed bootmenu to open the doors.
    Download-New(now kills recovery before start to avoid problems):
    http://www.mediafire.com/?xt5lo5qerd7c8wy

    Download: http://www.mediafire.com/?m273eadwvpz2x6c

    I'll inform quarx and epsy about this. If this kernel doesn't have RIL(I don't know how to check this) maybe we'll have custom-kernels via kexec soon.
    22
    wrap-up

    Summoning Gods of Motorola DEFY
    Quarx, Epsylon3, maniac103, ga1axy, m11kkaa, walter79.


    (ga1axy is the one who invented bootmenu for our Defy)


    Finally... :highfive:
    Once more there's a ray of light towards our legendary Defy to use custom kernel.
    custom kernel : better custom rom experience.
    locked bootloader : no custom kernel.
    but there's another way, Kexec, kernel execution. :fingers-crossed:

    Previously, last year, Kexec method was abandoned,
    due to when RIL (it's about call, sms) reinitialized, it forces the whole system to reboot.. :(

    For those of you missing the exciting news,
    you should start reading it from here, page 53. :D
    http://xdaforums.com/showthread.php?t=1169557&page=53

    NI55AN, with his normal Defy (not eng-version one),
    realize that he could flash unsigned custom zip from stock recovery.
    thanks to m11kkaa who guide and help to do it.. ;)

    It's about "special" stock recovery which could flash custom unsigned zip (not came from motorola).
    this could pave the way for kexec boots from stock recovery. :eek:

    If this thing doesn't have RIL, kexec will do first init,
    and kernel doesn't crash, and could work properly. :good:
    18
    Code:
    [15:09:16] <kholk> I've got an OMAP3 device
    [15:09:18] <kholk> Motorola Milestone
    [15:10:25] <Quarx> you will not do kexec for ML?
    [15:12:25] <kholk> Milestone has already got 2ndboot
    [15:13:33] <Quarx> 2ndboot is useless..
    [15:13:53] <Quarx> radio part/usb/audio doesn't work
    [15:14:09] <kholk> even if I port kexec on Milestone
    [15:14:16] <kholk> that basically does the same job 2ndboot is doing
    [15:14:28] <kholk> I could get USB and audio to work
    [15:14:32] <kholk> but radio will never work
    [15:14:48] <Quarx> but kexec is not 2ndboot...
    [15:15:18] <kholk> yeah, but radio will never work
    [15:15:23] <Quarx> why?
    [15:15:34] <kholk> TI Wrigley 3G can't be rebooted
    [15:15:42] <kholk> and it will panic when reinitialized from nothing
    [15:15:51] <kholk> and instead of rebooting itself, it will reboot the entire device
    [15:17:03] <Quarx> that's sad:(
    [15:18:35] <kholk> yeah
    [15:18:43] <kholk> Milestone and Defy users
    [15:18:50] <kholk> will never get nothing more than that
    [15:19:24] <kholk> sad enough
    [15:19:36] <Quarx> no other ways?
    [15:19:50] <kholk> probably not
    15
    i'd flashed my sbf after a soft brick and went into recovery and thought... oh crap need CWM but i thought I'd try it anyway and it worked.
    Kinda did it out of laziness =]

    Edit: I'm not doing further development work... i'm no developer so credits should, as always, be to the developers