Hey you can say im a noob i dont care i learn fast i had a iphone all the way up to 4g and jail broke them all. Im trying to jail break my phone
Baseband is I897UCKB2
Firmware 2.2
If i need to update to higher firmware will do so just give me instructions on what to do after it is updated i tend to learn quick at hacking.
Why don't you try reading a single sticky. That seems to be the logical start.
Yea the stickies have all the info you need to get started.
Sent from my SAMSUNG-SGH-I897 using XDA App
@ OP, normally users here flash custom firmware made by other developers which also gives us root(jailbreak) etc etc. OR you can flash stock firmware and root it with fugu root.
you want to be careful playing with bootloaders though when updating to 2.3+, i advise you search a bit and read a little first.
Hi welcome to xda let's cover a couple basics: Jail breaking is for crapples. On Android you root...
Questions go in q&a not general
And ALWAYS SEARCH before starting a new thread, this phone is almost a year and a half old, all you need to know has been posted at least 5 times already...
^This lol.
studacris said:
all you need to know has been posted at least 5 times already...
Click to expand...
Click to collapse
I will say at least 10 times, lol
As a noob myself I understand the immediate overwhelming feeling you get when you see the wealth of information and possibilities on this site. I read everything I could find, soft-bricked my captivate a few dozen times, flashed dozens of ROMS and Kernel combos until I finally found something that worked for my unique needs. The information below is very basic and not intended as a guide. There may be some wording or errors but the general description of each item is accurate enough to get the point across.
Some basic things I learned to begin with:
Eclaire: Android Operating System 2.1.x
Froyo: Android Operating System 2.2.x
Gingerbread: Android Operating System 2.3.x
Root: Gives you full "Super User" rights to the device. As a super user you can browse, delete, change any folder or file on the device. It allows you to remove pre-installed programs that AT&T seems to think are too important to erase. It allows you to change system settings that were locked by the manufacturer. Without being rooted you are limited to using the operating system provided by the service provider as shipped.
Bootloaders: The initial starting point when a device is booted. The bootloader basically gets the device hardware powered up and starts the Kernel. From there the kernel loads the base operating system and starts the GUI for you. The bootloader is really the only item that will bite you when trying to change your device's operating system. If you try and flash it and something goes horribly wrong while it's loading it is possible to make the device unbootable for repairs. Bootloaders from a device running Eclaire or Froyo must be updated to Gingerbread in order to properly boot the Kernel. Interestingly, Gingerbread Bootloaders are backwards compatible and can be used on Eclaire or Froyo as well.
Kernel: In its basic sense, the kernel acts as the bridge between the device hardware and the chosen operating system. Custom kernels can open up many of the device's potential by allowing the CPU to be overclocked or the voltage levels to be adjusted for heat and performance. Many of the devices weaknesses can be tweaked around for better performance. On our devices there are a lot of custom kernels that allow you to overclock and can change the format of the system and data partitions to make them faster (lag fix). Kernels for the 2.1 -2.22 ROMS can make huge differences to the battery life and speed of the device. Developers must have the initial Source Code of the kernel to tweak many of the hardware functions and unfortunately, Samsung has not released any source code for our specific phones for any of the 2.3+ Roms.
CWM = Clockwork Mod. Clockwork mod is a Recovery menu that replaced the stock useless menu that comes on the device. It allows you to install new ROMS, updates, mods, etc... from the device itself. It would be like booting your PC in to DOS or an Linux box to a command line. You can either install CWM on a pre-rooted device or download a kernel that has already had CWM coded into the file. For instance, on the latest leaked 2.3.5 ROM for the I897 I took a rooted phone running a 2.2 ROM and installed the new operating system to it. It was unrooted. Boog cooked up a new kernel with CWM added. After installing the new kernel I booted up and my phone was rooted.
Root Explorer: File browsing software from the market that allows users of rooted devices to browse the entire file system of their device. Hidden and locked items are accessible and "changable". Use with caution.
Rom Manager: A downloaded program that can be used to install CWM on a rooted phone. It can also be used to locate and download roms that developers submit to their database. It also acts as a GUI to some of the minor functions of CWM in that once a ROM has been downloaded you can choose to install it and set some of the parameters for that installation up before it reboots to CWM and starts the install. I prefer to boot to CWM myself and install from there. Most would agree.
AOSP: Raw Android release from Google Developers. Device manufacturers take these AOSP releases and create their own device specific versions to be installed on their devices. Many custom ROMS are based on AOSP and are very popular. Cyanogen (CM7 currently) and MIUI are very popular versions of AOSP. Unfortunately, on our Captivates these AOSP based ROMS drain the battery much faster than on Samsung based ROMs. When an AOSP based ROM/Kernel is installed the phone must be flashed back to a stock Samsung ROM with Odin or Oneclick before a non-AOSP ROM can be installed. AOSP ROMS use a different partition setup and Samsung based ROMS will not run if installed directly on top of an AOSP Rom. Interestingly, MIUI can be installed via CWM directly on top of a Samsung ROM but not the other way around.
I9000 based ROMS: Many custom Gingerbread Roms are actually Roms built off of Roms that were originally for the Samsung I9000. They work well and can be tweaked and adjusted because the I9000 kernel source is available for developers. While they work great in most aspects they fail to utilize the full potential of the I897 because the I9000 has a different chipset. Audio quality, GPS lock and battery life can be problematic or degraded in these ROMS.
ODIN: Odin is a program for your Windows based PC that is used to install Roms, Kernels, bootloaders and features to your device. It can wipe your device and install an unrooted, clean, fresh stock operating system or canbe used to install custom Roms if the developer chooses to release it in an Odin package. Odin can be picky and unstable at times so limit bootloader flashing to the absolute minimum with this software. To use Odin you must get your phone in to Download mode.
Odin oneclick: A derivative of ODIN where the ROM or feature you are wanting to install is prepackaged into the ODIN program itself. There are no options or files to choose. You start the software, connect your phone in Download mode. Wait for Odin to recognize it then hit "Start".
TAR: Often referred to as a Tarball. Similar to ZIP or RAR. It is a linux based zip format for packaging programs and compressing them for download. When flashing anything with Odin you will download files with the TAR extension. Odin does not open files with Zip extensions.
Heimdall: Opensource program for Linux, MAC or PC that can be used like ODIN. Much more reliable.
APK: APK files are the individual programs for the device. When you download a file it will be *.APK. You can manually install an APK file on your device as long as you have enabled non-market APPs in the setting. Programs downloaded from the market are also in APK packages but are automatically installed when you download them.
Download mode: Base mode for the phone. Shows a yellow triangle with an android digging. This is used whenever you are connecting your device to the computer to load a new bootloader, kernel, update or ROM via Odin. If you completely ruin your operating system and think you have bricked your phone, you can reload it and start from scratch as long as you can get your phone in to download mode. To boot in to download mode on a Captivate you have to remove the battery and put it back in. Hold down both volume buttons while plugging in the usb. Some devices require you to hold vol-up or volume-down instead. Mine has always been both.
Recovery Mode: Simple text based mode where the kernel has booted but the operating system and GUI have not been loaded yet. The standard Recovery Mode menu is basic and allows you to reboot or install an update.zip file. On a rooted phone with CWM installed the recovery menu is much larger ith options to wipe the cache, adjust kernel settings (on custom kernels), install new roms or kernels, format SD card, Wipe phone, etc...
jbabbler said:
As a noob myself I understand the immediate overwhelming ... with CWM installed the recovery menu is much larger ith options to wipe the cache, adjust kernel settings (on custom kernels), install new roms or kernels, format SD card, Wipe phone, etc...
Click to expand...
Click to collapse
As a follow up / additional information, check out the link in my signature (or the associated sticky). That has some more definitions and terms if you need them.
jmtheiss said:
As a follow up / additional information, check out the link in my signature (or the associated sticky). That has some more definitions and terms if you need them.
Click to expand...
Click to collapse
mucho grassyass
The above made me lol
Sent from my SGH-I897 using XDA App
Related
So as of Oct 1st I've been the proud owner of a Captivate. This is upgrading from an Ericsson feature phone, which while I hacked, the scene here is very different. Moreover, the organization and level of detail I tend to find things is a little lacking (yes, I've used the search feature). I understand that the Android platform is spreading rapidly, the Captivate especially, so I will say I don't fault XDA or anything. I'm just trying to educate myself (and hopefully be able to help the community later) via a massive post on breaking myself into the Captivate hacking circle.
Most of the below are questions that fall under some kind of similar topic.
What do the I8000/I9000 terms pertain to? Which phones or firmware versions are which Ix000? How can I check for myself in the future? (I'm under the impression that the Captivate falls under I9000, but still I'd like more firm determination.)
How many ROMs can be active on a phone at once? (Can a ROM be just some UI changes, on top of another that changes some backend file organization or, say, another UI alteration for a different section of the phone?)
ROM Manager + Clockwork Mod seems to be the defacto tool for flashing phone ROMs and creating backups with the Captivate. But I've also seen people suggest using Titanium Backup often for creating backups if the user wants to have a stock state of their phone to revert to in order to go back to a clean slate. (Only real difference that is apparent is TB seems to use the word "image" and not "backup", but if that's the case then what does a "backup" count as out of ROM Manger?) And what of Odin? Or Nandroid? I get there are different methodologies to do the same thing, but it’d be nice to lay out the details, uses, pros, cons, and comparisons between all these backup utilities.
Thanks in advance!
EDIT: Shoot, thought I was on the Q&A page. Feel free to move. Apologies.
While you are in development look at the captivate bible, it links to the important threads, I think there is a wiki up somewhere too that answers the important questions.
Titanium backup backs up apps and data but I don't know if its in the form of an image, certainly not a full disk image.
Nandroid is a feature of rom manager/clockwork recovery, I believe that is an image but I haven't actually used a backup from it yet so I don't know if it is or isn't.
Odin is a tool for flashing samsung firmwares, 3rd party roms can use odin and a hybrid can be made my mixing one rom with another kernel or modem.bin.
Most recent 3rd party roms use a .zip file run in clockwork recovery which can be launcher from rom manager.
Some mods and I think a few roms are run as an update.zip in the stock recovery screen which you get to via a button combo on boot up. Hold both volumes for 2 sec then press power and continue holding all 3 buttons till the att screen pops up.
Since you are new to android, I'd look at designgears work, or eugene. High quality stuff. Cognition 2.2 is based on leaked froyo and is probably the best gps and fastest, linpack shows the best numbers with froyo(2.2). But for 3d gaming the overclock (only on eclair (2.1)) will give better frame rates from a higher gpu clock. Not that the humming bird needs better 3d performance. It already leads the field in that area, most benchmark are ineffective because the gpu is capped at 56fps and it will hit that cap through most tests.
Kernels for overclock/undervolt and/or voodoo are loaded into condition 2.1.x and can be added to other eclair roms with ease.
eugenes roms are very thought out but take a while to get right on the captivate since he has a vibrant and there are differences.
I-9000 is the international galaxy s and is the most feature rich version that is gsm, many files roms ect can run on the captivate with some bugs, I-9000 kernels are used to enable hsupa, but break the bluetooth.
Lag fix is a ext2 or ext4 partition to boost file system speeds, ask a dev about how that works, I have no idea. Voodoo lag fix, I think is a full file system replacement and considered superior. its not available in froyo, we have no source code for froyo to build the kernel.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Cyber_Bruno said:
What do the I8000/I9000 terms pertain to? Which phones or firmware versions are which Ix000? How can I check for myself in the future? (I'm under the impression that the Captivate falls under I9000, but still I'd like more firm determination.)
Click to expand...
Click to collapse
It is the Samsung's code for their devices. For example :
i900 --> Samsung Omnia
i8000 --> Samsung Omnia II
i9000 --> Samsung Galaxy S (International)
B7610 --> Samsung OmniaPRO (the touchscreen slider)
C6625 --> Samsung Valencia
And finally, i897 --> AT&T Samsung Captivate
Cyber_Bruno said:
How many ROMs can be active on a phone at once? (Can a ROM be just some UI changes, on top of another that changes some backend file organization or, say, another UI alteration for a different section of the phone?)
Click to expand...
Click to collapse
No, only one ROM can be used in the device at the same time. It is recommended to flash stock ROM first before flashing non-stock ROM, to avoid conflict between ROMs. Every non-stock ROMs is made to replace stock ROM, not another non-stock ROMs.
Cyber_Bruno said:
ROM Manager + Clockwork Mod seems to be the defacto tool for flashing phone ROMs and creating backups with the Captivate. But I've also seen people suggest using Titanium Backup often for creating backups if the user wants to have a stock state of their phone to revert to in order to go back to a clean slate. (Only real difference that is apparent is TB seems to use the word "image" and not "backup", but if that's the case then what does a "backup" count as out of ROM Manger?) And what of Odin? Or Nandroid? I get there are different methodologies to do the same thing, but it’d be nice to lay out the details, uses, pros, cons, and comparisons between all these backup utilities.
Click to expand...
Click to collapse
ROM Manager & Clockwork Mod --> Same utility, get from the market. Flash stock ROM first. You don't need PC to flash with ROM Manager/Clockwork Mod
Odin --> Conventional way that needs PC to flash the ROM. Flash stock ROM first. Usually ROMs that need Odin will be available as .exe file, and the .exe file contains Odin with the ROM, so, you don't need to download Odin separately
Titanium Backup --> A backup app, get from the market. It will generate an .APK file that contains the app with their data (for example : saved games) as an .APK file. After flash the new ROM, just reinstall the generated .APK file. It can backup app (with data), WiFi settings, contacts & calendar (better use your Google account), SMS/MMS (better use separate SMS/MMS backup app from the market), Call History, etc
Nandroid --> I don't know, never used before.
Cyber_Bruno said:
Thanks in advance!
Click to expand...
Click to collapse
You're welcome
Nandroid --> I don't know, never used before.
Click to expand...
Click to collapse
Nandroid is a function of RM/CWM wherein it take a full snapshot of the current rom setup: system, application data, etc. (no, it does not copy the entire internal SD card.)
Well, your questions are pretty standard things, not really related much to actual dev work.
I will point you to the 3 most important things you will need to get started.
apk manager
auto-deodexer
apktool
...and the obvious dev tools, netbeans, android sdk, etc...
...one more thing...
This thread is godly;
http://forum.xda-developers.com/showthread.php?t=725870
I just got a new I9000 Running 2.2 from Vodaphone in Australia.
Getting very bored of it in stock form and want an increase its speed/features as much as I can. Unfortunately I know absolutely nothing about anything custom. This is my first smart phone.
The amount of custom stuff released for this phone is mind numbing, and I know there is a lot of potential there to be unlocked.
So my question is in mid 2011, near the end of the phones prime life, what is the generally accepted best thing you can do with this phone? I'm sure after all this time many things have become redundant and been replaced by better things?
In a nutshell I want to get my phone to the highest speed and feature rich state I can. Speed is definitely the highest priority followed by features and ease of use.
This includes any kind of modding including overclocking.
What I know about this phone is from when it was released there used to be lagfix, voodoofix etc to change the file system and speed up the phone. But have those things been replace by custom roms now etc?
I can follow instructions easily, but as long as they encompass everything from Stock form to completion.
For example I really don't like guides or instructions that as a first step they say something like
"Before you do this made you have rooted your phone, go into flash recovery mode use the Jhp.ascii and use odin to enter download mode. male sure you have the dbdata.rfs, boot.bin in the directory before proceeding"
I want instructions that tell you how to root the phone properly, how/what flash recovery to use, how do I use get Odin etc what all these files are what they do how to get them etc.
Bassicaly talking someone who has never flown before into landing a plane.
I think for many of the people who write instructions things they see as completely obvious basic and what they consider common knowledge are completely unknown to new people. I find 97% of the instructions for any modding mention things where prior knowledge is assumed.
Lastly even if you know how to follow instructions, the amount of stuff available for this phones means I wouldn't know where to start. So I need to know what are the most favoured mods to do, in as complete packages as possible.For example I would rather flash with one mega rom that comes with everything than install every little tweak manually
Hi go checkout romkitchen.org
Also live support in irc, check my sig.
See you there ;-)
Thanks. I'll definitely be checking that chanel out if I can't manage here, but it will have to be sometime next week for irc.
At the moment Im busy doing things around the house and I may need to go in out at any time so I was hoping for a forum post so I can read it and check up on it when I can.
But like I said when I get a few hours of no interuptions I may sit down to do all the mods live
So is darkys rom any good?
From what I can tell its
Root phone.
Install Darkys ROM.
Done.
I just need to get someone to tell me if my phone is fully compatible, and how to back up my vodaphone stock firmware if its not available on the internet already.
Phone info.
Baseband version
I9000HVJP3
KERNEL VERSION
2.6.32.9
[email protected] #6
BUILD NUMBER
FROYO.HVJP4
My personal experience is that whenever you're using a custom rom, you're using a lot more potential of your phone, than by using a Stock-Rom, updated by Kies.
The Guides all seem a bit hardcore when you start first, but it really is worth it. I recommend you start with the EZbase Guide which offers a step by step guide with screenshots (which I was really happy for, having no clue where to start), located here: http://forum.xda-developers.com/showthread.php?t=991792
After reading AND understanding this guide, you are good to go to start flashing, BUT every flash has a potential risk of bricking your phone, making it a pretty expensive paperweight. If you come to bootloops or a lot of force closes on start: Don't be worried, you can fix this (or at least i could after running into them). The first time I flashed was due to lots of force closes after updating with Kies, which was my start for using custom roms.
The choice of custom rom is pretty much your own. There are several roms I liked and there is one, I pretty much stick with: Insanity (currently using 8.5, which has some battery drain issues for me, after loading the battery or putting the phone to flight mode ... I'm gonna report that to nitr8, once I got 10 Posts ).
However, you got to (or rather better) find your own favorite.
When I got the phone I was told it was locked.
Will this interfere with any modding?
I was told I can call vodaphone and they will unlock it for me, but it seems there is also a hack way to unlock it.
. Unlocking your phone.
--Why, when, where: If you bought your phone with a contract, chances are that it might be locked in that specific network. If you want to also use other SIM cards in it, that are from another provider, you will have to unlock the phone (!! WARNING !! in most cases this will lead to a void warranty, please consult your contract).
--Prerequisites: Root privileges, adb.
8.1. Get the /efs/nv_data.bin file from your device to your computer. You can do this either with adb or by copying the file to your SD card with "Root Explorer" and then copying it over to your machine from the SD (Be sure to keep a backup of this file and the /efs/.nv_data.bin.md5 file.)
8.2. Open up the file in a hex editor, go to the address 0x181468, where you will see something like this:
FF 01 00 00 00 00 46 46 46...
We are interested in that first '01', that means the phone is locked. Just change it to '00' and save the file. Copy it back to your SD card and then with "Root Explorer" back to it's original location (or 'push' it directly with adb). Then remove the .nv_data.bin.md5 file and restart the device (Again, be sure to make copies of these files before modifying or deleting them!). After this, you should be able to insert any SIM card into your device and it should work without the need for any further hacks.
miui for beauty and speed
welcome to the galaxy of galaxy S ROMs..
you have made a very wise decision to buy galaxy S.... even though a year old it blows every single core phone out of the water..
now back to your question:
1. ROM :
if you are looking for speed and beauty then you don't have any other place to go than MIUI..
other custom ROMs are good but they are just some cosmetic change of galaxy ROM. .but MIUI is totally different.. (awesome would be understatement)
Trust me I have battery problem in MIUI but still I can't go back to samsung ROM>
that is how good the ROM is... others are getting good battery life out of the latest MIUI ROM... with the latest kernel you can overclock your phone upto 1.5 ghz...
http://forum.xda-developers.com/showthread.php?t=992251
head over to this link and read carefully and decide whether you want to flash this ROM or not..
there are other good gingerbread ROMs as well though I have not tried most of them..
2. VOODOO sound!!!!!
this is the biggest thing that has happened to galaxy S... google it once and you will know its awesomeness.. It's basically well tuned sound driver made by supercurio... most of the people after using voodoo sound have considered galaxy S to be the most awesome sounding music player (not just phone) ever..
better than iphone and other DAP..
(most of the custom ROMs comes with kernel supporting VOODOO sound... you just need to download voodoo app from the market)
I think those are the two awesome things you can do with your galaxy S...
there are other things too that you can learn if you follow xda..
happy XDAing
steps for installing MIUI ROM
to make things short,, just follow these 8 steps.. that's it
0: Be sure that you're based on a Froyo FW! CRUCIAL.
1: Load these files:
a) galaxy-efsbackup.zip / Mirror
b) cm7-galaxys-initial-kernel.tar / Mirror
c) MIUI MCGv1 / Mirror
d) speedmod-kernel-k13c-500hz.tar / Mirror
(thanks to creative59 for mirrors!)
2: Copy all files except:
speedmod-kernel-k13c-500hz.tar & cm7-galaxys-initial-kernel.tar
3: Flash speedmod-kernel-k13c-500hz.tar via Odin, wait for reboot and after that shutdown
4: Start via 3-button-combo in recovery mode and install galaxys-efsbackup.zip
5: Pull out battery and in again, start via 3-button-combo via download mode and flash cm7-galaxys-initial-kernel.tar via Odin BUT DON'T check repartition and auto reboot
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
7: Choose "mounts & storage" and format system, data, cache
8: Flash MIUI MCGv1.
First and foremost check if bootloader locked...then check the recovery / download modes work and then proceed...
Sent from my GT-P1000 using XDA Premium App
Thanks for your post ujjwal321. For a first attempt, I am very happy with what you suggested. I think there is enough there for me to try it on my own and MIUI seems good.
A few things I'd like to point out though. The ONLY reason I actually decided I have enough information from your post to mod is because of the youtube video that goes through the install process. There is absolutely no way would ever know what to do without the video, and most roms do not come with it.
I am very unhappy at the level of ease and lack of instructions in the written instructions of roms...
For example If I did not watch the video, I would never know to put the phone in "USB Debug" mode.
Why are things like this not listed in step by step instructions?
Secondly, even the things that are listed like
": Load these files:
a) galaxy-efsbackup.zip / Mirror
b) cm7-galaxys-initial-kernel.tar / Mirror
c) MIUI MCGv3 / Mirror
d) speedmod-kernel-k13c-500hz.tar / Mirror"
are baffling.
To someone doing this for the first time the word "load" is as meaningless as kaka
Load to what!?
"Copy all files except:
speedmod-kernel-k13c-500hz.tar & cm7-galaxys-initial-kernel.tar
3: Flash speedmod-kernel-k13c-500hz.tar via Odin, wait for reboot and after that shutdown"
Copy to what? Flash to what, how? what is flash?
Luckily by looking at the video, I know exactly what to do. However its all because of monkey see monkey do, there is no level of good communication through a good set of instructions or guide, and thus there incomplete understanding on my end.
IMPORTANT
Before doing any of these things, does my phone need to be rooted? Currently it is locked and completely stock. Or Can I just follow the youtube video instructions from the get go? I also just read "When upgrading to 1.5.20 you need to wipe data, datadata, cache and system!". What? All I know is how to go to settings>SD card and storage and format the SD card, as well as Privacy>reset settings>Factory settings, Is this enough?
I ask because form what I have seen so far nothing is clear cut and your meant to already know 99 facts for every 1 mentioned.
Lastly, before I do any flashing, I really NEED to know either how to back up my current firmware, or if it is available online. It is Aussie vodaphone 2.2
What do I do in case I need to claim warranty? I need to put the stock one back on. I have 2 years of warranty after all, If I don't back it up I loose all that.
So, can anyone shed some light on this?
P.S blackheart, I can enter the download mode and the recovery mode by doing the 3 button combo, it goes into the respective screens and i can scroll up down using the volume button. I have not done anything more than that, I hope that means its not locked.
Hey!
About the loading of files. It just means u copy them to your phone.
There are 2 ways of flashing. With odin/heimdall, and through the phones recovery. To flash in the recovery the files need to be located in the phones memory.
Before flashing without having any clue i suggest reading a lot of faqs etc.
Sent from my GT-I9000 using XDA App
I realky recomend ezbase as your start point. Idiot proof instructions, it worked for me so they must be!
Sent from gt i9000 insanity 8.5/fugumod
Get CM7 and you'll never look back
splendidtry said:
I just got a new I9000 Running 2.2 from Vodaphone in Australia.
Getting very bored of it in stock form and want an increase its speed/features as much as I can. Unfortunately I know absolutely nothing about anything custom. This is my first smart phone.
The amount of custom stuff released for this phone is mind numbing, and I know there is a lot of potential there to be unlocked.
So my question is in mid 2011, near the end of the phones prime life, what is the generally accepted best thing you can do with this phone? I'm sure after all this time many things have become redundant and been replaced by better things?
In a nutshell I want to get my phone to the highest speed and feature rich state I can. Speed is definitely the highest priority followed by features and ease of use.
This includes any kind of modding including overclocking.
What I know about this phone is from when it was released there used to be lagfix, voodoofix etc to change the file system and speed up the phone. But have those things been replace by custom roms now etc?
I can follow instructions easily, but as long as they encompass everything from Stock form to completion.
For example I really don't like guides or instructions that as a first step they say something like
"Before you do this made you have rooted your phone, go into flash recovery mode use the Jhp.ascii and use odin to enter download mode. male sure you have the dbdata.rfs, boot.bin in the directory before proceeding"
I want instructions that tell you how to root the phone properly, how/what flash recovery to use, how do I use get Odin etc what all these files are what they do how to get them etc.
Bassicaly talking someone who has never flown before into landing a plane.
I think for many of the people who write instructions things they see as completely obvious basic and what they consider common knowledge are completely unknown to new people. I find 97% of the instructions for any modding mention things where prior knowledge is assumed.
Lastly even if you know how to follow instructions, the amount of stuff available for this phones means I wouldn't know where to start. So I need to know what are the most favoured mods to do, in as complete packages as possible.For example I would rather flash with one mega rom that comes with everything than install every little tweak manually
Click to expand...
Click to collapse
Here are some instructions I gave to someone in a similar situations. Install videos are available on my site sgsromreviews.weebly.com. Hope you find this useful
1. Download Odin 1.3, Tweaky ROM, CF Root Kernal and JVH firmware 2. Use Odin to flash JVH.(you need to get the phone in to download mode using the vol down key + home key + power at the same time. (If this does not work I WOULD STOP NOW AND LOOK AT HACKING YOUR PHONE TO ENABLE THIS FUNCTION) 3. In select the JVH .tar file in the PDA section. DO NOT TICK RE-PARTITION and then click start 4. The initial boot will take longer than usual so be patient, if your phone begins to vibrate constantly and for no reason then take the battery out and enter download mode again for re-flashing (if this happens feel free to email me again for further advice) 5. Once you are running JVH copy Tweaky ROM over to your INTERNAL SD card 6. Enter the back in to download mode 7. Use Odin to flash the CF Root Kernal, select the .tar file in the PDA section again and again DO NOT TICK RE-PARTITION 8. Once this has booted turn the phone off and enter clockwork recovery using the vol up key + home key + power at the same time until the white Galaxy S I-9000 writing comes on the screen then let go 9. Navigate clockwork recovery using the vol keys and the power key to select. Go down to install .zip from SD card, then choose .zip from SD card and choose to install Tweaky 10. Use clockwork to wipe data then wipe dalvik cache (found in advanced section) 11. Reboot phone and enjoy Tweaky
I have provided the download links for you, if you need more help feel free to ask.
Thanks Chris
Odin 1.3 http://www.multiupload.com/4JLU4QHUV7 Tweaky http://forum.xda-developers.com/showthread.php? t=1059561 CF Root http://forum.xda-developers.com/showthread.php? t=788108 JVH http://www.samfirmware.com/ (free account needed to download)
Sent from my GT-I9000 using XDA Premium App
Im a relatively new flasher as well, so I know exactly what you're going through just now!
That said, I've done about 15 flashes now so I feel I have a good grasp of what's required. I would also like to suggest MIUI. I have tried a few of the roms out there, but MIUI simply takes my breath away it's that good.
To give you an idea of how good it is, I've flashed it onto 4 other peoples phones because they were blown away by it!
If you need any help with what to do, PM me. I'll put together a package of everything that you need and I'll happily sit and explain each and every step to you personally if need be (if you are a gamer and use Ventrillo I'll verbally speak you through the process as well).
As for returning to stock, you can restore your phone back to it's original state by downloading stock firmware and isntalling that on your phone. It's very simple. EXBase is probably the most straightforward one there is that I have come across.
alright installed MIUI.
Looks like it will take a while to get used to compared to the stock rom. I dont know if its any better yet. Just different. I am not seeing any more features, actually kind of less, but I am sure I am missing a lot.
It is faster though.
Anyway, how do I overclock now? There seems to be no options for that.
I also dont like how its all symbols and no writing.
Al in all seems like a decent stable rom.
I'm planning on updating my ROM soon and was wondering if there was anything special I need to do to my phone prior to flashing the new ROM?
I'm currently on JPP with the hardcore speedmod i1r2, so pretty old compared to what's out there now. I flashed the hardcore kernel previously via Odin.
If I follow the instructions on [email protected] http://insanity.rollus.net/EZbase/EZbase-2.00.pdf but replace the insanity ROM with any other ROM (e.g. JUWE ROM), will it work ok?
Thanks
MIUI is awesome i can second that !!
since i switched to MIUI on RC3 months ago, i havent looked back.
MIUI is packed full of features and gets updates weekly / sometimes daily lol
just get familiar with it and you will discover its true beauty
azzledazzle said:
MIUI is awesome i can second that !!
since i switched to MIUI on RC3 months ago, i havent looked back.
MIUI is packed full of features and gets updates weekly / sometimes daily lol
just get familiar with it and you will discover its true beauty
Click to expand...
Click to collapse
(Be aware I don't know much about MIUI or smart phone software in general.
and I just installed it about an hour ago)
What features is is packed full of? I want to know so I can try it out/make use of it.
The only new thing I see extra is that maxthon internet browser.
Everything else I notice that is different, its funnily enough things missing compared to stock.
For example where are is the ability to add all the shortcuts/apps etc on the main screen by just holding the screen down? A lot similar features like this seem either not there or or at least harder to find/make use of comapred to stock.
Some things are just definitely taking a step back, for example adding a Doom 1 style grey border on the camera.
And my fav live wallpaper, Aurora, doesn't work on MIUI. It just crashes and I have to force close?
Also TV out doesn't work, and choppy movie playback?
And my 3d performance seems to have gone down about 15% from stock Stock, frames hit about 570, MIUI, about 470.
I'll be using it for longer but I gotta figure out what all the hype is about.
I think a stock rom + speedmod and lagfix is the most easy and the fist step to any new user of SGS?
as its really simple to apply
yihinlau said:
I think a stock rom + speedmod and lagfix is the most easy and the fist step to any new user of SGS?
as its really simple to apply
Click to expand...
Click to collapse
So by flashing to MIUI from complete stock phone, did I achieve all of this plus more? OR did I miss something? E.g do I have lagfix as well? Or do I need to install this on top of MIUI?
I followed the install instructions step by step. 3.11 MIUI.
It seems like my Benchmark scores aren't flying like I expected them to, and the phone still lags/jerks on animations doesn't respond etc...
My Quadrant standard score went from 1000 on the stock phone to 1700 when I flashed to MIUI.
I also decided to install setcpu and overlocked to 1.2 ghz then 1.4 on both the on demand and performance setting
And still my score only goes up to about 1900 quadrant standard score on 1.4ghz :S
I find it strange that people are getting much higher much more easily.
For example how did this phone get 2500 just on 1.2ghz? Is it MIUI that sucks?
http://www.intomobile.com/2010/08/1...ck-hits-1-2ghz-delivers-off-chart-benchmarks/
I feel like I would have to go to 2.5Ghz to get that score.
Not to mention 3100? Wow?
http://www.addictivetips.com/mobile/overclock-samsung-galaxy-s-to-1-6-ghz-blows-off-competition/
What am I doing wrong here? What are they using?
like I said I also noticed 3d perf went down from stock 2.2
On the stock 2.2 the total frames was higher. For example in the test with the corridor and cube, my frames would reach about 570 at the end of the test on 2.2 stock ROM.
On MIUI ROM it only reaches about 476.
got honeystreak rc 2.1 on my dell streak 7 and i have no clue how to get clockwork recovery on it with honeystreak, so when i get rom manager and flash clockwork it works, then i reboot into the original recovery then i choose software upadate.pkg then when i click it nothing happens it just has the dell logo then it just powers up like it normally would so i cant get clockwork i need help!!!
CWM and Honeystreak are not compatible.
Same thing happened to me, the root was easy with gingerbreak, had root so I could run rom manager and flashed that to the clockwork recovery and backed up. Installed honeystreak using the nvflash and didnt like the instability of it so I wanted to go back but didnt realize the way back was another nvflash the breaks the device and then you have to recover from the cwm back up. I returned it at that point.
I've learned some more about nvflash since then, it seems its the official way they install the os's to the tegra devices. But without the official install files needed for your device, it has to be rigged. Which is why the honeystreak is unstable and the flash back to stock is broken and has to be recovered from a back up.
Windows, ubuntu are such easy installs compared to android. Everythings on a disc(that you can setup on a usb stick), there arent 14 or how ever many separate files you have to download(for the nvflash). And it just starts the install, you dont need separate program to install. They really made the process needlessly complicated for installing android.
I just find it hard to believe, non developers have to RELY on the hacker community to perform fresh(or not so fresh) installs because google/the middlemen dont provide installation media. Oh wait they provide the source code... which if your not a developer is no help to the uninitiated that just want a clean install, install newer versions.
http://forum.xda-developers.com/showthread.php?p=16257823#post16257823
http://forum.xda-developers.com/showthread.php?t=1018809&highlight=nvflash
papermate said:
Same thing happened to me, the root was easy with gingerbreak, had root so I could run rom manager and flashed that to the clockwork recovery and backed up. Installed honeystreak using the nvflash and didnt like the instability of it so I wanted to go back but didnt realize the way back was another nvflash the breaks the device and then you have to recover from the cwm back up. I returned it at that point.
I've learned some more about nvflash since then, it seems its the official way they install the os's to the tegra devices. But without the official install files needed for your device, it has to be rigged. Which is why the honeystreak is unstable and the flash back to stock is broken and has to be recovered from a back up.
Windows, ubuntu are such easy installs compared to android. Everythings on a disc(that you can setup on a usb stick), there arent 14 or how ever many separate files you have to download(for the nvflash). And it just starts the install, you dont need separate program to install. They really made the process needlessly complicated for installing android.
I just find it hard to believe, non developers have to RELY on the hacker community to perform fresh(or not so fresh) installs because google/the middlemen dont provide installation media. Oh wait they provide the source code... which if your not a developer is no help to the uninitiated that just want a clean install, install newer versions.
http://forum.xda-developers.com/showthread.php?p=16257823#post16257823
http://forum.xda-developers.com/showthread.php?t=1018809&highlight=nvflash
Click to expand...
Click to collapse
so your saying its not possible to get cwm on honeystreak
azoller1 said:
so your saying its not possible to get cwm on honeystreak
Click to expand...
Click to collapse
Its possible to get cwm(the app) ON honeystreak. What doesnt work on honeystreak is the clockwork recovery boot up menu as you have noticed yourself. Dont ask me why, I dont know. And the only current "fix" for it is to nvflash to stock where the clockwork recovery boot up menu works.
I have an open question for anyone, does clockwork rom manager work properly on honeycomb and thereby make the problem isolated to honeystreak? Or does it not work properly on honeycomb at all.
Honeystreak requires NVflash to install because it completely repartitions the nand.
nandroid depends on knowing ahead of time what the partition layout is, it's not gonna work if it'd different depending on what rom is installed.
If someone made a HC compatable clockwork it wouldnt be compatable with the stock rom either
so when the official honeycomb comes out for the dell streak 7 will clockwork mod actually boot up correctly?
azoller1 said:
so when the official honeycomb comes out for the dell streak 7 will clockwork mod actually boot up correctly?
Click to expand...
Click to collapse
When clockwork rom manager is updated to work on HC it will work... thats what I understood from his post, considering the partition layout is different on HC from previous versions.
There needs to be a partition editor and usb/sd card install-able android media like with ubuntu/windows too do away with these crippled ways of doing this. This modern os cant even perform the basics of installation that desktop os's have performed for a decade?. Maybe when Ice cream source code comes out, this is exactly what someone will do. Til then this is ridiculous. They have so hamstrung the ability to control the os on your hardware. What good is open source software if they control how it gets on the hardware. This is not a methodology I would support.
I'll have to see how windows 8 is handled on arm hardware. Might be the only os you can install and update on your own without the hassle. Or I just wont buy any arm devices and stick to flip phones and laptops for mobility.
papermate said:
When clockwork rom manager is updated to work on HC it will work... thats what I understood from his post, considering the partition layout is different on HC from previous versions.
There needs to be a partition editor and usb/sd card install-able android media like with ubuntu/windows too do away with these crippled ways of doing this. This modern os cant even perform the basics of installation that desktop os's have performed for a decade?. Maybe when Ice cream source code comes out, this is exactly what someone will do. Til then this is ridiculous. They have so hamstrung the ability to control the os on your hardware. What good is open source software if they control how it gets on the hardware. This is not a methodology I would support.
I'll have to see how windows 8 is handled on arm hardware. Might be the only os you can install and update on your own without the hassle. Or I just wont buy any arm devices and stick to flip phones and laptops for mobility.
Click to expand...
Click to collapse
The only reason the HC builds all require repartitioning is because they're based off system dumps form other devices. As the majority of the source isnt available the only way to get them to work is to make the device more closely resemble the donor rom device instead of making the rom more similar to the reciving device.
If/when HC lands it's either going to use the 2.2's partition map or require a pc to install that has a streamlined version of nvflash bundled. The only thing that would happen if users were able to manually repartition devices is seeing the rom completely break and require a un-repartitioning as android is hardcoded to take a specific partition layout, as device makers have the source they can change the hardcoded values.
Being able to repartition would be more akin to being able to shuffle around the layout of your pc's bios more then being able to repartition windows. There's no generic version of android (nexus devices might be considered generic, but nexus roms wouldnt boot on any other device anyway), it requires it to be ported to a specific device to work. you COULD play around with your bios to the point that you can shuffle stuff around but unless you had a good reason to there's no point.
Being Linux based, I would like to see Android loaded as modular as opposed to monolithic, and then the device manufacturers could simply release open source modules for their hardware. Of course, maybe this would slow things down for processing; but I'd really like a simple way to just port the OS on any device. This would be a great boon for the open source community.
could it be pssible to port over clockwork from another device to this? or is the only way to flash it
The original clockwork is a port, there would need to be 3 versions total to cover every rom:
2.2
3.1
3.2
as the HC roms are based off multiple device dumps and neither are compatable with eachother
Hello, people of xdadevelopers! I'm new here and keen to learn up on custom Android roms. Sorry if i sound really noob or am doing things wrong in this forum, but... everybody has their own starting phases right?? ^^ Please guide me where I'm going wrong...
Anyway, I'm from Singapore and i own a SAMSUNG GALAXY BEAM GT-I8520 (rare and unheard of phone released only in Singapore x.x). I won't elaborate much, but basically I'm kind of still a student (therefore no money to buy other phones) and my mobile plan is left with about 11 months to go before i can renew my plan and select another phone for a cheaper price... I don't really like my phone because the moment Samsung released it, they decided to stop updates because there is not enough users of this phone so I'm stuck with 2.1 eclair. It also has a slow 500/700mhz processor and lags like he**. By the way, it was released around July 2010 at the same time with the Galaxy S, and they have really similar specs, that's why i posted in this area of the forums.
So, i was thinking of switching over to the MIUI rom which i desperately want... and i decided to follow the Galaxy S I9000 (because they are sister phones!) tutorials to flash over to MIUI in hope it would revitalise my phone, stop the laggyness and crashes, give it a new look, allow me to use features that i miss out in froyo or gingerbread!!
I can understand most terms and softwares about flashing... been researching for a few days... and i found this guide
http://forum.xda-developers.com/showthread.php?t=1101601
which tells me to replace my bootloader with a gingerbread bootloader through ezodin, then boot into recovery mode which is the custom cwm recovery, and from there straight up install my rom that was placed in the sd card, and walla i get my MIUI. I assume that the bootloader will give me CWM recovery because the guide doesnt tell me to get it through rom manager. I currently have the base google stock recovery, so question <1> do i have to install cwm recovery through rom manager first or will the gb bootloader give it to me once flashed? and question <2> i've tried to install it through rom manager but it didnt work the first try (i chose my phone model as the S) and even erased all my apps and data :S Is there a way to go around installing clorkworkmod? I understand my phone isn't EXACTLY Galaxy S, but they're similar...
Also, another problem i face is that i DON'T have the 3 button shortcut to recovery mode or download mode. I'm following this tutorial to try repair it, since I've heard a batch of Samsung galaxy s have flawed recover and download modes that can't be accessed by the 3 buttons. since the two phones were released around the same time, it could be that the galaxy beam was affected also. Everything is fine going through this tutorial (even getting to download mode trough ADB is fine), problem is i get stuck every single time in ODIN at SetupConnection. Question <3> any freaking idea how to solve this? I've gone through google and searched through this forum... Now i don't know what to do and don't dare try anything else or other flashing unless i fix this 3 button shortcut because i know i can only access recovery or download through ADB REBOOT RECOVERY / DOWNLOAD and the phone has to be plugged in, turned on, booted into android, and in usb debug mode. the ADB command won't work if the phone is off and i'm worried the GB bootloader will stop eclair from loading.
This leads to the question <4> if i decide not to follow this repairing tutorial and just flash the gingerbread bootloader up front, will it give me the 3 button shortcut boot? because if i am not able to load the eclair rom with gingerbread bootloader, and have no 3 button shortcut, i will not be able to boot into recovery to install rom and wipe data and cache etc. Also, if i flash the gingerbread bootloader, can i still load into my stock eclair rom? If i can load into the stock eclair rom, then i don't need the 3 button shortcut, i can go straight to doing usb debug and the ADB command again after flashing bootloader and rebooting to go straight into recovery and installing MIUI.
Question <5> What about gingerbread bootloaders that can backtrack and load froyo roms and eclair roms? Do these exist? Where to download? If so, i can load into my eclair rom and use ADB for recovery mode, eliminating the step: repairing the 3 buttons.
Question <6> Also, i noticed the guide didn't speak anything about kernels etc. From what I understand about kernels, it is the architecture or system between the hardware and the software. People can tweak kernels (leading to custom kernels) for different and maybe even better sound and video etc right? But the guide doesn't say anything about installing a custom kernel, so am i supposed to keep my current Zues kernel from Samsung, or is a custom kernel recommended by MIUI ALREADY provided in the zip folder i downloaded from here? (the I9000 one) When i flash this zip through CWM recovery, is the kernel changed together? Does this apply for the bootloader also? Is the bootloader supplied in the zip and flashed together at the same time? if everything, (rom kernel bootloader) is flashed together at the same time then i can eliminate many steps and just work on installing CWM recovery through rom manager. then use adb to boot into recovery and flash that one simple MIUI zip. no need for 3 button boot...
Question <7> Is there another way to get MIUI to install on my device without so much hassle? haha..
Thanks for the trouble, I know it's a lot of questions... Please answer whatever you can
umm, almost a 100 views... but no replies? :'(
I'd never heard of it until this post, I looked at some specs and they're quite significantly different to the SGS's ones, smaller screen and completely different processor(which is most important(TI OMAP 3440 720MHz in the Beam and Hummingbird S5PC110 in the SGS)). It's a completely different phone, don't even try to install MIUI for the I9000 on it unless you don't mind your phone being in a bricked state. I may not be right but it's my strong opinion. Here is the Xda wiki for it: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Beam Which shows how to root and then OC it which may increase performance. And if you like the Miui look there is a look a like launcher floating round if you search. Good luck
true, they aren't exactly the same. the processor is definitely different, but i think MIUI was made for performance, which fits well with this lousy processor haha. screen shouldn't be a problem, most softwares fit to screens automatically. I've already Rooted and OC'ed it but its still slow.
Is there any way to flash everything at once, e.g. kernel rom everything flash together at the same time using ODIN, then maybe i will reboot and see if the MIUI works... The problematic part is the 3 buttons download mode. I'm willing to flash everything at once then see if i'm lucky and MIUI will work for me. I'm not willing to flash just kernel or etc, then can't get in to download mode already because phone cant be booted, thus cannot install ROM...
Does anybody know exactly what when flashed into the phone gives me the 3 button recovery and download...?
I also realised something in the wiki link u gave me...
Power+Menu+Volume Down -> Soft Reset
Power+menu+Volume Up -> Ready for Flash Screen
Could this be my recovery and download...? I'll try later.
I'll try and give you an example, the Galaxy SL or the I9003 came out the start of this year as a replacement for the original with the only difference being the chipset and display type. Quite a few people have got this phone and have being trying to get Miui to work on it hasn't happened. The I9000 kernel for Miui is made for the I9000, it only works with the Hummingbird chipset, end of story. I'm not stopping you from trying but expect the most likely consequence to be the phone dead, not running Miui.
Wow, if the I9003 which was even closer (spec-wise) to the I9000 can't flash I9000 MIUI, then my I8520 won't make it... :'( I understand what you mean, any kernel made for I9000 phones, even custom user-made ones, only work with specific hardware, like that chipset, unless that kernel some how is clever enough to work with my hardware, or probably just lucky enough to be compatible with my chipset.
I didn't know the software had to confirm so tightly to the hardware... I'd always thought software would automatically work with basic hardware, albeit there would be some issues and glitches, but at least it would still work. I thought maybe it would be possible to keep my Zues kernel, and just flash the rom, and let the rom use my kernel.. It wouldn't be very optimised because they weren't made for each other, but at least with a few bugs, still usable... But now I know my Zues kernel works with my hardware but probably wont work with I900 MIUI unless it was coded for my phone... Though, if my phone does have the same chipset and gpu, maybe it will work?
Seems like I'll have to continue to use this lousy unsupported phone :S
Thanks for your help
Good day all.
Before I ask my questions I would like to say that In the few days I have been here I have been working on Understanding the Technical terms and Jargon this site uses ever so much, I have learned.
While the wiki (and these posts here) has helped a bit...I still find myself feeling a bit nauseous from what I have been currently been unable to understand so you might have to stand me being a noob for just a little bit longer I'm afraid.
Anywho...on to the questions...
I am aware the ROMs must match a given make and model of a phone to work and custom kernels must be matched to specific ROMs, but alot of these ROMs have really awesome features & improvements. Better Sound, DSP-equalizer, More efficient battery use, more function UIs, more control on security, SONY based Engines, CRT-Off Animations, ...why can't they all just work together?!?! So now I have to ask the crazy...
Is it possible to stack the features of different ROMs?
What is it I need to be looking for compatibility wise between all these ROMs/Themes/Apps/Kernels to make sure that I don't Clay or Brick the Note by combining the wrong codes?
I'm trying to figure out what I can do to mix and match intelligently to get the most out of a rooted note (as is... I suppose... all of you here).
On that...uh...note, I have seen a lot of talk about Titanium-backup App, Clockworkmod Recovery App & Nandroids.
Why do I need to use these to back up?
Why can't I just go into the phone & copy and paste all the files on a folder in the computer? Is it because Android is Linux based? Do not all the files show?
Should I have all these Backup Apps to back up every part of the Note or is just one enough?
Oh and one more thing... I Received my note today & a lot faster than I expected. So...
What would you recommend to be the smartest thing to do first after root?
Decisions Decisions.
Thank You
The most basic differentiating factor is to see if the ROMs are TouchWiz based or AOSP/CM/AOKP based, those are the main 2 categories that every ROM here falls under
Features from one category *mostly* can not be ported to other category if they are not present there. For example, S-Memo are exclusive to TouchWiz ROMs just like Tablet mode is exclusive to AOSP/CM/AOKP ROMs, but there might some rare exceptions
IMHO Titanium Backup is useful only if you have games data, normal apps I prefer to set them up manually to have the cleanest setup possible. Nandroids, OTOH, are essential, they are your safety net if anything goes wrong.
You can't back up an OS just by copying the files over cause you don't have access to the kernel and lower system files, that's where nandroids help
Hope this helps
matius44 said:
The most basic differentiating factor is to see if the ROMs are TouchWiz based or AOSP/CM/AOKP based, those are the main 2 categories that every ROM here falls under
Features from one category *mostly* can not be ported to other category if they are not present there. For example, S-Memo are exclusive to TouchWiz ROMs just like Tablet mode is exclusive to AOSP/CM/AOKP ROMs, but there might some rare exceptions
IMHO Titanium Backup is useful only if you have games data, normal apps I prefer to set them up manually to have the cleanest setup possible. Nandroids, OTOH, are essential, they are your safety net if anything goes wrong.
You can't back up an OS just by copying the files over cause you don't have access to the kernel and lower system files, that's where nandroids help
Hope this helps
Click to expand...
Click to collapse
Oh! Right... I'm not just backing up apps... I'm backing Up the OS. Duh. Ok.
I was thinking about it the wrong way.
I know what a TouchWiz ROM is, and its good to know that Tablet mode is exclusive to AOSP/CM/AOKP ROMs, I didn't know that either. As I mentioned in my post... I'm still working on the Jargon here. What does "AOSP/CM/AOKP" Mean? Can I switch around features if I kept in those respective types of ROMs?
CrazyOGuy said:
Oh! Right... I'm not just backing up apps... I'm backing Up the OS. Duh. Ok.
I was thinking about it the wrong way.
I know what a TouchWiz ROM is, and its good to know that Tablet mode is exclusive to AOSP/CM/AOKP ROMs, I didn't know that either. As I mentioned in my post... I'm still working on the Jargon here. What does "AOSP/CM/AOKP" Mean? Can I switch around features if I kept in those respective types of ROMs?
Click to expand...
Click to collapse
AOSP is "Android Open Source Project". That is just one kind of custom ROM. Also, several ROMs on here are built on "AOSP", meaning they use AOSP as a base and add "features" to it.
CM is "CyanogenMod". They are a very popular team that builds custom ROMs for different phones out there. Same thing applies, people will builld custom ROMs based on CM9 (which is Ice Cream Sandwich based) and add their own "features" to it. CM7 is Gingerbread based and not on the Note.
Also, read about the bricking situations, just to wrap your head around it and stay safe. Basically, just know right now that the only "safe" kernel is the CM9 kernel built by xplodwild OR the DAFUQ kernel built by Entropy.
The ICS sources have come out so we should see more kernels come out as the devs get their hands dirty.
I use Titantium Backup, personally, to back up my individual apps and such when I switch ROMs. Now, of course, if you restore apps, you might run into problems and you might need to wipe data again and start over and not restore apps. But, I RARELY have problems.
I hope all these details help!
CrazyOGuy said:
Oh! Right... I'm not just backing up apps... I'm backing Up the OS. Duh. Ok.
I was thinking about it the wrong way.
I know what a TouchWiz ROM is, and its good to know that Tablet mode is exclusive to AOSP/CM/AOKP ROMs, I didn't know that either. As I mentioned in my post... I'm still working on the Jargon here. What does "AOSP/CM/AOKP" Mean? Can I switch around features if I kept in those respective types of ROMs?
Click to expand...
Click to collapse
AOSP = Android Open Source Project = Google's pure android
CM = CyanogenMod
AOKP = Android Open Kang Project
Features theoretically can be ported between these, but it requires hackery skills since mostly it's framework dependant
For example, AOKP is famous with its ROM Control option in Settings menu, this is not present in AOSP at all and some of it is present in CM9. If you have good knowledge in code you can port, not very easy task
CrazyOGuy said:
What would you recommend to be the smartest thing to do first after root?
Click to expand...
Click to collapse
There are things that need to be done before the root. You need some basic tools to get into the business of flashing stuff.
1. PC Odin - that's a software for flashing firmware from your Windows. You can get it here. Top left hand corner of the first post.
2. Windows drivers - they are needed so your PC can recognize the phone once connect the two. Get it from the same URL, same place.
3. Mobile Odin Pro - basically does the same functions as PC Odin, but from your Note, not from the PC. Get the Lite version
if the Playstore doesn't let you buy the Pro one.
4. Titanium Backup - this is optional. I use it all the time with no trouble, but some prefer to re-install their apps manually after they switch to another Rom. Titanium allows you to backup all your apps and their data, and does a quick batch restore when you need it.
Now about the rooting matter.
I would recommend the following method:
http://forum.xda-developers.com/showpost.php?p=25285584&postcount=3
I think it is by far the easiest and quickest one.
After you are successfully rooted, come back here, report, and we'll take it from there, OK?
We won't be going anywhere.
P.S. If you get into bootloop after the PC Odin has finished the flash, don't panic, but read this:
http://forum.xda-developers.com/showpost.php?p=26460335&postcount=4
chasmodo said:
There are things that need to be done before the root. You need some basic tools to get into the business of flashing stuff.
1. PC Odin - that's a software for flashing firmware from your Windows. You can get it here. Top left hand corner of the first post.
2. Windows drivers - they are needed so your PC can recognize the phone once connect the two. Get it from the same URL, same place.
3. Mobile Odin Pro - basically does the same functions as PC Odin, but from your Note, not from the PC. Get the Lite version
if the Playstore doesn't let you buy the Pro one.
4. Titanium Backup - this is optional. I use it all the time with no trouble, but some prefer to re-install their apps manually after they switch to another Rom. Titanium allows you to backup all your apps and their data, and does a quick batch restore when you need it.
Now about the rooting matter.
I would recommend the following method:
http://forum.xda-developers.com/showpost.php?p=25285584&postcount=3
I think it is by far the easiest and quickest one.
After you are successfully rooted, come back here, report, and we'll take it from there, OK?
We won't be going anywhere.
P.S. If you get into bootloop after the PC Odin has finished the flash, don't panic, but read this:
http://forum.xda-developers.com/showpost.php?p=26460335&postcount=4
Click to expand...
Click to collapse
I did all that Pre-Root stuff two days ago. ☜(゚ヮ゚☜) YEAAAA!
As for how the root went...so far so good. As such I've just been upgraded from noob to kiddie hacker. Yay me...I guess.
I also did go for Titanium-backup App & Clockwork mod Recovery App (Free). Could not find Nandroid.
I am currently on 2.3.6 GB.
With that said. Now comes the fun part(...right?)
If you have done just what cursed4eva did in his video, you are rooted, but still haven't got a proper CLockWorkMod Recovery for further flashing.
If that is the case, you need to go to Chainfire's kernel thread and download the matching CF-Root kernel. For instance, download CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5.zip if you have flashed N7000XXLC1_N7000OXALC1 Open Europe.
You need to extract the kernel zip to get the tar file inside. Put that tar file on your SD card, start Mobile Odin, tap on 'kernel' option, navigate to the kernel tar and flash. The phone will reboot, MO will flash the kernel, and you'll have the fully functional CWMR you need for doing nandroid backups/restores and flashing custom Roms.
Sorry for the Delay. Micro-SD Card took longer to receive than expected.
I have gone in and put that matching LA# .tar file on Moble ODIN. At the risk of asking a question whose only answer can be "DUH!"...
To flash the Kernel (or any of the respective things Mobile ODIN can do) do I press "Flash Firmware"?
My Concern of Bricking > Risk of asking Stupid Obvious Question
Edit: Every single place I searched presses said button...so I guess that's a yes. >_<
Edit 2: Success!
So how are the names given? Is all I need to look for is just match random bits of the titles code to see if the two are compatible?
And with this done...I can now start with some of the fun stuff... right?