Database Info

Can I install a rom from Rom Manager

I would love some help, can someone tell me how to install a rom using Rom Manager. I've install clockwork recovery downloaded CM7.2 for my ascend. Can I install this, using Rom Manager? I have premium, but I have ruined 2 zio m6000 , 1 samsung moment, and 1 ascend. Up really dont want to loS another phone. Could I get a hand, here? I havE nO clue whaT half the things talked about on here are. But, its starting to cosT to much $ learning.
Sent from my M860 using XDA Premium App

As we are speaking about ROMs, any wrong operation can turn your phone in a simple book holder. I am not expert (bought my first HTC 3d ago), but already have good experience to help you A BIT.
- enter ClockWork (reboot your phone, press volume-down as it starts, navigate and enter RECOVERY mode: clock-work is installed in the recovery zone; some ROMs may have a reboot-to-recovery feature)
- navigate and wipe system, user-data, and cache zones
- navigate in menus a either perform a restaure, or apply-patch-from-zip depending on your type of ROM (IMG, zip ... )
You can also try to install your ROM without wipe, BUT, if you see CW does NOT says it will erase or format the partition first, then you are going to have troubles (small troubles: it will boot, but not work properly). You can start by this operation, and when you have found how to flash, then you wipe ... this will avoid having an empty system, and have your phone unusable for a time.
If you have a broken system, you can always put the SD card into computer and push a working rom using SD (then CW) or fastboot.
After successfull flash, you may want to wipe user and cache zones. Again, it just helps having a clean system, and is not mandatory; keeping old user-data usually works, but CAN make bugs trigger.
At your own risks. Good luck.

- how to flash my Samsung Galaxy S Fascinate CDMA. using Rom Manager. with file name .ota .? huhuh. sorry, i'm noob in this kind of thing.!! i;m begging you guys.!! help me , i'm stock to Eclair 2.1 and i hate it,! thanks.!!

-help me guys.!!! thanks.

kakroch99 said:
-help me guys.!!! thanks.
Click to expand...
Click to collapse
Learn to help yourself. You are not asking a new question.
1. Use the search function.
2. Use Google.
3. Research!
4. Read, read, read!
5. Don't actually try any modifications until you're confident you know what you're doing and willing to accept the consequences if you screw up.
6. If you fail, do more research and reading so you can...
7. Try to fix it yourself before asking for help.
8. Ask intelligent questions if you do still need help.
Sent from a HTC G2

Android rescue.zip project..

So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.

I generally do a backup before doing any modding and just reflash from the start and do a restore.

projectsome said:
I generally do a backup before doing any modding and just reflash from the start and do a restore.
Click to expand...
Click to collapse
yup most of the time restoring just boot.img fixes a bootloop

Usually you can just reflash the rom .zip without wiping user data and your data will remain intact and your phone will continue functioning normally if the problem is due to corrupted system files or kernel.
Sent from my LG-P920 using Tapatalk 2

Thread will be locked until, there is further progress made.
@OP PM me when when there is an update.

Help an aging PC hacker upgrade his brain and his TF101

Hi young grasshoppers
I'm an aging PC hacker (down to disassembling viruses with Softice and the works, I'm THAT old!) with a splendid TF101 and I could use an upgrade to my brain and my TF101. I looked for a thorough FAQ to get a clue, but clue I didn't get.
Long story short, one year ago I rooted my TF101 in a rush with success, but didn't have enough time to do the homework and RTFM as I am used to (damn crisis!).
Presently the TF101 has Prime! 1.4 (Android 3.1), Kernel 2.6.36.3-00001-gf377a2b, CWM Recovery 3.1.0.1 Solarnz-R3-230511
My goals are two:
1. trying the new 4.x roms on my TF101;
2. get a clue;
My mental framework comes from PC: mobo holds flashable ROMs and BIOS, hd holds Operating System(s), Apps and Bootloader. As I don't know how the TF101 and Android's structureI'm a little bit lost and I don't want to brick it or upgrading without understanding how to restore it to its present state.
As far as I understood, the TF101 has: Internal SD (holding apps and kernel ? ), external SD aka MicroSD holding media and apps movable to SD, some flashable memory for ROM (?).
As I was cosidering trying Android Revolution HD 3.5.1, I noticed that it requires: CWM v3.2.0.1 and a Super Wipe Full which scared the hell out of me...what is it going to Wipe??? ...and rooting made by RazorClaw
What I would like to understand is:
1. How do I backup the present Kernel and Apps and eventually restore it ? Under CWM 3.1.0.1 I just did a (I believe it's called) Nandroid System Backup that was stored to the MicroSD (external SD) ... what did I just back up ? Kernel,apps,both?
1.1 CWM also offers the Factory Wipe/ Reset function: what does it do? Does it restore the OLD (original as bought) Rom and wipes the Kernelt (and deletes the apps) so that it basically reverts to my original unrooted TF101 as-bought?
1.2 Upgrading the CMW would need: copying the new CWM zip into the external SD card, launcing CWM and using the upgrade procedure?
2. As apparently I need to root throught RazorClaw, I think the present rooting might interfere w/ ARevolution installation. So what would the correct unrootin procedure would be, considered my situation? I'm aware that some apps are able to unroot, but not being sure I'd rather ask.
Finally, I would absolutely love to know if there's a post generally addressing my doubts, giving me an overview of a. what's get modded by rooting b. and where c. and what ROM, Kernel, Bootloaders are in a TF101 or (more generally) in the Android world.
Thanks a lot for your help and for giving me some clues! :laugh:

Ill try to answer your questions as best i can
1.0 Nandroid backs up your rom, apps and appdata not the kernel
1.1 Factory reset wipes apps, data and internal sd it does not change your rom or kernel
1.2 Yup just copy over the new cwm (rouge or twrp are my favorites) and navigate to the file in cwm and hit install
2. If you already on prime you are already rooted so thats not a problem
Rooting just allows you elevated privileges like read/write in the system and things like that. Its like su is essentially sudo
All rooting is is putting the su.sh and busybox.sh into the system using an exploit
You really should not restore a kernel from android 3.1 on anything but 3.1 or your going to have a bad time
Before you update make sure to back up your apps. Titanium Backup is a good choice
Most the roms that are currently active are Jelly bean betas which are a little unstable so i would go with a nice stable ICS rom like megatron or revolver
There is a lot of info in the android general form that you might want to read through but a most development seems to be device specific

elpapacito said:
Hi young grasshoppers
I'm an aging PC hacker (down to disassembling viruses with Softice and the works, I'm THAT old!) with a splendid TF101 and I could use an upgrade to my brain and my TF101. I looked for a thorough FAQ to get a clue, but clue I didn't get.
Long story short, one year ago I rooted my TF101 in a rush with success, but didn't have enough time to do the homework and RTFM as I am used to (damn crisis!).
Presently the TF101 has Prime! 1.4 (Android 3.1), Kernel 2.6.36.3-00001-gf377a2b, CWM Recovery 3.1.0.1 Solarnz-R3-230511
My goals are two:
1. trying the new 4.x roms on my TF101;
2. get a clue;
My mental framework comes from PC: mobo holds flashable ROMs and BIOS, hd holds Operating System(s), Apps and Bootloader. As I don't know how the TF101 and Android's structureI'm a little bit lost and I don't want to brick it or upgrading without understanding how to restore it to its present state.
As far as I understood, the TF101 has: Internal SD (holding apps and kernel ? ), external SD aka MicroSD holding media and apps movable to SD, some flashable memory for ROM (?).
As I was cosidering trying Android Revolution HD 3.5.1, I noticed that it requires: CWM v3.2.0.1 and a Super Wipe Full which scared the hell out of me...what is it going to Wipe??? ...and rooting made by RazorClaw
What I would like to understand is:
1. How do I backup the present Kernel and Apps and eventually restore it ? Under CWM 3.1.0.1 I just did a (I believe it's called) Nandroid System Backup that was stored to the MicroSD (external SD) ... what did I just back up ? Kernel,apps,both?
1.1 CWM also offers the Factory Wipe/ Reset function: what does it do? Does it restore the OLD (original as bought) Rom and wipes the Kernelt (and deletes the apps) so that it basically reverts to my original unrooted TF101 as-bought?
1.2 Upgrading the CMW would need: copying the new CWM zip into the external SD card, launcing CWM and using the upgrade procedure?
2. As apparently I need to root throught RazorClaw, I think the present rooting might interfere w/ ARevolution installation. So what would the correct unrootin procedure would be, considered my situation? I'm aware that some apps are able to unroot, but not being sure I'd rather ask.
Finally, I would absolutely love to know if there's a post generally addressing my doubts, giving me an overview of a. what's get modded by rooting b. and where c. and what ROM, Kernel, Bootloaders are in a TF101 or (more generally) in the Android world.
Thanks a lot for your help and for giving me some clues! :laugh:
Click to expand...
Click to collapse
OK here goes:
You have a custom recovery (CWM) which will allow you to flash whatever you like. There are other versions of recoveries out there CWM, rougue, etc. They all do the similar things, but some have more features than others. The nice part is that you can use one recovery to flash another. My personal preference is for the simpler versions.
1) The nandroid backup backs up system and data, but not the kernel (aka boot.img). This is typical for TFs- I think it's because the kernel is usually flashed through the staging partition and not directly in recovery, like many other android devices. The issue with not having a kernel backup when you restore a backup to "go back" but you have an incompatible kernel. This could happen if you flash a jelly bean rom and then decide to restore a backup to go back to prime (honeycomb). You'll get boot loops and hangs, but you will be able to go back to recovery and flash a compatible kernel.
1.1) Factory wipe will wipe the data partition, which is where all your info is kept. Other roms, this is called userspace. The system partition is untouched, so it will still boot, but you will have to reconfigure wifi, email, bookmarks, etc.
1.2) Essentially, yes. If you can get a CWM flashable version of a recovery, you can flash it in CWM or any other custom recovery. It will be a zip file. Be warned, some versions of recovery don't see or use the external SD card, so be sure your files are somewhere you can get to them. If only I had a $1 for every time someone flashed CWM 5.x and then did a superwipe- it uses the internal SD card and the superwipe erases all the roms and backups they had.
2) You are already rooted because you have Prime 1.4. You can use CWM to flash any rom you like, including stock, as long as you don't overwrite the recovery.
Most android users are obsessed with wiping and super-wiping. It's usually only necessary when going from a custom (a la ASUS) rom to an AOSP rom or vice-versa, and even then it will probably be fine.
---------- Post added at 08:22 PM ---------- Previous post was at 08:13 PM ----------
As far as rooting goes, it's usually an exploit that allows root level access to the file system.
I think technically, all that is needed is the su binary installed in the system folder so that it is persistent and executable. Of course, the system folder on stock roms is usually read only, which makes the exploit necessary. On custom roms, su is usually pre-installed in system/bin or system/xbin.

Follow these steps... download TWRP (its a recovery), download either ICS jelly bean ROM... place both of them in your SD card ( internal and external). Place it both because I don't know what version of CWM you are using... now restart you tablet into recovery ( press both power and volume down buttons together and as soon as tablet turns on press volume up button)... now go to the folder where you placed your recovery (TWRP.ZIP) flash/install it and reboot into recovery... now wipe (factory data, cache wipe, dalvik wipe, system, internal memory)... after these steps install the required kernel and flash the ROM... wipe dalvik cache and cache again and restart... you are good to go...
If you want to back up your old OS.. select backup and recovery option in recovery and do a backup..
Link for twrp
http://forum.xda-developers.com/showthread.php?p=28454456
Link to kernel
http://forum.xda-developers.com/showthread.php?p=29010487
Link to jelly bean ROM
AOSP ROM
http://forum.xda-developers.com/showthread.php?p=28915296
Team eos ROM
http://forum.xda-developers.com/showthread.php?p=28992514
Coming to your questions
Root access..... it gives you administrator access called superuser by which you can remove/modify/change system apps or configurations. Since you already have cwm access i assume you have superuser/root privileges. So don't worry about it... all you need to do is download the latest recovery from above link and install it through recovery. To install choose "install from SD card" and not "update from SD card"
I wouldn't advice you to back up anything because there is no use and sometimes backed apps with data give problems like random restarts/force close etc... if you still want then you can backup from recovery but it won't back up the kernel... it backs up all your system but not kernel.
Your tablet is already rooted because you have recovery access. So don't worry about rooting... if you want to unroot anytime then search for easy flash/nvflash method..
Ask questions if you have more doubts
GOOD LUCK
Sent from my Transformer TF101 using xda app-developers app

udupa82 said:
Follow these steps... [...]. now wipe (factory data, cache wipe, dalvik wipe, system, internal memory)... [...]
If you want to back up your old OS.. select backup and recovery option in recovery and do a backup..
Click to expand...
Click to collapse
First socks, then shoes!

WOW thank guys, many answers and many very detailed options! You rock!
Gee One: oh I see, so Superwise indeed does delete and format, so bye bye to any Titanium Backup on the internal SD.
Brilliant, so I guess I have to move the backup directory to the external (microsd).
Two more fast questions : what's the difference (roughly) between a "custom (a la ASUS)" ROM and an AOSP rom?
And the second one: you state that "You can use CWM to flash any rom you like, including stock, as long as
you don't overwrite the recovery." Oh wow, makes sense..without recovery it's pretty darn difficult to flash anything...but
where does Recovery reside? On the internal SD? I wouldn't like to accidentaly Wipe it out the machine.
Udupa82: wow thanks for the very detailed instructions. For the time being, I guess I'll go with Ice Cream
as I gather that Jelly Beans are still not stable...unfortunately I can't really afford the luxury of having TF101 misbehaving or
behaving weirdly (that's why I staid one year with a stable rom, I already have enough issues to address in work life, so I have
to have the Transformer running and upgraded within the week..so that if problems arises, I still have time to fix it).
Anyhow I succesfully installed CWM v3.2.0.1 - but your detailed indications made me wonder one thing: is it safer to
always place the ROM/other zip packages ALSO in the root of the internal SD (assuming having SU privileges allows me to write
in the root dir of the internal SD) ?
I also gather that restoring an Apps Backup may not be the brightest idea when doing such a jump from a 3.1 to 4.0.3 or higher,
so I guess the Titanium Backup at this point may generate more problems than It would solve.
All: as for the Kernel, I figured by the very few modded kernels (fewer people know how to mess with it properly) I've found
on XDA and by their description that kernels indeed manage the core functions of the machine, which had me wondering if any
of you guys had issues with Kernel 2.6.36.3-00001-gf377a2b in combination with some ICS or Jelly Bean Rom.
Thanks a lot for your precious directions!

elpapacito said:
Gee One: oh I see, so Superwise indeed does delete and format, so bye bye to any Titanium Backup on the internal SD.
Brilliant, so I guess I have to move the backup directory to the external (microsd).
Two more fast questions : what's the difference (roughly) between a "custom (a la ASUS)" ROM and an AOSP rom?
And the second one: you state that "You can use CWM to flash any rom you like, including stock, as long as
you don't overwrite the recovery." Oh wow, makes sense..without recovery it's pretty darn difficult to flash anything...but
where does Recovery reside? On the internal SD? I wouldn't like to accidentaly Wipe it out the machine.
Click to expand...
Click to collapse
The ASUS rom is just the stock firmware that comes with the TF. It has whatever bloatware they ASUS decided to put on there. The AOSP is built from the google code and usually contains little or no bloatware. The AOSP roms are usually cooked up by devs here on XDA. CyanogenMod is a AOSP based rom, for example.
The recovery is located on the SOS partition. I don't think you can erase it by wiping or even super wiping. Wheelie or nvflash (which is the nvidia bootloader) can wipe the partition.

elpapacito said:
WOW thank guys, many answers and many very detailed options! You rock!
Gee One: oh I see, so Superwise indeed does delete and format, so bye bye to any Titanium Backup on the internal SD.
Brilliant, so I guess I have to move the backup directory to the external (microsd).
Two more fast questions : what's the difference (roughly) between a "custom (a la ASUS)" ROM and an AOSP rom?
And the second one: you state that "You can use CWM to flash any rom you like, including stock, as long as
you don't overwrite the recovery." Oh wow, makes sense..without recovery it's pretty darn difficult to flash anything...but
where does Recovery reside? On the internal SD? I wouldn't like to accidentaly Wipe it out the machine.
Udupa82: wow thanks for the very detailed instructions. For the time being, I guess I'll go with Ice Cream
as I gather that Jelly Beans are still not stable...unfortunately I can't really afford the luxury of having TF101 misbehaving or
behaving weirdly (that's why I staid one year with a stable rom, I already have enough issues to address in work life, so I have
to have the Transformer running and upgraded within the week..so that if problems arises, I still have time to fix it).
Anyhow I succesfully installed CWM v3.2.0.1 - but your detailed indications made me wonder one thing: is it safer to
always place the ROM/other zip packages ALSO in the root of the internal SD (assuming having SU privileges allows me to write
in the root dir of the internal SD) ?
I also gather that restoring an Apps Backup may not be the brightest idea when doing such a jump from a 3.1 to 4.0.3 or higher,
so I guess the Titanium Backup at this point may generate more problems than It would solve.
All: as for the Kernel, I figured by the very few modded kernels (fewer people know how to mess with it properly) I've found
on XDA and by their description that kernels indeed manage the core functions of the machine, which had me wondering if any
of you guys had issues with Kernel 2.6.36.3-00001-gf377a2b in combination with some ICS or Jelly Bean Rom.
Thanks a lot for your precious directions!
Click to expand...
Click to collapse
As far as I remember CWM 3.2.0.1 will give you access to external SD card so no need to place the zip file in internal memory... but creating a copy in internal is always better... remember CWM 5.x.x.x version doesn't allow external SD access so never install it...
Do not use restore apps from backup as I always faced problem of force closing. If you still want to then back up any app which is important to you using titanium backup..
Asus stock ROM= its the ROM from Asus with some added softwares from Asus..
AOSP= Android Open Source Project is a OS usually written from scratch using Google's / android's source codes as android is a open software, it comes without any added software(plus point) and more setting/ tweak options(plus point)
There are some good and stable ROMs... but if you don't want much issues then I advice to go for rooted/detoxed stock ROMs because they dont need any custom kernels
Revolver ICS
http://forum.xda-developers.com/showthread.php?p=23000467
Android Revolution HD
http://forum.xda-developers.com/showthread.php?p=17202357
Good luck
Sent from my Transformer TF101 using xda app-developers app

Android Revolution HD
http://forum.xda-developers.com/showthread.php?p=17202357
Good luck
Thanks guys, the upgrade was succesfull! Indeed there's a world of a difference in speed from 3.1 to ARevolution HD..smooth as silk so far Thanks a lot for the help!

My phone wont boot into Cmw recovery, Please help.

My phone is rooted (With Super One Click) and when tap the "boot into recovery" option in Rom Manager it just send me to the stock recovery (with Blue text and what not). I have flashed Rom Manager with my Sidekick 4g before I tried to boot into recover. Please, someone help me. The answer is probably right in my face, but my noobish eyes just cant see it. :crying:
Please don't bash me this is my first post. I made sure there wasnt any post like this before i started a new tread.

Don't use ROM Manager with Sidekick 4G as CWM doesn't work the same way. When you reboot you always go into Samsung recovery from where you gotta reinstall packages to 'fake flash' the CWM recovery. If it says permission denied, the recovery file wasn't pushed to /system properly. You gotta reinstall every single time .. till of course you install a custom ROM. I think most come with voodoo CWM which replaces stock recovery, allowing you to go into CWM directly when you go to Recovery.
Firstly you need root, which I'm assuming you already have. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using other similar apps that give you R/W (read and write) access. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery.
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
Edit: Looks like the links on Krylon's page aren't working .. if someone can give an alternative it would be great!

I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app

Those guided really helped me out I spent ages reading up different things so when I finally went and did it, I didn't face any problems!
Important notes:
1. Root, obviously I personally didn't use the latest edition of SuperOneClick (at the time) on the website, but the file the dev posted on his XDA Thread.
2. Don't use ROM Manager or any other 'one click' kind of recovery for this phone. You need to download a custom recovery file and update file (links above, thanks Krylon) and go into CWM Recovery through the official Samsung Recovery through reinstalling the custom update file. This is the only way to access Orange CWM. Most custom ROMs come with the Red Voodoo CWM which is permanent in the sense that when you go into recovery, you should go into CWM (Red), instead of having to go through Samsung.
3. Orange CWM (and some say Red CWM as well) has some mounting issues. Always remember to check your mounts such that System, Data (well just to be safe, all of the items in the list) always say UNMOUNT. Basically when its mounted, means CWM has access to the partition. It says UNMOUNT because it is MOUNTED. I know thats a bit confusing, but think of it like this - there is a light switch that says ON so when you press it, turns the lights on but then the writing changes to OFF because you need to push the switch to turn it off. Erm .. hope that helps?! Lol.
4. Basically if your partitions are showing up as MOUNT, means you need to MOUNT them. Otherwise whatever changes you did won't apply! Instead of getting confused like I did, just make sure the screen says UNMOUNT SYSTEM and so forth for the rest of the items on the list.
5. Before installing a custom ROM, I always wiped x 3, before and after. Means after checking mounts, wipe data / dalvik, etc. 3 times. So for me, after checking mounts I would go to wipe date - yes - done 1; wipe data - yes - done 2; wipe data - yes - done 3. Followed by wipe dalvik and whatever else you want to wipe. Then I'd check mounts again (they usually get unmounted after a wipe .. well for me they always have anyway) before installing the ROM. Oh, sometimes I installed the ROM twice. Then I'd check mounts, wipe x 3, check mounts again before finally rebooting and letting it stand still for around 20 minutes or so. I don't really know if there is a logic or if doing it so many times makes a difference but I know some other people have done this and (other than wasting time) it doesn't really do any harm (someone correct me if I'm wrong) so why the hell not? I think the basic reasoning behind double / triple wiping and installing is to make sure that the changes are properly written as sometimes the system still retains old data.
6. Some people have SD card partitioning issues apparent. I can't remember why everyone went around partitioning in the first place (it must have been for some important reason, completely slipped my mind right now .. I personally did it to link my apps / data to SD card and save internal memory / space) but I personally used Gparted to partition my card on a computer (rather than CWM on the phone as I've heard people have issues with this) and never had a problem.
But I think thats it. I know there is a lot of information but its really worth having a look at the guide and other posts on that thread as that and the ROM thread (I personally use GOV 3.2) really had me prepare for any possible issue beforehand so I started off in a position where I could avoid them.

WTF_IsA_Android said:
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
can someone update the sidekick 4g stuff everything is either dead or does not lead anywhere to download any of the required files, thanks.

TWRP flashing basics for the Note Pro

... just some quick tips to help folks new to flashing ROMs on the mighty Notepro. Please feel 100% free to add your tips and tricks; with some luck this might be a good link reference for developers to add to their ROM postings to avoid having to rehash the same questions over and over again. I'm not shooting for 100% of info about every aspect of the flashing process, just a simple Q+A sort of thing that hopefully will help new flashers jump in and experience some success. This guide assumes you already have successfully rooted and flashed TWRP.
Q: How do I flash a ROM?
The most important thing to do is to read the posts and instructions given to you by the developers in the ROM threads. Do this first, you'll thank yourself later. Some ROMS require specific versions of TWRP or other recovery packages, or have slightly different load procedures, so it's really worth taking the time to read first.
After that, here's the general procedure for flashing a ROM under TWRP.
Download the ROM ( and optionally gapps ) from the posting, save it to your external SD card.
Reboot into recovery... with the power off, press and hold these buttons on the tablet ...
Volume Down + Power - this is Download mode ... this is typically used with ODIN or with tools that connect your tablet to a PC.
Volume Up + Power - this is Recovery mode
Q: Okay, I'm in recovery... now what?
you'll need to prepare your tablet for the new ROM, which usually means wiping some partitions . Here's the general idea once you're in the TWRP interface.
Wipe -> Advanced Wipe -> select dalvik cache, cache, system, data, internal storage (remember, your ROM and gapps should be on external-sd card).
After it - go to Install -> choose ext-sd card. First install your ROM, then (if needed) gapps.
Then reboot - first run will typically be longer ( sometimes a lot longer ) than you it normally would be.
Q: It didn't seem to work... what now?
Head back to the ROM posting, or to the Q+A for your ROM in this section and search/read. Most of the time you won't be the first person to have the problem you're having, and an answer will be out there. The Search function is a good place to begin to find your help, as is reading the ROM thread to see if others have had the same concerns.

I've pressed Volume + or - , Home key and Power. It's new for me, that the Home key must be not hold simular