yashsingh1/xdaforums huggingface dataset:
[Defy General] @non4:
This breakthrough could be extended to other improvements like better kernel optimization, perhaps a new thread by the devs to discuss where to go from here is the answer :)

Sent from the real world by hacking into the matrix
[Defy General] remix96:
Yes, but with an unlocked bootloader, we can improve battery life, performance... all ;)
[Defy General] nidhish91:
Why dont we spam Motorola on twitter with unlocking bootloader thing or anyone of us having good contacts with famous tech sites can bring this Motorola autocracy in limelight. We need boot loaders unlocked and we need to do something to get Motorola's attention.
[Defy General] remix96:
+1
[Defy General] NI55AN:
Things like this have been done. We can't rely on Motorola. The devs are doing a great job despite the boot loader. When they get stopped they don't give up, any problem in the future I have no doubt in our devs that they can fix it like with the Hardware Acceleration.
[Defy General] nidhish91:
All I see is the petition signed which is also dead now.
[Defy General] jassi32:
+1

thats what i am talking about ...... trust developers ......have faith .....

they are the best guys on xda ......HWA is done ....

rest will also be done ...... don't except everything on single day .....

Donate them or else at least hit thanks button on their posts of success ....
[Defy General] Kayant:
You haven't searched enough look back on all the comments on motorola facebook page, twitter and a search xda for the many threads about this and also the 2 massive petition with more than 20,000 signatures. This happened every day for about a month or so and what do we get for spamming them - a so called developer razr edition phone.... like seriously moto you expect people to pay for another device for an unlocked bootloader(Really) but like it's been mentioned earlier there is no point in waiting for motorola if you want a device with an unlocked bootloader if you want that then samsung is your manufacturer of choice all phones are unlocked from the factory and are very hard to brick :D or LG but then people don't buy their devices so developement is little or doesn't exist and HTC is in the middle with their policies. If not be happy that the defy has come so far thanks to the amazing work of the awesome devs and hopefully more will come for you guys in future. I really want my defy back now :(.
[Defy General] nidhish91:
I do have a hope one day one of our awesome devs will find a way to unlock our bootloaders and that day we will laugh on Motorola. I am learning myself how to get into main stream development. Lets see what future has.

S3nt fr0m my D3fy/w1u1 GB st4BL3
[Defy General] kadopt:
Read here http://xdaforums.com/showthread.php?p=28302773
[Defy General] pepcisko:
lucky verizon SGS3 users :) http://www.epiccm.org/2012/07/kexec-and-proof-of-concept-source-built.html
[Defy General] pepcisko:
https://plus.google.com/105844328547178759011/posts/NaZUCL6oe1q
[Defy General] marhensa:
does kexec method works on defy?

i hear the news last year kexec caused no radio (sms, call, data) to be working.

Sent from TapaTalk | MotoDEFY - Android Jelly Bean 4.1.1
[Defy General] ksrao_iete:
wow...is it true?
[Defy General] walter79:
kexec works only without radio. (sms, call....)
[Defy General] pepcisko:
You're right. But - the latest (from the g+ link) says : " Voice calls and SMS function as expected, but the SIM appears to be failing provisioning resulting in no 3G/4G connectivity." ... which is definitely a progress from last time. I think it's worth following their progress, even though it's not defy/defy+ related.
[Defy General] vanyas:
It is for Samsung, not for Defy.
[Defy General] adamo3957:
Main issue = defy bootloader doesn't allow custom recoveries
[Defy General] idoavni99:
But this issue is already solved using the bootmenu to bypass the bootloader check
[Defy General] josuearisty:
Maybe they use the same kexec method, if they gets it, we can get it later.
[Defy General] adamo3957:
That isn't actually correct

After the kernel is loaded the android boot process starts, boot menu is positioned to boot before android, its the 2nd unit module, when boot menu selects the custom recovery it is not loaded from the recovery partition it is loaded from the system,

The Samsung mod is based of running using the recovery system which we cannot change
[Defy General] GodSlayer:
Here is an idea - what if we build a special recovery, as a kernel module, which will be loaded right after the kernel is loaded. The module will then load it's own kernel, unloading the previos kernel and then loads the system.
[Defy General] m11kkaa:
I think this works, because a recovery-kernel does not initialize RIL so there are no conflicts if you do a kexec-boot.

That's what kexec does. but this causes RIL-problems on defy.
[Defy General] adamo3957:
Exactly

For kexec to work on the defy it would have to be before initialization of the radio
[Defy General] yodawg:
Thanks for the info. How is the situation on our Defy(+)? Do we also have an extra kernel only used for recovery, or uses recovery the same kernel as in normal boot?
[Defy General] m11kkaa:
Our Recovery-Kernel should work with kexec.

The problem is that there is no (known) way to access the phone in recovery-mode. (adb disabled and nothing is executed from NAND so we can't start 2ndinit)
[Defy General] adamo3957:
Unless if we can change the recovery whilst the device is running however I can't remember what the issues were etc
[Defy General] yodawg:
How do you mean that? Change it while the device is in normal mode or while it is already in recovery? And how would you do that... I'm asking because it sounds like you already know a way but have some problems.

Also, for my better understanding, please correct me if I'm wrong:

Our "custom recovery" runs the normal kernel, only the stock recovery runs on the recovery kernel, right?

And the custom bootmenu also runs on the normal one... is this correct?
[Defy General] skeevydude:
For the last 2 questions, Yes.

It may be possible to make a stock recovery zip that executes kexec and a new kernel, but we also have no way of signing that zip and the unsigned zip hacks were fixed with android 2.1 so that's not an option either. We either have to figure out how to get kexec to boot with the current kernel (the RIL issues) or an exploit to get stock recovery to execute unsigned code, neither of which I have any idea on how to do.
[Defy General] m11kkaa:
I tried to enable adb inside recovery with the file /data/local.prop. But it seems init tries to read the file before mounting the data-partition - stupid thing xd
[Defy General] yodawg:
How do you even know recovery tries to read it?

On sourceforge Motorola hosted the sourcecode for Userspace + Kernel (nothing new).

Are there also somewhere sources for bootloader/ recovery/ some other useful things?

Sorry for my noobish question, but in earlier bootloader versions of the defy, was it possible to flash another kernel? If so, could one simply overwrite the bootloader with this old one?
[Defy General] m11kkaa:
No it was never possible(as far as I know).

And if it would be true we couldn't downgrade.
[Defy General] 57op:
So if someone finds a way to enable ADB in recovery-mode, will we have the probability to unlock bootloader?
[Defy General] m11kkaa:
unlock? maybe never! forget this word. only workarounds like kexec.

But you should know even if we would have adb inside recovery you would need your pc to boot your phone.
[Defy General] espaciosalter20:
And a init script to change the order of booting? Load kernel module before radio...

Enviado desde mi MB525 usando Tapatalk 2
[Defy General] m11kkaa:
That's not possible because we can start scripts at init-stage only.

If you aren't a developer please don't ask such questions. If it would be possible that easily we, would have a working solution now.

Believe me: Such questions sounds really stupid in the ears of a developer.
[Defy General] yodawg:
Is the driver for wrigley compiled into the kernel or loaded as module? If so, removing (or moving to another location) the module from the filesystem maybe would prevent initialization so that we could do it when the kexec-loaded kernel has booted.

Is the driver opensource? So that one could look for special files inside /proc or /sys which could potentially used for resetting the device...

Sorry for being silly... Probably all the things I mention have been tried before, but it's just that I stumble around and then see something and think... "oh maybe THIS is gonna help us and hasn't been discovered before"... So can you give any links where all the things that were tried before are listed, or maybe links to chatrooms or chatlogs where the devs discussed all of that? Would be cool.
[Defy General] adamo3957:
Its in the kernel, we can move it as that would be a kernel change at which point it would fail boot loader check

We are all stumped at the min

And I don't have chat logs etc, I was no good at dev work when all this was going on
[Defy General] espaciosalter20:
Did you think that was polite? Because, the same thing can think anyone with more knowledge than you of your questions... So, be a little more kind next time...

Enviado desde mi MB525 usando Tapatalk 2
[Defy General] Ant-ON:
When you boot the kernel via kexec can not reinitialize the modem. Perhaps not initialize modem when booting the original kernel? We can replace modules in the rootfs. modem_pm_driver - modem driver. If the device does not open, then it will not be initialized?

The reasoning on the subject ... Perhaps they are meaningless(
[Defy General] yodawg:
I was also curious about modem_pm_driver. However, it sounds like it's only the power management driver, which I doubt it helps us. As mentioned, the main driver is compiled into the kernel, which we cannot change... also we cannot prevent initializing it.
[Defy General] adamo3957:
This may sound semi stupid but, if the modem pm driver handles start up power then if it was removed and then used in the kexec wouldn't that bypass rail initialization? No power means it was never started?
[Defy General] skeevydude:
Its not that simple, by the time it even gets to that point, the radio is already active and on. Removing that would do nothing as far as kexec is concerned. Kexec has to be done very very early with the stock kernel which may not be possible, or by running it from the recovery kernel which doesn't activate the radio and has no way of getting commands as far as we know.

Interestingly, apparently NI55AN can install CM9 from stock recovery. Maybe he has an Engineering Defy and the Engineering Defy's can run unsigned code from the stock recovery? While that doesn't help the Bravo or Milestone2, its interesting nonetheless.

Perhaps there's something exploitable with the recovery kernel's init? Although if there was, I'm sure it would have been found by now.
[Defy General] pranks1989:
If this in any way may help, I started a discussion in Moto forums for Defy+ about the bootloader. May be we can again try once by commenting a lot and spamming there?! I have been closely folllowing this thread but all the time it seems we are hitting the stone!! I know already many attempts at spamming in SNS etc has been done. So may be try this too..!

Discussion is here
[Defy General] yodawg:
Probably, but if everybody would think so, there wouldn't be any root exploits found on locked phones ;)

Can you provide a link where he described that?
[Defy General] NI55AN:
I don't have an eng defy... I flashed a 2.3.4 sbf on my green lenses. The recovery is 3e but it allows me to flash cm9 and gapps etc.
[Defy General] pranks1989:
Oh!! Then that SBF has an unsigned kernel?! A signed SBF with unsigned kernel that is! Link me. I want to test and if true will inform the devs
[Defy General] espaciosalter20:
somebody knows where the signed-key is??? I mean, if i took kernel from http://sourceforge.net/projects/moto-defy.motorola/files/DEFY%20LATAM%20MOL%20%28FROYO%29/3.4.2-107_JDNL-6_R02/, or from a extracted boot.img where i have to look to find the piece of code where signed key lies???

I still believe the answer for break that key is using a computer grid project.....
[Defy General] G00fY2:
But only if you're a dreamer. Just look for RSA-1024 factorization on Google.;)
[Defy General] espaciosalter20:
:eek: well, yeah...it's really really hard, but also I know there is a LOT of people who wants to break that key (assume that because this thread and others as well has multiple statements about unlock that signed kernel), if at least 1000 of us "donate" free cpu time of, let's say, two cores in this task, there will be at least, 2000 cores calculating every single hash of that key which, in some point (and by that i mean maybe months), can give us freedom...

Enviado desde mi MB525 usando Tapatalk 2
[Defy General] royale1223:
Can you tell as what displays on rsdlite when your phone is connected? Also can you flash a froyo sbf and and see if it works. Just putting this out here : Milestone users have a vulnerable recovery.
[Defy General] NI55AN:
Can't flash lower cg sbf's. This sbf has become my permanent one
[Defy General] G00fY2:
Dream on. 1000x2000 are 2.000.000 cores for one year... And Hardware power isn't all. First we would need a realy, realy tricky algorithm.

Till now noone made this. A few years ago, there were 100.000$ prize money to factorize RSA-1024. And please think about other areas, where RSA is used to make our live save. For example website and email encryption, electronic payment systems or identity cards. If it would be possible for a smartphone community to decrypt such a key, think about what other people could do with RSA-cryptosystem.;)
[Defy General] royale1223:
That's great. Could you upload recovery.img from a full nandroid backup?
[Defy General] hsrars-d:
F*ck that! :D

They will invent more and better cryptosystems eventually.

Sent from my MB525 using Xparent ICS Tapatalk 2
[Defy General] fiskenigaten:
+1

I have bl6 froyo, so it might work on my defy+
[Defy General] NI55AN:
When I flash cm9 through stock recovery. I cannot access stock recovery anymore.... just freezes on boot logo so will I have to reflash sbf?

Edit: I mean for the backup of recovery.img
[Defy General] m11kkaa:
How you flashed a custom rom through stock-recovery? Are you sure you don't mean CWM?
[Defy General] NI55AN:
I flashed it through stock recovery

Android recovery 3e
[Defy General] m11kkaa:
Can you give instruction how todo that? Normally StockRecovery only accepts signed zipfiles.
[Defy General] zyxwvut:
Which sbf are you flashing to get this strange recovery?
[Defy General] NI55AN:
Just the normal way... don't have a way to record to show....maybe I'll try using my old iPhone 3 to show later.

I'll post a drop box link once I've uploaded the sbf I'm using but beware no downgrade to froyo after
[Defy General] m11kkaa:
This sbf would really help. If that's true we could do kexec-boots via stock-recovery(theoretically).
[Defy General] NI55AN:
sbf

http://xdaforums.com/showthread.php?t=1739761

I had lost this sbf recently and got it back due to this person uploading it... dont know if the mirror still works
[Defy General] zyxwvut:
Im very aware of the non downgrade to froyo by flashing 2.3.4 sbf's. But like m11kkaa stated, this could pave the way for kexec boots from stock recovery
[Defy General] pranks1989:
I would have loved to test it but mine is BL7! Moto guys flashed it once in service center!! Someone please confirm its working because if it does then it will be a whole new light in Defy community!!
[Defy General] Hellmanor:
I can check it, but I have two questions.

Will I be able to restore it to froyo?

And what exactly I have to check?

I have red-lensed Defy, so it's like Defy+, yup ? ;)
[Defy General] NI55AN:
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
[Defy General] Hellmanor:
So if I restore this system from recovery I'll be able to downgrade? I just dont wanna lose warranty :D
[Defy General] zyxwvut:
I think a backup of recovery would be a good starting point for testing!
[Defy General] m11kkaa:
yes and don't forget devtree. We'll need both in combination.
[Defy General] NI55AN:
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?
[Defy General] m11kkaa:
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
[Defy General] NI55AN:
Which site would you recommend for uploading the backup of the partitions boot, recovery and devtree?
[Defy General] pranks1989:
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??
[Defy General] Hellmanor:
Speedyshare, ofc.
[Defy General] devilthehellraiser:
Maybe make a torrent file anyway best of luck
[Defy General] klovan200:
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.)
[Defy General] m11kkaa:
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.
[Defy General] NI55AN:
hope it works =]
[Defy General] m11kkaa:
The recovery-kernel contains full-description of the NAND-partitions:

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
[Defy General] espaciosalter20:
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
[Defy General] yodawg:
Amazing! One little noob question, though: Could this work on BL7-Defy+ too?
[Defy General] m11kkaa:
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.

In theory yes, just backup everything and try it :D

But currently these files are only good for devs. So wait until we can do something useful with it.
[Defy General] zyxwvut:
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!
[Defy General] m11kkaa:
All thanks should go to NI55AN if this works :)
[Defy General] NI55AN:
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
[Defy General] zyxwvut:
for me start-bootmenu.zip is not taking me to bootmenu I get thrown into a bootloop. A battery pull and it boots just fine. I'm using Quarx's CM10 20120720 defy+ build on Red lense defy

I did flash CM10 through stock recovery and that was pretty cool :)

I did not lose my stock recovery aftery flashing CM10 as Ni55an did
[Defy General] m11kkaa:
The blue led will show for 3sec just like on a normal boot :)

Just press VolDown and you will get to bootmenu. Booting with recovery-kernel can't work because too much drivers are missing :)
[Defy General] Hellmanor:
So now we have to w8 what Quarx or Epsylon have to say?
[Defy General] hsrars-d:
Yes. Fingers crossed for recovery not containing RIL :D :thumbup:

And maybe someone should make a new thread for kexec if this leads to anything ;)

Sent from my MB525 using Xparent ICS Tapatalk 2
[Defy General] bharaththeunique:
Oh boy.....any update from quarx?????...have been refreshing this page since 3 hrs now........
[Defy General] nidhish91:
Patience is the key to success. I have a gut feeling that we are getting a new kernal soon(please God). Good find NI55AN and great work mikkkaa.

S3nt fr0m my D3fy/w1u1 GB st4BL3
[Defy General] pranks1989:
I guess RIL is not there in the kernel! Why? Coz i see it gets started up by the init.rc in stock.. Had it be in kernel I guess it would have been started earlier! Not sure though.. Lets wait what Quarx or epsylon has to say..
[Defy General] bharaththeunique:
Quuuuuaaarrxx....pls look into this...

PS...sorry for the over excitement.....but I haven't run a custom kernel in a long time now.....my prev device was a Samsung galaxy 551....using custom kernels there messed up my graphics....and now defy is locked.....so...glimmer of hope...
[Defy General] marhensa:
can't stop reloading,

to see what Quarx or Epsylon3 would say about it.

custom kernel : better custom rom experience.

Sent from TapaTalk | MotoDEFY - Android Jelly Bean 4.1.1
[Defy General] m11kkaa:
BTW: If you need to flash an full-sbf just flash this sbf(which does the same like "flash_unlocked_recovery.zip").

http://www.mediafire.com/?ana046e5f57860i

Then you can boot into recovery and flash any signed custom-rom(cm7,cm9,cm10, maybe more). No need to root :D
[Defy General] bharaththeunique:
Its bl6 2.3.4 rt????coz if its bl5....I don't know if I can use it....I am currently on bl6 2.3.6 base.....:fingers crossed:
[Defy General] jalal-jap:
its work on bl7?
[Defy General] m11kkaa:
Just try it. If it doesn't work you just have to flash an full sbf to recover your CWM-backup.

The only thing you shouldn't do is to flash the full-sbf of shadow(the source of the unlocked recovery). Just flash the CWM-update or my "unlocked_recovery.sbf"
[Defy General] bharaththeunique:
OK...so its like flashing only the boot,devtree and recovery images....???