Database Users

Unrevoked 3.2 and #009 update.zip - What do I have?

Ive been reading a lot of threads here that mention rc1 and rc2 and cm6 etc. I rooted my Aria quite some time ago and wanted to know more about the specs I guess? Not sure really what I'm asking sorry.
What I used to root my phone was:
Unrevoked 3.2 and #009 update.zip
and I believe that included ClockworkMod Recovery v2.5.0.1
1). What did I ultimately put into my phone so that when reading threads on the forum I can put two and two together. Would like to make more mods to the phone but want more education on what I did in the first place.
2.)What is cycling your battery? and why do people do it?
3). Also what is the difference in using the nandroid backup vs the titanium?

kickmongwi said:
Ive been reading a lot of threads here that mention rc1 and rc2 and cm6 etc. I rooted my Aria quite some time ago and wanted to know more about the specs I guess? Not sure really what I'm asking sorry.
What I used to root my phone was:
Unrevoked 3.2 and #009 update.zip
and I believe that included ClockworkMod Recovery v2.5.0.1
1). What did I ultimately put into my phone so that when reading threads on the forum I can put two and two together. Would like to make more mods to the phone but want more education on what I did in the first place.
2.)What is cycling your battery? and why do people do it?
3). Also what is the difference in using the nandroid backup vs the titanium?
Click to expand...
Click to collapse
Answer to #3: http://forum.xda-developers.com/showthread.php?t=853020
By rooting using Unrevoked you did indeed install a new recovery app named ClockworkMod. When you boot into recovery mode, ClockworkMod allows you to flash new ROMs and apps to your phone that are stored as zip files on your SD card (you need to download and copy them to your SD card).
Cycling your battery involves using your phone until the battery is fully discharged and then fulling charging it and then letting it discharge again. In some cases you may see mention of going into Settings and clearing the battery statistics before you cycle the battery,

clear your battery stats in clockwork when the battery is fully charged to 100% and then some, then let it drain fully, charge again to 100% and then some.
you do not need to do this all the time. i've only done it once when I went from stock rom to CM6 for good measure.

[Q] Can't boot... have been meticulous... Help please?

This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic

syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App

Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??

Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App

OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App

syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!

syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.

last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.

You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???

Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.

lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.

Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.

lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!

And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?

syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App

OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!

How to install a Kernel.

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?

[Q] Possible destroyed my Note.

Hi guys,
Pretty new to the android scene (came from iOS). After using my Note at stock rom for about 2 months I decided to go ICS. Well.. here is where the pain started. It seems I have really ruined my phone, however I do not understand why.
What did I do?
I rooted my phone with CWM and used ODIN 1.8 to flash a default rom (as the guide told me to) so I could flash ICS afterwards. At the moment I flashed the first rom something strange happend. The phone was clicking itself (I will add youtube links as soon as I can) just at the middle of the screen. For example, if I were to send an SMS (vertically placed) it will press T or G constantly, depending on the rom. <-- Weird right? It actually switches to G or T depending on the rom, which should indicate software problems and not hardware.
As far as I know it has something to do with the way android mounts the SD card. Because as soon as I plug in the USB, the problem is gone. As soon as I unplug its back again. The ''clicking'' seems to be localized on the same place no matter if I go portrait or landscape, must be hardware right?
I've flashed over 50 times. Using different kernals, rockroms, ICS etc. etc. They all show the same problem. Even after ''factory resets'' in CWM, reinstall stock rom etc. I've even deleted everything on the internal SD card (as far as I could see files, not sure about hidden files) but that didn't help either.
Didn't make a backup either (dumb ****ing me) but I figured it wouldn't matter because I had a stock rom from my country zipped anyway.
The fact that it only shows up unplugged, must be an indication it has something to do with the fact that it only occurs during the mount of android to the phone.. but I can't figure out how to solve it.
HELP

Clicking itself? As in, it was registering touches at the center of the screen, without you actually touching it?

Yes, exactly that. It simply registers touches without me touching it.
There is no damage either, screen is clean as can be.

I've seen a few users here on the forum having issues with their touchscreen, and almost all the time the charger/cable is identified as the culprit. Search the general and Q&A forums with "touchscreen", you'll find a few of these posts.
It seems the screen is affected by voltage fluctuations, or incorrect voltages due to use of third-party cables/ chargers. If your Note is connected to the computer and the earthing for your machine is not proper, it can cause issues too. Some people suggest using a different power outlet, or at a friend's place, just to be sure. Also, the screen seems to get damaged that way very quickly, and no software changes seem to solve anything.
I personally haven't experienced a problem like that, but I'd recommend that you flash a stock rom for your country using Odin on the PC, and get the phone replaced.

This may sound dumb... but try taking your s-pen out of the back.
Some users report over sensitive screens, and it wouldn't surprise me if it would go THROUGH the back of the phone.
Give it a shot, let us know.

Just try full flash via odin with .pit file and repartition checked. Maybe it will help you.

Hi Guys,
Thanks for your input!
After the suggestion about voltage it got me thinking. So I charged the battery to 100% using a different power outlet. Problem seemed to be gone for a while, but as soon as the battery hit 80% or so it started again. Seems the voltage regulation is off scale or something like that. Either way, the damage seems to be permanent.
I flashed back to stock rom, gonna mail it to the samsung repair center tomorrow.

arf_cz said:
Just try full flash via odin with .pit file and repartition checked. Maybe it will help you.
Click to expand...
Click to collapse
Any idea where I can find this PIT file? Alot of people are talking about it but I am not able to find it.
EDIT: nvm found it

Its not only the .pit file, you need complete full flash (3 files - code, modem and csc).
For me, when i mess up my gnote trying a lot of different roms/kernels/ics stuff, helped this pack (open eu):
link in attached file (cant post links)
it includes odin and some other unimportant stuff. You need only odin, .pit file, modem file, code file and csc file.
In odin tick re-partition, auto reboot, f.reset time and phone bootloader update.
Put pda, modem, csc and pit files, than start and good luck!

Just chill
Hey there,
First things first, it is very hard to get your android messed up so, just and follow the below steps one-by-one and let me know. Please understand by following this process all your data, apps and settings will be reset.
1. Take a back up of all your data using Titanium or MyBackup.
2. Move the back up file to a location on your PC.
3. Flash a ROM that you can root and get CWM to work.
4. Once flashed and rooted, unplug the device and boot in recovery mode.
5. Once in recovery mode
a. Format Data/Factory Reset
b. Format cache
Under the advanced option in recovery mode select
a. Wipe Dalvik Cache
b. Wipe Battery Stats
Under the mounts option in recovery mode select
a. Format SD/MMC
b. Format System
c. Format Ext SD
Once done, select reboot. Now, the phone will be stuck on the flash screen, hold the power button down for as long as the phone does not turn off.
Now launch Odin, select the ROM of your choice.
Press the Power + Middle (Menu) + Volume down button until you get a warning on updating a new firmware, press the volume up button.
Plug the device and update.
Do check and let me know if this helped. The problem here is of the Battery Stats being clogged by moving from Gingerbread to ICS especially LP1 leak is disastrous and cannot be used as a daily ROM.
Please keep in mind the above steps and follow accordingly whenever you are ready to move a much advanced version of the firmware such as ICS and you will never face a problem.

sunil.inxs said:
Hey there,
First things first, it is very hard to get your android messed up so, just and follow the below steps one-by-one and let me know. Please understand by following this process all your data, apps and settings will be reset.
1. Take a back up of all your data using Titanium or MyBackup.
2. Move the back up file to a location on your PC.
3. Flash a ROM that you can root and get CWM to work.
4. Once flashed and rooted, unplug the device and boot in recovery mode.
5. Once in recovery mode
​a. Format Data/Factory Reset
​b. Format cache
Under the advanced option in recovery mode select
​a. Wipe Dalvik Cache
​b. Wipe Battery Stats
Under the mounts option in recovery mode select
​a. Format SD/MMC
​b. Format System
​c. Format Ext SD
Once done, select reboot. Now, the phone will be stuck on the flash screen, hold the power button down for as long as the phone does not turn off.
Now launch Odin, select the ROM of your choice.
Press the Power + Middle (Menu) + Volume down button until you get a warning on updating a new firmware, press the volume up button.
Plug the device and update.
Do check and let me know if this helped. The problem here is of the Battery Stats being clogged by moving from Gingerbread to ICS especially LP1 leak is disastrous and cannot be used as a daily ROM.
Please keep in mind the above steps and follow accordingly whenever you are ready to move a much advanced version of the firmware such as ICS and you will never face a problem.
Click to expand...
Click to collapse
I'm on Imilka's AOSP ICS ROM (GB -> Chinfire repack -> AOSP). If I just delete battery stats via recovery, that should be it, right?

sunil.inxs said:
Hey there,
First things first, it is very hard to get your android messed up so, just and follow the below steps one-by-one and let me know. Please understand by following this process all your data, apps and settings will be reset.
1. Take a back up of all your data using Titanium or MyBackup.
2. Move the back up file to a location on your PC.
3. Flash a ROM that you can root and get CWM to work.
4. Once flashed and rooted, unplug the device and boot in recovery mode.
5. Once in recovery mode
a. Format Data/Factory Reset
b. Format cache
Under the advanced option in recovery mode select
a. Wipe Dalvik Cache
b. Wipe Battery Stats
Under the mounts option in recovery mode select
a. Format SD/MMC
b. Format System
c. Format Ext SD
Once done, select reboot. Now, the phone will be stuck on the flash screen, hold the power button down for as long as the phone does not turn off.
Now launch Odin, select the ROM of your choice.
Press the Power + Middle (Menu) + Volume down button until you get a warning on updating a new firmware, press the volume up button.
Plug the device and update.
Do check and let me know if this helped. The problem here is of the Battery Stats being clogged by moving from Gingerbread to ICS especially LP1 leak is disastrous and cannot be used as a daily ROM.
Please keep in mind the above steps and follow accordingly whenever you are ready to move a much advanced version of the firmware such as ICS and you will never face a problem.
Click to expand...
Click to collapse
Argh, thanks alot for your information.
Unfortunatly I already sent the phone to Samsung for repairs. But your story sounds logical, as well as others did. However I cannot test it at the moment. If Samsung wont fix the problem i'll try your method and get back to this topic.
For those who're insterested, here's a short video of the problem ->
youtube .com/watch?v=_8UV_9jz-Wo <- space between youtube & .com
Thanks alot everyone, will get back to you! cheers
Martijn

bloodyhippo said:
I'm on Imilka's AOSP ICS ROM (GB -> Chinfire repack -> AOSP). If I just delete battery stats via recovery, that should be it, right?
Click to expand...
Click to collapse
This should work, if not take the long route..
Sent from my GT-N7000 using xda premium

Well bloodyhippo,
It turns out you were right. According to Samsung my Note's screen was defective, most likely due to to a lousy/non-grounded power connector.
Which is pretty upsetting as this basicly means I can't charge or flash my phone at 90% of all places im at.
They've replaced the screen, phone works like a charm.
Let this be a warning to all.. The G Note has a REAL sensative screen..!

extreemwisse said:
Well bloodyhippo,
It turns out you were right. According to Samsung my Note's screen was defective, most likely due to to a lousy/non-grounded power connector.
Which is pretty upsetting as this basicly means I can't charge or flash my phone at 90% of all places im at.
They've replaced the screen, phone works like a charm.
Let this be a warning to all.. The G Note has a REAL sensative screen..!
Click to expand...
Click to collapse
Buy a UPS for clean energy and a surge protector.

KF won't power up

Oh crap, here goes:
I loaded up the Energy Rom from NRGZ28 in my kindle and booted into recovery. I hit the "Wipe Data" option and noticed after a couple of minutes that the application froze (it wans't doing anything) and would not respond to anything I did. So figuiring it was only data and not a system wipe I held the power button down for the 10 second reboot expecting it reboot into the current rom since all it was missing was data and I would just sign in and set up like I always do. How wrong was I, it is now off and will not turn on no matter what I do. Crap, after flashing roms for the last 3 years on phones and my Kindle since roms were available for it I think I made my first brick
I did not get to flash the new ROM so I know it wasn't that and Iv'e been using this recovery since Hash put it out for us so not sure what went wrong.
Anybody able to bring theirs back to life, I'll be trying the fire_fix tonight to see if that might help via USB.

did firekit sort it for you?
sent from my new non bricked kindle

Jdom58 said:
Oh crap, here goes:
I loaded up the Energy Rom from NRGZ28 in my kindle and booted into recovery. I hit the "Wipe Data" option and noticed after a couple of minutes that the application froze (it wans't doing anything) and would not respond to anything I did. So figuiring it was only data and not a system wipe I held the power button down for the 10 second reboot expecting it reboot into the current rom since all it was missing was data and I would just sign in and set up like I always do. How wrong was I, it is now off and will not turn on no matter what I do. Crap, after flashing roms for the last 3 years on phones and my Kindle since roms were available for it I think I made my first brick
I did not get to flash the new ROM so I know it wasn't that and Iv'e been using this recovery since Hash put it out for us so not sure what went wrong.
Anybody able to bring theirs back to life, I'll be trying the fire_fix tonight to see if that might help via USB.
Click to expand...
Click to collapse
What recovery did you use-TWRP or CWMR 5.5.0.4? See herehttp://forum.xda-developers.com/showthread.php?t=1651413