Related
I rooted my Hero a long time ago and installed Cyanogen's Recovery Image 1.4 on at the same time.
Over the last couple of days I've finally got hacked off waiting for an official 2.1 ROM to be released and decided to have a play with some of the Custom ROMs. The problem I've run into is that all of the guides talk about erasing data from different directories and partitions but none of them discuss how to do it !?
All I really need to know is if this is something that must be done via adb and what/where the directories are that need to cleared out.
I have searched and trawled but I get the feeling that this step is something that is done antomagically by the newer Recovery Images. If that's the case, would you suggest I upgrade mine ? And to what ?
Thanks for the help
(Really looking forward to playing with VillainROM 6 )
Yep,... Id 1st updrage your recovery to AmonRa 1.6.2.
Use BTDAG's guide in my signature to find out how to install it or I think there are ADB instructions for the installation in the Amon Ra thread.
Once that is done, before you flash a new ROM, turn of your phone, you go into your recovery by holding "HOME" and "POWER" buttons, then go into wipe, then select all of them one by one,....
[Recovery ROM] [07-Mar-2010] RA-hero-v1.6.2
Thanks ddotpatel, I guessed it might be due to the age of the Recovery Image I've got
I'll upgrade this evening
ddotpatel said:
Yep,... Id 1st updrage your recovery to AmonRa 1.6.2.
Use BTDAG's guide in my signature to find out how to install it or I think there are ADB instructions for the installation in the Amon Ra thread.
Once that is done, before you flash a new ROM, turn of your phone, you go into your recovery by holding "HOME" and "POWER" buttons, then go into wipe, then select all of them one by one,....
Click to expand...
Click to collapse
Any idea exactly what stats are erased by the battery stats & rotation settings options?
No idea pal,... but if Im flashing a new ROM without having 100% battery I leave the battery settings wipe.
I assumed that wiping battery stuff makes your phone think your battery is full after the wipe,...
So say its actually at 50%, then you wipe stats and flash a new ROM, then your phone thinks that battery is at 100% so will only charge upto that level.
The only thing I'm basing this on is I have read people say that when flashing a ROM when battery is not 100% they seem to lose battery capacity. But who knows, it could be psychological?
AFAIK battery stats deletes stuff like which programs have been using your battery as well as the currently stored battery figure. I assume that on next boot it checks the battery capacity afresh and goes with that figure.
Rotate one - i assume is to do with application rotation and the g-sensor.
I always wipe this data because it can't hurt - worst case it has to work it out again and it takes an extra 10 secs or so on startup.
Lithium Ion batteries don't have the "memory" problem of older batteries where they forget any charge that is left in the battery when it is put on charge and assume when its removed from charge that it is 100%. They should always stay the same capacity for their entire life duration. Again this is all AFAIK
Aahaaa,...
I always take what you say as gospel BTDAG.
Might have a read up on batteries later,... If I remember,... If I can be arsed!
Do you ever flash ROMs without having 100%?... No problems?
btdag said:
I always wipe this data because it can't hurt - worst case it has to work it out again and it takes an extra 10 secs or so on startup.
[snip]
Again this is all AFAIK
Click to expand...
Click to collapse
I took the same cautious view as ddotpatel. I figured if it's important enough to store in it's own private flash, it's probably holding data related in some way to the physical state of the phone, or an estimate thereof. I'm wary to touch them without ever having seen any solid info on what's there.
I've noticed one or two new ROM threads where the user is told to wipe these stats. I hope no one gets burned as a result.
BTW Also all afaik. It's just that in my case that isn't very far.
Good day all. I recently bought a Nook Color. I'm running CM7.0.2 along with gapps 20110613 from a 16gb SanDisk class 4 SD. When set up the apps (after enabling wifi) I got an error, due to the fact that my sucky router dropped the signal. As a result of this I was not able to download gmail, google maps, etc. My android market runs perfectly but I wanted to flash gapps so as to download gmail and the others. I went into ROM manager and updated to the latest CWM. However, no matter what I do I can't but into recovery. I tried n+power button, reboot into recovery from the power button menu, and from within ROM manager. All no go...it just booted into CM7, so I removed the SD card to boot into stock Nook 1.2 software. When I did this it brought me to the CWM recovery menu (SD card not in). Of course I could not select anything on the menu. Put back in the SD while still in the menu to try select an option but nothing. Shut it down by holding the power button and booted it back up and it went str8 into CM7. Shut down took out SD and it booted into stock Nook 1.2 software. What am I doing wrong guys? I'm trying to flash the overclock kernel and reflash gapps. THANKS
Could the reason gmail, youtube, googlemaps didn't install on setup be due to the fact that I'm not in the USA? If so I'd still like to know what the problem is so I can flash the overclock kernel.
No one has any idea? I know one option is to backup and redo everything, but I'd really like some troubleshooting ideas before.
Did you use the 1.3 image from verygreens thread? If so the old 7.0.* stables are not supported. You will need to back up and redo it either with the old image or a new CM7 version.
---
- Sent from my LG Optimus V using Tapatalk
Yea I used the 1.3 in the thread with 7.0.2. What version cm7 would I need to use with the 1.3? 7.0.3 or a nightly,? Where would I be able to find an older image to work with 7.0.2 and what version of the image should it be?
The 1.3 image won't work with any 7.0.* versions. You should upgrade to either a recent nightly or the 7.1.0 RC. You could find an older image somewhere but there isn't much of a point as you would have to redo it all anyway so why not upgrade? Plus your battery life will improve by a lot as 7.1 RC and the nightlys have deep sleep.
---
- Sent from my LG Optimus V using Tapatalk
As I said many times to newbie who runs CM7 off uSD that do not or should not mess up with ROM Manager. In fact, there are members also confirm that if booting off uSD, ROM Manager has no effect.
Based on what you, OP, described, you had flashed the CwM into the internal memory.
Keep your fingers crossed as I do hope you didn't screw up anything else.
Anyway, using verygreen's 1.3 image along with the latest nightly-built CM7 and the latest 06132001 gapps and boot it off uSD again. You should be fine.
Before that, fix your home wireless network first.
I decided to just go with 7.1RC1 since I wanted the better battery life. Is there a way to check about the CWM on the internal and how would I go about removing it if I did? I ask for warranty purposes ofcourse since I opted for the 2 year extended one. Also to flash upgrades and such, since you don't recomend using ROM manager then how should I go about doing it (i.e. overclocking kernel)?
dna59 said:
I decided to just go with 7.1RC1 since I wanted the better battery life. Is there a way to check about the CWM on the internal and how would I go about removing it if I did? I ask for warranty purposes ofcourse since I opted for the 2 year extended one. Also to flash upgrades and such, since you don't recomend using ROM manager then how should I go about doing it (i.e. overclocking kernel)?
Click to expand...
Click to collapse
1. I never have any issue related to battery with any nightly build that I've ever used. I am currently having the nb153 and it is fantastic.
2. Check CwM and how to remove off the internal memory? I don't know any quick way except restoring the original ROM.
Again, for warranty purposes, strongly suggest running off uSD
3. Updating by loading/copying/dragging the updated files onto the root folder (aka "boot" partition), then TRY loading into Recovery by:
a. combination of power/N buttons if you have skill or
b. let it boot normally into CM7, wait until completely loaded, then reboot and select "recovery" option. Keep yr fingers crossed. This is an easy method but if it doesn't work then option a is the only choice.
Sorry the battery issue was as compared to the current CM7 stable not the nightly. I got everything installed so far besides the overclock kernel. So I will try your recommendation for booting into recovery not using ROM manager.
You don't flash anything when running off an sd card you just boot into recovery and then reboot. Easiest way to get the overclock kernel would be to just upgrade to the latest nightly.
---
- Sent from my LG Optimus V using Tapatalk
I've been running CyanogenMod 7.0.3 on my Desire Z for the last couple of weeks but have been unhappy with the battery life, so thought I'd try installing the Pershoot kernel as it had been recommended elsewhere here.
I downloaded and installed Pershoot using ROM manager but the phone got stuck trying to reboot - I got the blue Android with the spinning arrow going perpetually I waited 10-15 minutes for it to complete, took out the battery, retried, waited another 10-15 minutes but it still wouldn't complete the boot process. In the end I had to restore to my previous backup.
Has anyone successfully deployed Pershoot on an existing CM7 setup?
itm,
I've been running Pershoot on both CM7 and MIUI on my Desire Z without issues. Might just have been a hickup with your handset.
I'd try it again. Just to see.
Cheers mate,
Hopefully you won't run into the problem again.
Thanks for your reply. As a matter of interest, what method did you use to flash the kernel? Did you use ROM Manager?
Hopefully your flashing straight through recovery and not RM. If your not, that might be the problem.
I downloaded Pershoot from Rom Manager and then used the Install feature from Rom Manager which then rebooted into CLOCKWORK RECOVERY and then installed the Kernel.
I didn't run into any problems.
Thanks for the replies. I tried installing a different ROM from a .zip on the SD card (Wildmonk's 2.6.38.8) and this time it worked.
The main reason for checking out alternatives is to compare battery life. How have you guys found battery life compared to the CM7 default kernel?
Also, which version of Pershoot are you running?
I just updated to the latest MIUI release earlier 1.8.19.
My battery life depends on how much I use it... I'm quite a heavy user and I'm getting a little over 24hrs. On the weekend I may get more as I don't use it often up to 30hrs.
I'm currently running on the following:
Hey guys,
I know everyone is going to first think, What the hell, this is too easy what a noob.
Anyway, point is, ive been looking for a tutorial on this for ages and just can´t find one.
On all Android Roms they always just write things like "Also make sure to intall the kernel" and thats it or when you look through generall ROM tutorials for android you just see "Don´t forget to install the coresponding kernel"
Nothing on how to do it.
So I have the following questions please:
1. I want to install this ROM on my HTC HD2
http://forum.xda-developers.com/showthread.php?t=1316632
Click to expand...
Click to collapse
How do I install the kernel for it?
2. It tells me to partition the SD card, I really don´t get what they mean with all of those numbers?
Please send me to a tutorial where it is explained or explain it, it would really be a great great help. Thank you!
Well.
First thing - it depends on whether you want to flash the Magldr or cLK version.
I highly recommend cLK, with it you can use ClockworkMod Recovery, which will allow you to easily install pretty much everything that's in correct zip format.
So if you flash the cLK version, afterwards you just download the kernel (that's in the thread you provided) in the .zip format and save it on your sdcard. Then go into Clockworkmod Recovery (if you don't know what it is, search the net, and study) and flash zip from sdcard. That's it for the kernel.
If you want to use Magldr, I can't help with that, I'm using cLK.
About SD partitioning - there is a good guide here https://docs.google.com/document/d/1dhXJZPjZzBHcAtIE_jfEeuG988UDUaP7GfZk909nNCc/edit?hl=en&authkey=CLDJw80N&pli=1
It's a guide made especially for AmeriCan Android ROM, but the partitioning part is well written and it should work for all ROMs like that.
Just check it out, if you need anything more, let me know.
Thanks man.
This is great.
Did it with cLK and it was really easy.
Thanks!
Edit.
I need some help on this ROM. I tried to post this question in the ROM thread but it wont let me so im hoping someone can help me here.
My phone won´t boot anymore. It just gets stuck at the HTC logo with this ROM installed.
What I did was:
1. Wiped data and cleared cache
2. Installed kernel via CWM (from SD)
3. Installed ROM via CWM (from SD)
4. After succesful install (with out errors at least) i press reboot now.
And from then on its just suck at the HTC logo.
Ive left it for over an hour now just to be sure but nothing.
Can someone tell me what is wrong with it?
Thanks!
Cheesus182 said:
Thanks man.
This is great.
Did it with cLK and it was really easy.
Thanks!
Click to expand...
Click to collapse
No problem mate, if anything more, just ask - here or PM.
Edit:
P.S. if you wanna confirm that you have the new kernel installed, just go to settings, about phone and there you see the kernel info.
I'm going to jump this existing thread as I also have a beginners question on the same subject...
I already installed a ROM (NexusHD2) and having huge battery drain problems (drains from 100% to dead in aprox. 15 hours on 100% standby with no applications running), but having less than 10 posts on this forum, I can't ask in the thread for the particular ROM. But I see a lot running this ROM with a tytung_r14 kernel, so I figured that I probably had to install this as well and I'm going to try it, but one question though...
Was I supposed to install the kernel BEFORE installing the ROM? Or can I just go and install the kernel now and all will be dandy?
Thanks.
Just flash Rom again in Recovery mod then flash kernel later on. It's gonna be fine, I believe.
Sent from my Desire HD using xda premium
Why should I do a recovery flash of my ROM and then flash kernel afterwards instead of just flashing the kernel right now if that is possible?
The ROM was flashed friday afternoon, so it's a pretty clean ROM.
You can flash kernel at anytime, you don't have to reflash anything.
Also, it might not be the kernel, which is responsible for your battery life.
Search for thread called something like ultimate battery guide for android and there are all things you can do to check what's wrong and make your battery life great. I did that, and am very satisfied.
DaneX said:
I'm going to jump this existing thread as I also have a beginners question on the same subject...
I already installed a ROM (NexusHD2) and having huge battery drain problems (drains from 100% to dead in aprox. 15 hours on 100% standby with no applications running), but having less than 10 posts on this forum, I can't ask in the thread for the particular ROM. But I see a lot running this ROM with a tytung_r14 kernel, so I figured that I probably had to install this as well and I'm going to try it, but one question though...
Was I supposed to install the kernel BEFORE installing the ROM? Or can I just go and install the kernel now and all will be dandy?
Thanks.
Click to expand...
Click to collapse
I'm currently running the existing ROM on my SD card, and I'm not experiencing any battery drain what so ever...
I've also installed the ROM in NAND previously and didn't experience any heavy battery drain as well.
But to answer your question, no you weren't suppose to install the kernel before installing the ROM; The ROM (in SD or NAND format) already comes with a compiled kernel (It's a file called zImage).
You can install the kernel and you should just be dandy. Just remember that your battery life is heavily influenced by your cell reception and by the synching that occurs in the background.
To give you a reference, my phone is at 89% has been on standby for 13.5 hours with WIFI ON and data ON, but with data synching turned OFF for facebook and gmail. I'm also currently running it through the SD card with kernel r13. You should get similar results with the newer or existing kernel.
g.s said:
To give you a reference, my phone is at 89% has been on standby for 13.5 hours with WIFI ON and data ON, but with data synching turned OFF for facebook and gmail. I'm also currently running it through the SD card with kernel r13. You should get similar results with the newer or existing kernel.
Click to expand...
Click to collapse
Is this with the NexusHD2 ROM?
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
With the screen on and lowest standard brightness setting it is at 115-125 mA
DaneX said:
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
Click to expand...
Click to collapse
That means that you have a lurking app that keeps your phome from going into standby,so called partial wake.
Go into you app Spare Parts, click on battery history, choose other usage, since last boot or unplugged.
The screen on and running percentages tell you about the wake lock.
If it is nearly the same, that means you have almost no partial wakes.
If running is much higher, than screen on, that means you have some app that keeps phone awake.
Now choose partial wake usage in Spare Parts and it'll show you the apps.
And now you either uninstall them or change settings.
I'm on AmeriCan Android rom, getting 1-4mAh consumption in standby.
DaneX said:
Is this with the NexusHD2 ROM?
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
With the screen on and lowest standard brightness setting it is at 115-125 mA
Click to expand...
Click to collapse
Yep, this is with the NexusHD2 ROM. My phone during standby, only draws about 2-4mA.
55-60mA during sleep/standby is not normal. Are you in an area with bad cell reception?
Gang,
This a little different situation than what I've found here so far. I have a flashed Nook Color running a stable CM7 from the official site.
The other day the battery was low - maybe 13 percent - and it died. I plugged it in, it charged but when I started it up it gets to the CM7 load screen and goes no further. I can get into recovery mode but none of what I've tried works.
As a side note, I have a sideload CM7 SD card from back when I was trying things out and that boots up no problems.
This is the first time I've had issues with the Nook since flashing back in December.
Suggestions?
Brian
Brian0079 said:
Gang,
This a little different situation than what I've found here so far. I have a flashed Nook Color running a stable CM7 from the official site.
The other day the battery was low - maybe 13 percent - and it died. I plugged it in, it charged but when I started it up it gets to the CM7 load screen and goes no further. I can get into recovery mode but none of what I've tried works.
As a side note, I have a sideload CM7 SD card from back when I was trying things out and that boots up no problems.
This is the first time I've had issues with the Nook since flashing back in December.
Suggestions?
Brian
Click to expand...
Click to collapse
Did you try reflashing a new CM7 to internal? If that did not work, I suggest you go to my tips thread in my signature and make a new bootable CWM card I have there and reflash both a new CWM and CM7 to internal. Look at my item A8.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A