Database Develop

[Q] can't get Cyanogenmod working

I'm new to using non stock ROMs and have heard good things about the Cyanogenmod and wanted to give it a try. I rooted my phone using Super One Click, I installed Clockworkmod to install the ROM and backup my settings, then I got the stable version of Cyanogenmod for my phone HTC Hero CDMA (update-cm-6.0.0-Heroc-signed.zip). I then followed the steps from the WIKI I updated the Radio, wiped my phone's data, then the cache, I selected the ROM to install from the root directory of my SD card, let it run through then told it to reboot the system. thats where the problem shows up it comes to the first HTC screen and will just sit there forever I even tried leaving it on overnight. I tried to flash it with different versions of Cyanogenmod and all had the same result, however I was able to get a version of damagecontrol to flash correctly on my phone so I know its not a brick.
I have searched quite a few posts but have not found anything that helps I have tried wiping multiple times and even wiped Dalvik cache. I ran a logcat to see if it might help me debug whats going on and it appears to be looping through the same things over and over I rebooted it again and had the same results. I can supply any info needed from the logcat needed but not sure what parts might help.
the different versions of ROMs I have tried to use are:
update-cm-6.0.0-Heroc-RC1-signed
update-cm-6.0.0-Heroc-signed
update-cm-6.1.0-RC1-Heroc-signed
Also tried Cyanogenmod nightly 87, 95, & 99
fresh-cdma-hero-1.1
DamageControlv2.08.1

adrazar said:
I'm new to using non stock ROMs and have heard good things about the Cyanogenmod and wanted to give it a try. I rooted my phone using Super One Click, I installed Clockworkmod to install the ROM and backup my settings, then I got the stable version of Cyanogenmod for my phone HTC Hero CDMA (update-cm-6.0.0-Heroc-signed.zip). I then followed the steps from the WIKI I updated the Radio, wiped my phone's data, then the cache, I selected the ROM to install from the root directory of my SD card, let it run through then told it to reboot the system. thats where the problem shows up it comes to the first HTC screen and will just sit there forever I even tried leaving it on overnight. I tried to flash it with different versions of Cyanogenmod and all had the same result, however I was able to get a version of damagecontrol to flash correctly on my phone so I know its not a brick.
I have searched quite a few posts but have not found anything that helps I have tried wiping multiple times and even wiped Dalvik cache. I ran a logcat to see if it might help me debug whats going on and it appears to be looping through the same things over and over I rebooted it again and had the same results. I can supply any info needed from the logcat needed but not sure what parts might help.
the different versions of ROMs I have tried to use are:
update-cm-6.0.0-Heroc-RC1-signed
update-cm-6.0.0-Heroc-signed
update-cm-6.1.0-RC1-Heroc-signed
Also tried Cyanogenmod nightly 87, 95, & 99
fresh-cdma-hero-1.1
DamageControlv2.08.1
Click to expand...
Click to collapse
try this:
using a rom that works flash a new recovery image using ROM Manager (find it in the market)
Tell ROM Manager to flash the recovery for ClockworkMod 2.5.0.1
Then Reboot to recovery.
**********NANDROID FIRST!!*********
Starting the flash:
1. Choose the "Wipe data/factory reset" then click "wipe cache partition"
2. Choose "install zip from sdcard" and choose "choose zip from sdcard"
3. Pick the zip file with the CM6 make sure it completes and the installer confirms that it is complete.
4. Reboot phone. This might take more then 5 mins on the initial boot, when it boots up all the way and everything has loaded, do one more reboot to clear out the cache from the initial boot and you are good to go
**If this doesnt work for you, follow step one, select a DIFFERENT ROM, reboot, then reboot into recovery, then wipe again, and flash back CM6.

I tried this, I already had Rom Manager installed but checked to make sure it was all up to date, flashed it to 2.5.0.1 and rebooted to recovery. I wiped the data and cache and installed the CM6 and rebooted with teh same results of it being stuck at the HTC screen and logcat showed it cycling through the same actions over and over, I then tried to just reboot it and it did same thing. I then wiped and installed a different ROM (the Damage Control one) and it worked fine got all the way booted up. I then rebooted to the recovery manager again, wiped and reinstalled with the CM6and had the same results as the first time. out of curiosity I even tried installing the damage control and then installed CM6 without the wipe and it still did not work.

adrazar said:
I tried this, I already had Rom Manager installed but checked to make sure it was all up to date, flashed it to 2.5.0.1 and rebooted to recovery. I wiped the data and cache and installed the CM6 and rebooted with teh same results of it being stuck at the HTC screen and logcat showed it cycling through the same actions over and over, I then tried to just reboot it and it did same thing. I then wiped and installed a different ROM (the Damage Control one) and it worked fine got all the way booted up. I then rebooted to the recovery manager again, wiped and reinstalled with the CM6and had the same results as the first time. out of curiosity I even tried installing the damage control and then installed CM6 without the wipe and it still did not work.
Click to expand...
Click to collapse
Find a new download of CM6, the one you downloaded was corrupt, try finding the thread, its in Development so find the extreme blue or redglass version.

I tried both the Extremely Blue CM6 Build (EXTBLUE_09NOV.zip) and the Red Glass CM6 Build (REDGLASS_09NOV.zip) that I got from the development area, a poste named
[ROM] (UPDATED 09-NOV) FroYo 2.2 - CM6 Extremely Blue, BlackMod, Red, Purple, Vanilla
the results as far as it looks are exactly the same as when I tried the other ROMs. I know two lines that kinda stand out to me in the endlessly repeating messages I get from logcat are:
E/dalvikvm( 326): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 326): Unable to process classpath element '/system/framework/framework.jar'
I'm not fully sure if these are the issue or if it is just random information about it failing to load the ROMs.

Does anyone know what those error messages could be caused by or a way to get around this issue?

adrazar said:
I tried both the Extremely Blue CM6 Build (EXTBLUE_09NOV.zip) and the Red Glass CM6 Build (REDGLASS_09NOV.zip) that I got from the development area, a poste named
[ROM] (UPDATED 09-NOV) FroYo 2.2 - CM6 Extremely Blue, BlackMod, Red, Purple, Vanilla
the results as far as it looks are exactly the same as when I tried the other ROMs. I know two lines that kinda stand out to me in the endlessly repeating messages I get from logcat are:
E/dalvikvm( 326): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 326): Unable to process classpath element '/system/framework/framework.jar'
I'm not fully sure if these are the issue or if it is just random information about it failing to load the ROMs.
Click to expand...
Click to collapse
adrazar said:
Does anyone know what those error messages could be caused by or a way to get around this issue?
Click to expand...
Click to collapse
What recovery are you using?

I use Rom Manager (clockwork mod) for installing the ROMs and its currently flashed to version 2.5.0.1 to recover my phone to the way it was before I flashed to to the cyanogenmod I use nandroid

adrazar said:
I use Rom Manager (clockwork mod) for installing the ROMs and its currently flashed to version 2.5.0.1 to recover my phone to the way it was before I flashed to to the cyanogenmod I use nandroid
Click to expand...
Click to collapse
That's probably the problem, try the 1.7 Darch RA, much better IMHO

Also ive noticed sometimes when I download a rom onto my computer for some reason it doesnt download the whole file correctly. So just make sure that when you download your rom to your computer the the size of the file is correct.If the rom is 50 mb make sure your download is the same.

I found a post that I believe I got that one from (RA-Darchstar.img) but it is an img file and i am having trouble getting that to install. i found another post elsewhere telling me to use commands from the SDK, it said to use
cd C:\android-sdk-windows\tools
adb devices
adb shell
flash_image recovery /sdcard/RA-Darchstar.img
exit
adb shell reboot recovery
which seems like it should work however when I do the flash_image recovery /sdcard/RA-Darchstar.img it tells me that the flash_image cannot be found. is this the wrong command line? and i do have the file on my phone's SD card in the root directory. or is there another way to get the 1.7 Darch RA?

never mind on my last question I figured it out, I wasn't in the Recovery program I already had when trying to do it. I got the 1.7 Darch RA on and working then tried to flash some of the ROMs again and every one of them failed with the same logcat errors as before.

Try backing up ur SD then taking out ur SD and formatting it on ur CPU then put it back in ur phone and format it threw the recovery I have a 28 MB swap and the rest for the system them go to ext and upgrade/update ur ext from ext2 to ext3 then try and flash CM6.1 hope this helps good luck.
Root-Hack-Mod-Always™

I formatted my card via the computer, formatted everything that RA-Darchstar will let me format, I then set up the partitions and upgraded to ext3, and then copped the CM6.1 to the phone and installed it (also tried EXTBLUE_09NOV). the end result was the same as each other time I have tried to install any of them CM6 ROMs.

Ok I ended up getting it to work by following some of the things I read on
http://forum.cyanogenmod.com/topic/...-cm-build-but-cm-6-nightly-tests/page__st__20
the part where they told this other person to extract the framework.jar to the PC and point adb to it.

[Q] CWM, Dual-boot & Market issues...dazed and confused

Hi Everyone,
Sorry for this long-winded post. I've spent hours reading posts here, AndroidCentral and AndroidTablets.net forums, but have not found answers that work for me.
I hope someone can sort out the mess I've created on my rooted 1.1 Nook. Everything worked for 4-5 weeks after I rooted with Decad3nce method until...
A few days ago I decided to try 1.1G kernel. Read many threads about issues with Root Manager/ CWM; 3.0.0.5/3.0.0.6/SD CWM/EMMC CWM/Nook/Nook (old). When I booted into CWM, the version was 3.0.0.5. If I tried flashing CWM through Rom Manager, it said it 'flashed' 3.0.0.6 (tried both "Nook" and "Nook(old)"), but it never changed version of CWM I booted into. I also tried nemiths' "[RECOVERY] Official CWM 3.0.0.6 Update [BROKEN] (new fix soon!)" method to flash 3.0.0.6, but "adb shell busybox" always gave a 'can't get root' type error, so I gave up on that. I ended up using my current CWM to flash 1.1G kernel, and it worked very well. So I ignored the the CWM issues.
Then, I decided to try rookie1's dual-boot method so I could try out Honeycomb. I could never get 'prep_dualboot' zip to flash. It always gave an 'error in zip (status 0)'. His thread showed a few others getting same error, but none of the fixes given worked for me. I re-flashed that zip and ran the 'un-dualboot' zip many times with same result. I then found a "EMMC_CWM_3.0.0.6" zip and flashed that with my CWM. That actually gave me 3.0.0.6 CWM, but flashing dualboot still didn't work. I also again un-dualbooted, wipe cache partition, wipe dalvik cache, fix permissions with same result. So I gave up on that for now.
Then this morning, I found Market updates and downloads don't work anymore. It says 'about to download', then shows the arrows in status bar and nothing else happens. Saw threads regarding this issue and tried clearing Market cache and wiping whatever I could in CWM. Nothing I've found has helped so far.
As a side note in Rom Manager, "Recovery" section now shows 3.0.0.5 (before it wanted to flash 3.0.0.6). Tried flashing 3.0.0.5 there, but it doesn't seem to do anything (same as when it tried to flash 3.0.0.6). I can't understand the logic in Rom Manager. I also have Fascinate phone and RM has issues on that phone also.
I do have CWM backups and Titanium backups of all my stuff, so at worst I can do those. Looking for possibly easier way to get back to 'normal' so Market works and I can download the 'dual boot' zip and be happy again.
Some additional questions I have:
1) I saw in Decad3nce post that he left out 'root' for busybox in an early release, so that may be why mine won't work. I know I had used busybox before, but that may have been on earlier rooted 1.0.1. Is there a way to fix my current busybox without re-rooting?
2) What is the correct CWM I should use for 1.1 and will let me flash dual-boot zip? Also, where can I download it from and how can I replace the one I have?
3) I have saved my SD card to my computer many times and then re-formated it on the Nook. Is there some partition on it that format isn't cleaning that may contain some CWM image(s) causing at least some of my headaches?
Thanks in advance to anyone that can help with these issues. I may have tried a few other 'fixes' that I've since forgotten in the 5 hours last night trying to setup dual boot and quick hour this morning before work trying to sort out Market. Sorry (in advance) if you suggest something and I then say I tried it already. Possibly, just doing all the fixes I've tried previously in the correct sequence is what I need.

I seem to back to where I was before 'bad' versions of CWM skewered Market on me.
1) busybox: found that I just had to 'chmod 755' on my /system/xbin/busybox.
2) Saw that nemith posted a 3.0.0.9 version of CWM. Flashed that using his manual method. Didn't flash his kernel. Rebooted.
3) Tried clearing Market cache and didn't help. Wiped partition cache in CWM (or possibly Dalvik cache, not sure now...was going to do both but rebooted by mistake). After reboot, Market is working again.
Not sure if any of these affected Market, but I also unchecked/checked "Allow Non-Market Apps" and Unchecked/Checked "USB Debugging" and Unchecked "Auto Mount" in Settings.
Can't post in Dev area, so hope some there having same issue as me Market see this.
Now, gonna try the dual-boot again.

Alas, still getting (status 0) error flashing dual boot prep zip. Project for another night.
Sent from my LogicPD Zoom2 using XDA App

I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.

jhoward88 said:
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
Click to expand...
Click to collapse
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.

vinal said:
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
Click to expand...
Click to collapse
No luck getting this to work

vinal said:
No luck getting this to work
Click to expand...
Click to collapse
Got a suggestion from Rookie1 to reformat my media partition. Prep now succeeded!
newfs_msdos -F 32 -L media /dev/block/mmcblk0p8

[Q] Rom Manager made bad back up image...HELP PLEASE!!!!

I rooted my hero using the 1 click root from the market. I then used rom manager to make a back up image, then flashed cyanogenmod 7.0.2 on it. There was no Market, my home button didnt work, and a few other quirks so I decided to go back to my original os. I clicked on the manage and restore in rom manager. It went thru the process and said restore complete. when it boots up it has overlayed images, and says "the application Settings(process.com.android.settings)has stopped unexpectedly.FC. As i go thru the set up, many of they options are greyed out and not accessable, then when i get to "finish setup" it FC's and says" the application Setup(process.com.htc.android.htcsetupwizard)has stopped unexpectedly. Then i get a black screen. Just wondering if I can get a good Back up image from someone to put on my sd card, then do a restore? I am pretty noob at all this, so any help would be greatly appreciated!!!!!

Mmhmm...first, 1 click bad, second, rom manager...worse in the wrong hands...
Why don't you download the gapps and put it on the root of your sdcard and then flash it after the 7.0.2 and then you'll be ok I'm sure if you take a little time to figure out you may be the only person that can fix your issue. By that, what I mean is in the install steps I'd bet it mentions to install gapps and if it doesn't let me know and I'll get the op to add that step.
As for all your messed up permissions try running fix permissions in rom manager if you can get there.
~maybe I set it too high...

i tried that first but coulnt get it to work, so i downloaded the rom directly from rom manager. The only thing i can do on the phone now is thru clockworkMod recovery

You can do fix permission in cwm also, I think under advanced. Just whatever you do, do NOT format recovery or misc if those options are in your recovery.
If you're in recovery though you're in the right place to flash. It's just
Wipe data /factory reset
Advanced -> wipe dalvik cache
Back
Install zip from sdcard and choose the7.0.2 zip and then thesame thing with gapps.
Reboot system
Edit, you could also just try to restore again from cwm. I'm assuming it holds the backup.
~maybe I set it too high...

ok, im off to bed...i will try this in the morning and post my status, thanks for your help so far

Did you ever wipe between installations and flashes? I always play it safe and wipe boot, cache, data, system and dalvik cache when I am flashing different ROMs and when restoring. Try going back into recovery and wipe what I posted and then restore your backup.
Sent from my HERO200 using XDA Premium App

I couldnt wait, I had to try it....YOU ARE ABSOLUTELY AWESOME!!!!!!!!!!!! Thank you so very much. I already had Rocksteady and Gapps downloaded on my comp, so i put those on the sd, followed your steps and BAMM! Works great! I can not thank you enough!

[Q] i897 dont boot

I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.

kalabazoo said:
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
Click to expand...
Click to collapse
The I9000 and the I897 are 2 different phones. I9000 is the international version of the Captivate, therefor, if you flashed the I9000 bootloaders on a I897 Captivate, you'll have distorted colors/screen.
What exactly was done to the phone before this happened?

Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.

kalabazoo said:
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
Click to expand...
Click to collapse
Have you tried re-flashing the ROM (Without factory reset)? Wipe cache and dalvik.

BWolf56 said:
Have you tried re-flashing the ROM (Without factory reset)?
Click to expand...
Click to collapse
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
BWolf56 said:
Wipe cache and dalvik.
Click to expand...
Click to collapse
Yes, did it, but no changes at boot at all (wait there >10 minutes).

kalabazoo said:
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
Yes, did it, but no changes at boot at all (wait there >10 minutes).
Click to expand...
Click to collapse
Reflashing your ROM won't touch your data as long as you don't wipe/factory reset. It's what we call a dirty flash, you just wipe cache/dalvik and flash your ROM again with the Gapps.

Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?

kalabazoo said:
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
Click to expand...
Click to collapse
I guess i wasn't so clear. What I mean by reflashing is to simply get in recovery mode and reflashing RemICS and their Gapps. Not to start fresh with stock.
Sent from my SGH-I747 using xda app-developers app

You explained well, errors on my side Resolved this issue with copying all data from filesystem, then reflashing with fresh slimrom . For those who fall into same situation: you could get access to filesystem of your phone trough ADB tool, and just copy sensible data to another partition/SD/device. See QtADB program also, very friendly for that.

Issue with installation of rom with temporary cwm recovery by shaaan

I am having issues with the installation of a Custom ROM on my Galaxy S Advance.
I have done it before, and it went smoothly. But later I reverted back to official one.
Now I am doing it again. But having a few problems with the CWM recovery (v6.0.2.8). I am having an old file which was probably uploaded by Shaaan.
The file name is "update.zip".
I tried downloading the new file from one of his new threads, but that download infected my laptop with a large number of viruses, malwares and adwares that were on the host site. So I am using the old file itself.
So the issue is, I used the "root.zip" file to root my phone and it was done successfully as the Root Checker app also verified the root.
Later, I booted using the CWM Recovery.
Did the Wipe Data/ Fatory Reset.
Did Wipe Cache Data.
Did Wipe Dalvic Cache.
Then I moved to Installation of ROM.
When I select the option, "CHOOSE ZIP FROM SDCARD", there comes an error saying...
"E: Can't Mount /sdcard/"
I browsed the internet and found a solution that said CHANGING THE FILE SYSTEM OF THE SDCARD. So I did that too. Tried with NTFS as well as FAT32, but nothing happened.
I even tried to install by placing the ROM files in Internal Memory since they are not even getting cleaned after Wipe Data operation. But that too resulted in negative.
This is happening every time. By now, I have installed the official firmware 4 times, so as to start the process afresh, but no luck.
The ROM files are also not corrupted, as I have used them earlier.
Here are the images of the issue I am encountering. (Please tell how to upload images, as all that I can see is an option to add URL and not an image, also an error like posting 10 posts)
EXPECTING A SOLUTION TO IT ASAP, as the Official Jellybean version has again started to lag too much.