Related
Hi all, :
Ive owned a defy since january, and after a lot of lurking here decided to take the plunge and have a play with it.
It was a stock unbranded uk defy with 2.51 blur rom, it rooted no problem with super one click, i then installed thi version of recovery : http://forum.xda-developers.com/showthread.php?t=875233
I then botted it into recovey and am now stuck in a bootloop.
I can access stock recovery (vol down and power) then touch bottom right of screen. I wiped cache and user data from here.
I can enter bootloader (vol up and power) and rsd lite can detect the phone.
My question is what is the easiest way to bring my phone back to life ? Im not sure if i need to flash sbf or rom.
Not to fussed about having the latest roms or mods, just a working phone before the battery gives out.
Thanks in advance, Sam
This happened to me a few days ago the way you should do it is download the 2.51 uk sbf file and flash it over using rsd lite and it should boot straight back Into the operating system and by the way how come that version did that to your phone I've installed recovery on 2 defys and they both worked
One more question did it boot up into recovery or not ?
No it didnt boot into recovery, just the boot loop. Any idea where i can get the uk sbf ? the link here seems to be dead
So you installed system recovery and then once again in the program installed it and then you clicked boot into recovery right ?
http://and-developers.com/sbf:defy
This website has all the sbfs your one should be the second on the list
RSD lite that one into your phone and it should be good to go
so.. is the usb debugging on?
when tap install recovery button, you should turn off usb debugging.
memz180 said:
So you installed system recovery and then once again in the program installed it and then you clicked boot into recovery right ?
http://and-developers.com/sbf:defy
This website has all the sbfs your one should be the second on the list
RSD lite that one into your phone and it should be good to go
Click to expand...
Click to collapse
mannn you save my life, i was looking for a stock rom from Latin America, and i got it from that link.
Thanks for the link memz180. Downloaded sbf and flashed sbf and phone is now working. Next question is what is the idiot proof way to install recovery ?
You installed the correct recovery just make sure you click into the program and install the system recovery within the program and then click on boot to recovery make sure i would make sure superuser is allowing it so check that out to and also as stated above turn off your debugging in development and then click on recovery see if it works.
Goodluck
Rerooted phone and reinstalled recovery, no problems this time. Thanks all for your help.
Sam
No problem here at xda we do our best to help our fellow android mates lol
Another Noob with an almost bricked Defy!
sammitch said:
Hi all, :
Ive owned a defy since january, and after a lot of lurking here decided to take the plunge and have a play with it.
It was a stock unbranded uk defy with 2.51 blur rom, it rooted no problem with super one click, i then installed thi version of recovery : http://forum.xda-developers.com/showthread.php?t=875233
I then botted it into recovey and am now stuck in a bootloop.
I can access stock recovery (vol down and power) then touch bottom right of screen. I wiped cache and user data from here.
I can enter bootloader (vol up and power) and rsd lite can detect the phone.
My question is what is the easiest way to bring my phone back to life ? Im not sure if i need to flash sbf or rom.
Not to fussed about having the latest roms or mods, just a working phone before the battery gives out.
Thanks in advance, Sam
Click to expand...
Click to collapse
I have the same problem on my T-mobile US branded Defy + when I try to flash the sbf file, on RSDlite It gives me this error
"Failed flashing process. Failed flashing process. Error processing flash file. (0x700F); phone conected"
What am I doing wrong? I tried RSDlite ver 4.9 and 5.0 to no avail! Please help! Thank you!
SOLVED!
NrikeCalderon said:
I have the same problem on my T-mobile US branded Defy + when I try to flash the sbf file, on RSDlite It gives me this error
"Failed flashing process. Failed flashing process. Error processing flash file. (0x700F); phone conected"
What am I doing wrong? I tried RSDlite ver 4.9 and 5.0 to no avail! Please help! Thank you!
Click to expand...
Click to collapse
So, I was using my laptop with W7 to flash my Defy, I tried RSD lite 4.9 and 5.0 and kept getting the error message. I decided to give my desktop with Vista a shot and installed RSD lite 4.9 and the motorola drivers; i don't know why but immediately after plugging the phone in it started flashing! Awesome! After that I rooted again and installed 2ndInit (Wich is awesome!).
I backed up and flashed CM7 from the custom recovery mode. Everything started working excellent until I decided to re install 2ndInit!!! BIG MISTAKE! Never do that! I nearly bricked my phone again and couldn't load into recovery mode anymore! I had to re flash JRDNEM_U3_2.51.1. After that I had to repeat the whole process with the exemption of reinstalling 2ndInit after CM7.
Since 2ndinit is already installed you don't need to re install even if you don't have the app in your tray.
I'm in the same boat, my phone is in a reboot loop, and I can't seem to flash it...
RSD Lite 4.9 on win7
Error:
Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected
/me bangs head against the wall...
read somewhere else it has to do with where RSD Lite is installed, on my win 7 32bit that was c:\Program Files\Motorola\RSD Lite...
uninstalled, reinstalled in c:\Motorola\RSD Lite and copied the sbf to that dir too... seems to be working... hope this helps someone else!
NrikeCalderon said:
So, I was using my laptop with W7 to flash my Defy, I tried RSD lite 4.9 and 5.0 and kept getting the error message. I decided to give my desktop with Vista a shot and installed RSD lite 4.9 and the motorola drivers; i don't know why but immediately after plugging the phone in it started flashing! Awesome! After that I rooted again and installed 2ndInit (Wich is awesome!).
I backed up and flashed CM7 from the custom recovery mode. Everything started working excellent until I decided to re install 2ndInit!!! BIG MISTAKE! Never do that! I nearly bricked my phone again and couldn't load into recovery mode anymore! I had to re flash JRDNEM_U3_2.51.1. After that I had to repeat the whole process with the exemption of reinstalling 2ndInit after CM7.
Since 2ndinit is already installed you don't need to re install even if you don't have the app in your tray.
Click to expand...
Click to collapse
Yer cm7 comes with it pre installed it would flash blue at bootup you should of seen it I think on the installation instruction it's written dont install 2ndinit
just rename the .sbf file to smaller name and try again
Hey guys,
so, a lot of my quetstions will be already posted, but i can´t find them all.
So i hope i annoy no one here ;-).
Ok, now to the important:
I have a SGS until 6 month. over the time i learnd a lot of android and i´m very lucky with them.
Then i heard from cyanogenmod. and all i read about it is great.
i have knowledges about root of linux an so of android.
So, during my research i have a lot of question before i flash my sgs:
- i found only one forum enty where i read i have to format all partitions.
So, how do i flash a sgs?
i have a modded boot rom with root and clockwork mod.
I tried a backup of the system.
the rom manager don´t show ne the cm7 mod for my device.
Do anyone know why? because the RC status?
When i get an error, how can i rollback my firmware with the backup?
Which pc software i need?
my plan ist to flash the sgs with the experimental version, no nightly build.
CWM makes al lot if IMG files. the cm7 zip has only one IMG.
So, i hope anyone can tell some or send my some nice links.
thanks a lot :-D
ravn
Use this
Boom, that's how it's done folks.
Sent from my I9000m running Cyanogen Mod Nightly
Hey,
thanks guys.
So, can anyone explain me how i can go back to the original rom if i got any probs or even i want?
So, i made a backup with Titanium Backup (premium user) and secondly with CWM.
So, i copied them to my PC.
CWM makes some IMG files. So, how can i rollback them to my device?
Also if i try to create a rom image with the rom manager the recovery manager makes a error.
:-D
So, i get by saving my rom the following error:
-- Installing package ...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Why do the rom manager want to install a package by making an backup?
PS: i have the rooted bootloader: PDA_XXJVK_Sbl.tar installed.
to revert back to you need to revert to a stock rom. using odin and a full PDA froyo will do the job.
Hey,
so u mean, i have to download the offical rom and install them over odin.
then i have to root them and install CWM and reverse the backup.
is that right?
ravn83 said:
Hey,
so u mean, i have to download the offical rom and install them over odin.
then i have to root them and install CWM and reverse the backup.
is that right?
Click to expand...
Click to collapse
yes.. that will be the proper way to do it.
Hi,
My phone detail --
MB526, have android 4.1.2 and have rom -CM-X MIG 2.02
I have two issues :-
1. my wifi disconnects after some time and i have to disable it for long time and then enable it to work ,so any way to solve it -on my other phone
there is no issue about wifi atall.
2.I been trying to install kitkat 4.4 on my defy plus but always fails to do in recovery with message like this:--
error in /sdcard/.....zip, installation aborted"
tried both recoveries but now on touch TWRP -- any idea ?
Thanks
vaibhavm said:
Hi,
My phone detail --
MB526, have android 4.1.2 and have rom -CM-X MIG 2.02
I have two issues :-
1. my wifi disconnects after some time and i have to disable it for long time and then enable it to work ,so any way to solve it -on my other phone
there is no issue about wifi atall.
2.I been trying to install kitkat 4.4 on my defy plus but always fails to do in recovery with message like this:--
error in /sdcard/.....zip, installation aborted"
tried both recoveries but now on touch TWRP -- any idea ?
Thanks
Click to expand...
Click to collapse
I tooo faced the same problem at the beginning with cm11 (cm-11-20140117-NIGHTLY-mb526) by quarx, though I was able to install cm11(cm-11-20131229-NIGHTLY-mb526) by quarx successfully.... Im a noob to this flashing stuff still managed and understood a bit of this procedure... I believe I read this some where on this forum that if you want to install ***cm11 (cm-11-20140117-NIGHTLY-mb526)*** then you need to go back to the custom rom first then from there you can install , though I'm not 100% Sure and afraid to do any experimentation with my Defy+.... As of now Im on
"Android 4.3.1"
Kernel 2.6.32.9-Aerokernel
10.2-20131030-NIGHTLY-mb526
I am facing almost the same problems as yours "Installation failed" as if there is a problem with the zip file which I'm sure of that isnt the case :/
Please somebody help the noobs...!!!
Thank you.
imdroid87 said:
I tooo faced the same problem at the beginning with cm11 (cm-11-20140117-NIGHTLY-mb526) by quarx, though I was able to install cm11(cm-11-20131229-NIGHTLY-mb526) by quarx successfully....
Thank you.
Click to expand...
Click to collapse
Did you update recovery?
Link for that is in OP of http://forum.xda-developers.com/showthread.php?t=2515036
becer said:
Did you update recovery?
Link for that is in OP of http://forum.xda-developers.com/showthread.php?t=2515036
Click to expand...
Click to collapse
Yes I did the recovery Update and then rebooted and then tried installing cm11 (cm-11-20140117-NIGHTLY-mb526) but unfortunately it failed "Aborted"
imdroid87 said:
Yes I did the recovery Update and then rebooted and then tried installing cm11 (cm-11-20140117-NIGHTLY-mb526) but unfortunately it failed "Aborted"
Click to expand...
Click to collapse
Try maybe installing from scratch (starting with original sbf).
I reinstalled Kitkat on my Defy+ tonight - sbf, rooted sbf, 2ndInit, cm-10-20131030, recovery update and then 140120.
becer said:
Try maybe installing from scratch (starting with original sbf).
I reinstalled Kitkat on my Defy+ tonight - sbf, rooted sbf, 2ndInit, cm-10-20131030, recovery update and then 140120.
Click to expand...
Click to collapse
Buddy "becer" can u please guide me step wise to go back to the Stock Rom then 2init what ever it is I dont understand a thing
I know what stock Rom is but don't know how to degrade to the stock rom from 4.3.1 and how to install this 2init thing
would be a great help if you could guide me through the procedure step wise
Thank You.
1. root with Framaroot http://forum.xda-developers.com/showthread.php?p=37508806
2. Install 2nd init http://forum.xda-developers.com/showthread.php?p=12837303
3. Update recovery with this http://forum.xda-developers.com/showthread.php?p=48501247
4. Install CM11
Sent from my MB526 using Tapatalk
cyrusct82 said:
1. root with Framaroot http://forum.xda-developers.com/showthread.php?p=37508806
2. Install 2nd init http://forum.xda-developers.com/showthread.php?p=12837303
3. Update recovery with this http://forum.xda-developers.com/showthread.php?p=48501247
4. Install CM11
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
Buddy Im already running cyanogenmod on my defy+ and in the second link what you gave for installing the 2ndinit Recovery it says:
DO NOT INSTALL THIS IF ARE YOU ALREADY RUNNING CYANOGENMOD. That ROM already has bootmenu pre-installed, and you'll probably end up having to flash an SBF file to recover your phone.
NOTE: You need ROOT installed on your Defy to use this application.
What should I do ???
I will try from start by using original sbf file using RSD and then CM11 and updating recovery after that Kitkat ,btw can you mention which ROM you tried because i tried these 2 earlier --> omni-4.4.2-20140117-mb526-HOMEMADE .zip and AOSPA 4.0+ PARANOIDANDROID [beta]
Kitkat 4.4.2 KOT49H android-4.4.2_r1.
Also can some1 help me with my wifi frequently disconnection problem too please .
vaibhavm said:
I will try from start by using original sbf file using RSD and then CM11 and updating recovery after that Kitkat ,btw can you mention which ROM you tried because i tried these 2 earlier --> omni-4.4.2-20140117-mb526-HOMEMADE .zip and AOSPA 4.0+ PARANOIDANDROID [beta]
Kitkat 4.4.2 KOT49H android-4.4.2_r1.
Also can some1 help me with my wifi frequently disconnection problem too please .
Click to expand...
Click to collapse
I tried this
Mokee
"MK43.1-jordanplus-201312040138-NIGHTLY"
with Gapps
gapps-jb+-20130730_defy-minimal
and
update-recovery
CM11 by Quarx
"cm-11-20131229-NIGHTLY-mb526"
with Gapps
1-16_GApps_Standard_4.4.2_signed
They both worked for me but unable to install the latest one.... I'm trying the method just mentioned by the senior member but unable to root again using framaroot as its showing me this error
"Half-Success :-/ ... system partition is read-only, use local.prop trick. Reboot your device and use adb to see if it run as root"
I don't know what to do now :silly:
imdroid87 said:
I tried this
Mokee
"MK43.1-jordanplus-201312040138-NIGHTLY"
with Gapps
gapps-jb+-20130730_defy-minimal
and
update-recovery
CM11 by Quarx
"cm-11-20131229-NIGHTLY-mb526"
with Gapps
1-16_GApps_Standard_4.4.2_signed
They both worked for me but unable to install the latest one.... I'm trying the method just mentioned by the senior member but unable to root again using framaroot as its showing me this error
"Half-Success :-/ ... system partition is read-only, use local.prop trick. Reboot your device and use adb to see if it run as root"
I don't know what to do now :silly:
Click to expand...
Click to collapse
Mine sbf is rooted alredy so maybe try it first then go to CM10 .
its DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
downloaded it earlier from here only.
I have tried Mokee, but direct return to Quarx compilation made big stability problems too. Solution was to flash with original rom, then rooted one, 2ndInint and Quarx cm10, then cm11.
As I had Android 2.3.6 (3.4.5.1 - 231), I used these roms - http://forum.xda-developers.com/showthread.php?t=1542956.
It is very important to wipe data and cache just after first, original flash - otherwise you will have infinite boot loop and cannot run phone.
Look at http://forum.xda-developers.com/showthread.php?t=966537 too.
becer said:
I have tried Mokee, but direct return to Quarx compilation made big stability problems too. Solution was to flash with original rom, then rooted one, 2ndInint and Quarx cm10, then cm11.
As I had Android 2.3.6 (3.4.5.1 - 231), I used these roms - http://forum.xda-developers.com/showthread.php?t=1542956.
It is very important to wipe data and cache just after first, original flash - otherwise you will have infinite boot loop and cannot run phone.
Look at http://forum.xda-developers.com/showthread.php?t=966537 too.
Click to expand...
Click to collapse
Im phone is f***** , what I did is install this framaroot and installed rootchecker..... I tried to do the rooting using "installsu" and then clicked Gilmo and it gave me this message:
“Half-Success :-/ … system partition is read-only, use local.prop trick. Reboot your device and use adb to see if it runs as root”
then I restarted my phone and check with root checker and found its saying its saying Root access successful and then I wondered which I suppose I shudnt have wondered :crying: to user framaroot and do the "unroot" and again restarted , and now after restart I tried to do the regular thing wipe cache ,Dalvik , Data and the phone is not even mounting them its sayin
E: Can't mount /cache/recovery/command etc
Im able to open the android 4.1.2 (Jb - quarx)
but not able to install a thing in my internal memory coz I messed up bad with the partition table bad:crying:
I tried to fix it through this
http://forum.xda-developers.com/showthread.php?t=1759558&highlight=status+0
but no luck :/
I been able to flash and run cm-10.2-20140120-NIGHTLY-mb526.zip thts-- android 4.3 ,so do factory reset and go here http://quarx2k.ru/roms/defy-cm10.2/ --get latest build .
my problem is only wifi disconnects frequently -seems on this working fine ,will check it for few days ,anyway 4.4 will still have bugs so better be on some lower version.
For the opening post: the first issue is a known bug in 4.4, I did not know it is wrong even in 4.1...
vaibhavm said:
I been able to flash and run cm-10.2-20140120-NIGHTLY-mb526.zip thts-- android 4.3 ,so do factory reset and go here http://quarx2k.ru/roms/defy-cm10.2/ --get latest build .
my problem is only wifi disconnects frequently -seems on this working fine ,will check it for few days ,anyway 4.4 will still have bugs so better be on some lower version.
Click to expand...
Click to collapse
Oooh in that case even if I can install the latest Cm11 by Quarx then I should not be doing it as the problem your saying about the wifi getting disconnecting frequently is not acceptable :silly:
anyways just fighting with my Defy+ as of now , Installing the Stock sbf on it as I bricked the phone
So the new Question arises what CM version is more stable or can I ask whose performance is Better in terms of speed.... As I don't mind with Features but I dont want Lags.... Previously I installed 4.2.1 I Suppose and installed the mininal gapps and was have around 240mb free of RAM...
is that good ???
Thank you for the responses buddies :fingers-crossed:
imdroid87 said:
Oooh in that case even if I can install the latest Cm11 by Quarx then I should not be doing it as the problem your saying about the wifi getting disconnecting frequently is not acceptable :silly:
anyways just fighting with my Defy+ as of now , Installing the Stock sbf on it as I bricked the phone
So the new Question arises what CM version is more stable or can I ask whose performance is Better in terms of speed.... As I don't mind with Features but I dont want Lags.... Previously I installed 4.2.1 I Suppose and installed the mininal gapps and was have around 240mb free of RAM...
is that good ???
Thank you for the responses buddies :fingers-crossed:
Click to expand...
Click to collapse
vaibhavm I have installed this 4.4.2 Android Panroid
http://forum.xda-developers.com/showthread.php?t=2576930
[AOSPA 4.4.2 KOT49H] [Beta] Defy(+) PARANOIDANDROID 4.0+ [18/01/2014]
Working awesome fast and seems stable until now and I have gone through some reviews about it on defy+ on that forum even they are giving it positive reviews..
Check it out for sure:good::fingers-crossed:
I want to install Jelly Bean on Motorola Defy+...
I had earlier installed it with this zip cm-10.2-20130917-NIGHTLY-mb526...
But since I tried to install kit kat on it which I m not able to....
So, I began from start
1. installed DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf than,
2. installed firmwaresbf to root it. Rooted Saw Superuser In Menu. Than,
3.insatlled CyanogenDefy Recovery v5.0.3.1-jordan recovery. than
4.Try to install cm-10.2-20130917-NIGHTLY-mb526. by going in custom recovery But now I got this Error
Installing Update...
E:Error in/sdcard/cm-10.2-20130917-NIGHTLY-mb526.zip
(Status 0)
Installation aborted.
5. Also want to install Team win recovery Project....
One More thing this is a same Zip from which I installed Jelly Bean on Defy+.... I haven't deleted it... so it Can't be corrupted I think so...
Please HELP.
Provide me your valuable assistance...
Tooooo many tutorials was posted on this subject. Is enough.
In the forum rules is stipulated that first search and if you NOT found anything then ask!
can u post a link of the forum that can explain.....
pgreed said:
Tooooo many tutorials was posted on this subject. Is enough.
In the forum rules is stipulated that first search and if you NOT found anything then ask!
Click to expand...
Click to collapse
can u post a link of the forum that can explain.....that will be very helpful
&
Thanks for Answering...
Pls Help....
it would've took you less time answering him than complaining.
Mate, I've had this very problem.
You need to flash an earlier version of cm. try cm10 or 10.1.
it doesnt work because you have an outdated recovery. flashing cm10 solves this.
Good luck!
edit: after you flash cm10 make sure to get the 20 oct version of cm10.2 as the 17 sept you tried to flash is not the latest
defynoob said:
it would've took you less time answering him than complaining.
Mate, I've had this very problem.
You need to flash an earlier version of cm. try cm10 or 10.1.
it doesnt work because you have an outdated recovery. flashing cm10 solves this.
Good luck!
edit: after you flash cm10 make sure to get the 20 oct version of cm10.2 as the 17 sept you tried to flash is not the latest
Click to expand...
Click to collapse
Not necessary. If you has follow my explanation (from other post) you've found that is another simplified method.
still Help Needed
pgreed said:
Not necessary. If you has follow my explanation (from other post) you've found that is another simplified method.
Click to expand...
Click to collapse
Try to install this with recovery but still getting same error cm-11-20131229-NIGHTLY-mb526.zip
E:Error in/sdcard/cm-10.2-20130917-NIGHTLY-mb526.zip
(Status 0)
Installation aborted.
Pls Help Me
no one there to HELP!
What happen is there no one who can provide any HELP to me...
As I want it much...
Pls Help Me...
thanks in advance..
I have the same problem now with my new Defy+.I had 2 Defys+ in past and just root and install 2init then instal .zip CM9 or CM10 and love it.Now I go to kill myself.From more than week I flash,install,reboot,reflash....and have no fully working Cm10.First I have no way to install newer than cm10.0!Any try with 10.1 or 10.2 is folow ERROR in the beginning and nothing more.My custom recovery now is CWM.Any try to update recovery or try with TWRP,or try dual recovery or,or...is going to boot loop or sot brick...Now Im on CM10/Android 4.1.2 and try to get telephony functions.Im in Bulgaria and before with previous Defys I use baseband switch to 342-145.Now just after install new ROM(CM10) telephony worked first couple of minutes,not more.After dialing it come to black screen or in normal incall screen but no voice from bot sides.I switch to other bands but nothing.It come to pissed me out.Please help
I go directly to CM11, it is much stable now.
Not able to install TWRP
Not able to install TWRP Tried by installing it from CyanogenDefy Recovery v5.0.3.1-jordan recovery and it says installed successfully from SD card but not able to boot in team win recovery project and therefore not able to install any CM version Yet
trying n getting nstalling Update...
E:Error in/sdcard/cm-10.2-20130917-NIGHTLY-mb526.zip or any other cm version
(Status 0)
Installation aborted.
Need help pls help me...:crying:
[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")
So, I tried to flash CM11 for the MB520 Bravo, found in this post:
http://forum.xda-developers.com/showthread.php?t=2515036
So I copy the ROM .zip to the SD card in my Bravo, and I reboot into CWM Recovery version 5.0.3.9, with the name "CyanogenDefy Recovery v5.0.3.9-jordan" on the top of the screen. This version of recovery came from josuearisty's one click tool for rooting and putting a recovery on the MB520 Bravo, which can be found here:
http://forum.xda-developers.com/showthread.php?t=1559109
I factory reset/clear cache like I know I am supposed to when flashing a custom ROM, but when I select the "Install zip from sd card" option and select the CM11 MB520 Nightly to flash, it gives me this:
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-11-20140407-NIGHTLY-mb520.zip
(Status 0)
Installation aborted.
So then as I read on further in the CM11 install page, it says this: "For CM10,10.1,10.2 < 07.11.13 users: To install KitKat, need update recovery. Do not forget reboot, after install recovery. http://defy.bytekiste.de/cm11-nightl...e-recovery.zip". The thread is for the DEFY+ according to the title, but since I see there's also a Bravo download link, I assume that this means that I should install this updated recovery as well, since I am running the stock rooted 2.2.1, which is in fact "less than" 10.x or 4.x. I select the same "Install zip from sd card" option, and the same Status 0 is presented to me.
Then I go and try putting on CM10.x first, because then according to the thread's instructions I won't have to install this updated recovery if I am running that currently. I find a link for CM10.2 for the Bravo here:
http://forum.xda-developers.com/showthread.php?t=1779324
I download it, do the same install method, and I STILL GET A STATUS 0 saying it is unable to flash the zip!
Now I've done some research, and I THINK the status 0 means the zip is not compatible with my phone. I could see that with the updated-recovery.zip, but I don't see why that is showing up for the ROM's themselves because they are in fact made for the mb520.
Can someone please tell me what I am doing wrong, and if possible post a set of step-by-step instructions as to how I can go installing CM11 on my MB520 Bravo? Thanks.
*BUMP*
UPDATE: I seemed to get around the Status 0 issue in CM10.2 so far. First, I went from 2.2.1 to CM9 4.0.4. Then, I went from CM9 to CM10.1 in quarx2k's "archive" folder on his website. This updated my recovery to TWRP 2.6.0.0. From this new TWRP, I was able to flash the latest 10.2 nightly CM rom. I will keep this posted on how things go, in case anyone out there is actually following this
*BUMP AGAIN, PROBLEM SOLVED*
I got CM11 finally running on the Bravo. Here's the steps I took to get it on there. Some of these steps may be unnecessary, but I'm just going to list EXACTLY what I did in case all of these steps really are necessary:
1) I started out with stock 2.2.1. I rooted it, and used josuearisty's tool for one click root and recovery just to put recovery on it.
2) I flashed a build of CM9 from quarx2k's website. Here is a direct link to download it. Flashing this ROM also updated my cwm recovery. HOWEVER, this new version of recovery had scrolling issues with the volume rocker, so I just rebooted and pressed the vol. down button at the blue flashing LED light to boot into the boot menu. From there, I select to go to recovery, but instead of selecting "Custom Recovery" I select "Stable Recovery". This takes me back to the older recovery I got with the one click tool.
3) I flashed one of quarx2k's builds of CM10.1, which you can get for yourself here. Doing this updated my recovery again. It went from CWM 5 to TWRP 2 (I believe it was 2.6.0.0).
4) I flashed a CM10.2 build for the bravo from quarx2k, which I got from here. This updated my recovery YET AGAIN, to TWRP 2.6.3.0.
5) From here, I was able to flash the update-recvery.zip that is mentioned in the CM11 topic. I don't think this was necessary, because when I then booted into recovery again after flashing the update-recovery.zip, the version number for TWRP still read 2.6.3.0, the exact same as last time. But I just did it anyway to be safe. Here is a direct download link to the update-recovery ZIP mentioned on quarx's CM11 thread.
6) FINALLY, I flash the CM11 nightly zip from quarx2k's website. I get an error, but this time it's not a status 0 error, this tells me that the ZIP is not compatible with my device.
7) I give myself a facepalm, and take 3 deep breaths. "All hope is lost..." I think to myself.
7.5) A GOOGLE SEARCH TELLS ME THAT ALL HOPE IS NOT LOST!!! (that's supposed to signal you to keep reading)
8) Turns out, there is a way to disable the device compatibility check. So what I did was copy the CM11 zip to my pc, and unzip all of its contents. I go to META-INF\com\google\android\, and add a .txt ending to the "updater-script" file, which allows me to open it with Notepad++. It is possible to edit this with plain old Notepad in Windows, but it doesn't format the code very neatly like Notepad++ does. If you open the file in Notepad and Notepad++ and compare them you will see what I mean. Anyway, the line of code that reads...
assert(getprop("ro.product.device") == "mb520" || getprop("ro.build.product") == "mb520" || abort("This package is for \"mb520\" devices; this is a \"" + getprop("ro.product.device") + "\"."); (ignore that winking face in the line of code, that is supposed to be a "; )" but without the space between them.)
... was the one I deleted from the updater-script file. This should be the first line of code. I save, exit Notepad++, and remove the .txt ending from the updater-script so that it returns to an unknown filetype. Now, I take the META-INF, system, and file_contexts files that came from the original CM11 ROM zip and I create a NEW ZIP with all of the NEW files and folders.
9) I reboot to TWRP with the ROM zip copied to my phone's SD card, and I flash the new, fixed ROM zip. "Installation completed."
10) My Bravo is rebooted, it boots up, and i get a "Welcome!" bubble in my brand-new homescreen in KitKat
11) I nearly cried. Seriously.
So looking back I think it was really the recovery that was the issue for the Status 0 problem, and the only real way to update the recovery and solve the Status 0 problem is by flashing all these ROMs in the order I mentioned, but that's as far as I know, there may be a better and quicker way to do this that I just don't know about.
So basically this thread turned into a how-to. I wanted to post the instructions here because on the CM11-for-the-Defy-and-Bravo topic did NOT have any instructions whatsoever for flashing the Bravo CM11 build on the Bravo. If anyone has questions about what I wrote, then you can certainly post them below and I'll respond to them as soon as I can, and I'll answer them to the best of my abilities.
Thanks for the Guide
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?
Gastnow said:
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?
Click to expand...
Click to collapse
I think you should upgrade to 2.2.1 to make sure the one-click tool works with it because I do not know if the one click root and recovery works with 2.1. Upgrade to 2.2.1 just to be safe.
Sent from my SAMSUNG-SGH-I847
Thanks for the guide
Appreciate the work. What gapps are you using.
Doesn't have much support
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.
ilikepcs said:
Appreciate the work. What gapps are you using.
Click to expand...
Click to collapse
ilikepcs said:
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.
Click to expand...
Click to collapse
The gapps for this KitKat ROM can be found here. This came from the 4.4 thread:
QUARX2K'S KITKAT GAPPS
I used this as a daily driver for a little bit, until an update (I believe was from April 10th) with the Android 3.0 kernel broke the Camera. Whenever you would try to open the camera it would say "Can't connect to Camera". I'm not sure if this issue was fixed since then, and I know the versions before this had the 2.x kernel which was fine with the camera. I lent my Bravo to a family member because their phone broke, so I can't really do anything with the phone because it is not in my possession.
Anyway, check back at this thread and the link that it gives to the Bravo version of 4.4 to keep up with the latest version. This thread does not give a change log for the BRAVO version, but I assume that it's basically the same as the main version that the majority of the thread is talking about:
ANDROID KITKAT FOR DEFY AND DEFY PLUS (ALSO FOR THE MOTOROLA BRAVO)
Help please
The procedure to install cm11 after October 1 is the same? Or did it change? @jasonmerc
Quarx on their website does not mention cm10 and cm10.1
Sent from my mb520 using XDA Free mobile app
@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus
oldschool63 said:
@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus
Click to expand...
Click to collapse
Its been forever since I've used my Bravo let alone CM11. From what I can remember the new CM11 was EXTREMELY FAST compared to other ROMs. The only issue was the camera.
Sent from my LG-D415 using XDA Free mobile app
can you create a backup of it because some of the downloads don't work i got cm 9 4.0.4 im 12 and i ran into
a problem on cm 10.1 i cannot download it or flash it thx