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!!
Related
I rooted my Sprint Hero and have been able to successfully flash and operate Fresh 2.3.3 but CANNOT figure out how to get CM6 to boot. I wiped prior to attempting the flash but all that happens is a lockup on the HTC boot screen. I have attempted to flash it twice, and waited about 20 minutes the first time and 45 the second time with no progress, eventually having to pull the battery and reboot in recovery mode. I was only able to wipe the data but when I tried to wipe the delvik cache, it told me I needed to do it via ADB. I tried to partition my SD card but it ended up cutting the available memory in half, and erasing my backup, and I had to use an external card reader to reload Fresh so that I could actually use my phone (which IS fully functional now). Should I be wiping EVERYTHING on the phone (including the battery and rotate info)? What am I missing?
I have heard nothing but great things about CM6 and am very disappointed that I cannot get it to work. Can anyone help?
Sprint HTC Hero
Firmware version: 2.1-update 1
Software version: 2.27.651.6
try wiping your ext partition
I wiped everything that the recovery menu would allow me to prior to the first attempt at flashing and it wouldn't load. I pulled the battery and rebooted to the recovery menu then partitioned the SD card, wiped just prior to the second attempt at re-flashing, re-flashed and it still locked up at the HTC screen.
I like to think I'm pretty computer savvy but I just can't figure this out. Why would Fresh 2.3.3 load without a hitch, but CM6 not?
make sure you recovery is 1.6 or 1.7 to be able to wipe dalvik i had same prob
My recommendation would be flashing the recovery in this thread here.
This the recovery I used while I was using Fresh 2.3.3, and when I upgraded to the CM6 Nigtlies.
I say Flash The Custon Amon_RA 1.7 in Darchdroid thread->NANDROID!!!!->Wipe Data->Dalvik->sd-ext(if using apps2sd)->Flash RC1 or Latest Nightly (your choice)->Flash Optionally Google Apps->Optionally Flash Uncapped Kernel and/or Battery Tweak(I use the uncapped Kernel, and not the battery tweak, and I get 24 hours+ with average use)
Try that out.
Funny, im running into the same problem after flashing the wrong blackmod... wiped, reflashed cm and now it wont go past the htc white boot screen
It did boot before though which is odd
Edit: Wiped, wiped dalvik and ext part, flashed rom and gapps, working just fine now... will flash batt tweak, bm and round clock in a min, hopefully it doesn't break it
jUgGsY,
Thank you for being so thorough in your response, it all makes sense! My only issue now is trying to re-flash the recovery image. I downloaded the RA-Darchstar image but I'm not sure if it's correctly being pushed to the SD card (all I get is a long list of ADB commands, no particular confirmation) and when I try to flash the image, I get a message telling me that it can't find the partition. What does this mean? Is the recovery image really that important to the updated ROM? How come there is no specific recovery image recommended on the CM forum?
EDIT: I found directions from the Unlockr on the youtubes. Gonna give it a try and see how it goes after that...
So it was decadence#7 kernel that was screwing up my boot... removed it and using stock darchstar
Ok... this is getting ridiculous.
*I flashed the RA-Darchstar (1.7) recovery image
*NANDROIDed
*Wiped data, cache, Dalvik and sd-ext
*Flashed RC1
*Flashed the google addon
*Rebooted
Been waiting for the damn thing to boot for almost 30 minutes now, still stuck on the HTC screen. Can anyone tell me what is going on?
jordanjackthomas said:
Ok... this is getting ridiculous.
*I flashed the RA-Darchstar (1.7) recovery image
*NANDROIDed
*Wiped data, cache, Dalvik and sd-ext
*Flashed RC1
*Flashed the google addon
*Rebooted
Been waiting for the damn thing to boot for almost 30 minutes now, still stuck on the HTC screen. Can anyone tell me what is going on?
Click to expand...
Click to collapse
Are you flashing RC1 or one of the nightly ones? I had the same issue with RC1. I could not get it to boot past the HTC screen. However, the nightly ones flash just fine. I would suggest flashing a nightly. I now see you said RC1, lol. Try the latest nightly.
It looks like I will have to go with a nightly. Are there any that you recommend? The most recent or one from a few nights back?
jordanjackthomas said:
It looks like I will have to go with a nightly. Are there any that you recommend? The most recent or one from a few nights back?
Click to expand...
Click to collapse
The latest one seem to be very good. 8/22 but make sure you download the latest google apps for it also.
For some reason, I couldn't get any variation of CM to load on my phone (CM6 or the Vanilla variant). I went with Darch's LegendROM and it is excellent - much better than stock 2.1 for the Hero! Really fast and has some neat extra features. I noticed, though, that my reception is kind of bad now and I usually have excellent coverage at my house. I already downloaded the most up-to-date Sprint radio (2.42.01.04.27) but was just curious: do I need to wipe and re-flash the image FIRST or can I just flash the radio image over the already installed ROM?
AND: Please excuse my inexperience with all of this, but I'm about to ask two already answered questions: I'm not looking for long-winded answers but if someone could point me to a relevant thread, it would be GREATLY appreciated.
1) I keep getting a "process com.google.android.googleapps has stopped working" error when I try to sync with my gmail account. How do get this to work?
2) I remember reading that there was a known MMS issue with Darch's DroidROM, not any issue with the LegendRom, but I just received a "generic network failure" message when my wife tried to send me picturemail. Is there a workaround for this?
Thank you all for your patience!
hopefully this is where this goes. >_> if not, please guide me to where i need to be.
OK. so what is going on:
-right now i am using a STOCK version of 2.2.1 FRG83D, that i rooted with superoneclick.
-i used rom manager to flash RA recovery, because somehow i can't flash roms with clockwork anymore. errors out every time, regardless of version
-i can flash new custom roms using RA, etc etc, but cannot flash roms and restore to old backups
-if i try to USE a custom installed rom, no matter which it is (i have tried a few gingerbread, nxsense, and some 2.2.1 roms), they will ALWAYS reboot after using them for a few seconds, regardless of what i am doing (setting up, using market, or just letting it sit and do nothing)
what i have done before this happened:
-i was using nxsense perfectly fine. great rom, ran great.
-updated rom manager, and clockwork recovery
-tried to flash a new boot animation, but noticed that the new clockwork won't install older .zips that use assert-scripts(?)
-tried to downgrade clockwork, and it randomly restarted the phone during the downgrade
-wanted to try gingerbread, so i flashed the new(er) hboot 0.35.0017 even though i think i had it already, and installed the rom succesfully.
-the rom wouldn't let me download from the market, as it restarted when i tried to download anything.
-i thought the problem was with the new hboot, so i went through a tutorial to revert it back to 0.33.0012 and went back to eclair, so i updated up to frg83d (and obviously got the 0.35.0017 hboot back through updating) and rooted.
the rom i am using now (stock with root) runs fine. haven't really found any real problems.
i just have NO clue why i can't use custom roms. i would absolutely LOVE if someone could help me on this.
I also had similar problem two days ago. I upgraded my clockworkmod recovery to 3.0.0.5 and tried to flash MM CM7 v14. All the problem began. I cannot restore any custom roms except the stock froyo and MM CM7 restarts like crazy whenever I try to install any apps from the market. After that, I also tried RA recovery. No luck. Luckily, I finally find out that the latest recovery messes up my ext3 partition. So, I backup and format my SD card, recreate ext3 partition, restore the SD card, downgrade clockworkmod to 2.5.1.4, wipe everything, fix permission and install MM CM7. It finally works. Hope this help.
PS: as long as I downgrade the clockworkmod, I can restore any custom roms.
Never flash now you will brick it soon
Sent from my Nexus One using XDA App
Latest ClockworkMod was known to have some problem, perhaps.
Use Amon_Ra's, if you want to be sure, and wipe everything (data & dalvik-cache) when going from ROM to ROM. Use Titanium Backup for restoring the apps.
ricky9237 said:
I also had similar problem two days ago. I upgraded my clockworkmod recovery to 3.0.0.5 and tried to flash MM CM7 v14. All the problem began. I cannot restore any custom roms except the stock froyo and MM CM7 restarts like crazy whenever I try to install any apps from the market. After that, I also tried RA recovery. No luck. Luckily, I finally find out that the latest recovery messes up my ext3 partition. So, I backup and format my SD card, recreate ext3 partition, restore the SD card, downgrade clockworkmod to 2.5.1.4, wipe everything, fix permission and install MM CM7. It finally works. Hope this help.
PS: as long as I downgrade the clockworkmod, I can restore any custom roms.
Click to expand...
Click to collapse
omfg thank you so much!!! <3 worked like a charm
kevvibot said:
omfg thank you so much!!! <3 worked like a charm
Click to expand...
Click to collapse
You're welcome. Glad to know my experience can help solving yours too.
Definitely a problem with Clockwork 3.0.0.5! I just went through madness trying to figure out WTF was up as well. The only fix was to completely format and re-partition my card then use RA instead of CW, works great now and I don't know if I will use CW again! What a pain...kinda regret having paid for ROM Manager now after this latest fiasco.
First off: one dumb question: does different rom need an updated Google Apps package?
Here's what happened: I was running CM6.1 with iNexus theme, everything was fine. Then Cm7 RC2 came out, I thought since it's a RC it should be stable enough for everyday use. So I installed CM7 RC2 using clock work recovery. Installation went fine. booted up and running. Then i installed iNexus theme for it. iNexus theme developer clearly stated that I should use RA recovey instead of clockworkmod. so i flashed RA recovery. once again it was just fine: booted up and running. Then i noticed I had no Google Apps working, i figured I forgot to flash Gapps package. I went back to recovery and flashed the zip. I thought since both RA and clockwork are custom recoveries, they should do just about the same as each other => RA 2.2.1 was used to flash Gapps package. Here's what I think that keeps my phone from rebooting all by itself over and over: The Gapps package i used was the old one that i downloaded the same time I downloaded CM6.1. I thought that since they're all Google Apps, they're just getting installed but nothing else. Now my phone just boots up to the Welcome page where it asks if you want to learn how to use your nexus one, the phone will then reboots back into the bootanimation after like 3 seconds showing the welcome page.
I did do a backup using clockworkmod, not RA recovery so I can not restore.
Anybody ever ran into this situation before??? HELP!!!! T_T
CM7 have a different gapps package, the one for CM6 will not work.
Theres a small gapps package that will work with both cwm and amon ra. if not you'll have to make sure the gapps your flashing is compatible with the recovery you're using.
umh...since i can't boot the phone into work. so I'm gonna download another Gapps and put it on my sd card then I'll flash it...maybe that'll work? hopefully!
Can you still boot into recovery?
I would do this
put the following files on your sd card
1-temasek extreme wipe file
2-cm7 ROM your choice of RC2 or nightlies
3-CM7 Gapps
Than flash them in that order
i'll be right back with some links
Get gapps here for CM7 http://forum.cyanogenmod.com/topic/15767-cyanogenmod-7-for-nexus-one-v700-rc2-3072011/
Actually there's a new GB Gapps package, let me find that link
Get temasek's extreme wipe here http://www.mediafire.com/?bxfijcp6f6bf1me
Flashing the Extreme wipe will lessen the headache of "little" things that could go wrong.
Also recommend you sticking with Amon Ra, too much problems with CWM lately
uh.... some of the apps don't work??? is it supposed to be like that? Neither Market or Youtube or GTalk work ^^!
No problems here, all apps working for me. You flashed the right gapps?
I've installed Amon Ra on my Nexus One as part of the process to get cyanogen running on it. I did the fastboot oem unlock + flash amon ra + manual update zip process.
Part of the reason was that for some reason I could never boot into clockwork recovery (yes I followed the wiki to the letter), and could only access the standard recovery (which doesn't allow custom roms, says the signature is invalid), the one in blue font. So I flashed amon ra instead and that worked fine.
Can I now flash back to clockwork, and even better, just do it via rom manager? Is there any risk or downside?
This is because I'm reading that amon ra doesn't have a wipe option, and that its better to wipe when you upgrade roms (or is that another fallacy or am I mis interpreting things)
cheers
1. If you didn't find and delete recovery-item-boot.p and install-recovery.sh, they will restore stock recovery when boot, regardless of what custom recovery you flashed.
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
2. You can change your recovery via ROM Manager, or manually. By the way, Amon RA Recovery has wipe option, of course. Where did you read that from?
LFact said:
1. If you didn't find and delete recovery-item-boot.p and install-recovery.sh, they will restore stock recovery when boot, regardless of what custom recovery you flashed.
2. You can change your recovery via ROM Manager, or manually. By the way, Amon RA Recovery has wipe option, of course. Where did you read that from?
Click to expand...
Click to collapse
1.) I'm pretty sure I'm booting into amon_ra, it has a nandroid backup option.
My attempt (fail) to install clockwork was exactly the same as how I successfully installed amon: via fastboot flash recovery /path/to/recovery-RA-nexus-v2.1.1-CM.img after unlocking the bootloader. I didn't manually find and delete those files you specified (wouldn't even know how TBH), just followed the Cyanogen wiki.
2.) Cool good to know. I suppose then there's no point in changing really. I was just reading posts and saw it referenced several times. Maybe they were out of date or early on in the piece.
Out of curiosity, is it worth wiping if you're just upgrading between the same version e.g. cyanogen 7.03 to future 7.04?
I much prefer Amon 2.2.1 It is 2.2.1 which is the latest version, not 2.1.1
Stay away from CW 3.+
Amon has a Data/Factory reset wipe for installing new roms, I wipe 5X with it. And, a Dalvik Cache and Cache options. Do those 5X also
If doing nightlies, just wipe the caches
Here is a link to a System Wipe zip you can flash from recovery. That is probably what they were taliking about. CW has that option and Amon will on the next version, I think.
http://forum.xda-developers.com/showthread.php?t=723844&page=1767
Ken
PS:
Otherwise, like mentioned you will default back to CW even if you flashed 2.2.1 thru Rom Manager on reboot.
Or, you can flash Amon thru fastboot and remove the two scripts mentioned above by LFact
Thanks mate I'll just keep using Amon
So you're saying to wipe I have to flash that zip, there's no way of just wiping it from the menu options before flashing the relevant ROM?
But in any event since I'm on CM7 I'll only be doing minor version bumps for the foreseeable future lol
I"m confused about the reboot issue: I can reboot into Amon at any stage. I haven't deleted those scripts. But you guys are telling me that unless I delete those scripts if I reboot I'll go back to stock recovery?
Sorry wrong thread.
Sent from my PC36100 using Tapatalk
@wintermute000
Yes, flash the system wipe zip from recovery like any zip. Only a few seconds. Hopefully , it will be in next Amon version.
Never an issue with Amon--
Get Quick System from market and use it to boot into recovery--exc app
Then you don't need Rom Mgr or CW--better that way
If you install Amon thru Fastboot or Terminal, it will not be erased on reboots--you still need to delete the two scripts mentioned before any rebooting
See post three on this link--DR has a flash able zip to do it--nandroid always first on this stuff
http://www.nexusoneforum.net/forum/...330-custom-recovery-wont-stick.html#post99962
wintermute000 said:
Thanks mate I'll just keep using Amon
I"m confused about the reboot issue: I can reboot into Amon at any stage. I haven't deleted those scripts. But you guys are telling me that unless I delete those scripts if I reboot I'll go back to stock recovery?
Click to expand...
Click to collapse
If you type
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
in terminal and it shows error message such as 'no file or directory', it means they were already removed. (I think ROM manager automatically remove them when flashing Clockwork recovery. When I changed to RA recovery, I found out those 2 files were gone)
If you're still curious about changing recovery, you can. I accomplished this yesterday by using Amon to flash a ROM with root access, then I downloaded CwM from the market. Installed the recovery using CwM. It's a simple process as long as you have root. As for going back to Amon, I haven't tried that.
Those files are gone (I didn't do rm, I just did basic ls in those directories). So I guess somehow during my Amon flashing it deleted it. Good to know.
Thanks for your patience all, I think I'll just stick to Amon then if I can just as easily wipe using a zip file if I need to. From what I've read I won't need to wipe anyway if I'm upgrading minor versions (i.e. CM7.03 to say 7.04 or nightly) and that's all I'm interested in doing. Hopefully by the time CM8 comes around I'll have taken the plunge on something dual core!!!
The whole reason I started investigating root/flash etc. was to give my N1 more legs until the price/performance point for the dual core phones gets to a better state, and its more than done that, I'm kicking myself for not doing it earlier. I guess once you're familiar with it then its a piece of cake, but I was reluctant for ages as I didn't want to screw up my PHONE (as opposed to say a tablet).
You don't need to remove those files since after you loaded Amon_RA, you installed CyanogenMod. Those files are used in Stock Android to replace whatever recovery you may have with the stock recovery on every boot.
I would still download the flashable zip that rugmankc linked to for formatting /system. Like I said in the CM forums, it normally isn't necessary when upgrading from minor versions, but sometimes it is the only thing you can do to fix a phone. I figure it is better to download it and never use it, then need it and having a hard time finding it.
+1 bass
@wintermute000,
I still wipe Dalvik Cache and Cache between nightlies. Seemed like the time or two I didn't do it, I had an issue.
The deal on using System Wipe if flashing new rom or if a lot of versions in between is:
When you flash a new rom it wipes system, but backs up some files from old rom first and reinstalls them as part of the new rom. After while things get cluttered, so a system wipe prolongs more serious issues. It has reduced the amount of times I need to do a complete wipe and/or sd card redos.
All Props to Temasek on this stuff
Ken
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