Related
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
I defy the red lens, and when trying to flash GB Kernel regardless of where in March, is suspended on the Google logo ... what's the problem? I do wipe data / cache and cache dvlk but it did not give
Which build are you using? you should install defy + builds (from quarx) and can use gb kernel. If you had installed regular defy builds for froyo kernel, and on top of it if you flash GB kernel them you will be stuck on boot logo.
Sent from my MB526 using XDA App
Nishanu said:
I defy the red lens, and when trying to flash GB Kernel regardless of where in March, is suspended on the Google logo ... what's the problem? I do wipe data / cache and cache dvlk but it did not give
Click to expand...
Click to collapse
same here, i originally got my phone (2nd hand) running on ecclair. i was able to install cm7 2.3.7. i tried cm9 and did the necessary steps (e.g. wiping cache, data, and delvik) but got stuck on the google boot page... T_T
After a night of combining found a solution that worked for me. So I had to change foryo karnel the to GB.
Well, first wipe 3x ((wipe data, cache, Dalvik)) then installed CM9_Kernel-signed.zip. Then install the package CM9-nightly-120 330-Defy +. Zip then upload GAPPS, wipe Dalvik, restart and it works. Be sure to install patch for the battery !
haha! i kinda figured out what went wrong on my end too. i tried to install cm9 with gb based kernel. im running on froyo T_T... i know what to do now once i get home from work...
I have just installed cyanogenmod 9 on my defy from given link. it is just showing startup logo not going forward. after waiting long time same cyanogenmod 9 logo showing.
Link:
http://forum.xda-developers.com/show....php?t=1432100
Please be more specific on what build you are trying to install and what kind of defy you have (defy red lens, defy green lens, defy+).
Defy red lens and defy+ are no different, just that the latter has different battery and capacity. Green lens SOC defy is different and can only use froyo kernel builds (GB kernel builds have camera problems).
Defy Red lens: Can take Quarx CM9 builds from http://quarx2k.ru and flash. You can as well use quarx cm9 defy+ builds (GB kernel)but you need battery fix for battery to work (you can search CM9 thread to get this, otherwise just reply to me and will attach next time).
Defy+: Can take defy+ builds of Quarx and flash.
Defy green: Can take Epsylon CM9 builds and flash.
Enjoy flashing!! Thank me if I had helped you
premaca said:
Please be more specific on what build you are trying to install and what kind of defy you have (defy red lens, defy green lens, defy+).
Defy red lens and defy+ are no different, just that the latter has different battery and capacity. Green lens SOC defy is different and can only use froyo kernel builds (GB kernel builds have camera problems).
Defy Red lens: Can take Quarx CM9 builds from http://quarx2k.ru and flash. You can as well use quarx cm9 defy+ builds (GB kernel)but you need battery fix for battery to work (you can search CM9 thread to get this, otherwise just reply to me and will attach next time).
Defy+: Can take defy+ builds of Quarx and flash.
Defy green: Can take Epsylon CM9 builds and flash.
Enjoy flashing!! Thank me if I had helped you
Click to expand...
Click to collapse
First of all sorry for my bad english and thank you for reply.
Well I have defy with green light (mb525). I just install bootmenu in it and then install "CM9-ICS-MR1-120305-jordan" in it from quarx another link (I think it was froyo kernel). when I restart my phone It was hang on boot logo (pic is attached)..
Now the big problem is I want go back to CM7 or other 2.3 froyo but when i go to the bootmenu (the bootmenu i had installed before delete, i dont know why), the (install from zip) option not showing. it is just showing update from zip , cache wipe and format.
Now please let me know how to solve the problem. Thanks
Hi, seems like you are entering to the wrong recovery.
Does the blue led blink before the boot animation? If then, press volume down during that blink and you should enter the CWM recovery. If not you've possible overwritten the 2ndinit. (Please somebody correct me if I'm wrong)
good luck
ponzoj said:
Hi, seems like you are entering to the wrong recovery.
Does the blue led blink before the boot animation? If then, press volume down during that blink and you should enter the CWM recovery. If not you've possible overwritten the 2ndinit. (Please somebody correct me if I'm wrong)
good luck
Click to expand...
Click to collapse
Yes two lights blink blue and then green before boot animation. How to install 2ndinit, when phone is not opening means phone stuck on boot animation.
slhysf said:
Yes two lights blink blue and then green before boot animation. How to install 2ndinit, when phone is not opening means phone stuck on boot animation.
Click to expand...
Click to collapse
Are you pressing volume down during blue light?
If yes and anyway you access the recovery menu that you said (just "install update.zip") then maybe you will have to flash a clean .sbf image and start over with rooting the phone, install 2nd init...
Just a question: from which recovery have you flashed the ROM last time??
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
ponzoj said:
Are you pressing volume down during blue light?
If yes and anyway you access the recovery menu that you said (just "install update.zip") then maybe you will have to flash a clean .sbf image and start over with rooting the phone, install 2nd init...
Just a question: from which recovery have you flashed the ROM last time??
Click to expand...
Click to collapse
Check on this: http://forum.xda-developers.com/showthread.php?t=1558315
slhysf said:
Yes two lights blink blue and then green before boot animation. How to install 2ndinit, when phone is not opening means phone stuck on boot animation.
Click to expand...
Click to collapse
You already should have CWM!! And if somehow even that is not working do a SBF flash to get out of the mess!
ponzoj said:
Are you pressing volume down during blue light?
If yes and anyway you access the recovery menu that you said (just "install update.zip") then maybe you will have to flash a clean .sbf image and start over with rooting the phone, install 2nd init...
Just a question: from which recovery have you flashed the ROM last time??
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
Check on this: http://forum.xda-developers.com/showthread.php?t=1558315
Click to expand...
Click to collapse
I installed 2nd init for bootmenu and then install ROM after installing ROM bootmenu vanished. (i dont know why). Now Rom is not working properly and have no CMW for reinstall ROM. when I press volume down key on blue light, the defy default menu shows up there are only 3 option cache clear, format and update from sdcard. Installing option not there?
NOW will it fix with flashing SBF?
slhysf said:
I installed 2nd init for bootmenu and then install ROM after installing ROM bootmenu vanished. (i dont know why). Now Rom is not working properly and have no CMW for reinstall ROM. when I press volume down key on blue light, the defy default menu shows up there are only 3 option cache clear, format and update from sdcard. Installing option not there?
NOW will it fix with flashing SBF?
Click to expand...
Click to collapse
Flashing an SBF should fix your problem.
check the link. You will need the .SBF, RSDLite and to boot the phone in "boot loader" mode, it is holding volume up while you power on the phone.
Take care the SBF you will flash since they might be not downgradeable I mean, if you flash a GB SBF you will not be able to get froyo anymore.
read a lot before to do anything and let me know how it goes!
ponzoj said:
Flashing an SBF should fix your problem.
check the link. You will need the .SBF, RSDLite and to boot the phone in "boot loader" mode, it is holding volume up while you power on the phone.
Take care the SBF you will flash since they might be not downgradeable I mean, if you flash a GB SBF you will not be able to get froyo anymore.
read a lot before to do anything and let me know how it goes!
Click to expand...
Click to collapse
OK, just let me know, If I will try SBF and RSDLite. Is there any cause for phone dead or etc? OR it will work fine? Please also provide SBF download link and tutorial link. Thanks
slhysf said:
OK, just let me know, If I will try SBF and RSDLite. Is there any cause for phone dead or etc? OR it will work fine? Please also provide SBF download link and tutorial link. Thanks
Click to expand...
Click to collapse
Go to Dev section the first post has tutorials and list of sbf..
Sent from my MB526 using XDA
pranks1989 said:
Go to Dev section the first post has tutorials and list of sbf..
Sent from my MB526 using XDA
Click to expand...
Click to collapse
I donot flash any kernel after installing CM 9. Is that the problem, CM 9 not working ? I have just install CM9.
slhysf said:
I donot flash any kernel after installing CM 9. Is that the problem, CM 9 not working ? I have just install CM9.
Click to expand...
Click to collapse
Yes you need to but only if you have a froyo sbf and u flashed cm9 for defy + ... Did u do data wipe??
Sent from my MB526 using XDA
pranks1989 said:
Yes you need to but only if you have a froyo sbf and u flashed cm9 for defy + ... Did u do data wipe??
Sent from my MB526 using XDA
Click to expand...
Click to collapse
I have defy (green lens) i want to install CM7 please provide links for kernel. and also tell me procedure. Thanks
Hi, i have some questions about the 2ndboot updates. I had tested cm10 for a while now (but currently in cm7.2), but i got a little lost with this whole kernel update.
1st of all, in quarx page i don't see a "cm10-2ndboot-nightly-defy/" folder, just the one for defy+, this new builds are only for defy plus yet?, or there work on both devices?
and if they do, how sould i install them, do they change to 2ndboot by themselves or do i have to do it myself?
elpiole said:
Hi, i have some questions about the 2ndboot updates. I had tested cm10 for a while now (but currently in cm7.2), but i got a little lost with this whole kernel update.
1st of all, in quarx page i don't see a "cm10-2ndboot-nightly-defy/" folder, just the one for defy+, this new builds are only for defy plus yet?, or there work on both devices?
and if they do, how sould i install them, do they change to 2ndboot by themselves or do i have to do it myself?
Click to expand...
Click to collapse
They are for both and no change is required from your part in the bootmenu settings
I've tried flashing 10.11 and update.zip today, with no luck.
I first tried flashing over my original cm10 (9.12 - froyo kernel, on green lens) - wiped cache, then dalvik.
boot loops on red led
then i tried wiping all data/cache and flashing both again
same boot loops
next i tried flashing a new sbf (t mobile usa 2.1 updated to 2.2 - then rooted and 2ndinit)
now still waiitng at red led on boot, but no boot loops.
I have read the bootup time is very long the first time, but I've let it sit over 15 minutes, and tried a battery pull and let it sit another 15 minutes.
I am about to try again from nordic deblur 2.2 sbf
Am i doing something wrong? I'm not an expert at this stuff, but i'm usually pretty good about following directions. please help!
Amazing job again Quarx and everyone!
Start fresh; use the ultimate wiper for defy and flash cm11/10, and them flash only update v2
Sent from my MB526 using xda premium
tronjojo said:
I've tried flashing 10.11 and update.zip today, with no luck.
I first tried flashing over my original cm10 (9.12 - froyo kernel, on green lens) - wiped cache, then dalvik.
boot loops on red led
then i tried wiping all data/cache and flashing both again
same boot loops
next i tried flashing a new sbf (t mobile usa 2.1 updated to 2.2 - then rooted and 2ndinit)
now still waiitng at red led on boot, but no boot loops.
I have read the bootup time is very long the first time, but I've let it sit over 15 minutes, and tried a battery pull and let it sit another 15 minutes.
I am about to try again from nordic deblur 2.2 sbf
Am i doing something wrong? I'm not an expert at this stuff, but i'm usually pretty good about following directions. please help!
Amazing job again Quarx and everyone!
Click to expand...
Click to collapse
I think You've misundersttod my friend. There no long time of bootlooping. Theres a long first boot. Boot lopping shouldn't happen continuously.
Maybe following the steps below from a post on the defy general forum should help
nidhish91 said:
OOk guys so I found this thread which shows MS2 got a custom kernel. The proceduce is bit difficult but can be modified for working for Defy too.
Hope has struck back again.
http://forum.xda-developers.com/showthread.php?t=1908687
Update: 2ndboot module sources are here:
https://github.com/czechop/2ndboot
Quarx puts his kernel here:
quarx2k.ru
Sdcard symlink Fix:
http://forum.xda-developers.com/showpost.php?p=32428611&postcount=392
Thanks to walter.
-------------------------------------------------------------------------------------------------------------------------------
BIGNOTE: Green lens users who flashed redlens builds please dont try using flash, you will end up burning it like me and many others.
STEPS TO FOLLOW WHEN YOU HAVE BOOTLOOPS OR BLACK SCREEN WITH RED LED ON:
-1st of all set default boot to 2nd-boot
-Go to recovery and flash the 24.9 build
-Then flash the kernel 6.10
-After that flash the latest build
-Wait and you will have your phone working proper.
!
Click to expand...
Click to collapse
Also you cont just go down to a previous sbf version. Youve flashed a custom kernel. You would need to go to your standard kernel which you would find elsewhere. I think the CM10 faqs have the 525 and 526 kernels
i followed the same procedure as last time, but this time starting from the nordic deblur sbf and everything worked fine. no bootloops. long first boot time. If anyone tries this, do NOT use the official tmobile USA sbf. didn't work for me at all. I'm guessing that's why i had problems with 9/24 build as well.
Flashing nordic to workaround red led + black screen ?
tronjojo said:
i followed the same procedure as last time, but this time starting from the nordic deblur sbf and everything worked fine. no bootloops. long first boot time. If anyone tries this, do NOT use the official tmobile USA sbf. didn't work for me at all. I'm guessing that's why i had problems with 9/24 build as well.
Click to expand...
Click to collapse
Hi,
Your message rings a bell to me !
I have tried to flash cm10 18/10 + update_v4 on my Defy (green lens) but I have failed, I always get stuck on red led + black screen. Waiting or removing battery and retrying did not help. Wiping did not help either. I am coming from cm7, had never flashed cm9 or cm10 before, and before cm7 my phone was on french froyo stock rom 3.4.2-164.
Do you think I should try to flash another sbf, such as nordic deblur sbf as you did ?
Is your bootloop like that:
Splashscreen -> red LED + black screen -> Splashscreen -> red LED + black screen
If yes, you should think about upgrading your bootloader...
Had the same problem and was on BL5, some people in Support thread had the same prob on BL5...
So I flashed this chinese rom, rooted and upgraded to cm10 and everything worked fine for me.
Use this SBF just as a stepstone to CM10, because it may break your flashlight or ****.
Make sure you have snd-init on your sd, cause there is no gapps on the sbf...
well thats it...
esok44 said:
Is your bootloop like that:
Splashscreen -> red LED + black screen -> Splashscreen -> red LED + black screen
If yes, you should think about upgrading your bootloader...
Click to expand...
Click to collapse
In my case, it's not looping, it is stucked on red led + black screen.
did you wipe cache and dalvik?
or did you try a clean installation?
wich sbf was the last one you flashed?
- 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