Related
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.
I accidentaly installed the CM9 kernel when i should have installed the CM7 one with ICS. Then i made a nandroid restore of my previous CM7. Than... phone dead. Starting but no CWM no ROM booting.
As i have had CM7 with GB kernel( i think) i flashed ( not knowing) an old SBF than didn't booted. I tried the JORDN_U3_97.21.51 T-Mobile It boots, i can root it, install CWM.
But than when i try to install a CM7 nightly ( installed ok) it dies again. Starts but No CWM no Rom booting.
What to do? I don't know what SBF to flash or what method to install?
Problem update I red that the above SBF has a CG Version 3: SBF 2.51 (Éclair) (Defy) so i installed several CG Version 4: SBF 3.4.2 (Froyo) (Defy).
They don't work. RSD says PASS but phone is dead .No stock recovery no boot. Only way to get it back to life is if i flash the eclair again.
I red that if i get a back screen when booting i have installed a lower CG version. As i tested with version 4, version 5 GB is the only option. I didn't try it out because there are some issues. Froyo would have been much more easier.
i think many readers of your post are getting problems with understanding your problem ...
you got a stock defy, rooted it, installed 2ndinit via apk, booted into recovery (vol- at blue led) and installed CM7 zip ??? correct ???
after succesfull install of CM7 your phone doesn't turn on? Black screen?
black screen after zip is (i think) impossible ... but i can fail ...
i would like to help you, but first you have to give the detailed steps you did and what you wanted to do ...
To make it simplier
I installed the JORDN_U3_97.21.51 T-Mobile (which is 2.1 update1) It boots, i can root it, install 2nd-init > CWM. Set Normal boot.
Than in CWM nothing works.
Installing a CM7 nightly, or restoring a CWM backup.
I install a CM7 nightly like this> In CWM> Custom Recovery> Wipe data, wipe cache> install Cm7 zip, install Gaaps zip. After this, phone restarts, screen is on, logo appears and i wait and wait. Nothing happens.
Do i have to install a special CM7 build?
The CWM backup does not restore. It says that files are missing ( like android.secure..) I am not interested in keeping downgrade ability. i would like to try another SBF. I am not 100% sure what SBF to use from the wiki page.
I red that the SBF i installed has some special "problems" here> http://forum.xda-developers.com/showthread.php?t=905371. They are talking of a CWM revoery app by tenfair here> http://forum.xda-developers.com/showthread.php?t=875233
Maybe that works^. Will try it after the phone is fully charged.
so, ok ... thats detailed as i wish
ok, the problem is clear i think ... first of all eclair is not a nice system for a defy ... upgrade to froyo or even gingerbread ... (keep in mind, that GB has problems with green lens camera) ...
than you can root it with SuperOneClick e.g. ... if this is running correctly, you can install 2ndinit via apk ... then boot, vol- while blue led (i know, you know how ) ... in that clockworkmod recovery you can wipe the devices data and cache partition (even wipe dalvik cache in advanced menu) ... then install CM7.2-nightly-.... .zip ... you may have to flash an fixed sbf with the nessesary kernel for CM7 at this point to boot ...
if this is working fine, you can install the gapps.zip via recovery ...
also try to set boot to 2ndinit in boot-menu ... i don't think it's "normal" boot for CM7 ... but i can't try at the moment cause of my bricked defy ...
Thanks for the reply.
The problem is that i can't install other Froyo SBF's. Will try Gingerbread SBF. The last froyo didn't boot, will try a new one. Weird, i know. Maybe someone can tell me which CM7 to flash? An older one with Kernel ? I didn't think the install would be so tricky.
Froyo Full-SBF doesn't boot on your defy?
be aware of flashing Gingerbread then ... if GB doesn't boot, you will have a problem downgrading to froyo / eclair ...
it sonds crazy, that froyo isn't booting on your device ... have you done a full wipe after froyo sbf? it's important ...
I'm on the Eclair SBF right now. What should i do? Go into recovery and do a wipe or install a new Froyo SBF? It's about the CG value maybe. I understand the mechanism but don't know how to check the CG value. If i search for my current eclair SBF i get all sorts of weird stuff. Nevertheless i will try and try until i succeed. It took me a while to figure out the Rooting method. Superoneclick does not work. It's a special method for the 2.51.
The thing is that i wanted to go the my Nordic SBF( the one Quarx used during the first days of CM7) and it didn't booted. That's why i tried this one. Funny ho flashing the wrong kernel(CM9 instead of CM7) can brake things like this. What i don't understand is how my CWM backup didn't restore. It restored well, finished, then phone dead. No CWM.
edit: i just red: 2.51 is Not downgradable. But no downgrade to what??? Will try to some Froyo SBF's, see if works. But that does not solve my CM7 issues.
Tried a few Froyo SBF's. Wiped data/cache in Stock Recovery. RSD says PASS than phone does not boot. Only the 21.51 eclair works all the time.....Where next?
Update 2 got it to work with this>
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=cg
OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???
Glad it worked.
DJ_Synergy said:
OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???
Click to expand...
Click to collapse
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .
HI Deonix, I have the similar problem. However I am unable to use RSDlite as it gives a failure messg when u click start. I tried JRDNEM_U3_3.4.3-36-1.7.sbf and JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B50AA028.0R_USAJORDANRTINT15_P003_A020_HWp3_Service1FF.sbf.
Both failed, I will try using the rsdlite after the cache and factory rest this time based on your suggestions. Can you tell, if your adb command was listing your device, as mine is not.
my CWM is also gone I get some old android recovery system 3e instead which fails after signature check.
Hi,
I think I know what is your problem.
I also installed the firmware JORDN_U3_97.21.51 and now I can only install any Custom ROM after installing the firmware fix for JORDN_U3_97.21.51.
I did upload it for you: http://www.4shared.com/rar/o02VEk_v/firmware.html?refurl=d1url
It is the following:
Install JORDN_U3_97.21.51;
Rootear;
Install the Recovery;
Install the fix;
enter the recovery and install any rom you want, remembering to delete the caches (data and Dalvik cache)
ps: have 100% of the battery before installing the SBF.
any problems let me know.
Sometimes you could get stuck in a bootloop and all you need to do is pull battery and reboot
Sent from my MB525 using xda premium
Same Problem, Please help!
Deonix said:
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .
Click to expand...
Click to collapse
Hey bro.
Even i have got the Defy working, but its not detecting the device when connected to the computer, i have done all the basic troubleshooting, is it working for you??
is it bcoz this room is for ME525??
Hello , I just acquired a new Defy+ sometime back and would like to know if somebody could help me find a thread which would help me install the best custom firmware out there.
What are the advantages of using a custom firmware over stock and would it be stable ?
Read this fully and all your doubts will be cleared. Regarding custom ROM, CM10 is pretty good. I'm using the same on my Defy+.
http://forum.xda-developers.com/showthread.php?t=1216982
andr0idfreak said:
Read this fully and all your doubts will be cleared. Regarding custom ROM, CM10 is pretty good. I'm using the same on my Defy+.
http://forum.xda-developers.com/showthread.php?t=1216982
Click to expand...
Click to collapse
Thank you for the link , I will read through it now.
Should I go ahead with this method ?
How to Root: (NOT for BL7)
Get SuperOneClickRoot
Get and Install Motorola Drivers [32bits] [64bits]
Reboot your PC
Turn USB Debugging ON (Settings -> Applications -> Development on your Defy)
Connect your Defy to the PC
Wait for the PC to install any missing Drivers
Click on Root
Let it work, then it will ask if you want to install BusyBox, hit YES
After it finished it will ask to make a test, click cancel and just Reboot your Defy
Done, Defy rooted
Assuming that you've confirmed your ROM is not BL7, the method is fine.
andr0idfreak said:
Assuming that you've confirmed your ROM is not BL7, the method is fine.
Click to expand...
Click to collapse
Ok I just found out that I have BL7 and the procedure for rooting my phone is in this guide
http://forum.xda-developers.com/showthread.php?t=1542956
Can you please explain to me the steps in detail ? from wiping the phone to flashing the required files , I'm a complete noob at this.
"1. Wipe phone twice (2x make Wipe Data/Cache in stock recovery) [just to play safe] [to boot in stock recovery restart your phone while holding Power+Vol Down button]"
When I power+vol down i just get a green android logo with an icon , how do i get into stock recovery to wipe data/cache ?
Hi, so i have latest miui V4 2ndboot on my defy. First i have latest CM10 Quarx.
When I change Rom all perfect
but when I try enter to stock recovery my phone stay on moto logo and i pull out battery fot boot phone
For other i can enter to cwm recovery and phone work,
For restore motorola recovery? I flash any zip?
this can cause problems?
Thanks for all
P.S. I have motorola defy MB525 red lense
up
Why you need stock recovery, if you have included 2ndinit in custom roms. 2nd: if you want to restore stock recovery, you'll need to start from scratch...
Gianluca85 said:
Hi, so i have latest miui V4 2ndboot on my defy. First i have latest CM10 Quarx.
When I change Rom all perfect
but when I try enter to stock recovery my phone stay on moto logo and i pull out battery fot boot phone
For other i can enter to cwm recovery and phone work,
For restore motorola recovery? I flash any zip?
this can cause problems?
Thanks for all
P.S. I have motorola defy MB525 red lense
Click to expand...
Click to collapse
stock recovery is available through bootmenu (2nd or 3rd option). So reboot in bootmenu.
pgreed said:
stock recovery is available through bootmenu (2nd or 3rd option). So reboot in bootmenu.
Click to expand...
Click to collapse
when I try, bootmenu -> recovery -> stock recovery stay on motorola logo and i pull off battery
turffe said:
Why you need stock recovery, if you have included 2ndinit in custom roms. 2nd: if you want to restore stock recovery, you'll need to start from scratch...
Click to expand...
Click to collapse
Because when i have cm 10 (2nd-boo) stock recovery work , I try install cm7 official (2nd-init) but i can enter to cwm but stock recovery don't work.
If this not cause problem, I stay whit this rom and work whit cwm recovery
If I want restore recovery? I flash sbf file whit ROM stock?
Gianluca85 said:
when I try, bootmenu -> recovery -> stock recovery stay on motorola logo and i pull off battery
Click to expand...
Click to collapse
In that case you need to start from begining: flash sbf. etc. because I dunno if you find a bootloader.img to flash.
pgreed said:
In that case you need to start from begining: flash sbf. etc. because I dunno if you find a bootloader.img to flash.
Click to expand...
Click to collapse
I have found my bachup of original rom and on this file i find boot img and recovery img?
If I restore this?
I restore original stock recovery?
the cwm recovery remaning?
thanks for all.
you can reinstall custom recovery (which contain stable recovery) through terminal emulator (with an sh script) or restore a img.
pgreed said:
you can reinstall custom recovery (which contain stable recovery) through terminal emulator (with an sh script) or restore a img.
Click to expand...
Click to collapse
if I use 2ndinit.apk and install cwm this restore the stock recovery?
if no i have download sbf rsd lite and ready for all
Thanks for all
Stock recovery disappeared, it's happen sometimes when using custom roms. No clue too.
But it's not even a problem, you don't need stock recovery if you're using custom roms. Custom/stable recovery work it all.
You only need Stock recovery once you want to revert back to stock roms.
When you flash stock SBF successfully Stock recovery will work again! (and let you wipe to gracefully boot into rom.)
So, you plan to return to stock? If not, stop this worries until you planned to.
intemptesta said:
Stock recovery disappeared, it's happen sometimes when using custom roms. No clue too.
But it's not even a problem, you don't need stock recovery if you're using custom roms. Custom/stable recovery work it all.
You only need Stock recovery once you want to revert back to stock roms.
When you flash stock SBF successfully Stock recovery will work again! (and let you wipe to gracefully boot into rom.)
So, you plan to return to stock? If not, stop this worries until you planned to.
Click to expand...
Click to collapse
thanks for all, i asked if this is a problem. only you say me this not a problem. Now I Know the procedure and that happen when flash rom.
For me the tread closed
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