Database Users

[Q] Can i install MS2Ginger over CM7 ?

Hi there i had a problem 2 month ago installing 2endint on my defy anyway i installed CM7 using the custom recovery, now i have CWM installed so i was wonder if i can install MS2Ginger over CM7 thanks

I've not had success with it. I usually have to flash a Froyo SBF before going to a Gingerblur ROM.

Monzer_ said:
Hi there i had a problem 2 month ago installing 2endint on my defy anyway i installed CM7 using the custom recovery, now i have CWM installed so i was wonder if i can install MS2Ginger over CM7 thanks
Click to expand...
Click to collapse
i was able to install ms2 ginger over cm7 and again cm7

Yes, you can. However, after installing the CM7 zip, you need to flash this fixed sbf using RSD Lite.

Zorua said:
Yes, you can. However, after installing the CM7 zip, you need to flash this fixed sbf using RSD Lite.
Click to expand...
Click to collapse
what is this fixed sbf for ? and should i flashed it after i install MS2Ginger ? thanks

You wipe data in 2ndinit, boot into the flashing menu, flash fixed sbf, reboot phone ibto 2nd init recovery, advanced restore, boot, then system, then devtree, then data, then reboot
Sent from my MB525 using Tapatalk

ok so this fixed SBF for CM7 in case i wanna come back from MS2Ginger to CM7 right ?

Yes, that's right. After you install the CM7 zip from clockworkmod, hold up button while rebooting and flash this fixed sbf using RSD Lite. Make sure you clear data and cache from clockworkmod after flashing the fixed sbf.

another question its maybe out of the thread but does it matter that i didnt use 2endinit to install CM7 or not ? coz i used custom recovery i mean is there any side effects ?

Yes, there could be some problems. You should install 2nd init, format data and cache, install CM7 and install the fixed sbf after that. Should work fine then.
Sent from my MB525 on the latest CM 7.2 Nightlies using XDA App

Zorua said:
Yes, that's right. After you install the CM7 zip from clockworkmod, hold up button while rebooting and flash this fixed sbf using RSD Lite. Make sure you clear data and cache from clockworkmod after flashing the fixed sbf.
Click to expand...
Click to collapse
i was able to come back to cm7 from ms2ginger without flashing the fixed sbf . i have ms2ginger 2.1 for green lens i.e soc module
so if i didn't flashed fixed sbf over ms2ginger will i not be able to get back to my nandroid of 2.2.2 version?
please correct me!

Adityaak said:
i was able to come back to cm7 from ms2ginger without flashing the fixed sbf . i have ms2ginger 2.1 for green lens i.e soc module
so if i didn't flashed fixed sbf over ms2ginger will i not be able to get back to my nandroid of 2.2.2 version?
please correct me!
Click to expand...
Click to collapse
Adityaak did u install ms2gigner over cm7 ?? if u did are u having any problem with it like rebooting it self ?? thanks in advance

Monzer_ said:
Adityaak did u install ms2gigner over cm7 ?? if u did are u having any problem with it like rebooting it self ?? thanks in advance
Click to expand...
Click to collapse
yeah i restored the nandroid of ms2ginger2.1 over CM7 and the ms2ginger 2.1 is really good i love it battery backup is really nice just some FC with the camera at starting but now i day i dont even get those FC for the camera i'm loving this ROM.

[Q] update cm9 to cm10 2ndboot

I want to go from cm9 to cm10 2ndboot on my defy.
I think I've read the relevant threads about doing this and ask here just to get a last 'ok' from here...
I have downloaded the CM10-20121018 nightly and the update for it. So I unpack the CM10 copy the update over it and pack it again.
Then I'll do:
wipe data *sigh*
wipe cache and dalvik
flash cm10 2ndboot version
flash google apps
wipe dalvik and cache again
switch 2ndinit boot method to 2ndboot ( <-- is this ok. ? )
reboot
by the way, where can I see my 2ndinit version?
After entering the boot menu it says at the top of the screen: "Android Bootmenu v1.3.0 ICS"
Is this the version of 2ndinit? I thought it should be something over 2 ...
Thanks
Michael

Just flash the nightly and then flash the update. The nightly should automatically change the boot method to 2nd-boot.
In case anything goes wrong, make a nandroid backup first.
Sent from my Nexus 7 using xda app-developers app

Thanks for the answer. Somehow missed that I can just flash the rom and then the update, no need to merge them before flashing.
ralphx10 said:
Just flash the nightly and then flash the update. The nightly should automatically change the boot method to 2nd-boot.
In case anything goes wrong, make a nandroid backup first.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse

Worked like a charm. I'm very happy with this version, great work.
Now I have to convince a friend of me to let me put this on his defy+ . He experiences random reboots and other bad things (camera not working, losing photos...) . I hope this goes away with CM10, allthough it maybe a hardware bug...
Michael

[Q] All ROMs are failing

Hi all!
Almost all ROMs out there are failing to work correctly or even boot on my Defy (red lens). Some do boot, some go to bootloop.
Here's the full story. Two days ago the latest CM10 nightly from Quarx went to bootloop, it was working just fine, but at some point the phone rebooted and didn't boot back up.
I've decided to try another ROM and installed WIUI v4 (JB) from CWM. I went to check device's internal memory and it appeared that I had 48 MB used and that that was all internal memory - the system hasn't even loaded total memory info.
I performed some search and found this thread with the similar issue: http://forum.xda-developers.com/showthread.php?t=1940503
It suggested flashing an SBF via RSD Lite. I did that using the SBF from that thread (2.2 CEE Froyo). I suppose that was my mistake since the thread referred to Defy with a green lens. However, I was finally able to boot the device. I decided to try another SBF. JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDN to be precise. Everything went just fine. I was able to root the device, install CWM using SndInitDefy 2.0, and install stable CM7 (the official one, update-cm-7.1.0-jordan-signed.zip) and Froyo kernel from WIUI.
Everything was working fine except for the camera. It was showing the following error:
"Camera error. Cannot connect to camera"
After that I though that maybe I've messed up with SBF versions. The phone is not sold in Ukraine officially and I didn't remember which SBF it used when it was shipped.
I then followed the guide from All-in-one beginners guide and installed that Chinese SBF with Version 5 CG (thus I presume I can't flash any full SBF now since this will cause a black screen and I will have to re-flash 97.21.51 SBF and do all that stuff all over). Again, I was able to root the phone and stuff. However, none of Quarx's nightlies are working, CM7.2 or 2nd-boot CM10 are simply bootlooping, WIUI v4 can't connect to any of Google's services (they constantly FC), and none of the ROMs can connect to the camera.
Currently I'm using the following:
official CM7.1.0
Android 2.3.7
kernel [email protected] #1
Build number Gingerbread GWK74
I'm okay with staying on CM7.1, but I require the camera to work. So, the question is, what should be done in order to make the camera work?
Maybe, I should change some lib files, if so, could you please provide with the link to the correct ones? I've already tried some camera fix SBF's but they didn't seem to work. If there is any additional information required, please let me know.
Any help will be really appreciated!
Thank you in advance.

Maybe you could get rid of the sbf problem(camera issue caused by wrong flashing) by flashing a defyplus sbf with group code 6. Then your camera should work.
Sent from my MB526 using xda premium

Thanks, thekguy! Will try this later today.

Nope, that didn't work, unfortunately. Flashed 4.5.1-134_DFP-125, but the camera is still failing, as well as the latest CM10. Any suggestions are welcome.

Hmm, latest cm10 2ndboot right? That's a very bad sign, since that rom indeed works with both the camera modules, and its really curious that it's not working.
Flash back to any defy bl6 sbf from this list(don't flash defy+ sbf since that approach isn't working):
http://forum.xda-developers.com/showthread.php?t=966537
Wipe data, and use the defy ultimate wiper script(it's there in themes and apps section, use ext4 version if you're on cm10 or ext3 for any other rom).
Now flash cm10 2ndboot build, and try using the camera.
Normally that should work, even if you have a green lens module, but if not so then it could be add a result of a hardware failure
Sent from my MB526 using xda premium

Yeah, I've also tried CM7 for Defy+, but that didn't work either. And I guess I pushed my device few steps closer to the brick yesterday. I flashed one of Chinese SBFs (JRDNEM_U3_3.4.3-36-1_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTINT_P011_A013_HWp3_Service1FF). It's BL7 SBF and it's known for its outstanding unbricking abilities. Didn't work for me. However, the bootloader is still accessible and I will keep playing with the phone today.
I'm getting tired of all this.

Didn't work? Camera or unable to boot?
Remember, you must wipe data from stock recovery before you can boot into the stock rom
Once you are running on the stock rom, check if the camera works. If not then follow my other post about getting to cm10 2ndboot. It may hang once on boot but it will boot after that. If still the camera is not working then I'm afraid it's beyond help
Sent from my MB526 using xda premium

thekguy said:
Didn't work? Camera or unable to boot?
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Didn't boot at all, just a blank black screen. I can't enter stock recovery and the bootloader is not visible. However, if I boot up with power+vol+ and connect the phone to the desktop, RSD Lite detects the phone and I can flash an SBF. But my guess is that this would be useless since the last SBF I flashed was BL7.
Well, I'm at work right now, thus I can't try anything out right now. Theoretically, I should be able to flash any SBF with BL7, and root it using this guide http://forum.xda-developers.com/showthread.php?t=1542956

Then, flash both sbfs from that guide, and it should work.
You shouldn't get any blank screen, simply because you've got the highest possible group code, and you cannot have a wrong kernel just after flashing the sbf. It must work
Sent from my MB526 using xda premium

Thanks. Will definitely give it a try once I get home.

OK, I've managed to install 4.5.1-134 DFP-231 Retail.en.EU CEE, root it, and flashed CM10 2nd-boot nightly. However, I'm still unable to boot the phone. It shows CM10 logo spinning for 10-20 seconds and then reboots. I assume that this is the only ROM which can make the camera work. Am I right? If yes, what should I check or do in order to fix the boot looping? If I can use some other ROM, could you please let me know which one exactly and what can be done in order to fix the camera?
Thank you!

Just flashed CM10 and checked the log, there's the following message:
set_perm: chown of /system/xbin/tcpdump to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/tcpdump to 6755 failed: No such file or directory
Click to expand...
Click to collapse
Could this be a source of the problem?

Another update. I've installed WIUI v4 for GB kernel and looks like it requires less internal memory/RAM to run so I'm able to boot the phone completely. And it's showing that I have 0.00 MB of internal storage in total and 58 MB used. I guess internal memory issue is somehow related to the bootloop.

Before flashing cm10, use both the ultimate wiper scripts(ext4 and ext3 version)
After flashing cm10, go back to boot menu and select tools, file system tools and format to ext4. It should boot now
Sent from my MB526 using xda premium

Thanks for the clue, but I'm afraid that didn't work. Since I had some time and have no data to lose, I wiped the phone from stock recovery, flashed both standard 4.5.1-134 DFP-231 and rooted 4.5.1-134 DFP-231, wiped everything using both ext3 and ext4 Ultimate scripts, flashed Quarx's 2nd boot CM10, formatted data and cache to ext4 using File System tools. CM10 still bootloops, but at least now I have internal memory info displayed correctly in WIUI v4 (JB). But since it's not a 2nd boot ROM, the camera isn't working.
In fact, I've tried some other 2nd boot scripts (NEGAN-6DIC and Codenameandroid 3.6.6), but they are bootlooping as well.
Maybe there are some other 2nd boot ROMs I should check? Or maybe if I get a nandroid backup of a working system I could restore it on my phone?

Try converting to ext4 and flash after that. It is really curious why it bootloops. You must get cm10 to boot, so that the camera works. Look here for downloading a stock kernel that should hopefully fix the boot loops.
http://forum.xda-developers.com/showthread.php?t=1909242
Scroll down for the post which talks about having a compatible stock kernel which should allow 2ndboot to work(it's titled for bl7 users).
Flash this kernel after stock sbf flash, then try installing cm10.
Let's see how this goes
Sent from my MB526 using xda premium

Still no joy. Neither formatting, nor following this guide http://forum.xda-developers.com/showthread.php?t=1909242 worked. Is there a way to see boot log from a desktop? I have both Debian and Win7 on my desktop.
Thanks.

There is a way to debug using uart, but I have no experience with it. So, sbf flash+ compatible stock kernel failed? Please describe the boot loop. Does it reach the cyanogenmod logo? Or stuck at red Motorola logo? I am at my wits end at this one. All my semi bricks and other problems I could fix by the methods outlined in my previous posts, but they don't seem to work in your case. You flash full sbfs right? And are you able to boot the stock Rom?
Sent from my MB526 using xda premium

Here's how it loops:
- the phone starts
- shows red Moto logo
- blue led
- red led
- blank black screen
- HW buttons blink once
- CM10 spins for approx 5-10 seconds
- the phone restarts and all the steps repeat
Yes, I'm able to flash full SBF (BL7 ones). I'm able to boot into a stock ROM, I can flash modded SBF for BL7 (the rooted one). I've tried flashing CM10 SBF, but the phone booted into a bootloader and showed an error, with set of numbers. Looks like because of the kernel (my guess is that SBF contains non-2nd boot version of CM10).
If I install WIUI v4 right after I flash rooted SBF I have no issues with the internal storage.
If I install 2nd boot CM10 (Kayant's, Quarx's) I get a boot loop (Ultimate Wipe doesn't help)
If I install WIUI v4 after CM10 (without re-flashing SBF's), I get 0.00 internal storage, but wiping data/cache from stock recovery solves the issue.
Unfortunately, wiping data/cache from stock recovery doesn't do the trick for CM10 2nd boot builds.
One more thing, after I flash CM10 and try to wipe data/cache from stock recovery for the first time, it shows recover log errors. There are errors when entering stock recovery after that.

Might be a false trail, but what about wiping from custom recovery? Dalvik cache wipe?
This indicates that the kernel had loaded before some other problem caused the phone to enter into boot loop. What about the camera in the stock build? Same error as before?:banghead:
The cm10 sbf probably had a lower group code(bl6 perhaps) hence that approach won't work, and even discarding that it will yield the same results as before.
Also, in stock, check if the kernel version changes after you flash the compatible stock kernel from the thread I had mentioned earlier. This is important because otherwise there is no chance for cm10 to boot.
Sent from my MB526 using xda premium

[Q] Only CM10 won't install on red lens Defy?

I recently found out, that some people and I are unable to install Quarx CM10 for our red lens defy, but we can try a method going to a defy+ sbf which comes with BL version 7, and after that it works, but you won't be able to downgrade.
Is there any other way to make it successfully install without this radical approach of flashing a dfp sbf on my red lens MB525? Why won't Quarx's CM10 install if i'm not BL7? Is there any JB rom that does not require this kind of treatment?

gyorgyszemok said:
I recently found out, that some people and I are unable to install Quarx CM10 for our red lens defy, but we can try a method going to a defy+ sbf which comes with BL version 7, and after that it works, but you won't be able to downgrade.
Is there any other way to make it successfully install without this radical approach of flashing a dfp sbf on my red lens MB525? Why won't Quarx's CM10 install if i'm not BL7? Is there any JB rom that does not require this kind of treatment?
Click to expand...
Click to collapse
Your most probably doing something wrong. List your steps.

hotdog125 said:
Your most probably doing something wrong. List your steps.
Click to expand...
Click to collapse
i was on cm9, and i usually tried installing this way
wipe data/cache/dalvik
install cm10
install gapps
reboot
bootloop
OR
wipe data/cache/dalvik
format to ext4
install cm10
install gapps
reboot
bootloop
I also have an older thread which was kinda 'deadline' for me bcuz i won't go risky by installing defyplus sbf, when it should work normally, here's the link: http://forum.xda-developers.com/showthread.php?t=2218569

gyorgyszemok said:
i was on cm9, and i usually tried installing this way
wipe data/cache/dalvik
install cm10
install gapps
reboot
bootloop
OR
wipe data/cache/dalvik
format to ext4
install cm10
install gapps
reboot
bootloop
I also have an older thread which was kinda 'deadline' for me bcuz i won't go risky by installing defyplus sbf, when it should work normally, here's the link: http://forum.xda-developers.com/showthread.php?t=2218569
Click to expand...
Click to collapse
Get AROMA wiper for Defy (search for it), 'flash' it, a white screen with some options will appear. Choose wipe system, data and cache in ext4 (DO NOT REBOOT AFTER THIS), and then immediately flash latest CM10 (9 July) and minimal gapps.
OR, choose Defy ultimate wiper. Download the appropriate file and flash.

hotdog125 said:
Get AROMA wiper for Defy (search for it), 'flash' it, a white screen with some options will appear. Choose wipe system, data and cache in ext4 (DO NOT REBOOT AFTER THIS), and then immediately flash latest CM10 (9 July) and minimal gapps.
OR, choose Defy ultimate wiper. Download the appropriate file and flash.
Click to expand...
Click to collapse
As long as you do not do this on TWRP, which no longer works due to random reboots that will leave you knee-deep in sh*t, you should be fine.
Use CWM to follow his instructions or you can flash your stock SBF (NOT BL7, WHO TOLD YOU THAT BL7 WOULD SOLVE YOUR PROBLEMS??) to get a clean install and start over.
Whoever told you that you should flash a DFP-188/231/2311/2312 SBF in order to use CM10 is a nuthead and should not be helping anyone.

droid_<3er said:
As long as you do not do this on TWRP, which no longer works due to random reboots that will leave you knee-deep in sh*t, you should be fine.
Use CWM to follow his instructions or you can flash your stock SBF (NOT BL7, WHO TOLD YOU THAT BL7 WOULD SOLVE YOUR PROBLEMS??) to get a clean install and start over.
Whoever told you that you should flash a DFP-188/231/2311/2312 SBF in order to use CM10 is a nuthead and should not be helping anyone.
Click to expand...
Click to collapse
It works on TWRP 3 out of 5 times. I've had to reflash sbf 2 times because of an unexpected reboot.

droid_<3er said:
As long as you do not do this on TWRP, which no longer works due to random reboots that will leave you knee-deep in sh*t, you should be fine.
Use CWM to follow his instructions or you can flash your stock SBF (NOT BL7, WHO TOLD YOU THAT BL7 WOULD SOLVE YOUR PROBLEMS??) to get a clean install and start over.
Whoever told you that you should flash a DFP-188/231/2311/2312 SBF in order to use CM10 is a nuthead and should not be helping anyone.
Click to expand...
Click to collapse
I mentioned my old post regarding the same issue, there you can find all other information regarding the users, or why did they say that. To be honest I did not really want to believe that flashing a dfp 231 sbf would solve my problem, neither that it could be the only solution.. Im giving AROMA wiper a try in the next few hours, wish me luck.

i got status 7 error...
edit: the sad part is i found a solution by googleing the error, but the line i should remove from the updater script wasnt even there.

@droid_<3er
If you could check previous such threads, you will find that in certain cases, because of 2ndboot incompatibilities, some people were unable to use cm10 because of the same. The stock kernel must be compatible for the kexec approach. It seems it isn't true for all kernels. You should read up before trying to pass comments on others.
As for OP I wish you luck in solving this issue, since I have by elimination found bl version upgrading to be the only working solution. It may not be the only one, but it certainly works.
Sent from my MB526 using Tapatalk 2

[Q] uninstalling slimkat (cm11)

Hi guys, need some help here. I'm sure this has been asked before but i just couldn't find any
Installed slimkat 20140406-0134 rom (cm11) last night and it's basically working. But I'm still not feeling comfortable using it as there's still bugs around. So thought of going back to cm7.2 for now. But for the life of me couldn't figure out how to get to the tool section so I can re-partition it back to ext3!!!
All I could get in to is twrp recovery and that's it. how do I even get into the bootmenu section where I can choose recovery, cpu settings, tools, etc? There's no red Moto logo with blue LED at boot up anymore
Is there any uninstall instruction somewhere, or perhaps someone should write one?

44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........

jh20 said:
44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........
Click to expand...
Click to collapse
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.

Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk

aperture said:
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.
Click to expand...
Click to collapse
thanks. i'll remember that next time. don't know why i didn't think of that. panic striken maybe
hotdog125 said:
Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
that's exactly what i did but didn't work. aromawiper seems to have worked properly but twrp 2.6.3.0 keep saying "no os installed" after i installed the gb rom and tried to reboot. tried maniac's cm7.2 and an older wiui gingerbread rom. i thought it might be a hickup and rebooted anyway and that was it.
don't know what went wrong there. has anyone actually tried this method before and got it to work?
edit: imho twrp is not worth it. it rebooted 8-10 times on me after installing cm11 and tried to get back into recovery to flash gapps. also other problems like blank backup files and my failures to install rom problem. they should have stuck to cwm until the problems are fixed.
edit 2: and i think removing bootmenu is not a good idea. more steps to take if you want to go back to cm7.2.