-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?
Related
Hello everybody, I recently decided to try CM9 after months with CM7,
Well, I didnt like... too many bugs for me.
I want to go back to Cm7 but i think I read somewhere that downgrades are tricky...
I flashed my phone a lot of times, got the bootloader and everything but is it exactly the same as any other rom ? Just copy files to sd card,
Clear all caches > update zip from sdcard -> etc etc ?
That's depends, do you have a Defy+ or Defy?, which CM9 kernel based did you flashed??, always keep in mind that Defy+ has GB Kernel and Defy Froyo Kernel, it means that the stock ROM comes with that Kernel version, so, if you flashed a CM9 GB kernel for Defy+ in your Defy/Defy+ you must flash the CM7 with GB Kernel or you can flash the Kernel via a CWM zip and then flash the CM7 which uses the Kernel you flashed, ALWAYS the kernel you have installed and the kernel that the ROM uses must be the SAME!
Good hacking!
danielzyy said:
Hello everybody, I recently decided to try CM9 after months with CM7,
Well, I didnt like... too many bugs for me.
I want to go back to Cm7 but i think I read somewhere that downgrades are tricky...
I flashed my phone a lot of times, got the bootloader and everything but is it exactly the same as any other rom ? Just copy files to sd card,
Clear all caches > update zip from sdcard -> etc etc ?
Click to expand...
Click to collapse
Just do a data wipe > flash the CM7 you were using(or may try a new one) > boot to recovery > data,cache and dalvik wipe. Reboot. I think that should suffice!
I didnt flash any kernel m8, I got normal Defy...
I was told that if I got a CM7 before I just need to flash CM9 Froyo without any kernel (seems right as it worked).
Yes,in that case, do what pranks1989 says
Ty all, just charging my Defy to 100% and then I will try the new CM7.2
I'm using the 31 dec version of CM7.2, is great!
Hello, I am on a mb525, green lense, CM7.1 and I'm continuosly getting bootloops white trying to upgrade to CM10.
I follow the steps:
1) Go to Stable 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 froyo kernel (222-179-4-signed)
5) Flash CM10-20120924-NIGHTLY-mb525.zip.
6) Flash minimal Gapps.
7) Wipe Cache and Dalvik again (recommended).
8) Restart.
After restart, the red Motorola logo appears, and then the phone gets into a bootloop.
The same story while trying to upgrade from CM9 to CM10. My bootmenu is v1.0.5 and my recovery is v5.0.2.4.
Thank you,
why are you flashing froyo kernel separately? the cm10 zip includes kernel...also don't flash 24/9.
the 2nd boot builds are now much better, so flash 2/11
syllogyking said:
why are you flashing froyo kernel separately? the cm10 zip includes kernel...also don't flash 24/9.
the 2nd boot builds are now much better, so flash 2/11
Click to expand...
Click to collapse
Hi! had my defy resting in a drawer for some time, I see there's a custom kernel now, if I want to flash de 11/2 nightly do I need to flash a different kernel or do I keep using old CM10 kernel (gingerbread kernel)
Thanks in advance for the response! I'm gonna keep reading in the mean time
PS: I have a defy mb525 with red lense
jceballos said:
Hi! had my defy resting in a drawer for some time, I see there's a custom kernel now, if I want to flash de 11/2 nightly do I need to flash a different kernel or do I keep using old CM10 kernel (gingerbread kernel)
Thanks in advance for the response! I'm gonna keep reading in the mean time
PS: I have a defy mb525 with red lense
Click to expand...
Click to collapse
you can just flash the 11/2 nightly, it includes the custom kernel. after you flash, it should automatically use 2ndboot instead of the default 2ndinit to boot your phone.
syllogyking said:
you can just flash the 11/2 nightly, it includes the custom kernel. after you flash, it should automatically use 2ndboot instead of the default 2ndinit to boot your phone.
Click to expand...
Click to collapse
you are so right my friend, I flashed 11/2 nightly last night and gapps and that was it. Forgot to update my post to let everyone know. I was surprised that it wasn't even necessary to flash a battery fix!
Thanks a lot for your answer, rom is great so far.
syllogyking said:
why are you flashing froyo kernel separately? the cm10 zip includes kernel...also don't flash 24/9.
the 2nd boot builds are now much better, so flash 2/11
Click to expand...
Click to collapse
unfortunately that didn't solve it for me, still bootloop after 2/11
Zgabitzu said:
unfortunately that didn't solve it for me, still bootloop after 2/11
Click to expand...
Click to collapse
maybe you should try a clean install, I flashed cee deblur sbf, root with superoneclick, installed 2ndinit 2.3 and flashed 11/2 nightly and gapps for android 4.1.2 from goo.im
Keep in mind that I have a red lense defy, don't know if it could make a difference
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 :/
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
hiandro said:
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
Click to expand...
Click to collapse
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
skeevy420 said:
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
Click to expand...
Click to collapse
can u give me link to download latest CWM please.
hiandro said:
can u give me link to download latest CWM please.
Click to expand...
Click to collapse
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
skeevy420 said:
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
Click to expand...
Click to collapse
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
hiandro said:
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
Click to expand...
Click to collapse
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
skeevy420 said:
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
Click to expand...
Click to collapse
Yeah, i tried to restore backup using cm10 recovery and although it said cant restore .android.secure something like that(iam not quite sure) it restored system as well as data.
The thing is i like mokee os .its speed, clean and clear... ecetra but it is not jelly bean.can't we have a cm10 tweaked and modified for bravo.of course I love your PA jelly bean there are lots of tablet tweaks can you also add some other functions like in pimp my rom.
And thanks man for answering my queries
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