Related
I was trying to upgrade to CM6 from CM5 and was facing lot of issues so I followed below process and got it worked. I thought of sharing it with everybody as lot of person are having issues.
I know most of the information is available on XDA but not on a single place.
I have made a separate thread because A2sd and SWAP are not supported by CM6 officially.
This is not an official method of installing CM6, this is how I got it worked and you can use it for reference.
1) Preperation: You need to get the below mention files, Please get these files from below mentioned thread:
a) CM6 and Gaaps
b) CustomMTD Patch - You only need FR-recovery and FR-boot latest version.
c) Script for a2sd and swap - get the latest script.
d) Fastboot - Fastboot should be setup and working, If you are on Linux go here
e) SD Card Partition - If you are not sure how to partition the sd card. If you want to use a2sd and swap, please partition your sd-card.Store all files on root of sd-card.
2) Connect the phone to PC, do not mount the phone.
3) Wipe the phone:
a) Boot into recovery(reboot while holding home and power). Wipe everything.
b) Boot in fastboot mode. (reboot while holding back and power)
Enter the command in terminal or command prompt on the PC
fastboot erase system -w c) reboot into recovery.
4) Install the custom MTD. (If you already have custom MTD then this step is not required.)
a) Flash customMTD fr-recovery file.
b) Reboot into recovery.
5) Install CM6 Gapps and boot loader.
a) Flash CM6
b) Flash Gapps
c) Flash Boot Loader fr-boot file
d) reboot phone
6) Once phone is booted and you are on the home screen, go to
CyanogenMod Settings > Application Settings > Install location - Set Install location as Internal, make sure allow application moving is not checked.
CyanogenMod Settings > Performance Settings - make sure that Compcache, JIT, dithering is not checked. If something is checked please uncheck it.
Lock home in memory can be checked, but some guys has reported that it drains a lot of battery.
Reboot the phone.
7) Go to terminal type below code
su
sh /sdcard/fr-patch140.txt a2sd
It will ask if you want to install a2sd, type Y and press enter. Once APKManager is installed, type quit to exit.
Reboot the phone.
8) If you are not using a2sd and want to setup swap, please enter the below command in the terminal otherwise continue to step 9.
su
sh /sdcard/fr-patch140.txt sdext
reboot the phone.
9) Go to terminal type below code
su
sh /sdcard/fr-patch140.txt swap
It will ask for swappiness, I use 60 there, but its your own preference. After that it will ask you if you want to use swap-file, press n and enter.
After this enter below to terminal
FreeIf you get swap setup it will show in front of swap in terminal, if the result show zero swap then reboot and do the step 9 again.
Now you have a CM6 with apps2sd and swap. All the newly installed apps will automatically go to ext.
If you don't like 3d gallery and want it to replace it with old gallery..This has been provided by ZilverZurfarn on CM6 thread.
Extract Gallery.apk from a older CM update (like 5.0.8) somewhere (c:\temp in the example below)
Using adb:
adb remount
adb shell rm /system/app/Gallery3D.apk
adb push c:\temp\Gallery.apk /system/app/Gallery.apk
Also there are some apps which I don't prefer, as I don't use android native keyboard, Android browser, POP email, amazon MP3 etc. So I have created a script for my use which has been shared and it can be run from the terminal..
download remove-app-v1.0.txt and store it to root of your sd card. than enter below commands in terminal
su
sh /sdcard/remove-app-v1.0.txt
currently this script will remove below mention apps based on user input.
Amazon MP3, Live Wallpaper picker, CM Wallpapers, POP Email, Android Native Browser, Android Native Onscreen Keyboard, Genie Widget...
Note: - Before removing browser and keyboard please make sure you have a replacement for them.
I do not take any credit for work, its just a reference for installing CM6. Thanks to Cyanogen and team, Firerat, Lbcoder for producing these amazing roms and methods.....
Please provide your feedback and suggestion for the guide.
If you like my guide and want to Donate
Can I have swap without app2sd?
I skipped the app2sd part, but the swap wouldn't work.
it didn't ask me about the swap file.
It ended with:
use
/system/bin/swappy on # to turn swap on
supa2001 said:
Can I have swap without app2sd?
I skipped the app2sd part, but the swap wouldn't work.
it didn't ask me about the swap file.
It ended with:
use
/system/bin/swappy on # to turn swap on
Click to expand...
Click to collapse
Yes, swap can be there without A2sd..
Do you have Fr-Patch139.txt script or any other version...could you please reboot and so the step 8 again
I did it many times
Do I need to create some files like userinit ?
Thanks for replying.
supa2001 said:
I did it many times
Do I need to create some files like userinit ?
Thanks for replying.
Click to expand...
Click to collapse
Try below command:
sh /sdcard/fr-patch139.txt sdext
reboot the phone
sh /sdcard/fr-patch139.txt swap
If this doesn't work, could you please pass on the message you are getting from the script.
G1sanju said:
Try below command:
sh /sdcard/fr-patch139.txt sdext
reboot the phone
sh /sdcard/fr-patch139.txt swap
If this doesn't work, could you please pass on the message you are getting from the script.
Click to expand...
Click to collapse
It works now. Thanks.
What does sdext do ?
When I ran sdext, it said "danger detected" though, is it still safe?
Same thing appeared when I did swap.
G1sanju said:
I was trying to upgrade to CM6 from CM5 and was facing lot of issues so I followed below process and got it worked. I thought of sharing it with everybody as lot of person are having issues.
I know most of the information is available on XDA but not on a single place.
I have made a separate thread because A2sd and SWAP are not supported by CM6 officially.
This is not an official method of installing CM6, this is how I got it worked and you can use it for reference.
1) Preperation: You need to get the below mention files, Please get these files from below mentioned thread:
a) CM6 and Gaaps
b) CustomMTD Patch - You only need FR-recovery and FR-boot latest version.
c) Script for a2sd and swap - get the latest script.
d) Fastboot - Fastboot should be setup and working, If you are on Linux go here
d) SD Card Partition - If you are not sure how to partition the sd card. If you want to use a2sd and swap, please partition your sd-card.Store all files on root of sd-card.
2) Connect the phone to PC, do not mount the phone.
3) Wipe the phone:
a) Boot into recovery(reboot while holding home and power). Wipe everything.
b) Boot in fastboot mode. (reboot while holding back and power)
Enter the command in terminal or command prompt on the PC
fastboot erase system -w c) reboot into recovery.
4) Install the custom MTD. (If you already have custom MTD then this step is not required.)
a) Flash customMTD fr-recovery file.
b) Reboot into recovery.
5) Install CM6 Gapps and boot loader.
a) Flash CM6
b) Flash Gapps
c) Flash Boot Loader fr-boot file
d) reboot phone
6) Once phone is booted and you are on the home screen, go to
CyanogenMod Settings > Application Settings > Install location - Set Install location as Internal, make sure allow application moving is not checked.
CyanogenMod Settings > Performance Settings - make sure that Compcache, JIT, dithering is not checked. If something is checked please uncheck it.
Lock home in memory can be checked, but some guys has reported that it drains a lot of battery.
Reboot the phone.
7) Go to terminal type below code
su
sh /sdcard/fr-patch139.txt a2sd
It will ask if you want to install a2sd, type Y and press enter. Once APKManager is installed, type quit to exit.
Reboot the phone.
8) Go to terminal type below code
su
sh /sdcard/fr-patch139.txt swap
It will ask for swappiness, I use 60 there, but its your own preference. After that it will ask you if you want to use swap-file, press n and enter.
After this enter below to terminal
FreeIf you get swap setup it will show in front of swap in terminal, if the result show zero swap then reboot and do the step 8 again.
Now you have a CM6 with apps2sd and swap. All the newly installed apps will automatically go to ext.
If you don't like 3d gallery and want it to replace it with old gallery..This has been provided by ZilverZurfarn on CM6 thread.
Extract Gallery.apk from a older CM update (like 5.0.8) somewhere (c:\temp in the example below)
Using adb:
adb remount
adb shell rm /system/app/Gallery3D.apk
adb push c:\temp\Gallery.apk /system/app/Gallery.apkI do not take any credit for work, its just a reference for installing CM6. Thanks to Cyanogen and team, Firerat for producing these amazing roms and methods.....
Please provide your feedback and suggestion for the guide.
Click to expand...
Click to collapse
Thanks mate this will really help me to put my apps on SDcard..as past days m really trying to get my phone memory safe...
supa2001 said:
It works now. Thanks.
What does sdext do ?
When I ran sdext, it said "danger detected" though, is it still safe?
Same thing appeared when I did swap.
Click to expand...
Click to collapse
"danger detected" message is for SPL, It checks for the SPL first and you have danger spl installed.
By default CM6 does not mount ext partition as it does not support a2sd right now. sdext creates a mount point for ext partition. a2sd internally does that but as you are not using a2sd this was not done.
vermaekansh said:
Thanks mate this will really help me to put my apps on SDcard..as past days m really trying to get my phone memory safe...
Click to expand...
Click to collapse
Thanks, If you use this guide then please provide your feedback and suggestion towards it.
Sorry, but is there a script to disable swap? I am gonna do some test to see what works best.
Thanks.
supa2001 said:
Sorry, but is there a script to disable swap? I am gonna do some test to see what works best.
Thanks.
Click to expand...
Click to collapse
In the terminal
sh /sdcard/fr-patch139.txt rev swap
this will turn the swap off.
Watch out...newbie in the room
Okay, you are going to love this.... I'm sorry if this is too long but I hope you can help a newbie trying to learn this stuff!
I am REALLY new to all this, and did a Root and Rom Update as the Unlockr.com videos taught me, to get CM6. And then also added the gapps file because I read a thread that that was needed to get gmail and the market on my phone. Once rebooted, everything worked ok but slow. Then I noticed that my gmail wasn't syncing, and then it started to force close. So I did a wipe and loaded CM5 because I saw on a thread that that was faster for the G1. With all of this, after reading your thread and suggestion, I am wondering...
1. Is CM6 slow for you?
2. Should I have loaded gapps? IS that how to get gmail and should it sync automatically? If not, is there a way to make it?
3. Should I stick with CM5 or try CM6 following these suggestions??
And big ones.... I wish there was a website somewhere with definitions to all the terms and apps used. Lol.. I Google all of them but don't always find anything that actually describes what they are.
Swap and app2sd were mentioned on the video instructions for loading a new ROM but do they automatically come in the ROM zip files? Because in the video they didn't load them separately. They partition the card "for" them, but don't show installing them. Obviously I assume App2sd is a program to store your apps on your sd card. Is this something that I SHOULD install? Is swap something I should install?
And what is a CustomMTD Patch? Annnnnnd, what is fastboot??
I know this is a lot of questions... I decided to ask them all here because they pertain to this thread because I'm wondering if I should do this...
Thanks for any and all answers!
I would assume that you have a G1, and my answer is based on that assumption. If you have different phone let me know.
1. Is CM6 slow for you?
If I don't use a2sd and swap, answer is yes. I install lot of apps, with cutomMTD it works fine in starts but slows down after some time. With a2sd and swap it is worth a try.
2. Should I have loaded gapps? IS that how to get gmail and should it sync automatically? If not, is there a way to make it?
CM roms does not distribute google apps with the rom as its not legal. So if you want gapps then yes that file has to be flashed. CM6 can be run without gapps, but you won't get gmail, market etc..once you have gmail it should sync automatically.
3. Should I stick with CM5 or try CM6 following these suggestions??
CM5 is quite stable rom and runs fine. Choice is yours...CM6 is in initial stages, but is good too...I go with CM5 for my daily driver as a2sd is not officially supported. It will be there in CM6.1....
And what is a CustomMTD Patch? Annnnnnd, what is fastboot??
G1 was build with a low memory and the way internal memory has been partition todays rom can't fit into it. That's why dangerSPL, but there is a risk involved in installing dangerSPL. If you don't follow the instruction you can brick your phone. CustomMTD is a safe method. This increase the size of data partition so you can install more apps internally. link for that thread is in first post.
a2sd is a way to store apps on sdcard, sdcard needs to be partitioned to support that..step 1 - e in my guide. That's a manual way of doing it. If you have AmanRA recovery then it will have a menu option for that. Most of the rom supports it automatically, so if you have sd card partition then rom will automatically do that.
CM6 does not support a2sd so it has to done in different way. CM5 supports it but in settings - application - a2sd has to be checked on to move your apps to sdcard.
Swap is kind of extra memory to help running the applications. if you run multiple application together then you need swap on CM5 and CM6.
G1sanju said:
CM5 is quite stable rom and runs fine. Choice is yours...CM6 is in initial stages, but is good too...I go with CM5 for my daily driver as a2sd is not officially supported. It will be there in CM6.1....
Click to expand...
Click to collapse
So when CM6.1 is comming out for G1..do you have nay idea about HCTCLAY's ROM over CM6
vermaekansh said:
So when CM6.1 is comming out for G1..do you have nay idea about HCTCLAY's ROM over CM6
Click to expand...
Click to collapse
Nope I don't follow htcclay but it is based on CM so should be updated
Sent from my HTC Dream using XDA App
G1sanju said:
Nope I don't follow htcclay but it is based on CM so should be updated
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
No hard feeling for CM but for me htcclay's ROM's are more stable than CM's.....any release date for CM6.1 for G1?
vermaekansh said:
No hard feeling for CM but for me htcclay's ROM's are more stable than CM's.....any release date for CM6.1 for G1?
Click to expand...
Click to collapse
Roms are personal preferences, I also tried lot of roms before settling on CM... and for CM there are no eta it will be released when it's done...
Sent from my HTC Dream using XDA App
WOW!
THANK YOU!!! You are awesome for going through all of those!
Yes, it is a G1.
Are there any features in CM6 that aren't in CM5, or is it faster than CM5 with the ap2sd & swap?
I believe I partitioned the sd card when I loaded the CM6 ROM.
So I'd like to try the CM6 with the ap2sd, swap and the CustomMTD. I do have the AmanRA recovery, but not sure about how to select the ap2sd.
Any chance you would tell me how to get the ap2sd, swap and CustomMTD on the phone if I have already Flashed CM6 on there?
Thanks again, regardless. The info you gave me helped me learn a little more. I'm still a bit confused about what fastboot is though. But I will just keep at it and keep learning!
Are there any features in CM6 that aren't in CM5, or is it faster than CM5 with the ap2sd & swap?
CM6 is based on froyo, latest version of android...its good and yes speed is comparable. Also CM has added new stuff in it, like fully customizable power bar and other stuff...Full changelog is there in CM6 thread.
I believe I partitioned the sd card when I loaded the CM6 ROM.
So I'd like to try the CM6 with the ap2sd, swap and the CustomMTD. I do have the AmanRA recovery, but not sure about how to select the ap2sd.
For CM6 a2sd is through script, instruction is in first post. I have included customMTD also there. So if you follow the guide, you will be having customMTD, a2sd and swap...swap require an partition on your sdcard, if you don't have that partition then it will ask for swap file.
Any chance you would tell me how to get the ap2sd, swap and CustomMTD on the phone if I have already Flashed CM6 on there?
you can wipe and start over again, first post should be good for you.
Thanks again, regardless. The info you gave me helped me learn a little more. I'm still a bit confused about what fastboot is though. But I will just keep at it and keep learning!
Oh I forgot about the fastboot, fastboot and adb are tool, which give an option to control, flash and do other thing on the phone from PC. The link for setup guide is in first post.
Thanks again!!
Man! You are great! Thanks again for all your help! Now let's see if I can manage to follow your thread and not brick my phone! Lol
Until next time....
This is mostly for anyone who runs kifno's rocksteady ROM, along with his scripts. Essentially, I am not sure how to install both of them together properly. It seems the instructions kind of overlap? And I do not want to wipe anything at the improper time. So if someone could edit these instructions so I could follow them in sequence, I would be grateful. If it makes a difference, I will be flashing the uncapped kernel (768mhz).
P.S. - I've been running xda roms for about a year now, and just wanted to say thank you for all your hard work and contributions to the open-source community. To ALL developers
ROM INSTRUCTIONS
Instructions:
1. Backup EVERYTHING (SD Card, Titanium Backup, Nandroid)
2. Wipe EVERYTHING (Data/Factory Rest, Wipe Cache, Format Boot, System, Cache, and Data, Wipe Dalvik)
3. Download and Copy RockSteady & Gapps to your sdcard
Get Rock Steady Here
Get Gapps Here
4. Flash RockSteady and Gapps and Reboot
5. Skips gapps setup and reboot into recovery and wipe data, cache, and dalvik again
6. reboot into system
7. After setting up gapps, in the menu > sense settings > ui setting > check tink ab and make the scale factor 1 instead of 7
8. Long press home screen and create a custom widget with phone as the activity. Then click the phone icon and us es file explorer or gallery and use the transparent.png I provided for you on the root of your SD card. Okay the custom widget and the drag and drop it over the phone button. Do the same for right sense dock button (choose a custom activity of your choice)
9. Add the sense clock by using the fancy widget widget i provided for you.
10. Choose a new wallpaper if you wish by picking one of the sense wallpapers I provided for you on your sdcard's root directory.
11. Please see here about widgetlocker. Please purchase this app from the market to use as the sense lockscreen. I REALLY RECOMMEND IT. And you can easily disable the default lockscreen once you start using this app by going into the cyanogenmod settings > tablet settings > and checking disable lockscreen.
SCRIPT INSTRUCTIONS
Installing Instructions (Recovery Menu):
Difficulty: Easy
Download the Kifno Tweak's Universal Script v1.5 from below:
Get the Capped 691mhz Build Here
Get the Uncapped 768mhz Build Here
Charge phone to 100% and leave on the charger during this process
Put the .zip on the root of your sd card
Reboot into recovery
Backup Everything (Apps, SD Card, etc) & Wipe Everything (Data, Sd-Ext, Cache, System, Boot, Dalvik-Cache)
Flash Rom
Fix permissions if using clockwork recovery
Flash your capped or uncapped build
Delete data, cache, and dalvik
Reboot
Reboot Recovery
Delete data, cache, and dalvik
Unplug Charger and do not plug back in until your phone dies.
Reboot into recovery once it is dead by connecting charger.
Wipe battery stats
Charge to 100% and repeat the discharging, wiping, and charging process about 3-5 times
Enjoy the battery life and performance
The red is the confusing part. Thanks!
Ill post instructions in about an hour or two. Glad to see you're using my work though and sorry for the confusion.
Sent from my HERO200 using XDA Premium App
The Muiu Camera Doesnt Work :[
backup everything
wipe everything
flash rom
flash gapps
flash v1.5 stable
reboot into rom
skip gapps and reboot recovery
wipe data,cache, and dalvik
reboot into rom
then follow my set up instructions for my rom after that process
enjoy
also miui camera works on 4-21-11 it does. are you using the latest version?
Yes I amm
Sent from my HERO200 using XDA App
Jurellz said:
Yes I amm
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Oh sorry didn't see your reply but try the latest one now
So I was able to successfully install CM7 on my new NC last week and got it just the way I want it. Now I would like to try Miui. I have never used Rom Manager (not working on the Epic), and would like to know how to go back and forth using that app.
Can someone break it down so I can follow along painlessly?
ROM manager is nice for doing incremental updates. What you want to know how to use is clockwork mod.
I'm in the car ATM, but I'll be at my computer in 15 or so. I'll write up what you need.
Sent from my Vortex using Tapatalk pro
OK, first turn on wifi. Then, from within Rom manager check and make sure you have the latest Clockworkmod flashed.
at the top it will say 'current recovery' if that's 3.2.0.1 then you're good, if not, select 'flash Clockworkmod'
if you get a selection between old and new, select new.
Now would be a good time to make a directory on your SD-card called 'ZIPS' and put the .zip files of whatever rom you want to flash.
CM7 nightlies
MIUI
And, you'll want to pickup the Gapps (google applications) zip from here
Clockworkmod is a recovery program. It is able to boot ahead of anything else and has access to every partition. From within clockwork mod you're able to do system level backing up, restoring, or just plan changing. I'll give you the run down on flashing different roms.
To boot Clockworkmod just turn off the nook, then hold the [pwr]+['n' button] until you see the text 'booting into recovery' release the buttons.
Now within clockworkmod [vol+] is up, [vol-] is down, ['n' button] is select, and [pwr] is back.
First we need to backup your current data. With this backup you will be able to restore to that EXACT time and setup. Make as many as you want, feel free to rename then to keep track.
->backup and restore->Backup
The backup is saved to the SD-card in the Clockworkmod folder
Then we need to wipe all that uncool old data from the emmc. Pick one, not both.
Scenario #1: upgrading versions of the SAME ROM
->mounts and storage->unmount /cache
->mounts and storage->format /cache
->advanced->wipe dalvik cache
Scenario #2: SWITCHING from one type of ROM to another
->mounts and storage->unmount /cache
->mounts and storage->format /cache
->mounts and storage->format /data
->mounts and storage->format /system
->advanced->wipe dalvik cache
->wipe data/factory reset (a little redundant, but it can't hurt)
Now to install the new ROM or ROM version
->install zip from sdcard->choose zip from sdcard->ZIPS/->ROM file
->install zip from sdcard->choose zip from sdcard->ZIPS/->Gapps file (should look something like this: gapps-gb-20110613-siged.zip)
After you've installed a new update of a ROM or a new ROM you'll have to fix the permissions.
->advanced->fix permissions
Reboot and you're done.
This should cover all of your flashing needs. If I missed something please point it out. If something doesn't work just post it, someone will know.
Awesome breakdown! Now to get apps back, do I need to use titanium or can I go to restore in CWM and do it that way?
Thanks again, that was very useful!
I seem to remember that titanium backup's app data restore does not work for CM7, only restoring the app itself works.
The restore in CWM will REVERT you back to when you backed up, undoing everything you've done since.
I can confirm that Titanium backup does work in CM7 I use it all the time to restore apps and data.
It also worked after I installed Miui. Batch restored all of my apps and data, no FC's.
Glad to hear it worked ok for you.
Can anyone please help?
I just installed the Ultimate JB ROM XXLSA 4.1.2 v5 upgrade on top of v4.
All went perfectly well and I was able to enter all my setup and account details after the initial boot of the phone.
When I tried to re-install apps from Google Play, however, (Titanium Backup Pro, Quickboot) the phone hangs at the Samsung Splash screen and won't go any further. I re-tried the procedure 3 times but each time the result is the same.
Can anyone tell me what the problem could be? I followed all the instructions about wiping etc. correctly.
Trevor
v4 and v5 use completely different bases (LS7 and LSA).
I would save everything to my ext SD card.
Then goto Settings > Backup & Restore > Factory Reset (don't click on format external sd card).
Your phone will restart and do some crazy things. Then restart again.
When you get to the welcome page, or bootloop... take the battery out (its safe).
Then hold Vol Up, Home and Power (let go of Power after ~5-15sec) and goto recovery.
In recovery, wipe cache.
Then format data.
Then format system.
Then format cache.
Then wipe Dalvik cache.
Then install the v5 zip.
It shouldn't restart automatically, but it might, don't worry let it.
Now you should have a fully, fresh, clean install of v5.
Connect to your wifi, go through the start up.
Goto SuperSU and update binary.
Goto Play Store and install TiBu.
Open TiBu and grant it root access.
Close TiBu.
Connect phone to PC, then copy your TitaniumBackup folder into your sdcard directory.
Open TiBU and now, it will see your previous saves.
Restore your apps + data.
Presto! No bootlooping and no App FC !
Thanks for going to all the trouble to write all that out.
I followed the instructions to the letter but no, same result I'm afraid: it worked fine but as soon as I installed Titanium and granted root access, it asked me to choose to restore the original phone ID which I did. The phone rebooted but then wouldn't go past the "Samsung Galaxy Note Gt-N7000" screen.
I have no choice but to restore from my Nandroid backup. This is really p****ng me off but at least I can restore v4 easily.
Thanks again
Trevor
Kangal said:
v4 and v5 use completely different bases (LS7 and LSA).
I would save everything to my ext SD card.
Then goto Settings > Backup & Restore > Factory Reset (don't click on format external sd card).
Your phone will restart and do some crazy things. Then restart again.
When you get to the welcome page, or bootloop... take the battery out (its safe).
Then hold Vol Up, Home and Power (let go of Power after ~5-15sec) and goto recovery.
In recovery, wipe cache.
Then format data.
Then format system.
Then format cache.
Then wipe Dalvik cache.
Then install the v5 zip.
It shouldn't restart automatically, but it might, don't worry let it.
Now you should have a fully, fresh, clean install of v5.
Connect to your wifi, go through the start up.
Goto SuperSU and update binary.
Goto Play Store and install TiBu.
Open TiBu and grant it root access.
Close TiBu.
Connect phone to PC, then copy your TitaniumBackup folder into your sdcard directory.
Open TiBU and now, it will see your previous saves.
Restore your apps + data.
Presto! No bootlooping and no App FC !
Click to expand...
Click to collapse
Mystery solved - well partly. Turns out Titanium Backup Pro was causing it on my phone for some reason. This was naturally the first app I wanted to install so I could restore apps one by one from the Nandroid backup. I tried Quickboot too which also caused the same problem so because TB and then QB did the same thing I assumed every app was going to cause trouble. Shouldn't jump to conclusions, I know.
I have JB Ultimate XXSLA v5 installed and am restoring my apps one at a time from Google Play and making new Nandroid backups as I go along.
And now I just tried installing TB free version - the phone boots normally! Then I installed the TB Pro version and again the phone boots normally. When TB was the first app I installed after the ROM upgrade it hung up the phone every time on 6 attempts. I'll try re-installing Quickboot now and see what happens. Conclusion: I must have been doing something in the wrong sequence but can's see what.
Many thanks for your help.
Trevor
sacentre said:
Thanks for going to all the trouble to write all that out.
I followed the instructions to the letter but no, same result I'm afraid: it worked fine but as soon as I installed Titanium and granted root access, it asked me to choose to restore the original phone ID which I did. The phone rebooted but then wouldn't go past the "Samsung Galaxy Note Gt-N7000" screen.
I have no choice but to restore from my Nandroid backup. This is really p****ng me off but at least I can restore v4 easily.
Thanks again
Trevor
Click to expand...
Click to collapse
This is to at least avoid the need to boot into CWM recovery every time
Reason:
I immediately flashed my brand new Nook HD+ with the emmc CM 10.1 three weeks ago
The vanilla CM booted in 90 seconds but that was 350 app installs ago and many uninstalls and app updates as well
If I power on the HD+ seem to always get stuck in the boot loop of the CM Logo; I wait up to 10 minutes
It seems booting into CWM recovery via N button on Power on and choosing wipe dalvik-cache allows a rebuild of dalvik-cache for the 350 apps followed by normal boot into CM 10.2
Besides the long delay is there any harm in wiping Dalvik-Cache every time I reboot or poweron?
I believe only this method and CM safe mode are the only way I know to avoid bootloops
Do I need to modify Dalvik-Cache settings/properties to fix bootloops? If not can I automate/ default into the Dalvik-Cache wipe for each poweron / reboot
BTW reason I rebooted a few times is I am still trying to struggling getting USB OTG / USB host mode working
Should I turn off USB debugging if I can not use USB OTG and I also do not use ADB?
TIA
Dave
What is CM safe mode?
The dalvik cache is split into two places. The system app dalvik cache is stored in /cache/dalvik-cache. The installed apps dalvik cache is stored in /data/dalvik-cache. It does no harm to clear those caches periodically. It just takes a while when you reboot for the operating system to rebuild them from the apks.
So you should be able to manually delete the /data/dalvik-cache folder with your file manager just before you reboot. I am assuming that is the one giving you problems. If not it, try the one in /cache.
If you know how to write scripts you can automate it.
Edit: if it turns out to be the dalvik-cache in /cache causing the problem, I have a build.prop setting to move the /cache dalvik to /data.
Sent from my Nook HD+ running CM10.1 on emmc.
Help with automating the Dalvik-Cache wipe
Thanks for the reply Leapinlar!
When I am booting into in CWM recovery and choose the Dalvik-Cache wipe is it wiping out both /data/dalvik-cache and /cache/dalvik-cache?
How long do I realistically need to wait before I can determine I am in a bootloop situation? I do wait 10 minutes but maybe less time?
Does CM 10.1 boot time dramatically increase over time or does adding apps also increase the boot time ?
I found a script on: http://smanager.wikidot.com/scripts:power-scripts[/U "Superclean and reboot "
As a newbie I would like to know which file or directory to put a subset of this script so that it automaticly runs when I poweroff or reboot via the power button even better would be how to add a popup question box asking me if I want to wipe out dalvik-cache as part of the shutdown.
TIA
Dave
leapinlar said:
What is CM safe mode?
The dalvik cache is split into two places. The system app dalvik cache is stored in /cache/dalvik-cache. The installed apps dalvik cache is stored in /data/dalvik-cache. It does no harm to clear those caches periodically. It just takes a while when you reboot for the operating system to rebuild them from the apks.
So you should be able to manually delete the /data/dalvik-cache folder with your file manager just before you reboot. I am assuming that is the one giving you problems. If not it, try the one in /cache.
If you know how to write scripts you can automate it.
Edit: if it turns out to be the dalvik-cache in /cache causing the problem, I have a build.prop setting to move the /cache dalvik to /data.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
The CWM dalvik wipe wipes both of them.
Yes, adding apps increases boot time. The operating system has to verify that the dalvik cache files match the apks. The more apks installed, the longer the boot. If they do not match, it rebuilds them. If they are missing (like after a wipe) it starts rebuilding immediately without checking. 350 apps sounds very high. Do you really need that many?
Some have said that the ability to read emmc decreases with use (kind of akin to defrag on a PC). That is what that trim controversy is all about. There is a process where that can be cleaned up with the trim app, but it has been known to brick certain Samsung memory chips (and some HD+s have them).
I don't know anything about that script or where to put it to execute on power off. You put it either in /system/etc/init.d or /data/local/userinit.d to execute on startup.
And you have still not told me what CM safe mode is.
Sent from my Nook HD+ running CM10.1 on emmc.
safe mode on CM 10.1
safe mode on CM 10.1
Press power button and then press and hold reboot option..
Phone / Tablet will ask you to boot in safe mode or normal mode..
I did this twice in the past
So the apps folder upon reboot is much smaller as most APKs are not loaded in this safe mode
I am kind of a newbie with CM but it is very nice
TIA
Dave
leapinlar said:
The CWM dalvik wipe wipes both of them.
Yes, adding apps increases boot time. The operating system has to verify that the dalvik cache files match the apks. The more apks installed, the longer the boot. If they do not match, it rebuilds them. If they are missing (like after a wipe) it starts rebuilding immediately without checking. 350 apps sounds very high. Do you really need that many?
Some have said that the ability to read emmc decreases with use (kind of akin to defrag on a PC). That is what that trim controversy is all about. There is a process where that can be cleaned up with the trim app, but it has been known to brick certain Samsung memory chips (and some HD+s have them).
I don't know anything about that script or where to put it to execute on power off. You put it either in /system/etc/init.d or /data/local/userinit.d to execute on startup.
And you have still not told me what CM safe mode is.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
[email protected] said:
safe mode on CM 10.1
Press power button and then press and hold reboot option..
Phone / Tablet will ask you to boot in safe mode or normal mode..
I did this twice in the past
So the apps folder upon reboot is much smaller as most APKs are not loaded in this safe mode
I am kind of a newbie with CM but it is very nice
TIA
Dave
Click to expand...
Click to collapse
Huh! That is a new one for me. LOL. Thanks.
If it boots faster in that mode, that tells me you have too many apps.
Sent from my Nook HD+ running CM10.1 on emmc.
Your boot loop sounds similar to the one I had for a while. It just sits at the Cyanogen Mod circle for EVER. The fix for me was to go in and disable 'quick render' in the launcher settings. (Remove the checkmark)
Will try disable 'quick render' in the launcher settings.
Aaron thanks for the info * I will see if helps my bootloop issue
I went to Trebuchet settings to uncheck 'quick render' in the Homescreen panel
TIA
Dave
Solution: quick & dirty automating the Dalvik-Cache wipe
Thanks to Leapinlar for great explanations and patience and
Kudos to Bartito for his Shutdown APK!
Just tested the instructions below on HD+ CM 10.1
Leapinlar can you please verify the commands before other users try this as I am still a Newbie to CM
after following these instructions I powered on the HD+ and the dalvik-cache rebuilt 268 APKs without needing to boot into CWM recovery
This will continue for every poweron and reboot until the script /system/etc/shut.d/rmdalvikdata is removed
The boot process is obviously delayed significantly but hopefully no more bootloops!
1) launch terminal emulator app and type these commands from the terminal:
su
mount -o rw,remount /system
mkdir /system/etc/shut.d
chmod 755 /system/etc/shut.d
echo "rm /data/dalvik-cache/*" > /system/etc/shut.d/rmdalvikdata
chmod 777 /system/etc/shut.d/rmdalvikdata
ln -s /system/etc/shut.d /system/etc/shutdown
exit
exit
2) please, download the "SystemScriptsExecutor-cwminstaller.zip"
from: http://forum.xda-developers.com/showthread.php?t=1387692
Note: I saved it the zip file to the MicroSdXc card
3)install SystemScriptsExecutor-cwminstaller.zip from CWM recovery on Nook HD Plus.
Note: I actually used vi on term with a USB keyboard to create /system/etc/shut.d/rmdalvikdata
and I am not sure the symlink is necessary
It looks correct. And I would leave the symlink in. The Executer may need it.
Sent from my Nook HD+ running CM10.1 on emmc.
I saw the same problem on cm-10.1.3-RC2-ovation: "wallpaper quick render" enabled causes bootup to stall on the animated logo. Clearing cache was the only way to complete with it enabled. Disabling restores the ability to boot and reboot normally.
It's a devious bug as you might only run into it days after enabling the feature. In my case, it was a few days after a fresh CM installation, having setup and installed everything the way I wanted. adb logcat didn't show anything obvious within the boot loop. I spent a while building the installation back from scratch with incremental nandroid backups attempting to find the point where things broke. Glad I found this thread instead!
It'd be nice to have it fixed as quick render makes scrolling between home pages noticeably smoother.
Aaron Camp said:
Your boot loop sounds similar to the one I had for a while. It just sits at the Cyanogen Mod circle for EVER. The fix for me was to go in and disable 'quick render' in the launcher settings. (Remove the checkmark)
Click to expand...
Click to collapse
Thank you sir! I have struggled with this and your suggestion seems to have cured the problem. I have spread the word in 2 other threads.
Wish the developer would see this. Then, perhaps, a fix might be in the future.