Database Users

[RECOVERY] ClockworkMod Recovery [v6.0.4.6]

Version 6.0.4.6 - Stable
Bugs (Report):
No offmode charging.
Sideloading does not work with large files.
CMD side (adb) reboot is not working.
Installation:
Reboot to recovery.
Download the flashable zip below & flash it on top of your current recovery.
If you don't have custom recovery installed before, refer to 5.5.0.4 instructions before updating to 6.0.4.6.
Downloads:
Sourceforge
Version 5.5.0.4 - Stable
Bugs (Report):
No capacitive key support on Synaptics, due to v5.5.0.4 not having virtual keys implemented.
Installation:
Root your phone.
Download the recovery.img down below.
Save it to wherever you want.
Make sure the image name is recovery.img, rename if needed.
Download any root file manager, which can mount and show hidden folders.
Mount /.cust_backup as rw.
Copy and replace recovery.img from SD card to /.cust_backup/image/recovery.img
Usage:
Make sure you have disabled fast boot (on official Gingerbread). Go to Settings->Applications->Fastboot and disable it.
Start the phone in recovery mode [Volume Up] + [Power]. Hold the keys down until you can see boot logo.
To move up, press [Volume Up].
To move down, press [Volume Down].
To select, press [Power].
Downloads:
MediaFire
Credits:
TomGiordano at GitHub. Thanks for helping me fix rmt_storage.
dzo at XDA. Thanks for giving instructions.
Cyanogenmod. Thanks for the original ClockworkMod Recovery.

Nice going there! You used 2.35 kernel for this?
Also touchscreen not working anyway in recovery so that's not really a problem.
You are able to create/restore backups? Tried flashing any custom rom?
Also have a look at /tmp/recovery.log

ret4rt said:
Nice going there! You used 2.35 kernel for this?
Also touchscreen not working anyway in recovery so that's not really a problem.
You are able to create/restore backups? Tried flashing any custom rom?
Also have a look at /tmp/recovery.log
Click to expand...
Click to collapse
Yeah, I extracted it from boot.img. I saw stockwell had this working, maybe he had a custom recovery kernel for that. The rebooting issue is making thing hard, I almost backed it up, but it rebooted, so that's the main problem. If I get that fixed, I'll try flashing/backup.
Also, in 2.2, I was able to just start the phone with volume down + power, to get to recovery, but in 2.3, this doesn't work for me. I can only get there when I use "adb reboot recovery".
-EDIT-
Got it working, thanks genti7. It starts with vol up + power.

Before my phone bricked i got that problem too with 2.3 stock i cant enter on recovery with key combo

Blefish said:
Yeah, I extracted it from boot.img. I saw stockwell had this working, maybe he had a custom recovery kernel for that. The rebooting issue is making thing hard, I almost backed it up, but it rebooted, so that's the main problem. If I get that fixed, I'll try flashing/backup.
Also, in 2.2, I was able to just start the phone with volume down + power, to get to recovery, but in 2.3, this doesn't work for me. I can only get there when I use "adb reboot recovery".
Click to expand...
Click to collapse
its volume up + power not volume down + power. Try again.

Done any progress?

I don't have time today, will continue tomorrow. I realized that the /boot partition is wrong, can someone help me with this? Maybe the data one is wrong too, the logs say something about that. I'll post correct details tomorrow.
Sent from my U8800

The reboot is probably because you aren't running the rmt_storage server. The modem needs this to run and so reboots the phone without it. The HW recovery mounts /system to run it which is a stupid idea because /system may not always be there. rmt_server needs some shared libs so you will have to copy them to the recovery image too.

Attached is a recovery that I made, it's v4 but should work. I just modified the hw recovery so it needs a working /system. Obviously there's nothing to flash yet (and you won't be able to flash the old ROMs because amss has changed). I don't intend to support this but feel free to try it out.

dzo said:
The reboot is probably because you aren't running the rmt_storage server. The modem needs this to run and so reboots the phone without it. The HW recovery mounts /system to run it which is a stupid idea because /system may not always be there. rmt_server needs some shared libs so you will have to copy them to the recovery image too.
Click to expand...
Click to collapse
Thanks. Will do today.
Sent from my U8800

dzo said:
Attached is a recovery that I made, it's v4 but should work. I just modified the hw recovery so it needs a working /system. Obviously there's nothing to flash yet (and you won't be able to flash the old ROMs because amss has changed). I don't intend to support this but feel free to try it out.
Click to expand...
Click to collapse
Dzo did you upgrade AMSS to 2.3.5 beta or did you stay on B138SP04?

boss_y said:
Dzo did you upgrade AMSS to 2.3.5 beta or did you stay on B138SP04?
Click to expand...
Click to collapse
You must upgrade amss for the new kernel to work, it also has a new bootloader. Attached is a boot.img that will give you root access with adb in the gb beta rom.

Hold on... maybe we have clockwork
QT @tomgiordano: Sorry, I didn't get notifications for either of your tweets. http://205.185.123.36/u8800-35-recovery.img
Credits to tomgiordano
I'm not home for testing..
Sent from my IDEOS X5

well, about the CWM recovery,you can try the recovery Genokolar has released for the u8800+(or pro), it can work fine. I have tried it, and i have flashed a zip successfully!
PS: i am using u8800 (not u8800+), the official 2.3.5(u8800) has the same partition as u8800+.

dzo said:
You must upgrade amss for the new kernel to work, it also has a new bootloader. Attached is a boot.img that will give you root access with adb in the gb beta rom.
Click to expand...
Click to collapse
did not root mine

demolition23 said:
Hold on... maybe we have clockwork
QT @tomgiordano: Sorry, I didn't get notifications for either of your tweets. http://205.185.123.36/u8800-35-recovery.img
Credits to tomgiordano
I'm not home for testing..
Sent from my IDEOS X5
Click to expand...
Click to collapse
This is working good...just tried flashing tweak zip installed with out problems.....

krish_nank said:
This is working good...just tried flashing tweak zip installed with out problems.....
Click to expand...
Click to collapse
Good news!
Sent from my IDEOS X5

krish_nank said:
This is working good...just tried flashing tweak zip installed with out problems.....
Click to expand...
Click to collapse
can you try flash a rom ?

Darksage07 said:
can you try flash a rom ?
Click to expand...
Click to collapse
In theory,yes but current ROMs must be modified to support this recovery.so no flashing ROM for now...
This maybe work is an backup ROM..I think... :-\
Sent from my IDEOS X5

demolition23 said:
In theory,yes but current ROMs must be modified to support this recovery.so no flashing ROM for now...
This maybe work is an backup ROM..I think... :-\
Sent from my IDEOS X5
Click to expand...
Click to collapse
hmm maybe not .krish_nank can you send me the zip that you flashed ? so i can check one thing

[Q] [q] motorola defy plus 2.3.6

is there any custom ROM stable and 100% working, without any issues and please mention apps,steps,cautions step wise so that others could follow, read a lot of posts but all left me with doubts in the end, am fairly new to android so forgive me if this post is not worth. want to run stock sbf with custom rom possible i guess, ( installed 2ndinit for defy and my cam stopped showing preview posted as my first question. although uninstalled it and cam working now please help devz... i hope u will for sure. thx in advance

http://forum.xda-developers.com/showthread.php?t=1140839
works on my 2.3. 6 defy+

I am currently using the latest CM7.2-Nightly for Defy+ with the camera and battery fix attached in that post. It is very, very stable and with the fix, the battery charges up to 100%.
Installation:
!!!Read all steps before you do them!!!
1. Copy the three files linked above and the CM7-Google-Apps to your SD-Card.
2. Root your defy. I used this method.
3. Install 2nd-init recovery:
3.1 Download the app SndInitDefy from here
3.2 Install and start the app. Press on "Install 2nd-init Recovery".
3.3 Choose "Latest Recovery"
3.4 Allow the superuser-request
4. If the LED is green now, you can reboot your Defy. Press Vol-Down when you see the blue LED
5. Now you should get into the bootmenu. You can navigate with the volume keys there. Choose "Recovery" and press the power button to select.
6. Now choose "Custom Recovery"
7. Choose "install zip from sdcard" and install the downloaded zips:
7.1 Install cm72-120127.0846-NIGHTLY-Defy+.zip
7.2 Install gapps-gb-20110828-signed.zip
7.3 Install the fixes (the two other zips)
8. Now you have to do a factory reset. After that all your apps and settings will be deleted. If you want to keep them, you must backup the apps/settings first. You could do that with the app TitaniumBackup.
9. Choose "wipe data/factory reset" to do this factory reset.
10. Reboot the defy now. If you stil see the boot animation after five minutes, reboot the defy (I think you must remove the battery and put them into the phone again).
Now you should have a defy with CyanogenMod 7!

possible, in posibble?
188 2.3.6 motorola defy+ their full SBF will not work the root of the superoneclickk 2.3.3 not possible

WARNING!!!
The below guide is useless! It instructs you to download 2ndinit 2.0 which DOES NOT BOOT on Defy+ I have thus far killed 2 phones using it!!! Only use 1.4.2 no later. Thanks! =)
Mister Ypsilon said:
I am currently using the latest CM7.2-Nightly for Defy+ with the camera and battery fix attached in that post. It is very, very stable and with the fix, the battery charges up to 100%.
Installation:
!!!Read all steps before you do them!!!
1. Copy the three files linked above and the CM7-Google-Apps to your SD-Card.
2. Root your defy. I used this method.
3. Install 2nd-init recovery:
3.1 Download the app SndInitDefy from here
3.2 Install and start the app. Press on "Install 2nd-init Recovery".
3.3 Choose "Latest Recovery"
3.4 Allow the superuser-request
4. If the LED is green now, you can reboot your Defy. Press Vol-Down when you see the blue LED
5. Now you should get into the bootmenu. You can navigate with the volume keys there. Choose "Recovery" and press the power button to select.
6. Now choose "Custom Recovery"
7. Choose "install zip from sdcard" and install the downloaded zips:
7.1 Install cm72-120127.0846-NIGHTLY-Defy+.zip
7.2 Install gapps-gb-20110828-signed.zip
7.3 Install the fixes (the two other zips)
8. Now you have to do a factory reset. After that all your apps and settings will be deleted. If you want to keep them, you must backup the apps/settings first. You could do that with the app TitaniumBackup.
9. Choose "wipe data/factory reset" to do this factory reset.
10. Reboot the defy now. If you stil see the boot animation after five minutes, reboot the defy (I think you must remove the battery and put them into the phone again).
Now you should have a defy with CyanogenMod 7!
Click to expand...
Click to collapse

fr0dzy said:
WARNING!!!
The below guide is useless! It instructs you to download 2ndinit 2.0 which DOES NOT BOOT on Defy+ I have thus far killed 2 phones using it!!! Only use 1.4.2 no later. Thanks! =)
Click to expand...
Click to collapse
dude u have done something very wrong.i have installed the recovery like 5-6 times over and over and it worked on every occasion.even after flashing full SBF twice on my defy+.and it was 2nd init 2.0 with a 1.0. 7 bootmenu

fr0dzy said:
WARNING!!!
The below guide is useless! It instructs you to download 2ndinit 2.0 which DOES NOT BOOT on Defy+ I have thus far killed 2 phones using it!!! Only use 1.4.2 no later. Thanks! =)
Click to expand...
Click to collapse
That's strange...
For me it works well, i installed CWM sucessfully on both 2.3.4 and 2.3.6 devices. I was using the original firmware (from factory) for the 2.3.4 device and at the second device i flashed a 2.3.6 DFP-139 sbf form droid-developers.org. After installing the latest recovery and removing the "2nd-init Defy" app, I rebooted the phones and everything worked fine.
When you start the phone, do you see the blue led then? If not, you don't have installed 2nd-init correctly. If yes, try to 'wipe data/factory reset' the phone (you should have a backup, this erases all your user data which is not stored on the sd card and all your apps). If the phone is still not booting, you/the 2nd-init installer have/has made a wrong change to the system partition.
Then you should try to flash a new 2.3.4 SBF (look here and also here) and try it one more time.

Mister Ypsilon said:
I am currently using the latest CM7.2-Nightly for Defy+ with the camera and battery fix attached in that post. It is very, very stable and with the fix, the battery charges up to 100%.
Installation:
!!!Read all steps before you do them!!!
1. Copy the three files linked above and the CM7-Google-Apps to your SD-Card.
2. Root your defy. I used this method.
3. Install 2nd-init recovery:
3.1 Download the app SndInitDefy from here
3.2 Install and start the app. Press on "Install 2nd-init Recovery".
3.3 Choose "Latest Recovery"
3.4 Allow the superuser-request
4. If the LED is green now, you can reboot your Defy. Press Vol-Down when you see the blue LED
5. Now you should get into the bootmenu. You can navigate with the volume keys there. Choose "Recovery" and press the power button to select.
6. Now choose "Custom Recovery"
7. Choose "install zip from sdcard" and install the downloaded zips:
7.1 Install cm72-120127.0846-NIGHTLY-Defy+.zip
7.2 Install gapps-gb-20110828-signed.zip
7.3 Install the fixes (the two other zips)
8. Now you have to do a factory reset. After that all your apps and settings will be deleted. If you want to keep them, you must backup the apps/settings first. You could do that with the app TitaniumBackup.
9. Choose "wipe data/factory reset" to do this factory reset.
10. Reboot the defy now. If you stil see the boot animation after five minutes, reboot the defy (I think you must remove the battery and put them into the phone again).
Now you should have a defy with CyanogenMod 7!
Click to expand...
Click to collapse
thank you very much mister ypsilon...
your method works perfectly...camera works...though i cant find out how to check if its charging full, (it shows upto 100%, is that all i need ?)
i have some minor problems though:
1)sometimes when i go out of coverage area and come back, the phone doesn't regain the signal
2)there is no 720p recording...had that in the stock ROM...

i want to try 7.2 cm7 for defy+ but on dual boot, did any one tried ??? plz procedure guyz.

dual boot
veeranna said:
i want to try 7.2 cm7 for defy+ but on dual boot, did any one tried ??? plz procedure guyz.
Click to expand...
Click to collapse
afaik you absolutely have to dual boot a defy/defy+...because of the locked bootloader you cant remove the stock rom...
follow the above instructions carefully and you will have a cm7.2...then you can dual boot by selecting the preferred entry from the menu....

steadywarp said:
188 2.3.6 motorola defy+ their full SBF will not work the root of the superoneclickk 2.3.3 not possible
Click to expand...
Click to collapse
Bro even I have done this n times! In fact I had stock 2.3.4 which I upgraded to 2.3.6 by a full SBF flash and since then I have rooted using superoneclick and installed recovery many times and it works perfectly! The only issue however is that there are less frequent releases for 2.3.6 as compared to the Froyo kernel!

Mister Ypsilon said:
I am currently using the latest CM7.2-Nightly for Defy+ with the camera and battery fix attached in that post. It is very, very stable and with the fix, the battery charges up to 100%.
Installation:
!!!Read all steps before you do them!!!
1. Copy the three files linked above and the CM7-Google-Apps to your SD-Card.
2. Root your defy. I used this method.
3. Install 2nd-init recovery:
3.1 Download the app SndInitDefy from here
3.2 Install and start the app. Press on "Install 2nd-init Recovery".
3.3 Choose "Latest Recovery"
3.4 Allow the superuser-request
4. If the LED is green now, you can reboot your Defy. Press Vol-Down when you see the blue LED
5. Now you should get into the bootmenu. You can navigate with the volume keys there. Choose "Recovery" and press the power button to select.
6. Now choose "Custom Recovery"
7. Choose "install zip from sdcard" and install the downloaded zips:
7.1 Install cm72-120127.0846-NIGHTLY-Defy+.zip
7.2 Install gapps-gb-20110828-signed.zip
7.3 Install the fixes (the two other zips)
8. Now you have to do a factory reset. After that all your apps and settings will be deleted. If you want to keep them, you must backup the apps/settings first. You could do that with the app TitaniumBackup.
9. Choose "wipe data/factory reset" to do this factory reset.
10. Reboot the defy now. If you stil see the boot animation after five minutes, reboot the defy (I think you must remove the battery and put them into the phone again).
Now you should have a defy with CyanogenMod 7!
Click to expand...
Click to collapse
Thanks for very useful and very clear and easy steps Now i have CM on defy plus
(i have clicked thanks too)

Try this. It worked for me
veeranna said:
i want to try 7.2 cm7 for defy+ but on dual boot, did any one tried ??? plz procedure guyz.
Click to expand...
Click to collapse
Search google for the following string. "MB526 custom rom".
It should be in the first few links by soulness

1. Ijust bought a defy +....it has version dfp_1321.....do I need to flash any other sbf before ics????? It is presently 2.3.6 stock at present.....rooting n all not a problem.....just wanted to know if any other specific sbf or nandroid backup would be necessary.......
2. In the thrrad fr dis sbf Walter said cm7 and miui are unavailable....wt happens if u flash them??????
Sent from my MB526 using Tapatalk
Sent from my MB526 using XDA

bharaththeunique said:
1. Ijust bought a defy +....it has version dfp_1321.....do I need to flash any other sbf before ics????? It is presently 2.3.6 stock at present.....rooting n all not a problem.....just wanted to know if any other specific sbf or nandroid backup would be necessary.......
2. In the thrrad fr dis sbf Walter said cm7 and miui are unavailable....wt happens if u flash them??????
Sent from my MB526 using Tapatalk
Sent from my MB526 using XDA
Click to expand...
Click to collapse
Hi,
Good to know new Defy+ are coming in India with latest updates! I too have the very same SBF in my phone. As you said rooting and all not a problem. No need to flash any specific SBF as such. A nandroid backup is recommended in case you want to come back to where you left before flashing! And if you want back warranty just flash the SBF with RSD lite(Walter's thread has the SBF and even I can give you the link if you want.).
For your second answer:
This SBF has BL6. So you cannot go back to any ROM or sbf which has a previous version. Thus, walter said about unability to flash MIUI or CM7. However, you can flash CM7.2 for Defy+ or CM9 for Defy+(By quarx). Just flash the CM. No need to flash any kernel. It worked fine for me. You can even try dual boot and that too works great.
Happy flashing!

thnx a tonne....I was wanting cm7 fr its completeness....n cm9 fr awesomeness.....thnx again....
Also....can u give a link to the best cm7.2 build fr us....?
Sent from my MB526 using XDA

pranks1989 said:
steadywarp said:
188 2.3.6 motorola defy+ their full SBF will not work the root of the superoneclickk 2.3.3 not possible
Click to expand...
Click to collapse
Bro even I have done this n times! In fact I had stock 2.3.4 which I upgraded to 2.3.6 by a full SBF flash and since then I have rooted using superoneclick and installed recovery many times and it works perfectly!
Click to expand...
Click to collapse
Bro, dont speak from ignorance, especially when it can lead to others ending up in a bad place. The latest versions of 2.3.6 eg 4.5.1-134-DFP-188 can not be rooted by any currently known exploit, so you have to be careful when choosing an sbf to flash. See here for which versions can and can't be rooted.
There's even a whole thread all of its own where people are trying to root the latest 2.3.6 releases, here.

ejstubbs said:
Bro, dont speak from ignorance, especially when it can lead to others ending up in a bad place. The latest versions of 2.3.6 eg 4.5.1-134-DFP-188 can not be rooted by any currently known exploit, so you have to be careful when choosing an sbf to flash. See here for which versions can and can't be rooted.
There's even a whole thread all of its own where people are trying to root the latest 2.3.6 releases, here.
Click to expand...
Click to collapse
Yep, I realised it later and saw the whole discussion about 188 version SBFs with BL7! Sorry, if that was offending!!
---------- Post added at 04:23 PM ---------- Previous post was at 04:21 PM ----------
bharaththeunique said:
thnx a tonne....I was wanting cm7 fr its completeness....n cm9 fr awesomeness.....thnx again....
Also....can u give a link to the best cm7.2 build fr us....?
Sent from my MB526 using XDA
Click to expand...
Click to collapse
http://quarx2k.ru/cm7-nightly-defy+/ That is CM7 nightlies for Defy+ by Quarx!!

Followed the steps listed by Mister Ypsilon, on to my new Defy+ which used to run Motorola Stock with Motoblur. So far looks good. I will post further regarding the battery.
The only glitch that I faced after installing the ROM is that it always froze at the Boot Animation. I had to pull the battery almost 5-6 times and then magically it started to work. Boots within 10 second from the Motorola Logo.
Not sure if the battery pulls were because of something that I did wrong.
Thank you Mister Ypsilon.
Andy

veeranna said:
i want to try 7.2 cm7 for defy+ but on dual boot, did any one tried ??? plz procedure guyz.
Click to expand...
Click to collapse
Search for Multuboot v0.8, its a flashable ziped file, through which you can dual boot, i have tried and it works perfect !! :laugh:
You will need 3 img files also ,so that your 2nd rom can be installed is sd card with atleast 900 MB of space ..
---------- Post added at 06:25 PM ---------- Previous post was at 06:22 PM ----------
rebeleagle said:
thank you very much mister ypsilon...
your method works perfectly...camera works...though i cant find out how to check if its charging full, (it shows upto 100%, is that all i need ?)
i have some minor problems though:
1)sometimes when i go out of coverage area and come back, the phone doesn't regain the signal
2)there is no 720p recording...had that in the stock ROM...
Click to expand...
Click to collapse
Use baseband switcher app to choose appropriate baseband according to your location, it may help in signal problem..

[Q] All ROMs are failing

Hi all!
Almost all ROMs out there are failing to work correctly or even boot on my Defy (red lens). Some do boot, some go to bootloop.
Here's the full story. Two days ago the latest CM10 nightly from Quarx went to bootloop, it was working just fine, but at some point the phone rebooted and didn't boot back up.
I've decided to try another ROM and installed WIUI v4 (JB) from CWM. I went to check device's internal memory and it appeared that I had 48 MB used and that that was all internal memory - the system hasn't even loaded total memory info.
I performed some search and found this thread with the similar issue: http://forum.xda-developers.com/showthread.php?t=1940503
It suggested flashing an SBF via RSD Lite. I did that using the SBF from that thread (2.2 CEE Froyo). I suppose that was my mistake since the thread referred to Defy with a green lens. However, I was finally able to boot the device. I decided to try another SBF. JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDN to be precise. Everything went just fine. I was able to root the device, install CWM using SndInitDefy 2.0, and install stable CM7 (the official one, update-cm-7.1.0-jordan-signed.zip) and Froyo kernel from WIUI.
Everything was working fine except for the camera. It was showing the following error:
"Camera error. Cannot connect to camera"
After that I though that maybe I've messed up with SBF versions. The phone is not sold in Ukraine officially and I didn't remember which SBF it used when it was shipped.
I then followed the guide from All-in-one beginners guide and installed that Chinese SBF with Version 5 CG (thus I presume I can't flash any full SBF now since this will cause a black screen and I will have to re-flash 97.21.51 SBF and do all that stuff all over). Again, I was able to root the phone and stuff. However, none of Quarx's nightlies are working, CM7.2 or 2nd-boot CM10 are simply bootlooping, WIUI v4 can't connect to any of Google's services (they constantly FC), and none of the ROMs can connect to the camera.
Currently I'm using the following:
official CM7.1.0
Android 2.3.7
kernel [email protected] #1
Build number Gingerbread GWK74
I'm okay with staying on CM7.1, but I require the camera to work. So, the question is, what should be done in order to make the camera work?
Maybe, I should change some lib files, if so, could you please provide with the link to the correct ones? I've already tried some camera fix SBF's but they didn't seem to work. If there is any additional information required, please let me know.
Any help will be really appreciated!
Thank you in advance.

Maybe you could get rid of the sbf problem(camera issue caused by wrong flashing) by flashing a defyplus sbf with group code 6. Then your camera should work.
Sent from my MB526 using xda premium

Thanks, thekguy! Will try this later today.

Nope, that didn't work, unfortunately. Flashed 4.5.1-134_DFP-125, but the camera is still failing, as well as the latest CM10. Any suggestions are welcome.

Hmm, latest cm10 2ndboot right? That's a very bad sign, since that rom indeed works with both the camera modules, and its really curious that it's not working.
Flash back to any defy bl6 sbf from this list(don't flash defy+ sbf since that approach isn't working):
http://forum.xda-developers.com/showthread.php?t=966537
Wipe data, and use the defy ultimate wiper script(it's there in themes and apps section, use ext4 version if you're on cm10 or ext3 for any other rom).
Now flash cm10 2ndboot build, and try using the camera.
Normally that should work, even if you have a green lens module, but if not so then it could be add a result of a hardware failure
Sent from my MB526 using xda premium

Yeah, I've also tried CM7 for Defy+, but that didn't work either. And I guess I pushed my device few steps closer to the brick yesterday. I flashed one of Chinese SBFs (JRDNEM_U3_3.4.3-36-1_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTINT_P011_A013_HWp3_Service1FF). It's BL7 SBF and it's known for its outstanding unbricking abilities. Didn't work for me. However, the bootloader is still accessible and I will keep playing with the phone today.
I'm getting tired of all this.

Didn't work? Camera or unable to boot?
Remember, you must wipe data from stock recovery before you can boot into the stock rom
Once you are running on the stock rom, check if the camera works. If not then follow my other post about getting to cm10 2ndboot. It may hang once on boot but it will boot after that. If still the camera is not working then I'm afraid it's beyond help
Sent from my MB526 using xda premium

thekguy said:
Didn't work? Camera or unable to boot?
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Didn't boot at all, just a blank black screen. I can't enter stock recovery and the bootloader is not visible. However, if I boot up with power+vol+ and connect the phone to the desktop, RSD Lite detects the phone and I can flash an SBF. But my guess is that this would be useless since the last SBF I flashed was BL7.
Well, I'm at work right now, thus I can't try anything out right now. Theoretically, I should be able to flash any SBF with BL7, and root it using this guide http://forum.xda-developers.com/showthread.php?t=1542956

Then, flash both sbfs from that guide, and it should work.
You shouldn't get any blank screen, simply because you've got the highest possible group code, and you cannot have a wrong kernel just after flashing the sbf. It must work
Sent from my MB526 using xda premium

Thanks. Will definitely give it a try once I get home.

OK, I've managed to install 4.5.1-134 DFP-231 Retail.en.EU CEE, root it, and flashed CM10 2nd-boot nightly. However, I'm still unable to boot the phone. It shows CM10 logo spinning for 10-20 seconds and then reboots. I assume that this is the only ROM which can make the camera work. Am I right? If yes, what should I check or do in order to fix the boot looping? If I can use some other ROM, could you please let me know which one exactly and what can be done in order to fix the camera?
Thank you!

Just flashed CM10 and checked the log, there's the following message:
set_perm: chown of /system/xbin/tcpdump to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/tcpdump to 6755 failed: No such file or directory
Click to expand...
Click to collapse
Could this be a source of the problem?

Another update. I've installed WIUI v4 for GB kernel and looks like it requires less internal memory/RAM to run so I'm able to boot the phone completely. And it's showing that I have 0.00 MB of internal storage in total and 58 MB used. I guess internal memory issue is somehow related to the bootloop.

Before flashing cm10, use both the ultimate wiper scripts(ext4 and ext3 version)
After flashing cm10, go back to boot menu and select tools, file system tools and format to ext4. It should boot now
Sent from my MB526 using xda premium

Thanks for the clue, but I'm afraid that didn't work. Since I had some time and have no data to lose, I wiped the phone from stock recovery, flashed both standard 4.5.1-134 DFP-231 and rooted 4.5.1-134 DFP-231, wiped everything using both ext3 and ext4 Ultimate scripts, flashed Quarx's 2nd boot CM10, formatted data and cache to ext4 using File System tools. CM10 still bootloops, but at least now I have internal memory info displayed correctly in WIUI v4 (JB). But since it's not a 2nd boot ROM, the camera isn't working.
In fact, I've tried some other 2nd boot scripts (NEGAN-6DIC and Codenameandroid 3.6.6), but they are bootlooping as well.
Maybe there are some other 2nd boot ROMs I should check? Or maybe if I get a nandroid backup of a working system I could restore it on my phone?

Try converting to ext4 and flash after that. It is really curious why it bootloops. You must get cm10 to boot, so that the camera works. Look here for downloading a stock kernel that should hopefully fix the boot loops.
http://forum.xda-developers.com/showthread.php?t=1909242
Scroll down for the post which talks about having a compatible stock kernel which should allow 2ndboot to work(it's titled for bl7 users).
Flash this kernel after stock sbf flash, then try installing cm10.
Let's see how this goes
Sent from my MB526 using xda premium

Still no joy. Neither formatting, nor following this guide http://forum.xda-developers.com/showthread.php?t=1909242 worked. Is there a way to see boot log from a desktop? I have both Debian and Win7 on my desktop.
Thanks.

There is a way to debug using uart, but I have no experience with it. So, sbf flash+ compatible stock kernel failed? Please describe the boot loop. Does it reach the cyanogenmod logo? Or stuck at red Motorola logo? I am at my wits end at this one. All my semi bricks and other problems I could fix by the methods outlined in my previous posts, but they don't seem to work in your case. You flash full sbfs right? And are you able to boot the stock Rom?
Sent from my MB526 using xda premium

Here's how it loops:
- the phone starts
- shows red Moto logo
- blue led
- red led
- blank black screen
- HW buttons blink once
- CM10 spins for approx 5-10 seconds
- the phone restarts and all the steps repeat
Yes, I'm able to flash full SBF (BL7 ones). I'm able to boot into a stock ROM, I can flash modded SBF for BL7 (the rooted one). I've tried flashing CM10 SBF, but the phone booted into a bootloader and showed an error, with set of numbers. Looks like because of the kernel (my guess is that SBF contains non-2nd boot version of CM10).
If I install WIUI v4 right after I flash rooted SBF I have no issues with the internal storage.
If I install 2nd boot CM10 (Kayant's, Quarx's) I get a boot loop (Ultimate Wipe doesn't help)
If I install WIUI v4 after CM10 (without re-flashing SBF's), I get 0.00 internal storage, but wiping data/cache from stock recovery solves the issue.
Unfortunately, wiping data/cache from stock recovery doesn't do the trick for CM10 2nd boot builds.
One more thing, after I flash CM10 and try to wipe data/cache from stock recovery for the first time, it shows recover log errors. There are errors when entering stock recovery after that.

Might be a false trail, but what about wiping from custom recovery? Dalvik cache wipe?
This indicates that the kernel had loaded before some other problem caused the phone to enter into boot loop. What about the camera in the stock build? Same error as before?:banghead:
The cm10 sbf probably had a lower group code(bl6 perhaps) hence that approach won't work, and even discarding that it will yield the same results as before.
Also, in stock, check if the kernel version changes after you flash the compatible stock kernel from the thread I had mentioned earlier. This is important because otherwise there is no chance for cm10 to boot.
Sent from my MB526 using xda premium

[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

[Q] uninstalling slimkat (cm11)

Hi guys, need some help here. I'm sure this has been asked before but i just couldn't find any
Installed slimkat 20140406-0134 rom (cm11) last night and it's basically working. But I'm still not feeling comfortable using it as there's still bugs around. So thought of going back to cm7.2 for now. But for the life of me couldn't figure out how to get to the tool section so I can re-partition it back to ext3!!!
All I could get in to is twrp recovery and that's it. how do I even get into the bootmenu section where I can choose recovery, cpu settings, tools, etc? There's no red Moto logo with blue LED at boot up anymore
Is there any uninstall instruction somewhere, or perhaps someone should write one?

44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........

jh20 said:
44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........
Click to expand...
Click to collapse
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.

Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk

aperture said:
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.
Click to expand...
Click to collapse
thanks. i'll remember that next time. don't know why i didn't think of that. panic striken maybe
hotdog125 said:
Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
that's exactly what i did but didn't work. aromawiper seems to have worked properly but twrp 2.6.3.0 keep saying "no os installed" after i installed the gb rom and tried to reboot. tried maniac's cm7.2 and an older wiui gingerbread rom. i thought it might be a hickup and rebooted anyway and that was it.
don't know what went wrong there. has anyone actually tried this method before and got it to work?
edit: imho twrp is not worth it. it rebooted 8-10 times on me after installing cm11 and tried to get back into recovery to flash gapps. also other problems like blank backup files and my failures to install rom problem. they should have stuck to cwm until the problems are fixed.
edit 2: and i think removing bootmenu is not a good idea. more steps to take if you want to go back to cm7.2.