yashsingh1/xdaforums huggingface dataset:
[Defy Q&A, Help & Troubleshooting] fiskenigaten:
Yes, you are very confused! :silly: You know, when you install a custom rom it totally replaces your stock rom. The stock recovery is not there to recover your stock rom/restore it (where would it restore it from?? I'll have to disappoint you, but your phone is not magic!). The stock recovery can only wipe user data and install updates by Motorola onto an already existing system! You will never be able to restore your system to its original state if you don't have a backup or some idea what retail version you were on. But you'll definitely find a similar sbf over at droid developers or Walter's sbf thread.

When you see the exclamation mark with the cute green guy, you have to press vol+ and vol- together to reveal the stock recovery.

Motorola recovery = stock recovery = the recovery made by Motorola. You can acces it buy pressing vol- while powering up, through bootmenu>recovery>stock/motorola recovery or bootmenu>recovery>custom/stable recovery>advanced>motorola recovery
[Defy Android Development] m11kkaa:
We've found a stock-recovery which allows us to install customroms.

This means we don't need to root and to install 2ndinit after flashing a full sbf :)

Does NOT work with BL7!

So now we have new instructions to go from stock to custom:

1) Flash you favorite stock-rom via RSDLite

2) Flash unlocked_recovery.sbf via RSDLite

3) Hold Vol-Down while powering on the phone. Now you should see "Android Recovery 3e"

4) Flash your custom rom(CM7,CM9,CM10,...). Please note, that this ROM has to be signed with Google's testkeys, otherwise you will get an verification-error. Some rom's by themer's aren't signed. I'm working on an solution for that.

5) You have to know: "unlocked_recovery.sbf" flashed a gingerbread-kernel. If you are using a GB-based rom, just ignore this step. Otherwise you might need to flash a Froyo-Kernel via CWM to boot your rom.

After you flashed this kernel Unlocked-Recovery will be lost, but you don't need it anymore because now you have bootmenu(it's always bundled with custom roms).

Download:

unlocked-recovery.sbf: http://www.mediafire.com/?ana046e5f57860i

Froyo/Gingerbread-Kernel: http://defy.wdscript.fr/kernel/
[Defy Android Development] m11kkaa:
reserved
[Defy Android Development] m11kkaa:
reserved2
[Defy Android Development] m11kkaa:
reserved3
[Defy Android Development] m11kkaa:
reserved4
[Defy Android Development] mihovil13:
Nice!

---------- Post added at 08:16 PM ---------- Previous post was at 08:11 PM ----------

Can this help to use custom kernels?
[Defy Android Development] brajesh.sharma87:
Unfortunately no.
[Defy Android Development] jassi32:
thank you :)
[Defy Android Development] espaciosalter20:
Sorry. But I really don't see what is the advantage of this, since we could root and install a 2nd-init recovery... I was excited with this when we thought that could be a way for overpass bootloader...

Enviado desde mi MB525 usando Tapatalk 2
[Defy Android Development] marhensa:
Sorry, but why so rude about it?

Sent from TapaTalk | MotoDEFY - Android Jelly Bean 4.1.1
[Defy Android Development] nidhish91:
The biggest advantage is that you dont need to go through the rooting procedure or the 2nd init method. Brings ease to the process.

Please be grateful rather than sounding rude.
[Defy Android Development] pabloltg:
WOW, this would be the recovery stock modified to install customs roms right? but we still 2nd init?.

i ask it for restores, advanced options, and others stuff ..
[Defy Android Development] fiskenigaten:
m11kkaa, does the sbf include the kernel too or only the recovery? Also, it would be really handy if a flashable 2nd-init bootmenu was provided in the first post :)
[Defy Android Development] m11kkaa:
We can't modify this recovery. Everything is still signed.

It does contain the boot-partition because boot and recovery are using the same devtree. Sure, I can set a link to other threads which are about bootmenu.
[Defy Android Development] espaciosalter20:
I wasn't meant to be rude! Just I was pointing my disappointment with a failed method to do a kexec on our defy... That's all!!

EDIT: @vaserbanix creates custom sbf that everyone can flash, which already have custom roms, root and 2nd-init...

Enviado desde mi MB525 usando Tapatalk 2
[Defy Android Development] jalal-jap:
I have defy green full flash dfp231.

i have bootloader error after flash unlock recovery sbf !
[Defy Android Development] bhupatib:
Thanks for your efforts, it does seem like a more convenient method than sbf--superoneclick--2ndinit--flash!

But some instructions are not clear. If "unlocked_recovery.sbf" flashes GB kernel as well then won't it cause bootloop if we flash the recommended CEE sbf which has froyo kernel?

Can you make a froyo version (with the latest epsylon kernel)?
[Defy Android Development] pradipsoman:
Have some doubts

1) Will this work on a new Defy+ with BL7 (with factory installed stock ROM) ?

2) I have already rooted my BL7 with the existing old method (flashing the two sbf's ). After rooting by the old method is my Defy+ with BL7 or BL6?

3) Does the method 2 change the factory installed kernel ?

4) Can I again go back to BL7 from BL6 by flashing the stock ROM? (If the rooting actually downgraded my phone from BL7 to BL6)

5) If I am already rooted with the method 2, can I still try this recovery flash method?

Am willing to experiment. But being new to Defy I wanted to confirm some basic doubts before I experiment :)
[Defy Android Development] pjgowtham:
heyyy does this install it over stock recovery????...this is so awesome.....god..from today no bricking my phone!!!!.thanks mate!!

so from now on i think we dont need 2nd init..but how did u do that with a locked bl??..this s awesome
[Defy Android Development] pranks1989:
It was great fun and all that excitement while it was being worked on in Project Cheesecake.. :) Pretty good job by m11kkaa.. If I got it right, now I too can flash the Froyo kernel to it and try all those Froyo builds when I feel like..? I got BL7 DFP1321 !!

---------- Post added at 10:21 AM ---------- Previous post was at 10:17 AM ----------

YOu got your answers there ^
[Defy Android Development] zyxwvut:
It is still just stock recovery. Everything is still signed and kernel must be as well. It's just they included googles test keys in this particular recovery so it is capable of executing .zip packages that are signed with googles test keys.
[Defy Android Development] sUpErwHoO:
Might sound dumb, and maybe it has been spoken about but what if a custom kernel is made and signed using the test keys? Won't it work? Doesn't it work the same way? Not like I know anything about coding, just asking :)
[Defy Android Development] zyxwvut:
won't work! We have always had the ability to "install" custom kernels with CWM or ADB, They just won't boot because bootloader will fail to verify the kernel is signed with Moto's RSA key

Stock recovery has nothing to do with kernel signature verification. This is simply a stock recovery that will install packages signed with google test keys. CWM has always had the ability to do this.
[Defy Android Development] hackergnome:
For the signing u can use zipsigner from play store

https://play.google.com/store/apps/details?id=kellinwood.zipsigner2
[Defy Android Development] abhifx:
someone made a "save your time" sbf files... i find that approach more elegant... but this is cool too. good finding m11kka
[Defy Android Development] pradipsoman:
So you mean to say that whatever I do, I stay on BL7, but I can downgrade my kernel from GB to froyo with this recovery flash??

And if my kernel turns to GB after rooting what was it before rooting (I mean factory stock kernel?)
[Defy Android Development] INZANEDUD:
Interesting...so i can return to froyo? If i flash a gingerbread 2.3.6 firmware

Enviado desde mi MB526 usando Tapatalk 2
[Defy Android Development] NI55AN:
Do you know why my stock recovery might be dissapearing every time. I flashed through CWM this time but still my stock recovery is inaccessible afterwards.

I tried power+VolDown and Motorola recovery in CWM.

just freezes on bootlogo every time.
[Defy Android Development] m11kkaa:
I see that most people get this thing wrong!

1) This recovery is NOT made to replace CWM

2) This recovery WILL and SHOULD be removed if you want to use another kernel(Froyo)

3) You can root your stock-rom with this recovery but after that you need to flash your original kernel if you want to boot a rom which is not compatible with this. So it's easier to use Gingerbreak in this case
[Defy Android Development] NI55AN:
Duh completely forgot sorry... green lenses therefore I'm froyo kernel my bad. Just forgot
[Defy Android Development] zyxwvut:
You CAN NOT do anything with this recovery that you couldn't do before with CWM except root a stock rom from within stock recovery!

I could be wrong but I don't think BL7 will boot a typical froyo kernel? Will it???

Your kernel doesn't turn to GB after rooting. The .zip m11kkaa provided for us to install this recovery contains boot.img(kernel), recovery.img(recovery) and devtree.img(devtree). The boot.img included is a GB kernel so thats where the GB kernel comes from. These files do nothing to root your device. Its up to you to use this recovery to flash SU binaries etc. if you wish to root your stock rom!

Without telling us your factory/stock system, nobody knows what kernel you had. You stated that you are on BL7 now so you are using GB kernel.
[Defy Android Development] pradipsoman:
If the boot.img in this recovery flashes another kernel(that too is GB as you have said) then does that mean that my stock GB kernel on BL7 is changed to another version GB kernel? I do not get it. So does Defy+ have several versions of stock GB kernels? I do see many GB kernel versions like Walters 11,22 Epsylon etc...Are all these UNMODIFIED stock GB kernels from different stock ROMS around the world??

To one of my queries, Auris has said that whatever I do on my Defy+ BL7, it will remain BL7 WITH THE STOCK KERNEL THAT CAME WITH THE PHONE. This is confusing. That's why am asking this doubt. And elsewhere in this thread, someone says that now you can flash a froyo kernel on top of any Defy (which I think is incorrect)....
[Defy Android Development] joydeep1985:
This is really helpful instead of going through pathetic long route of installing 2nd-init and then installing and rigorous rebooting . Sometimes used to piss me off . This would save a lot of time :) . Although the solution for custom Sbf is quite elegant . But I m not sure which sbf is for which bl . So i generally tend to avoid that custom sbf method to avoid any confusion . Yea one thing if someone can post how to make custom sbf . That would be quite helpful . Then everyone can make a custom sbf of their own stock / favorite rom and can keep it aside as per their own requirement :)
[Defy Android Development] espaciosalter20:
Man, did you check this anytime???. http://xdaforums.com/showthread.php?t=1691901

Custom sbf + tutorial on how to create one

Enviado desde mi MB525 usando Tapatalk 2
[Defy Android Development] neo.ank:
You are seriously confused with kernels, Recovery and other stuff..

You cannot change your kernel/ BL version ever.

You can use the custom ROMs for GB kernel..Thats it..

And as for kernels, defy cannot use a custom/ modified kernel. Every kernel needs to be signed by moto..

And since you're already rooted, it'd be better to install 2ndinit and follow the process rather getting confused with it..
[Defy Android Development] pradipsoman:
If I was confused, I would not be having a working MS2Ginger 4.0 on it :)

I just wanted to clear some basic doubts as I am new to this phone. So I do expect answers. I still dont have an answer on this question.

How many stock GB kernel versions are there? As many as different retail stock versions or only a few used across in the many stock ROMS?

I know that this is not an issue with regards to someone having a BL6 or down. I know that BL7 guys are stuck with their BL7 and GB kernel.

I tried this stock recovery on my BL7 but it fails. I also tried the scotland MIUI ROM with the BL7 patch, but that also fails :(

So I request the author of this thread to give a warning at the beginning of this thread ...."Not for those with BL7" :)
[Defy Android Development] m11kkaa:
What you mean with "it fails"?

Bootloader-error or just not booting?
[Defy Android Development] pradipsoman:
Bootloader error. On pressing the power button, immediately goes to the bootloader error instead of booting :(
[Defy Android Development] m11kkaa:
is the warning at OP big enough? :D:D:D
[Defy Android Development] walter79:
Boot.img in sbf is the problem. Only flash the recovery and devtree.

If you like to use all update.zip you have to resign the zip with this tool. http://www.chinadigitalcomm.com/sig...ss-verification-of-stock-recovery-t11099.html
[Defy Android Development] hackergnome:
Need help over hee...

I tryed to flash CM10 with this recovery but gave me verification fail...

Also twerp has same issue along with Battery fix...

PS:I used the zip file posted on Cheesecake thread...
[Defy Android Development] claudiobastos:
Verification fail is almost always corrupt file. Check md5 :)

Froyo Red 525 xda premium
[Defy Android Development] walter79:
Did you use latest CM10 20120726 ? If not resign zip.
[Defy Android Development] hackergnome:
ok that one worked... twrp works... but not battery fix... ill resign...
[Defy Android Development] diogo.sena:
Good Job

Thank you m11kkaa !

To everyone thinking that this Unlocked recovery has no point, think again...

Just bricked my custom recovery trying to install TWRP in Quarx CM10 from 02/08.

This procedure saved me, just flashed this recovery and reinstalled cm10 from that, no need for data wipes, just perfect!
[Defy Android Development] AnTerNoZ:
if it's possible to get this file manager working with this stock recovery http://xdaforums.com/showthread.php?t=1646108?

if ur know what's going wrong on ur phone ur just can correct it this way...

Jelly powered.Defy
[Defy Android Development] droid_<3er:
I've been following news of this new recovery on the Project Cheesecake thread for a while.

But I do have a few questions.

1: So will WIUI v4 work? I don't know if it's a Google SignApk signed zip.

2: So I don't need CWM anymore? Because when using 2nd-init, the stock recovery usually

doesn't work to wipe the 2nd-init rom.

3: Do I still need to root or it is rooted already after I flash the ROM? Because I use TELUS

8500/1900/2100 I usually need to use baseband switcher and that needs root...

Thanks to everyone who contributed to Project Cheesecake. I know this wasn't what we expected,

but it's absolutely AWESOME
[Defy Android Development] ofmb:
ehmmm... what if maybe easy recovery is more powerful than we thought...?!

prologue:

2ndboot\kexec doesn't work on defy mainly because of RIL panicking after soft reset and switch of kernel.

that happens because restart happens after RIL init' and linking with kernel.

idea:

* main assumption is that Wrigley 3G modem will not panic .

* let's sum all the possibilities from scripting in this recovery.

* if we end up managing to kexec another kernel from recovery, maybe it'll open a whole new option to kernel devs !

example: we can use "run_program PACKAGE:install_busybox.sh" .. so probably we can also init system..

you can see here the boot chain:

http://droid-developers.org/wiki/Booting_chain

@Devs, what say you? :confused:
[Defy Android Development] labsin:
Doesn't seem to work with latest CMX rom's??

Tried with the one from 18 Oct but gave verification fail. Had to use a much older release..
[Defy Android Development] dlhxr:
please resign the zip with google test keys
[Defy Android Development] labsin:
Tried with the tools found here on XDA and couldn't get it to work. Installed and old one and updated from the custom recovery.

Perhaps the size? (to big)
[Defy Android Development] dlhxr:
that's because the key you use to sign is not a recognizable test key.

Please replace the attached two files in your sign-tool and try to sign again.
[Defy Android Development] labsin:
Thanks, will try next time.
[Defy Android Development] dape16:
Just wanted to say thanks for this great recovery tool! My Defy restarted itself during flash of a ROM update, and after that it was just freezing at the boot screen, recovery wasnt accessible at all. I was going to do a full sbf flash and wipe all my data when I found this. After flashing this recovery sbf I was able to flash my custom ROM again, which then started up and all my data was still there!

Thanks!
[Defy Android Development] toroloco73:
I don't have bl7

but after i flash it on my mb526 appears that

Bootloader

9.10

Err:A5,70,00,00,23
[Defy Android Development] fiskenigaten:
This basically means the kernel was made for a lower bootloader version. You've bricked your device. :^/ Its quite easy to fix with RSD-Lite, though. Do you know which bootloader version you have?

Sent through the Internet.
[Defy Android Development] toroloco73:
I flash stock sbf and my defy+ now is working...

I don't know what version is my bootloader... do you know how can i see it?

Inviato dal mio GT-I9100 con Tapatalk 2
[Defy Android Development] fiskenigaten:
You can download all the tools you need in Walter79's thread for SBFs! :) here

Check the attachments at the bottom of his first post. First you need Moto-android-depacker to depack the sbf file. The depacked sbf consists of several .smg files, e.g. cg39.smg, cg35.smg, etc. These files are for different partitions on your phone. To check the version of these files you need "ceck version of cmg.rar" (also found in attachments). Don't really remember how to use it though. Think you need to put the .smg-files in the same folder as the tool and execute it.
[Defy Android Development] lulli1:
will this work with milestone2 as well? Do we have the same dev tree?
[Defy Android Development] pravarth:
This doesn't work with the newer CM10.2 roms or the CM11 roms. It shows error status 0. Any idea why?
[Defy Android Development] Keboid:
Yes, they need newer version of recovery. probably the ext4 partition requirement of those new android versions. Older recoverys format them to ext3 with which 10.2 and 11 can't be used. Atleast thats my guess, not sure if thats the real reason.

You will need to update recovery, you can follow for example this thread.
[Defy Android Development] pravarth:
Latest cm10.2 can run on ext3 afaik, because nandroid backups do spit out ext3 file for system partition. But regardless, I think it might have something to with an updated "update-binary" or script which is incompatible with older versions, because even the update-recovery zip for cm11 give the same error.
[Galaxy S III Q&A, Help & Troubleshooting] Paul_Days:
Where do I find or add a string so my Demo Unit can have a UUID? I have installed an app that give me the error "No UUID found" and want to have one so I can run the app.

Thanks,

Paul
[HTC One S] randomnoob83:
i wanna buy a tmobile htc one s because i hear all of them have a s4 but on ebay it gives me an option for a black htc one s from tmobile but tmobile hasnt released it so im awesome its just an it doesnt have an s4 any help or clarifications ?
[HTC One S] SawManiac:
Use proper interpunction. I can't understand a word you're saying :eek:
[HTC One S] lykos:
I have an inquiry to present to the board. I wish to proceed in the purchase of a T-Mobile Black One S but have arrived to unsettling gossip on this merry board. When T-Mobile does pre-take in the--albeit dated--release of this HTC machinery, will it feature the more technologically stunning processor or a inadequate alternative?
[HTC One S] k1llacanon:
Haha lol nice .... And now answering question t mobile do sell the black one I bought the black one two weeks after it came out on tmboile contract in UK anyway
[HTC One S] randomnoob83:
my question is i want a black one s for tmobile in the us with a s4 do they exist in the us, like if i went to the tmobile store in miami and asked for a black one s would they have it
[HTC One S] lykos:
I think he is speaking of T-Mobile US. Which means we will not know until the phone is released but if I were to venture a guess I'd assume--for the better--that T-Mobile will release the phone with the S4 processor to continue combatting their rival ATT and its One X.
[HTC One S] SawManiac:
Well, thank you my good sir. :highfive:
[Nexus 7 Q&A, Help & Troubleshooting] mirrored:
Hello,

1) Is there any way to root without losing all of your data? I'm not talking about basic things that Google backs up for you.

2) Is there any way to back up your apps and data without having root?

Thank you
[Nexus 7 Q&A, Help & Troubleshooting] krelvinaz:
1) If your bootloader is still locked, Nope.

2) Need root access to do full backups.
[Nexus 7 Q&A, Help & Troubleshooting] mirrored:
And the catch is the only way to unlock the bootloader is through a process by which you lose all of your user data, correct?
[Nexus 7 Q&A, Help & Troubleshooting] Rapscallion16:
1. If your boot loader is still locked, then you have to do a full wipe.

2. If you use the Nexus Root Toolkit 1.5, you can create a backup of your apps, data and media, then restore it after root. Worked for me. :)
[Nexus 7 Q&A, Help & Troubleshooting] xxgoosexx:
try this thread. you can back up your apps with adb without root or unlocking

http://xdaforums.com/showthread.php?t=1420351
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidUser00110001:
Introduction:

Some of you may know me from my AOSP+ ROMs and my work with CodeName Android. I have previously made ROMs for the Nexus devices and some others. I had a small break but I am back now. The AT&T Galaxy SIII is one of the devices I will be building for. This is a modified stock ROM for now. Will have AOSP based ROMs soon.

Info:

UCALG1 - Modified stock ROM

Kernel - not secure for ADB access plus some other tweaks

Root, Zipalign and deodexed

Removed all bloatware

Replaced Samsung keyboard with AOSP ICS keyboard

Added enhanced reboot menu

International Boot animation and sounds

Web Presence:

Twitter

Google+

Would be best to follow me on Google+ for latest updates and news. Sometimes I post stuff there more than I do here...

Info:

UCALG1 - Modified stock ROM

Change Log:

V1.1

Added WiFi Tethering

Added init.d support

Some other tweaks but dont recall all since I have been working on this since 10 AM :)

V1 - First release

Install Instructions:

Root and Install Clockwork recovery if you have not done so

Place ROM on either internal or external storage

Up to you to wipe or not, the installer will wipe dalvik cache

Install ROM

Reboot

Enjoy!

Downloads:

ROM - HERE

Filename - SGH_I747_UCALG1_AndroidUser_V1.1.zip

MD5 - e86011a097f44e511f73e11100605f8f

Credits:

Google, AOSP, Sixstring, Codenamedroid, Braway, Romanbb, CM, peteralfonso, xplodwild and all others that I have gained knowledge and source from.

Einstein quote but modified a bit for this

I am often worried at the thought that my Android development is based to such a large extent on the work of my fellow developers and I am aware of my great indebtedness to them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidUser00110001:
Reserved...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Thanks mate, I will be adding you to the Directory

Is this AOSP base? Will AOSP themes be applicable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jroyalty7:
Thanks bro remember you from the gnex!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidUser00110001:
Thanks...This is stock modified ROM for now. Will have AOSP based ones once I am done building and testing.

Nice to see you hear :) Porting all CNA features now to the ATT GS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Good stuff, needed to know where to put you:laugh: Directory
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidUser00110001:
Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airbillion:
Rom looks really nice. Quick question, is the tethering mod enabled?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidUser00110001:
No...going to update it later on with the tether fix.