Hi, I have a rooted HTC Wildfire and was trying to install the CyanogenMod 7 ROM based on instructions here (http://forum.xda-developers.com/showthread.php?t=918072).
After wipe+format, I have installed the ROM in recovery mode and rebooted the phone.
Although the phone shows the CyanogenMod 7 startup blue android image, the phone keeps rebooting thereafter without starting up fully.
Can someone tell me what's wrong??? Thanks in advance.
bah. still trying and not working.
Which nightly have you tried ?
Sent from my HTC Wildfire using XDA App
Did you wipe /system under Partitions Menu also?
Yup did the wipe + format as per instruction. but had difficulty booting up CM7 build #34.
decided to install CM6 instead and it's ok.
Just don't understand why CM7 not booting up.
whoorderlaksa85 said:
Yup did the wipe + format as per instruction. but had difficulty booting up CM7 build #34.
decided to install CM6 instead and it's ok.
Just don't understand why CM7 not booting up.
Click to expand...
Click to collapse
It is probably because of the new kernel. Many users are reporting the same issue. To circumvent this, you have two options:
* Use an older Nightly. #0 and #19 are recommended.
* Flash #34, then, Flash HCDR.Kernel v4.1 from the HCDR.Kernel thread under Wildfire Android Development Thread, then reboot.
Is there an cm7 which also on the internet can and you can make calls.
Ihad it before but I can't call
guus_1995 said:
Is there an cm7 which also on the internet can and you can make calls.
Ihad it before but I can't call
Click to expand...
Click to collapse
Tried #19??
Related
Hey All,
First I want to apologize if this isn't the place for this thread or if this has been brought up before.
Now onto what I came here for. I have a myTouch 3G phone (the one without the jack) and I have rooted my phone a couple of months ago. The rooting process went fine and currently I'm running the CyanongenMod 4.2.15.1 rom on my phone. It's running fine as it should be. Now my dilemma is when I tried to update to CM 5.0.7 or 5.0.8. At first when I flashed the rom, I thought everything was fine during the setup process but then when it came to using any Google apps, none of them seem to work with the exception of GTalk and Google Maps. I've tried the troubleshooting guide where it says to do the fix_permissions but that didn't work at all. After about 3 days of trial and error, I finally admitted defeat and flashed back to CM 4.2.15.1. I also came to the conclusion that my phone will only take 1.5 & 1.6 roms whereas any roms 2.0 and above will not work correctly. I even tried to flash CM 6.0 RC1 and it got stuck at the green boot screen.
My question is there something wrong with my phone or am I doing something wrong? Has anyone else ran into this problem? Please let me know because I would love to have the 2.0 and above roms on my phone.
Thanks in advance
Did you do a full wipe and then upgrade?
Yes I did a complete wipe, even did the command that you do in fastboot
u gotta install the google pack i think....for that u will find it in cyanogen forums
If you mean by installing the gapps after flashing the rom, I've done that already. Also I've even reflashed the gapps again just to make sure and I also tried the fix_permissions and that didn't work either.
I also saw that the browser was acting funny too (not sure if that's part of gapps)
Sent from my T-Mobile myTouch 3G using XDA App
Hello,
In your sign, you're using an old rom with the old method of app2sd (on /system/sdcard/), newer rom uses /sd-ext/ but 1.6.2 recovery is not compatible with the new method.
Not sure but try to update your recovery with 1.7.0.
Good luck, Scargoll.
scargoll, i failed to mention that I'm already using Amon Ra's 1.7G recovery image. I need to update my sig (my bad). also as i stated before, i tried upgrading to CM 5.0.8 and running into issues, that's why i'm still running CM 4.2.15.1
Yup. Wrong section. I'll move to General when I get back home.
Google Addon: FRF91-MDPI-2
Mirror: http://kanged.net/mi...91-3-signed.zip
EBI1 Port:
Download: http://briancrook.ca...ebi1-signed.zip
MD5Sum: 30f00833c6b9e15027603be4cbe415cc
Are those what you tried?
jeff, if i'm correct the FRF91 Google Addon is for the CM 6.0 RC1 rom and i don't have a MyTouch 3G 1.2 32A phone to be using the EBI1 port.
Well, since you say so, your phone is just jacked.
Have you tried reflashing the whole ROM and GAPPS again? See if a different version of cyanogenmod works for you.
jeffakajeff said:
Well, since you say so, your phone is just jacked.
Click to expand...
Click to collapse
LOL...jacked how?
appledroid said:
Have you tried reflashing the whole ROM and GAPPS again? See if a different version of cyanogenmod works for you.
Click to expand...
Click to collapse
appledroid, i've tried relashing both CM 5.0.7 and CM 5.0.8 roms gapps. the roms flashes fine but when it comes to using the gapps (with the exception of GTalk & Maps), they either close without a warning or i get a app loop (GMail does that most before it finally closes without warning)
sounds to like your running out of space on a partition while flashing. try fireat's mtd partition hack and see if it works for u.
flash the 1.1 zip
flash cm6
flash gapps
flash 1.2 zip
and then reboot
chrisgto4 said:
sounds to like your running out of space on a partition while flashing. try fireat's mtd partition hack and see if it works for u.
flash the 1.1 zip
flash cm6
flash gapps
flash 1.2 zip
and then reboot
Click to expand...
Click to collapse
hey chris,
running out of space on a partition - are you talking about the space on the phone or on the SD Card? if it's the SD Card, not sure how that's possible when I have 4GB card (also it's not partitioned as of now but before I did have it partitioned)
if i follow this route, do i need to flash CM 6 or can I flash CM 5.0.8?
also where can i find the 1.1 and 1.2 zip files?
in any case, i'll try both to see what's up
um does anyone know what chris is talking about?
c'mon....anyone?
hey im not to sure why u cant switch to the latest cm roms. cause mine is doing fine on every updates.
i use clockworkmod recovery
try redownloading the rom. while downloading, watch ur downloading progress bar, makesure u have good internet connection. do not let the data connection change speed( switching from 3g to e or g) do not let phone switch from portrait to landscape.
if any of the above does happen you will have to cancel current download then redownload.
try to download cm6 rc3 - its 2.2 and it have lots of goodies. gapps are also preinstall
well i had this problem too... i was stuck on green screen... setup abort... gapps was acting up... so i did the above and everything is fine...
i hope this works for
rooted mt3g 32b cm6-rc3 htcClay 1.3
forgot to mention... since u have this problem, i recommend a full wipe... i dont kno if it is ok to flash without wipe from cm4 to cm5 or 6... flashing rom over another rom is wat i normally do... cause i hate reinstalling apps
rooted mt3g cm6-rc3 htcClay 1.3
Okay brief background:
Originally stock VFAU supplied Legend, updated to the stock Froyo. Rooted by (roughly) following the steps outlined in the How to root HBoot 1.01 thread and am now happily able to flash roms using ClockworkMod 3.0.0.6 "fake flash" update.zip
Was keen to try out CM7RC2 on this phone so I have downloaded the update and Gapps .zips from the Cyanogenmod wiki page.
Tried multiple times now to flash the CM7 update and the relevent Gapps, always formatting user data / cache / dalvik before hand. After the process, I am always able to boot into CM7 on the device, but it appears the Gapps update hasn't been applied properly / at all. For example - on initial boot, I don't get the google android setup wizard, so no way to link the phone to my gmail account. Gmail app isn't installed, and when I try to launch Market it just goes to a white screen for a second, and then back to the launcher.
I'm wondering if this is related to the fact that the phone is on HBOOT 1.01, and S-ON? or is there another explaination? eg, a specific kernel, or radio that I should be flashing before I try to flash CM7 (nothing is mentioned in the install guide over at CM wiki).
Thanks in advance.
are you shure ou downloaded the right gapps
the one touse is "gapps-mdpi-20101020-signed"
karlanal said:
are you shure ou downloaded the right gapps
the one touse is "gapps-mdpi-20101020-signed"
Click to expand...
Click to collapse
Hey mate, thanks for the quick reply! Just to clarify - are you sure this is the right version of Gapps for CM7 on the Legend?? Looking here under the "Google Apps Version" section it appears that the correct version for all devices running CM7 should be Gapps-gb-20110307-signed.zip and that gapps-mdpi is for CM6??
I tried your suggestion nontheless, and with that version of Gapps flashed - I'm now getting a boot-loop of the cyanogen boot animation
I'm on HBOOT 1.01 (Vodafone Legend) and CM7 was the first I tried, though it was back around the nightly build 31. I didn't have any issues and CM7 started up straight away. I realised I was missing all the Google stuff so did a separate flash, maybe you could try this. I'm yet to try the RC version hopefully no issues here...
EpicSauce said:
I'm on HBOOT 1.01 (Vodafone Legend) and CM7 was the first I tried, though it was back around the nightly build 31. I didn't have any issues and CM7 started up straight away. I realised I was missing all the Google stuff so did a separate flash, maybe you could try this. I'm yet to try the RC version hopefully no issues here...
Click to expand...
Click to collapse
I have tried flashing the gapps package as a separate flash (after the intial flash to CM7, booting into CM7, then reboot into recovery to flash Gapps), and the result has been the same as when I flash them together.
I had wondered about trying a nightly, but being new to CM roms please forgive my next question. To flash a nightly, do I first have to flash CM7 RC2, then flash the nightly, or can you just flash the nightly by itself, then Gapps over the top??
I'm definitely willing to give it a try at this stage.
Flashing the nightly won't need a prior RC2 flash, its a self contained package so you shouldn't have any problems. Hopefully the Gapps flash works this time.
black beard said:
Hey mate, thanks for the quick reply! Just to clarify - are you sure this is the right version of Gapps for CM7 on the Legend?? Looking here under the "Google Apps Version" section it appears that the correct version for all devices running CM7 should be Gapps-gb-20110307-signed.zip and that gapps-mdpi is for CM6??
I tried your suggestion nontheless, and with that version of Gapps flashed - I'm now getting a boot-loop of the cyanogen boot animation
Click to expand...
Click to collapse
yes i was wrong, gave you the wrong gapps suggestion
i was allways using "gapps-gb-20110120-signed" and all was working great
EpicSauce said:
Flashing the nightly won't need a prior RC2 flash, its a self contained package so you shouldn't have any problems. Hopefully the Gapps flash works this time.
Click to expand...
Click to collapse
Well tried flashing the latest nightly last night, full wipe, then flash, then reboot, then reboot into recovery and flash the Gapps and it worked!! Don't really understand why something like that wouldn't work with the RC
karlanal said:
yes i was wrong, gave you the wrong gapps suggestion
i was allways using "gapps-gb-20110120-signed" and all was working great
Click to expand...
Click to collapse
Thats cool mate - made me recheck myself anyway
I'm currently using the wildfire. I rooted it and installed rom manager.
I did backup my rom (CWRv3.2.0) and installed the wildpuzzle rom (Newest one).
But i think forgot to wipe off the data. After installing the rom, it booted fine but it says that my phone memory was low.
I waited for a very long time but it does not respond. Hence, i thought something was wrong and tried to go to cwr and did a factory reset.
But now it gives me a black screen after the htc logo.
And after 10 to20 minutes and it still does not respond. I went back and did a restore(before the wildpuzzle rom I've installed)and it came out that my phone cannot boot and stucked in a loop. (after 2 turns it went back to cwr)
I'm scared that i might bricked my phone.
Help please! Much appreciated!
When you do a Factory Reset in Clockworkmod, you need to flash a ROM again. Also, if you read the thread completely, WildPuzzle 2.3.2 does NOT work. It was released untested by danne (as he stated), and, various tests by users show it didnt boot.
EDIT: And if you are talking about Android 2.2 Sense ROM's, you will need to flash it using Clockworkmod 2.x. They are not supported on 3.x
So do i have to flash a new rom like CyanogenMod ? Sorry, I'm a complete noob at these. Edit: Its the Wildpuzzle 2.2 froyo v0.8 rom.
Clubbysupercharged said:
So do i have to flash a new rom like CyanogenMod ? Sorry, I'm a complete noob at these. Edit: Its the Wildpuzzle 2.2 froyo v0.8 rom.
Click to expand...
Click to collapse
Yeah flash the CyanogenMod 7 ROM. But before you install this ROM please make sure to Wipe the data, Clear cache partition and also to clear dalvik cache and then proceed to install the CM7 ROM
Yes! Thanks a lot! Flashed Cm7 Nightly Builds 2.3.4. Running perfectly
EDIT: Wifi does not connect lol, stucked on locating ip address.
Hello dear xda community.
I own a Defy+ with 2.3.6 stock Kernel and want to switch to CM7. (Do I need another Kernel?)
Which build do you prefer, I can't decide between:
7.1.0-11
Quarks nightly
Epsylon3s nightly
maniacs nightly
Basically I'm just looking for a stable AOSP/blurfree ROM, so which one is the stablest up to now?
Which of the mentioned ROMS need/work with the battery/camera patches and are there different versions of these patches around? (here and here)
Am I right that there should be no more problems than battery and camera functionality up to now?
Thank you in advance
Edit: Another question I forgot:
In the title of the 7.1.0-11 it is written "Android 2.3.7". So does this mean even though the zip doesn't contain a Kernel it does contain 2.3.7? I couldn't find a 2.3.7 kernel for the Defy+ elsewhere.
Edit 2: I found an answer concerning whether to use 7.1.0-11:
The latest nightlys are stable, don't use 7.1.0-11
Click to expand...
Click to collapse
Though thats a tough statement whenever it comes to nightlys, I assume I will trust him here.
Like I wrote to you (by PM) before, I don't own a Defy+, but I'd say go on and try the latest Defy+ nightly which is from Quarx at this time: cm72-20120308-NIGHTLY-Defy+.zip md5 checksum: 8df5562b60ded2978a38eb9ac21bdc8e .
Make a nandroid backup of your system (custom recovery / advance / backup&restore / backup all) before installing it and then see how it goes from there...
If it really doesn't boot up, you have problems with battery not fully charging, camera or other things, you can find solutions or ask again - but at least you'll have a nand to fall back on... so no risk involved.
I haven't tried that specific March 8th Defy+ nightly yet, but I bet that it is probably at 1 or 2 small fixes close to perfection and you won't regret installing it I assure you.
Just be patient at first boot and wait a good 5-6 minutes before thinking being in a bootloop and do anything crazy..
God luck.
I tried cm72-20120308-NIGHTLY-Defy+.
Wifi is not working ..
and battery yet to check..
also camera prob..
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Let me recommend CM7 WhiteRabbit Edition 1.3! Pure awesomeness + Aroma touch based installer. This means you can customize your installation (e.g. defy+ battery fix, what apps you want installed, witch wifi driver, etc)!!
Install the PLUS edition for gingerbread kernel!
hafizca said:
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Click to expand...
Click to collapse
I was using the CM7 for Defy+ 140312 build and everything worked fine for me! Also played all sorts of games like Dead Space, Shadow Gun with ease!
you should try WUIU:http://forum.xda-developers.com/showthread.php?t=1161110
works great!!!!
The whiterabbit version problem
Hey
i did download the whiterabbitplus version as i has android 2.3.6 with kernel also 2.3.6
i rooted it as mentioned using the latest superclick
i theninstalled sndinit 2.0 and attempted to enter recovery but i got the triangle with the xclamation mark so i installed clockworkmod and it got me into recovery alright
here i format cache ,data wipe,factory reset etc and say install "zip from sd card "
auroma installer starts off fine works upto letting me select the options and everything ...just when it says "click next to start " when i do ..it just says
system/mount
error(system/mount) fail or something ...
and pretends its complete and asks for reboot
after reboot i discover no changes and it just acts like a facotry reset too place and i need to configure everything again
ive tried everything on the net ..please do help ..should i flash a lower version like froyo and try again ??
Maniacs builds are great, you should check them out.
Johnny_Queste said:
you should try WUIU:http://forum.xda-developers.com/showthread.php?t=1161110
works great!!!!
Click to expand...
Click to collapse
Sag1e said:
Maniacs builds are great, you should check them out.
Click to expand...
Click to collapse
Please, guys, stop the confusion. Both of those are Froyo only.
@athenus Have you managed to flash any ROM? From those you have mentioned...
CM7.1 - Froyo only
maniac's builds - Froyo only
Epsylon's builds - there are both Froyo and Gingerbread available
Quarx's builds - both Froyo and Gingerbread available <- this should be your choice. The latest Quarx's builds is awesome and you can find it here - http://quarx2k.ru/cm7-nightly-defy+/
P.S. Quarx is currently the only developer that actually owns a DEFY+.
If you are confused still, feel free to PM me, as I can't keep with all the threads I've posted in
hafizca said:
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Click to expand...
Click to collapse
I might be wrong, but the problems you have described having make me believe that you did not use and set the Defy Baseband Switcher app properly. Am I right/wrong?
Phone carriers around the world do not all use the same radio frequencies to receive/transmit phone signal and after any first install of cm7, you have to use that included app, give it root access, select the baseband that correspond to your location/carrier and reboot. Failing to do so causes bad signal eception, high battery drain and hot phones...
I hope that it was your problem because it will make it very simple to solve for you then.
EDIT: I believe that the baseband can now simply be changed under: Device settings/Baseband selection - no more dedicated app...
Installation failure of CM7 latest Joudan-plus
I hope someone can help me please . . .
Having rooted the phone successfully, and having followed all the relevant instructions (including installing first the various utilities - Titanium, 2ndInit, etc), to upgrade my Defy+ Build 4.5.1-134_DFP-231 with the latest CM7, I copied the CM7 zip to my Defy+ then installed it using 2ndInit - success.
Then, on the reboot, the phone just hangs at the M logo.
After doing the normal recovery, and trying to install again, these messages appear:
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Can anyone suggest what I should do next to recover the situation?
Installing CM7 on Defy+
Following my previous posting, I installed the nightly Jordan plus, from the night before - the only other one available.
That installed without any error message,
However, upon normal reboot, the phone hung at the M logo.
Any ideas please?
INSPEC said:
Following my previous posting, I installed the nightly Jordan plus, from the night before - the only other one available.
That installed without any error message,
However, upon normal reboot, the phone hung at the M logo.
Any ideas please?
Click to expand...
Click to collapse
Wipe data/cache?
Sent from my ATRIX HD using XDA Free mobile app
Installing CM7 on Defy+
Thanks for the response.
Yes, I did first wipe data and cache.
And have tried repeating the installation (including wiping).
Still hung at M logo.
INSPEC said:
Thanks for the response.
Yes, I did first wipe data and cache.
And have tried repeating the installation (including wiping).
Still hung at M logo.
Click to expand...
Click to collapse
Which recovery are you using? The normal one or the one designed for bigpart?
Sent from my ATRIX HD using XDA Free mobile app
Installing CM7 on Defy+
Thanks again for response.
I am using, from the xda posting,
2ndInit Recovery Installer v2.3 [Updated: 24-April-2012]http://forum.xda-developers.com/showthread.php?p=23465603
Installin CM on Defy+
This is an update on a previous posting of mine . . .
It read:
I hope someone can help me please . . .
Having rooted the phone successfully, and having followed all the relevant instructions (including installing first the various utilities - Titanium, 2ndInit, etc), to upgrade my Defy+ Build 4.5.1-134_DFP-231 with the latest CM7, I copied the CM7 zip to my Defy+ then installed it using 2ndInit - success.
Then, on the reboot, the phone just hangs at the M logo.
After doing the normal recovery, and trying to install again, these messages appear:
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I have subsequently performed:
Wipe data/Factory reset, then
Wipe cache.
and then trying to install three different version of CM - they are, CM 7 (both of the available Jordan Plus Nightlies), and then a CM 12 from another posting here in XDA.
All three resulted in the 'signature' problem. But the filename of all three files said they were "signed".
So can someone please explain . . . ?
---------- Post added at 02:25 AM ---------- Previous post was at 01:35 AM ----------
I have now discovered the enable/disable signature check . . .
Having disabled the signature check, and repeated all of the steps in my previous posting, and wiping the Dalvik cache, the phone still hangs at the M logo on reboot.
Any suggestions please?
Installing CM on Defy+
Following on . . .
Could this be a Bootloader problem?
I see references to similar symptoms being fixed by unlocking/relocking the Bootloader.
But my understanding, from the Cyanogen Mod website, is that CM looks after this automatically . . .
Hello,
bricked my defy a few days ago after rom flashing failed. Phone wasn't booting properly, always showing the big red 'M' letter. Fixed it via rds tool, roms are running again but they don't keep the settings.
After every reboot I have to do systems setup again (language, accout, time). It's like having a wiped phone.
What's going wrong? What can I do?!
Few odds:
- can't wipe dalvik cache in recovery. Something pops up very short, couldn't read.
- cannot install apps. Market doesn't start Download.
...
Flashed my rom+gapps again. This time market tells me there's not enough memory on my phone.
Anything's wrong with my recovery? How do I install a new one? Via sndinit again? Any alternatives?
Hi there,
I had exactly the same problem few days back when I tried to make my phone dual boot and wanted to run CM7.2 as primary ROM and CM10 as a test ROM. Experiment failed miserably and the CM7.2 was wiped out and on top of that CM10 was overwritten as primary ROM. Then the same problem as you. It was going through boot loop and every time I had to start the phone setup.
I had to flash SBF using RSDLite and root it again using superone click.
Then installed the CM7.2 again and then later flashed CM10 Nightly just on top of the CM7.2 with out wiping the data.
CM10 I used was Quarx one from Aug 25th and it works great.
I know I am not that smart but I try stuff so I can experience latest stuff.
Not sure if this helps but, let me know if you need more details.
Regards
Kalyan
Sent from my MB525 using xda app-developers app
In the meantime I found out that /data isn't and can't be mounted...
Maybe you should start again with flashing a stock sbf...
Edit: or check out this :
http://forum.xda-developers.com/showthread.php?t=1787541
Sent from my MB525 using xda app-developers app