hi, what's about moto defy?
1-when you flashing your defy to SBF can you flash it back again to another SBF "is any condition"
2-does the Firmware's updating relate to your kernel version and lens color
3-when you installing new android (rom) "update.zip from SD card" can you install again another rom "is any condition"
thank you guys for you are giving me that opportunity
samhawk said:
hi, what's about moto defy?
1-when you flashing your defy to SBF can you flash it back again to another SBF "is any condition"
2-does the Firmware's updating relate to your kernel version and lens color
3-when you installing new android (rom) "update.zip from SD card" can you install again another rom "is any condition"
thank you guys for you are giving me that opportunity
Click to expand...
Click to collapse
1. When flashing a full SBF with RSD Lite you need to be careful about the bootloader version, some don't allow rooting or going back to older versions.
2. These are Android versions, and yes, Gingerbread has a newer kernel and only red lens works with it.
3. Well, you can go from one ROM to another but you need to wipe everything then (Data, Cache and Dalvik cache). If you go from a nightly to another (we're talking about the same ROM here) you need to wipe only Cache and Dalvik cache.
Trimis de pe Defy CM9
thank you your knowledge is good
i have defy, green lens an i'am now on android 2.2.2
*can i install Gingerbread "CM7"?
thank you again
samhawk said:
thank you your knowledge is good
i have defy, green lens an i'am now on android 2.2.2
*can i install Gingerbread "CM7"?
thank you again
Click to expand...
Click to collapse
Just follow some CM7 guides (lots of them out there)
, make sure you know what you're doing, make a nandroid backup
of current rom and you should be fine
Sure you can. You'll find the CM7 thread (started by quarx) in the Development section. Instructions are there too. I would've given you the direct link, but I'm posting this from my Defy .
From what I remember, since you're on 2.2, you need to root your phone, then install 2nd Init. After that, just copy the CM7 stable .zip and gapps on your SD card and flash them through the bootmenu, after wiping everything (you'll lose all data if it's not backed up with something like Titanium Backup).
LE: Yes, doing a nandroid backup before moving to Gingerbread is a good precaution measure.
Trimis de pe Defy CM9
thanks guys
what are the most stable and good rom "CM7/MIUI/CM9..."
what do you think by you personal experience
Stable: cm7
Beautiful: miui
Smooth and reliable: definitely NOT CM7
Sent from my MB526 using XDA
I was pleased with the stability of CM7.2 (version from 27 February by maniac).
Now I'm using CM9 (05.03 by quarx, Froyo kernel), and while it has a few bugs it can be used as a day to day ROM .
You can also flash CM7.2 and then multiboot with CM9, to test both.
Trimis de pe Defy CM9
thank you, i appreciate
so what do you think is the right one in this case ?
"i mean when you have a green lens and firmware 2.2.2"
Because you are new to this, you should go for CM7.2 (Android 2.3.7), it's stable and fast.
When you'll learn more about your phone you can flash CM9 (and this ROM is getting better and better with time).
Good luck.
Trimis de pe Defy CM9
ThANks mAn you'R genius.
i was asking for this stuff before and labsin answer me with "this" but i did not understand these steps "\\5. Choose Install zip from SD Card, select CM7..... .zip and let it finish.
(for CM7: Do 6 again with the gapps zip and the CM7kernel.zip)
6. select "Wipe Cache" then go to Advanced and select "Wipe Dalvik Cache". Reboot Now!//"
can you help me!!!
Well, I assume you want to install CM7.2, starting from Froyo.
Step 5 means that you need to flash CM7.zip (stable first, as it includes the CM7 kernel too, then you go with a nightly - I recommend the one from 27 of February by maniac).
Then you need to go back one step and select "choose zip from sd card" again, and select the gapps (the ones from 08.2011 for CM7, you'll find them in the main thread) to flash them too. This is like step 5.1.
Step 6 means you need to Wipe Cache, and after that go to Advanced and select Wipe Dalvik Cache. After these 2 wipes, you can reboot (don't worry, it'll take a around 8 minutes - this is happening for the first boot after wiping cache/Dalvik cache and flashing a new ROM).
But I recommend that you do a nandroid and then wipe everything before flashing CM7 (Data, Cache and Dalvik Cache) and after flashing CM7 and gapps, wipe again only Cache and Dalvik Cache to prevent errors.
thank you vap_66 you are the best
i just now complete the updating as you help me thanks again.
the CM7 latest nightly "CM72-20120304-NIGHTLY-Defy" is wonderful but the WiFi dose not work and the video-camera dose not work too
what do you think
Good, you made it .
I've read that the camera app had some issues in the latest nightlies, but you could try to clear data on it (from Manage Apps - I forgot what it was called in CM7). If not, flash another nightly. I was satisfied with a nightly from 27 February by maniac, you could try that.
What do you mean with "Wifi not working"?
Trimis de pe Defy CM9
thanks bro
"Wifi not working"***
*when i connect to WiFi, it's connecting "showing name,IP... and looks it's connected" but when i go to the browser or any thing has retaliation to WiFi connection, my defy says no connection, then i back to sitting>wireless...>WiFi settings>"i found my WiFi network are not connected and WiFi scanning!"
Hm, kinda weird. Did it work before with this wifi network? You could try to forget it and search for it again, this worked once for me. If not, I'm out of ideas - you could try another nightly as an ultimate solution.
Trimis de pe Defy CM9
vap_66 said:
Hm, kinda weird. Did it work before with this wifi network? You could try to forget it and search for it again, this worked once for me. If not, I'm out of ideas - you could try another nightly as an ultimate solution.
Trimis de pe Defy CM9
Click to expand...
Click to collapse
Is he on a nightly? I remember the nighties used to have like, massive wifi problems. That's why I used stable instead.
Sent from my MB526 using XDA
No wifi is weird with that nightly, Epsylon's 0304. I was using it from release until yesterday when I started using the latest kang cherrypick (real stable and reliable for past 30 hours) to do preliminary testing for a White Rabbit 1.4 port to the Bravo.
Btw, wifi and data tethering are the two most important things for me. The wifi problem may have been with how the roms now handle wifi when the screen is off, they disable it until the screen comes back on. Maybe it just didn't initialize? I'd never notice if it ever glitched like that because I use Wifi Keep Alive to keep my wifi on when the screen is off and I'm tethering. Just a thought anyways.
Good luck on your journey into the world of custom roms. Remember, take your time, read carefully, and always nandroid before a flash.
thanks guys i repeat all the steps again, and now it's fine videocam works and WiFi too
thanks again
Related
Hello dear xda community.
I own a Defy+ with 2.3.6 stock Kernel and want to switch to CM7. (Do I need another Kernel?)
Which build do you prefer, I can't decide between:
7.1.0-11
Quarks nightly
Epsylon3s nightly
maniacs nightly
Basically I'm just looking for a stable AOSP/blurfree ROM, so which one is the stablest up to now?
Which of the mentioned ROMS need/work with the battery/camera patches and are there different versions of these patches around? (here and here)
Am I right that there should be no more problems than battery and camera functionality up to now?
Thank you in advance
Edit: Another question I forgot:
In the title of the 7.1.0-11 it is written "Android 2.3.7". So does this mean even though the zip doesn't contain a Kernel it does contain 2.3.7? I couldn't find a 2.3.7 kernel for the Defy+ elsewhere.
Edit 2: I found an answer concerning whether to use 7.1.0-11:
The latest nightlys are stable, don't use 7.1.0-11
Click to expand...
Click to collapse
Though thats a tough statement whenever it comes to nightlys, I assume I will trust him here.
Like I wrote to you (by PM) before, I don't own a Defy+, but I'd say go on and try the latest Defy+ nightly which is from Quarx at this time: cm72-20120308-NIGHTLY-Defy+.zip md5 checksum: 8df5562b60ded2978a38eb9ac21bdc8e .
Make a nandroid backup of your system (custom recovery / advance / backup&restore / backup all) before installing it and then see how it goes from there...
If it really doesn't boot up, you have problems with battery not fully charging, camera or other things, you can find solutions or ask again - but at least you'll have a nand to fall back on... so no risk involved.
I haven't tried that specific March 8th Defy+ nightly yet, but I bet that it is probably at 1 or 2 small fixes close to perfection and you won't regret installing it I assure you.
Just be patient at first boot and wait a good 5-6 minutes before thinking being in a bootloop and do anything crazy..
God luck.
I tried cm72-20120308-NIGHTLY-Defy+.
Wifi is not working ..
and battery yet to check..
also camera prob..
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Let me recommend CM7 WhiteRabbit Edition 1.3! Pure awesomeness + Aroma touch based installer. This means you can customize your installation (e.g. defy+ battery fix, what apps you want installed, witch wifi driver, etc)!!
Install the PLUS edition for gingerbread kernel!
hafizca said:
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Click to expand...
Click to collapse
I was using the CM7 for Defy+ 140312 build and everything worked fine for me! Also played all sorts of games like Dead Space, Shadow Gun with ease!
you should try WUIU:http://forum.xda-developers.com/showthread.php?t=1161110
works great!!!!
The whiterabbit version problem
Hey
i did download the whiterabbitplus version as i has android 2.3.6 with kernel also 2.3.6
i rooted it as mentioned using the latest superclick
i theninstalled sndinit 2.0 and attempted to enter recovery but i got the triangle with the xclamation mark so i installed clockworkmod and it got me into recovery alright
here i format cache ,data wipe,factory reset etc and say install "zip from sd card "
auroma installer starts off fine works upto letting me select the options and everything ...just when it says "click next to start " when i do ..it just says
system/mount
error(system/mount) fail or something ...
and pretends its complete and asks for reboot
after reboot i discover no changes and it just acts like a facotry reset too place and i need to configure everything again
ive tried everything on the net ..please do help ..should i flash a lower version like froyo and try again ??
Maniacs builds are great, you should check them out.
Johnny_Queste said:
you should try WUIU:http://forum.xda-developers.com/showthread.php?t=1161110
works great!!!!
Click to expand...
Click to collapse
Sag1e said:
Maniacs builds are great, you should check them out.
Click to expand...
Click to collapse
Please, guys, stop the confusion. Both of those are Froyo only.
@athenus Have you managed to flash any ROM? From those you have mentioned...
CM7.1 - Froyo only
maniac's builds - Froyo only
Epsylon's builds - there are both Froyo and Gingerbread available
Quarx's builds - both Froyo and Gingerbread available <- this should be your choice. The latest Quarx's builds is awesome and you can find it here - http://quarx2k.ru/cm7-nightly-defy+/
P.S. Quarx is currently the only developer that actually owns a DEFY+.
If you are confused still, feel free to PM me, as I can't keep with all the threads I've posted in
hafizca said:
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Click to expand...
Click to collapse
I might be wrong, but the problems you have described having make me believe that you did not use and set the Defy Baseband Switcher app properly. Am I right/wrong?
Phone carriers around the world do not all use the same radio frequencies to receive/transmit phone signal and after any first install of cm7, you have to use that included app, give it root access, select the baseband that correspond to your location/carrier and reboot. Failing to do so causes bad signal eception, high battery drain and hot phones...
I hope that it was your problem because it will make it very simple to solve for you then.
EDIT: I believe that the baseband can now simply be changed under: Device settings/Baseband selection - no more dedicated app...
Installation failure of CM7 latest Joudan-plus
I hope someone can help me please . . .
Having rooted the phone successfully, and having followed all the relevant instructions (including installing first the various utilities - Titanium, 2ndInit, etc), to upgrade my Defy+ Build 4.5.1-134_DFP-231 with the latest CM7, I copied the CM7 zip to my Defy+ then installed it using 2ndInit - success.
Then, on the reboot, the phone just hangs at the M logo.
After doing the normal recovery, and trying to install again, these messages appear:
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Can anyone suggest what I should do next to recover the situation?
Installing CM7 on Defy+
Following my previous posting, I installed the nightly Jordan plus, from the night before - the only other one available.
That installed without any error message,
However, upon normal reboot, the phone hung at the M logo.
Any ideas please?
INSPEC said:
Following my previous posting, I installed the nightly Jordan plus, from the night before - the only other one available.
That installed without any error message,
However, upon normal reboot, the phone hung at the M logo.
Any ideas please?
Click to expand...
Click to collapse
Wipe data/cache?
Sent from my ATRIX HD using XDA Free mobile app
Installing CM7 on Defy+
Thanks for the response.
Yes, I did first wipe data and cache.
And have tried repeating the installation (including wiping).
Still hung at M logo.
INSPEC said:
Thanks for the response.
Yes, I did first wipe data and cache.
And have tried repeating the installation (including wiping).
Still hung at M logo.
Click to expand...
Click to collapse
Which recovery are you using? The normal one or the one designed for bigpart?
Sent from my ATRIX HD using XDA Free mobile app
Installing CM7 on Defy+
Thanks again for response.
I am using, from the xda posting,
2ndInit Recovery Installer v2.3 [Updated: 24-April-2012]http://forum.xda-developers.com/showthread.php?p=23465603
Installin CM on Defy+
This is an update on a previous posting of mine . . .
It read:
I hope someone can help me please . . .
Having rooted the phone successfully, and having followed all the relevant instructions (including installing first the various utilities - Titanium, 2ndInit, etc), to upgrade my Defy+ Build 4.5.1-134_DFP-231 with the latest CM7, I copied the CM7 zip to my Defy+ then installed it using 2ndInit - success.
Then, on the reboot, the phone just hangs at the M logo.
After doing the normal recovery, and trying to install again, these messages appear:
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I have subsequently performed:
Wipe data/Factory reset, then
Wipe cache.
and then trying to install three different version of CM - they are, CM 7 (both of the available Jordan Plus Nightlies), and then a CM 12 from another posting here in XDA.
All three resulted in the 'signature' problem. But the filename of all three files said they were "signed".
So can someone please explain . . . ?
---------- Post added at 02:25 AM ---------- Previous post was at 01:35 AM ----------
I have now discovered the enable/disable signature check . . .
Having disabled the signature check, and repeated all of the steps in my previous posting, and wiping the Dalvik cache, the phone still hangs at the M logo on reboot.
Any suggestions please?
Installing CM on Defy+
Following on . . .
Could this be a Bootloader problem?
I see references to similar symptoms being fixed by unlocking/relocking the Bootloader.
But my understanding, from the Cyanogen Mod website, is that CM looks after this automatically . . .
Hi, a noob here
I have a green lense (SOC) Defy with CM7.2.
I have tried a CM7.2 and CM9 multiboot, it worked really well apart from my unSIMlock. It didn't work for my CM9 then it messed up my CM7.2 unlock aswell, i had a nandroid backup though, so i restored.
Anyway, how can a multiboot CM7.2 as main ROM and have either Ms2Ginger or MIUI/WIUI v4 as my secondary, is it the same procedure, or is there some diferences. I really want a second ROM, but I don't want to brick my phone, even if it is nearly impossible to brick it.
I have a Samsung 16GB microSD class 10 if that helps.
Thanks
Will
so no-one will help me then
willster273 said:
Hi, a noob here
I have a green lense (SOC) Defy with CM7.2.
I have tried a CM7.2 and CM9 multiboot, it worked really well apart from my unSIMlock. It didn't work for my CM9 then it messed up my CM7.2 unlock aswell, i had a nandroid backup though, so i restored.
Anyway, how can a multiboot CM7.2 as main ROM and have either Ms2Ginger or MIUI/WIUI v4 as my secondary, is it the same procedure, or is there some diferences. I really want a second ROM, but I don't want to brick my phone, even if it is nearly impossible to brick it.
I have a Samsung 16GB microSD class 10 if that helps.
Thanks
Will
Click to expand...
Click to collapse
Hi, I have the same defy that you do.
You should be good to go, just install the latest multi boot zip, reboot, then either extract the fsimages zip from the first post into the multiboot folder on your sd, or even easier, download the latest multiboot manager, hit menu, then create vfs. Reboot, you'll see a new menu.... choose cwm recovery, select your vfs and install it. When you reboot just choose the one you want, no fuss no muss
Sent from my MB525 using Tapatalk 2
Allright.. i decided to start using a custom rom, which will be CM9. but because of soo mutch information on this website i dont fully understand anymore what to do, and because im still a noob, i cant post in the original thread of CM9.
I have a Red lens Motorola Defy MB525, found out with catlog that i got the bayer camera module , non branded, stock froyo.
Rooted my defy
nandroid backup with 2nd init , made a copy to my laptop to be completely save.
did backup the apps with titanium backup
also have the app battery calibration so i can fix my battery after the custom rom.
i will write the custom rom when my battery is on atleast 50 percent, so it will not die.
So what do i have to do next?
download the correct ROM, it will come as a .zip
copy it to your sdcard, reboot to 2nd init recovery,
factory reset, and wipe dalvik cache from advanced menu.
then in recovery choose install zip from sdcard, choose your ROM.zip, install,
reboot, it will take pretty long until it boots first time because system is rebuilding the dalvik. (~5min)
Wow , thats sounds way more simple then i can find on this site.
Ill try it tommorow night! any further suggestions?
Maybe you should try multiboot first just to be on the safe side.
what is multiboot and how can i do that?
Multiboot is basically the possibility to have two or more different ROMs (e.g. CM7 and CM9) installed at the same time and when you boot up you can choose which ROM you want to use. But it is a bit complicated and it wouldn't work with stock Froyo as one of the ROMs I think.
More suggestions? You should also download the latest gapps from http://goo.im/gapps and put the zip on your sd card as well. After wiping and installing the CM9 Nightly from sd go to install zip from sd again and choose the gapps .zip. After that you can reboot the system.
The gapps are the Google Apps (i.e. Play Store and some more) and without them you can't even setup your Google Account, download apps, use Gmail etc.
Ah thanks for that! downloaded it and saved it to my desktop for now.
Still need to figure out which rom i need to choose.. the epsylon?
regenboognl said:
Ah thanks for that! downloaded it and saved it to my desktop for now.
Still need to figure out which rom i need to choose.. the epsylon?
Click to expand...
Click to collapse
That would be good. Try it out and see if it suits your requirements..There are many ROM's for froyo kernel. You can try those and see which suits you best.
Happy Modding.
yeaaay! Thanks for all the great help, it worked perfect and was really easy to do!
Cant wait till all the apps are back on my phone from the backups that i made and then let the modding begin! haha
- running Epsylon CM9!
regenboognl said:
yeaaay! Thanks for all the great help, it worked perfect and was really easy to do!
Cant wait till all the apps are back on my phone from the backups that i made and then let the modding begin! haha
- running Epsylon CM9!
Click to expand...
Click to collapse
Congratulations, have fun with ICS on your Defy!
Questions go in the Q&A section
- So I was updating to Quarx's 5th Nov build (2ndboot) and in the middle the flash my phone turned off and decided not to start up. (The battery WAS NOT drained)
- I started with this guide in order to get it back to life:
http://forum.xda-developers.com/showthread.php?t=1807899(I used the exact same files, even the sbf. I live in India and I couldn't find India's sbf in this list: http://sbf.droid-developers.org/umts_jordan/list.php)
- Everything went as excepted and I was back on 2.2.2, so I tried to flash Quarx's build again. (I installed gapps, and cleared everything twice, thrice). However, the phone stuck on a bootloop:
red Motorola logo -> blue led -> greend led -> blank screen -> repeat.I cleared the cache's, factory reset, etc etc. No use.
- So i followed the original method again to get back to 2.2.2 and then flashed ICS from Cyano's website. It worked! So I tried again to flash a CM10 release, but this time a PRE-2ndboot build - 24th Sep.
It didn't work either. So JellyBean is the evident problem, but it doesn't make any sense, right?
- I started agin and tried to flash a different sbf, I got to this thread:http://forum.xda-developers.com/showthread.php?t=1093352 and tried the sbf provided (they claim it to be the one for SEA, including India). However, even after doing a factory reset from the stock recovery and flashing this sbf, I got a brick. The phone won't start whatsoever. No bootloader, no recovery - zilch. Dead.
- I again went back to my original method and got back to ICS...Flashed JB -> Same bootloop as before.
- Somethings I have noticed:
1. On flashing, the internal memory shrinks to only 128MB. I tried a factory reset from within the phone, from custom recovery and from the stock recovery. The memory was still 128MB with about 40MB free.
2. When I return to stock, the phone is somehow pre-rooted. On running superOneClick it shows that it;s already rooted but I continue nonetheless.
3. I think MAYBE the low internal storage might be at fault since JB Gappa require a lot of space.. I have tried it with minimal gapps too.
4. I have flashed every sbf available for Asian countries...but the only one that works is the one from the first link provided.
5. The only thing I can do right now is get to 2.2.2 or ICS...So if someone can help me out, that's my current status.
PS - I have been at it for 3 straight days, so yea, I have tried just about everything and read every thread regarding this. I even had to jump start by battery once as it ran out in the middle of a sbf flash.
There s a chance you didn't installed JB the right way. Also you ca install it without Gaaps. Does 2nd boot got enabled in Bootmenu? Did you flashed the kernel accordingly?
if you have bl4 try one of my fixed sbf with 2ndboot
ex. 28.11JB.Quarx+jellyX.kernel
than make a data and cache format fom bootmenu
bootmenu/ CPU settings/ system tools/ format data and cache to ext3
reboot
hve the link in my signature
I think you need bl. 4 from an 2.3.4 sbf for defy
In my country there was as an official update to GB
Users posted prblems with bootloader 3 and 7 @ quarx cm10 2ndboot roms
MB525 red lense
Hi,
You can take one more try (if you wanna ) to flash 12.09 JB build - it shall work
If so then flash Nordic retail 2.2.2 or WE retail (U3_3.4.2-177 or 179 from here)and try again 2ndboot builds (for some sbfs the last pre 2ndboot, 24/09 was the first not working)
Flash then 5/12 and jb gapps, wipe dalvik cache and cache after flashing.
Concerning 128 MB free memory - I suppose you are talking about data partition, not a system. Of course it is too small - the same as prerooted phone - try another sbf
Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.
vinu.shukl said:
Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.
Click to expand...
Click to collapse
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions
corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Click to expand...
Click to collapse
These are the sbf's I found pertaining tp your specifications:
http://i.imgur.com/muQdT.jpg
EDIT: But they are all in the DEFY-PLUS repository...can I flash them?
So I can use anyone of them?
Also, I don't know much about BL versions...So should I just download one of the above sbf's and flash it using RSD? Do I need a nandroid backup to go with it too?
The procedure I would follow would be:
1. Factory reset, clear cache's
2. Go into bootloader menu
3. Flash above sbf using RSD
4. Reboot ??
Should that suffice?
First: if you are red lense it is ok to flash BL6
If you are green lense, to have your camera working, you will need 2ndboot builds (CM9, 10 or 7)
You will probably need red lens battery fix to show correct percentage, no matter you have green or red lense then.
You can flash it even later, after flashing CM10 and gapps and checking how it works
I would choose Nordic retail
Sometimes you can have problems with rooting with SuperOneClick (version 2.3) - force close Motorola Portal before rooting and it shall work ok then
And nandroid backup is not very useful when changing BL version, at least you will not be able to restore all
I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)
vinu.shukl said:
I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)
Click to expand...
Click to collapse
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see
corrinti said:
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see
Click to expand...
Click to collapse
Okay!
Gonna flash it tonight...Finger's crossed. =D
UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?
vinu.shukl said:
UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?
Click to expand...
Click to collapse
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting
corrinti said:
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting
Click to expand...
Click to collapse
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.
vinu.shukl said:
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.
Click to expand...
Click to collapse
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life
corrinti said:
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life
Click to expand...
Click to collapse
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.
vinu.shukl said:
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.
Click to expand...
Click to collapse
The ramdisk zip is to be installed in a standard way, like any other zip, probably doesn't require wiping caches, but probably
I usually use zRam (18%) - I didn't notice any bigger battery drain.
KSM off
WiFi - change to never when screen is off - you can have wifi on all the time without special battery drain
And choose proper baseband for you region
And CPU settings are ok as above
Defy on BL6
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas
---------- Post added at 06:03 PM ---------- Previous post was at 05:48 PM ----------
corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions
Click to expand...
Click to collapse
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas
@Vycas
The problems might be several, unfortunately even hd problem, but try this:
- try different USB cable, different computer, different USB socket - the problem can arise when signal transmission is poor. Sometimes reinstalling of motorola drivers also helps
- if above does not help try Linux computer instead of Windows one
Regarding sbf - well, as you received error after each sbf flashing there could be a hope that you still may have BL4 (but also you may have BL6) - start your above mentioned trials with BL4 sbf, which will give you camera also with CM7
Hi
I have installed CM11 (4.4.2) on Defy and it is working fine except the battery.
This entailed installing TWRP
Earlier I had MIUI Pikachu edition.
Questions
1. How do I install or restore my MIUI backup again.
2. Also I would like to downgrade to CM 7/9 which is more stable
Any links or step by step suggestions would be appreciated
Thanks
Ninad
ninadb said:
Hi
I have installed CM11 (4.4.2) on Defy and it is working fine except the battery.
This entailed installing TWRP
Earlier I had MIUI Pikachu edition.
Questions
1. How do I install or restore my MIUI backup again.
2. Also I would like to downgrade to CM 7/9 which is more stable
Any links or step by step suggestions would be appreciated
Thanks
Ninad
Click to expand...
Click to collapse
please do not post questions in the development section
post moved to the Q&A
No reply for this? I Also want to chahge from CM11 to MIUI on Defy, but just flashing the zip in the TWRP does noting and the phone always start the CM11.
Thanks a lot!
evilinheaven said:
No reply for this? I Also want to chahge from CM11 to MIUI on Defy, but just flashing the zip in the TWRP does noting and the phone always start the CM11.
Thanks a lot!
Click to expand...
Click to collapse
Probably you need to flash sbf to get an old bootstrap.
Sent from my HTC One using Tapatalk
I wan to downgrade as well, preferrably w/o sbf. But I flashed so often by now, searching for the fastest way w/o: 1-sbf, 2-reroot, 3-custom recovery and 4-flashing cm7 would take more time, than the flashing process itself.
So that's what I'm gonna do. Hope it gets snappier then. CM11 with just about 9-10 apps (facebook, messenger, whatsapp, gmail, gcal, aero control, battery stats, es file explorer) is already torture for my defy.
erdnuesse said:
I wan to downgrade as well, preferrably w/o sbf. But I flashed so often by now, searching for the fastest way w/o: 1-sbf, 2-reroot, 3-custom recovery and 4-flashing cm7 would take more time, than the flashing process itself.
So that's what I'm gonna do. Hope it gets snappier then. CM11 with just about 9-10 apps (facebook, messenger, whatsapp, gmail, gcal, aero control, battery stats, es file explorer) is already torture for my defy.
Click to expand...
Click to collapse
I have an idea, and its a possibility for you. I have a Atrix 4G which also is on CM11, and like you guys on the Defy, has a bigpart mod. For us to downgrade, its flash an old recovery, boot to recovery, factory reset, wipe all partitions (system, data, cache, boot (that should be the ones you have too)), flash desired ROM/restore backup. Not sure if that will work for you, but its worth a shot. If it doesn't work, i'd try sbf'ing (someone posted an sbf lately if i remember correctly
Sent from my ATRIX HD using XDA Free mobile app
Unfortunately I don't know what sbf to take - it might be irrelevant, since i accidentally flashed to bl7 long ago and since I wanted to reroot again, twrp and cm7 it might not matter which one to flash. I am trying to speed things up a bit, and struggle with twrp atm, because safewipe.zip might no longer be safe (unable to enter twrp) or the version was not meant for my configuration.
Now i trimmed all part's and try amplifying services, but it's been a while since i tuned my defy.
OT: I switched to Moto G and E2 (but lost both ones - or they've been stolen) and now I want to reactivate my old pal before switching to anything new again. It's getting expensive...
So don't wait, maybe I'll get CM11 to work good enough again, but if not, I'll try to provide a checklist.
palmbeach05 said:
I have an idea, and its a possibility for you. I have a Atrix 4G which also is on CM11, and like you guys on the Defy, has a bigpart mod. For us to downgrade, its flash an old recovery, boot to recovery, factory reset, wipe all partitions (system, data, cache, boot (that should be the ones you have too)), flash desired ROM/restore backup. Not sure if that will work for you, but its worth a shot. If it doesn't work, i'd try sbf'ing (someone posted an sbf lately if i remember correctly
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse