Database Develop

Preparation b4 flashing between ROMS?

is there a guide anywhere on this or could someone give me a rough guide?
Do I need to format the partitions I made on my SD to run Hero, when flashing to another ROM that uses APPS2SD like Soulife's Rogers? I'm getting untold weird problems with this ROM - syncing etc.
Also, looks like APP2SD might not be working - 45MB free space is this right?
(For the record, all I did was a 'wipe' and then flash - which didn't seem to get rid of most apps)
Thanks!

You need to wipe your ext partition before switching roms.
That will get rid of the apps that stayed.

Hmm.. I digg my double post even though I only clicked once. Thx xda

can you wipe with the 'repair ext filesystems' option in cyanogens bootloader?
didn't seem to work for me. :?

with adb:
adb remount
adb shell
rm -r /system/sd/*
reboot recovery
then flash the update

thanks!
when I do
rm -r /system/sd/*
I get:
cannot remove '/system/sd/*': No such file or directory
So I guess there's nothing there anyway? ... looks like it when I 'ls' the directory anyway... confused as to why my apps keep on showing up after flashing ???

what a minute I adb'd in when it was in bootloader mode would that effect what I see?

Trouble installing JacxHEROSki 2.1

I get a bootloop on the seconds splash screen with the little green android popping out.
I've tried wiping and reflashing multiple times, as well as repairing the file system extensions. Sometimes, however, it gets to the third "HTC" screen, but then goes back to the green android popping out.
No luck. I'm coming from Cyanogen Mod 4.0.1
If anyone has any ideas, I'd appreciate it.
Thanks.

nasman1993 said:
I get a bootloop on the seconds splash screen with the little green android popping out.
I've tried wiping and reflashing multiple times, as well as repairing the file system extensions. Sometimes, however, it gets to the third "HTC" screen, but then goes back to the green android popping out.
No luck. I'm coming from Cyanogen Mod 4.0.1
If anyone has any ideas, I'd appreciate it.
Thanks.
Click to expand...
Click to collapse
did you wipe the ext partition?
you need too

Sorry for the noob question, but how do I do that?

Here be sure to follow this or this guide.
i wuld recommend u do the manual partition and only delete the ext2 partition and remake it for a lot more simpler process i.e only rm 2 n rm 3 after print so that your sd card files are not deleted

Dare{D}evil said:
Here be sure to follow this or this guide.
i wuld recommend u do the manual partition and only delete the ext2 partition and remake it for a lot more simpler process i.e only rm 2 n rm 3 after print so that your sd card files are not deleted
Click to expand...
Click to collapse
yup thats how i did it, but if you dont want to go through all that, you can follow these steps: http://forum.xda-developers.com/showthread.php?t=535797
1.) Turn on the phone holding the home key and power to boot. Attach the phone to your computer via usb.
2.) Wipe your phone from the menu in cyanogen
3.) Open console ALT + X and enter the following commands. Press "Enter" after each line. This wipes the ext partition.
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -r /system/sd/*
or this in adb
adb remount
adb shell
rm -r /system/sd/*
Click to expand...
Click to collapse
Note: this will delete your apps on your sd as well as userinit files or w/e was there
Code:
to backup your ext partition to your current directory: adb pull /system/sd/ %CD%\sdbackup
to restore back to sdcard: adb push %CD%\sdbackup /system/sd

the easiest way to wipe ext3 partition is in the recovery console with
Code:
mke2fs -j /dev/block/mmcblk0p2
that is all. one command. and all is gone.

Cyanogen slow downs?

I'm using cyanogen-4.1.999 and for some reason, I'm seeing a massive speed decrease. I got 4.1.99 to run before it, but it also got slow-downs as well. None of cyanogen's roms did this before.
Example. It takes more than a few seconds for the screen to go from off, to maximum illumination (according to system setting that is).
What should I do?

I don't know what rom you were running before cm-4.1.99 but before you flash 4.1.99 make sure you wipe/clear your ext2/3/4 if you are using a second partition. After you have flashed 4.1.99 you should no longer need to wipe/clear your ext partitions when installing new cyanogen versions

ninjavampire said:
I don't know what rom you were running before cm-4.1.99 but before you flash 4.1.99 make sure you wipe/clear your ext2/3/4 if you are using a second partition. After you have flashed 4.1.99 you should no longer need to wipe/clear your ext partitions when installing new cyanogen versions
Click to expand...
Click to collapse
Crap... I only wiped ALT+W style. Oh well. Should I wipe ALT+W again after reformating?
edit: and when you say second partition, you mean the SDcard right?

Instructions to install cm-4.1.99 and 4.1.999 using cm-recovery1.4
Download tmo1.6, cyanogen 4.1.99 and cyanogen 4.1.999 from cyanogen fourm to root of your sd card (not in any folder)
Boot into recovery mode (home+power)
Wipe
If you are not using a second partition ignore next steps
Enter recovery console any type the following:
#mount -o /system/sd
#rm -rf /system/sd/*
#reboot recovery
Wipe again
Fix filesystems
Continue here if you are not using a second partition
Select option flash any .zip from sdcard and flash the tmo1.6 rom
When it is finished select option flash any .zip from sdcard and flash cm-4.1.99. You can do this with out rebooting your phone after the tmo1.6 flash
When 4.1.99 is finished select reboot option (home+back)
After boot and phone setup turn off your phone and boot into recovery again (home+power)
Select option flash any .zip from sdcard and select cm-4.1.999
When finished reboot phone (home+back) and enjoy the awesomness of Cyanogen!

Tactical Fart said:
Crap... I only wiped ALT+W style. Oh well. Should I wipe ALT+W again after reformating?
edit: and when you say second partition, you mean the SDcard right?
Click to expand...
Click to collapse
Yes I mean the sdcard when talking about second partition

ninjavampire said:
Instructions to install cm-4.1.99 and 4.1.999 using cm-recovery1.4
Download tmo1.6, cyanogen 4.1.99 and cyanogen 4.1.999 from cyanogen fourm to root of your sd card (not in any folder)
Boot into recovery mode (home+power)
Wipe
If you are not using a second partition ignore next steps
Enter recovery console any type the following:
#mount -o /system/sd
#rm -rf /system/sd/*
#reboot recovery
Wipe again
Fix filesystems
Continue here if you are not using a second partition
Select option flash any .zip from sdcard and flash the tmo1.6 rom
When it is finished select option flash any .zip from sdcard and flash cm-4.1.99. You can do this with out rebooting your phone after the tmo1.6 flash
When 4.1.99 is finished select reboot option (home+back)
After boot and phone setup turn off your phone and boot into recovery again (home+power)
Select option flash any .zip from sdcard and select cm-4.1.999
When finished reboot phone (home+back) and enjoy the awesomness of Cyanogen!
Click to expand...
Click to collapse
Ohh i had the same problem too. So Do we need to do the 'alt w' in recovery still?

NOback said:
Ohh i had the same problem too. So Do we need to do the 'alt w' in recovery still?
Click to expand...
Click to collapse
Yes in the instructions I posted above "wipe" is the same as "alt+w"

Doing all those instructions seems to be a lil extreme. Clear your data and cache in the browser, google maps, and street view (thats where it's held the most). And then go to terminal and type:
Code:
su
cd /system/sd/dalvik-cache
rm *
exit
exit
Then reboot your phone. It will take awhile for it to boot up like the very first time flashing.

supremeteam256 said:
Doing all those instructions seems to be a lil extreme. Clear your data and cache in the browser, google maps, and street view (thats where it's held the most). And then go to terminal and type:
Code:
su
cd /system/sd/[B]dalvik[/B]-cache
rm *
exit
exit
Then reboot your phone. It will take awhile for it to boot up like the very first time flashing.
Click to expand...
Click to collapse
fixed typo (dalvik instead of dalvick)

B-man007 said:
fixed typo (dalvik instead of dalvick)
Click to expand...
Click to collapse
Thank you. Way to keep your eye on the ball son.

This only worked until today. When I checked the directory some (all?) of the files there were restored and I had to "rm *" the directory again. Earlier, it took me about 5 minutes to get the phone to cooperate long enough to order a reboot. Ideas?

Tactical Fart said:
This only worked until today. When I checked the directory some (all?) of the files there were restored and I had to "rm *" the directory again. Earlier, it took me about 5 minutes to get the phone to cooperate long enough to order a reboot. Ideas?
Click to expand...
Click to collapse
Well when you reboot the phone...android remakes those files. thats why it takes so long to boot after you do that. the phone should run smoother then.
Have you tried wiping your ext partition?

B-man007 said:
Have you tried wiping your ext partition?
Click to expand...
Click to collapse
Yes. I used sdparted to nuke the whole thing. Now I have a main, swap, and ext2 partitioned card.

Tactical Fart said:
Yes. I used sdparted to nuke the whole thing. Now I have a main, swap, and ext2 partitioned card.
Click to expand...
Click to collapse
is it in that order? because its in the wrong order then. it needs to be FAT32, EXT, Linux-Swap
you should upgrade to EXT3 as it uses journaling (its safer)
did you try booting without the sd card? (wipe and flash the update, remove the sdcard, and reboot)
is there still a problem with the speed w/o it?

No, my partitions are the order you said they should. It was just a basic reformat without any special paramaters.
Also, the slow downs don't occcur until the phone has been on for a while. A reboot fixes the problem quickly, but while the problem is in place, I can't use "su" in the terminal (the phone is so slow that the su permissions manager can't respond in time to give permission and it refuses) and I can't receive calls. Plus it takes about 5 minutes of fighting to reboot, and thats if I don't pull the battery.

Tactical Fart said:
No, my partitions are the order you said they should. It was just a basic reformat without any special paramaters.
Also, the slow downs don't occcur until the phone has been on for a while. A reboot fixes the problem quickly, but while the problem is in place, I can't use "su" in the terminal (the phone is so slow that the su permissions manager can't respond in time to give permission and it refuses) and I can't receive calls. Plus it takes about 5 minutes of fighting to reboot, and thats if I don't pull the battery.
Click to expand...
Click to collapse
im starting to get these problems too. Cyan is going to release anotherr rom (probably today) that aims to fix some of the major errors with the rom according to his twitter. I guess we should just wait and see if it makes it better

cyanogen 4.1.99 and 4.1.999 slow down cure
I upgraded two g1’s to 4.1.99 and then to 4.1.999. First they were slow. I had to upgrade my ext2 partition to ext3. I did this from cyanogen recovery console, 4.1 If you already have 4.1 console installed, Go to console, enter/return, on the keyboard and typed the command, upgrade_fs next to the # and then pressed enter.
If you do not have recovery console 4.1 installed. Use this link below, in the instructions for installing it from the terminal emulator make sure you type, su then press the return/enter then type in the flash command per the instruction.
http://www.cyanogenmod.com/downloads/recovery-image
Then you must be in the 4.1 recovery console, you access by holding down the power and home buttons while rebooting, got to alt-x, Go to console)
in console press enter/return
type the command upgrade_fs then press enter/return then type reboot and press enter/return.
I then downlaoded everything I needed and put them on my sd card and installed following these instructions.
http://www.simplehelp.net/2009/10/04/how-to-install-cyanogenmod-4-1-99-on-your-g1-android-phone/
Worked like a charm and runs fast and stable. Hope this helps.

Problems with nandroid help please

Hey guys, im asking your help this time with problem maybe you can give me an idea. I was running MLIGN Hero and didnt have any problem, due to my headphone were not working property i decided to build CYAN build in order to use my Bluetooth headphones, first thing i did was to erase my ext3 partition using this commands:
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# rm -rf /system/sd/*
but in the last statement i made a mistake and wrote
# rm -rf /system/sd//*
with one more slash, in order to correct my mistake i retype the sentence correctly and pass to erase the dalvik cache with these commands:
mount system
mount system/sd
rm -rf system/sd/dalvik-cache
then i upload the cyan build and flashed but when it booted it got stuck in the first screen, didn't pass from this screen with was strange, i reflashed the build, downloaded again, just to be sure, and nothing the same result.
I got a nandroid backup and tried to flash it but got this message:
error performing restore! try running 'nandroid-mobile.sh restore' from console
so dont know what to do know, i typed those commands in console but dont know how they are working.
please anyone know something about it, i would appreciate your help.
Thank you.
PS: Im sorry for posting this kind of problem.

I had that problem before. It's because you typed 'recovery' in console to get back into the recovery menu perhaps? I know amon_ra suggests not to do that becuase it screws up nandroid. And that's what happened to me. Why don't you just get amon_ra 1.4.0 recovery that way you won't have to go into console and manually type those in?

Hah, was just googling because i get the exact same error on my HTC Magic. I have Amon Ra's latest Recovery (1.3.2H) and i get the same error when i try to restore a nandroid backup.
EDIT: Hmm...did a new nandroid backup just to test to restore it, and it worked...so it's the old nandroid (like 2 weeks old) that i cannot restore without getting the error. What could be wrong? could it be corrupt?

Need advice - Fastest Eclair Rom on top of Cyanogen

Hello,
I am currently running Cyanogen Mod 4.2.14.1 on my G1. My additional specs are listed below. I am looking for a fast but stable ROM that I can flash on top of Cyan's Rom without the need to wipe or change my Radio/SPL, etc. I just really don't want to go through losing all my data. Any advise would be greatly appreciated. Thanks!
SD Card: 6 Class Fat32/ext3/Linux-Swap
SPL: HBOOT-0.95.0000
Radio: 2.22.19.26i
Rom: CyanogenMod 4.2.14.1
Recovery: Cyanogen's Recovery 1.4

You can't flash a completely different ROM on top of another. It might cause some un wanted issues.
Suggestion:
Make a backup of your stuff.
Full Wipe
Flash a Different ROM.
Restore your stuff.

Bummer. Welp, Cyan it is then. Don't need a bunch of issues messin' around. Thanks for the reply!

I believe that xRom by JAC is based off the same kernal which means no wipe going to it... you could use switchrom to backup and restore without wiping to go back to cyanogen if you dont like it...

Let me ask this then. I always use Nandroid for my backups. Can I just do a nandroid backup, flash xrom, and if I don't like it...do a nandroid restore to get back to Cyanogen?

your app data might not be compatible coming back.. do you know how to use switchrom? its not that hard once you learn it... and it backs up the app data before doing a nandroid...
google xda switchrom.sh
download the switchrom.txt file
rename to switchrom.sh
move to root of sdcard
go to terminal emulator type: (hit enter after each line)
su
cp sdcard/switchrom.sh /system/sd
reboot recovery
enter recovery console: (hit enter after each line)
mount /system/sd
sh /system/sd/switchrom.sh -s (todays date)<this will be the backup name
*this stores your rom* notice -s
to restore the backup--enter recovery console
mount /system/sd
sh /system/sd/switchrom.sh -r
it will give you a choice... choose the most recent (or stable) rom
I do one of these backups every weekend JIC I mess something up (which I did last night... last back was 01/28/10 so not too bad..

Well, your instructions are impecable! Never used it but I'm gonna give it a whirl. Thanks so much for the detailed assistance

junkdruggler said:
your app data might not be compatible coming back.. do you know how to use switchrom? its not that hard once you learn it... and it backs up the app data before doing a nandroid...
google xda switchrom.sh
download the switchrom.txt file
rename to switchrom.sh
move to root of sdcard
go to terminal emulator type: (hit enter after each line)
su
cp sdcard/switchrom.sh /system/sd
reboot recovery
enter recovery console: (hit enter after each line)
mount /system/sd
sh /system/sd/switchrom.sh -s (todays date)<this will be the backup name
*this stores your rom* notice -s
to restore the backup--enter recovery console
mount /system/sd
sh /system/sd/switchrom.sh -r
it will give you a choice... choose the most recent (or stable) rom
I do one of these backups every weekend JIC I mess something up (which I did last night... last back was 01/28/10 so not too bad..
Click to expand...
Click to collapse
Wow Just USe AmonRA LAst recovery It Lets you Use Switchrom Eazy You Can Save your Rom =D i Can Give you a youtube video that will Help U =D Youtube video