[Project Cheesecake] Unlocking the DEFY bootloader! - ABANDONED

NI55AN · Jul 20, 2012

would you prefer a backup of recovery?

doesnt bother me just means reflash, could record it like i said earlier when i reflash cm9 after

---------- Post added at 07:32 PM ---------- Previous post was at 07:28 PM ----------

Its a 2.3.4 sbf ergo > no downgrade
i made that error... i have a green lense but it may have proven to be a useful error

Hellmanor · Jul 20, 2012

So if I restore this system from recovery I'll be able to downgrade? I just dont wanna lose warranty

zyxwvut · Jul 20, 2012

I think a backup of recovery would be a good starting point for testing!

m11kkaa · Jul 20, 2012

yes and don't forget devtree. We'll need both in combination.

NI55AN · Jul 20, 2012

right, well just backing up my cm9 installation and then ill flash the sbf, install 2nd init and backup recovery and devtree... this is all yes?

do you know why the stock recovery seems to be innaccessible if i flash through stock recovery?

m11kkaa · Jul 20, 2012

Ok i tried it.
1) flashing the partitions directly(without full-sbf) does work
2) the recovery really contains the test-keys
3) it's not a "normal" recovery. it has a file-chooser like CWM.

I'll write an update.zip which enables adb or starts bootmenu and then the analysis and hacking can BEGIN!!! I really hope, this kernel does NOT contain RIL

NI55AN · Jul 20, 2012

m11kkaa said:
Ok i tried it.
1) flashing the partitions directly(without full-sbf) does work
2) the recovery really contains the test-keys
3) it's not a "normal" recovery. it has a file-chooser like CWM.

I'll write an update.zip which enables adb or starts bootmenu and then the analysis and hacking can BEGIN!!! I really hope, this kernel does NOT contain RIL

Which site would you recommend for uploading the backup of the partitions boot, recovery and devtree?

pranks1989 · Jul 20, 2012

m11kkaa said:
Ok i tried it.
1) flashing the partitions directly(without full-sbf) does work
2) the recovery really contains the test-keys
3) it's not a "normal" recovery. it has a file-chooser like CWM.

I'll write an update.zip which enables adb or starts bootmenu and then the analysis and hacking can BEGIN!!! I really hope, this kernel does NOT contain RIL

Wow!! I hope this time we are really very near! You directly flashed the partitions... So I guess though I am in BL7 I could do that too??

Hellmanor · Jul 20, 2012

Speedyshare, ofc.

devilthehellraiser · Jul 20, 2012

Maybe make a torrent file anyway best of luck

Sent from my MB525 using xda app-developers app

klovan200 · Jul 20, 2012

Mirror:

http://acrane.eu/defy/other/

flash_unlocked_recovery.zip - m11kkaa
start-bootmenu.zip - m11kkaa

b-r-dt.zip - .img of boot, recovery, devtree (NI55AN)

(If someone will need web-storage for DEFY project, send me message and I'll give FTP access to my server.)

m11kkaa · Jul 20, 2012

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.

NI55AN · Jul 20, 2012

hope it works =]

m11kkaa · Jul 20, 2012

The recovery-kernel contains full-description of the NAND-partitions:

Code:

major minor  #blocks  name      alias

   7        7       4096 loop7
 179       32    1912832 mmcblk1
 179       33        128 mmcblk1p1      mbmloader
 179       34        512 mmcblk1p2      mbm
 179       35        512 mmcblk1p3      mbmbackup
 179       36          1 mmcblk1p4      ebr
 179       37        512 mmcblk1p5      bploader
 179       38        512 mmcblk1p6      cdt.bin
 179       39       4096 mmcblk1p7      pds
 179       40        512 mmcblk1p8      lbl
 179       41        512 mmcblk1p9      lbl_backup
 179       42       1024 mmcblk1p10     logo.bin
 179       43       2048 mmcblk1p11     sp
 179       44        512 mmcblk1p12     devtree
 179       45        512 mmcblk1p13     devtree_backup
 179       46       4096 mmcblk1p14     bpsw
 179       47       8192 mmcblk1p15     boot
 179       48       8192 mmcblk1p16     recovery
 179       49      14336 mmcblk1p17     cdrom
 179       50        512 mmcblk1p18     misc
 179       51        512 mmcblk1p19     cid
 179       52       4096 mmcblk1p20     kpanic
 179       53     334848 mmcblk1p21     system
 179       54        512 mmcblk1p22     prek
 179       55        512 mmcblk1p23     pkbackup
 179       56     204800 mmcblk1p24     cache
 179       57    1319936 mmcblk1p25     userdata
 179        0   15558144 mmcblk0
 179        1   15557120 mmcblk0p1

and there is an additional bootparam: omap3_die_id

espaciosalter20 · Jul 20, 2012

m11kkaa said:
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: 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.

can you explain how it's that a "normal" stock recovery can flash zip files may be related with unsigned kernel?

Enviado desde mi MB525 usando Tapatalk 2

yodawg · Jul 20, 2012

Amazing! One little noob question, though: Could this work on BL7-Defy+ too?

m11kkaa · Jul 20, 2012

espaciosalter20 said:
can you explain how it's that a "normal" stock recovery can flash zip files may be related with unsigned kernel?

Enviado desde mi MB525 usando Tapatalk 2

Maybe you know that there is a way to reload the running kernel: kexec
The problem is that its impossible/really hard to reinitialize RIL(all the phone stuff). Recovery-kernels normally are very minimal. They don't contain any drivers which aren't needed etc.
So if the RIL wasn't initialized before you boot a kernel via kexec, ther will be no problems with that.

But FIRST we must confirm that this recovery-kernel doesn't contain RIL-drivers. I don't know how to do that but I informed quarx and epsilon. I'm sure they know how todo that.

So we'll just have to wait for their report.

yodawg said:
Amazing! One little noob question, though: Could this work on BL7-Defy+ too?

In theory yes, just backup everything and try it

But currently these files are only good for devs. So wait until we can do something useful with it.

zyxwvut · Jul 20, 2012

wow this is an amazing find. Who would have ever tried flashing custom roms through stock recovery and discover this! This could be a breakthrough!

m11kkaa · Jul 20, 2012

All thanks should go to NI55AN if this works

NI55AN · Jul 20, 2012

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

[Project Cheesecake] Unlocking the DEFY bootloader! - ABANDONED

Senior Member

Senior Member

Senior Member

Recognized Dev / Inactive Recognized Contributor

Senior Member

Recognized Dev / Inactive Recognized Contributor

Senior Member

Senior Member

Senior Member

Senior Member

Member

Recognized Dev / Inactive Recognized Contributor

Senior Member

Recognized Dev / Inactive Recognized Contributor

Senior Member

Senior Member

Recognized Dev / Inactive Recognized Contributor

Senior Member

Recognized Dev / Inactive Recognized Contributor

Senior Member

Similar threads

Top Liked Posts