Database Users

[SOLVED] Defy can't get back to JB

See Page 4 for details on how I solved it.
In short I upgraded to BL7
OP:
Edit 30/1/2013 22:26GMT:
The current rom I am on (The Froyo mentioned below) has the following 'About Phone')
Kernel: [email protected]
Baseband: EPU93_U_00.59.01
BPflex version: UCAJRDNEMARAB1B80AA03A.0R
APflex version: GAS_EMEA_USAJRDNFRYORTCEE_P016
Build number: JOREM_U3_3.4.2_179-2
Hey all,
I'm stuck with my Defy (MB525 Red Lens).
I recently flashed an SBF which I then realised had a messed up CG version (too low or high or whatever)... I went to the AIO Defy Beginners guide as I remember seeing something there about this, and this is what I found.
Black Screens when booting up: (!) Tried to install a version of Android with a lower CG Version than the one currently on the phone.
Weird behavior after installing a Fixed SBF: Install a matching Nandroid backup with your SBF, and remember to clear Cache/Dalvik Cache using Recovery.
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Method 1:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backup << File is Back, thanks Ichibanme again!>>
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot.
I used the first method.
I have completed these parts (So I'm now on Froyo - the second SBF), however I can't seem to upgrade to Jellybean anymore.
I tried following these instructions to install JB from FroYo again, but once I have it installed I just get a black screen with a red LED. It hangs there, then returns to the red M logo.
I've tried taking the battery out for 5 minutes, and leaving it on that screen, but no luck.
Currently I'm again at the FroYo ROM, which is working for me, but I want my Jellybean back
Can anyone help me please?​​

You has flashed GB kernel and cannot revert to Froyo. From now one you must use the fixed sbf and flash the nandroid backup. After that you can install CM10.

pgreed I tried installing this, but it didn't work (including the nandroid backup)
Current settings:
Edit 30/1/2013 22:26GMT:
The current rom I am on (The Froyo mentioned below) has the following 'About Phone')
Kernel: [email protected]
Baseband: EPU93_U_00.59.01
BPflex version: UCAJRDNEMARAB1B80AA03A.0R
APflex version: GAS_EMEA_USAJRDNFRYORTCEE_P016
Build number: JOREM_U3_3.4.2_179-2
Click to expand...
Click to collapse
Aim:
A functional (daily) Jelly Bean ROM!
Click to expand...
Click to collapse
First SBF I think I flashed: JRDNEM_U3_2.21.1_SIGNED_USAJRDNEMARAB1B8TMGB028.0R_USAJORDANTMGB_P030_A012_M001_HWp3_Service1FF.sbf.gz
Please help, anyone!

pk92 said:
Edit 30/1/2013 22:26GMT:
The current rom I am on (The Froyo mentioned below) has the following 'About Phone')
Kernel: [email protected]
Baseband: EPU93_U_00.59.01
BPflex version: UCAJRDNEMARAB1B80AA03A.0R
APflex version: GAS_EMEA_USAJRDNFRYORTCEE_P016
Build number: JOREM_U3_3.4.2_179-2
Hey all,
I'm stuck with my Defy (MB525 Red Lens).
I recently flashed an SBF which I then realised had a messed up CG version (too low or high or whatever)... I went to the AIO Defy Beginners guide as I remember seeing something there about this, and this is what I found.
I used the first method.
I have completed these parts (So I'm now on Froyo - the second SBF), however I can't seem to upgrade to Jellybean anymore.
I tried following these instructions to install JB from FroYo again, but once I have it installed I just get a black screen with a red LED. It hangs there, then returns to the red M logo.
I've tried taking the battery out for 5 minutes, and leaving it on that screen, but no luck.
Currently I'm again at the FroYo ROM, which is working for me, but I want my Jellybean back
Can anyone help me please?
Click to expand...
Click to collapse
Under method 2, there is info on how to install CM7. Use it to flash CM10.

Vicsa said:
Under method 2, there is info on how to install CM7. Use it to flash CM10.
Click to expand...
Click to collapse
Thanks for the reply.
"8. Flash this Fixed SBF"
What Fixed SBF (for CM10) should I use in place of this step?
Will "cm10Quarx.31.12+BM.tweaks.fixed.sbf" from this thread work?

pk92 said:
Thanks for the reply.
"8. Flash this Fixed SBF"
What Fixed SBF (for CM10) should I use in place of this step?
Will "cm10Quarx.31.12+BM.tweaks.fixed.sbf" from this thread work?
Click to expand...
Click to collapse
you misunderstood me. Don't use method 2, but info under that method on how to install CM7.

Vicsa said:
you misunderstood me. Don't use method 2, but info under that method on how to install CM7.
Click to expand...
Click to collapse
Ahh, so you meant
Root your Defy (Using SuperOneClick 1.7 and not 1.9).
Install SystemRecovery from GoAPK. If you install 2nd init, you'll just get into a boot loop and have to start over.
Reboot to recovery. Do a factory wipe, then do the cache wipe.
Install CM7 .Zip and then gapps zip file. DO NOT wipe again, you'll just go back to 2.2.2 CEE (if you accidentally do this, you can pick up again from step 3).
profit!
Click to expand...
Click to collapse
Alright, I'll see how that goes Thank you very much
Edit: The SystemRecovery from GoAPK link says it's outdated :S http://forum.xda-developers.com/showthread.php?t=875233
Will try EasyRecovery instead http://forum.xda-developers.com/showthread.php?t=1787541

pk92 said:
Ahh, so you meant
Alright, I'll see how that goes Thank you very much
Edit: The SystemRecovery from GoAPK link says it's outdated :S http://forum.xda-developers.com/showthread.php?t=875233
Will try EasyRecovery instead http://forum.xda-developers.com/showthread.php?t=1787541
Click to expand...
Click to collapse
ah man you are fast
Do not wipe after flashing cm10 and gapps (just before), if you manage to come that far.I think that's the key.

Vicsa said:
ah man you are fast
Do not wipe after flashing cm10 and gapps (just before), if you manage to come that far.I think that's the key.
Click to expand...
Click to collapse
OK What I did (from the rom with above specs):
Install EasyRecovery (Android Recovery 3e)
Wipe Data/Factory Reset
Wipe Cache
Install CM10 31st December 2012 build (CM10-20121231-NIGHTLY-mb526(last-in-2012))
Installed Gapps (gapps-jb-20121212-signed)
Reboot
Now I've got a bootloop between Red Motorola logo and Red LED with black screen :/
Going to try again from method 1, but install EasyRecovery instead of going to the second ROM
To do list:
Download this SBF and Flash it
Root your Defy (Using SuperOneClick 1.7 and not 1.9)
Install EasyRecovery from GoAPK.
Reboot to recovery. Do a factory wipe, then do the cache wipe.
Install CM10+Gapps
Reboot
Click to expand...
Click to collapse

Don't forget also to wipe dalvik cache before you flash a custom ROM (CM10)!

Vicsa said:
Don't forget also to wipe dalvik cache before you flash a custom ROM (CM10)!
Click to expand...
Click to collapse
But... you can't wipe dalvik with EasyRecovery :/
Options are:
reboot system now
apply update from sdcard [this one allows installation of cm10 zip]
wipe data/factory reset
wipe cache partition
Not worked by the way :/ now have the ECLAIR motorola logo...

I'm pretty sure that I couldn't install cm10 before wiping dalvik cache, coming from the stock ROM. I'd try that outdated system recovery. They didn't changed that step, so I think it should work.

Vicsa said:
I'm pretty sure that I couldn't install cm10 before wiping dalvik cache, coming from the stock ROM. I'd try that outdated system recovery. They didn't changed that step, so I think it should work.
Click to expand...
Click to collapse
Alright, I'll give it a go tomorrow. For now I'm going to sleep =P Only got 2 hours sleep last night wrestling with this!
Thank you very much for your help!

You're welcome. Hope it'll work. Good night.

Vicsa said:
You're welcome. Hope it'll work. Good night.
Click to expand...
Click to collapse
No luck :/ it had the white motorola logo (from Eclair) still.. I'll try going that route from the FroYo

Re: [Q] Defy can't get back to JB
Did you try format data to ext4 from boot menu in file system tools, you have to do it after flashing cm10
Also, for good measure you can try using the system wiper zip
Sent from my MB526 using xda premium

thekguy said:
Did you try format data to ext4 from boot menu in file system tools, you have to do it after flashing cm10
Also, for good measure you can try using the system wiper zip
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I've tried the ext4 BEFORE flashing CM10... Damnit why didn't I try after =P haha.
I used a zip to wipe ext4 too... I'll give those a try, thanks

Try method 1 again, but use this newer version of 2nd init 2.0 instead of 1.4.3.
After that you could try this steps to install CM10 (copy/paste from FAQ):
For MB526 and PRE 2ndBoot Builds
1) Go to Custom Recovery.
2) Wipe data/factory reset, wipe cache and go to advanced ► Wipe dalvik.
3) Go to Install zip from sdcard ► Choose zip from sd card.
4) Flash gb Kernel (JUST FOR DEFY RED LENS USERS).
5) Flash CM10-20120924-NIGHTLY-mb526.zip.
6) Flash Gapps.
7) Flash Battery fix (only for red lens)
8) Wipe Cache and Dalvik again (recommended).
9) Restart.
Because you haven't suceed to install 2ndBoot release, try this one to see if it works.
You are a red lens user, so follow all the steps and see wat happens..

I've tried it with 2nd init v2.3, but I'll give 2.0 and those builds a go.
Thanks for helping. Really confusing me haha

Vicsa said:
Try method 1 again, but use this newer version of 2nd init 2.0 instead of 1.4.3.
After that you could try this steps to install CM10 (copy/paste from FAQ):
For MB526 and PRE 2ndBoot Builds
1) Go to Custom Recovery.
2) Wipe data/factory reset, wipe cache and go to advanced ► Wipe dalvik.
3) Go to Install zip from sdcard ► Choose zip from sd card.
4) Flash gb Kernel (JUST FOR DEFY RED LENS USERS).
5) Flash CM10-20120924-NIGHTLY-mb526.zip.
6) Flash Gapps.
7) Flash Battery fix (only for red lens)
8) Wipe Cache and Dalvik again (recommended).
9) Restart.
Because you haven't suceed to install 2ndBoot release, try this one to see if it works.
You are a red lens user, so follow all the steps and see wat happens..
Click to expand...
Click to collapse
OK, that's different.
Boot:
1) Red M logo
2) Blue LED
3) GREEN LED
4) Red M logo no LED
5) Bootloop
I think what I need is a CM10 nandroid to install with the CM10 zip :/

[Q] Last version of CM10.1 for defy (mb525)

Hello,
I own a defy mb525 with CM7.2.0. I am not so happy with this version (bad 3g access; battery life very short)
So I decided to install the CM10.1.
On the develloper page I saw that the status has been updated on the 26.03. But if I look for my model (mb525), I can find only a version dated on the 120904.
Is there a newer version for the mb525 or is it only for the mb520 and mb526 ?
Regards

http://forum.xda-developers.com/showpost.php?p=34616788&postcount=1
--> FAQ2
It should work for both. Same as latest builds of CM10.

thubi said:
http://forum.xda-developers.com/showpost.php?p=34616788&postcount=1
--> FAQ2
It should work for both. Same as latest builds of CM10.
Click to expand...
Click to collapse
Sorry I was meaning the 4.1.2 so it should be the 10.0

Cid156 said:
Hello,
I own a defy mb525 with CM7.2.0. I am not so happy with this version (bad 3g access; battery life very short)
So I decided to install the CM10.1.
On the develloper page I saw that the status has been updated on the 26.03. But if I look for my model (mb525), I can find only a version dated on the 120904.
Is there a newer version for the mb525 or is it only for the mb520 and mb526 ?
Regards
Click to expand...
Click to collapse
2ndboot builds: they are one build for both mb525 &5 26 .... so you can download the 26.03 nightly build and update on your MB525 :good:

Cid156 said:
Hello,
I own a defy mb525 with CM7.2.0. I am not so happy with this version (bad 3g access; battery life very short)
So I decided to install the CM10.1.
On the develloper page I saw that the status has been updated on the 26.03. But if I look for my model (mb525), I can find only a version dated on the 120904.
Is there a newer version for the mb525 or is it only for the mb520 and mb526 ?
Regards
Click to expand...
Click to collapse
Yes, there is CM10 from Quarx. Your device can be either mb525 or mb526 with red lens or green lens. CM10.1 from the same person also can.

hi
I have a similar question I have MotoDefy 525 running 2.3.7 I want to install ([ROM][JB+][4.3.1] MokeeOS 43.1 Defy/Defy(+) Official) http://forum.xda-developers.com/showthread.php?t=2453395
but it needs TWRP I tried installing on my 2.3.7 but it dosent install I looked around the forms I read that I have to up date my android version.
being a newbi im a little worried about bricking
A little help
can some one give the steps in Newbi language on how to update my phone to MokeeOS 43.1 please.:fingers-crossed:

Super_Moto said:
hi
I have a similar question I have MotoDefy 525 running 2.3.7 I want to install ([ROM][JB+][4.3.1] MokeeOS 43.1 Defy/Defy(+) Official) http://forum.xda-developers.com/showthread.php?t=2453395
but it needs TWRP I tried installing on my 2.3.7 but it dosent install I looked around the forms I read that I have to up date my android version.
being a newbi im a little worried about bricking
A little help
can some one give the steps in Newbi language on how to update my phone to MokeeOS 43.1 please.:fingers-crossed:
Click to expand...
Click to collapse
First of all, none of you guys ever read the stickies. It is packed with good info.
Our phone has a locked bootloader, it is almost impossible to brick.
Download latest CM10 and then install.

Ive come across a newbi problem im on the link of the latest cm10 (http://forum.xda-developers.com/showthread.php?t=1768702) and the file I try to flash wont install it gets aborted, I searched the forms for other cm10 and same issue file gets aborted.
If possible to be directed to the file I need to flash to cm10
not easy being newbi these days :crying:
Motorola 525 green lens running 2.3.7

What error do you get?
Sent from my MB526 using Tapatalk

hotdog125 said:
What error do you get?
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
the error shows when I try to flash the .zip file _Install zip from sdcard_choose zip from sdcard I pic the file and it doesn't install it says aborted show me the yellow triangle symbol I was assuming im flashing the wrong file.
before I do an install I wipe data/factory reset and wipe cache partition

Super_Moto said:
the error shows when I try to flash the .zip file _Install zip from sdcard_choose zip from sdcard I pic the file and it doesn't install it says aborted show me the yellow triangle symbol I was assuming im flashing the wrong file.
before I do an install I wipe data/factory reset and wipe cache partition
Click to expand...
Click to collapse
You are trying to flash through stock recovery. Install through custom recovery.

hotdog125 said:
You are trying to flash through stock recovery. Install through custom recovery.
Click to expand...
Click to collapse
I tried that and im also giving me (installation aborted) I used file cm-10-20130918-NIGHTLY-mb526 but no luck

Super_Moto said:
I tried that and im also giving me (installation aborted) I used file cm-10-20130918-NIGHTLY-mb526 but no luck
Click to expand...
Click to collapse
The file is ok, i've installed it on my defy

MikBre said:
The file is ok, i've installed it on my defy
Click to expand...
Click to collapse
Im clue less what im doing wrong I looked on u tube on installing jelly bean im following the same steps but Im getting (file aborted) when I try flashing the file
what r the steps u take on installing the file ?
At first I tried: Reboot in _Recovery _Install zip from sdcard_choose zip from sdcard_pick the the file _yes install
it starts by saying
Finding update package...
Opening update package...
E:Can't open /sdcard/cm-10-20130918-NIGHTLY-mb526.zip
(bad)
Installation aborted.
2nd I tried
Reboot in Bootmenu
Recovery _ Custom Recovery etc ..etc ..
and get the same message
Finding update package...
Opening update package...
E:Can't open /sdcard/cm-10-20130918-NIGHTLY-mb526.zip
(bad)
Installation aborted.
always did the factory rest and wiping during both process

Super_Moto said:
Finding update package...
Opening update package...
E:Can't open /sdcard/cm-10-20130918-NIGHTLY-mb526.zip
(bad)
Installation aborted.
Click to expand...
Click to collapse
just to be sure, your phone is not connected to a computer when you did the flash, right?

jh20 said:
just to be sure, your phone is not connected to a computer when you did the flash, right?
Click to expand...
Click to collapse
yes phone is disconnected from computer,I had no issues installing cm7
My is CMRecovery v5.0.3.2-jordan
and Bootmenu <v1.1.1> could these be the problem some thing needs to be updated ?

Super_Moto said:
what r the steps u take on installing the file ?
Click to expand...
Click to collapse
If you want a video guide look at the Youtube channel of locslikes.
Therre is a guide call "MOTOROLA DEFY How To Install ClockWorkMod and Cyanogenmod 10 Jelly Bean Android"

MikBre said:
If you want a video guide look at the Youtube channel of locslikes.
Therre is a guide call "MOTOROLA DEFY How To Install ClockWorkMod and Cyanogenmod 10 Jelly Bean Android"
Click to expand...
Click to collapse
Im just guessing.... that my bootmenu seems to be out of date possible being the reason that jellybean wont install,
bootmenu is up to 2ndInit Recovery v2.3 can this file be installed over v1.1.1 ?

Super_Moto said:
Im just guessing.... that my bootmenu seems to be out of date possible being the reason that jellybean wont install,
bootmenu is up to 2ndInit Recovery v2.3 can this file be installed over v1.1.1 ?
Click to expand...
Click to collapse
out of curiousity, i restored my mb525 back to cm7 nightly 20111201 nandroid, which has cwm v5.0.3.2. i did not check the bootmenu version but it should be the same as yours. then, after formatting system/cache partitions, i flashed cm-10-20130918-nightly-mb526.zip, and it worked.
so i don't really know what's wrong with your phone, but i have a couple of suggestions for you to try. not that there's any logical explanations but try it anyway:
1. according to the error messages, you have the cm10 rom in the root folder of the sdcard. try creating a sub-folder called cm10 and copy the cm10 rom and the minimal gapps into it.
2. download the defy_fullwipe_ext4.zip and defy_fullwipe_ext3.zip ( for later use, when you want to revert back your rom) from here and put them in cm10 folder as well:
http://forum.xda-developers.com/showthread.php?t=1818520
3. reboot into recovery but don't do any format or wipe. instead flash the file defy_fullwipe_ext4.zip and this will format your partitions into the ext4 file system.
4. then flash the cm10 rom. if it installs sucessfully, then without any further wiping,nor flashing the minimal gapps, reboot the phone. (note that the os will reboot once more in the middle of booting up, seemingly having a bootloop problem. don't worry it's meant to do that, unless it rebooted more than once)
5. if it boots up sucessfully, do some basic set up first before rebooting back into recovery to flash the minimal gapps.
alternatively you could try flashing cm9.1 (ext3) to get a newer bootmenu and cwm versions before flashing cm10. no need to flash any gapps, just wipe system/cache partitions and flash the cm9.1 rom by itself. reboot into cm9.1, do basic set up. once it's ready reboot into recovery and do the above steps, starting from step 3, to flash cm10.
good luck.....
edit: did you get your cm10 rom from here:
http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/

jh20 said:
out of curiousity, i restored my mb525 back to cm7 nightly 20111201 nandroid, which has cwm v5.0.3.2. i did not check the bootmenu version but it should be the same as yours. then, after formatting system/cache partitions, i flashed cm-10-20130918-nightly-mb526.zip, and it worked.
so i don't really know what's wrong with your phone, but i have a couple of suggestions for you to try. not that there's any logical explanations but try it anyway:
1. according to the error messages, you have the cm10 rom in the root folder of the sdcard. try creating a sub-folder called cm10 and copy the cm10 rom and the minimal gapps into it.
2. download the defy_fullwipe_ext4.zip and defy_fullwipe_ext3.zip ( for later use, when you want to revert back your rom) from here and put them in cm10 folder as well:
http://forum.xda-developers.com/showthread.php?t=1818520
3. reboot into recovery but don't do any format or wipe. instead flash the file defy_fullwipe_ext4.zip and this will format your partitions into the ext4 file system.
4. then flash the cm10 rom. if it installs sucessfully, then without any further wiping,nor flashing the minimal gapps, reboot the phone. (note that the os will reboot once more in the middle of booting up, seemingly having a bootloop problem. don't worry it's meant to do that, unless it rebooted more than once)
5. if it boots up sucessfully, do some basic set up first before rebooting back into recovery to flash the minimal gapps.
alternatively you could try flashing cm9.1 (ext3) to get a newer bootmenu and cwm versions before flashing cm10. no need to flash any gapps, just wipe system/cache partitions and flash the cm9.1 rom by itself. reboot into cm9.1, do basic set up. once it's ready reboot into recovery and do the above steps, starting from step 3, to flash cm10.
good luck.....
edit: did you get your cm10 rom from here:
http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/
Click to expand...
Click to collapse
I did try using that link but the files still would abort when flashing, also tried http://d-h.st/users/Quarx files it did the same thing
I followed your instruction but decided to goto cm 9 first I flashed the (ext3) file it installed and cm9.1 installed also installed twrp with no issues but when I was going through cm9 and its functions I couldent go on line a popup message (Unfortunately, brower has stopped) also I wasn't able to log on google play a pop up message (Unfortunately,com. google android.gb has stopped). so I got fed up and decided to goto cm10.1 so I first flashed with ext4.zip it installed and then tried to flash 10.1 file once again the file wouldn't install it gave me aborted file message again. I had no choice to reboot and I had to reinstall the factory file(brick). I am now back to where I started :silly: cm7 2.3.7 its been a hell of a weekend ........... ill give it another shot soon :fingers-crossed:

[Q] Only CM10 won't install on red lens Defy?

I recently found out, that some people and I are unable to install Quarx CM10 for our red lens defy, but we can try a method going to a defy+ sbf which comes with BL version 7, and after that it works, but you won't be able to downgrade.
Is there any other way to make it successfully install without this radical approach of flashing a dfp sbf on my red lens MB525? Why won't Quarx's CM10 install if i'm not BL7? Is there any JB rom that does not require this kind of treatment?

gyorgyszemok said:
I recently found out, that some people and I are unable to install Quarx CM10 for our red lens defy, but we can try a method going to a defy+ sbf which comes with BL version 7, and after that it works, but you won't be able to downgrade.
Is there any other way to make it successfully install without this radical approach of flashing a dfp sbf on my red lens MB525? Why won't Quarx's CM10 install if i'm not BL7? Is there any JB rom that does not require this kind of treatment?
Click to expand...
Click to collapse
Your most probably doing something wrong. List your steps.

hotdog125 said:
Your most probably doing something wrong. List your steps.
Click to expand...
Click to collapse
i was on cm9, and i usually tried installing this way
wipe data/cache/dalvik
install cm10
install gapps
reboot
bootloop
OR
wipe data/cache/dalvik
format to ext4
install cm10
install gapps
reboot
bootloop
I also have an older thread which was kinda 'deadline' for me bcuz i won't go risky by installing defyplus sbf, when it should work normally, here's the link: http://forum.xda-developers.com/showthread.php?t=2218569

gyorgyszemok said:
i was on cm9, and i usually tried installing this way
wipe data/cache/dalvik
install cm10
install gapps
reboot
bootloop
OR
wipe data/cache/dalvik
format to ext4
install cm10
install gapps
reboot
bootloop
I also have an older thread which was kinda 'deadline' for me bcuz i won't go risky by installing defyplus sbf, when it should work normally, here's the link: http://forum.xda-developers.com/showthread.php?t=2218569
Click to expand...
Click to collapse
Get AROMA wiper for Defy (search for it), 'flash' it, a white screen with some options will appear. Choose wipe system, data and cache in ext4 (DO NOT REBOOT AFTER THIS), and then immediately flash latest CM10 (9 July) and minimal gapps.
OR, choose Defy ultimate wiper. Download the appropriate file and flash.

hotdog125 said:
Get AROMA wiper for Defy (search for it), 'flash' it, a white screen with some options will appear. Choose wipe system, data and cache in ext4 (DO NOT REBOOT AFTER THIS), and then immediately flash latest CM10 (9 July) and minimal gapps.
OR, choose Defy ultimate wiper. Download the appropriate file and flash.
Click to expand...
Click to collapse
As long as you do not do this on TWRP, which no longer works due to random reboots that will leave you knee-deep in sh*t, you should be fine.
Use CWM to follow his instructions or you can flash your stock SBF (NOT BL7, WHO TOLD YOU THAT BL7 WOULD SOLVE YOUR PROBLEMS??) to get a clean install and start over.
Whoever told you that you should flash a DFP-188/231/2311/2312 SBF in order to use CM10 is a nuthead and should not be helping anyone.

droid_<3er said:
As long as you do not do this on TWRP, which no longer works due to random reboots that will leave you knee-deep in sh*t, you should be fine.
Use CWM to follow his instructions or you can flash your stock SBF (NOT BL7, WHO TOLD YOU THAT BL7 WOULD SOLVE YOUR PROBLEMS??) to get a clean install and start over.
Whoever told you that you should flash a DFP-188/231/2311/2312 SBF in order to use CM10 is a nuthead and should not be helping anyone.
Click to expand...
Click to collapse
It works on TWRP 3 out of 5 times. I've had to reflash sbf 2 times because of an unexpected reboot.

droid_<3er said:
As long as you do not do this on TWRP, which no longer works due to random reboots that will leave you knee-deep in sh*t, you should be fine.
Use CWM to follow his instructions or you can flash your stock SBF (NOT BL7, WHO TOLD YOU THAT BL7 WOULD SOLVE YOUR PROBLEMS??) to get a clean install and start over.
Whoever told you that you should flash a DFP-188/231/2311/2312 SBF in order to use CM10 is a nuthead and should not be helping anyone.
Click to expand...
Click to collapse
I mentioned my old post regarding the same issue, there you can find all other information regarding the users, or why did they say that. To be honest I did not really want to believe that flashing a dfp 231 sbf would solve my problem, neither that it could be the only solution.. Im giving AROMA wiper a try in the next few hours, wish me luck.

i got status 7 error...
edit: the sad part is i found a solution by googleing the error, but the line i should remove from the updater script wasnt even there.

@droid_<3er
If you could check previous such threads, you will find that in certain cases, because of 2ndboot incompatibilities, some people were unable to use cm10 because of the same. The stock kernel must be compatible for the kexec approach. It seems it isn't true for all kernels. You should read up before trying to pass comments on others.
As for OP I wish you luck in solving this issue, since I have by elimination found bl version upgrading to be the only working solution. It may not be the only one, but it certainly works.
Sent from my MB526 using Tapatalk 2

[Solved] Only with Quarx CM10: Status 7, Installation aborted?

Title says it all: I get symlink: some symlinks failed, status 7 error, installation aborted when I try to install Quarx's CM10 (2nd boot). Haven't tried any other JB, since I can't find any that fits. Maybe something with 2nd boot? It seems not to work on my phone...
I tried google-ing the problem, found some information about removing lines from updater-script, but the line was not even there (something with asserts).
Defy red lens MB525

Try a system wipe. That error is because of some filesystem problem, not 2ndboot
Sent from my MB526 using Tapatalk 2

I tried wiping with AROMA wiper yesterday: ext4, wipe data, system, cache, dalvik, then NO reboot and install cm 10... it failed as hell.

ive had the same issue as you with cm10 2ndboot. i moved on after trying to get it installed for months. 10.2 is awesome! just make sure you start from a fresh sbf flash and reroot and all that jazz. also, start with twrp!

undyingvisage58 said:
ive had the same issue as you with cm10 2ndboot. i moved on after trying to get it installed for months. 10.2 is awesome! just make sure you start from a fresh sbf flash and reroot and all that jazz. also, start with twrp!
Click to expand...
Click to collapse
thanks for the advice but i can't seem to install twrp. goomanager is not available for stock éclair/froyo, and without installing any cwm i can't install twrp. also, i tried to install twrp from cm9's cwm, it wrote success but after reboot i still had cwm. WUT

Dummy question: did you try to download another ROM?s zip file ?

Alka-Seltzer PLUS said:
Dummy question: did you try to download another ROM?s zip file ?
Click to expand...
Click to collapse
I tried different nightlies of JB 4.1, 4.2, 4.3, MIUI JB. Also did clean install with 0 success. I'm getting close to the problem, and reached this far:
1.: My CWM (5.x.x.x) does not support the 2nd boot updater script. I don't know how could I upgrade to CWM v6 (seriously, I searched a lot but nothing.)
2.: I can't install TWRP. I mean... Éclair and froyo does not support GooManager to install from an app, and I can only install CWM from 2ndinit.apk. From CWM I install TWRP, it says: "Whoah you are great bro, reboot recovery!" I do that and boom CWM again.
Srsly.: HOW can this happen to me? Other ppl resolved this problem by flashing DFP sbf to their normal Defy (red lens). I won't do that. You know, there must be a way I can install CWM v6 or TWRP. But how? If anyone gives me a solution for my problem which is going on for half a year... I'll get a heart attack I'll be so happy

Uhm.... recently i had to start from SBF and had no problem installing last ( Quarx's ) build of 4.1.2 after having installed the first 2ndinit i downloaded from the web ... so... write exactly your steps ( i know, i know, .. but .... where'R talking through a monitor and misunderstandings are waitnig for us )

Alka-Seltzer PLUS said:
Uhm.... recently i had to start from SBF and had no problem installing last ( Quarx's ) build of 4.1.2 after having installed the first 2ndinit i downloaded from the web ... so... write exactly your steps ( i know, i know, .. but .... where'R talking through a monitor and misunderstandings are waitnig for us )
Click to expand...
Click to collapse
I start from sbf (Froyo). Install 2ndinit apk, install 2ndinit, reboot, wipe data cache dalvik, (try to) install cm10.x > status 0 or status 7
I start from cm9(epsylon build). Reboot into recovery, (try to) install cm10.x > status 0 or status 7
I start from cm9(epsylon build). Reboot into recovery, AROMA Wipe (system, data, cache) into Ext4, (try to) install cm10.x > status 0 or 7
After these, I can't revert to any rom even if i format to ext3 with AROMA Wiper. Cuz' my defy goes soft-bricked and i have to recover it RSD Lite.

Do not reboot after wiping/formatting system. Immediately flash some ROM. Ext3 --> CM7.
Sent from my MB526 using xda app-developers app

gyorgyszemok said:
I start from sbf (Froyo). Install 2ndinit apk, install 2ndinit, reboot, wipe data cache dalvik, (try to) install cm10.x > status 0 or status 7
I start from cm9(epsylon build). Reboot into recovery, (try to) install cm10.x > status 0 or status 7
I start from cm9(epsylon build). Reboot into recovery, AROMA Wipe (system, data, cache) into Ext4, (try to) install cm10.x > status 0 or 7
After these, I can't revert to any rom even if i format to ext3 with AROMA Wiper. Cuz' my defy goes soft-bricked and i have to recover it RSD Lite.
Click to expand...
Click to collapse
No rooting between sbf (Froyo) and installing 2ndinit apk ?

hotdog125 said:
Do not reboot after wiping/formatting system. Immediately flash some ROM. Ext3 --> CM7.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Ehm, I didn't reboot after system format, I know that I shouldn't or I get softbricked.

Alka-Seltzer PLUS said:
No rooting between sbf (Froyo) and installing 2ndinit apk ?
Click to expand...
Click to collapse
Yea. It's rooted by default when i flash it....

gyorgyszemok said:
Yea. It's rooted by default when i flash it....
Click to expand...
Click to collapse
I would try to check the md5 at this point

gyorgyszemok said:
Ehm, I didn't reboot after system format, I know that I shouldn't or I get softbricked.
Click to expand...
Click to collapse
I started with sbf, Framaroot, 2ndinit. Then I directly flashed CM10 (9th July) and it flashed successfully. The latest dual recovery has CWMv6, but it's only for CM10 ROMs. Have you tried pre-TWRP builds (maybe the November builds)?
Or maybe, other ROMs like PA, PAC, etc.?

gyorgyszemok said:
Title says it all: I get symlink: some symlinks failed, status 7 error, installation aborted when I try to install Quarx's CM10 (2nd boot). Haven't tried any other JB, since I can't find any that fits. Maybe something with 2nd boot? It seems not to work on my phone...
I tried google-ing the problem, found some information about removing lines from updater-script, but the line was not even there (something with asserts).
Defy red lens MB525
Click to expand...
Click to collapse
Happened to me to before. Try change your kernel. Stock kernel cant flash cm10 and its variant. It'll give status 7 error. When i change to other kernel ex;BL v12 no problem at all.

aiis89 said:
Happened to me to before. Try change your kernel. Stock kernel cant flash cm10 and its variant. It'll give status 7 error. When i change to other kernel ex;BL v12 no problem at all.
Click to expand...
Click to collapse
I forgot to add that my problem got resolved like a month ago.
My main problem was that I couldn't install any JB rom because of status 0, status 7 or bootloop (always), so I went radical:
I flashed DFP231.sbf (for defy plus) on bayer lens defy (MB525!), used Framaroot to root, installed LATEST(!) cwm, and then I could install CM10.x with no problem!

[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.