I have been running the base nightly #197 and it is cool. But now I put the CM6.2.0 vanilla on my hero and i can't go back to the nightly #197. I get an error assert failed Status 7. Did a data wipe. And wiped everything. I have clockwork recovery installed. Also tried AR recovery any ideas
wallen31 said:
I have been running the base nightly #197 and it is cool. But now I put the CM6.2.0 vanilla on my hero and i can't go back to the nightly #197. I get an error assert failed Status 7. Did a data wipe. And wiped everything. I have clockwork recovery installed. Also tried AR recovery any ideas
Click to expand...
Click to collapse
I knew this looked like a funny post. Do you have a hero cdma or gsm? the 197 nightly is for gsm, the 6.2 vanilla (from jaybob413 right?) is for cdma.
Can't install
The 197 is a type-o it's 167 I cant go back to 167 or 166, 165. And the problem started when I tried to install the Dec. 25th vanilla update over the Dec 17th. But thanks anyway.
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!
My boot went corrupt with CM 7.0.2. I was able to restore to stock with no problem, but everytime I attempt to install CM 7 (stable or nightly), I get a black screen except for a little white/light blue line in the upper right corner.
I use the 3.0.0.5 Recovery with the directions in the following link.
http://forum.xda-developers.com/showthread.php?t=949699
Does anyone have an idea why this happens? I do remove the SD recovery card, and insert a blank SD card before rebooting.
Any help would be much appreciated!
Use 3.0.2.8 recovery
Thanks, I'll give that a shot right quick.
NewZJ said:
Use 3.0.2.8 recovery
Click to expand...
Click to collapse
Tried it and it boots back to the black screen with the line in the upper right corner.
Here's what I did.
Made the bootable sd card, copied over lastest build of cm7 and gapps.
Installed zips.
wiped data.
switch sd cards, rebooted
also tried it w/o wiping data.
Is there anything I'm doing wrong?
Wiping cache?
NewZJ said:
Wiping cache?
Click to expand...
Click to collapse
Should I do that before or after installing the zips?
wipe system, data, cache, then flash zips
NewZJ said:
wipe system, data, cache, then flash zips
Click to expand...
Click to collapse
Just tried that, no dice. It's still going back to the same screen.
Download the cm7 again, might be corrupt
NewZJ said:
Download the cm7 again, might be corrupt
Click to expand...
Click to collapse
Just downloaded a stable release, and it works. Is there any reason why the Nightly 80 wouldn't work, even after re-downloading it?
I'm also dealing with the same issue as well. The problem started when I tried to update from nightly 76 to 77. I also tried to flash to nightly 80, but no luck. I'm flashing a stable release now.
Edit: Flashing the stable release also worked for me. However, I wasn't able to flash the latest nightly over the stable build.
Yep.
Same problem here.
The stable works, boots fine, but the nightlies won't boot.
They go into the same flashing blue line.
I tried all the advice I could find, wipe system, cache, data and tried restoring to stock, still no dice.
I am using CWM 3.0.2.8.
I'm just a different flash method (verygreen's SD install), but found that nightlies beyond 75 won't boot without installing the .32 OC kernel. There's a discussion in both cyanogenmod experimental nook forum and in the dev forum here about it.
I guess I'll just wait until they resolve the issue then. I was really wanting to see how well the deep sleep worked.
Finally got the latest nightly from today with OC kernel and gapps. Running great so far. Just waiting on market being able to download.
Hello, I was on the latest stable,
I tried installing the latest nightly - 19 using the cm updater. It said something about data has another partion please try to install again to confirm wiping /data
so i selected the zip again, it seem to install just fine but I cant get past the cyanogenmod logo.
I wiped both cache and installed it again but same problem. Any tips what to do next?
I think you mean Nightly of CM 10.2 ...
Use the newest nightly ,in one Nightly there was an error about installation.
The warning is because with the nightly beginning from 20130816 the partitioning layout have to be changed because of Out of space on /system...so the massage is only that you know it and you have to confirm it a second time ...
So test a newer nightly an it should work!!!
Here is the link to the thread of CM 10.2 ....http://forum.xda-developers.com/showthread.php?t=2385178 there are some additional infos ...
Let me no if it works ...
unrealbe said:
Hello, I was on the latest stable,
I tried installing the latest nightly - 19 using the cm updater. It said something about data has another partion please try to install again to confirm wiping /data
so i selected the zip again, it seem to install just fine but I cant get past the cyanogenmod logo.
I wiped both cache and installed it again but same problem. Any tips what to do next?
Click to expand...
Click to collapse
Today Cyanogen updater notified me that the 10.2M build was available. I usually only flash stable builds, but I decided to check it out.
I was updating from 10.1.3- did everything as I always did, flashing seemed to go fine, but then I got stuck on the Cyanogen splash screen. So I went back to safestrap recovery, flashed back to 10.1.3- wiped cache etc... same thing. Just stuck on the Cyanogen splash. Tried installing 10.1.2, which was the first version I ever flashed. Same problem.
I was able to successfully boot back into stock using Safestrap (v3.11), but now I can't seem to get any version of Cyanogen to successfully boot.
Any suggestions?
Reboot into cm 10.2 before flashing gapps?
Sent from my XT894 using Tapatalk
If I flash any update after the Nov 10th update I get a "unfortunately the process com.android.phone has stopped" error, looping
Is clearing the data, and all cache, followed by flashing the newest nightly rom the only option?
Could I backup texts and apps in TWRP and flash the backup after applying the nightly or would I need to use an app like Titanium?
I reverted back to the Nov 10th where the issue doesn't occur.
Cyanogenmod
TWRP Recovery
Appreciate any help
Thanks!
cBreezy22 said:
If I flash any update after the Nov 10th update I get a "unfortunately the process com.android.phone has stopped" error, looping
Is clearing the data, and all cache, followed by flashing the newest nightly rom the only option?
Could I backup texts and apps in TWRP and flash the backup after applying the nightly or would I need to use an app like Titanium?
I reverted back to the Nov 10th where the issue doesn't occur.
Cyanogenmod
TWRP Recovery
Appreciate any help
Thanks!
Click to expand...
Click to collapse
What recovery version are you using? CM now require specific version of TWRP or CWM to flash properly. More info about this on the cyanogemod website (look in the htc one wiki)
You can also expect nighlty builds to be unstable. Would recommend using the latest stable version or snapshot version.
http://wiki.cyanogenmod.org/w/M7_Info
http://wiki.cyanogenmod.org/w/HTC_fstab_updates