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?
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!
I tried to install TWRP from CWM. The process goes down, it tells me to reboot recovery. I rebooted, and still, i have CWM. What should i do?
defy red lens cm9 epsylon
if youre not opposed to starting over with a fresh sbf, then do just that. this time stick to twrp. seems to be doing much better than CWM
undyingvisage58 said:
if youre not opposed to starting over with a fresh sbf, then do just that. this time stick to twrp. seems to be doing much better than CWM
Click to expand...
Click to collapse
but i can't install twrp. i just does not replace cwm, and from froyo or éclair i cant install it with goomanager. from cm9 goomanager tells my device is not supported
gyorgyszemok said:
but i can't install twrp. i just does not replace cwm, and from froyo or éclair i cant install it with goomanager. from cm9 goomanager tells my device is not supported
Click to expand...
Click to collapse
my next advice is to learn how to manage your own roms without goomanager. for the most part you can read the tutorials on the defy wiki page to install "2ndInit Recovery". then use the 2ndinit recovery to install twrp. from there you install 10.2/4.3 and enjoy. just make sure you know well how to do sbf flashes just in case you goof and softbrick your phone in the process.
plus you should be able to install goo manager once youve settled in with twrp.
undyingvisage58 said:
my next advice is to learn how to manage your own roms without goomanager. for the most part you can read the tutorials on the defy wiki page to install "2ndInit Recovery". then use the 2ndinit recovery to install twrp. from there you install 10.2/4.3 and enjoy. just make sure you know well how to do sbf flashes just in case you goof and softbrick your phone in the process.
plus you should be able to install goo manager once youve settled in with twrp.
Click to expand...
Click to collapse
You misunderstood me maybe. I never used Goomanager. The first time I did was like 2 days ago when I found out I can't install CM10.x with CWM v5, but v6 or TWRP, and tried to install TWRP from it. It didn't work. Also, the TWRP flashable zip won't install from CWM. I mean... It says it's ok and reboot recovery but nothing. Gwah I know all about sbf flashes in case of softbrick and all...
edit: im very, VERY familiar with cwm... never used any apk to manage my roms just 2ndinit to install.
gyorgyszemok said:
You misunderstood me maybe. I never used Goomanager. The first time I did was like 2 days ago when I found out I can't install CM10.x with CWM v5, but v6 or TWRP, and tried to install TWRP from it. It didn't work. Also, the TWRP flashable zip won't install from CWM. I mean... It says it's ok and reboot recovery but nothing. Gwah I know all about sbf flashes in case of softbrick and all...
edit: im very, VERY familiar with cwm... never used any apk to manage my roms just 2ndinit to install.
Click to expand...
Click to collapse
theres nothing else i can help you with then. all i can say is start from sbf flash and stay away from cm 10 2ndboot
Maybe not enough memory?
Sent from my MB526 using xda app-developers app
undyingvisage58 said:
theres nothing else i can help you with then. all i can say is start from sbf flash and stay away from cm 10 2ndboot
Click to expand...
Click to collapse
yeah... but i'd like to try it at least...
hotdog125 said:
Maybe not enough memory?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
I don't think so. Something is very fishy about my phone. very-VERY strange... I can't install cm10.x cuz' of no update-binary support in cwm v5, and i can't find a way to make TWRP work, nor can I find any CWM v6 install methods... srsly WUT EVERY OTHER stuff works as intended. everything. all roms before jelly bean. i need to make twrp work or a cwm v6 installation.
gyorgyszemok said:
yeah... but i'd like to try it at least...
I don't think so. Something is very fishy about my phone. very-VERY strange... I can't install cm10.x cuz' of no update-binary support in cwm v5, and i can't find a way to make TWRP work, nor can I find any CWM v6 install methods... srsly WUT EVERY OTHER stuff works as intended. everything. all roms before jelly bean. i need to make twrp work or a cwm v6 installation.
Click to expand...
Click to collapse
Only CM10.2 needs the new CWMv6. CM10 and CM10.1 should work.
Your phone seems to trolling you:laugh:. But seriously, as a last resort I would flash DFP sbf. Gingerbread isn't half bad (especially with MS2Ginger, which is really stable and is compatible with Green Lens too).
hotdog125 said:
Only CM10.2 needs the new CWMv6. CM10 and CM10.1 should work.
Your phone seems to trolling you:laugh:. But seriously, as a last resort I would flash DFP sbf. Gingerbread isn't half bad (especially with MS2Ginger, which is really stable and is compatible with Green Lens too).
Click to expand...
Click to collapse
Well then it's trolling me 'cuz CM10 gives the same status 7 error. It IS trolling me. But i'm scared of flashing a DFP sbf. What if things go wrong? I won't be able to rollback then.
You can try to use twrp on gb roms by replacing the boot menu folder in system by that of cm10 or later. Try once with a clean folder, and once by copying over the existing files.
As for defy plus sbf, if you have a green lens, camera won't work on any gb except ms2ginger. In addition a battery patch must be flashed after every rom for full charging. For red lens only battery patch has to be flashed.
None of the above applies to cm10 and later.
Sent from my MB526 using Tapatalk 2
gyorgyszemok said:
Well then it's trolling me 'cuz CM10 gives the same status 7 error. It IS trolling me. But i'm scared of flashing a DFP sbf. What if things go wrong? I won't be able to rollback then.
Click to expand...
Click to collapse
If things go wrong, try a different SBF.
thekguy said:
You can try to use twrp on gb roms by replacing the boot menu folder in system by that of cm10 or later. Try once with a clean folder, and once by copying over the existing files.
As for defy plus sbf, if you have a green lens, camera won't work on any gb except ms2ginger. In addition a battery patch must be flashed after every rom for full charging. For red lens only battery patch has to be flashed.
None of the above applies to cm10 and later.
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
I tried replacing the bootmenu folder with different apps, but all got some "Operation failed!" or "Error with files" in itself, so I also tried to replace some of the files 1 by 1, they still failed. So that could be the reason why the zip won't flash properly... Maybe some safety option somewhere in CM9??? My phone can't seem to handle the recovery zips, only the 2ndinit apk. Very strange!
That must be done from recovery. I recall helping someone replace the recovery using a flashable zip because only a legacy recovery worked for him. I think it was zer0-gravity. Check my posts on that.
Replacing the recovery files with twrp ones in the zip I had made on that thread should with hopefully.
Also, your problems indicate file system errors, and I'll advise you to flash a different(higher) sbf, since that has in the past worked out well, for me and others. Beyond this point I'm out of ideas.
Sent from my MB526 using Tapatalk 2
thekguy said:
That must be done from recovery. I recall helping someone replace the recovery using a flashable zip because only a legacy recovery worked for him. I think it was zer0-gravity. Check my posts on that
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
another fast question. i recover my phone using the JORDN_U3_97.21.51 method, after that i have to do a root, nandroid, then instantly flash a fixed sbf (firmware.sbf...). its cuz i got the phone 2nd hand, and he f-ed up smth upgrading to gingerbread or so... can it be the root of my problem?
http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143
Why do you need a fixed sbf? After rooting try directly 2ndinit. Don't restore nandroid. Also, root using framaroot since its much easier and faster. You can jump from 2.1 to
2ndboot directly.
Sent from my MB526 using Tapatalk 2
thekguy said:
Why do you need a fixed sbf? After rooting try directly 2ndinit
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Cuz' my mb525 got flashed a GB sbf accidentally, from which you can't downgrade (by its user before me), and you can only recover it from éclair via the method i linked. other sbf's wont work
Ok, so when you flash the first sbf, and root, what stops you from directly using 2ndboot at that point
Sent from my MB526 using Tapatalk 2
thekguy said:
Ok, so when you flash the first sbf, and root, what stops you from directly using 2ndboot at that point
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
It just won't install, with status 0 or 7.
But right now I grew tired of this problem and i will flash a DFP 231.sbf from here:
http://forum.xda-developers.com/showthread.php?t=1542956
I will follow these steps. Can i do that? (MB525 Red Lens)
edit: 4.5.1-134 DFP-231 Retail.en.EU CEE
Yes. Flash that and root with framaroot.
Don't follow the guide for rooting, just flash dfp 231 , if it hangs on moto wipe data and cache from stock, and use framaroot.
Depending on eu or cee you've flashed, you may require a kernel to boot successfully with 2ndboot roms(otherwise you will just hang even after waiting a lot). It can be found in the defy custom kernel thread in General
Best of luck
Sent from my MB526 using Tapatalk 2
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.