Cyanogen slow downs? - G1 Q&A, Help & Troubleshooting

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.

Related

[SOLVED]I can't root RC29

Okay I've been trying to figure this out for 4 and a half hours now, I've downgraded from cupcake to RC29 and now I'm trying to root it, I've tried using this guide - http://forum.xda-developers.com/showthread.php?t=442480
But when I get to here -
"What To Do Now That You Have Root
Now that you have root, you will want to apply "Hard SPL" to your phone. HardSPL is what will allow you to apply flash images from other regions (like UK on US phones, and vice versa), create full backups of your phone, install the latest build from the Android source, and usually resurrect your phone if it is "bricked". You have already downloaded the file to your SD card, so now you can apply it.
1. Power off your phone.
2. Start up in recovery mode by holding home and pressing power.
3. You will now enter recovery mode. You should see an exclamation.
4. If you do not see a menu on screen, press Alt-L to show the menu.
5. Press Alt-S to apply the update from the SD card.
6. After the update is complete, hold Home and press Back to restart.
"
I go into recovery mode but all I see are lines and I try alt-f and alt-s but nothing happens.
Then I tried this guide - http://android-dls.com/wiki/index.php?title=Quick_Root
I get stuck here -
"# In the terminal you opened earlier (with root access) Enter the following commands in to flash the modified recovery
* mount -o remount,rw /dev/block/mtdblock3 /system
* rm -f /system/recovery.img
* flash_image recovery /sdcard/recovery_testkeys.img
"
When I type the second line of commands it says not found or something similar so I'm pretty much stuck and can't figure out how to root RC29, I would really appreciate your help.
Sounds like you didn't flash the recovery image... Are you sure you placed it on your phone and followed the instructions to flash it? the flash_image recovery recovery.img command. Anyways, I have to run to work, I"ll help you more when I get back if you haven't figured it out by then. good luck.
http://www.youtube.com/watch?v=GgJ2VtSqtJY&feature=channel
this viedo help me with my rooting since i learn better thru visual =)
this is part 1 of 3. this dudes videos helped me from stock to root. to another cupcake rom. to jachero rom. it toook me like abt a day to do everything. but then after that it shouldnt take long to start uploading various roms =)
Knightsofwar210 said:
Okay I've been trying to figure this out for 4 and a half hours now, I've downgraded from cupcake to RC29 and now I'm trying to root it, I've tried using this guide - http://forum.xda-developers.com/showthread.php?t=442480
But when I get to here -
"What To Do Now That You Have Root
Now that you have root, you will want to apply "Hard SPL" to your phone. HardSPL is what will allow you to apply flash images from other regions (like UK on US phones, and vice versa), create full backups of your phone, install the latest build from the Android source, and usually resurrect your phone if it is "bricked". You have already downloaded the file to your SD card, so now you can apply it.
1. Power off your phone.
2. Start up in recovery mode by holding home and pressing power.
3. You will now enter recovery mode. You should see an exclamation.
4. If you do not see a menu on screen, press Alt-L to show the menu.
5. Press Alt-S to apply the update from the SD card.
6. After the update is complete, hold Home and press Back to restart.
"
I go into recovery mode but all I see are lines and I try alt-f and alt-s but nothing happens.
Then I tried this guide - http://android-dls.com/wiki/index.php?title=Quick_Root
I get stuck here -
"# In the terminal you opened earlier (with root access) Enter the following commands in to flash the modified recovery
* mount -o remount,rw /dev/block/mtdblock3 /system
* rm -f /system/recovery.img
* flash_image recovery /sdcard/recovery_testkeys.img
"
When I type the second line of commands it says not found or something similar so I'm pretty much stuck and can't figure out how to root RC29, I would really appreciate your help.
Click to expand...
Click to collapse
Well I've had my Original (incorrect radio flash method), 1st Warranty replacement (keyboard too lose for my liking), 2nd Warranty replacement (sending back due to 'ASDF' keys stick), all flashed in past 2 weeks. I've almost memorized the stupid commands. The "flash_image recovery /sdcard/recovery_testkeys.img" had me puzzled on this one. But I've figured it out as the short method vs changing directory.
I think your issue is the last part of copying the recovery image to the phone. I've always used the following:
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd sdcard
# flash_image recovery recovery.img
# cat recovery.img > /system/recovery.img
seems Like you're instructions kind of combine the 3rd and 4th and skips the cat command, so i have no ideal how yours is getting the file to the actual phone. I may be wrong, but just looks half done. It may be as simple as copying the image to the /system path with the 'cat' command. Good luck with it tho.
Link: http://forum.xda-developers.com/showthread.php?t=442480
It just won't copy that img file, because I still get the old color boot menu. Nothing I do works.
Oh and I read somewhere I have to upgrade to the latest radio too, where do I get it and install it?
I finally got it to work I was pushing power and camera instead of power and home.
Where do I download the latest rooted build?
Knightsofwar210 said:
I finally got it to work I was pushing power and camera instead of power and home.
Where do I download the latest rooted build?
Click to expand...
Click to collapse
Well, that's your choice
JF 1.51 is just a plain cupcake rom with root
Haykuro's 6.0 sapphire port is very nice, like JF 1.5 but with HTC Dialer, Camera ect
Cyanogen's build is like JF but more heavily modded, has auto Apps2SD and a few other modifications.
Then there's the Hero builds if you want to be adventurous.
Just have a look in the development section and see which best suits your needs
Be aware the Haykuro's ports, Rogers and Hero all require haykuro's SPL (which needs the new radio or you will brick).
Okay well I downloaded Cyanogen's build, so what are the features and how to use them?
Just read through the thread. Most are automatic optimization mods (CPU scaling, audio mods) which just make for a nicer experience. There are also others like the HTC Camera app which is a vast improvement over the stock camera app. APPS2SD is also atomatic so all you need is a second partition on your card formatted to ext3, so you will have much more room for market apps.
* Based on AOSP 1.5r2, various collected patches, and some help from JF-1.51-ADP
* Enhanced ramdisk which uses optimal mount options and smart startup
* Includes E2FSProgs for checking and converting Ext filesystems
* Apps2SD is automatic! All you need is a second partition (ext).
* Includes script to upgrade to ext3 (from recovery mode, see FAQ)
* Supports ext2/ext3/ext4 for Apps2SD
* Includes HTC Framework and various applications
* Includes latest HTC_IME with long-press, calibration, and compact QWERTY.
* Launcher with 5 screens and auto-orientation and compact drawer layout
* Sexy pattern-lock from Sapphire and Stericson's lock screen
* Clean filesystem shutdown at poweroff/reboot, and fsck at boot (no FS corruption!)
* Includes T-Mobile IM application, Amazon MP3 (with Stericson's hack), and updated Google Maps
* Does not require "DangerSPL"
* Highly optimized kernel with many extra modules
* Includes Haykuro's APN list
* Tweaked frequency scaling options to be more responsive
* Maximum CPU scaling frequency set to 528MHz (3.3)
* Various enhancements to the Settings app including extra partition space
* Runs /system/sd/userinit.sh after A2SD setup and before starting the runtime for user scripts
* Microsoft Exchange support (Work Email from myTouch)
* Includes Compcache modules
* Linux cgroups for better app prioritization
Click to expand...
Click to collapse
Knightsofwar210 said:
Okay well I downloaded Cyanogen's build, so what are the features and how to use them?
Click to expand...
Click to collapse
Most of Cyan's features are under the hood. It boosts your CPU speed from 384mHz to 528mHz
You can also use a swap partition to speed it up even more (like a paging file/ram)
http://forum.xda-developers.com/showthread.php?t=531988
You will have to partition your SD card with a swap extension to do this. If you create another partition as an ext2, ext3, ext4 partition, Cyan has a script that will automatically put your apps on the SDcard
If you want the above, you will have to format like this
fat32, ext, linux-swap
inthat order
there are threads that will help you with partitioning
http://forum.xda-developers.com/showthread.php?t=534714
^ very useful for me. Requires cyans recovery
note the ext partition shouldnt be larger than 1.5gb and the swap partition shouldnt be larger than 32 mb (24mb recommended, but im to lazy to repartition mine)
note swap will reduce the life of the sd card (though you will have probably moved on by that time)
Also try out the HTC apps that it comes with, such as the camera and keyboard (keyboard can be used by long pressing on an input area, selecting input method and chosing "Touch Input")
You can also install HTC's Music app from here
http://forum.xda-developers.com/showthread.php?t=530572
Thats all i can think of other than themes. Tehre are others i intentionally left out that you can find yourself after you get more experience with everything
How do I partition my 8GB Micro SDHC with one that is 500mb and is ext3? Thanks.
EDIT - Saw your post above.
B-man007 said:
Most of Cyan's features are under the hood. It boosts your CPU speed from 384mHz to 528mHz
You can also use a swap partition to speed it up even more (like a paging file/ram)
http://forum.xda-developers.com/showthread.php?t=531988
You will have to partition your SD card with a swap extension to do this. If you create another partition as an ext2, ext3, ext4 partition, Cyan has a script that will automatically put your apps on the SDcard
If you want the above, you will have to format like this
fat32, ext, linux-swap
inthat order
there are threads that will help you with partitioning
http://forum.xda-developers.com/showthread.php?t=534714
^ very useful for me. Requires cyans recovery
note the ext partition shouldnt be larger than 1.5gb and the swap partition shouldnt be larger than 32 mb (24mb recommended, but im to lazy to repartition mine)
note swap will reduce the life of the sd card (though you will have probably moved on by that time)
Also try out the HTC apps that it comes with, such as the camera and keyboard (keyboard can be used by long pressing on an input area, selecting input method and chosing "Touch Input")
You can also install HTC's Music app from here
http://forum.xda-developers.com/showthread.php?t=530572
Thats all i can think of other than themes. Tehre are others i intentionally left out that you can find yourself after you get more experience with everything
Click to expand...
Click to collapse
Experience? Ha, this is just like custom firmware for the Playstation Portable. Custom firmware is the equivalent of a rooted build so I do have experience with this type of thing.
I'm stuck at the very last step - http://forum.xda-developers.com/showthread.php?t=534714
At the bottom it says - "part iv - copy rom to sdcard and install, enable swap:
after phone reboots...drop to console
in your win cmd prompt, enter:
adb shell mount /sdcard
adb push /update-path/update.zip /sdcard
on g1 console, enter:
recovery
wipe data (alt + w) <--this one is optional, but i like fresh installs
install rom (alt + s)
to enable swap, see this page!"
http://forum.xda-developers.com/showthread.php?t=531988
but when I try to do this - "2. in terminal or adb shell type:
don't type things in ().
Code:
$su (terminal only)
#mv /sdcard/userinit.sh /system/sd/
#chmod 775 /system/sd/userinit.sh
#sh /system/sd/userinit.sh
"
When I enter the first command "mv /sdcard/userinit.sh /system/sd/" it says file or directly not found.
I want to use this theme too but I'm not sure if it's compatable with my current build model and I'm not sure how to install it.
http://forum.xda-developers.com/showthread.php?t=475917
Knightsofwar210 said:
I'm stuck at the very last step - http://forum.xda-developers.com/showthread.php?t=534714
At the bottom it says - "part iv - copy rom to sdcard and install, enable swap:
after phone reboots...drop to console
in your win cmd prompt, enter:
adb shell mount /sdcard
adb push /update-path/update.zip /sdcard
on g1 console, enter:
recovery
wipe data (alt + w) <--this one is optional, but i like fresh installs
install rom (alt + s)
to enable swap, see this page!"
http://forum.xda-developers.com/showthread.php?t=531988
but when I try to do this - "2. in terminal or adb shell type:
don't type things in ().
Code:
$su (terminal only)
#mv /sdcard/userinit.sh /system/sd/
#chmod 775 /system/sd/userinit.sh
#sh /system/sd/userinit.sh
"
When I enter the first command "mv /sdcard/userinit.sh /system/sd/" it says file or directly not found.
Click to expand...
Click to collapse
use "cp" instead of "mv"
note that /system/sd only exists when you have apps2sd (atleast i think? someone correct me if im wrong)
also make sure you unzipped the userinit.sh
What your going through is experience.....this isn't just flashing psp roms xD
Custom firmware flashing is extremely simple on the g1..... this is like going into the ROM and changing things up. The mods im talking about involve lots of terminal and adb commands and you really shouldnt be using them unless you understand what its doing. If you have plenty of experience in linux,then you should be able to find lots of interesting things to do in the development section.
Knightsofwar210 said:
I want to use this theme too but I'm not sure if it's compatable with my current build model and I'm not sure how to install it.
http://forum.xda-developers.com/showthread.php?t=475917
Click to expand...
Click to collapse
Which build did you install? Its compatible with Cyan 3.6.7-2. The latest is Cyan 3.6.8 which released 4 hours ago
B-man007 said:
Which build did you install? Its compatible with Cyan 3.6.7-2. The latest is Cyan 3.6.8 which released 4 hours ago
Click to expand...
Click to collapse
It's compatible with the one I had, I don't have the latest version of Cyan.
I still need help enabling swap because I have done everything including partition but I still need help enabling it thanks.
Knightsofwar210 said:
It's compatible with the one I had, I don't have the latest version of Cyan.
I still need help enabling swap because I have done everything including partition but I still need help enabling it thanks.
Click to expand...
Click to collapse
use "cp" instead of "mv"
note that /system/sd only exists when you have apps2sd (atleast i think? someone correct me if im wrong)
also make sure you unzipped the userinit.sh
Click to expand...
Click to collapse
Did you already set up apps2sd? (basically partition like i told you and boot up cyans rom? to check if you have it enabled, go to
settings > sd and storage and check if you have secondary system storage
where are you getting stuck? i need a little more info on whats happening if the above didnt work
B-man007 said:
Did you already set up apps2sd? (basically partition like i told you and boot up cyans rom? to check if you have it enabled, go to
settings > sd and storage and check if you have secondary system storage
where are you getting stuck? i need a little more info on whats happening if the above didnt work
Click to expand...
Click to collapse
Yes I have cyan running with a new theme I installed, and yes I do have a secondary system storage, I'm stuck here - http://forum.xda-developers.com/showthread.php?t=531988
B-man007 said:
use "cp" instead of "mv"
note that /system/sd only exists when you have apps2sd (atleast i think? someone correct me if im wrong)
also make sure you unzipped the userinit.sh
Click to expand...
Click to collapse
I'll try this.

clearing cache between roms

hello all, just trying to get a little input on the correct procedures for clearing the cache inbetween roms. i recently swithed from cyanmod 4.1.6 to Drizzy's Hero-V1.2r1 . Ive tried several commands in console so far to wind up reading something along the lines of : not found. Could someone inlighten me with the correct commands to do this or even the correct steps such as wipe, flash , yada yada and then what commands. thanks in advance , veritas
ronrey, so ronreyyyy, so ronrey im all aloonnneeeee
When you switch roms the only thing you need to do is wipe your ext partition and wipe your phone (alt + w). I use Ubuntu to clear my partition, but there are commands to do it if thats what your asking.
supremeteam256 said:
When you switch roms the only thing you need to do is wipe your ext partition and wipe your phone (alt + w). I use Ubuntu to clear my partition, but there are commands to do it if thats what your asking.
Click to expand...
Click to collapse
when u switch roms a small trace of them remains behind in the dalvik folder in the internal that doesnt just get cleared using alt+w so there are a set of commands to handle this task and i believe they go something like this rm -rf system/sd/dalvik-cache. along with some pre and post commands, that are the ones im refering to.
actually here is a direct quote of what i found, i just couldnt get these commands to work, so im thinking maybe they differ when switching to hero, maybe not..but they didnt work for me>>>>>>>>>>>>>>>>>>>>>
Monday, 31 August 2009 18:51 by Simon Walker
--------------------------------------------------------------------------------
User Rating: / 1
PoorBest
--------------------------------------------------------------------------------
So I started running into some performance problems with the Enomther ROM and was considering removing it and going back to Cyanogen. I decided to have a quick chat with Enomther and he gave me some things to do. The results are even more amazing than the first install.
I found out that the dalvik-cache gets carried over between ROM installs and that it can cause problems and that I should delete it, wipe my phone and start again. Enomther gave me this little guide to follow:
Ok ... so reboot into cyanogen's recovery
Press (Alt+x) to enter the console
Enter the following commands ...
mount system
mount system/sd
rm -rf system/sd/dalvik-cache
umount system/sd
umount system
recovery
This will bring you back to recovery, from there perform the "Data Wipe" option in the menu.
When it's done reboot and you should be all good. Of course you'll have to redo your settings, but your apps will reinstall properly.

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.

Just loaded Cyano ROM (newest), reboot is taking too long.

Hello!
I followed this guide and read the comments of everyone, and it's a reliable guide to rooting and installing a new ROM. The rooting went perfect, so I decided to go further and load cyanogen's latest ROM.
Power off your phone.
Boot into recovery mode. (Press and hold the Home key, then hit the power button).
Before you flash a rom file, perform a wipe. Press Alt+W to wipe the data and cache folders. You must wipe when going form different builds of Android.
Wait for the wipe to finish and the recovery image to display again, then select “apply any zip from sd”. Flash the zip file of your choice.
After flashing any zip you should be able to reboot your system and watch it load to the home screen.
After changing Android builds, it came take several minutes for the first boot. If you phone hangs on the animated Android logo, this is because you did not perform a wipe. If you are stuck in a boot loop, return to the recovery image and make sure you wipe.
Click to expand...
Click to collapse
-Taken from the guide
At the first time I rebooted it took me back to recovery, so using logic I rebooted again and now it is stuck at the T-Mobile G1 screen (the one before it normally shows the android)...
I know it's supposed to take several minutes.. but 30minutes is ridiculous -.-"
Can somebody please help me out before I do something stupid and remove the battery? Thanks so much..
You need to read a bit more then, because you would have learned that you have to install the 1.6ADP fro Htc before installing a cyanogen rom, that is one of the things you would know if you followed the guide in his thread...
-Best Regards
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
Don't think so It didn't say anything in this guide about that and several comments below recently show that they succeeded with the process..
tk112190 said:
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
Don't think so It didn't say anything in this guide about that and several comments below recently show that they succeeded with the process..
Click to expand...
Click to collapse
You have to listen to cyanogen plus that might be a different rom like enom or something.Cyanogen has a different maybe tricky install method.
You need to goto his thread.
-Go to http://developer.htc.com/adp.html
-DL the 1.6 "recovery image" the file name is - signed-dream_devphone_userdebug-ota-14721.zip
-Then DL CyanogenMod-XXXX
-put them both on your SD card
-Boot up into Amon_RA recovery by rebooting and holding the home button, do a wipe.
-update using any zip to that "recovery image" (signed-dream_devphone_userdebug-ota-14721.zip)
(it should auto reboot install radio then reboot again and load back up to the CMrecovery img screen)
-Then update any zip usig CyanogenMod (update-cm-xxxx-signed.zip)
-Then reboot the phone
Thanks a lot man.
I found the 1.6 ADP file and I have it downloaded onto my computer. Is there anyway I can put this on my SD card? It won't let me.. :/ If I could somehow get this on there, run it.. and THEN run the cyanogenrom.zip I think it could work again?
You need to delete the partitions with console while in recovery mode.
1.console
3.parted dev/block/mmcblk0
4.print
rm 1
rm 2
rm 3
quit
reboot recovery
Dont rename any of the files just leave them.
Now try it on your pc.
You need to delete the partitions with console while in recovery mode.
1.console
3.parted dev/block/mmcblk0
4.print
rm 1
rm 2
rm 3
quit
reboot recovery
Dont rename any of the files just leave them.
Now try it on your pc.
Thanks a lot for the help, I really appreciate it.
I took your advice and did those steps and it rebooted me into recovery like you commanded. I plugged it via USB into my computer hoping that the computer would recognize it and let me put the file on the SD card - but to no avail.
What is the next step I can take?
http://code.google.com/p/sapphire-port-dream/
I loaded the radio first...
and then I loaded the SPL...
and then I loaded the ROM...
I didn't go out of order. Was the problem that I didn't have the 1.6 ADP on my SD?
@Ace42: If I get a card reader and add the 1.6 ADP (signed-dream_devphone_userdebug-ota-14721.zip) to my sd card.... and load it. Can you tell me what to do from there?
Do I load that zip and then reload the ROM?
You may want to try Dwang1.13 rom. I don't think his rom requires the extra step to get the google apps.

[Q] HELP! Maybe brick?

I was trying to fix my NC and install the 1.0.1 firmware. So I tried to format everything back to factory setting so I went into clockwork mod recovery and thought formatting the system partitions would restore me back to factory settings. Well I formatted "boot" and now it will not boot.
tl;dr I formatted boot, is it bricked?
help?
wolffboy212 said:
I was trying to fix my NC and install the 1.0.1 firmware. So I tried to format everything back to factory setting so I went into clockwork mod recovery and thought formatting the system partitions would restore me back to factory settings. Well I formatted "boot" and now it will not boot.
tl;dr I formatted boot, is it bricked?
help?
Click to expand...
Click to collapse
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Do "Method one: Eight interrupted Boots" and post what happens afterwards
As I understand it, it is not bricked. You need to go read both the Nookie Froyo thread and the Clockwork Thread in the Nook Color Development Subforum. There is a way to put Nookie Froyo on an sdcard. You then boot with that and there's a way to put stuff back on the NC.
Do you have a Clockwork backup?
If you can boot back into Clockwork, there are some copies of other folks nandroid backup available. You can then put that on your sdcard and restore it.
I don't have the exact answer for you, but I'm sure it can be fixed.
Geezer Squid said:
As I understand it, it is not bricked. You need to go read both the Nookie Froyo thread and the Clockwork Thread in the Nook Color Development Subforum. There is a way to put Nookie Froyo on an sdcard. You then boot with that and there's a way to put stuff back on the NC.
Do you have a Clockwork backup?
If you can boot back into Clockwork, there are some copies of other folks nandroid backup available. You can then put that on your sdcard and restore it.
I don't have the exact answer for you, but I'm sure it can be fixed.
Click to expand...
Click to collapse
Paul22000 said:
Do "Method one: Eight interrupted Boots" and post what happens afterwards
Click to expand...
Click to collapse
When I press the power button nothing happens. I.E. screen stays black. Would your guy's ideas work if you can boot at all?
wolffboy212 said:
When I press the power button nothing happens. I.E. screen stays black. Would your guy's ideas work if you can boot at all?
Click to expand...
Click to collapse
I had the same thing happen. I tried plugging it into my Macbook, but nothing happened. I plugged into my Windows PC, and it came back to life.
A nookie froyo SD card would work fine. Restore from there manually. Next time make a nandroid and do not delete things that you do not know...
Syco54645 said:
A nookie froyo SD card would work fine. Restore from there manually. Next time make a nandroid and do not delete things that you do not know...
Click to expand...
Click to collapse
i have a nandroid back up and i cant get into recovery mode.
Because you deleted boot. Use a nookie froyo SD card and put the contents of boot back manually.
wolffboy212 said:
i have a nandroid back up and i cant get into recovery mode.
Click to expand...
Click to collapse
Which button combo are you trying to use to boot into recovery mode? If you haven't already, make sure you're using the three-button method.
Sent from my Nooted friend...
I have gotten it to boot to froyo on my sd card.
Now I need help restoring the boot partition from there.
Thank you very much with the support so far
It is not three buttons. Only need home and power.
wolffboy212 said:
I have gotten it to boot to froyo on my sd card.
Now I need help restoring the boot partition from there.
Thank you very much with the support so far
Click to expand...
Click to collapse
I am not certain what to do exactly as I have never used nookie froyo. Generally you are going to want to do
modified /system/boot
mount -t vfat /dev/block/mmcblk0p1
then put the files back in there from in nookie froyo.
Someone else may have the exact way. Sorry I cannot be of more help but that will mount boot when in stock. Of course you will have to mount system as RW as well.
Syco54645 said:
I am not certain what to do exactly as I have never used nookie froyo. Generally you are going to want to do
modified /system/boot
mount -t vfat /dev/block/mmcblk0p1
then put the files back in there from in nookie froyo.
Someone else may have the exact way. Sorry I cannot be of more help but that will mount boot when in stock. Of course you will have to mount system as RW as well.
Click to expand...
Click to collapse
Bare with me I know very basic unix and linux commands but I do have the brain capacity to figure things out (not boot partitions).
I was on the command line and I couldn't get into the nook color stuff just the nookie froyo stuff on the sdcard.
suggestions?
Please read CW recovery thread. All answers are in there!
Really, please take time to browse through existing threads before posting questions which have already been answered several times.
Anyway, considering the number of people asking, here goes:
Note: You can do all this from the Nook, without the need of ADB, except for the fact that you will need gapps on nookie in order to install terminal and root explorer (although you could install those apps by directly installing APK's), see http://nookdevs.com/NookColor:_Nookie_Froyo_Tips, Third-party app support
Please read entire thread before attempting anything!
- Boot into nookie with market installed.
- Install terminal emulator.
- Install root explorer
- Create a new folder at root (/), for example "boottmp" => "/boottmp"
- Launch terminal emulator
- type: "su"
- type: "mount /dev/block/mmcblk0p1 /boottmp"
- type: "echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt" (this will force reset on next boot, as if you did 8 failed boots)
- open browser
- Download boot.zip from here: http://forum.xda-developers.com/showpost.php?p=10470539&postcount=268
- copy zip content to "/boottmp", by replacing existing files
- shutdown
- remove sdcard
- power up, you should see installation process after splash screen. Wait for it to finish, and it will reboot.
- power off
- Next you need to reset to factory settings:
- Boot while using power button and N button. Should boot to menu allowing reset. Proceed with reset.
Boot and be happy.
OR,
If you're able to access ADB (available when booting CW recovery and mounting /system and /SDcard, format from android required on SD to work here), CREDIT GOES TO Duloz, try this:
adb push uRecRam.bak /sdcard/
adb shell
su
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
mkdir /system/boot/
mount -t vfat /dev/block/mmcblk0p1 /system/boot
cat /sdcard/uRecRam.bak > /system/boot/uRecRam
umount /system/boot
rmdir /system/boot
Click to expand...
Click to collapse
Note: Don't worry about errors concerning unmount.
If you're not back in business, post your questions, being very clear about what worked and what didn't.
Thank you.
Sent from my HTC Desire using XDA App
Back from Clockwork Recovery to Virgin (Factory) Recovery ... works like a charm!
samuelhalff said:
Please read CW recovery thread.
- Boot into nookie with market installed.
- Install terminal emulator.
- Install root explorer
- Create a new folder at root (/), for example "boottmp" => "/boottmp"
- Launch terminal emulator
- type: "su"
- type: "mount /dev/block/mmcblk0p1 /boottmp"
- type: "echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt" (this will force reset on next boot, as if you did 8 failed boots)
- open browser
- Download boot.zip from here: http://forum.xda-developers.com/showpost.php?p=10470539&postcount=268
- copy zip content to "/boottmp", by replacing existing files
- shutdown
- remove sdcard
- power up, you should see installation process after splash screen. Wait for it to finish, and it will reboot.
- power off
- Next you need to reset to factory settings:
- Boot while using power button and N button. Should boot to menu allowing reset. Proceed with reset.
Boot and be happy.
Click to expand...
Click to collapse
Works perfectly, thanks! I actually used adb instead of root explorer to do the copy and mount (etc.) commands, and did a manual 8-times power start interruption, but essentially the same. This made my poor "sound-failing" Nook a virgin again so I can swap it out at the store today. Crossing fingers that they will provide quick and easy exchange service (and let me test the sound on the replacement before I leave the store!)... Then, back to Autonooking (and even back to Clockwork Recovery...) again; now that I know how to go back and forth.
Owe you (or y'all) a beer!

Categories

Resources