[Q] General questions regarding rooting, unlocking, flashing on a Samsung - Verizon Samsung Galaxy S III

This is my first Samsung phone - had an HTC incredible, then a motorola bionic. I'm a veteran regarding flashing, rooting, etc - but, as many of you know, each device has it's own nomenclature and quirks - so, I'm getting my feet wet. I familiarized myself but had a couple more questions.
I followed this thread first:
http://forum.xda-developers.com/showthread.php?t=1974114
Decided to install latest leaked image - then rooted and unlocked and flashed TWRP. No issues, works great. This had me on VRBMA2.
I got squirrley for a new experience - only took me maybe 24 hours - so, decided to flash a ROM or two. Stuck with stock ROMs based off VRBLK3, CleanROM and Synergy. Both flashed fine, no big issues. I did note however that baseband still read VRBMA2. Because I've had the Bionic for so long with it's *$*%*$* locked bootloader, the idea of flashing custom kernel's and radios is foreign to me. I PRESUME, the baseband is the radio, but I don't know. I realized it was probably ideal to have the VRBLK3 baseband, but, since it was still JB, figured SHOULD be ok. Which it was in general, but, I wasn't sure - so I went back to stock via openyoureyes thread above.
So
1. Can someone clarify the importance of matching the baseband with what the ROM is based off of? How does this relate to non-stock ROMs? i.e. AOSP, AOKP, CM. I'm 99 % sure I've read that the ROM does not modify the baseband or the kernel.
(( 2. openyoureyes files do not modify data (I presume he means data folder with system apps). If I wanted to go back to square one - I presume the image files that he has 'hidden' and warns about using are the original image files to flash via ODIN if I want stock stock. (analagous to an SBF or FXZ file in a motorola device. He just has such serious warnings I wanted to be sure.
** Answered question 2 myself via here -- http://forum.xda-developers.com/showthread.php?t=1762709 section 5 *** ))
Thanks in advance. I love this phone and am having fun learning another device.

MrRedPants said:
This is my first Samsung phone - had an HTC incredible, then a motorola bionic. I'm a veteran regarding flashing, rooting, etc - but, as many of you know, each device has it's own nomenclature and quirks - so, I'm getting my feet wet. I familiarized myself but had a couple more questions.
I followed this thread first:
http://forum.xda-developers.com/showthread.php?t=1974114
Decided to install latest leaked image - then rooted and unlocked and flashed TWRP. No issues, works great. This had me on VRBMA2.
I got squirrley for a new experience - only took me maybe 24 hours - so, decided to flash a ROM or two. Stuck with stock ROMs based off VRBLK3, CleanROM and Synergy. Both flashed fine, no big issues. I did note however that baseband still read VRBMA2. Because I've had the Bionic for so long with it's *$*%*$* locked bootloader, the idea of flashing custom kernel's and radios is foreign to me. I PRESUME, the baseband is the radio, but I don't know. I realized it was probably ideal to have the VRBLK3 baseband, but, since it was still JB, figured SHOULD be ok. Which it was in general, but, I wasn't sure - so I went back to stock via openyoureyes thread above.
So
1. Can someone clarify the importance of matching the baseband with what the ROM is based off of? How does this relate to non-stock ROMs? i.e. AOSP, AOKP, CM. I'm 99 % sure I've read that the ROM does not modify the baseband or the kernel.
2. openyoureyes files do not modify data (I presume he means data folder with system apps). If I wanted to go back to square one - I presume the image files that he has 'hidden' and warns about using are the original image files to flash via ODIN if I want stock stock. (analagous to an SBF or FXZ file in a motorola device. He just has such serious warnings I wanted to be sure.
Thanks in advance. I love this phone and am having fun learning another device.
Click to expand...
Click to collapse
Welcome to the SGS3 :good:
1. Yes, baseband = radio. Any baseband can go with any rom (AOSP or TW). They are separate and not interrelated. I tend to keep mine flashed to the current newest, but use whichever one gives you best reception in your area. It's very subjective and what works for me may not be what works best for you. Flash away
2. The data he talks about is the /data/app folder (all the user apps you have installed from the Play store or otherwise) and the /data/media folder (your internal SD card). All the system apps (camera, contacts, email, phone, etc) are in the /system/app folder, which is part of the /system partition that gets overwritten when you flash the images in his thread. To go back to stock stock, as you put it (stock recovery, unrooted, locked bootloader), look at Section 5 in the OP here.
The difference between the openyoureyes files and the ones in droidstyle's is that droidstyles wipes your internal SD (you lose everything on the internal sd - it doesn't touch the external sd) and openyoureyes does not wipe the internal.
Hope that helps.

MrRedPants said:
So
1. Can someone clarify the importance of matching the baseband with what the ROM is based off of? How does this relate to non-stock ROMs? i.e. AOSP, AOKP, CM. I'm 99 % sure I've read that the ROM does not modify the baseband or the kernel.
Click to expand...
Click to collapse
Welcome aboard!
Basically there isn't any importance with matching your baseband with your rom. Just use whichever you think improves your signal the best. Fyi, you may see these terms thrown around a lot so to clarify: baseband = radio = modem. Your baseband is not flashed when you flash custom roms which is why you saw it stay the same. It will change if you Odin flash a stock rom.
2. openyoureyes files do not modify data (I presume he means data folder with system apps). If I wanted to go back to square one - I presume the image files that he has 'hidden' and warns about using are the original image files to flash via ODIN if I want stock stock. (analagous to an SBF or FXZ file in a motorola device. He just has such serious warnings I wanted to be sure.
Thanks in advance. I love this phone and am having fun learning another device.
Click to expand...
Click to collapse
What you'll want to look out for is whether the stock rom tar will format /sdcard. Open1your1eyes0 has hidden those in his thread I believe. At this point, each of the primary threads that contain Odin specific stock tar detail whether flashing them wipes /sdcard or not. With /sdcard being your internal storage, most user data is stored at /sdcard/data. You're external sd card will not be wiped when using a full wipe Odin tar.
Also, anything ending in ".tar" or ".tar.md5" is flashed only with Odin.
Sent from my SCH-I535 using xda app-developers app

Related

[OLD] Outdated MIUI Thread

UPDATE: This ROM is now outdated. Please use Dfgas's newer MIUI port, located here:
http://forum.xda-developers.com/showthread.php?t=1152518
Original Post:
You've watched. You've waited. You've sat impatiently looking for an update. I know I have. The wait is over.
Gingerbread AOSP MIUI 1.6.24 MTD Port
Ported to: Mesmerize (still having issues with Showcase port)
Please note: The 1.6.24 links currently posted are not my work! I just couldn't correct the eri.xml in framework-res.apk to remove "Verizon Wireless" from the top bar (cosmetic I know, but it bugged me--I'm picky like that), and... BDE sorta had his port done several hours before mine anyway. I can't take any credit whatsoever for these links, this is all his porting work.
WARNING: READ BEFORE FLASHING!!
This ROM was designed using the newer (for us) yaffs2/ext4 filesystem. Excepting CM7MTD, no other ROM uses this filesystem. As a result, this ROM uses CWM 4, and once you flash, you CANNOT flash any other ROM from Recovery. Should you have issues with the flash, or want to return to a different non-MTD ROM, you will need to Odin all the way back to stock. See post #2 for instructions.
SHOWCASE USERS: This is especially critical for Showcase users, as Cell South has prevented Odin flashing packages for the Showcase. IF YOU USE A CELLSOUTH SHOWCASE AND WANT TO FLASH BACK TO A DIFFERENT ROM, FIND A WORKING ODIN PACKAGE FIRST.
As always, the standard warning applies: I am not responsible for what may happen to your phone as a result of flashing this ROM, properly or improperly. No warranty whatsoever. You have been warned.
Credits
The biggest thanks go out to jt1134. NONE of this (including CM7MTD) would be possible if it weren't for the work he's done for the Fascinate, Mesmerize, and Showcase.
Andmer has also been critical to making this happen. He was the one to take JT's work, use his AOSP source, and build a working MIUI port for the Fascinate. Both he and JT continue to modify the ROMs and Kernels for MTD that we enjoy to work towards getting that hardware working.
Without these guys, there would be no port for us.
I'd like to thank lmartin92 for his tremendous help and knowledge. He worked tirelessly with me to get this working. Similarly, bdemartino has been a huge help in all around, as well specifically making sure we could get the "fascinatemtd" SMS padding code implemented into CM7MTD, and therefore MIUI MTD. Lastly, I'd like to thank Akellar for getting some Framework-res cosmetic edits working when I could not.
1.6.24 Note: Again, these are actually BDE's ports, not mine, I can't take any credit.
ROM Details
Update Schedule: MIUI receives weekly official updates, and Andmer has said he intends to port them to the Fascinate on that same schedule. I intend to port from his work on that same schedule, and once my overlay is fully worked out, it should take me only as long as it takes to apply it and upload. This thread will be updated every time a new ROM is released. I'll try to keep one or two previous week's ROM links just in case.
Radio: This ROM does not flash a radio, so it should use whatever radio you had before you flashed. This ROM is built for a Mesmerize/Showcase radio (making it an actual Mesmerize port), so if you're using the Fascinate EC01 radio, you'll want to either flash the EC10 or EE19 radios (typically by flashing the stock versions of those ROMs). Don't worry if you flash those ROMs; everything else (except the radio) will get overwritten.
Recovery: In order to support the yaffs2/ext4 filesystem, this ROM uses CWM 4. As a result, the normal "three finger Recovery" method does not work. Similarly, although the ROM includes a "Reboot into Recovery" menu option after holding power, that does not boot into recovery. The only method of getting into recovery at this point is to either use ADB or a Terminal Emulator app.
Within Terminal Emulator, type the bolded, underlined text:
su (enter; this grants SuperUser rights to Terminal Emulator)
reboot recovery (enter)
This should properly reboot the phone into Recovery mode.
Working:
Calls
Bluetooth!!
3G / Data
WiFi
SMS
Camera/Camcorder!!
USB mass storage / sdcard
GPS
ALL Sensors!!
Not Working/Known Issues:
MMS
Calls/SMS during deep sleep mode are not waking up the device to ring.
This app will prevent your device from deep sleep which is of course a battery drain, but you will receive calls. Whether its worth it or not is up to you.
https://market.android.com/details?id=otis8.softlocker
How to Flash
Copy the ROM to your SDcard.
Reboot phone into recovery, flash ROM as normal.
Make sure to wipe data, cache, and dalvik cache if you are coming from a non-MTD ROM, and possibly even CM7MTD.
Flash MIUI ROM from SD card.
The "MIUI" branded flash script will appear, and quickly disappear. THIS IS NORMAL. This verifies if CWM 4 is installed (on the first time through it will not be), and if not, installs it. The phone should reboot once again into recovery, but it will be standard CWM 4 Orange recovery.
Flash the ROM from your SD card once more. Note that the softkeys have changed; use the Search key as "Enter". The flash should proceed as normal.
1.6.24.1: Flash the 1.6.24.1 patch to correct all sensors.
Reboot phone when complete.
When your phone reboots, you should see the normal Samsung logo, and then a Galaxy S/CyanogenMod 7 logo. This will be followed by the MIUI.us boot screen, which is a moving starfield with a spinning globe.
Welcome to GB MIUI!
Mesmerize Download
http://olvisfoundation.com/xdadump/bdemartino/ROMS/MIUI/MIUI.us_mesmerize_1.6.24.1_Eng_Deo_ZipA_Signed_0627.zip
Showcase Download
((Still broken))
1.6.24.1 Patch Download - Fixes ALL sensors! (for both Mesmerize and Showcase, once later is released)
http://olvisfoundation.com/xdadump/bdemartino/ROMS/MIUI/MIUI.us_patch.zip
HOW TO GO BACK TO NON-MTD ROMS
Kanged from the Fascinate forums with immense thanks to kidserious, and referencing the "Files to get your Mesmerize back to stock 2.1 and 2.2.1" guide from Phidelt82
Things you'll need:
Odin
Working Odin package for your phone model
If you don't already have these, here are some links (sorry, Mesmerize stock ROM only):
Odin: http://download1422.mediafire.com/ii578172dylg/429fcpdtpckkcea/Odin3+v1.83.exe
EC10 Odin Package: http://www.megaupload.com/?d=N6JNT1ZE
Whatever Odin package you use must have a full bootloader included in the flash. EC10 should work, EE19 may not. I'm unable to advise which Showcase Odin package would work, I'm not familiar enough and they're not generally available.
STEP-BY-STEP
I'm writing these for the Odin newbie in mind. Experts, as long as you check "Repartition", you know the drill.
Open Odin. This does not need to be installed, simply run.
Pull off the back from your phone, remove the battery.
Connect the USB cable (best with the Samsung one that came with your phone), and hold Volume Down until you see the phone say "Download Mode". A little box should turn Yellow in Odin, signifying it detects the phone and is ready to flash it.
Click the PIT button. Locate the path to the PIT file extracted from the ZIP you downloaded above (or previously) to populate that field.
Click on the PDA button. Locate the path to the TAR.MD5 file extracted from the ZIP you downloaded above (of previously) to populate that field. Do NOT click on PHONE, Phone should be empty.
Make sure Re-Partition is checked. We want to overwrite the previous MIUI flash, and Re-Partition is what lets us do that fully.
Click the Start button. Let it proceed through the whole flashing process, which is approximately 10 minutes. You'll see "Complete!" in Odin and your phone's screen will go blank once it's finished.
For thoroughness' sake, I'm including the below steps. Again, experts could potentially circumvent, but below is the failsafe way.
Re-insert battery, boot phone. Allow it to boot into Blue (stock) recovery. it's okay if it says it can't mount "HIDDENSDCARD"; it's done the rest of the setup it needs to. If you're just staying with the stock ROM and recovery, you're done.
If you want a custom recovery:
Follow steps 1-7 above, skipping over step 4 (no PIT file needed), and flash your recovery of choice. You should now be able to flash whichever custom ROM you were on before, or restore from a Nandroid backup.
It is absolutely mandatory that you follow these steps exactly to properly get off of GB MIUI MTD (or CM7MTD for that matter) so that you can flash another ROM. Attempting another method or not following these steps implicitly will result in a bricked phone and you will have to follow this guide to fix it.
#3 reserved for me also.
Good for you man. Way to go!!!!!!
Tap-a-Talked from my Mesmerize
is there anyway u could port the cm7 releases to id really love to be running cm7 instead of having to flash fascinate radios and all tht crap..
Outstanding.
I'd love to test on my showcase. I have everything I need to go back via odin, and this is the rom I've been waiting for.
Congrats man, I know how much time/effort you put into this!
Sent from my SCH-I500 using XDA App
O and thx my pants are wet now good rom
Sent from my SCH-I500 using XDA App
hold of on tht keeps boot looping on the miui bootupscreen any thoughts?
I got the same thing, but I think it's because I forgot to wipe data/cache/whatever... So I'm trying again.
Edit:
Yeah, it's just looping the spash.
Im also getting boot loop. Im on the ee19 radio, should i do the 10 and retry it?
i tryed both and it bootlooped
godofwar762 said:
i tryed both and it bootlooped
Click to expand...
Click to collapse
That makes me very worried about flashing this.. I was just going to do it.
I wonder if flashing to the cm7 then trying to flash this would work better. Using the cm7 you can use rom manager to install the miui, so im gonna try that.
Edit: Unfortunately same thing that route also. Boot loop
That's what I came from, then the second time I went from the latest offical froyo.
seishuku said:
That's what I came from, then the second time I went from the latest offical froyo.
Click to expand...
Click to collapse
With no issues?
It did the same thing.
Well imma go try it ill report back when I'm done.
Are you guys flashing the Rom twice like the op says to?
Sent from my SCH-I500 using XDA App

Why flash custom Roms?

Can a kernel be flashed without a rom and vice versa?
Does it erase all saved data to flash a kernel? A rom?
The designations KD1, KB5, KJ6, wtf do these represent?
What is firmware version 2.2.1? Does this dictate what kernels/roms will work?
My phone came stock with
Baseband version: T959VUVKD1
after an unsuccessful root, it now it has
Baseband version: T959VUVKB5
What's the difference? Is my new one better?
My kernel is now 2.6.32.9
Wasn't stock kernel 2.2.1?
Why bother switching kernels/Roms in the first place? It seems like it's just a big headache. Launcher apps seem to provide more customization then alternate Roms. What gives?
Thanks in advance, this may seem noob but I find it hard just finding BASIC information sometimes.
I've spent a LOT of time dicking around with this new phone (my first smartphone) and I love the fact that it is customizable it but it takes up too much time to have to read up on everything, flash, then re load all my icons, screw that. I just want to know what is the best, fastest, simplest, most customizable rom/kernel combo up front, or I'm going back to stock, I have to believe that they designed the stock OS around the phone to maximize effectiveness.
Thanks in advance
Alot of questions but I'll attempt to answer them. Disclaimer though, I havent been on these forums for that long so my answers may not be correct and I wont be held responsible for incorrect info.
Farlander said:
Can a kernel be flashed without a rom and vice versa?
Does it erase all saved data to flash a kernel? A rom?
Click to expand...
Click to collapse
Yes a kernel can be flashed without a rom, but roms come with kernels already on them. When flashing a kernel, data on you're device is kept, but not vice versa.
The designations KD1, KB5, KJ6, wtf do these represent?
Click to expand...
Click to collapse
They are versions. They are labeled in alphanumeric order. Example, KB5 is the oldest of the three, KD1 is newer, and KJ6 is the newest (and the newest kernel at the moment for this phone as well).
What is firmware version 2.2.1? Does this dictate what kernels/roms will work?
Click to expand...
Click to collapse
2.2.x are Froyo (Frozen Yogurt) versions. 2.3.x are Gingerbread versionss with the Gingerbread bootloaders that are needed to flash most roms on here with Clockwork Mod (CWM).
General Android Knowledge:
Cupcake < Donut < Eclair < Froyo < Gingerbread (GB) < Honeycomb < Icecream Sandwich (ICS)
My phone came stock with
Baseband version: T959VUVKD1
after an unsuccessful root, it now it has
Baseband version: T959VUVKB5
What's the difference? Is my new one better?
Click to expand...
Click to collapse
Well "better" is relative, but it is indeed older. Also, try using the new SuperOneClick to root next time if you haven't.
http://forum.xda-developers.com/showthread.php?t=803682
My kernel is now 2.6.32.9
Wasn't stock kernel 2.2.1?
Click to expand...
Click to collapse
I'm noob so idk how to answer this.
Why bother switching kernels/Roms in the first place? It seems like it's just a big headache. Launcher apps seem to provide more customization then alternate Roms. What gives?
Click to expand...
Click to collapse
Custom ROMs can add features, take away bloatware (relatively useless programs that come preloaded with the phone), and provide functional inprovements (such as KJ6's better WiFi reception.
Thanks in advance, this may seem noob but I find it hard just finding BASIC information sometimes.
I've spent a LOT of time dicking around with this new phone (my first smartphone) and I love the fact that it is customizable it but it takes up too much time to have to read up on everything, flash, then re load all my icons, screw that. I just want to know what is the best, fastest, simplest, most customizable rom/kernel combo up front, or I'm going back to stock, I have to believe that they designed the stock OS around the phone to maximize effectiveness.
Thanks in advance
Click to expand...
Click to collapse
You may just want to just follow this guide for now:
Then after which, use SuperOneClick (SOC) to root
After you get yourself situated here, then move on to bigger and better roms such as RaverX3X's Octane:
http://forum.xda-developers.com/showthread.php?t=1305145
or Somairotevoli's 2.3.6 Debloated SimplySimple:
http://forum.xda-developers.com/showthread.php?t=1321611
Be sure to always follow the OP's Instructions to the T. For example, when wiping or mounting.
And UMMU mounts means in CWM under mounts set them to:
Unmount
Mount
Mount
Unmount
Hope this helped
Oh also, if all else ever fails when attemoting to flash a ROM, try the method found here:
http://forum.xda-developers.com/showthread.php?t=1223765
Farlander said:
Can a kernel be flashed without a rom and vice versa?
Does it erase all saved data to flash a kernel? A rom?
The designations KD1, KB5, KJ6, wtf do these represent?
What is firmware version 2.2.1? Does this dictate what kernels/roms will work?
My phone came stock with
Baseband version: T959VUVKD1
after an unsuccessful root, it now it has
Baseband version: T959VUVKB5
What's the difference? Is my new one better?
My kernel is now 2.6.32.9
Wasn't stock kernel 2.2.1?
Why bother switching kernels/Roms in the first place? It seems like it's just a big headache. Launcher apps seem to provide more customization then alternate Roms. What gives?
Thanks in advance, this may seem noob but I find it hard just finding BASIC information sometimes.
I've spent a LOT of time dicking around with this new phone (my first smartphone) and I love the fact that it is customizable it but it takes up too much time to have to read up on everything, flash, then re load all my icons, screw that. I just want to know what is the best, fastest, simplest, most customizable rom/kernel combo up front, or I'm going back to stock, I have to believe that they designed the stock OS around the phone to maximize effectiveness.
Thanks in advance
Click to expand...
Click to collapse
I'll do my best to answer this; hope I don't skip anything
Can a kernel be flashed without a rom and vice versa?
- The kernel is a traffic cop. It is what controls the underlying hardware in your phone, on your tablet, or on your PC. It handles things like memory management and allocation, access to hardware, process scheduling, and much more. You can flash a kernel onto an existing ROM (for example, Gingerbread VUVKG4 ROM with a modified KG4 kernel that has root access). The kernel you flash replaces the one that's already there. When you flash a ROM, it has a kernel already in it.
Does it erase all saved data to flash a kernel? A rom?
- Generally flashing a kernel does not wipe any of your data as you're only replacing the kernel. Flashing a ROM can wipe your data; it really depends on what you're flashing. It's always good practice to make a backup before flashing unless you've nothing on the phone to lose. Flashing a ROM that does wipe your data will not wipe the contents of your sdcard, it wipes the /data and other partitions on the phone's internal memory/storage.
The designations KD1, KB5, KJ6, wtf do these represent?
- Versions. Generally ROMs for our model of phone (Galaxy S 4G, SGH-T959V) have a name like VUVKB5, VUVKD1, or VUVKJ6. The last two characters correspond to a certain build/version number. The more recent the last two characters the more recent the build. The builds for our phone were on 2.2 (Froyo) through KD1 then went to 2.3 (Gingerbread) starting with KF1. Gingerbread required updated boot loaders for the phone. Without the proper boot loaders the phone wouldn't work.
What is firmware version 2.2.1? Does this dictate what kernels/roms will work?
- 2.2.1 is Froyo. It's a version of the Android operating system (OS). It does not dictate what will work, per-se. Rather it's telling you what version of the OS your phone is currently running. If you were to try and flash something, say a kernel, you'd definitely need to know what version you are on so that you flash a kernel/ROM for that version. You can upgrade to newer ROMs, though, say to go from 2.2.1 (KD1) to 2.3.6 (KJ6). You just have to make sure you have all of the right pieces in place first.
My phone came stock with
Baseband version: T959VUVKD1
after an unsuccessful root, it now it has
Baseband version: T959VUVKB5
What's the difference? Is my new one better?
- The "new" one is actually older, which means it is missing bug/performance fixes and the like.
My kernel is now 2.6.32.9
Wasn't stock kernel 2.2.1?
- Confusing, isn't it? The 2.6.32.9 is the kernel version & 2.2.1 is the ROM version. When you upgrade ROMs there's a good chance the kernel version will change, too, but not necessarily. They are independent numbers but kernels/ROMs are dependent upon one another. Clear as mud, right?
Why bother switching kernels/Roms in the first place? It seems like it's just a big headache. Launcher apps seem to provide more customization then alternate Roms. What gives?
- It's a personal preference most of the time. You could upgrade to the latest release ROM by Samsung which is VUVKJ6 using their Kies Mini software. It's Gingerbread based, faster, better battery life, wifi is a little weaker. Just make sure you backup any information you want to keep first. I generally keep my contacts synched with T-Mobile or Google and after a data wipe they sync back to the phone.
As for flashing custom ROMs you'd have to read up on the different ones to see if they interest you. Some increase performance, some have mad themes wrapped up in them, some have better battery life, some do their best to roll all of that up into them.
In short, you don't have to flash anything. The development community here enjoys doing it though despite what headaches it might bring. It enables us to hack/tweak the phone to see what it can do, what performance we can wring out of it, etc. I've learned a lot in the little time I've been in this community and have a TON more to learn.
I've spent a LOT of time dicking around with this new phone (my first smartphone) and I love the fact that it is customizable it but it takes up too much time to have to read up on everything, flash, then re load all my icons, screw that. I just want to know what is the best, fastest, simplest, most customizable rom/kernel combo up front, or I'm going back to stock, I have to believe that they designed the stock OS around the phone to maximize effectiveness.
- Unfortunately reading up on it, trying ROMs out, and going through some trials and tribulations is a part of the process. Which is the best ROM is strictly subjective so you'd get a bunch of different answers from a bunch of different people.
The best thing I can suggest is, if you're really interested, to take the time to read the stickies in the different forums (General, Q&A, Developer, etc.). They contain a plethora of information that will actually help you to avoid a lot of the problems. Read some threads on different ROMs & issues. You'll find a lot of "I had this problem" followed by the developer or someone else saying "Yeah, I fixed that" or "here's how to avoid/fix it". Utilize the search feature; it's there to help. The more research you do on your own the more you will learn and the less likely you'll get flamed by anyone for not trying to help yourself before asking for the help of others.
Welcome to the forums. Best of luck to you.
Kudos to you both I hope other noobs find this info as well. I think I'll flash KJ6 deodexed (faster/cleaner/more customizable right?) rooted. I don't really see the need for CWM or Titanium unless there's a ton of bloatware to remove, or I want to go crazy flashing ROMS - from what I gather, with CWM you can modify the recovery mode so that new roms can be installed right from the phone?
I have really looking for some specific key features that would improve my experience, such as a customizable destination folder for camera pics, i.e. SD card, not internal memory, a good all-time gestures program, wifi file sharing w/ pc, some cool widgets and animations, and a major reduction in the spyware content and background data of the phone, specifically google apps that try to sync my entire brain.
Farlander said:
...from what I gather, with CWM you can modify the recovery mode so that new roms can be installed right from the phone?
Click to expand...
Click to collapse
Basically, but you always have to be careful when doing so. Make backups of your data and follow the instructions carefully unless you really enjoy losing important files and using Odin lol.
I have really looking for some specific key features that would improve my experience, such as a customizable destination folder for camera pics, i.e. SD card, not internal memory, a good all-time gestures program, wifi file sharing w/ pc, some cool widgets and animations, and a major reduction in the spyware content and background data of the phone, specifically google apps that try to sync my entire brain.
Click to expand...
Click to collapse
I already thought the default destination for Camera pictures was in sdcard/DCIM ? And for cool widgets and animations, you are better off using a custom Launcher, such as GO Launcher EX. A ton of roms on here, however, do offer very nice looking themes and many remove bloatware.
My advice: get comfortable with CWM and flash a few roms; however many you need until you know you're preferences.

[Q] n00b to custom ROMs

Hi, I'm new to flashing ROM's and wanted to give this a try, but I had a few questions (I searched and read the wiki, but I didn't see these specific questions):
I have the Samsung Galaxy S2 Skyrocket on ATT. I'm rooted on Stock GB 2.3.6
1. I wanted to try flashing this ROM([ROM][CyanogenMod 9 (unofficial)][TeamChopsticks][Alpha 1 - 4/26]), Can I come from gingerbread if I follow the instructions in post 1? Or do I need to have an ICS leak installed first?
2. I assume I can revert back to my rooted-stock ROM by using CWM with my current restore point?
3. If I restore the backup from step-2, does it restore the original radio (the UCLA3 radio)? Or am I stuck with the new one? Any disadvantes to just leaving the new one installed?
4. When flashing the new radio, is it just like flashing a ROM in CWM?
5. How would I get all my apps back on the custom ROM? (I know the contacts are linked to the google cloud) I have titanium backup pro installed now, but I read something about not restoring the apps across different ROMs?
6. If I decide to go back to my stock ROM after looking at a few custom ROMs, would I be able to get the ATT OTA updates? (I know I'd need to un-root and un-freeze all the bloatware, but I assume installing the custom ROM's would trigger the flash counter?)
7. I keep hearing about the "yellow triangle" when the flash counter is triggered. Does it only happen at boot and go away after that? Or is it always there?
Thanks in advance!
skyrockets said:
Hi, I'm new to flashing ROM's and wanted to give this a try, but I had a few questions (I searched and read the wiki, but I didn't see these specific questions):
I have the Samsung Galaxy S2 Skyrocket on ATT. I'm rooted on Stock GB 2.3.6
1. I wanted to try flashing this ROM([ROM][CyanogenMod 9 (unofficial)][TeamChopsticks][Alpha 1 - 4/26]), Can I come from gingerbread if I follow the instructions in post 1? Or do I need to have an ICS leak installed first?
2. I assume I can revert back to my rooted-stock ROM by using CWM with my current restore point?
3. If I restore the backup from step-2, does it restore the original radio (the UCLA3 radio)? Or am I stuck with the new one? Any disadvantes to just leaving the new one installed?
4. When flashing the new radio, is it just like flashing a ROM in CWM?
5. How would I get all my apps back on the custom ROM? (I know the contacts are linked to the google cloud) I have titanium backup pro installed now, but I read something about not restoring the apps across different ROMs?
6. If I decide to go back to my stock ROM after looking at a few custom ROMs, would I be able to get the ATT OTA updates? (I know I'd need to un-root and un-freeze all the bloatware, but I assume installing the custom ROM's would trigger the flash counter?)
7. I keep hearing about the "yellow triangle" when the flash counter is triggered. Does it only happen at boot and go away after that? Or is it always there?
Thanks in advance!
Click to expand...
Click to collapse
1) if you're a newb I wouldn't recommend flashing alpha versions of anything
2)You can revert back
3)No, flash a ginger radio before restoring
4)Yes, wipe cache/dalvik cache
5)You can restore apps accross the same OS, but I never do
6)Yes, if you're on official software. It wont trigger unless you flash with odin or sometimes a custom kernel like cm will trigger it. No big deal, we have a counter reset.
7)only at boot, we have counter reset, so no worries
Wow, that was a quick reply! Thanks.
Sorry if I'm dense, I just wanted to clarify two things before proceeding.
Re 1: I also saw another ROM I wanted to try, I guess I'll do that one ([ROM]SKY ICS--- 4.2D-9). Thanks for the heads up.
Re 3: From your response, am I correct to understand I can't use an ICS radio with GB? (it just wont work? or there's no advantage to keeping it?)
Re 5: Same OS meaning inside GB based ROMs or ICS based ROMs? If I go from stock GB to custom ICS, I need to re-download each app individually?
skyrockets said:
Wow, that was a quick reply! Thanks.
Sorry if I'm dense, I just wanted to clarify two things before proceeding.
Re 1: I also saw another ROM I wanted to try, I guess I'll do that one ([ROM]SKY ICS--- 4.2D-9). Thanks for the heads up.
Re 3: From your response, am I correct to understand I can't use an ICS radio with GB? (it just wont work? or there's no advantage to keeping it?)
Re 5: Same OS meaning inside GB based ROMs or ICS based ROMs? If I go from stock GB to custom ICS, I need to re-download each app individually?
Click to expand...
Click to collapse
1) very good choice, I run it and it is outstanding.
3)they will have a RIL mismatch. You can use them by deleting the system folder out of it, but I would just use the la3 radio and flash that before the rom. After a full wipe, of course.
5)Right, it ensures everything will be clean and run right.

So Rusty - Need Help.

It has been FOREVER since I have messed with my G2x. But lately it has been super laggy, the keyboard never picks up what key I pressed properly, and the accelerometer is a MESS.
Im currently on March 2011 baseband, Android Version 2.3.7, and a very, very old nightly.
Im looking to update to the newest baseband as I hear it is a huge improvement, and also try out an ICS rom. I have been browsing and reading up, but am so rusty on reverting and flashing.
Would the proper, easy way to do this be as follows:? This is what I've gathered from reading, just don't want to brick my phone for a stupid reason.
1)Flash a stock ROM - Full Factory Wipe
2)Update baseband with LG Update Tool
3)Root Phone again
4)Flash Custom ROM?
Also, can you revert to stock ROM without an external SD card? I was reading a few topics stating you can't. I also have a backup of the original stock ROM(or at least I think) from a very, very long time ago. Can I just restore that?
I apologize in advance for all the questions, just trying to refresh my memory on this entire process.
from what ive seen, after getting cwm on your phone via nv flash you install one of the ics roms then before rebooting the phone you have to install a fix via cwm that owain has on one of rom pages (domination i think) then you are good to go. and yes, you have to use an external sd card for all of this.
After updating baseband you will lose root as well as CWM. You need to put it back on before you can flash a custom rom on it.
cricketAC said:
After updating baseband you will lose root as well as CWM. You need to put it back on before you can flash a custom rom on it.
Click to expand...
Click to collapse
Ahh thank you! And I can not run the tool from a custom rom, correct? I have to flash back to stock, and then the updater will update baseband as well as unroot everything.
I also dont have an external SD card, so I guess I will be buying one to flash back to stock

Lifecycle of ROM's posted here - Alpha, Beta, offcial?

Hello,
I have a general noob question on the custom [ROM] threads.
Do custom ROM's posted go though an alpha, beta, official release stages? I see some [ROM] threads marked with an alpha or beta... while some others are not.
thanks!
U r right, alpha means something major is broken, beta its the "refinig" stage, and final its the complete rom
sent from the gray stuff inside my skull
demonoid phenomenom said:
U r right, alpha means something major is broken, beta its the "refinig" stage, and final its the complete rom
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
Is this process that is true for all ROMs that are posted? I see a few ROMs that don't say alpha or beta. Does it mean they are release grade?
gcretro said:
Is this process that is true for all ROMs that are posted? I see a few ROMs that don't say alpha or beta. Does it mean they are release grade?
Click to expand...
Click to collapse
There is no such thing as release grade. Everything should be considered at least developmental in some form or fashion.
The terms of alpha and beta do not mean what most people think they do in here.
Even the ones marked alpha and beta can still be daily drivers, just take a look at the first post of each ROM you are thinking about and see if the bugs will "bug" you like for instance any of the CM based ROMs here have issues with camera and video and few other small bugs.
Any ROM based off of "stock" will have less/no bugs and therefore not marked as beta or alpha, since they are not compiled.
It all depends on your personal needs as to what you are comfortable with and if you can deal with certain things not working right out of the box, or that you might have to make a work around for.
I call mine "alpha" or "beta" depending on bugs and/or how much more work I expect to put into it... and my mood at the time
Jim explained it well... it's all subjective to the dev and the end-user..
Best to just make a good backup, know how to restore it, and slap a new ROM on your phone to try it out for yourself.
That being said, be on the lookout for a gamma version of Numa ... (j/k - it's been a long time since I was back on ICS)
Sent from my paranoid phone's mind
alteredlikeness said:
I call mine "alpha" or "beta" depending on bugs and/or how much more work I expect to put into it... and my mood at the time
Jim explained it well... it's all subjective to the dev and the end-user..
Best to just make a good backup, know how to restore it, and slap a new ROM on your phone to try it out for yourself.
That being said, be on the lookout for a gamma version of Numa ... (j/k - it's been a long time since I was back on ICS)
Sent from my paranoid phone's mind
Click to expand...
Click to collapse
Thanks.
Regarding making a good back up, Should I just follow the CWM thread? I found this link in the newbie thread. However, there was little explanation on it's use.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
- Does using the CWM recovery to create a back up have any per-requisites? Can I use it on my stock AT&T Atrix2 that is still on GB?
- If I understand correct, this is used to dump an entire image of the phone (firmware, OS, apps, files etc...) to an SD card? And one can later restore back from.
- I am planing flashing the NUMA Rom. If I take a back up using CWM, I assume I can restore everything to they way it was (i.e. back to GB) without risks?
thanks
gcretro said:
Thanks.
Regarding making a good back up, Should I just follow the CWM thread? I found this link in the newbie thread. However, there was little explanation on it's use.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
- Does using the CWM recovery to create a back up have any per-requisites? Can I use it on my stock AT&T Atrix2 that is still on GB?
- If I understand correct, this is used to dump an entire image of the phone (firmware, OS, apps, files etc...) to an SD card? And one can later restore back from.
- I am planing flashing the NUMA Rom. If I take a back up using CWM, I assume I can restore everything to they way it was (i.e. back to GB) without risks?
thanks
Click to expand...
Click to collapse
First, you need to get ICS on your phone if you want to flash Numa. You must be on 4.0.4 firmware to flash any of the ICS and/or JB based ROMs. The choice is yours on how to get there... please search thoroughly, as it has been covered an insane amount of times.
But, to try and answer your questions:
-Yes, the pre-requisites are that you need to be rooted, and have a custom recovery installed on your phone.. and an sdcard. You can do it on your rooted GB phone, but you cannot restore a GB backup while you are on ICS (for the only way to have the option to return to GB from ICS, you need to look here and here - but some will say there's no reason to go back to GB.. maybe nostalgia )
-A backup will backup your current system, data, and sometimes cache - and it will usually make a new folder, named by date, with a few .tar files inside of a "clockworkmod" folder on your sdcard. And yes, those are what you restore (when restoring, you choose the backup by date/folder name).
-No, you can not restore a GB backup from Numa (see above comments.. again) - also see here for a note on compatibly between different custom recovery options (might be easiest/safest to use BMM, I think you can flash all ROMs with that now..)
So if I understand all that correctly, here is my summary of steps to install Numa. Appreciate if you can correct my steps in-line if I am wrong. [Current state of my phone: Atrix2 on stock GB (AT&T). Only thing I have done is uninstalled/removed unwanted apps.]
Steps:
1. First get on ICS leak-1 following Jim thread. [OR OTA to the official/final ICS. But if I do this, I lose the option to return to GB? or will I loose that ability regardless since Numa itself is based on final ICS OTA?]
2. Install CWM A2 bootstrap recover from here.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
(No point taking a backup now I suppose since going back to GB isn't an option after Numa.)
3. Then follow the install instructions under the Numa Rom thread.
4. Once I have Numa up & running, I suppose I am limited to putting only those ICS/JB based roms that don't require me to be on leak-1?
On a side note, I hate how they have removed the "contacts" tab, "Only show contacts with phone number" option etc... from the Dialer app in ICS and replaced it with the People thingy . I like GB dialer. Also, In ICS they seem to have removed the data saver option that was available in GB.
Thx
gcretro said:
So if I understand all that correctly, here is my summary of steps to install Numa. Appreciate if you can correct my steps in-line if I am wrong. [Current state of my phone: Atrix2 on stock GB (AT&T). Only thing I have done is uninstalled/removed unwanted apps.]
Steps:
1. First get on ICS leak-1 following Jim thread. [OR OTA to the official/final ICS. But if I do this, I lose the option to return to GB? or will I loose that ability regardless since Numa itself is based on final ICS OTA?]
If you uninstalled any stock apps, the installation of the update will probably fail, and you will either need to fix your system by replacing everything (very carefully).. or just FXZ back to stock GB<--post is a bit out-dated. [Yes, if you ota to final ICS, you can not return to GB ever. It doesn't matter what the ROM you flash is based on, they basically only change your /system partition (and data) - the problem is the new bootloader in final ICS.
Make a full backup of your stock ICS if you want to go back to it (see below - probably best to use BMM to backup)
2. Install CWM A2 bootstrap recover from here.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
(No point taking a backup now I suppose since going back to GB isn't an option after Numa.)
You could use that, or BootMenu Manager (I heard that it works to flash roms now - it used to not - and I personally have not tested it recently.. so, not sure - and we also have Safestrap, but not sure of the status on that - still a wip, I think). Either way, you will loose it once you flash Numa... you will need to reinstall it to flash a different rom or make a backup (I recommend using BMM to make a backup since it's compatible with the CM10-based recovery, and since it is easy to uninstall)
3. Then follow the install instructions under the Numa Rom thread.
Yup.. maybe a bit outdated also, but wipe data/factory reset, dalvik-cache maybe, then install zip..
4. Once I have Numa up & running, I suppose I am limited to putting only those ICS/JB based roms that don't require me to be on leak-1?
You can put any ICS/JB rom available for our phone, if you wish - or restore the backup you made of stock ICS before installing Numa
On a side note, I hate how they have removed the "contacts" tab, "Only show contacts with phone number" option etc... from the Dialer app in ICS and replaced it with the People thingy . I like GB dialer. Also, In ICS they seem to have removed the data saver option that was available in GB.
There are other ways to get from dialer to contacts in ICS (underneath the favorites tab, scroll down.. or is that only jb?)
Thx
No prob. Good luck.
Click to expand...
Click to collapse
See in-line..

Categories

Resources