Related
-Solved btw-
Hey all. I've just tried installing CM9 using the instructions HERE.
I used the second options..
How To Flash ICS(Defy Builds)
1:Head Over To Stable recovery
2:Wipe Data
3:Install ZIp from SD Card
4:Select ICS(Defy) .zip
5:Flash
6:Flash Gapps and CM7 Kernel
7:Clear Cache and Dalvik Cache
Click to expand...
Click to collapse
I used the most recent CM9 rom from here.
(CM9-NIGHTLY-120319-Defy.zip 19-Mar-2012 23:15 104M )
I got my kernels from this thread. I've tried both CM7 (2.2 kernel) and CM9 (2.3 kernel). With the CM7 2.2 Kernel, I get stuck on the "Motorola" logo, and with CM9 2.3 kernel I get stuck on the CM9 boot logo (1 hour + now)
From the FAQ thread I found this (below), but as I said I've tried both kernels.
FAQ:
Q: I installed 08/12 build(or newer), but it gets stuck at the CM boot logo. What do I do?
07/12 contains the required 2.3 kernel. 08/12 and newer do not. If you have installed 08/12 or newer, enter recovery and flash the 2.3 kernel, then reboot. This applies only to Defy owners; Defy+ owners already have 2.3 stock ROM and kernel, so they do not need to apply the kernel.
In fact, the kernel zip for Defy owners is the kernel from Defy+.
Click to expand...
Click to collapse
I've tried everything I can think of. Can anyone help?
Thanks.
pk92 said:
Hey all. I've just tried installing CM9 using the instructions HERE.
I used the second options..
I used the most recent CM9 rom from here.
(CM9-NIGHTLY-120319-Defy.zip 19-Mar-2012 23:15 104M )
I got my kernels from this thread. I've tried both CM7 (2.2 kernel) and CM9 (2.3 kernel). With the CM7 2.2 Kernel, I get stuck on the "Motorola" logo, and with CM9 2.3 kernel I get stuck on the CM9 boot logo (1 hour + now)
From the FAQ thread I found this (below), but as I said I've tried both kernels.
I've tried everything I can think of. Can anyone help?
Thanks.
Click to expand...
Click to collapse
Hi,
Can you also provide the following info:
Which ROM did you have as stock?(Was it a froyo kernel or GB kernel as stock)
If you already had GB ROM in your phone you don't need the kernels to be installed!
It was a Froyo kernel
He's right. U don't have to flash a kernel if u were on froyo (2.6.32.9-gb08c3c8). Just make a wipe after installing the cm9 rom.
U only have to pick the right version. There are froyo-cm9 builds and GB-cm9 builds (so if u are on GB-kernel right now, take a GB-Build).
Or try the "codename android 1.5.5"... (froyo-kernel!) it's ported from the nexus
I'm testing this rom right now and for me it's working much better than cm9 builds.
Greetz
I recieved a pm suggesting installing cm7 then cm9 over, but more bootloop..
Sent from my Huawei_8100-9 using XDA
Oh, its a cm7 bootloop now by the way, forgot to mention that
Sent from my Huawei_8100-9 using XDA
pk92 said:
Oh, its a cm7 bootloop now by the way, forgot to mention that
Sent from my Huawei_8100-9 using XDA
Click to expand...
Click to collapse
Well, I think there is no need to flash cm7 before? (I didn't and it worked, correct me if I talk bull****)
Try to install the zip, and AFTER that make a wipe (do not boot in system after installing, first the wipe than boot!)
Is it a quark or epsy? When I flashed the epsy over quark I had big problems so I had to start again.
I have no idea if it's Quark or Epsy :S
hboy1337 said:
Well, I think there is no need to flash cm7 before? (I didn't and it worked, correct me if I talk bull****)
Try to install the zip, and AFTER that make a wipe (do not boot in system after installing, first the wipe than boot!)
Is it a quark or epsy? When I flashed the epsy over quark I had big problems so I had to start again.
Click to expand...
Click to collapse
pk92 said:
I have no idea if it's Quark or Epsy :S
Click to expand...
Click to collapse
Hi,
Well you are correct you do not need to flash CM9 above CM7! it's Quark or Epsy do not matter. What matters is the kernel! If you have a Defy+ or stock GB use the CMs for Defy+(preferably Quarx's because they are more updated and he is the only dev with a Defy+) and don't flash any extra kernels. If you have Defy or Froyo kernel then use CMs for Defy. Always remember two golden rules after flashing ROMs:
1.) Wipe data.
2.) Wipe Dalvik.
In fact even after or before a full SBF you may not be able to boot until you do a data wipe from stock recovery! (Seen that in some cases and in mine case too!) ....
pranks1989 said:
Hi,
Well you are correct you do not need to flash CM9 above CM7! it's Quark or Epsy do not matter. What matters is the kernel! If you have a Defy+ or stock GB use the CMs for Defy+(preferably Quarx's because they are more updated and he is the only dev with a Defy+) and don't flash any extra kernels. If you have Defy or Froyo kernel then use CMs for Defy. Always remember two golden rules after flashing ROMs:
1.) Wipe data.
2.) Wipe Dalvik.
In fact even after or before a full SBF you may not be able to boot until you do a data wipe from stock recovery! (Seen that in some cases and in mine case too!) ....
Click to expand...
Click to collapse
What I usually do when installing roms is this:
-Enter Stable Recovery
-Factory reset & clear data
-Install Zip from SD Card (Defy CM9.zip)
-Wipe cache
-Wipe dalvik cache.
So I need to do a Factory reset & data wipe in stock before flashing CM9?
I've managed to get the CM9-NIGHTLY-120112-Defy+.zip rom working from here.
I installed the CM7 kernel, then the CM9 kernel ontop of that, then installed gapps, and wiped cache/dalvik. (though I'm not sure wiping dalvik worked, as when I clicked it it just refreshed, didn't give me the option to confirm that I want to wipe dalvik)
However, this doesn't have any mobile network, and a lot of settings options are missing..
I'm still trying to get the CM9-NIGHTLY-120319-Defy.zip rom working from here working, but it's stuck on the bootloop.
If I try the baseband switcher in-rom then it asks me to restart, and then once it has restarted it goes back to factory settings (the welcome screen to set up the "new" phone)
pk92 said:
I've managed to get the CM9-NIGHTLY-120112-Defy+.zip rom working from here.
I installed the CM7 kernel, then the CM9 kernel ontop of that, then installed gapps, and wiped cache/dalvik. (though I'm not sure wiping dalvik worked, as when I clicked it it just refreshed, didn't give me the option to confirm that I want to wipe dalvik)
However, this doesn't have any mobile network, and a lot of settings options are missing..
I'm still trying to get the CM9-NIGHTLY-120319-Defy.zip rom working from here working, but it's stuck on the bootloop.
If I try the baseband switcher in-rom then it asks me to restart, and then once it has restarted it goes back to factory settings (the welcome screen to set up the "new" phone)
Click to expand...
Click to collapse
For CM9 you can do a data wipe from CWm itself, don't do from stock. Only if you do a full SBF flash do a data wipe from stock. And the CM9 you are using is toooo old!!! Quarx's CM9 for Defy+ are much newer! So try that here . 17th March is the latest one. That should run fine.. Worked great for me..
Hey I see once you were using CM for Defy(Dint work for you as you got bootloop) and next moment you were trying CM9 for Defy+(which worked) !!! :O First be sure which kernel you have in your original ROM(flashed SBF)!!
pranks1989 said:
For CM9 you can do a data wipe from CWm itself, don't do from stock. Only if you do a full SBF flash do a data wipe from stock. And the CM9 you are using is toooo old!!! Quarx's CM9 for Defy+ are much newer! So try that here . 17th March is the latest one. That should run fine.. Worked great for me..
Hey I see once you were using CM for Defy(Dint work for you as you got bootloop) and next moment you were trying CM9 for Defy+(which worked) !!! :O First be sure which kernel you have in your original ROM(flashed SBF)!!
Click to expand...
Click to collapse
I eventually decided to flash a froyo SBF (2.2.2), and flashed CM9 Defy from here. Suggested to me by Pottkopp.
I didn't flash any kernel and it worked fine.
Also installed Pottkopp's AIO.
So, all solved
Can someone help me?
Ok!
So i have green lensed defy. I already had CM9 installed( installed it using normal procedure). So i decided i will return to stock, by recovering backup. So i did. After a while on stock, i decided to go back to CM9. I forgot to do factory reset, and after install wipe chache and dalvik.I booted phone, and entered requesting data. I after that got back to recovery and did factory reset via custom recovery, and installed it again using correct method. My phone seems a bit slower than before, and did i damaged my phone?
Hello.
I have installed the Defy Red Len CM10 Nightly Build.
I know there is a 2nd boot nightly build which provided a better solution than the non 2nd boot build
Can anyone provide a step guideline to upgrade / flash installation to the 2nd boot nightly build?
Thanks a lot
reaperhk said:
Hello.
I have installed the Defy Red Len CM10 Nightly Build.
I know there is a 2nd boot nightly build which provided a better solution than the non 2nd boot build
Can anyone provide a step guideline to upgrade / flash installation to the 2nd boot nightly build?
Thanks a lot
Click to expand...
Click to collapse
Here you go
if upgrading from previous CM10 builds:
1) Wipe Cache and Dalvik.
2)Flash Rom
3)Flash Gapps
4)Wipe Cache and Dalvik again & Reboot
and if coming from different builds(like CM7,CM9 etc)
1)Wipe Data, Cache and Dalvik
2)Flash Rom
3)Flash Gapps
4)Wipe Cache and Dalvik again & Reboot
Hope this helps you and ALWAYS MAKE A NANDROID BACKUP BEFORE FLASHING NEW ROM.
Thanks a lot. It works
Do you know how to the url for the Check update repo for 2nd boot build?
if you have CM10 from 24.09. and want jump to new kernel by Quarx you don't have to flash gapps ,in the other side yes you have to ,i recommended minimal gapps
yep¡ whit out gapss, for me works like a charm... the new build is 21.10
flashing........
Sent from my MB526 using xda premium
Defy MB525 green lense
NeoAven said:
yep¡ whit out gapss, for me works like a charm... the new build is 21.10
flashing........
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Does anyone know whether this build works on a MB525 with green lense as well, and can confirm that this is one build for 525 green and red lenses as well as for MB526 ?
Greetz.
I own a MB525, red lens, and I am using CM10 by Quarx (Sep 12th). So I just have to:
1) Wipe Cache and Dalvik.
2)Flash Rom
3)Flash Gapps
4)Wipe Cache and Dalvik again & Reboot
And, in today's release, then the update?
What about the kernel? Which one, and when? Thanks
EDIT: Oh, is it incluided in the ROM file now? Sorry, I don't quite understand what the differences are between classic CM10 nightlies and CM10 2ndboot nightlies (I know something about the custom kernel, but haven't found much information exclusively about it).
Please ask all questions in the Q&A section. Thread moved there.
I just followed these steps and now can't boot. I am able to enter the boot menu, but custom recovery just brings me back to the main menu, stable recovery does the same thing and stock recovery brings me to an android with a exclamation point in a triangle.
In fact anything I tap just brings me back to the main menu except boot and reboot.
Any ideas?
so the usual wipe and flash rom works even for earlier cm10 builds? i thought there was more than that (to install new custom rom.. flash some other files as well etc).. just making sure..
can u tell me the advantages? faster? more battery life? ........
General rulez to upgrade from CM10 24.09. to new qkernel :
1. Wipe's all data/cache/dalvik
2. install zip the newest/upgrede v4 from 27.10.
3. install gapps (all or minimal ) (the same gapps as 24.09. version)
4. do wipe's but only cache and dalvik
5. reboot
it's all enjoy
Question:
Whats the difference between 2nd boot builds and "non"2nd boot builds?
the new kernel gives as new possibility ,i can tell you technical staff ,but i use ROM before and after and i think that 2nd boot is faster and more stabile
Hi.
I'd like to upgrade to upgrade my Motorola Defy+ MB526 from Quarx CM10 24-09 (non-2ndboot) to 27.10 (2ndboot), but I'm not really sure of the steps. So I have to:
Open Stable Recovery
Wipe Cache, Dalvik and Data
Install zip from sdcard - 18.10 2ndboot build for MB526
Install zip from sdcard - update_for_18.10_v4.zip
Install zip from sdcard - gapps
Reboot
Is that right?
EDIT: Worked, done the following:
- Start Stable Recovery (of last Quarx non-2ndboot ROM)
- Backup all (Nandroid)
- Wipe data/factory reset
- wipe cache
- wipe dalvik cache
- install zip from sdcard -> 2ndboot ROM>100MB.zip
- install zip from sdcard -> update_for_xxxx_vx.zip
- install zip from sdcard -> GAPPS (I used PicoTTS (all))
- wipe cache
- wipe dalvik cache
- exit recovery
- shutdown
- Start Bootmenu
- shutdown
- Power on
- After first boot it rebooted but then it booted 2ndboot ROM perfectly.
Why is it that it should be shut down and restarted twice? Any particular reason?
Conzo427 said:
I just followed these steps and now can't boot. I am able to enter the boot menu, but custom recovery just brings me back to the main menu, stable recovery does the same thing and stock recovery brings me to an android with a exclamation point in a triangle.
In fact anything I tap just brings me back to the main menu except boot and reboot.
Any ideas?
Click to expand...
Click to collapse
same problem here...........
prashant_ch said:
same problem here...........
Click to expand...
Click to collapse
do this:
goto recovery,
choose stable recovery>wipe data>wipe cache>advanced>wipe dalvik
than flash http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/CM10-20121018-NIGHTLY-mb526.zip
wipe cache and dalvik again
now flash http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/update_for_18.10_v4.zip
wipe cache and dalvik again.
and reboot
it should boot normaly,if not,than remove battery,and reinsert it after 10 mins,
first boot will take a little time,so dont worry.
if it boots perfectly than u can go into the recovery again and install gapps :good:
..
I normally updated CM9 to CM10 i dont wiped the data just cashes and then i updated to 2ndboot , Its like you instal a new rom from any kind , just you dont wipe the data . This worked for me.... I dont know it that will work for you , I have a defy + mb526 , hope it will work for you . But dont broke your phone .
defyus3r said:
Why is it that it should be shut down and restarted twice? Any particular reason?
Click to expand...
Click to collapse
its not necessary
---------- Post added at 12:50 AM ---------- Previous post was at 12:49 AM ----------
battlepower said:
I normally updated CM9 to CM10 i dont wiped the data just cashes and then i updated to 2ndboot , Its like you instal a new rom from any kind , just you dont wipe the data . This worked for me.... I dont know it that will work for you , I have a defy + mb526 , hope it will work for you . But dont broke your phone .
Click to expand...
Click to collapse
DEFY cant be broken merely by flashing rom :fingers-crossed:
About the updates for 18/10, i need to flash zip or apply update?
Hello,
I would know if we can downgrade the Defy+ with the last Quarx's nightly with the custom kernel to install CyanogenMod 7.2 stable and if we can take (with a data backup in recovery of course) the data from the actual version of CM10 and restore on CM 7.2 stable without problem like bootloop ?
Thank you in advance
Backup your /data/app folder
You can copy /data/app to /sdcard to save your downloaded apks.
Not sure if they are going to work.
euros60 said:
Hello,
I would know if we can downgrade the Defy+ with the last Quarx's nightly with the custom kernel to install CyanogenMod 7.2 stable and if we can take (with a data backup in recovery of course) the data from the actual version of CM10 and restore on CM 7.2 stable without problem like bootloop ?
Thank you in advance
Click to expand...
Click to collapse
rafaelsoaresbr said:
You can copy /data/app to /sdcard to save your downloaded apks.
Not sure if they are going to work.
Click to expand...
Click to collapse
Thank but I know already the manipulation in order to do a backup and restore.
I try to downgrade to CM7.2 stable, there is the battery problem with "?" icon, I installed the battery fix for CM7 but I re installed my backup of CM10, in fact in my precedent question I did a fault : I would to downgrade from CM10 to my rom stock's backup before the installing of CM10.
So I try also to downgrade to my stock rom's backup, same problem with unknown battery I also had the battery fix but when I try to restore my CM10's data, the stock rom's recovery doesn't see the files for restore my data, it says "no file data in this backup, no .ext3 ..."
I think the older recovery doesn't recognize the file types of CM10 recovery.
Thanks for your response !
Cannot enter recovery mode
I also want to downgrade from quarx´s CM 10 to CM7.2 or 9, but i can´t access to recovery mode. I´ve tried the button combination, and the recovery mode in android, but none works. Is there any tutorial on how return to something like stock just to star all over?
Install 2ndinit
Try installing 2ndinit.
yne22do said:
I also want to downgrade from quarx´s CM 10 to CM7.2 or 9, but i can´t access to recovery mode. I´ve tried the button combination, and the recovery mode in android, but none works. Is there any tutorial on how return to something like stock just to star all over?
Click to expand...
Click to collapse
yne22do said:
I also want to downgrade from quarx´s CM 10 to CM7.2 or 9, but i can´t access to recovery mode. I´ve tried the button combination, and the recovery mode in android, but none works. Is there any tutorial on how return to something like stock just to star all over?
Click to expand...
Click to collapse
press and hold the power button->reboot->custom recovery,tested on PA using quarx build sep 24th
defyus3r said:
press and hold the power button->reboot->custom recovery,tested on PA using quarx build sep 24th
Click to expand...
Click to collapse
Can anybody describe how the downgrade procedure should be carried out?
Regards, TY
euros60 said:
Hello,
I would know if we can downgrade the Defy+ with the last Quarx's nightly with the custom kernel to install CyanogenMod 7.2 stable and if we can take (with a data backup in recovery of course) the data from the actual version of CM10 and restore on CM 7.2 stable without problem like bootloop ?
Thank you in advance
Click to expand...
Click to collapse
Yes you can downgrade, I did it yesterday only.
For the downgrade to CM9:
-Wipe Data /Fullwipe
-Install the Cm9 nightly you want (Step by step guide is here - http://forum.xda-developers.com/showthread.php?t=1795647)
-install Gapps
-Format Cache/Dalvik Cache
Regards,
Amit Sharma
Press thanks button if this post helped you all the best
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 :/
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