Database Users

[Q] help! umts_jordan nightly to ms2ginger 2.1

hello,
is it possible to switch from cm7.1-nightly to ms2ginger easily?
(cm7.1 is android v. 2.3.7 with kernel 2.32.9)
regards

Yes you can do that easily. The ms2Ginger thread has enough information on how to do that. I have switched twice from Cm7 to ms2g and vice versa.
In a nut shell just restore the manseoid back up of ms2g system, data, boot , dev tree and recovery. Before you do this just take nandroid backup of your current cm 7, which can be useful to switch back at later time if needed.
Sent from my MB526 using XDA App

ok. after installing ms2ginger it seem to be not my flavour.
i tryed to install cm72 (120131.05331-nightly) by epsylon. now, the device boots up, lights blue and green up and nothing more happens..
what can i do? (got backup but want a fresh install)
regards

now, when i push the poweron button, nothing happens..
the led lits up, when usb plugged in.. but thats all..
help?

_xo said:
now, when i push the poweron button, nothing happens..
the led lits up, when usb plugged in.. but thats all..
help?
Click to expand...
Click to collapse
CM7.2 is for Defy+ which uses GB kernel.
You can either flash CM7 kernel if it works, otherwise go to advance restore and restore boot and devtree from MS2 nandroid.

hey guyz need some help here.i own a defy+. i dont noe why but when i tried to install the walter9 MS2Ginger over the CM7.2,i got the bootloader err msg and the phone wouldnt startup.then i flashed the 2.3.6 sbf file via rsdlite and phn was back to its original working condition.then i rooted it again and then again tried MS2Ginger but after installation in recovery it asks for reboot.and after reboot, i got the same error saying
the same thing again
Bootloader
09.10
Err:A5,70,00,0023
again had to flash to original sbf
need help

coolgame said:
hey guyz need some help here.i own a defy+. i dont noe why but when i tried to install the walter9 MS2Ginger over the CM7.2,i got the bootloader err msg and the phone wouldnt startup.then i flashed the 2.3.6 sbf file via rsdlite and phn was back to its original working condition.then i rooted it again and then again tried MS2Ginger but after installation in recovery it asks for reboot.and after reboot, i got the same error saying
the same thing again
Bootloader
09.10
Err:A5,70,00,0023
again had to flash to original sbf
need help
Click to expand...
Click to collapse
Are you installing MS2G 2.1? and Did you follow the complete restore of nandroid backup, - system, data, boot, devtree and recovery?

yup i did twice.

coolgame said:
hey guyz need some help here.i own a defy+. i dont noe why but when i tried to install the walter9 MS2Ginger over the CM7.2,i got the bootloader err msg and the phone wouldnt startup.then i flashed the 2.3.6 sbf file via rsdlite and phn was back to its original working condition.then i rooted it again and then again tried MS2Ginger but after installation in recovery it asks for reboot.and after reboot, i got the same error saying
the same thing again
Bootloader
09.10
Err:A5,70,00,0023
again had to flash to original sbf
need help
Click to expand...
Click to collapse
I am searching for the instructions too:
http://forum.xda-developers.com/showthread.php?t=1468867&page=2
Will work the ms2ginger with cg version 6?
Anyone?

I had managed to get working, with instruction in the ms2ginger topic
To begin:
Put the Nandroid backup folder MS2Ginger on the SDCard in this folder: /sdcard/clockworkmod/backup
Root your DEFY and Install BOOTMENU - CWM (2ndInit-Installer 2.0.apk - install 1.0.7) or use this SndInitDefy_2.0.apk
REBOOT
run 2nd-init (voldown on blue LED)
wipe data and cache in "Stable/Custom - Recovery"
Go to "Recovery"
Go to "Latest Recovery"
Go to "Backup and Restore"
Go to "Restore" (system+data)
reboot.
Booting up can take a while, max is about 10 minutes.
THEN(if you want to try also the 3.0)
wipe data/cache/dalvik; Do an advanced recovery and only restore system and data from 3.0NG.

[Q] Help with Defy (green lens) and custom ROMS

I am currently on a stock Android 2.1-update1 TMobile US ROM on my Defy (green lens) ROM. I would like to try out CyanogenMod 7.1 (or 7.2 RC) and need help confirming my understanding of the process. I am already rooted and have installed the GoAPK recovery.
1. I need to flash my kernel to froyo to 2.2. In order to be able to downgrade back to 2.1 I need to use a "fixed" sbf. If I run the smgver.exe utility on the sbf file and it says "no version found" than this is a safe sbf to flash (can still downgrade).
2. Before I flash this new kernel I need to (should) do a full nandroid backup of my current rom so I can restore it if things go wrong. I might need to install SuperOneClickFor2.x to do the backup and future recoveries.
3. Once I flash one of these "fixed" sbf I can then do the "update.zip" process to flash CM7 onto my defy. I will need to do a factory reset and wipe the data/cache partitions. This will cause me to lose my contacts/calendar/etc AND my installed applications (and their data, so I need to back them up using something like TitaniumBackup).
4. Once I've got CM7 (with froyo kernel) I can flash one of the CM9 builds for the defy green lens that is built specifically for the froyo kernel
I've searched and read as much as I can, I feel like I "got it" but I just wanted a little confirmation before I start hacking this phone apart =)
Thanks for any help you can give me =)

Here is the explanation from all that I know:
1. I need to flash my kernel to froyo to 2.2. In order to be able to downgrade back to 2.1 I need to use a "fixed" sbf. If I run the smgver.exe utility on the sbf file and it says "no version found" than this is a safe sbf to flash (can still downgrade). Ya, that is true. But after flashing fixed SBF you also need Nandroid backup to be restored.(This is not your nandroid backup. Its the nandroid backup supplied with the fixed sbf)
2. Before I flash this new kernel I need to (should) do a full nandroid backup of my current rom so I can restore it if things go wrong. I might need to install SuperOneClickFor2.x to do the backup and future recoveries.
Yes Nandroid backup is always recommended. Superoneclick is a software needed to root your phone. That answers the rest.
3. Once I flash one of these "fixed" sbf I can then do the "update.zip" process to flash CM7 onto my defy. I will need to do a factory reset and wipe the data/cache partitions. This will cause me to lose my contacts/calendar/etc AND my installed applications (and their data, so I need to back them up using something like TitaniumBackup).
Yes, however its not update.zip but its <ROM NAME>.zip Your contacts,calender can be backed up in your google account and if you use gapps(google apps. Needs to be installed separately by install .zip in CM) in your CM those will come again. Your installed apps and data yes can be restored from TB. You can backup SMS using SMS backup+
4. Once I've got CM7 (with froyo kernel) I can flash one of the CM9 builds for the defy green lens that is built specifically for the froyo kernel
Yes either that or you can even directly flash CM9 for Froyo kernel.
Hope that helps...

Rooted, SndInit... What now?

Well, not exactly what, but how... This is my first locked device and have read the beginners guide for 2 months now but still a bit confused...
My device runs Froyo and already did a backup... I plan to install CM9... Does my backup work? Should I install GB sbf and go from there?
Sent from my MB525 using Tapatalk 2

dbarrera said:
Well, not exactly what, but how... This is my first locked device and have read the beginners guide for 2 months now but still a bit confused...
My device runs Froyo and already did a backup... I plan to install CM9... Does my backup work? Should I install GB sbf and go from there?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
You did a NAND backup?
You could test your backup by doing a Wipe data , boot into stock to verify phone is wiped, then reboot into recovery and restore your NAND backup. That will give you some sense of security.
Then wipe data again and install the ROM of your choice.
DONT INSTALL A GB SBF on a MB525 - you will never be able to go back to Stock Froyo! .... Of course you already knew this if you read the beginners guide!!!

_ossie_ said:
You did a NAND backup?
You could test your backup by doing a Wipe data , boot into stock to verify phone is wiped, then reboot into recovery and restore your NAND backup. That will give you some sense of security.
Then wipe data again and install the ROM of your choice.
DONT INSTALL A GB SBF on a MB525 - you will never be able to go back to Stock Froyo! .... Of course you already knew this if you read the beginners guide!!!
Click to expand...
Click to collapse
Yes, a NAND backup with CWM... And the data backup is not what worries me, but the system partition backup...
LOL, yes I got that last part... But as I'm using my device overseas from where I bought it, kinda not that worried about it...
Sent from my MB525 using Tapatalk 2

dbarrera said:
Yes, a NAND backup with CWM... And the data backup is not what worries me, but the system partition backup...
LOL, yes I got that last part... But as I'm using my device overseas from where I bought it, kinda not that worried about it...
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
OK Do you have a stock SBF file for your ROM?
If so, flash that to prove you can return to stock if you like.
Then re-root, reinstall CWM, reinstall your backup to prove you can do that.
Then wipe, install CM9, and play with it.
If you don't like it, recover your NAND backup.
If you don't have a current stock SBF for your ROM, then try to obtain a "fixed" SBF which you can use to restore your system in case you ever screw it up. Then the process would be to re-root, reinstall CWM and recover your original NAND backup.

_ossie_ said:
OK Do you have a stock SBF file for your ROM?
If so, flash that to prove you can return to stock if you like.
Then re-root, reinstall CWM, reinstall your backup to prove you can do that.
Then wipe, install CM9, and play with it.
If you don't like it, recover your NAND backup.
If you don't have a current stock SBF for your ROM, then try to obtain a "fixed" SBF which you can use to restore your system in case you ever screw it up. Then the process would be to re-root, reinstall CWM and recover your original NAND backup.
Click to expand...
Click to collapse
I don't have the stock sbf for the ROM that came loaded, and the list for official sbf files doesn't have it...
Where can I obtain a fixed sbf? I read that the process to install a fixed sbf is a bit different but its confusing how it is written in the guide...
Sent from my MB525 using Tapatalk 2

dbarrera said:
I don't have the stock sbf for the ROM that came loaded, and the list for official sbf files doesn't have it...
Where can I obtain a fixed sbf? I read that the process to install a fixed sbf is a bit different but its confusing how it is written in the guide...
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
No the process is identical. Flash with RSD Lite.
But before you flash any SBF, you need to know which version of Bootloader you are on. You canot flash a full SBF with a lower Bootloader version. But you can flash any fixed SBF - you may need a matching NAND backup for the SBF you flash.
As you are not interested in returning your phone to stock for warranty purposes, you probably won't need to flash ANY SBF for the time being, unless you get stuck.
So you can jump in and flash CM9 or whatever ROM.

_ossie_ said:
No the process is identical. Flash with RSD Lite.
But before you flash any SBF, you need to know which version of Bootloader you are on. You canot flash a full SBF with a lower Bootloader version. But you can flash any fixed SBF - you may need a matching NAND backup for the SBF you flash.
As you are not interested in returning your phone to stock for warranty purposes, you probably won't need to flash ANY SBF for the time being, unless you get stuck.
So you can jump in and flash CM9 or whatever ROM.
Click to expand...
Click to collapse
There, that's the thing that confuses me "a matching nand backup"... Can you elaborate on that?
Sent from my MB525 using Tapatalk 2

dbarrera said:
There, that's the thing that confuses me "a matching nand backup"... Can you elaborate on that?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
I'm no expert but here goes:
A Nandroid backup is a backup of EVERYTHING.
Similarly, flashing a full SBF overwrites everything (well, almost!)
The full SBF contains a full self-consistent set of CG files.
A fixed SBF is missing some CG files (CG31 and CG39 deliberately omitted to circumvent version checking) so it allows for example "downgrading".
When flashing a full SBF you'll have no problems because you have a consistent system. No Nandroid restore is required, unless you want to get some data back. You can restore a backup if you want to.
However if you flash a "fixed" SBF you MAY need to also restore a Nandroid backup to restore the CG31 and CG39 bits that match the rest of the SBF (assuming you have changed versions). This Nandroid must be compatible with the fixed SBF you flashed. If not, it won't brick your Defy, but maybe it won't boot. So you'll be back to flashing an SBF to fix it.
You don't always have to use a Nandroid backup with fixed SBFs - it really depends on what's on your system and where you are trying to go.
Since you know your base SBF - you won't need any fixed SBFs or "matching backups" (aka custom Nandroids) unless you try to downgrade your system for some reason - just have a factory SBFon hand in case you ever need to go back to stock.

So, for example, if I install CM and want to go back to Froyo, I install a Froyo fixed sbf and use my backup to restore /system ?
Sent from my MB525 using Tapatalk 2

dbarrera said:
So, for example, if I install CM and want to go back to Froyo, I install a Froyo fixed sbf and use my backup to restore /system ?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
You won't need to restore system. If you flash a Froyo fixed SBF you'll have a Froyo system!
If you restore a nandroid backup you'll get the exact same system you backed up. (Froyo or whatever).
You can also selectively restore (system, data, boot, recovery, logo ... ) from your nandroid backup but this might yield unexpected results.
If you install CyanogenMod, you can just restore your (Froyo) nandroid backup from recovery and you'll be back to Froyo - no need to flash an SBF unless something screws up.

Then what's the deal with the eFuse? Installing CM9 doesn't make my device going up in CG version, does it?
Sent from my MB525 using Tapatalk 2

dbarrera said:
Then what's the deal with the eFuse? Installing CM9 doesn't make my device going up in CG version, does it?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Nope. Only flashing a full SBF with a later CG version.

That gives me some confidence to take the plunge... Here we go...
Sent from my MB525 using Tapatalk 2

So I went, I saw and was conquered... Sorta...
Installed CM9, played with it for a while and now the screen (digitizer) doesn't recognize my input... What I did? In CM9 I elevated the points of I don't remember what (it has to do with the number of simoultaneous finger pressing being recognized) from default (2) to 4... But I went back to default and screen stopped responding... Thought it was SW issue, restored to my Froyo backup; no luck, still unresponsive... So the "bug" went from SW to HW issue... What went wrong?
Planning on flashing Froyo sbf and for my version, there are a whole lot of options... Whats all the fuss about CEE version? The original OS that was loaded didn't have any brand from any carrier, should I go for the ones that say Retail in the SBF list? Must I go with a fixed version?
Thanks in advance to anyone who answers any of my questions...

[Q] Can't load after downgrade to 7.2 Jordan

Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?

llavsor said:
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
Click to expand...
Click to collapse
Try to wipe all from stock recovery ----> Power+Vol dwn

Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that

llavsor said:
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
Click to expand...
Click to collapse
That's good sorry forget to say you need to hold VOL dwn& Vol Up at the same time then wipe all...
Good luck

Exactly the same problem here, cannot downgrade to CM7.
Any good news?

Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium

So the recovery won't work and will have to start with SBF. Will wait until I have the computer environment to do so.
Thanks!

Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
farsight73 said:
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone

llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Wipe all from stock recovery that's you needed to do btw before installing cm7.... Sbf is not needed.
Go to stock recovery and wipe all your ROM should boot...
Let's Go ^_^

llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.

skeevy420 said:
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
Click to expand...
Click to collapse
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?

Since I have no luck restoring stock rom I now have the following plan.
Install ClockWorkMod recovery with ADB.
Using recovery to do a factory reset and clear cache.
Flash a CM10 ROM (or any rom that will successfully boot up my phone).
From that start over to downgrade to CM9 to find a stable ROM.
The question I have now is if I will be able to use ADB with the USB connection mode I get from the bootloader (volume up+pwr button)? Or does ADB actually require that I can boot my phone and go into some other USB mode such as UMS or MTP.
Second question. Playing with restoring stock ROM i run out of battery and now my defy wont charge (only see a big question mark when loading). Seems like I get no power when USB is connected so is there a way for me to charge the battery or do I need to find another happy camper in town with a working defy that can power up my battery?

llavsor said:
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Click to expand...
Click to collapse
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium

farsight73 said:
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Thanks for very informative reply. I have a Defy 525 with red lens.

It's working.
I found a friend blessed with a defy and used that to charge the battery, tried to charge it over night with USB but it didn't work.
I then followed the steps from the last post and managed to flash a stock rom and then from there I rooted the phone with SuperOneClick, installed 2ndInit with ADB (guess you could use an apk installer from the phone as well ). I booted into recovery and flashed 7.2.0 Jordan from CM and now I am where I started a few weeks back.
Thank you all for your help.

That was the low battery problem.......
Since i had this i allways look for a full battery
If you think your defy is dead , a look for a empty battery won't be mad
Could anybody took a reminder info into beginners guide
MB525 red lense

TWRP Recovery has killed my defy

Hello guys, unfortunately my defy + with CM 10.1 does not work since I installed TWRP Recovery 2.6.3.0, I also lost the ClockworkMod recovery, and so I can not restore my copy CM 10.1, the phone is not charging (it is now only 25 %) ask for help.

If your phone don't boot
Charge battery with external charger
Flash .sbf firmware
Wipe data in stock recovery....
Reboot
Root
Install recovery
Restore nandroid
Be happy again
If it's boot
Copy system/bootmenu folder from
extracted nightly .zip file (last you've uesed and paste it on the rigth place using adb or rootexplorer
Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom

thanks Bone for the answer, what is the right place to copy system / bootmenu?
I could try with the TWRP Recovery file manager

If you're have working twrp you can flash cwm recovery.zip or flash rom which contains cwm recovery
Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom

thanks bone, I flashed CM 11 with TWRP recovery and everything went well, I'll try this rom and then after I will do a restore of the CM10

you can not completely kill our defy as our bootloader is locked...

iAjayIND said:
you can not completely kill our defy as our bootloader is locked...
Click to expand...
Click to collapse
It is hard to kill but it's possible....
Throw in from 10m to asphalt ground,,
Over roll it with an airplain
Pull usb cable during sbf flash in the moment when rsd flashes the bootloader partition
Cheers
Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom

mb 525 not powering after flashing.. i am only getting white light while connecting usb cable..please help any solution