Related
I did NOT paritition my gTablet after I installed CWM 0.8. My CM7-based ROMs have installed and worked just fine, including the new Market app. Do I need to partition?
The only real error I have had is the inability to transfer files (using Astro) between my internal 16 GB memory (/mnt/emmc/) and my installed 2GB sd card (/mnt/sdcard). Will partitioning help solve this?
TIA!
I think partitioning is an important step and really should be a mandatory step at least for the first flash. It sets up your memory structure in the same architecture that the roms and recovery were built in. Its quick, painless and can solve many issues before they even start. Its best done right when you first start flashing as it destroys all data on the tablet, so anything you want to save needs to be backed up on a PC first.
Mantara said:
I think partitioning is an important step and really should be a mandatory step at least for the first flash. It sets up your memory structure in the same architecture that the roms and recovery were built in. Its quick, painless and can solve many issues before they even start. Its best done right when you first start flashing as it destroys all data on the tablet, so anything you want to save needs to be backed up on a PC first.
Click to expand...
Click to collapse
I agree with Mantara. I think it reduces the chances of corrupting the tablet's data. Also, repartitioning is a bigger pain if you decide to do it later when you have a like a ton of files in your internal memory and have to back it up because repartitioning reformats the internal sd card.
McGoo,
I don't disagree with Mantara that prevention might be good. You'll have to make that call.
I look at re-partitioning from the recovery perpective -- it simply hinges on the fact
that I have noticed what I believe is a correlation between Boot Loops and the need
to re-partition. Re-partitioning (and the associate wipes/etc.) seems to fix the boot
loops most of the time.
If your tablet is working fine, I go with the old computer quote "If it ain't broke, don't fix it!!!"
*********
Your other question -- I don't have a firm answer. The Android file system and the
USB stuff on the tablet -- to me operate in a strange. Kind of an OS with an arm or
two tied behind it's back. I know that's not an answer, so I'll quit.
Rev
butchconner said:
McGoo,
I don't disagree with Mantara that prevention might be good. You'll have to make that call.
I look at re-partitioning from the recovery perpective -- it simply hinges on the fact
that I have noticed what I believe is a correlation between Boot Loops and the need
to re-partition. Re-partitioning (and the associate wipes/etc.) seems to fix the boot
loops most of the time.
If your tablet is working fine, I go with the old computer quote "If it ain't broke, don't fix it!!!"
*********
Your other question -- I don't have a firm answer. The Android file system and the
USB stuff on the tablet -- to me operate in a strange. Kind of an OS with an arm or
two tied behind it's back. I know that's not an answer, so I'll quit.
Rev
Click to expand...
Click to collapse
that's the approach i'll take for now. when time comes for officially official CM7 tablet releases, i'll reformat then. until then i'll just enjoy things as they are. thanks for the feedback, all.
Hello,
I have strange defect in my phone: after every power cycle phone wakes up in state it was at about February 13 2012. I can not permanently change anything. I also can not change firmware. I even have made full three stage recovery from broken nand write, as described elsewhere here, without changing anything.
What is strange: no warnings or failure notices. Phone is working normally. Flashing is also seemingly working okay. But after restart nothing is changed. Only when I work with big files, random apps start to crash. I discovered this when downloading maps.
My question is: can sgs2 with Android 2.3.3 seemingly work O.K. with totally nonfunctional nonvolatile memory writing?
Because I don't know your history....
Did you full wiped that is
Format cache data system sdcard
Dalvik.
atifsh said:
Because I don't know your history....
Did you full wiped that is
Format cache data system sdcard
Dalvik.
Click to expand...
Click to collapse
I did. Nothing gets erased. If you know, how Android system works: in your opinion is it possible that system under light usage works O.K. in spite that nonvolatile storage is effectively read only?
Strange issue, but yes in theory, if your storage is busted in a way that it actually works as a read only, but when an application need to write something it fails and crashes.
atifsh said:
Strange issue, but yes in theory, if your storage is busted in a way that it actually works as a read only, but when an application need to write something it fails and crashes.
Click to expand...
Click to collapse
When an application needs to write something it does not fail, at least when it does not write large amounts of data. I can do everyday tasks: add or remove contacts, add few apps (which then actually work), move icons on screens and so on. Is all this possible with NVmemory working as ROM? Because after power cycle all that is gone and all reverts to February 13 2012 state.
Just a thought but have you tried erasing all the contents of your phone?
Using ODIN you can install an odin Cyanogenmod rom, use the pitfile and select repartition. This I believe wipes everything except the 14gb user data portion. Then, just format that under settings.
Perhaps a full wipe would fix it.
MikeMurphy said:
Just a thought but have you tried erasing all the contents of your phone?
Using ODIN you can install an odin Cyanogenmod rom, use the pitfile and select repartition. This I believe wipes everything except the 14gb user data portion. Then, just format that under settings.
Perhaps a full wipe would fix it.
Click to expand...
Click to collapse
That's what I think too, but didn't told him because using pit got a high chance of bricking.
And the way he is using suggests he is out of warranty.
MikeMurphy said:
Just a thought but have you tried erasing all the contents of your phone?
Click to expand...
Click to collapse
The phone does not effectively wipe at all. After any wiping or installing new roms/bootloaders/pits/anything the phone wakes up in state it was 2012/02/13, except date and time, which is current.
If you have used pit and tick repartition, and still nothing erased, boy your internal storage is shouting get rid of me fast or I'll go dead on you soon.
Or I could be wrong and your phone will out lived you
I am pretty much convinced that my phone is irreparable. I do not look for solution to make it work normally again (although I would very much welcome one if I'm wrong).
I seek an answer from somebody who intimately knows, how Android filesystem works: Is it possible, that phone works seemingly O.K. under very light usage in spite that it cannot in fact write to flash memory? And work like this for 2 months without giving warning/error messages?
I compare my situation to a PC with ram-disk setup and an unwritable hard disk. This would not work long. Can Android?
Hey Zie, you may not get this notification of reply, but I wanted to ask, did you ever reach a solution with you SGS II? I'm on the Skyrocket and the same thing happened to me a few days ago. So far nothing has worked and I just upgraded. This was my second Skyrocket coming from an Infuse 4g.
Can't return the phone because all can tell its a rooted device with a custom rom on it. AOKP Milestone 6. Let me know what u did to get around this if u can....
Sent from my SGH-I727 using xda premium
Hi,
My EVO 4G LTE is S-OFF. I've been running FreshROM 5.3.1 since it was released without issue. Last Thursday I started getting a lot of backround app crashes. Not a big deal, I wiped, reloaded the ROM, then restored everything via Titanium Backup pro. All was well for a couple of days.
Yesterday, my battery died within about 3 hours. Normally, I go over 16 hours. After some investigation and I found a process 'flush-179:0' eating CPU (and battery). I've wiped, flashed again, even flashed different ROMs. It's still there; every time.
I found one post on XDA where someone said it was caused by a performance tweak app (http://forum.xda-developers.com/showthread.php?t=2016993). Their fix was to flash stock, radios, etc. then root again. I haven't used any apps to tweak anything. So, if it's a similar cause...data/config corruption?
Has anyone else seen this? Does anyone know of a fix?
Thanks!
I'm not familiar with this specific issue but you mentioned that you restored everything using titanium backup. If you are experiencing problems I would strongly recommend NOT restoring all data as you may be restoring that very same issue. If you don't want to have to start all over then at least only restore just apps and data. Never system data.
Sent from my EVO using Tapatalk 2
eddy0090 said:
I'm not familiar with this specific issue but you mentioned that you restored everything using titanium backup. If you are experiencing problems I would strongly recommend NOT restoring all data as you may be restoring that very same issue. If you don't want to have to start all over then at least only restore just apps and data. Never system data.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Of course, the problem is that it's there when I wipe and flash a new ROM (Fresh, Rejuvenated, etc.). Even before I load my data via TB.
zisix said:
Hi,
My EVO 4G LTE is S-OFF. I've been running FreshROM 5.3.1 since it was released without issue. Last Thursday I started getting a lot of backround app crashes. Not a big deal, I wiped, reloaded the ROM, then restored everything via Titanium Backup pro. All was well for a couple of days.
Yesterday, my battery died within about 3 hours. Normally, I go over 16 hours. After some investigation and I found a process 'flush-179:0' eating CPU (and battery). I've wiped, flashed again, even flashed different ROMs. It's still there; every time.
I found one post on XDA where someone said it was caused by a performance tweak app (http://forum.xda-developers.com/showthread.php?t=2016993). Their fix was to flash stock, radios, etc. then root again. I haven't used any apps to tweak anything. So, if it's a similar cause...data/config corruption?
Has anyone else seen this? Does anyone know of a fix?
Thanks!
Click to expand...
Click to collapse
u should try mean rom 6.5 ICS.. if your still on the old base.. or flash new firmwear and radio in bootloader then flash a new jelly bean rom if u want to try the new base out
evo401 said:
u should try mean rom 6.5 ICS.. if your still on the old base.. or flash new firmwear and radio in bootloader then flash a new jelly bean rom if u want to try the new base out
Click to expand...
Click to collapse
I think I will; this seems to fit with the latest info I just figured out.
I flashed Fresh again, and suddenly started getting the warning about the SD card being damaged and to format it (as we know, that's not the external SD card). No matter how many times I format it, the error comes back. From some other searching, the 'flush-179:0' process seems to have something to do with storage, maybe because it can't read that partition it's causing issues.
I updated the firmware and radio, still no luck.
So I tried loading another ROM (I went with Mean Bean). That fixed the issue with the SD Card partition being unreadable/unformatable. Maybe that was caused by multiple flashes
But, the flush-179:0 process is still eating CPU and battery.
zisix said:
I updated the firmware and radio, still no luck.
So I tried loading another ROM (I went with Mean Bean). That fixed the issue with the SD Card partition being unreadable/unformatable. Maybe that was caused by multiple flashes
But, the flush-179:0 process is still eating CPU and battery.
Click to expand...
Click to collapse
?? i never heard of that flush-197:0?? could it be an app u downloaded maybe.. if u flash meanbean over abd dont install any app does is that flush-179 still there or it it there after u install yoir apps?
evo401 said:
?? i never heard of that flush-197:0?? could it be an app u downloaded maybe.. if u flash meanbean over abd dont install any app does is that flush-179 still there or it it there after u install yoir apps?
Click to expand...
Click to collapse
As far as I can tell, it's part of Fresh 5.3.1 and other ROMs I had on my SDCard that are based on the old OTA. The latest Mean Bean doesn't have the same issue after wipe & flash.
I emailed flipz (the Fresh dev), though who knows if/when he'll get back to me. For now, I'm thinking about running MeanBean for a while.
You really can't go wrong with mikeyxda and his mean series of ROM's. That man consistently puts out quality work. No doubt about it.
zisix said:
I flashed Fresh again, and suddenly started getting the warning about the SD card being damaged and to format it (as we know, that's not the external SD card). No matter how many times I format it, the error comes back. From some other searching, the 'flush-179:0' process seems to have something to do with storage, maybe because it can't read that partition it's causing issues.
Click to expand...
Click to collapse
You nailed it. I was having issues with the flush-179 system process taking up 100% of my CM10's (JB) CPU time. It got so bad that I couldn't even reboot or shutdown without pulling the battery, which of course caused other problems. Initially I thought the "System" process was just out in the weeds, but by using OS Monitor and unchecking "Hide System Process", I was able to find the flush-179 culprit.
My first clue that it might be SD card-related was obtained after opening a terminal window and typing 'mount'. The line for /mnt/sdcard showed (paraphrased):
# mount
...
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,...
...
Realizing that a "flush" process probably had something to do with filesystem caching and seeing the "179" in the mount output, I focused on my SD card. After pulling the card, backing it up, formatting, and restoring it in Windows, I am happy to report that my little Android has been fast, snappy, and problem-free for several days now.
- Dave
Hi,
sorry to disturb you but I do have some little "problems" with my HTC ONE AT&T.
I bought this phone, simunlocked already, and with revone I put it SOFF and than I "converted" it to international version of it (thinking that keeping the AT&T versionI coudn't install internatinal rom...I understood I was wrong but anyway I'm from Europe so I like to have international CID).
Few strange things happened (I'm not sure if it's normal or not).
The first one is that it seems that my phone is loosing memory, it's supposed to have 32 Gb but, as you can see from the attachment, it has just 25.5 Gb, is that normal (I do use a really slim rom, just 150 Mb, but anyway it's the same with any rom I install)...is it normal? Is it possible to format ALL and restore all the memory to an initial state (where there shall be at least 30-31 Gb avaialble I think)??
The second is that sometimes, after installing a rom, exiting the aroma installer, the screen become black instead of getting me back to the recovery (actually it seems it brings me back to the recovery but the screen goes off and no way to turn it on...so force reboot and than everything works fine....but sometimes reinstalling the same rom over and over it works fine, it bring me back to recovery and I can normally reboot the system), is it normal?
Than during the boot it says that this is a test device and so on (a sentence written under the HTC logo), is there a way to remove it? I thought I could do it with revone (I thought it was the tempered flag) but I tried the following thing and isn't removing it even if it says succesfully: Re-run revone to remove TAMPERED from your HBOOT screen: ./revone -t (but maybe it's another thing).
So is there a way to remove that sentence?
Thanks,
Massimiliano
Storage size is normal to show 25.59... As android system uses the rest that you don't see
Sent from my HTC One using XDA Premium 4 mobile app
TopoX84 said:
Storage size is normal to show 25.59... As android system uses the rest that you don't see
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is there a way to check if some part of the memory is lost/full from previous rom and it wasn't clean well??
I'm using this rom http://forum.xda-developers.com/showthread.php?p=50698141 it's realy minimal, without NOTHING, even the play store was missing...how can it use 7 Gb of memory?
m.zambonelli said:
Is there a way to check if some part of the memory is lost/full from previous rom and it wasn't clean well??
I'm using this rom http://forum.xda-developers.com/showthread.php?p=50698141 it's realy minimal, without NOTHING, even the play store was missing...how can it use 7 Gb of memory?
Click to expand...
Click to collapse
Just go into settings and select storage. It tells you what is being used and by what.. Memory is used like a hard drive and it is formatted so the system can use it properly. That being said on 32GB you loose about 2GB to the formatting. Then the system and everything else on he phone uses it. There is also a swap file of several GB that is used when the 2GB of RAM is too full. There are also a couple of cache that use that memory as well. What you are seeing is typical storage usage of most phones running on Android. You loose around 7 to 10 GB to the system.
m.zambonelli said:
Is there a way to check if some part of the memory is lost/full from previous rom and it wasn't clean well??
I'm using this rom http://forum.xda-developers.com/showthread.php?p=50698141 it's realy minimal, without NOTHING, even the play store was missing...how can it use 7 Gb of memory?
Click to expand...
Click to collapse
Well is like installing Linux on a computer.. The easy setup sets different partitions that the system is going to use for multiple purposes hence losing some GB in the process to be able to perform as required.
Sent from my HTC One using XDA Premium 4 mobile app
Solarenemy68 said:
Just go into settings and select storage. It tells you what is being used and by what.. Memory is used like a hard drive and it is formatted so the system can use it properly. That being said on 32GB you loose about 2GB to the formatting. Then the system and everything else on he phone uses it. There is also a swap file of several GB that is used when the 2GB of RAM is too full. There are also a couple of cache that use that memory as well. What you are seeing is typical storage usage of most phones running on Android. You loose around 7 to 10 GB to the system.
Click to expand...
Click to collapse
Ok I do understand that but as you can see from the screenshot attached in Setting-Storage it says Total Space 25.59Gb, available 24 and something.
I would like to see/understand/access the remaining 6/7 Gb that are not showed there!
I've the feelings that the memory is decreasing every time I'm installing a rom, I also formatted EVERYTHING. loosing the operating system (than I had to push a rom in the memory) but still is like that!
Any suggestion or idea on how to see what is inside those 7 Gb "missing" from the total space?
Any way to format them?
It's not missing, open a terminal window and execute df command - that will list partitions. Data is 25.6GB, system 1.8GB, cache 600MB, etc. All 32GB are there, but are partitioned for different aspects of the OS, you can't change that.
cschmitt said:
It's not missing, open a terminal window and execute df command - that will list partitions. Data is 25.6GB, system 1.8GB, cache 600MB, etc. All 32GB are there, but are partitioned for different aspects of the OS, you can't change that.
Click to expand...
Click to collapse
Thank you so much for your answer, I'm slowly understanding how this is working
I am than wondering if it's possible that multiple install of things (updating hboot, recovery, different rom and so on) can leave some "dirty" file or folder meaning that some not necessary files are still there taking space for nothing.
This is my df results, can you check if, for your opinion, everything is fine or if there is some folder too big as it shall be?
Another question is if it's possible to just delete ALL the 32Gb, removing all the partition and stuff and then in some way restore it to a "default" (I don't know what I'm actually saying, I hope you understood what I mean...mainly like in any windows pc you can just remove all the partition, format all and reinstall the OS from zero).
Thanks a lot,
Massimiliano
p.s. I'm including the screenshot of my df result
m.zambonelli said:
Thank you so much for your answer, I'm slowly understanding how this is working
I am than wondering if it's possible that multiple install of things (updating hboot, recovery, different rom and so on) can leave some "dirty" file or folder meaning that some not necessary files are still there taking space for nothing.
This is my df results, can you check if, for your opinion, everything is fine or if there is some folder too big as it shall be?
Another question is if it's possible to just delete ALL the 32Gb, removing all the partition and stuff
Click to expand...
Click to collapse
It looks normal, you can't delete all of the partitions it would brick the phone. Flashing roms doesn't leave old files, because the install wipes the system first.
m.zambonelli said:
Thank you so much for your answer, I'm slowly understanding how this is working
I am than wondering if it's possible that multiple install of things (updating hboot, recovery, different rom and so on) can leave some "dirty" file or folder meaning that some not necessary files are still there taking space for nothing.
This is my df results, can you check if, for your opinion, everything is fine or if there is some folder too big as it shall be?
Another question is if it's possible to just delete ALL the 32Gb, removing all the partition and stuff and then in some way restore it to a "default" (I don't know what I'm actually saying, I hope you understood what I mean...mainly like in any windows pc you can just remove all the partition, format all and reinstall the OS from zero).
Thanks a lot,
Massimiliano
p.s. I'm including the screenshot of my df result
Click to expand...
Click to collapse
I don't want to sound like an ass but what you have is normal so you are going to have to live with it. There is no way to get more memory cleared up unless you have absolutely nothing but the ROM running and nothing else downloaded and installed. Everyone who has the 32GB version of this phone has the same amount of memory as you. Some have less as they have installed other apps. added music, movies, and pictures.
The ONLY way you could get more memory is to get the 64GB version of this phone. I knew it did not have a card slot so I took that into account and bought the 64GB version so I would have plenty of space for anything I wanted.
cschmitt said:
It looks normal, you can't delete all of the partitions it would brick the phone. Flashing roms doesn't leave old files, because the install wipes the system first.
Click to expand...
Click to collapse
Ok, Thanks
Solarenemy68 said:
I don't want to sound like an ass but what you have is normal so you are going to have to live with it. There is no way to get more memory cleared up unless you have absolutely nothing but the ROM running and nothing else downloaded and installed. Everyone who has the 32GB version of this phone has the same amount of memory as you. Some have less as they have installed other apps. added music, movies, and pictures.
The ONLY way you could get more memory is to get the 64GB version of this phone. I knew it did not have a card slot so I took that into account and bought the 64GB version so I would have plenty of space for anything I wanted.
Click to expand...
Click to collapse
If I knew that 32 Gb meant 25 I would consider to buy the 64 Gb too ... but other than te space I just wanted to understand IF it was normal that, after just flashed a really basic clean rom (just 156 mb of rom) it was normal to have just 25 Gb free (no other additional apps, no photo and so on) ... it's normal, ok, I'll be happy with that and next phone I'll consider a 64Gb version of it.
Thanks everyone for the reply
Good evening.
I have a new UMI X2 for 3 weeks now. I do not receive texte messages. I have done 2 factory resets and then I get messages back to work, but after a few days and without any reason I stop receiving them again. I did some research and found that this is a common problem with umi x2 and some people say that I should apply a ROM fix or software update. But I dont know anything about this. I need your help in order to fix this please.
JonhyRico said:
Good evening.
I have a new UMI X2 for 3 weeks now. I do not receive texte messages. I have done 2 factory resets and then I get messages back to work, but after a few days and without any reason I stop receiving them again. I did some research and found that this is a common problem with umi x2 and some people say that I should apply a ROM fix or software update. But I dont know anything about this. I need your help in order to fix this please.
Click to expand...
Click to collapse
Have you tried just using a different text messaging app to see if it's not just an issue with the built in stock text messaging app? That would be quick and easy to test. If that doesn't work, then yes. an update or rom would be the next step.
Root: Supposedly this phone is already pre-rooted. Depending on where you got it from, it is possible this was disabled. If it does need to be rooted, then it is specific to what firmware and chip you have (I guess there are regular and "Turbo" versions)
Recovery: http://forum.xda-developers.com/showthread.php?t=2342943
Roms: http://www.needrom.com/phone-roms/umi/umi-x2/ - My suggestion would be CM11 due to a much better UI, more privacy / security, and it is highly rated. Recommend reading through comments for more info on what does / does not work.
All of these are very general guidelines to get started with reading. You should get familiar with how to restore to stock as well, in worst case scenarios.
https://www.facebook.com/pages/Umi-X2-1080p-Android-Phone-User-Group/572387056135889
Thank you so much for your help.
es0tericcha0s said:
Have you tried just using a different text messaging app to see if it's not just an issue with the built in stock text messaging app? That would be quick and easy to test. If that doesn't work, then yes. an update or rom would be the next step.
Click to expand...
Click to collapse
Yes. Did not work.
es0tericcha0s said:
Root: Supposedly this phone is already pre-rooted. Depending on where you got it from, it is possible this was disabled. If it does need to be rooted, then it is specific to what firmware and chip you have (I guess there are regular and "Turbo" versions)
Click to expand...
Click to collapse
Sorry, but I do not understand this part. I am totally illiterate in this matters, but I am pretty good at following tutorials.
Mine is the 1.5Ghz 2Gb RAM and 32Gb ROM (many call it Turbo, even though there have been other Turbo versions before).
es0tericcha0s said:
Recovery: http://forum.xda-developers.com/showthread.php?t=2342943
Roms: http://www.needrom.com/phone-roms/umi/umi-x2/ - My suggestion would be CM11 due to a much better UI, more privacy / security, and it is highly rated. Recommend reading through comments for more info on what does / does not work.
All of these are very general guidelines to get started with reading. You should get familiar with how to restore to stock as well, in worst case scenarios.
https://www.facebook.com/pages/Umi-X2-1080p-Android-Phone-User-Group/572387056135889
Click to expand...
Click to collapse
All these are great tips. Thanks a lot!
JonhyRico said:
Thank you so much for your help.
Yes. Did not work.
Sorry, but I do not understand this part. I am totally illiterate in this matters, but I am pretty good at following tutorials.
Mine is the 1.5Ghz 2Gb RAM and 32Gb ROM (many call it Turbo, even though there have been other Turbo versions before).
All these are great tips. Thanks a lot!
Click to expand...
Click to collapse
So, yea, seems like it should already be rooted. You can check with a root checker app from the Play Store to verify. If it is, then you can install the MobileUncle app and use that to install the CWM recovery which will allow you to backup your current rom as well as completely wipe and install a new one. Make sure you backup whatever you want and save it to a safe place before you start as a precaution. You can never be too careful, but you can certainly not be careful enough.
es0tericcha0s said:
So, yea, seems like it should already be rooted. You can check with a root checker app from the Play Store to verify. If it is, then you can install the MobileUncle app and use that to install the CWM recovery which will allow you to backup your current rom as well as completely wipe and install a new one. Make sure you backup whatever you want and save it to a safe place before you start as a precaution. You can never be too careful, but you can certainly not be careful enough.
Click to expand...
Click to collapse
Why do you think it is rooted. Is that bad or good?
Will I need a micro SD card to do this?
Because I've seen more than 1 post / review from various users stating that it is rooted already. This is excellent if you plan on modifying your phone as part of the work is already finished. Whether or not you need an SD card depends on how much storage you have left on your phone. Probably need at least a GB or 2 for the nandroid backup and then however much room the roms take up. Since you have a 32 GB phone, it's more than likely there is plenty of room left for this stuff. I really suggest reading up on how to use the Flash Tool and the files you need to restore the phone to stock, just in case. I've worked (rooted/customized) on well over a 100 different kinds of android devices, but even so, I rarely ever work on something that I don't have the ability to at least return it to it's original state.
"1. Downlaod CWM Recovery extract it and copy recovery.img only to root of your SD Cards
{ i.e. sdcard/recovery.img or sdcard2/recovery.img }"
In the beginning of the tutorial it says that. I am completely lost with that step. Is this on the phone or on the pc? Is this through an app?
They're saying you should download the CWM file - if it is zipped, you must unzip and move that file (will be something.img) to your SD card or internal storage. When it says root of card, that just means it should NOT be in a folder.