problem booting up cm7 - Defy General

i've just flashed cm7 on my defy, the phone starts (with the cm7 logo) and then it asks me to do those things in the beginning (touch the android logo, sign up for gmail) but before i can do anything the cm7 logo pops up, and then it asks me to touch the android logo all over again, and it repeats in a cycle, i tried flashing again but the problem remains, how can i fix this? and i've just found out another problem \= when i try to restore my backup it says "Error while flashing boot image" and im pretty sure my battery is charged, how can i fix any of these problems? \=

try to flash new cm7 rc0 rom /
before flash it please make wipe data and cash too .
hope it work fine this time .

attention u cant update your phone from 2.1 to cm7
u must flash 2.2 rom and then update to cm7

I did wipe the data and cache, and i flashed from 2.2.2
but it still happens, i tried flashing rc1, does it matter if its rc1 or rc0?
i've read somewhere that i need to flash a different kernel, what exactly does it mean? im kinda new to this stuff

CM7 comes with its own kernel though, so that shouldn't be the issue here.
A kernel controls much of the hardware on your device, such as your voltages, min/max cpu, wifi, bluetooth etc... You flash them through recovery like you did for a rom, or use kernel manager from the market.
You can look for a kernel that works on Android 2.3 for AOSP on the Defy. Kernels are device specific.
Hope this helps a bit.
Sent from my PC36100 using XDA Premium App

AOSP? :X and how can i tell if the kernel support whatever i'm looking for? and i've used the roms that were posted here in this forum (for the defy)

8nexus8 said:
AOSP? :X and how can i tell if the kernel support whatever i'm looking for? and i've used the roms that were posted here in this forum (for the defy)
Click to expand...
Click to collapse
I think he wasn't talking specifically about defy phones (look at his signature) The kernels you found on the defy forum are of course appropriate for the defy, no need to worry. Besides, it doesn't seem like a kernel problem at all, more like an application problem. Are you sure you clear cache and data? Most data in android phones is stored on a database format,so you could have incompatible data format being read on your CM7 install and crashing the application.
BTW, I found rc0 to be really stable, other than camera at low ligth conditions, it's great.
Sent from my MB525 using XDA App

i tried again with the rc0 but i get the same thing =[ this is very frustrating, and of course im sure i wiped, i did it 3 times to make sure but it still didnt work and it also screwed up my backup

for update to cm7
1- update your defy to ofical 2.2 with rsd- lite
2- after flash 2.2 u can update to cm7 or motoginger rom

Related

Cm6 & Shadowrom Bootloop after install?

For two months I have tried to install Cm6 and currently shadow rom. Every time after install from clockwork or nandroid I get the same bootloop splash htc screen. I have installed other roms with no problem....there must be a common issue with cm6 & shadowrom. I have wiped full, cache, davlik and even formated system cache etc. I have a 2.x radio kouche kernel and newest hboot. I've tried changing sd cards etc. No avail......any suggestions would be appreciated.
SamuraiXDroid
I would try wiping dalvik/cache before the flash, flashing, then wiping dalvik/cache again before the first boot of the new rom. I would also suggest trying kings kernel or koush's test kernel by flashing them from cwm recovery directly after the rom.
Aside from that, I could only guess that you might have a corrupt area preventing a full install of your rom/kernel which isn't too uncommon but which I have no experience with. I've heard there are ways to get around this by building the kernel manually or by restoring it from another nandroid (say king's on a ruby nandroid? though I'd venture to guess Ruby would have the same problem), but it seems fairly difficult.
I'm not a developer, but I hope my suggestions can hope point you in the right direction. I'm using the latest nightlies of CM6 and they are awesome. I hope you get the chance to try it.
Thanks jaguox for such a quick reply. So I tried this.method on both cm6 and shadowrom. Wiped full wiped cache wiped davlik. Installed rom and gapp and kernel. Tried koush and kingkernal....wiped davlik...cm6 boot loop.....shadowrom brings me to android touch screen initial setup. I try to touch screen but my phone dosnt respond....screen freeze. Sussesful installs I've had are sky raider virtuous most.sense roms...the only froyo I have that works is ruby...my fav right now. I would love to have cm 6....I've posted on this forum a few times as well as cyanogen forum. I hope im not the only one with this.issue.......
SamuraiXDroid
Here are some more ways to potentially solve your problem. Again, I am not a developer so I am just mentioning a few solutions that might work, I am not entirely sure what is wrong with your device. I'm just trying to help you hammer away from all sides.
Are you wiping data manually too? People have noted success before where they had none before by wiping data/dalvik/cache twice before flash and once after. Not sure why this would solve anything but it is worth a try.
Try installing cyanogen without GApps (I do this anyways with the nightlies since it seems to be corrupt for some reason) and then installing them later if it boots correctly.
I use the Paid rom manager for the ease of use for nightlies, but here is a web link to the nightlies which you can try if you don't have paid: http://mirror.teamdouche.net/?device=inc They are more up to date and stable at this point than 6.0.2 was (for me at least). I am using build 100 and have tried the packaged in kernel, koush test 6, and adrynalyne's, and all work well.
Adrynalyne has another kernel for AOSP roms you can try: http://adrynalyne.us/?p=79
You can also try using the phone to reformat one of your SD cards just to eliminate that potential pitfall, though I don't think you would be getting that far anyways if it was not formatted correctly (Menu>Settings>SD card). This will wipe any data currently on your SD card.
Now, I would wait for someone else to provide confirmation that this should work since I haven't done it personally, but you could also try restoring boot.img from a Ruby Nandroid with KK1/2 installed (Install Ruby, install KK, make nandroid backup, install CM6 w/o Gapps, nandroid>advanced restore>select ruby nandroid>Restore boot). This should restore a working AOSP kernel for CM6/shadow to use however I am unaware if there are any other consequences. I also suggest KK or adrynalyne since I do not know what Ruby uses and KK and adrynalyne have both worked for me on CM6. The reason I think the kernel is not installing correctly is because your touchscreen is not working and AOSP roms use a different driver than sense roms for it. I could be completely off base however.
Also, out of curiosity, which radio version exactly are you using?
Hi Jaguox,
Thanks again for the help here is what I tried. I do own the market app ClockworkMod Revovery v2.5.0.5/rom manager. I came from Ruby 1.1.1 with the newest kouch Kernal and radio 2.15.00.07.28. I then wiped data, cache and dalvik twice. I then installed cm nightley 96&98/shadowrom (two seperate installs of course for each rom). I then installed Adrynalyne/Kingkernal kernals and wiped dalvik cache once more. I did not install gapps and let the rom boot. Interesting enough the roms bypassed the intial setup and booted to the home screen. But both roms with both kernals still would not let me have touch access to the screen. So I could see the roms but I couldnt touch them...aaaahhhhhhh the irony. I also tried a reformatted sd card.....same outcome. One time out of the hundred I have tried in the past two months allowed me to initiate my account in a cm nightly and access apps. I rebooted after a fix permission and got a boot loop. That was the farthest I have ever made it. Its strange that both these two roms that share the same dna give my phone the same effect. I appreciate anyones help in solving this mystery.
Thanks in advance!
?
SamuraiXDroid
Same issue on my Dinc. I have.wiped, rewiped and.still.the same out come on 2.1. I did not have this issue when I installed the first release of SR a while back. I have no other issues with other ROM's. Help?
Sent from my ADR6300 using XDA App
So shadow rom first release woked for you? There must be some common denominater for why our phones cannot take certain aosp roms? Ruby works but not cm6 or shadow......very strange.
So I think shadow rom found the fix to the issue I was having....hopefully this thread helps anyone in the same vote as me.
http://forum.xda-developers.com/showthread.php?t=808972

[ROM] Hero CyanogenMod 7 Nightlys-Android 2.3.2 Gingerbread (2011-02-27)

Now CM7 Nightlys Android 2.3.2 Gingerbread available:
http://mirror.teamdouche.net/?device=hero
Gapps:
gapps-gb-20110120-signed.zip from here http://goo-inside.me/google-apps/
All changes to the source code, from which the nightlies are built from, are listed there.
It is not suited for end users but hey, it´s something where you can track the current progress.
http://review.cyanogenmod.com/#q,status:merged+project:CyanogenMod/android_device_htc_hero,n,z
HTC Hero @Github
is this the same as beta3?
CM7 Nightly ROM zip is a little bit smaller,maybe some little fixes
and updates there,but don`t know,not tested at the moment.
Nightly ROM has also the the other kernel "2.6.29.6-flykernel-12pre2"
Beta 3 has "2.6.29.6-flykernel-12a" kernel!
But Flykernel-12a is newer than Flykernel-12pre2, isn't it? Also, could anybody tell me how nightlies work? Is it like you get updates pushed to your device through the CyanogenMod menu, like OTA? Please explain lol
12a should be newer,but don`t know why now 12pre2!
Maybe more optimized for CM based ROMs.
You can ask erasmux:
http://forum.xda-developers.com/showthread.php?t=730471
wow,there is something that is good for expecting
12a will be used soon if I read the commits at github:
https://github.com/loxK/android_device_htc_hero/commit/53b03bf186cd4a4d47b3604cd6290e8dc8cfdb1b
I believe it was something about CM asking for IPv6 to be build as module, while in 12a this is included statically (straight into the kernel).
Krizp0 said:
Also, could anybody tell me how nightlies work? Is it like you get updates pushed to your device through the CyanogenMod menu, like OTA? Please explain lol
Click to expand...
Click to collapse
I second this question. I've never used nightlies before. Could someone please explain how they work?
Download and flash them. No OTA update (but its a great idea).
Wipes in between are not necessary but sometimes you need them.
Not every new nightly is better then the last one (performance).
i think that my Hero doesn't like these 2.3 roms ... i've flashed few of them, none will boot.
could it be the recovery or something ?
1immortal said:
i think that my Hero doesn't like these 2.3 roms ... i've flashed few of them, none will boot.
could it be the recovery or something ?
Click to expand...
Click to collapse
Yeah. You need the lastest recovery 'cause of some drivers.
RA-hero-v1.7.0.1
Link: http://forum.xda-developers.com/showthread.php?t=561124
thats the one i'm running, and also tried the other one, from clockworkmod, same thing:
1. wipe EVERYTHING.
2. WIPE again.
3. flash the rom.
and .... nada, nothing.
even replaced the sd card, still same crap.
this Hero ran cronos twice, and since then... not a single 2.3 rom.
2.1, 2.2 , no probs, reflashed the radio, tried everything.
wtf ???
1immortal said:
thats the one i'm running, and also tried the other one, from clockworkmod, same thing:
1. wipe EVERYTHING.
2. WIPE again.
3. flash the rom.
and .... nada, nothing.
even replaced the sd card, still same crap.
this Hero ran cronos twice, and since then... not a single 2.3 rom.
2.1, 2.2 , no probs, reflashed the radio, tried everything.
wtf ???
Click to expand...
Click to collapse
Hmmmm maybe some are boot oc but i dont think so.
How long have you waited till you think its bootlooping? Do you only see the "HERO"-screen or do you see the bootanimation? keyboard lights are off all the time?
can't even see the bootanimation. only seeing the spl logo, and it reboots there.
1immortal said:
can't even see the bootanimation. only seeing the spl logo, and it reboots there.
Click to expand...
Click to collapse
huuuuuuu crazy Okay sorry i dont know. You can create a logcat (dont ask me) and post it over the CM forum. Also you can tweet Lox and show him your log. Maybe he know anything.
or ... i could recreate the "will it blend ?!" with this phone ...
1immortal said:
i think that my Hero doesn't like these 2.3 roms ... i've flashed few of them, none will boot.
could it be the recovery or something ?
Click to expand...
Click to collapse
yes, woudl be recovery and your wiping within the recovery OR it could be a previous rom or something you did while using a previous rom that has somehow messed up one or more files on the phone. there are parts of the phone's memory that can sort of seem to get stuck. I can't explain more as I have no further details other than first hand experience with this phenomenon.
wiping several times in a rom, or wiping fully (all types of wipes in recovery menu) then flashing a totally different rom (like a 2.1 sense rom) then wiping fully and flashing the rom you want to use could maybe fix it - if in fact this is the cause of your problem.
try wiping ONLY dalvik cache AFTER flashing the rom. i use recovery 1.6 and everything works.
Found this,seems there is another bug at Android 2.3.2 too.
Not only the SMS bug!
Android 2.3 Shows Security Bug, Can Gain Access To Content On microSD Cards
http://www.talkandroid.com/28696-and...microsd-cards/
Have you tried wiping with fastboot? Then flash the ROM.
posted from the other side of town with a 2nd class stamp

[HOW-TO] CyanogenMOD on Telstra Defy

Hey everyone,
Just hope to make things a bit easier for all fellow aussies trying to install Cyanogen 7 on there Telstra Defy. Links and attachments at the bottom.
First thing is, so far as i can tell, 2nd-init does not run Clockwork recovery properly from the telstra stock SBF. On this ROM you will probably get the "unable to mount SDcard" error.
Also do NOT install clockwork recovery during any part of this, it comes with
2nd-init and does not need to be installed seperately (can cause problems if you do)
This is the series of steps I took to get it working.
1. Copy Defy-Cyanomod 7 Beta and Google Apps onto SDcard
2. Root phone with SuperOneClick 1.7 (1.8 doesnt seem to work)
3. Install 2nd-init (App is on market or below)
4. Reboot phone twice
5. Use RSD Lite and flash the Official Froyo Korean v3.4.2-74 fixed SBF
(This ROM allows you to downgrade back to the stock Telstra ROM and also
allows you to install CM7 from 2nd-init+custom recovery)
6. Reboot phone (2nd-init will still be installed after this SBF is flashed)
Your phone will now go into a Motorola boot loop. (this is ok)
7. Let the phone cycle through 2 complete loops.
(CM7 seems more stable once I did this)
8. On the third cycle enter 2nd-init (Volume Down when blue light is on)
9. Enter custom recovery from 2nd-init
10. WIPE Data/Cache
11. Install Defy-Cyanogen 7 from SDcard
12. Reboot phone and let CM7 load up
13. Reboot again and enter 2nd-init+custom recovery and install Google
Apps from SDcard
14. Enjoy some CM7 goodness
Thanks to everyone that made these things possible.
Links
Defy-Cyanogen 7
Latest Google Apps
http://forum.xda-developers.com/showthread.php?t=1033654
Korean 3.4-74 Fixed SBF
http://defy-sbf.4shared.com/
I'm running cm7 on my telstra,defy. At this stage no problems, only thing was i had already flashed a non-downgradable sbf. But for warranty purposes i can still go back to telstra by flashing a fixed telegraph Sgt and restoring with stock telegraph nandroid backup.
Sent from my MB525 using XDA App
Can you post a picture of the "About Phone" screen after restoring stock from non-downgradeable??
This is my second defy and Telstra wouldnt replace my first one because i didnt have the stock ROM. They can tell if its correct or not.
That's what I was thinking, my about screen after going back to the fixed sbf is not the telstra one.
Sent from my MB525 using XDA App
I will when I get a chance, don't suppose anyone could post an about screenshot of the stock telstra one.
Sent from my MB525 using XDA App
I suppose it depends on which tech you get at telstra, some will report it, others will just fix it.
I bricked mine while trying to produce a bufer overflow and divide by zero in the locked bootloader. Was getting some results until it bricked
This is what my about screen has after restoring nandroid and flashing fixed Telstra sbf.
System version: Blur_Version.2.26.0.MB525.Telstra.en.AU
Model Number: MB525
Firmware version: 2.1-update1
Baseband version: EPU93ST2_U_03.03.00
Kernel version: 2.6.29
[email protected] #1
BPFlex version: USAJRDNEMARAB1BTEL02A.OR
APFlex version: GAS_ASIA_USAJORDANTELSTRA_P033
Build number: JRNEM_U3_2.26.0
I would be intetested so see what a stock Telstra one says.
For now I've returned to Beta3 CM7. I had basically done the same as you to install, only difference is I used this fixed sbf, 3.4.2_155-002_DEBLUR
Cheers
I'll be changing mine back soon to get some things off my backup.
When i do i'll post up what it has on the "About Phone" screen
Thanks, I think the main one that will be different is the kernel version.
Sent from my MB525 using XDA App
Help...
The rom is perfect, very fast, so far so stable. Only
I noticed 2 bugs so far. 1. The camera's zoom, but that nothing
affects. 2. Skype does not connect here, / does anyone know how to solve
this? Put username and password, starts to connect, it restarts.
Someone managed to solve this problem?
CM7 Beta 4.1
Congratulations Quarx
Thanks
Hey, first of all thanks heaps for making this guide, thanks to you CM7 is finally running on my Defy. I have one problem though and just wanted to see if anyone else did: I can't play youtube on my Defy at all (through the app or m.youtube.com).
Is everyone else having this issue?
*Edit* I've seen a lot of forum posts from mid-last year relating to this, is this issue still unresolved or could this be a bug in the Defy CM7 port?
I've discovered that it will play youtube (both wifi and 3G) but it will only play HQ videos... While inconvenient, I can work with that
Thanks for the how-to+
Dazmonic said:
3. Install 2nd-init (App is on market or below)
Click to expand...
Click to collapse
For the idiots like me out there installing 2nd-init from the market isnt enough you have to run the file aswell by installing it from inside the 2nd-init program itself, i needed to reset my phone after using super one click for 2nd-init to be granted "superuser status" so it would run properly.
Also once you've chosen the cryogen mod file from the bootloader you can then go back to install the google apps file.
After stuffing up the 2nd init program I needed to reflash the origional telstra files, then repeat the guide.
All seems good now, and thanks alot for the guide. I'm sure i would have really botched it up with out it.
Dazmonic said:
I'll be changing mine back soon to get some things off my backup.
When i do i'll post up what it has on the "About Phone" screen
Click to expand...
Click to collapse
Have you changed back yet?
Sent from my MB525 using XDA App
hj all !
can u give me link download room fix sbf of KOREA ? i can't download it on 4share,because it's emty..
thanks bro
Dazmonic said:
5. Use RSD Lite and flash the Official Froyo Korean v3.4.2-74 fixed SBF
(This ROM allows you to downgrade back to the stock Telstra ROM and also
allows you to install CM7 from 2nd-init+custom recovery)
6. Reboot phone (2nd-init will still be installed after this SBF is flashed)
Your phone will now go into a Motorola boot loop. (this is ok)
Click to expand...
Click to collapse
My Defy is in the post and I will try install Cyanogen when I get it, however I would also like to try a blur free Froyo Rom so I was planning on installing the Nordic fixed ROM in step 5. and having a play with it before continuing the process. Is this possible or will I get a bootloop like you mention in step 6? Is the Froyo ROM used in step 5. useable or not?
Dazmonic said:
Korean 3.4-74 Fixed SBF
http://defy-sbf.4shared.com/
Click to expand...
Click to collapse
Has anyone got a copy of this SFB they could upload somewhere? It looks like all 4shared data has been pulled... see the updated 1st post here: http://forum.xda-developers.com/showthread.php?t=966537
I'd love to get a copy of this SFB so I can do these instructions by the book...
Thanks
Is there another SBF we could use besides the korean one? Does it mean if we use another SBF then we won't be able to flash back to the default telstra one?
****, Telstra are actually checking firmware versions before repairing known issues like the earpiece?
I flashed the China Froyo ROM from ages ago. Probably not downgrade-able huh. Does the upgrade to CM7 process change if you're already on Froyo?
Official 2.2, looking for some CM7 goodness
Hi guys,
I found this page to be a godsend, detailing exactly what i want for my device.
problem is now that Tesltra have updated to 2.2 and the links to the Korean fixed file seem to have all been nuked, im not sure what to do, im a super noob (yes i watched the intro video
I have rooted and flashed CM7 on my desire and want it on my Defy!
so if someone could kindly explain what substitutions (if any) are needed or a link to the files required as from what i understand, if you flash to an official 2.2rom larger then 50MB then you cant downgrade to factory ?
TLR Have Telstra Defy with Telstra 2.2 want CM7 - Halp please

[Q] Defy won't update - says it has, and more errors

Whatever I try, using System Recovery/Clockwork Recovery, when I boot up the phone it's still UK 3.4.3-11 Froyo, but now with a red motorola logo (Nordic firmwire I flashed I suppose) .
When wiping in recovery I get these errors: "can't mount /dev/block/mmcblk0p2 (File exists)" and "error mounting /sd-ext/!".
I've create a FAT (should this be FAT32?), Ext2 and Linux Swap partition on my SD Card.
My original aim was to install CM7 from Quarx. Here's what I did:
Stock Defy UK (Other than root)
Used clockwork recovery to wipe and update to CM7
Booted fine (CM7/2.3), tried to then install gapps as an update.zip, then got stuck on boot at "M" screen on every boot
Used RSD lite to flash 3.4.3-11 UK with Blur
Superoneclick etc., tried to install CM7 again, had no effect
Used RSD lite to flash 3.4.2_177 Nordic - comes up with red logo, but hasn't updated to the actual blurless froyo
Tried again to install CM7, had no effect, still have the 2 errors on wiping
I've also found that when using stock recovery, it no longer does anything when I press the bottom right of the screen, it just stays at the green robot screen, I have to remove the battery.
I did get an app2sd error, which was why I partitioned the SD card using Clockwork recovery (bad move?), I then did it on my PC instead with an SD card adapter.
The phone's not bricked, since I've got a working 2.2 rom, however I've no clue what I've done to make it like it is now, and I can't install CM7 using clockwork recovery and the default recovery doesn't work.
I think fixing those errors might do the trick? Any help would be appreciated.
I am also not able to install quarx rom, tried several times it does not boot and I had to reflash the sbf to get the phone working. Btw I do no have sd partition.
What I did was from cloclwork I tried restore, shall it be install from zip. No idea why I cannot get it running. I have nordic 005 at the moment
Sent from my MB525 using XDA App
...maybe you guys should start to read a little more before attempting flashing any ROM...
If you would have done that, maybe you would have noticed that some people warned about some mounting of the SD card problems in some instances (I don't remember the specifics at this time..I beleive had to do with Super1click version used to root)
And most importantly:
that for CM7 installation instructions ask you to use '2ndinit' recovery and NOT CWM.... In fact you should even avoid having CWM recovery installed before starting the process...
I'm a noob too guys, I sometimes appreciate the help I can get from a post here. But I try my best to find existing answers and read as much as I can on the subject first. Obviously, you guys did not do your homework on this one.
[] AL [] said:
...maybe you guys should start to read a little more before attempting flashing any ROM...
If you would have done that, maybe you would have noticed that some people warned about some mounting of the SD card problems in some instances (I don't remember the specifics at this time..I beleive had to do with Super1click version used to root)
And most importantly:
that for CM7 installation instructions ask you to use '2ndinit' recovery and NOT CWM.... In fact you should even avoid having CWM recovery installed before starting the process...
I'm a noob too guys, I sometimes appreciate the help I can get from a post here. But I try my best to find existing answers and read as much as I can on the subject first. Obviously, you guys did not do your homework on this one.
Click to expand...
Click to collapse
I did in fact read around before I started, obviously in the wrong places or not enough. I've been pretty naive but all the guides I saw recommended that recovery, I must have missed the posts about 2ndinit (which sounds a lot easier). In fact I hardly read the actual CM7 thread since it's around 190 pages long.
It's interesting you noted superoneclick as the first time it worked and I used z4root.
I think for now I'll just use what I've got, which is ultimately better than what I started with (2.1), it's just a bit worrying as those errors I'm getting seem to suggest I've messed up the internal storage; and the default recovery won't work.
Probably installing a beta CM7 wasn't the best idea anyway since I'm very new to this.
Thanks al
I tried with cw recovery only. Tonight will try with 2ndinit. my sys info nordic 177_005 will I be able to get beta4 straight installing the zip
Sent from my MB525 using XDA App
Hi al[]
I tried booting into 2nd init boot but nothing comes up. Just blank screen any idea
Sent from my MB525 using XDA App
binodnepal said:
Hi al[]
I tried booting into 2nd init boot but nothing comes up. Just blank screen any idea
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Have you read this one:
http://forum.xda-developers.com/showthread.php?t=1043420
and for the recovery:
http://forum.xda-developers.com/showthread.php?t=1032212
Other than that, I will leave it to others to guide you on this...they'll do a better job than I would.
Sorry if I sound/ed rude in my post above...but was before 1st coffee of the day
Last note: on my side, I'm waiting (more or less) patiently...
As seen here http://forum.xda-developers.com/showthread.php?t=1033654&highlight=CM7
CyanogenMod 7 for Motorola Defy
Status Beta4:
Works:Wifi, SD-Card, 3D, Auto-Brightness, LED, Photo Camera with Flash, Video Camera(H264), GSM/3G, Bluetooth +Headset + HID, Sensors, GPS(have bugs)
Not works: aGPS, FM-radio, 720p & WVGA Recording.
BugList:
- some people say that they have wifi problems <---
- DroidWall/Iptables - not work <--- <--- <---
====>>>> So I will wait for that "tiny detail" [DroidWall/IP Tables] to get fixed before testing out any CM7 on my phone.
I like DroidWall apk and I also like to have a relative control on which app can access the internet...
Some of my apks 'might' not be so 'official' [..let say] and who knows what kind of party they're having in my phone....
I got it working and its quite fast. GPS works for me. Camera photo works but not the video. Will test other later. Quadrant score is very high not sure if it is correct. I got 2200
Sent from my MB525 using XDA App
Anyone having issues with music player stopping after few songs in cm7 beta4
Sent from my MB525 using XDA App

[Q] CM7 nightly doubts.

Few n00b questions.
Firstly, how do i flash a nightly on my phone? lets say im running ofw 2.2 SEA edition? Do i follow the same procedure as if to flash RC1... do i also need to flash gapps similarly.
Secondly, are the links on quarxs' CM7 for defy thread up-to-date? or are there newer versions of gapps and nightlies floating around somewhere
Third, i have noticed that there is an issue with network and wi-fi when i flash cm7 RC1 over the nordic sbf. when i go back to official 2.2 SEA there is no hassle at all. Since i live in india i was wondering if that was the issue. I can easily take care of the network problem using "baseband switcher for defy" but it still doesnt help the wi-fi problem.
My question is.. will using the new BOOTSEA nightly solve this problem. I am assuming from the name is boot"SEA" im assuming its built southeastasia specific.
Fourth, ive used CM7 RC1 for a while and apart from the wifi issue i got problems with camera and video... it absolutely doesnt work, wether it be in potrait or landscape or whatever setting... the app just force closes. Any fixes for that.. ive got green lens.
please help!!! and i hope other similar questions can be added by members here so as to make this thread an FAQ for distressed users like me.
Thanks
Flash a Froyo ROM.
wipe all (data/cache/Davilk)
Test all works
Root your defy
Install 2d_init
Reboot twice (i dont know its necesary yet)
wipe all (its no necesary but for me is the only way works ok finaly the CM7)
Go into clockwork recovery. After reboot wait until led go blue then push vol down
Install zip from memory card (You must copy on a RCO o RC1)
Reboot
Test your phone
If you want, use same way for install nigthlys
sorry for my english
good look

Categories

Resources