Database Develop

[Q] Cyanogen 6 GApps

Using Clockwork, I was able to get Cyan6 on my phone but whenever I opted to include Froyo GApps in the download ROM part, I got "corrupt zip" error multiple times. Now I am running Cyan6 just fine , minus the Market et al. Any ideas?

You can get the current version of the Gapps add-on here:
http://forum.cyanogenmod.com/files/file/119-google-addon-hdpi-20101008/
Flash the downloaded zip either from ROM Manager or from custom recovery.

cmstlist said:
You can get the current version of the Gapps add-on here:
http://forum.cyanogenmod.com/files/file/119-google-addon-hdpi-20101008/
Flash the downloaded zip either from ROM Manager or from custom recovery.
Click to expand...
Click to collapse
ROM Manager / Custom Recovery, unable to recognize zip. Says (bad). However, on going back to ROM Manager, was able to download and flash. Thanks for the lead though
I did notice that reboots .... haphazard I should say are happening on device now. It's fast too, {compared to stock} esp when I try to download certain apps from market....will download fine, but when the installing dialogue appears on the menu bar, it reboots. Thoughts..

No idea, sounds like something is amiss. Is it possible you have an HBOOT version that isn't playing nice with the method you used to flash custom recovery and CM6? Are you running a Froyo radio version that is compatible with CM6?
OH - and I almost forgot - did you wipe data/cache when you installed CM6? If you didn't then you may find that CM6 boots up but acts very strange and would give you a world of problems.

Wiped data and cache and that did it. Thanks.
Sent from my Nexus One using XDA App

[Q] Problem flashing from Fresh 2.4 to Cyanogen 7.0.x

I've tried to look everywhere for info on this issue and the closest I got was in the developers thread where someone was going to flash from Fresh 2.4 to CM 6. Apologies if I'm completely dense here.
There seem to be tons of ins-and-outs that I'm not yet hip to like hboot versions and clockwork vs fastboot and etc.
I am running Fresh 2.4 and I'm getting the "Low on space" trouble that others have noted. I downloaded cyanogen 7.0.3 to my SD and installed ROM Manager. I am able to boot to ClockworkMod and can select the zip to install from. After CM installs I reboot and can't get past the boot screen. (As a side note, I notice the videos all have a white background with black HTC while my boot is gray HTC on black background.)
Is there something I'm missing? The only thought I had was to revert back to completely stock ROM and try to start all over again. Thanks!

1. Are you using any other mods/tweaks - Firerat's, Data2ext or such?
2. Did you wipe everything before flashing CM? Or what steps did you take before flashing CM?

andythegreenguy said:
1. Are you using any other mods/tweaks - Firerat's, Data2ext or such?
2. Did you wipe everything before flashing CM? Or what steps did you take before flashing CM?
Click to expand...
Click to collapse
1) no other tweaks. Just put Fresh 2.4 on and started using it.
2) In the ROM Manager I backed up after flashing to ClockworkMod. I've used that backup to get my phone working again. I also checked the boxes to wipe everything as I told it to install cyanogen from the SD card. I've also tried booting to recovery manually and scrolling to wipe/restore to factory before trying to install cyanogen from zip.

Make sure you wipe EVERYTHING

YoungSinema said:
Make sure you wipe EVERYTHING
Click to expand...
Click to collapse
From manual recovery (power + volume down -> home button) I "wipe data/factory reset" and I "wipe cache partition". I also "wipe dalvik cache" and "wipe battery stats" in the advanced menu.
I still get a persistent gray HTC text on black background boot screen.

tunafishman said:
From manual recovery (power + volume down -> home button) I "wipe data/factory reset" and I "wipe cache partition". I also "wipe dalvik cache" and "wipe battery stats" in the advanced menu.
I still get a persistent gray HTC text on black background boot screen.
Click to expand...
Click to collapse
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©

MattCrystal said:
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©
Click to expand...
Click to collapse
Yup. Id agree.
#Root/Hack-Mod_Always*

MattCrystal said:
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©
Click to expand...
Click to collapse
I've downloaded 7.0.3 twice and also 7.0.0 just for fun. All through my home internet onto a macbook pro and transferred via USB to the SD card.
I'll try again and make sure to only use the manual recovery. Also, thanks for the aosp suggestion!

It's a no-go on everything.
Formatted boot, system, data, and cache. Wiped dalvik cache and battery stats. Tried to install a fresh copy of CM7 and also tried AOSP 2.3.4 with same steps.
The only thing that doesn't stall at the boot screen is my backup.
There must be something about versions that is wrong here. Something isn't playing nice.

Excuse me sir. Don't mean to but in here. But I think you missed the part were matt suggested you reflash your recovery. Its good advice. Whatever your current recovery is try reflashing it, repeat the necessary wipes and flash your rom of choice. You can reflash your recovery threw adb or if your s-off threw an hercimg.zip or if you have a nand you can boot into you can do it threw terminal or rom manger.
#Root/Hack-Mod_Always*

Personally I bootload to flash any recovery but also I'm s-off. Its extremely easy and all you have to do is rename the file and move it to the root of the SD card. Using terminal emulator is also very easy if your not s-off. If your still unsure about some of this just keep asking us. More than willing to help. Here ill make it a little easier. Go find the s-off thread and make it happen. Ill throw you my renamed version of green lantern recovery. Trust me it works perfect. Still clockwork. Just different. Then all youll have to do is bootload the recovery then reboot to recovery. And you already know how to do that.
1st go to that s-off link
Dropbox link to greenlantern
http://db.tt/ORAwPdX
The file is named
greenlanternHERCIMG.zip, just delete the greenlatern part and it's good to go.
Heres the s-off thread. All you need is the zip in the bottom of the op. Then flash it through manual recovery as always now
Get the recovery working first then we can help fix the flashing rom if it continues
http://forum.xda-developers.com/showthread.php?t=759955
*I use bootloader just to be a dork really and watch it load for that 2 seconds it takes then reboot, but who's phone doesn't like a reboot .. honestly.
®patience is a virtue©

did the same thing bro
noob here
nandroid, nandroid , nandroid,,,got it?
wipe data,
wipe cashe,
wipe dalvic,
the only thing I do different sometimes ( when having trouble flashing)
format data,
formet cashe,
format system,
flash rom and enjoy
Learned this from a Dev that used to be here but is gone now. dont know why it works but it does.hope it helps

Update? Be nice to know what's happened
®patience is a virtue©

tunafishman said:
I've tried to look everywhere for info on this issue and the closest I got was in the developers thread where someone was going to flash from Fresh 2.4 to CM 6. Apologies if I'm completely dense here.
There seem to be tons of ins-and-outs that I'm not yet hip to like hboot versions and clockwork vs fastboot and etc.
I am running Fresh 2.4 and I'm getting the "Low on space" trouble that others have noted. I downloaded cyanogen 7.0.3 to my SD and installed ROM Manager. I am able to boot to ClockworkMod and can select the zip to install from. After CM installs I reboot and can't get past the boot screen. (As a side note, I notice the videos all have a white background with black HTC while my boot is gray HTC on black background.)
Is there something I'm missing? The only thought I had was to revert back to completely stock ROM and try to start all over again. Thanks!
Click to expand...
Click to collapse
Try Using the Firerats Tweek for the Low Space Issue!
As for the other Issue Firerats may Also Fix that Problem!
*Sent on My*
Fast as its Ever Been....
"Sprint" Hero.... Running My, *ExEnHeroC* Rom, w/Kifno's Twist, Also The XDA-BLUE.apk!! "Page 10" of My Thread!!
http://forum.xda-developers.com/showthread.php?t=957867
http://www.megaupload.com/?d=WTMLMK6M
http://www.mediafire.com/?bb1axugm0bw7oro
http://m.youtube.com/index?desktop_uri=/&gl=US#/profile?user=PMGRANDS

[Q] Constant Boot Loops when trying to install new ROMs

I have CWM 4.00.15 installed and I tried to install Ryyu's Rom (Wipe) by putting it on the SD card and rebooting into recovery, then selecting the zip file and hitting apply. When the installation tried to update my kernel, it just froze and rebooted. I was then stuck on a boot loop between the Galaxy S screen and the CyanogenMod boot screen. I know that Ryyu's did not install correctly because the CyanogenMod boot screen was still there. I had to use 3 button recovery and erase cache, davlik cache and user data before trying to install AOSP Essence, but same problem happened. Installation dies and phone keeps rebooting in loops. Finally, gave up and went back to CyanogenMod Nightly and it worked.
Why can't I seem to install any other ROMs besides Cyanogen? I know I am doing something wrong, but not sure what. Any advice/help appreciated. Thanks.

Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.

Br1g0 said:
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Click to expand...
Click to collapse
Hi,
this is what I initially did to get Cyanogen on:
1. Used Superoneclick root to root phone
2. Check that 3 button recovery and download mode works. Recovery version was 3e, so installed superlagfix from android market. This automatically installed ClockworkMod Recovery as well.
3. Use CWM and flashed recovery for Samsung Galaxy S i9000
4. Reboot into recovery and select the CyanogenMod zip file and click apply to install.
To install subsequent ROMs, I just put the zip file on my SD card, reboot into recovery and repeat step 4 above, after clearing cache and user data. It is after that I get stuck on boot loops.
I did do a Nandroid backup before my initial Cyanogen install so I can go back and restore it, but it would be Froyo.

when coming from CM / MIUI - Samsung based ROM
you MUST flash a 3 file firmware with pit and re-partition.
Cyanogen and MIUI use different partitions than samsung ROMs so this is why you are having issues.

Ok, just managed to flash Darky's EE 10.2 using Odin. Not sure if Odin is the ideal way, but it worked. Really enjoying Darky's. Thanks folks!

[Q][Still not Solved] Nexus one getting buggy with 7.1 mod

Greetings fellowmen!!
Recently i thought of rooting my nexus 1. So i did some research and found out that the easiest way to do it was by unlocking the bootloader installing a custom recovery (I did Amon Ra) and then wiping the data\factory settings and flashing the cm 7.1 zip. So i did all the above and there you go....I had an n1 running cm 7.1 smoothly but then after a few hours it starts to piss me of. The problem is that whenever i lock the homescreen with the power button and wake it up again it just displays the main homescreen and does nothing i cannot navigate to the left or right homescreen cannot open app drawer in short it just hung up there doing nothing. I had to take out the battery atleast 15 times. I rebooted my device and it kept on giving me the same problem.
So then i reflashed cm 7.1 by wiping the data and factory settings and installing it again. But still it gave me the same problem. So then i thought of flashing 7.0.3 version instead and surprisingly that works like a charm. So is it the mod thats buggy or is it my phone.
One more question. I have the stock 2.3.4 gingerbread rom which i got from here!!
Code:
http://forum.xda-developers.com/showthread.php?t=1061648
This one in particular-
GRK39F OTA (stock vanilla - odexed, unrooted):
MD5: 35C8B4B9FD22DD4CA19C5D026E74411D
So to install this rom do i have to install it the same way i did cm by wiping data/factory settings and then installing flash from zip or is there any other way to do it ?
Thanks in advance for taking out valuable time and reading my long problem!!

I am running the latest version of CM 7.1 that was released within the last week or so without any issues. Got it from here. http://download.cyanogenmod.com/?type=stable&device=passion
Before that I was running the RC for 7.1. One thing to try it wiping multiple times before flashing. I assume you are running Amon RA 2.2.1, which is the latest. I have never had a problem with that recovery, however I flashed my ROM with this recovery. So far I think I like it better than Clockwork and Amon.
http://forum.xda-developers.com/showthread.php?t=1291970
As for installing other ROMs yes you do flash them the same way you flashed CM.

So are you saying that it was the recovery that was causing the problem?
Yes I am using the latest Amon Ra 2.2.1 version.
I also got the rom from that link.
And can you explain whats the difference between all these recoveries?
Thanks for replying!

I am not saying it is the recovery, I highly doubt that is the problem. I was just comparing differences. There does not seem to be much difference in the recoveries for what you are trying to do. The recovery I am running is a fairly new one that I just wanted to test out. I do think I like it better than the others.
First thing I would do is wipe 3, 4 or 5 times before flashing. I have had rare occasions where a single wipe would not do it for me. Also have you verified the Checksum of the CM download? Does recovery say it installed successfully? I have also had error installing a ROM in recovery but then had the phone still load the ROM.

Yes i did check the md5 checksums and they match perfectly. Though i did wipe it out only one time so maybe that could be the problem. I think i should get clockworkmod and wipe it through that and then flash cm 7.1. Amon RA doesnt really give us the option of wiping the system partition. right?

Correct Amon Ra does not have an option to format system partition. It's recommend you also wipe system when coming from a different ROM.
Try this file by temasek's, format-signed.zip
http://www.mediafire.com/?8vbd13b440coxx6
just flash it in recovery and it will clean everything, now you can flash CM7.1 again

Are you sure you can't wipe the system with Amon? I remember having that option, but it's been several months since I have used that recovery. Kind of makes me want to flash it to find out.
Before flashing a different ROM I always wipe system, cache and dalvik cache. It is definitely important to wipe the system before flashing a new ROM. I'm sure that is where your problem lies.

No, ClockworkMod has it, but Amon_RA doesn't. Supposedly it is in the works for the next version, but that was a long time ago when I heard that (probably back when v3 for clockworkmod came out).

I did a nandroid backup and flashed the format zip file and then flashed cm 7.1 and its giving me the same problem!!
I had to restore and go back to 7.0.3
Why is this happening
Edit: I also wiped the dalvik cache and factory reset it also but still it just freezes!!

Any advise?

Have you tried downloading the file again maybe form another location I doubt this is the problem but sometimes it's something you don't expect.
You could try from here http://wiki.cyanogenmod.com/index.php?title=Latest_Version

But how does it matter I checked the md5 checksum and it matches!!

Why not stay on CM7.0.3 theres not much difference between the 2
if you dont want to i suggest to try to flash Clockwork recovery and do a full wipe then reflash CM7.1

But still I want to see how 7.1 is!
The main point here is to upgrade and not taking the alternative of staying at the older version!

Please guys any help would be appreciated!!

Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.

thealphamale05 said:
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
Click to expand...
Click to collapse
Make no different if you use amon Ra or CWM. I would definitely stay away from cwm 3.x or higher if you're using sd-ext

Looks like Ill have to stay with 7.0.3 there doesnt seem to be a solution!!

ROM Manager problem...

I installed the 5.0.2 CWM recovery to manually install the 4.0.4 update on my NexusS via Rom Manager application to avoid extra fuss since I will not be dealing anyway with custom roms, etc. Everything went fine with the update and indeed at every consequent reboot into recovery, the stock ICS appears meaning that it has overwritten CWM, as I wanted and as should happen ​​when installed over stock rom.
However, in Rom Manager still shows "current cwm version 5.0.2" even after clear cache & data application and uninstall / reinstall. Should I try manual stock recovery reflash or hard work for free and the program is simply... stuck??

maybe you have a nexus s 4g and put just nexus s? (or vice-versa).
your phone is unlocked and rooted, correct?
•neXus•S4G•ĄØKP•Mïlestøne 4•Aïr Kerneł 3.7•

It's locked and has always been cuz I rooted the simple way - without unlocking...
I flashed the correct version since everything worked fine at all stages. It's just that indication in the app that put me in thoughts...
SOLVED: Problem was a leftover folder post app uninstall in sdcard named clockworkmod. Deleted and when reinstalled the app to check, it correctly reported that I must install CWM in order to flash and restore ROMs. Rest assured now that I am 4.0.4 stock