[Q] Help with Defy (green lens) and custom ROMS - Defy Q&A, Help & Troubleshooting

I am currently on a stock Android 2.1-update1 TMobile US ROM on my Defy (green lens) ROM. I would like to try out CyanogenMod 7.1 (or 7.2 RC) and need help confirming my understanding of the process. I am already rooted and have installed the GoAPK recovery.
1. I need to flash my kernel to froyo to 2.2. In order to be able to downgrade back to 2.1 I need to use a "fixed" sbf. If I run the smgver.exe utility on the sbf file and it says "no version found" than this is a safe sbf to flash (can still downgrade).
2. Before I flash this new kernel I need to (should) do a full nandroid backup of my current rom so I can restore it if things go wrong. I might need to install SuperOneClickFor2.x to do the backup and future recoveries.
3. Once I flash one of these "fixed" sbf I can then do the "update.zip" process to flash CM7 onto my defy. I will need to do a factory reset and wipe the data/cache partitions. This will cause me to lose my contacts/calendar/etc AND my installed applications (and their data, so I need to back them up using something like TitaniumBackup).
4. Once I've got CM7 (with froyo kernel) I can flash one of the CM9 builds for the defy green lens that is built specifically for the froyo kernel
I've searched and read as much as I can, I feel like I "got it" but I just wanted a little confirmation before I start hacking this phone apart =)
Thanks for any help you can give me =)

Here is the explanation from all that I know:
1. I need to flash my kernel to froyo to 2.2. In order to be able to downgrade back to 2.1 I need to use a "fixed" sbf. If I run the smgver.exe utility on the sbf file and it says "no version found" than this is a safe sbf to flash (can still downgrade). Ya, that is true. But after flashing fixed SBF you also need Nandroid backup to be restored.(This is not your nandroid backup. Its the nandroid backup supplied with the fixed sbf)
2. Before I flash this new kernel I need to (should) do a full nandroid backup of my current rom so I can restore it if things go wrong. I might need to install SuperOneClickFor2.x to do the backup and future recoveries.
Yes Nandroid backup is always recommended. Superoneclick is a software needed to root your phone. That answers the rest.
3. Once I flash one of these "fixed" sbf I can then do the "update.zip" process to flash CM7 onto my defy. I will need to do a factory reset and wipe the data/cache partitions. This will cause me to lose my contacts/calendar/etc AND my installed applications (and their data, so I need to back them up using something like TitaniumBackup).
Yes, however its not update.zip but its <ROM NAME>.zip Your contacts,calender can be backed up in your google account and if you use gapps(google apps. Needs to be installed separately by install .zip in CM) in your CM those will come again. Your installed apps and data yes can be restored from TB. You can backup SMS using SMS backup+
4. Once I've got CM7 (with froyo kernel) I can flash one of the CM9 builds for the defy green lens that is built specifically for the froyo kernel
Yes either that or you can even directly flash CM9 for Froyo kernel.
Hope that helps...

Related

[Q] Can i go back from the ics test as of 7-12-11 version?

Hi
I flashed the new ICS experimental build and i like so far...but i am not sure now if i am able to switch back to cm7 if i want to since there is osmething with the kernel.
Does Quarx use the 2.3.4 (should be reverseable) or the 2.3.6 Kernel (cant go back from this one)
I like to use the new ics testversion but in case i need to use camera it would be nice to go back..
Is it possible? If so..just flash cm 7 or any tricks needed?
ace-drink said:
Hi
I flashed the new ICS experimental build and i like so far...but i am not sure now if i am able to switch back to cm7 if i want to since there is osmething with the kernel.
Does Quarx use the 2.3.4 (should be reverseable) or the 2.3.6 Kernel (cant go back from this one)
I like to use the new ics testversion but in case i need to use camera it would be nice to go back..
Is it possible? If so..just flash cm 7 or any tricks needed?
Click to expand...
Click to collapse
Re-installing CM7 Stable (e.g. 11.11.11) should definitely work.
If you took a nandroid before you installed ICS then you should be able to go back by restoring your backup. You need to restore boot and devtree also.
backup & recovery -> restore (which will restore system and data)
then do advanced restore and restore boot and devtree.
I flash the 11-11-11 version by quarx and after it starts reboot into recovery and restore my backup. if you have any problem try wipe dalvik
will flashing a full sbf of 2.2.2 work?
you can flash a zip with the boot.img and DEVTREE.IMG.have fun.
so i cant just flash CM 7 stable? never done anything nandroid...only flashed *.zips
just flashed ,today i flash ics,but i reflashed 2hour latter because i can read the relations .
I flashed ICS 7-12 today. I was able to go back to Cyanogenmod's official nightly 7.1 build 63 after wiping the data. I'm using the froyo kernel.
Sent from my MB525 using XDA App
just wipe data flash .zip of cm7 then wipe dalvik and after it turns on go into recovery again and restore your backup. Maybe you can try to do all in one boot but i think it is risky

Bootloop, SBF issue >please help

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??

Remove manually ClockWorkMod - CWM (2nd-init)

It's there a way to remove manually ClockWorkMod (2nd-init) from stock rom?
Besides, erase bootmenu folder, what more i have to do?
if you want to stay on stok Rom, reset the mobile data
of course you can back up apps first
Well, my intention it's a little more complicated... I want to create a custom sbf following instructions from Vaserbanix thread in order to have a 2.2.2 sbf from my original system. In some pages, i get an original sbf from my carrier but it's a 2.2.1 version... My phone came with a 2.2.2 version, so i made a nandroid backup, then i extracted system but i realized that my system it's already rooted and with bootmenu included. So, i want to make it more "stock"
Solved. Please, moderator...close this thread....

Bravo's bootloader

Hello
I have Motorola Bravo, everything stock 2.2.1 ROM
but I want to install custom ROMs and I have one question: Does Motorola Bravo's bootloader need unlock? I ask that, because I also have Motorola Atrix 4G and I had to unlock it's bootloader to install Cm7
Enigmavision said:
Hello
I have Motorola Bravo, everything stock 2.2.1 ROM
but I want to install custom ROMs and I have one question: Does Motorola Bravo's bootloader need unlock? I ask that, because I also have Motorola Atrix 4G and I had to unlock it's bootloader to install Cm7
Click to expand...
Click to collapse
No, just install 2nd-init recovery (search the Defy Forums\CM7 threads here) then flash away . Our bootloader is locked up like a con in a SuperMax with a triple life sentence. I'm getting ready for work so I don't have time to hotlink.
skeevy420 said:
No, just install 2nd-init recovery (search the Defy Forums\CM7 threads here) then flash away . Our bootloader is locked up like a con in a SuperMax with a triple life sentence. I'm getting ready for work so I don't have time to hotlink.
Click to expand...
Click to collapse
Here you go: https://www.box.com/shared/p07z8hangnqxydducrhr.
Edit: on a side note, I've had issues restoring my JB nand from the cm7 recovery. I get "error restoring system" in the middle of a nand restore. It also completely screws up mounts and the only thing I can do is install a ROM from scratch. The md5 checks out as well. Any ideas?
Dr. Orange said:
Here you go: https://www.box.com/shared/p07z8hangnqxydducrhr.
Edit: on a side note, I've had issues restoring my JB nand from the cm7 recovery. I get "error restoring system" in the middle of a nand restore. It also completely screws up mounts and the only thing I can do is install a ROM from scratch. The md5 checks out as well. Any ideas?
Click to expand...
Click to collapse
JB has a newer recovery. Install a JB rom then restore the nand of the JB backup.
Flash JB rom (cache\data wipes don't matter since you won't be booting into the system)
Reboot directly into recovery (don't let the system boot up, even once)
Restore JB Backup as usual
This is actually a common problem with Defy users running older MS2 roms trying to flash JB -- the different recovery versions can be a pita to deal with sometimes; but its usually fixed by flashing a rom with a compatible recovery version then restoring the nand afterwards.
While I won't go into the full details, you can also take the recovery from a JB rom and a GB rom and make them into a flashable zips -- basically open the rom's zip and delete all the /system folders except /system/bootmenu and edit the rom's updater-script to only set permissions to /system/bootmenu. It would also be a good idea to add in ramdisk backup commands as well (the init.rc files under 2nd-init and 2nd-boot) since they can change from rom to rom. Once all that's done you'll be able to flash the required recovery version for the nand you intend to restore or flash the JB recovery after flashing any rom and have an up-to-date recovery with an older rom. If you use multiboot it would be a good idea to merge it into your new recovery zip as well.
/About to test a CM7 port with many tweaks -- if it boots I'll start adding in some market apps and finish it up later today . Then its off to start updating PA with a Custom Kernel . I may have to drop MS2 PA support if the MS2's Custom Kernel differences makes it incompatible with the Defy base
skeevy420 said:
JB has a newer recovery. Install a JB rom then restore the nand of the JB backup.
Flash JB rom (cache\data wipes don't matter since you won't be booting into the system)
Reboot directly into recovery (don't let the system boot up, even once)
Restore JB Backup as usual
This is actually a common problem with Defy users running older MS2 roms trying to flash JB -- the different recovery versions can be a pita to deal with sometimes; but its usually fixed by flashing a rom with a compatible recovery version then restoring the nand afterwards.
While I won't go into the full details, you can also take the recovery from a JB rom and a GB rom and make them into a flashable zips -- basically open the rom's zip and delete all the /system folders except /system/bootmenu and edit the rom's updater-script to only set permissions to /system/bootmenu. It would also be a good idea to add in ramdisk backup commands as well (the init.rc files under 2nd-init and 2nd-boot) since they can change from rom to rom. Once all that's done you'll be able to flash the required recovery version for the nand you intend to restore or flash the JB recovery after flashing any rom and have an up-to-date recovery with an older rom. If you use multiboot it would be a good idea to merge it into your new recovery zip as well.
/About to test a CM7 port with many tweaks -- if it boots I'll start adding in some market apps and finish it up later today . Then its off to start updating PA with a Custom Kernel . I may have to drop MS2 PA support if the MS2's Custom Kernel differences makes it incompatible with the Defy base
Click to expand...
Click to collapse
Yep that makes sense. Thanks for the help as always skeevy.
*edit* Same issue.
Restoring system...
Error while restoring /system!
Problem while restoring system!
Maybe I didn't reboot correctly...bad backup maybe? I've restored this backup before with no problems. : \
*edit again* I goofed. Your instructions worked fine.

[Q] Motorola Defy+: Return phone to factory state

Hi,
I have Defy+ running quarx's CM10 android 4.1.2.
What I want is to recover my phone as it was, with official gingerbread and no 2nd init or other software installed on it.
Is there any way to do that?
If yes I would appreciate some help with it.
Thanks!
That's quite easy, isn't it? Simply download one of the offical bilds (sbf files), copy it (i mean if needed thing you need for flash like safe wipe) on sd card, wipe everything, boot into stock recovery (well i believe dl-mode) and flash official rom.
I was thinking about doing that and thanks for confirming it. What I am not sure about is if everything else installed that does not run in android, like 2nd init and other stuff lets call them , pre os, get deleted and only the stock firmware will be left. I will do this though and we will see how it goes.
Now do any of you helpful people have an sbf for Europe without blur UI in it?
A link would be helpful if so.
Thanks again!
Sbf cannot be flashed from sdcard! It must be done thru RSDLite. 2ndinit, etc will get wiped. If stuck in a boot loop after flashing, wipe data after stock recovery
Sent from my MB526 using Tapatalk
Quite simple. Wipe Data / Cache first via Stock Motorola Recovery. Flash SBF for your region. Voila! your phone is all stock again.
If you want a good De-Blur ROM try WIUI or if you still dont want the customizations move to MS2Ginger ->
http://forum.xda-developers.com/showthread.php?t=1140839

Categories

Resources