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?

How can I fix the Hero ROM's bootloop without wiping and fresh install?

I am frustrated that everytime an new release is out gotta reprogram my phone.

rm -rf /system/sd/*
search

sillyshyme said:
I am frustrated that everytime an new release is out gotta reprogram my phone.
Click to expand...
Click to collapse
Wiping your ext should not be an issue unless you're using Drizzy's "builds". If you're switching ROMs then you will have to wipe - get over it, but there should be "no wipe" updates when updating the a new version of the same ROM.

sillyshyme said:
I am frustrated that everytime an new release is out gotta reprogram my phone.
Click to expand...
Click to collapse
so i just noticed you had 27 posts, and im pretty sure all 27 have been about not wanting to wipe when switching roms, or complaining that you keep getting a boot loop. its just the dirty truth, if you wanna avoid a bootloop follow the info in the thread in my signature. if you dont wanna wipe, then dont switch, plain and simple.
SEARCH!!!!

palosjr said:
so i just noticed you had 27 posts, and im pretty sure all 27 have been about not wanting to wipe when switching roms, or complaining that you keep getting a boot loop. its just the dirty truth, if you wanna avoid a bootloop follow the info in the thread in my signature. if you dont wanna wipe, then dont switch, plain and simple.
SEARCH!!!!
Click to expand...
Click to collapse
Oh snap tellin it like it is..

I feel nice today, you're in luck, but this is the only post I'm writing to explain this procedure to you:
1. Reboot into recovery (Home + Power)
2. Backup NANDROID (or switchrom if you know how)
3. Enter into the console (alt+x)
4.
Code:
mount /system/sd
rm -rf /system/sd/app_s
rm -rf /system/sd/dalvik-cache
5.
Code:
ums_enable
6. Go into sdcard thru windows or whatever and then grab the data.img from the nandroid folder or switchrom folder depending on which one you used and place it in the same folder as fastboot (Go search if you don't know how)
7.
Code:
ums_disable
8.
Code:
recovery
9. Repair Filesystems (alt+f) (I think...)
10. Wipe data (alt+w)
11. Flash ROM of choice. (I've done this with practically every Hero flavor out there, should be no problem unless you cut corners in my directions some where... shame on you...)
12. Reboot phone when it finishes.
13. Wait for phone to get to setup page. Then, once there, reboot your phone again, but this time into bootloader (Camera + Power). You must wait for it to load the setup or this won't work.
14. Once fastboot is connected to the phone and can detect it (From connected PC):
Code:
fastboot flash userdata data.img
fastboot reboot
15. Wait for phone to boot up.... and bam, all wallpapers, lockscreen, program settings, mms, sms, contacts, etc. are already set up and your old settings + new ROM is ready to rock.

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.

[Help] Cyanogen 5.0.8 stuck at G1 Screen

Alright, I asked in the official thread itself and the best answer I could attain was that I should simply double down for a new phone. Nobody seems to be able to help me there. Wish so many other questions, I'm not surprised, though.
I've finally resorted to simply starting a thread in hopes of garnering assistance with my problem.
Now, on with the issue itself.
I cannot get, under any circumstances, Cyanogen 5.0.8 (the stable release) to boot. I can't get any of it's variants to boot, either. I meet every requirement, I've wiped everything with every option available to me and even manually typed in the commands for wiping Dalvik manually.
It just won't move past the T-Mobile G1 screen. At all. Under any attempts.
I'm on the DangerSPL.
I'm on the latest Radio.
I'm on Amon_Ra's latest recovery.
I simply don't get it. It doesn't make sense. I should be able to flash and boot.
I can go back to the latest Super E or Cyanogen's 5.0.7, but 5.0.8 just won't boot. I don't know what to do.
Any ideas what could be happening here? I'd really appreciate the assistance.
Thanks.

ok here goes nothin.. start to finish...
Download update cm blah blah blah
download GAPPS ere36-ds blah blah blah
download OC kernel (optional)
-Press home plus power
-go to console type this exactly pressing enter at the end of each line:
mount /system/sd
rm -rf /system/sd/*
reboot recovery
-wipe data/factory reset
-flash any zip
-flash 5.08, then flash GAPPS
-reboot system now
{if you downloaded an OC kernel}
-after setup power off
-press home plus power
-flash any zip
-flash OC Kernel

just noticed you have amon_ra recovery... I use cyanogen recovery, so you might want to flash that first... or totally ignore me all together

Haven't gone this route yet. giving it a go now. Thanks for the help. Hopefully it works.
Edit: Okay, I get the following error when I attempt the "mount /system/sd" command:
"Mount: can't find /system/sd in /etc/fstab"
Minus the quotes, of course.

so, what was the solution? anyone?
same as the topic starter... CM 5.0.8 & RA 1.7.0
????

[Q] Wiping Differences between Amon_RA and Clockwork

This is a basic question that is annoying because it highlights how much I don't really understand.
What is actually wiped using the different recoveries and should I prefer one over the other?
Details:
I have been using Amon_RA 1.5.2 for quite some time and it is fine. But recently I had to revert to a sense rom to get the newest PRL (60677) since I wasn't getting SMS. When reverting, it made me wonder where this update was kept that it wasn't removed during my wipe, and also, are there other things hanging around which should be cleaned up?
My current root file structure looks like this (ND=not a directory):
acct
cache
config
d
data
default (ND)
dev
etc
init (ND)
init.goldfish (ND)
init.heroc (ND)
init (ND)
mnt
..../asec
..../sdcard
..../secure
proc
root
sbin
sd-ext
sdcard
sys
system
*I had been messing with Apps2SD though it is not currently used on this set up. Should explain the multiple SD card mnts.
Amon_RA 1.5.2 Wipe Menu
Wipe
Wipe data/factory reset :: Wipe /data and /cache
Wipe Dalvik-cache :: Wipe Dalvik-cache both on /data and ext
Wipe SD:ext partition : Wipe the ext partition on your sdcard
Wipe battery stats : Wipe the battery stats in /data
Wipe rotate settings : Wipe the sensor settings in /data
Clockwork 2.5.0.7 Wipe Menu
wipe data/factory reset
wipe cache partition
Additional Clockwork 2.5.0.7 Mounts and Storage Menu
format boot
format system
format data
format cache
format sdcard
format sd-ext
Any clarification would be much appreciated by me, and I assume the community. Thanks.
--------------------------------------------------------------------
A different thread discussing general difference between Amon_RA and Clockwork

I can't provide much help technically, but I wanted to point out clockwork 2.5 also has a Wipe Dalvik Cache option under the Advanced menu.

I'd definitely like some more technical information too, but I can provide what I've read and observed.
Factory reset wipes data AND cache.
Wiping boot and system happen already when flashing a rom and wiping either will require you to nandroid or reflash the rom. Many roms seem to suppress the messages or something.
[dpeeps74]

mtnchkn said:
Details:
I have been using Amon_RA 1.5.2 for quite some time and it is fine. But recently I had to revert to a sense rom to get the newest PRL (60677) since I wasn't getting SMS. When reverting, it made me wonder where this update was kept that it wasn't removed during my wipe, and also, are there other things hanging around which should be cleaned up?
Click to expand...
Click to collapse
The radio itself, PRL, PRI, and profile, are all stored in a deeper part of the phone than recovery or bootloader, if I remember right it's hardcoded into the dialer function of the phone (NOT in the .apk or ROM), so they stick no matter what you wipe or flash. As for what's different between the 2 recoveries, they both do basically the same thing, but CWM has more wipe options and is newer code, also when flashing zips from CWM you can actually select them inside of folders from your sd, whereas with amon ra it must be on the root of your sd. Also, in amon ra there is an option to "fix UID mismatches" which could be helpful if your device goes crazy but I've never had to use it. CWM has a fix permissions option, but you can also do that from TE, so again, not much use to me personally. I use 2.5.0.1 because it will flash both amend and edify zips, it's green, and doesn't give me the error code that 2.5.0.7 did. I have used every recovery available for the heroc. Also, the 3x versions of CWM have even more options and wipe options. The other sucky thing about CWM is the fact that wipe sd is right next to wipe cache in mounts so people sometimes wipe the wrong one. That is why tte one in the main menu is the one to use for wiping cache. Also, wipe and format are the same thing, different words. Feel free to pick them both apart, I think clockwork has much better functionality, even though the UI kinda blows compared to amon ra. YMMV.

You shluld give RA.1.7 a try
Yea it's Me Again With The
Modified Hero

Wow, this is exactly what's been on my mind lately... I've been looking at the ClockworkMod thread in dev lol.
I just switched from Amon_RA 1.7 to CWM 3.0.2.4 last night. I decided that since I'm trying CM7 for the first time, I would also try a new recovery. Il Duce summed up the differences nicely. What I found comforting was that nandroid backups made in one recovery can be recovered in other recoveries, you just have to move your backups to the appropriate location on the SD card.
I think they're about equal. Amon_RA has a nice interface, and I much prefer the press Home to confirm instead of CWM's. With CWM, you could choose a "Format /system" or something and you are only presented with a "Yes - wipe" confirmation, which doesn't actually tell you what you're wiping. And like Il Duce said, that could easily wipe the sdcard instead of cache. But with CWM you can make your SD card less cluttered and put zips in different folders.
If you're not using Firerat's mod, there's no reason not to just try them all
If you are using Firerat's mod, it's just a bit more troublesome.

laie1472 said:
You shluld give RA.1.7 a try
Yea it's Me Again With The
Modified Hero
Click to expand...
Click to collapse
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?

mtnchkn said:
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?
Click to expand...
Click to collapse
darch-ra 1.7 is capped at 691.

mtnchkn said:
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?
Click to expand...
Click to collapse
IIRC it is OC'ed to 768 MHz.

c00ller said:
IIRC it is OC'ed to 768 MHz.
Click to expand...
Click to collapse
no that's godspeed. 1.7 works fine on my phone, which dies over 729, which means 1.7 isn't 768, it's probably 691, but most def it's not higher than 729.

So what is a good download link for the image, since the only 1.7 I can find on the forums is the 'unofficial mirror of Darch 1.7' which gives me an error when I try flashing (says there is no image)?
il Duce said:
no that's godspeed. 1.7 works fine on my phone, which dies over 729, which means 1.7 isn't 768, it's probably 691, but most def it's not higher than 729.
Click to expand...
Click to collapse

mtnchkn said:
So what is a good download link for the image, since the only 1.7 I can find on the forums is the 'unofficial mirror of Darch 1.7' which gives me an error when I try flashing (says there is no image)?
Click to expand...
Click to collapse
my dropbox
http://dl.dropbox.com/u/5669105/darchra.img

il Duce said:
my dropbox
http://dl.dropbox.com/u/5669105/darchra.img
Click to expand...
Click to collapse
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.

mtnchkn said:
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.
Click to expand...
Click to collapse
I wonder if that means the command is "not found" or if it's saying the .img is not found. If it's the latter, make sure you put quotes around the file path if there are spaces, e.g,
flash_image recovery "C:\Android Folder\recovery.img"
If it's the first, then you're right, it should work in adb shell.

mtnchkn said:
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.
Click to expand...
Click to collapse
Make sure the recover img. Is named.
recovery-heroc-RA-1.7.img
And make sure its not
img.img.
Sometimes the file is not named correctly. Also make sure the img. Is on the root of your sd/card and not in any folder. Good luck
Yea it's Me Again With The
Modified Hero

Turns out I was missing flash_image command. I am going to include the solution below for others, but bottom line, everything is fine now and am running 1.7. If someone has a download for CW 2.5.0.1 which someone mentioned, post it too. Also, here is 1.5 if anyone needs it
http://dl.dropbox.com/u/1759357/recovery-heroc-RA-1.5.zip
I came across this post, which pointed to a flash_image file here. So I copied that into my tools folder, then...
Code:
>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT041HF00432 device
C:\android-sdk-windows\tools>adb root
adbd is already running as root
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb push flash_image /system/bin
851 KB/s (26172 bytes in 0.030s)
C:\android-sdk-windows\tools>adb shell chmod 0755 /system/bin/flash_image
C:\android-sdk-windows\tools>adb shell flash_image recovery /sdcard/recovery-heroc-RA-1.7.img
C:\android-sdk-windows\tools>adb shell reboot recovery
So now I have a new recovery.