I am attempting to flash CM7 stable on my stock 2.3.5 fascinate, with CwM recovery ( 2.5.1 ). But I get this error- "assert failed: getprop(re.product.device)"
Anyone know what the problem is?
You need to use the CWM in the OP of the nightly thread.
http://forum.xda-developers.com/showthread.php?t=1190668
Its an attached file.
Also IMO the nightlies are better than the stable.
imo the cm7 skang by makelegs is better than all of them!
mentose457 said:
You need to use the CWM in the OP of the nightly thread.
http://forum.xda-developers.com/showthread.php?t=1190668
Its an attached file.
Also IMO the nightlies are better than the stable.
Click to expand...
Click to collapse
Thanks, cm7 is running great, except for one problem. I cannot install the google add ons. I flashed the add ons from the cm wiki ( I cleared catch before ), and it seemed to have flashed correctly but when I reboot there is nothing. I have fixed permissions via rom manager, but still no add ons. I am running the CWM from the link you provided.
StevaB793 said:
Thanks, cm7 is running great, except for one problem. I cannot install the google add ons. I flashed the add ons from the cm wiki ( I cleared catch before ), and it seemed to have flashed correctly but when I reboot there is nothing. I have fixed permissions via rom manager, but still no add ons. I am running the CWM from the link you provided.
Click to expand...
Click to collapse
I would try mounting /system (in cwm) before flashing gapps.
Sent from my SCH-I500 using Tapatalk
it says "error mounting /system", any other solution?
mentose457 said:
I would try mounting /system (in cwm) before flashing gapps.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Says "Error mounting /system", should I install another version of cwm?
StevaB793 said:
Says "Error mounting /system", should I install another version of cwm?
Click to expand...
Click to collapse
Try holding the power button > reboot recovery > flash this kernel in recovery.. http://androtransfer.com/tk-glitch/CM7kernels/Glitch 13.1/CM7Fascinate-Glitch-V13_1-REL.zip
That should update your recovery to the latest CWM. After that, reboot into recovery again, wipe cache/dalvik cache and flash the latest GAPPS for CM7. That should get you working.
Related
Hello,
I own a defy mb525 with CM7.2.0. I am not so happy with this version (bad 3g access; battery life very short)
So I decided to install the CM10.1.
On the develloper page I saw that the status has been updated on the 26.03. But if I look for my model (mb525), I can find only a version dated on the 120904.
Is there a newer version for the mb525 or is it only for the mb520 and mb526 ?
Regards
http://forum.xda-developers.com/showpost.php?p=34616788&postcount=1
--> FAQ2
It should work for both. Same as latest builds of CM10.
thubi said:
http://forum.xda-developers.com/showpost.php?p=34616788&postcount=1
--> FAQ2
It should work for both. Same as latest builds of CM10.
Click to expand...
Click to collapse
Sorry I was meaning the 4.1.2 so it should be the 10.0
Cid156 said:
Hello,
I own a defy mb525 with CM7.2.0. I am not so happy with this version (bad 3g access; battery life very short)
So I decided to install the CM10.1.
On the develloper page I saw that the status has been updated on the 26.03. But if I look for my model (mb525), I can find only a version dated on the 120904.
Is there a newer version for the mb525 or is it only for the mb520 and mb526 ?
Regards
Click to expand...
Click to collapse
2ndboot builds: they are one build for both mb525 &5 26 .... so you can download the 26.03 nightly build and update on your MB525 :good:
Cid156 said:
Hello,
I own a defy mb525 with CM7.2.0. I am not so happy with this version (bad 3g access; battery life very short)
So I decided to install the CM10.1.
On the develloper page I saw that the status has been updated on the 26.03. But if I look for my model (mb525), I can find only a version dated on the 120904.
Is there a newer version for the mb525 or is it only for the mb520 and mb526 ?
Regards
Click to expand...
Click to collapse
Yes, there is CM10 from Quarx. Your device can be either mb525 or mb526 with red lens or green lens. CM10.1 from the same person also can.
hi
I have a similar question I have MotoDefy 525 running 2.3.7 I want to install ([ROM][JB+][4.3.1] MokeeOS 43.1 Defy/Defy(+) Official) http://forum.xda-developers.com/showthread.php?t=2453395
but it needs TWRP I tried installing on my 2.3.7 but it dosent install I looked around the forms I read that I have to up date my android version.
being a newbi im a little worried about bricking
A little help
can some one give the steps in Newbi language on how to update my phone to MokeeOS 43.1 please.:fingers-crossed:
Super_Moto said:
hi
I have a similar question I have MotoDefy 525 running 2.3.7 I want to install ([ROM][JB+][4.3.1] MokeeOS 43.1 Defy/Defy(+) Official) http://forum.xda-developers.com/showthread.php?t=2453395
but it needs TWRP I tried installing on my 2.3.7 but it dosent install I looked around the forms I read that I have to up date my android version.
being a newbi im a little worried about bricking
A little help
can some one give the steps in Newbi language on how to update my phone to MokeeOS 43.1 please.:fingers-crossed:
Click to expand...
Click to collapse
First of all, none of you guys ever read the stickies. It is packed with good info.
Our phone has a locked bootloader, it is almost impossible to brick.
Download latest CM10 and then install.
Ive come across a newbi problem im on the link of the latest cm10 (http://forum.xda-developers.com/showthread.php?t=1768702) and the file I try to flash wont install it gets aborted, I searched the forms for other cm10 and same issue file gets aborted.
If possible to be directed to the file I need to flash to cm10
not easy being newbi these days :crying:
Motorola 525 green lens running 2.3.7
What error do you get?
Sent from my MB526 using Tapatalk
hotdog125 said:
What error do you get?
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
the error shows when I try to flash the .zip file _Install zip from sdcard_choose zip from sdcard I pic the file and it doesn't install it says aborted show me the yellow triangle symbol I was assuming im flashing the wrong file.
before I do an install I wipe data/factory reset and wipe cache partition
Super_Moto said:
the error shows when I try to flash the .zip file _Install zip from sdcard_choose zip from sdcard I pic the file and it doesn't install it says aborted show me the yellow triangle symbol I was assuming im flashing the wrong file.
before I do an install I wipe data/factory reset and wipe cache partition
Click to expand...
Click to collapse
You are trying to flash through stock recovery. Install through custom recovery.
hotdog125 said:
You are trying to flash through stock recovery. Install through custom recovery.
Click to expand...
Click to collapse
I tried that and im also giving me (installation aborted) I used file cm-10-20130918-NIGHTLY-mb526 but no luck
Super_Moto said:
I tried that and im also giving me (installation aborted) I used file cm-10-20130918-NIGHTLY-mb526 but no luck
Click to expand...
Click to collapse
The file is ok, i've installed it on my defy
MikBre said:
The file is ok, i've installed it on my defy
Click to expand...
Click to collapse
Im clue less what im doing wrong I looked on u tube on installing jelly bean im following the same steps but Im getting (file aborted) when I try flashing the file
what r the steps u take on installing the file ?
At first I tried: Reboot in _Recovery _Install zip from sdcard_choose zip from sdcard_pick the the file _yes install
it starts by saying
Finding update package...
Opening update package...
E:Can't open /sdcard/cm-10-20130918-NIGHTLY-mb526.zip
(bad)
Installation aborted.
2nd I tried
Reboot in Bootmenu
Recovery _ Custom Recovery etc ..etc ..
and get the same message
Finding update package...
Opening update package...
E:Can't open /sdcard/cm-10-20130918-NIGHTLY-mb526.zip
(bad)
Installation aborted.
always did the factory rest and wiping during both process
Super_Moto said:
Finding update package...
Opening update package...
E:Can't open /sdcard/cm-10-20130918-NIGHTLY-mb526.zip
(bad)
Installation aborted.
Click to expand...
Click to collapse
just to be sure, your phone is not connected to a computer when you did the flash, right?
jh20 said:
just to be sure, your phone is not connected to a computer when you did the flash, right?
Click to expand...
Click to collapse
yes phone is disconnected from computer,I had no issues installing cm7
My is CMRecovery v5.0.3.2-jordan
and Bootmenu <v1.1.1> could these be the problem some thing needs to be updated ?
Super_Moto said:
what r the steps u take on installing the file ?
Click to expand...
Click to collapse
If you want a video guide look at the Youtube channel of locslikes.
Therre is a guide call "MOTOROLA DEFY How To Install ClockWorkMod and Cyanogenmod 10 Jelly Bean Android"
MikBre said:
If you want a video guide look at the Youtube channel of locslikes.
Therre is a guide call "MOTOROLA DEFY How To Install ClockWorkMod and Cyanogenmod 10 Jelly Bean Android"
Click to expand...
Click to collapse
Im just guessing.... that my bootmenu seems to be out of date possible being the reason that jellybean wont install,
bootmenu is up to 2ndInit Recovery v2.3 can this file be installed over v1.1.1 ?
Super_Moto said:
Im just guessing.... that my bootmenu seems to be out of date possible being the reason that jellybean wont install,
bootmenu is up to 2ndInit Recovery v2.3 can this file be installed over v1.1.1 ?
Click to expand...
Click to collapse
out of curiousity, i restored my mb525 back to cm7 nightly 20111201 nandroid, which has cwm v5.0.3.2. i did not check the bootmenu version but it should be the same as yours. then, after formatting system/cache partitions, i flashed cm-10-20130918-nightly-mb526.zip, and it worked.
so i don't really know what's wrong with your phone, but i have a couple of suggestions for you to try. not that there's any logical explanations but try it anyway:
1. according to the error messages, you have the cm10 rom in the root folder of the sdcard. try creating a sub-folder called cm10 and copy the cm10 rom and the minimal gapps into it.
2. download the defy_fullwipe_ext4.zip and defy_fullwipe_ext3.zip ( for later use, when you want to revert back your rom) from here and put them in cm10 folder as well:
http://forum.xda-developers.com/showthread.php?t=1818520
3. reboot into recovery but don't do any format or wipe. instead flash the file defy_fullwipe_ext4.zip and this will format your partitions into the ext4 file system.
4. then flash the cm10 rom. if it installs sucessfully, then without any further wiping,nor flashing the minimal gapps, reboot the phone. (note that the os will reboot once more in the middle of booting up, seemingly having a bootloop problem. don't worry it's meant to do that, unless it rebooted more than once)
5. if it boots up sucessfully, do some basic set up first before rebooting back into recovery to flash the minimal gapps.
alternatively you could try flashing cm9.1 (ext3) to get a newer bootmenu and cwm versions before flashing cm10. no need to flash any gapps, just wipe system/cache partitions and flash the cm9.1 rom by itself. reboot into cm9.1, do basic set up. once it's ready reboot into recovery and do the above steps, starting from step 3, to flash cm10.
good luck.....
edit: did you get your cm10 rom from here:
http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/
jh20 said:
out of curiousity, i restored my mb525 back to cm7 nightly 20111201 nandroid, which has cwm v5.0.3.2. i did not check the bootmenu version but it should be the same as yours. then, after formatting system/cache partitions, i flashed cm-10-20130918-nightly-mb526.zip, and it worked.
so i don't really know what's wrong with your phone, but i have a couple of suggestions for you to try. not that there's any logical explanations but try it anyway:
1. according to the error messages, you have the cm10 rom in the root folder of the sdcard. try creating a sub-folder called cm10 and copy the cm10 rom and the minimal gapps into it.
2. download the defy_fullwipe_ext4.zip and defy_fullwipe_ext3.zip ( for later use, when you want to revert back your rom) from here and put them in cm10 folder as well:
http://forum.xda-developers.com/showthread.php?t=1818520
3. reboot into recovery but don't do any format or wipe. instead flash the file defy_fullwipe_ext4.zip and this will format your partitions into the ext4 file system.
4. then flash the cm10 rom. if it installs sucessfully, then without any further wiping,nor flashing the minimal gapps, reboot the phone. (note that the os will reboot once more in the middle of booting up, seemingly having a bootloop problem. don't worry it's meant to do that, unless it rebooted more than once)
5. if it boots up sucessfully, do some basic set up first before rebooting back into recovery to flash the minimal gapps.
alternatively you could try flashing cm9.1 (ext3) to get a newer bootmenu and cwm versions before flashing cm10. no need to flash any gapps, just wipe system/cache partitions and flash the cm9.1 rom by itself. reboot into cm9.1, do basic set up. once it's ready reboot into recovery and do the above steps, starting from step 3, to flash cm10.
good luck.....
edit: did you get your cm10 rom from here:
http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/
Click to expand...
Click to collapse
I did try using that link but the files still would abort when flashing, also tried http://d-h.st/users/Quarx files it did the same thing
I followed your instruction but decided to goto cm 9 first I flashed the (ext3) file it installed and cm9.1 installed also installed twrp with no issues but when I was going through cm9 and its functions I couldent go on line a popup message (Unfortunately, brower has stopped) also I wasn't able to log on google play a pop up message (Unfortunately,com. google android.gb has stopped). so I got fed up and decided to goto cm10.1 so I first flashed with ext4.zip it installed and then tried to flash 10.1 file once again the file wouldn't install it gave me aborted file message again. I had no choice to reboot and I had to reinstall the factory file(brick). I am now back to where I started :silly: cm7 2.3.7 its been a hell of a weekend ........... ill give it another shot soon :fingers-crossed:
I have CWM as my recovery and PA on the device.
I got a message today saying a new PA is out and grabbed the zip from goo manager.
Now I understand with goo manager you need a openscript recovery to use that to update though it appears CWM recovery doesn't use that but TWP does.
In CM10 you go to the settings and update from the OTA section in the about tab.
PA doesn't use those OTA updates it seems when CM does.
I would still be using CM but was getting a lot of crashes on M3 so I decided to try a few roms and currently running PA.
So what's the best way to update can I just flash the rom over the top of the current system without formatting first?
Thanks
drguild said:
I have CWM as my recovery and PA on the device.
I got a message today saying a new PA is out and grabbed the zip from goo manager.
Now I understand with goo manager you need a openscript recovery to use that to update though it appears CWM recovery doesn't use that but TWP does.
In CM10 you go to the settings and update from the OTA section in the about tab.
PA doesn't use those OTA updates it seems when CM does.
I would still be using CM but was getting a lot of crashes on M3 so I decided to try a few roms and currently running PA.
So what's the best way to update can I just flash the rom over the top of the current system without formatting first?
Thanks
Click to expand...
Click to collapse
Move the zip containing the update to /sdcard (your root documents directory, where all your files are stored- ANdroid, Data, DCIM, Downloads, etc), reboot to CWM, flash zip, select zip and go. That should be all you have to do. :good:
It worked fine for me using CWM and the usual method to update (recovery->install zip->select from SD). The only problem I'm having is a DPI issue in the launcher. Make sure to install the newest gapps as well and clear the cache.
Sent from my Nexus 10
purmou said:
It worked fine for me using CWM and the usual method to update (recovery->install zip->select from SD). The only problem I'm having is a DPI issue in the launcher. Make sure to install the newest gapps as well and clear the cache.
Sent from my Nexus 10
Click to expand...
Click to collapse
Cheers guys I read you can just flash over the top in CWM but just wanted to confirm it.
drguild said:
Cheers guys I read you can just flash over the top in CWM but just wanted to confirm it.
Click to expand...
Click to collapse
Correct.
I rooted my phone with the nexus tool kit (which installed clockworkmod. Then i used ROM Manager to flash cyanogenmod RC 4.. I have tried this a couple of times and my pone doesnt boot up from the cyanogenmod logo screen. Sometimes, it gives me an error that it failed to to launch setup.. Please help.
Right now, my phone is running the unlocked and rooted running the stock android 4.2.2
try to wipe the partitions from the recovery...factory reset it.....then flash cm 10.1 and g-apps.....from the recovery itself
am running rc4....perfectly fine...
djpry said:
try to wipe the partitions from the recovery...factory reset it.....then flash cm 10.1 and g-apps.....from the recovery itself
am running rc4....perfectly fine...
Click to expand...
Click to collapse
I tired that aswell... but it gives me an error which says "unfortunately, the process com.google.process.gapps has stopped"..
what do you recommend?
riki2 said:
I rooted my phone with the nexus tool kit (which installed clockworkmod. Then i used ROM Manager to flash cyanogenmod RC 4.. I have tried this a couple of times and my pone doesnt boot up from the cyanogenmod logo screen. Sometimes, it gives me an error that it failed to to launch setup.. Please help.
Right now, my phone is running the unlocked and rooted running the stock android 4.2.2
Click to expand...
Click to collapse
If you have CWM or TWRP recovery installed do NOT use Rom Manager and uninstall it. It conflicts with CWM and causes errors. Download CM from here http://get.cm/?device=mako&type= the first time, after that you can update and flash from within the rom itself in settings/ about the phone.
riki2 said:
I tired that aswell... but it gives me an error which says "unfortunately, the process com.google.process.gapps has stopped"..
what do you recommend?
Click to expand...
Click to collapse
the gapps version i have download is 4.1.2... if thats wrong. can you give me a link to download gapps from?
That's wrong gasps. Go to goo.im and download 4.2.2 gapps
Sent from my Nexus 4 using xda app-developers app
riki2 said:
the gapps version i have download is 4.1.2... if thats wrong. can you give me a link to download gapps from?
Click to expand...
Click to collapse
Dude read up first before you kill your phone, why the hell are you flashing all kind of stuff if you have absolutely no idea what you are doing?
gee2012 said:
Dude read up first before you kill your phone, why the hell are you flashing all kind of stuff if you have absolutely no idea what you are doing?
Click to expand...
Click to collapse
rom manager downloaded the gapps.. Can you recommend a source i could read? thanks
riki2 said:
rom manager downloaded the gapps.. Can you recommend a source i could read? thanks
Click to expand...
Click to collapse
Here
http://goo.im/gapps
Download gapps 4.2.2
Sent from my Nexus 4 using xda app-developers app
riki2 said:
rom manager downloaded the gapps.. Can you recommend a source i could read? thanks
Click to expand...
Click to collapse
Oke, i help you this once:
1. Uninstall Rom Manager, it serves no purpous anymore
2. Download RC4 from here http://get.cm/?device=mako&type=
3. Download Gapps from here http://goo.im/gapps/gapps-jb-20130301-signed.zip
4. Go in recovery and wipe data, cache, dalvik cache and format system.
5. Flash CM rom and straight after that Gapps
6. Reboot and you`re done.
riki2 said:
I tired that aswell... but it gives me an error which says "unfortunately, the process com.google.process.gapps has stopped"..
what do you recommend?
Click to expand...
Click to collapse
1. uninstall rom manager....Not really required
2. factory reset your current rom
3.go to Cmw or any other recovery.
4.erase cache,d cache and system
5.fresh install....cm 10.1 rc4
6.flash gapps for jb
reboot from recovery
njoy cm goodness
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!
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.