[Rooting & ROM Flashing VZW GS3] Noob Questions

[Rooting & ROM Flashing VZW GS3] Noob Questions - Verizon Samsung Galaxy S III

I apologize in advance for asking the following noob questions. I have been an iPhone user for 3 years and wanted to take advantage of the GS3, which I am loving even without it being rooted. I am fairly tech-savy and believe I'll have no problem rooting my phone. There are just a few things I want to thoroughly understand. I've been sold on the fact that I want to root my phone to gain control of it, remove the bloatware, and extend it's battery life, etc. If there is a thread or posting or website somewhere that explains what I need to know very well, please direct me!!
I was looking for some major tips on the best way to achieve my goal of rooting and flashing to a new ROM...If someone could, PLEASE answer EVERY question. I'd like to fully understand how to get to my goal of rooting and flashing to a desired ROM without bricking it. If this gets desires attention, it could be a great sticky posts for other newbies!
1. First and foremost...What is a kernal? I see things about CM9/CM10 kernals. Is it something like a ROM? How is it related/different?
2. What is the CMW, what is a Touch Wiz?
3. What is the overall best way for a newbie to root their phone and install a desired ROM? Odin or???
4. As I understand thus far, there is rooting, then there is ROM flashing, and then there is something to do with unlocking the bootloader... I'd like to fully understand all of these.
Here's my goal and what I'm seeking help on... I think I want to use the Synergy ROM. What is the first step I must do? Do I somehow root my phone and then use Odin to flash to the Synergy ROM? Or is the first step simply opening Odin, connecting phone, and flashing to Synergy ROM? Do I not even use Odin to flash to Synergy? I'm confused here based on the install info in Synergys FAQ - do I use Odin at all??? Do I need to back anything up? Do I need to download or use some app to block Verizon OTA updates permanently??
In the Q&A of the Synergy ROM thread, it states:
You should have an unlocked bootloader if you wish to take full advantage of this ROM.
Click to expand...
Click to collapse
Must I unlock the bootloader seperately via this thread here, or do ROMs or other kernals (or whatever) have the unlocked bootloader built-in?? Do I install the bootloader before I root or after I root? What's the best way to unlock the bootloader(mmmeff's EZ-Unlock App, Terminal Emulator, or Adam Outler's Casual for Rooting/Cwm/Unlocking Bootloader)? Also, how do I keep the bootloader from being updated OTA, to keep from having problems????
I think that answers most/all of my questions. I'd hugely appreciate a response and answers to clarify all this, or links to some post or site I'm missing that explain all this to me. My goal to to root my phone, likely install a ROM, and do all this without bricking it, and hopefully without voiding any warranties (though not a big deal).
Thanks a bunch in advance!!

All the answers you seek can be found in droidstyle's guide. It's a sticky in the development section.
Sent from my SCH-I535 using xda app-developers app

Introduction to Rooting:
This is meant as a very basic disccussion for people completely new to rooting and Android. As a result, it will omit many details and simplify others. If there is a blatant mistake, please let me know and I'll correct it, but if there's something that's just not QUITE right, chances are it's simplified on purpose. Also, it's not meant to be a rooting guide (as there are excellent ones out there already) so much as an explanation of concepts most of us take for granted, but noobies don't.
DISCLAIMER: I, nor anyone else referenced (or not) in this thread, am not responsible for what you do with your phone. Rooting and otherwise altering your phone has the potential to brick your device, void your warranty, and many other horrible horrible things. Perform these actions at your own risk.
What is root/rooting?
In Unix-style operating systems, "root" is the name of the user who has all permissions and is therefore able to run/modify/change/delete just about anything. If you're familiar with Windows, this account is called Administrator. The default account (that's you!) on an Android phone does NOT have these privileges. Rooting is the process of obtaining them (i.e. obtaining root access). Once you root, you can "flash" new software onto your phone without restriction. This is great because you now have control over what programs are on your phone, what your UI looks like, how your phone handles resources, what kernels you run, and more!
Once your phone is rooted, you don't always wield all of that power. You control your access to all these new abilities with a program called SuperUser (available on the market and baked into ROMS). This program can grant these special rights to any other program that requests them. So let's say a program wants to write data to a place it's not allowed. It will ask SuperUser to up its privileges and then BAM! it can write where it wants to. You yourself can gain SuperUser privileges in a shell by typing su. Then YOU can read, write, and execute to your hearts desire.
Before you root:
Before rooting, there are some basic things you should know. A lot of people rush into it without bothering to learn everything they should. Sometimes it goes well, and sometimes it doesn't.
Phone partitions: Your phone has a number of partitions. The important ones to know at first are:
1. System - this partition is essentially what you think of when you think of the operating system, the Android UI, and preinstalled
apps. When people talk about flashing ROMs (e.g. CyanogenMod, Synergy, etc), they are talking about flashing a new system
partition.
2. Boot - this is the kernel and ramdisk. The kernel is responsible for managing the interactions between the phones software (including the ROM) and the
hardware. Altering the kernel can increase/decrease performance, battery life, and more because it manages applications and system resources. When
you flash a new kernel, it flashes to the boot partition. You may not notice a big difference like you do when changing ROMS, but behind the scenes, your
phone's performance can be drastically altered. A *LOOSE* analogy is that the ROM is like the body and interior of your car (including exterior color, AC,
stereo, heated seats, TV in headrests, etc.) and the kernel is like the engine. You may not see it, but you'll know it's there if it's awesome or it sucks.
3. Aboot - this was largely unimportant for newbies until the bootloader lock/unlock situation. The short story is that aboot contains functions which
authenticate the boot partition (that's the kernel, remember?). It checks to see if your boot partition is Verizon legal and if not, it aborts the boot process
and politely tells you to contact Verizon. This authentication is what is referred to as a "locked" bootloader. It prevents you from completely booting the
phone with a custom kernel. The bootloader is "unlocked" by replacing the stock aboot partition with one that does NOT check up on the boot partition.
This is important because it allows us to run whatever kernel we want.
4. Data - this contains user installed apps, settings, contacts, bookmarks, etc, etc, etc. You can wipe this partition (as opposed to the above partitions) and
still boot into the operating system. You will have just lost all your setting and apps. This is called a factory/data reset.
5. Cache - this is stuff that you frequently use so it's kept available for better performance. You can wipe it without much consequence.
6. Recovery - this partition contains a separate operating system that allows you to recover from a corrupted/absent/otherwise jacked up operating system. It
has other functions as well. The big ones are to backup your device and restore said backups, to wipe certain partitions, and to flash things to your
phone (i.e. install new ROMs, recoveries, or other programs). The stock recovery is limited so you will definitely want a custom recovery, created by the
fine devs in the community, on your device.
What is a ROM and what is a kernel? I touched on this above. A ROM is what goes on the system partition. It contains what you think of as the Android OS including the UI and preinstalled apps. It controls how programs interact with you, the user. A kernel controls how those programs interact with the phones hardware. You need both a ROM and a kernel to have a functional phone.
How do I get started rooting and flashing?
There is an excellent guide stickied in the development thread here http://forum.xda-developers.com/showthread.php?t=1762709. However, many of us
forget what it's like to be a COMPLETE newbie and to someone who has no idea about anything, even fantastic guides like that can be a little intimidating.
You can follow the steps, but may not understand what you're doing. The steps to take to start out with are:
1. Make sure you understand what I've written above. Make sure you are comfortable with the possibility of bricking your phone.
2. Root your device. As I said above, this is simply gaining root/Admin/whatever you want to call it access on your phone. In and of itself, it does NOT alter
the ROM or kernel or much of anything else. However, there are many different ways to obtain root and some of them DO alter these things. The easiest
and safest way to root (IMO) is to use Noxious Ninjas excellent tool. http://forum.xda-developers.com/showthread.php?t=1792342. If you like it, I
encourage you to donate or at least "Thanks" him. It works by taking advantage of debugfs permissions to get su (remember this from above??) onto
your phone with permissions set so you can run it. It therefore doesn't change ROMs or anything else. You won't lose data, apps, or anything else. It just
sneaks su right onto your current setup.
3. Install a custom recovery. This will allow you to do all the fun stuff I talked about above. I recommend installing EZ-recovery from the market and flashing
CWM 6.0.1.0.
1. Install EZ-recovery
2. Under the "Recovery" heading, click the Recovery radio button and select CWM 6.0.1.0 next to it.
3. Click flash
4. Backup everything as if your life depended on it. This means backing up your IMEI as shown here
http://rootzwiki.com/topic/32397-tutorial-imeibackup-nv-with-qpst-us-variants/ and making a nandroid. A nandroid is an image of your phone
including your ROM, your data, and your kernel(depending on what phone you have). You can restore a nandroid backup and you'll be right back where
you were before flashing or changing things around. The steps to making a nandroid are:
1. Turn off your phone.
2. Hold down volume up, home, and power until recovery appears.
3. Use the volume rocker to go to "backup and restore" and hit the power button
4. Select backup and then select the external (default) or internal (labeled "internal") SD card
You can restore a nandroid in a similar fashion (although you should wipe data/cache first - see below).
5. Unlock the bootloader. You must do this seperately from flashing ROMs and kernels. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1839791 and give appropriate thanks! A warning...if you mess up your aboot partition, there's really nothing (that I know of) you can do to revive your phone besides send it to someone with JTAG or back to Verizon.
You're now ready to start flashing ROMs.
As a precursor, there are ROMS that are based on TouchWiz modified Android from Verizon/Samsung and there are ROMS based on AOSP (e.g. CyanogenMod). TW roms need a TW kernel and AOSP roms need an AOSP kernel. Until you get comfortable with everything, I would stick with TW. Also, some roms come with kernels and will flash the kernel to your boot partition as well as the ROM to your system partition. Some ROMs don't come with kernels. ALWAYS ALWAYS ALWAYS read the OP of a rom you want to flash to find out kernel information as well as how to install the rom and anything else you may need to know. The general steps to flashing a ROM are (remember to read the OP for specifics):
1. Backup apps, data, call log, contacts, messages, etc. My program of choice for much of this is Titanium Backup available on the market. Buy it as you'll
use it a billion times.
2. Download the ROM you want and check the MD5
3. Place the ROM on the root of your SD card. Do NOT unzip it.
4. Reboot into recovery and make a nandroid backup
5. Wipe data/factory reset and wipe cache. Wipe it more than once if paranoid.
6. Go to "install zip from sdcard" and select the ROM you want
7. If you want/need to flash a kernel, install that zip from the sdcard too with the same command
8. Reboot and restore all that you backed up
Remember:
- ALWAYS backup before doing anything
- verify MD5
- wipe data and cache (unless told not to by the ROM dev)
- NEVER accept an OTA (having a custom recovery should block OTAs anyway)
PS. The techniques, tools, roms, etc in this post are not mine and arte the products of hours of hard work by multiple devs. Please thank them accordingly.

Bleelas said:
Introduction to Rooting:
This is meant as a very basic disccussion for people completely new to rooting and Android. As a result, it will omit many details and simplify others. If there is a blatant mistake, please let me know and I'll correct it, but if there's something that's just not QUITE right, chances are it's simplified on purpose. Also, it's not meant to be a rooting guide (as there are excellent ones out there already) so much as an explanation of concepts most of us take for granted, but noobies don't.
DISCLAIMER: I, nor anyone else referenced (or not) in this thread, am not responsible for what you do with your phone. Rooting and otherwise altering your phone has the potential to brick your device, void your warranty, and many other horrible horrible things. Perform these actions at your own risk.
What is root/rooting?
In Unix-style operating systems, "root" is the name of the user who has all permissions and is therefore able to run/modify/change/delete just about anything. If you're familiar with Windows, this account is called Administrator. The default account (that's you!) on an Android phone does NOT have these privileges. Rooting is the process of obtaining them (i.e. obtaining root access). Once you root, you can "flash" new software onto your phone without restriction. This is great because you now have control over what programs are on your phone, what your UI looks like, how your phone handles resources, what kernels you run, and more!
Once your phone is rooted, you don't always wield all of that power. You control your access to all these new abilities with a program called SuperUser (available on the market and baked into ROMS). This program can grant these special rights to any other program that requests them. So let's say a program wants to write data to a place it's not allowed. It will ask SuperUser to up its privileges and then BAM! it can write where it wants to. You yourself can gain SuperUser privileges in a shell by typing su. Then YOU can read, write, and execute to your hearts desire.
Before you root:
Before rooting, there are some basic things you should know. A lot of people rush into it without bothering to learn everything they should. Sometimes it goes well, and sometimes it doesn't.
Phone partitions: Your phone has a number of partitions. The important ones to know at first are:
1. System - this partition is essentially what you think of when you think of the operating system, the Android UI, and preinstalled
apps. When people talk about flashing ROMs (e.g. CyanogenMod, Synergy, etc), they are talking about flashing a new system
partition.
2. Boot - this is the kernel and ramdisk. The kernel is responsible for managing the interactions between the phones software (including the ROM) and the
hardware. Altering the kernel can increase/decrease performance, battery life, and more because it manages applications and system resources. When
you flash a new kernel, it flashes to the boot partition. You may not notice a big difference like you do when changing ROMS, but behind the scenes, your
phone's performance can be drastically altered. A *LOOSE* analogy is that the ROM is like the body and interior of your car (including exterior color, AC,
stereo, heated seats, TV in headrests, etc.) and the kernel is like the engine. You may not see it, but you'll know it's there if it's awesome or it sucks.
3. Aboot - this was largely unimportant for newbies until the bootloader lock/unlock situation. The short story is that aboot contains functions which
authenticate the boot partition (that's the kernel, remember?). It checks to see if your boot partition is Verizon legal and if not, it aborts the boot process
and politely tells you to contact Verizon. This authentication is what is referred to as a "locked" bootloader. It prevents you from completely booting the
phone with a custom kernel. The bootloader is "unlocked" by replacing the stock aboot partition with one that does NOT check up on the boot partition.
This is important because it allows us to run whatever kernel we want.
4. Data - this contains user installed apps, settings, contacts, bookmarks, etc, etc, etc. You can wipe this partition (as opposed to the above partitions) and
still boot into the operating system. You will have just lost all your setting and apps. This is called a factory/data reset.
5. Cache - this is stuff that you frequently use so it's kept available for better performance. You can wipe it without much consequence.
6. Recovery - this partition contains a separate operating system that allows you to recover from a corrupted/absent/otherwise jacked up operating system. It
has other functions as well. The big ones are to backup your device and restore said backups, to wipe certain partitions, and to flash things to your
phone (i.e. install new ROMs, recoveries, or other programs). The stock recovery is limited so you will definitely want a custom recovery, created by the
fine devs in the community, on your device.
What is a ROM and what is a kernel? I touched on this above. A ROM is what goes on the system partition. It contains what you think of as the Android OS including the UI and preinstalled apps. It controls how programs interact with you, the user. A kernel controls how those programs interact with the phones hardware. You need both a ROM and a kernel to have a functional phone.
How do I get started rooting and flashing?
There is an excellent guide stickied in the development thread here http://forum.xda-developers.com/showthread.php?t=1762709. However, many of us
forget what it's like to be a COMPLETE newbie and to someone who has no idea about anything, even fantastic guides like that can be a little intimidating.
You can follow the steps, but may not understand what you're doing. The steps to take to start out with are:
1. Make sure you understand what I've written above. Make sure you are comfortable with the possibility of bricking your phone.
2. Root your device. As I said above, this is simply gaining root/Admin/whatever you want to call it access on your phone. In and of itself, it does NOT alter
the ROM or kernel or much of anything else. However, there are many different ways to obtain root and some of them DO alter these things. The easiest
and safest way to root (IMO) is to use Noxious Ninjas excellent tool. http://forum.xda-developers.com/showthread.php?t=1792342. If you like it, I
encourage you to donate or at least "Thanks" him. It works by taking advantage of debugfs permissions to get su (remember this from above??) onto
your phone with permissions set so you can run it. It therefore doesn't change ROMs or anything else. You won't lose data, apps, or anything else. It just
sneaks su right onto your current setup.
3. Install a custom recovery. This will allow you to do all the fun stuff I talked about above. I recommend installing EZ-recovery from the market and flashing
CWM 6.0.1.0.
1. Install EZ-recovery
2. Under the "Recovery" heading, click the Recovery radio button and select CWM 6.0.1.0 next to it.
3. Click flash
4. Backup everything as if your life depended on it. This means backing up your IMEI as shown here
http://rootzwiki.com/topic/32397-tutorial-imeibackup-nv-with-qpst-us-variants/ and making a nandroid. A nandroid is an image of your phone
including your ROM, your data, and your kernel(depending on what phone you have). You can restore a nandroid backup and you'll be right back where
you were before flashing or changing things around. The steps to making a nandroid are:
1. Turn off your phone.
2. Hold down volume up, home, and power until recovery appears.
3. Use the volume rocker to go to "backup and restore" and hit the power button
4. Select backup and then select the external (default) or internal (labeled "internal") SD card
You can restore a nandroid in a similar fashion (although you should wipe data/cache first - see below).
5. Unlock the bootloader. You must do this seperately from flashing ROMs and kernels. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1839791 and give appropriate thanks! A warning...if you mess up your aboot partition, there's really nothing (that I know of) you can do to revive your phone besides send it to someone with JTAG or back to Verizon.
You're now ready to start flashing ROMs.
As a precursor, there are ROMS that are based on TouchWiz modified Android from Verizon/Samsung and there are ROMS based on AOSP (e.g. CyanogenMod). TW roms need a TW kernel and AOSP roms need an AOSP kernel. Until you get comfortable with everything, I would stick with TW. Also, some roms come with kernels and will flash the kernel to your boot partition as well as the ROM to your system partition. Some ROMs don't come with kernels. ALWAYS ALWAYS ALWAYS read the OP of a rom you want to flash to find out kernel information as well as how to install the rom and anything else you may need to know. The general steps to flashing a ROM are (remember to read the OP for specifics):
1. Backup apps, data, call log, contacts, messages, etc. My program of choice for much of this is Titanium Backup available on the market. Buy it as you'll
use it a billion times.
2. Download the ROM you want and check the MD5
3. Place the ROM on the root of your SD card. Do NOT unzip it.
4. Reboot into recovery and make a nandroid backup
5. Wipe data/factory reset and wipe cache. Wipe it more than once if paranoid.
6. Go to "install zip from sdcard" and select the ROM you want
7. If you want/need to flash a kernel, install that zip from the sdcard too with the same command
8. Reboot and restore all that you backed up
Remember:
- ALWAYS backup before doing anything
- verify MD5
- wipe data and cache (unless told not to by the ROM dev)
- NEVER accept an OTA (having a custom recovery should block OTAs anyway)
PS. The techniques, tools, roms, etc in this post are not mine and arte the products of hours of hard work by multiple devs. Please thank them accordingly.
Click to expand...
Click to collapse
THANK YOU!!!!! Very helpful! I had no idea I needed EZ-Recovery to flash CWM as the primary recovery tool - that saved me big time as I was about to unlock the bootloader later today.
After posting this last night, and awaiting responses, I was browsing and trying to take in as much as I could. I finally realized that each section in the linked guide is a different way to either root or install a ROM. After I figured this out, and read about Odin being best for newbies, I decided to take the risk and wing it, even though I wasn't 110% sure.
So, now I'm rooted and have ROM manager/CWM installed, TiBu, and ES File Explorer installed. Now I'm just trying to figure out what I can/cannot remove as far as bloatware. A few items I'm sure I'd like to keep (working), so I don't want to mess with anything that might be used in another app/widget....Which brings me to my next question...
What's the best way to remove bloatware? I found an excel spreadsheet online that shows what's safe/unsafe to remove but I'm confused as to what I should do to get rid of items I NEVER want, and how to turn off items I MAY want in the future. If I freeze these items, do they stay frozen upon reboot, and until I unfreeze, or otherwise? What's the difference between a .APK package and a single process, etc?
Thanks in advance! I feel like I entered Android Elementary last night and already graduated to Android Junior High!
P.S. The captchas on this site to post ARE THE WORST CAPTAS IVE SEEN IN MY ENTIRE FRIGGIN LIFE, MY GOD!!!! I must refresh it 20x til something is RELATIVELY clear. Seriously????

ike034 said:
1...
Click to expand...
Click to collapse
Me too..... But the post are suppose to me helpful and or contribute in some way....
But at least we can thank all over the place......

Weioo said:
THANK YOU!!!!! Very helpful! I had no idea I needed EZ-Recovery to flash CWM as the primary recovery tool - that saved me big time as I was about to unlock the bootloader later today.
After posting this last night, and awaiting responses, I was browsing and trying to take in as much as I could. I finally realized that each section in the linked guide is a different way to either root or install a ROM. After I figured this out, and read about Odin being best for newbies, I decided to take the risk and wing it, even though I wasn't 110% sure.
So, now I'm rooted and have ROM manager/CWM installed, TiBu, and ES File Explorer installed. Now I'm just trying to figure out what I can/cannot remove as far as bloatware. A few items I'm sure I'd like to keep (working), so I don't want to mess with anything that might be used in another app/widget....Which brings me to my next question...
What's the best way to remove bloatware? I found an excel spreadsheet online that shows what's safe/unsafe to remove but I'm confused as to what I should do to get rid of items I NEVER want, and how to turn off items I MAY want in the future. If I freeze these items, do they stay frozen upon reboot, and until I unfreeze, or otherwise? What's the difference between a .APK package and a single process, etc?
Click to expand...
Click to collapse
Glad to hear you're rooted and learning a lot! Now you're opening another HUGE can of worms, namely how Android organizes the application framework, what are services, processes, activities, tasks etc. You may have already found the information you're looking for, but a montrously dumbed down version is that the APK is a package containing the compiled program and all the extraneous files it needs to run while a process is an actively running application. In order to debloat, you can either freeze an application with another program like TiBu, or you can manually freeze it by changing the app extension, or you can delete the APK, or you can remove it from the rom you want BEFORE you even flash it. What you choose depends on your goals...why you want to debloat.

Weioo said:
THANK YOU!!!!! Very helpful! I had no idea I needed EZ-Recovery to flash CWM as the primary recovery tool - that saved me big time as I was about to unlock the bootloader later today.
After posting this last night, and awaiting responses, I was browsing and trying to take in as much as I could. I finally realized that each section in the linked guide is a different way to either root or install a ROM. After I figured this out, and read about Odin being best for newbies, I decided to take the risk and wing it, even though I wasn't 110% sure.
So, now I'm rooted and have ROM manager/CWM installed, TiBu, and ES File Explorer installed. Now I'm just trying to figure out what I can/cannot remove as far as bloatware. A few items I'm sure I'd like to keep (working), so I don't want to mess with anything that might be used in another app/widget....Which brings me to my next question...
What's the best way to remove bloatware? I found an excel spreadsheet online that shows what's safe/unsafe to remove but I'm confused as to what I should do to get rid of items I NEVER want, and how to turn off items I MAY want in the future. If I freeze these items, do they stay frozen upon reboot, and until I unfreeze, or otherwise? What's the difference between a .APK package and a single process, etc?
Thanks in advance! I feel like I entered Android Elementary last night and already graduated to Android Junior High!
P.S. The captchas on this site to post ARE THE WORST CAPTAS IVE SEEN IN MY ENTIRE FRIGGIN LIFE, MY GOD!!!! I must refresh it 20x til something is RELATIVELY clear. Seriously????
Click to expand...
Click to collapse
Have you decided on a ROM you want to use yet? Personally I think that takes a lot of the decisions about de-bloating out of the equation. Pick a ROM, flash it, and see what you got? I first did the de-bloated root method and didn't have the stock e-mail app! While it is easy to download an e-mail app from the play store I was still shocked that it was considered bloat by the builder of the particular de-bloated version I chose.
Currently I am on Synergy 1.7 r23 with Darkhorse theme. I also like the Color in HD theme but can't decided between the two.

Bleelas said:
Glad to hear you're rooted and learning a lot! Now you're opening another HUGE can of worms, namely how Android organizes the application framework, what are services, processes, activities, tasks etc. You may have already found the information you're looking for, but a montrously dumbed down version is that the APK is a package containing the compiled program and all the extraneous files it needs to run while a process is an actively running application. In order to debloat, you can either freeze an application with another program like TiBu, or you can manually freeze it by changing the app extension, or you can delete the APK, or you can remove it from the rom you want BEFORE you even flash it. What you choose depends on your goals...why you want to debloat.
Click to expand...
Click to collapse
Awesome, the explanation of what a .APK is helped a TON! Thank you!
dan_joegibbsfan said:
Have you decided on a ROM you want to use yet? Personally I think that takes a lot of the decisions about de-bloating out of the equation. Pick a ROM, flash it, and see what you got? I first did the de-bloated root method and didn't have the stock e-mail app! While it is easy to download an e-mail app from the play store I was still shocked that it was considered bloat by the builder of the particular de-bloated version I chose.
Currently I am on Synergy 1.7 r23 with Darkhorse theme. I also like the Color in HD theme but can't decided between the two.
Click to expand...
Click to collapse
I know you've been helping me in my other thread. Thanks again for everything! I believe you know now, I am on Synergy r46, running quite stable so far but I haven't done much to the phone since flashing.

I've got a noob question... is there any way to back up your IMEI and install the samsung drivers from a Mac besides running Parallels or VMware? I rooted using Adam Outler's Casual and would like to start flashing ROM's but don't want to risk it without backing up my IMEI first.

See the note in this thread that backing up IMEI is obsolete. Nowadays you use the method linked from that thread, which does not involve making a backup first.

Weioo, I'd like to thank you for your intelligent questions, willingness to read, and attitude in this forum. It's good to see someone posting in the correct place, educating theirself, and not coming into the forum saying something like "plz help my phone wont boot and i didnt read enouf". So, respect. :good:
Anyway, to add something to this thread. What version of Clockwork Recovery are you using? If you're using version 6+, let me say a little how to manage your backups. The new CWR stores its backups in /sdcard/clockworkmod/backup/, which will only be about 20mb in size - this is normal. The backup file is just sort of an index, and the other couple hundred megabytes meat of the backup is stored as a ton of tiny files in /sdcard/clockworkmod/blobs/. If you ever need to clean up space on your phone's storage, always delete the backup file and do not touch the blobs directory. When you make your next backup, CWR will clean up the space freed from deleting that backup file.
What's actually going on is that instead of making one big file as a copy of a phone's complete image (as CWR did in previous versions), it saves space by backing up each file individually. If you have two backups with the exact same file (having the same hash), CWR deduplicates that by only backing it up once. The blobs folder has each fine, with the hash as its filename, and the backup file includes which hashes (filenames) it needs to function. When very few things change in between backups, the new backup only has to add new blobs for the things that changed (and thus have a different hash). You don't delete the blobs directly because it's not obvious which ones are used and which aren't. When CWR cleans up space, it reads the backup files and deletes blobs that aren't associated with any existing backups.

rednukleus said:
See the note in this thread that backing up IMEI is obsolete. Nowadays you use the method linked from that thread, which does not involve making a backup first.
Click to expand...
Click to collapse
Okay thanks, but if I do flash something and lose my IMEI, to do that process I'd need to be running Parallels or VMware on my Mac. Basically I'm trying to figure out if there is another way to do this using a mac or would I need to buy one of those programs if I lose my IMEI?

Great beginner post
lazarus2405 said:
Weioo, I'd like to thank you for your intelligent questions, willingness to read, and attitude in this forum. It's good to see someone posting in the correct place, educating theirself, and not coming into the forum saying something like "plz help my phone wont boot and i didnt read enouf". So, respect. :good:
Anyway, to add something to this thread. What version of Clockwork Recovery are you using? If you're using version 6+, let me say a little how to manage your backups. The new CWR stores its backups in /sdcard/clockworkmod/backup/, which will only be about 20mb in size - this is normal. The backup file is just sort of an index, and the other couple hundred megabytes meat of the backup is stored as a ton of tiny files in /sdcard/clockworkmod/blobs/. If you ever need to clean up space on your phone's storage, always delete the backup file and do not touch the blobs directory. When you make your next backup, CWR will clean up the space freed from deleting that backup file.
What's actually going on is that instead of making one big file as a copy of a phone's complete image (as CWR did in previous versions), it saves space by backing up each file individually. If you have two backups with the exact same file (having the same hash), CWR deduplicates that by only backing it up once. The blobs folder has each fine, with the hash as its filename, and the backup file includes which hashes (filenames) it needs to function. When very few things change in between backups, the new backup only has to add new blobs for the things that changed (and thus have a different hash). You don't delete the blobs directly because it's not obvious which ones are used and which aren't. When CWR cleans up space, it reads the backup files and deletes blobs that aren't associated with any existing backups.
Click to expand...
Click to collapse
This should be stickied!!

My apologies for the newb questions, but last night I modded my phone to Eclipse 2.1 version 10-20-12 with the latest GAPPS 10-21-12 ( http://forum.xda-developers.com/showthread.php?t=1934572 ). This latest GAPPS seems to be missing a bunch of applications including GMAIL registration (to access the Play store successfully) as well Google Now and many other Google based apps (Google Maps, Google Voice, etc etc). I don't believe the ROM was installed incorrectly - I went through the prerequisite Wipe Cache/Wipe Partition/Wipe Dvalik Cache and even Fix Permissions. Also the Voice Search application is missing, but maybe that's tied in with the Google suite of apps not running correctly.
Being that I'm a newb on this site I can't post the question over on the Eclipse page (not allowed access with less then 10 posts) but I find it impossible to properly register/access Google Play as well as using any of the Google Apps. I went ahead and downloaded Google Now separately and installed the APKs but this just resulted in the program crashing when the GPS is enabled (keeping it disabled keeps Google Now at the "Initializing" screen).
Thanks for any support that can be provided.

ResolveD
Disregard the previous post - used GAPPS from 10-12-12 (w/o Dvalik cache wipe) and Google Now, Voice Search, G-mail register, Google Play all work fine now. The only issue I see is presently with the Google Now browser not scrolling through links, but you can always use the magnifying glass (which shows you previews of the webpages it finds).
Anyways HIGHLY RECOMMENDED ROM!!! Eclipse 10-20 build (4.1.2) w/10-12 GAPPS. Easily the best ROM out there so far :laugh:

Deleting System apps
Now that I have finally rooted my VZW GS3, and installed Titanium Backup Pro, am I able to delete system apps from there without damaging anything? I have not installed a custom ROM, all I have done is root, unlock bootloader and install CWM. I want to get rid of bloatware (e.g. Polaris Viewer) can I use TI BU Pro?

levilib said:
Now that I have finally rooted my VZW GS3, and installed Titanium Backup Pro, am I able to delete system apps from there without damaging anything? I have not installed a custom ROM, all I have done is root, unlock bootloader and install CWM. I want to get rid of bloatware (e.g. Polaris Viewer) can I use TI BU Pro?
Click to expand...
Click to collapse
Yes.
Sent from my SCH-I535 using xda app-developers app

levilib said:
Now that I have finally rooted my VZW GS3, and installed Titanium Backup Pro, am I able to delete system apps from there without damaging anything? I have not installed a custom ROM, all I have done is root, unlock bootloader and install CWM. I want to get rid of bloatware (e.g. Polaris Viewer) can I use TI BU Pro?
Click to expand...
Click to collapse
Just wanted to add that it may be better to just freeze the apps, or at least run a nandroid backup so you can revert to stock. Without all system apps intact an OTA update would fail.

apacseven said:
Just wanted to add that it may be better to just freeze the apps, or at least run a nandroid backup so you can revert to stock. Without all system apps intact an OTA update would fail.
Click to expand...
Click to collapse
I'm not worried about an OTA update, and I made a nandroid, I just want to make sure I'm not going to delete anything important. are there any apps you can think of that I would want to delete but it would cause problems?

Related

[Q] 100% Original Stock ROM backup before root?

Hi there,
I am new to xda and new to Android hacking.
What I wanna ask is, (I guess it's of most newbies concern as well), can we have a 100% backup of our system (stock ROM)? Obviously, it is important because:
If we perform an official (OTA) update to a new Android version. And we don't like it. It is possible to get back to the old original one which we are used to. (not everybody likes new things, and/or not every new thing is good)
If our phones are having some problems. And we have to give it back to the company for a fix. In most cases they will flash a new ROM for us. If we wanna keep using the old one (explained in #1), we have to keep a copy of it by ourselves.
If we want to try new custom ROMs, we may want to switch it back after trying.
Whenever we do any modifications, it's always better to keep a backup/roll-back point. In case anything goes wrong, we have a safeguard.
For the official warranty issue.
Yup I do see there are some official stock ROMs downloads for some particular phones. But those are not really a backup of our original ROMs. And it's always hard to verify if those downloads are the original official releases. And, if those downloads are 100% stock ROMs, this means some guys out there could make it, so what is the way to do so?
Or, how those mobile phone companies do it in their labs?
I have been doing researches on this topic for a few days. Some posts claim that their methods are "backup stock ROM" or "backup before rooting". But after digging into it, they requires rooting and/or flashing CWM. Here comes a few questions:
Questions
Rooting will in fact changes some files/data of the system. So backup after root is NOT getting the original stock ROM. Is it?
Is there a method to "un-root", so ALL the changes are TOTALLY reverted?
Installing/flashing things like CWM in phone requires rooting, which would make the ROM not original. Is there a way to extract the system backup from a computer externally?
In addition, I have found some related pieces. which could be useful to anyone viewing this post, and might be useful for you to solve this (my) question. :fingers-crossed:
* as I'm a new user, I can't post links directly. Please delete the blank spaces in between.
ht tp://www .modaco .com/topic/351269-backup-original-rom/
In reply #5, user C3C0 raised a method of backing up the original stock ROM without root. But it seems he is flashing CWM and that method is only for ZTE Skate.
adb backup tool of Android SDK
At the first sight i came across this approach, I thought it is the official method to do whole system (ROM) backup (WOW - how nice!). But after studying for a few more posts, I think adb backup can only backup app+app_data, and possibly some system settings only. Am I correct? And also, adb backup is only for ICS (Android 4.0), isn't it?
adb backup usage: ht tp://forum.xda-developers .com/showthread.php?t=1420351
(But mentioned in the bottom of #1 the poster is having some issues on using adb backup. Perhaps there are some bugs and not reliable(?)
One more question on adb backup: Can it backup just one app+app_data, and restore just one app+app_data, without affecting other things? If yes, we don't need to root and don't need Titanium Backup (which requires root) for backup app+app_data. Isn't it?
** In case I have said anything or any terms wrongly in this thread, please DO correct me, for helping me and helping others.
P.S. i am using LG Optimus 3D.
Thanks a lot, wholeheartedly,
midnite_

Backup phone before root
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er

ASharpEdge said:
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er
Click to expand...
Click to collapse
Hi ya,
It's so nice that you are having the same concern as I do.
As far as i know, the approaches of rooting differ from phones to phones. So we may have to find our own specific rooting method in the phone model sub-forums. It won't be hard for your popular S3
I would like to have a look at that Mr. Robinson's thread. If he can backup the stock ROM, those app+app_data wont a big issue (i guess).
cheers,
midnite_

midnite_ said:
Questions
Rooting will in fact changes some files/data of the system. So backup after root is NOT getting the original stock ROM. Is it?
Is there a method to "un-root", so ALL the changes are TOTALLY reverted?
Installing/flashing things like CWM in phone requires rooting, which would make the ROM not original. Is there a way to extract the system backup from a computer externally?
Click to expand...
Click to collapse
Hi midnight, welcome to a new and exciting world of Android and trying new things. First, let me assure you, what you want is NOT something new. People have been doing this type of thing for years. That is flashing and testing roms. As you will learn, it actually becomes quite addictive. We call those folks that get addicted to flashing: Flashaholics or crackflashers, lol
First let me talk about "root". This process consists of unlocking a lower level of the Android system known as the bootloader. Unlocking the bootloader of your device allows you to flash a custom recovery, flashing a custom recovery allows you to flash the Superuser binary and Superuser.apk, This is what allows you to use apps that require "root". The bootloader is not an OS file. So when you are unlocking your bootloader you are not modifying your stock rom. Only when you have flashed the Superuser package have you modified your stock rom. And even that isn't really modifying anything. When you flash the Superuser package, it adds two files to your rom at certain locations of the file system. It adds the Superuser.apk file to system/app and it adds the SU binary to system/bin. Basically you CAN have a totally S-OFF (unlocked) bootloader and still have an entirely stock rom if you want. But the real benifit is flashing a custom recovery like ClockworkMod Recovery and then flash the superuser package.
As far as extracting the stock system, you should try giving adb a go. Do it right now if you like. Ensure you have the android sdk installed and properly set up on your computer and your computer can recognize your phone. Ensure your phone is in debugging mode, connect your phone to your computer, open up a command window, and run this command:
Code:
adb pull \
This command will pull everything off your phone except for data which is where your market or Google Play apps are stored.
Beyond XDA there are aso more resources to learn from. For example, http://www.android.com is a good place to start, and to learn more about adb check out http://developer.android.com/tools/help/adb.html
If you need to learn how to setup the sdk here is the place to learn how: http://developer.android.com/sdk/index.html
I'm sure others will add to this as well which is the good thing about this community.
Welcome to XDA, I hope you have fun learning, and maybe share back someday things you learn along the way.

wildstang83 said:
Hi midnight, welcome to a new and exciting world of Android and trying new things. First, let me assure you, what you want is NOT something new. People have been doing this type of thing for years. That is flashing and testing roms. As you will learn, it actually becomes quite addictive. We call those folks that get addicted to flashing: Flashaholics or crackflashers, lol
First let me talk about "root". This process consists of unlocking a lower level of the Android system known as the bootloader. Unlocking the bootloader of your device allows you to flash a custom recovery, flashing a custom recovery allows you to flash the Superuser binary and Superuser.apk, This is what allows you to use apps that require "root". The bootloader is not an OS file. So when you are unlocking your bootloader you are not modifying your stock rom. Only when you have flashed the Superuser package have you modified your stock rom. And even that isn't really modifying anything. When you flash the Superuser package, it adds two files to your rom at certain locations of the file system. It adds the Superuser.apk file to system/app and it adds the SU binary to system/bin. Basically you CAN have a totally S-OFF (unlocked) bootloader and still have an entirely stock rom if you want. But the real benifit is flashing a custom recovery like ClockworkMod Recovery and then flash the superuser package.
As far as extracting the stock system, you should try giving adb a go. Do it right now if you like. Ensure you have the android sdk installed and properly set up on your computer and your computer can recognize your phone. Ensure your phone is in debugging mode, connect your phone to your computer, open up a command window, and run this command:
Code:
adb pull \
This command will pull everything off your phone except for data which is where your market or Google Play apps are stored.
Beyond XDA there are aso more resources to learn from. For example, ht tp://www .android .com is a good place to start, and to learn more about adb check out ht tp://developer .android .com/tools/help/adb.html
If you need to learn how to setup the sdk here is the place to learn how: ht tp://developer .android .com/sdk/index.html
I'm sure others will add to this as well which is the good thing about this community.
Welcome to XDA, I hope you have fun learning, and maybe share back someday things you learn along the way.
Click to expand...
Click to collapse
Hi Wildstang,
Thanks very much for your warm welcome and very informative reply. So are you a Flashaholics or Crackflashers yet?
As I am a newbie, please forgive me if I am asking dumb questions.
As far as I understand,
The steps of root is
1. Unlock the bootloader
2. Flash Superuser binary & Superuser.apk
** does "flash a custom recovery" means "flash Superuser binary & Superuser.apk"?
"Flash Superuser binary & Superuser.apk" is just "add SU binary to system/bin" and "add Superuser.apk to system/app". Then why not just copy them into place?
I just found on the web that "flashing" means replacing the OS of the phone with a new ROM. Would that still keeping the stock ROM?
To have a backup of the original stock ROM, can I
1. Unlock the bootloader
2. Flash Superuser binary & Superuser.apk
3. Perform the backup
And later, after I have flashed a new ROM, or whatever I do, as long as I didn't brick it, when I want to rollback my phone to its original, I can
1. Restore the backup
2. Delete "SU binary in system/bin" and "Superuser.apk in system/app"
3. re-lock the bootloader
Is this correct?
I don't mean to challenge you. But does adb pull \ really backup the system, or just all the files?
Thanks very much again!
midnite_

Hey midnite_,
I am a newbie too and have a lot of blank spots in my understanding of what we can do with android. I also came here with same question. I found how to root, this isn't a secret. Like you, I want to know how do I fix it if I break it.
So, with regards to your questions.
1. Unlock the bootloader
Not clear on this one, as not every tutorial even mentions this part. My feeling is that this might be specific to some phones, like HTC.
2. Flash Custom Recovery (such as AmonRa, CWR, TWRP...)
Recovery is an intermediate stage of phone booting process after bootloader but before OS.
It is there to allow OTA (Over the air) updates. During those, the OS is halted and replaced with a newer one.
What this means for us is that the recovery is capable of replacing OS (ROM - are these terms interchangeable?).
Recovery is the same as hidden partition on windows, that is sometimes present on a PC. It has a limited interface.
It can replace one OS image with another. It probably checks the checksum and creates the new one after the update. It is probably the gatekeeper.
Stock recovery will not replace OS with an image from SD card or from PC through USB. Only OTA.
This is the reason for flashing the custom (hacked) recovery on.
Custom recovery is made to allow additional options, such as allowing image sources such as PC or SD card, and also a ROM backup (write OS image to PC).
3. Flash update file using "upgrade from SD card" function of custom recovery now in place.
In this step, the Superuser.apk and bin files are placed. Stock recovery will not let us do that.
Also, I think the reason we can't just use ADB to "copy" superuser package to phone is because the system is either running or exists as an image (compressed?), and is probably protective of its modification. (So, likely the superuser package also replaces the checksum that the OS uses to check if it has been compromised?) Yes, this modifies your rom.
I assume that unrooting could be done after this by updating again with a file that removes superuser package and that would make your rom stock again.
4 OR flash custom ROM, which usually includes superuser package. Of course using custom rom means you no longer have stock rom.
To have a backup of original ROM, you would :
1 Unlock bootloader,
2 Flash (install) custom recovery
3 superuser doesn't matter here
4 Use custom recovery function to back up your stock ROM.
I want to know the answers to the rest of your questions as well as some clarifications to mine.
Personally, I am looking for a way to backup the stock recovery as well.
I know there are some people asking about this. The procedure appears to be as follows:
(pieced together so don't take it as a tutorial)
1 Unlock bootloader (again, unclear on this. Also some mention S-OFF and others don't)
2 With USB debugging allowed (meaning connect as device requiring a driver), Connect to a PC with ABD, and a driver installed.
3 From ADB, issue a command "adb boot recoveryimage.name" instead of the usual "adb flash recoveryimage.name".
This will make the phone boot into a custom recovery image that is residing on PC, without first writing it to the phone.
4 Unclear how, but make that custom recovery now being live to back up stock rom to pc.
5 Unclear how, but make that custom recovery now being live to flash either root or custom rom to the phone.
6 Disconnect, reboot the phone. Once in OS, use root privileges to mount recovery partition ? (this makes it visible as drive)
7 Don't know how, but use root privileges to back up now visible stock recovery partition to PC as image.
( This should give you two out of three original parts.)
Keep in mind that even if my peace-by-peace "know-how" ever works, there is at least one clearly faulty step:
The back up of the original state of the boot loader has been never made. I do not know if it is easily can be toggled back and forth from lock to unlock and back without leaving any trace. Also, like yourself, I probably don't quite understand what am I talking about, but I have tried to make as much sense of what I have read here and there.
This is my first smart phone, and my experience with linux is limited to building a minecraft server on MineOS, which was pre-made so that not much was required to make it run. I have "mounted" a partition for the first time last week, trying to break Win7recovery, booting it with Knoppix. This is why I think this is probably will come in play here too, as the recovery partition on W7 was hidden. Until then I didn't understand what mounting means, as windows always does it for you. So, take everything I say with a bunch of salt.
Please, let me know too, if you find out more. I want to flash the hell out of my Prism, but I want to be smart about it.

bump... midnite_ r u still around?

Hi Descent2,
Yes i am still around but i am busy with other stuffs at this moment. Thanks very much for your reply. You have studied a lot and you really did good summarisations. Very informative and I learnt a lot from it. Hope some of the masters or experienced ones would come by and bring us out of the mist
cheers,
midnite_
Descent2 said:
Hey midnite_,
I am a newbie too and have a lot of blank spots in my understanding of what we can do with android. I also came here with same question. I found how to root, this isn't a secret. Like you, I want to know how do I fix it if I break it.
So, with regards to your questions.
1. Unlock the bootloader
Not clear on this one, as not every tutorial even mentions this part. My feeling is that this might be specific to some phones, like HTC.
2. Flash Custom Recovery (such as AmonRa, CWR, TWRP...)
Recovery is an intermediate stage of phone booting process after bootloader but before OS.
It is there to allow OTA (Over the air) updates. During those, the OS is halted and replaced with a newer one.
What this means for us is that the recovery is capable of replacing OS (ROM - are these terms interchangeable?).
Recovery is the same as hidden partition on windows, that is sometimes present on a PC. It has a limited interface.
It can replace one OS image with another. It probably checks the checksum and creates the new one after the update. It is probably the gatekeeper.
Stock recovery will not replace OS with an image from SD card or from PC through USB. Only OTA.
This is the reason for flashing the custom (hacked) recovery on.
Custom recovery is made to allow additional options, such as allowing image sources such as PC or SD card, and also a ROM backup (write OS image to PC).
3. Flash update file using "upgrade from SD card" function of custom recovery now in place.
In this step, the Superuser.apk and bin files are placed. Stock recovery will not let us do that.
Also, I think the reason we can't just use ADB to "copy" superuser package to phone is because the system is either running or exists as an image (compressed?), and is probably protective of its modification. (So, likely the superuser package also replaces the checksum that the OS uses to check if it has been compromised?) Yes, this modifies your rom.
I assume that unrooting could be done after this by updating again with a file that removes superuser package and that would make your rom stock again.
4 OR flash custom ROM, which usually includes superuser package. Of course using custom rom means you no longer have stock rom.
To have a backup of original ROM, you would :
1 Unlock bootloader,
2 Flash (install) custom recovery
3 superuser doesn't matter here
4 Use custom recovery function to back up your stock ROM.
I want to know the answers to the rest of your questions as well as some clarifications to mine.
Personally, I am looking for a way to backup the stock recovery as well.
I know there are some people asking about this. The procedure appears to be as follows:
(pieced together so don't take it as a tutorial)
1 Unlock bootloader (again, unclear on this. Also some mention S-OFF and others don't)
2 With USB debugging allowed (meaning connect as device requiring a driver), Connect to a PC with ABD, and a driver installed.
3 From ADB, issue a command "adb boot recoveryimage.name" instead of the usual "adb flash recoveryimage.name".
This will make the phone boot into a custom recovery image that is residing on PC, without first writing it to the phone.
4 Unclear how, but make that custom recovery now being live to back up stock rom to pc.
5 Unclear how, but make that custom recovery now being live to flash either root or custom rom to the phone.
6 Disconnect, reboot the phone. Once in OS, use root privileges to mount recovery partition ? (this makes it visible as drive)
7 Don't know how, but use root privileges to back up now visible stock recovery partition to PC as image.
( This should give you two out of three original parts.)
Keep in mind that even if my peace-by-peace "know-how" ever works, there is at least one clearly faulty step:
The back up of the original state of the boot loader has been never made. I do not know if it is easily can be toggled back and forth from lock to unlock and back without leaving any trace. Also, like yourself, I probably don't quite understand what am I talking about, but I have tried to make as much sense of what I have read here and there.
This is my first smart phone, and my experience with linux is limited to building a minecraft server on MineOS, which was pre-made so that not much was required to make it run. I have "mounted" a partition for the first time last week, trying to break Win7recovery, booting it with Knoppix. This is why I think this is probably will come in play here too, as the recovery partition on W7 was hidden. Until then I didn't understand what mounting means, as windows always does it for you. So, take everything I say with a bunch of salt.
Please, let me know too, if you find out more. I want to flash the hell out of my Prism, but I want to be smart about it.
Click to expand...
Click to collapse

check here
All your answers can be found here: [REF] [GUIDE] Welcome to your device, the Galaxy S III. For more XDA related issues check here: [GUIDE] - XDA New User Guide - Getting started on XDA
Good Luck!
mf2112
XDA Moderator
ASharpEdge said:
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er
Click to expand...
Click to collapse

Thanks mf2112. But those resources are seem only for GS3. And it seems it is not teaching us to backup our stock ROMs, it provides stock ROMs for us to download instead. Is there a general way to backup our stock ROMs?
Thanks,
midnite_
mf2112 said:
All your answers can be found here: [REF] [GUIDE] Welcome to your device, the Galaxy S III. For more XDA related issues check here: [GUIDE] - XDA New User Guide - Getting started on XDA
Good Luck!
mf2112
XDA Moderator
Click to expand...
Click to collapse

You must unlock your bootloader then flash a custom recovery. You will then use that custom recovery to make a backup of your rom. That backup will be stored on your sd card.
Now, I have tried to help you and so have a couple other folks. You expect us to just give you answers step by step. I am sorry but this is simply not how XDA works. XDA is set up in a way which makes it for any users to find quickly what they want to know. Use the search feature on the site and you will find many answers. I tell you to go do your own research now and be proud of what you learn on your own. And if you cannot, please do not try to modify your phone further, you may just brick it if you aren't careful.

midnite_ said:
Thanks mf2112. But those resources are seem only for GS3. And it seems it is not teaching us to backup our stock ROMs, it provides stock ROMs for us to download instead. Is there a general way to backup our stock ROMs?
Thanks,
midnite_
Click to expand...
Click to collapse
I put in the GS3 links since the OP was using that phone. Every phone will be different so I don't think a general way or guide would be practical.
Sent from my HTC Sensation 4G using xda premium

[Q] How to restore phone from backup made prior to ROM download

http://forum.xda-developers.com/showthread.php?t=1875914
Hi I used the above guide to root my phone and I also did the backup from recovery mode thing AND I backed my phone up with Kies on my computer beforehand. Well I messed my phone up and had to use Odin to restore it and now I'd like to see how I can restore my phone from the backup I made in recovery mode. Every time I try to backup using kies it crashes on my computer. Also, if possible, I'd like to know a way to not have to use the same app I used to back the phone up to restore it. I used an app called EZ Recovery or something like that. If someone could help with this I'd appreciate it thank you!

gamer6592 said:
http://forum.xda-developers.com/showthread.php?t=1875914
Hi I used the above guide to root my phone and I also did the backup from recovery mode thing AND I backed my phone up with Kies on my computer beforehand. Well I messed my phone up and had to use Odin to restore it and now I'd like to see how I can restore my phone from the backup I made in recovery mode. Every time I try to backup using kies it crashes on my computer. Also, if possible, I'd like to know a way to not have to use the same app I used to back the phone up to restore it. I used an app called EZ Recovery or something like that. If someone could help with this I'd appreciate it thank you!
Click to expand...
Click to collapse
So currently you are unrooted and still using the Odin factory rom? If so, the first steps are to:
1) Re-root
2) Unlock your bootloader using EZ Unlock v1.2 found here: http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
3) Custom Recovery backup files are proprietary, they only will restore using the same recovery you used. For the GSIII, you have two custom recoveries to use: ClockWorkMod or TWRP. If you want to restore to your previous backup that you made using your linked guide, then EZ Recovery will be the absolute easiest to use.
Two questions:
A) Why don't you want to use EZ Recovery? It's the easiesr way to install CWM recovery and you only use it once.
B) Which recovery did you select to make a backup using EZ Recovery? Was it touch based?
3) [Edit] Disregard my question about Kies, I believe I misinterpreted what you asked.
Sent from my SCH-I535 using xda-developers app

SlimSnoopOS said:
So currently you are unrooted and still using the Odin factory rom? If so, the first steps are to:
1) Re-root
2) Unlock your bootloader using EZ Unlock v1.2 found here:
3) Custom Recovery backup files are proprietary, they only will restore using the same recovery you used. For the GSIII, you have two custom recoveries to use: ClockWorkMod or TWRP. If you want to restore to your previous backup that you made using your linked guide, then EZ Recovery will be the absolute easiest to use.
Two questions:
A) Why don't you want to use EZ Recovery? It's the easiesr way to install CWM recovery and you only use it once.
B) Which recovery did you select to make a backup using EZ Recovery? Was it touch based?
3) [Edit] Disregard my question about Kies, I believe I misinterpreted what you asked.
Sent from my SCH-I535 using xda-developers app
Click to expand...
Click to collapse
The reason I didn't want to use EZ Recovery is because I thought it was an app that requires root, and I didn't want to root anymore because I thought that was why my phone jacked up in the first place, even though it was probably just because I'm dumb.
I did the backup as explained in that guide, as well as the one explained in the video I have posted. I didn't know if they were both necessary or if they were different types of backups or something so I did them both. Neither were touch based. The only thing that was touch based was when I touched the part in the apps to go into the recovery mode that I used to backup my phone. One just said to click on "backup" the other tutorial said click on "backup to ext sd card" so I did both. Both were initiated through the recovery mode thing though where you use the volume buttons and the power button. Thank you for the help!
Edit: I realized I can't link so if you go to "that place where you broadcast yourself" and after it says "watch?" And "v [equals]" in the link, paste the following: cgvEYCXHy7k&sns=em
(Sorry I deleted the link and it still kept saying I had a link in here I didn't know what was triggering it. Lol)

gamer6592 said:
The reason I didn't want to use EZ Recovery is because I thought it was an app that requires root, and I didn't want to root anymore because I thought that was why my phone jacked up in the first place, even though it was probably just because I'm dumb.
Click to expand...
Click to collapse
Well if you want to restore to that exact ClockWorkMod (CWM) backup, you do in fact need to be rooted. Even if you don't want to do anything else.
Just reboot into recovery using EZ Recovery, select "Backup and restore," then restore your backup. It's relatively easy honestly.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Well if you want to restore to that exact ClockWorkMod (CWM) backup, you do in fact need to be rooted. Even if you don't want to do anything else.
Just reboot into recovery using EZ Recovery, select "Backup and restore," then restore your backup. It's relatively easy honestly.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
SlimSnoopOS said:
Well if you want to restore to that exact ClockWorkMod (CWM) backup, you do in fact need to be rooted. Even if you don't want to do anything else.
Just reboot into recovery using EZ Recovery, select "Backup and restore," then restore your backup. It's relatively easy honestly.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Okay thanks I'll do that. I suppose it can't hurt to do it again. If it does I'll just have to restore my phone yet again. Couple questions though:
1: Is my phone any different right now since I used that Odin thing? I honestly didn't know what it was. I just looked up how to unbrick your phone because I tried downloading jelly bean and I got that software not authorized by verizon message so I followed another youtube video's tutorial and they said download that app and do a bunch of other stuff with it.
2: http://forum.xda-developers.com/showthread.php?t=1840414
In this thread, his first link (Titled "this page") has a bunch of things called nightlies. Wtf are those? Just a crap load of re-issued versions of the same software (jelly bean)? Are they all from trusted developers or could anybody post one there? Should I take any precautions in making sure I don't get a messed up version/virus? I would assume in that video I referenced, the two downloads he was talking about were just the top/newest "nightly" in that link and the other download he was talking about (GAPPS or Google Apps) is the second one from the top in that other link, right? The one that says it's for Android Version 4.1.x?
3: In that first link I sent you, the guide to rooting, at the bottom it says that rooting and bootloader unlocking are completely finished but the reason everyone says they think my phone messed up and gave me the unauthorized software message was because I didn't unlock my bootloader. There is a second link in the jelly bean download guide for downloading a different boot unlocker. Is that the one I should be downloading? Should I do that on top of everything else I did in that rooting guide?
4 (last question I promise): Also, in that bootloader unlocker he said I should really "know what I'm doing" if I am running windows because it was intended for Mac and Linux. I run windows and I really don't want to run linux or Ubuntu or anything and i don't have a Mac. I haven't actually downloaded or tried to run the BL unlocker yet but I mean is it really that hard to use on Windows? I know it may sound quite hard to believe because of how much of an idiot I sound like when it comes to rooting and crap but I really AM, at least in my opinion, quite good with computers. At the very least as far as fundamentals go. But yeah when it comes to programming and all this stuff, I'm as dumb as a rock. But what does "know what I'm doing" mean? Is the BL Unlocker you linked to different? Should I just use yours?
Thanks man you're the ****.

gamer6592 said:
Okay thanks I'll do that. I suppose it can't hurt to do it again. If it does I'll just have to restore my phone yet again. Couple questions though:
1: Is my phone any different right now since I used that Odin thing? I honestly didn't know what it was. I just looked up how to unbrick your phone because I tried downloading jelly bean and I got that software not authorized by verizon message so I followed another youtube video's tutorial and they said download that app and do a bunch of other stuff with it.
Click to expand...
Click to collapse
Whenever you use Odin, it's primarily to return to stock or flash a modified image to your Samsung device. In essence what you want to only use Odin for, is to return to the way you purchased your phone: fresh out of the box. You "should" be on a stock image if that's what resolved your previous issue which led to you creating this thread. In all honesty, I'm amazed that you fixed your phone via youtube. Going forward, all that you need to know about the Verizon GSIII is here: http://forum.xda-developers.com/showthread.php?t=1762709
Stick to using XDA for now.
2: http://forum.xda-developers.com/showthread.php?t=1840414
In this thread, his first link (Titled "this page") has a bunch of things called nightlies. Wtf are those? Just a crap load of re-issued versions of the same software (jelly bean)? Are they all from trusted developers or could anybody post one there? Should I take any precautions in making sure I don't get a messed up version/virus? I would assume in that video I referenced, the two downloads he was talking about were just the top/newest "nightly" in that link and the other download he was talking about (GAPPS or Google Apps) is the second one from the top in that other link, right? The one that says it's for Android Version 4.1.x?
Click to expand...
Click to collapse
Nightlies = a new version of that rom is updated each night. Some things may break, some things may be fixed but from nightly to nightly, there are new things introduced and new things broken. A nightly is essentially a prolonged "beta" of the overall rom. You can update from one nightly to another or even choose to update weekly if that works best for you, it's all about choice. Now in regards to CM10, CM10 = CyanogenMod10. This is the most popular Android rom and is supported on the most amount of Android phones. The [OFFICIAL] Verizon GSIII CM10 rom is one rom that is pulling software and improvements that are being worked on hourly by the "lead" or primary CyanogenMod team. If that doesn't make sense, the Verizon GSIII version of CM10 is one branch from the giant, ever growing tree that is CyanogenMod.
The "OP" or original post is the very first post, on the first page of any thread. It is also labeled #1. So, the OP of your thread would be your initial post which I responded to. When reading rom threads, the OP is where all the primary information and download links are. People will use this term all the time. I'm just dropping knowledge on this for future reference.
Usually, developers or respected developers have that title just below their name. For example, look at my name and it does not say "recognized developer." This is a title granted by the awesome people that run XDA to people who apply for this title. If accepted, this is a label that informs new users that this is someone of knowledge. Now, if someone doesn't have this title, then this does not mean they did not develop said rom or that they do not know what they're doing. Anyone can be a developer, but just know that there are people here who will easily put you in your place if you pretend to be one.
The thing about XDA is, you download anything and everything at your own risk. By modifying your phone software, you and you alone voided your warranty and accept this. Now, to answer your question. The OP in any thread that is in the Development or Original Development section is supposed to be a "true and reliable" link. If there were ever a virus or malware posted in the Development section, this is unquestionably a website that will remove it. For any and every phone that has a forum on XDA, there are moderators (or mods) who patrol and work for XDA to keep this place awesome, concise, and welcoming to new and old users alike. If you look at any given world/regional/carrier phone, there are a team of moderators who govern those entire threads. Sure, someone can post a spam link at any time but you should feel relatively safe knowing that there are people in place to control for those things. Now, if you see links ANYWHERE else, then I don't suggest downloading it unless you see others have done so as well and provided significant feedback as well.
This is by no means a rule but if a thread has over maybe 30 pages, then it's something that many others have used. Read a few pages if you have any doubts. The most recent posts about the rom are always at the end of the thread. The CM10 link that you posted has over 600 pages...it's trusted lol. The nicest way to say this is...the most popular roms may be the threads with the most pages.
Also, stick to downloading roms from XDA or Rootzwiki and download only what you feel comfortable with downloading to your phone. You mentioned a youtube video earlier, disregard it and refer to DroidStyle's Guide that I linked after your first question. Rooting may not be for you and that is perfectly fine because this is a hobby. As you can tell, there's a LOT to learn and I've barely scratched the surface.
3: In that first link I sent you, the guide to rooting, at the bottom it says that rooting and bootloader unlocking are completely finished but the reason everyone says they think my phone messed up and gave me the unauthorized software message was because I didn't unlock my bootloader. There is a second link in the jelly bean download guide for downloading a different boot unlocker. Is that the one I should be downloading? Should I do that on top of everything else I did in that rooting guide?
Click to expand...
Click to collapse
To properly unlock the bootloader on the GSIII, you need to be rooted first then you need to download EZ Recovery v1.2. I provided and labeled that in a prior post. The "unauthorized software" message occurred because you (I am assuming btw) watched that youtube video from July which predates when our bootloader was officially unlocked (August) and followed its instructions. Since our bootloader was unlocked on August 15, 2012: you must be rooted and unlocked prior to flashing roms or kernels.
You can use that thread to root BUT for the sake of helping you, just download EZ Unlock v1.2 (bootloader unlock tool) that I linked to on Rootzwiki.
4 (last question I promise): Also, in that bootloader unlocker he said I should really "know what I'm doing" if I am running windows because it was intended for Mac and Linux. I run windows and I really don't want to run linux or Ubuntu or anything and i don't have a Mac. I haven't actually downloaded or tried to run the BL unlocker yet but I mean is it really that hard to use on Windows? I know it may sound quite hard to believe because of how much of an idiot I sound like when it comes to rooting and crap but I really AM, at least in my opinion, quite good with computers. At the very least as far as fundamentals go. But yeah when it comes to programming and all this stuff, I'm as dumb as a rock. But what does "know what I'm doing" mean? Is the BL Unlocker you linked to different? Should I just use yours?
Thanks man you're the ****.
Click to expand...
Click to collapse
Because I do not want to confuse you further, the only bootloader unlock tool you need to know of is EZ Unlock v1.2 which is located on Rootzwiki. If you rooted with your laptop, just install EZ Unlock v1.2 and press "Unlock." You only need to do this one time and can uninstall the app afterwards.
To restore your CWM backup, you need to:
1) Root
2) Unlock via EZ Unlock v1.2
3) Install CWM using EZ Recovery
4) Reboot into recovery
5) Restore your backup in CWM recovery
6) Enjoy your backiup predating the triangle warning "Unauthorized software on this device" incident
Did I cover everything? haha

SlimSnoopOS said:
Whenever you use Odin, it's primarily to return to stock or flash a modified image to your Samsung device. In essence what you want to only use Odin for, is to return to the way you purchased your phone: fresh out of the box. You "should" be on a stock image if that's what resolved your previous issue which led to you creating this thread. In all honesty, I'm amazed that you fixed your phone via youtube. Going forward, all that you need to know about the Verizon GSIII is here: http://forum.xda-developers.com/showthread.php?t=1762709
Stick to using XDA for now.
Nightlies = a new version of that rom is updated each night. Some things may break, some things may be fixed but from nightly to nightly, there are new things introduced and new things broken. A nightly is essentially a prolonged "beta" of the overall rom. You can update from one nightly to another or even choose to update weekly if that works best for you, it's all about choice. Now in regards to CM10, CM10 = CyanogenMod10. This is the most popular Android rom and is supported on the most amount of Android phones. The [OFFICIAL] Verizon GSIII CM10 rom is one rom that is pulling software and improvements that are being worked on hourly by the "lead" or primary CyanogenMod team. If that doesn't make sense, the Verizon GSIII version of CM10 is one branch from the giant, ever growing tree that is CyanogenMod.
The "OP" or original post is the very first post, on the first page of any thread. It is also labeled #1. So, the OP of your thread would be your initial post which I responded to. When reading rom threads, the OP is where all the primary information and download links are. People will use this term all the time. I'm just dropping knowledge on this for future reference.
Usually, developers or respected developers have that title just below their name. For example, look at my name and it does not say "recognized developer." This is a title granted by the awesome people that run XDA to people who apply for this title. If accepted, this is a label that informs new users that this is someone of knowledge. Now, if someone doesn't have this title, then this does not mean they did not develop said rom or that they do not know what they're doing. Anyone can be a developer, but just know that there are people here who will easily put you in your place if you pretend to be one.
The thing about XDA is, you download anything and everything at your own risk. By modifying your phone software, you and you alone voided your warranty and accept this. Now, to answer your question. The OP in any thread that is in the Development or Original Development section is supposed to be a "true and reliable" link. If there were ever a virus or malware posted in the Development section, this is unquestionably a website that will remove it. For any and every phone that has a forum on XDA, there are moderators (or mods) who patrol and work for XDA to keep this place awesome, concise, and welcoming to new and old users alike. If you look at any given world/regional/carrier phone, there are a team of moderators who govern those entire threads. Sure, someone can post a spam link at any time but you should feel relatively safe knowing that there are people in place to control for those things. Now, if you see links ANYWHERE else, then I don't suggest downloading it unless you see others have done so as well and provided significant feedback as well.
This is by no means a rule but if a thread has over maybe 30 pages, then it's something that many others have used. Read a few pages if you have any doubts. The most recent posts about the rom are always at the end of the thread. The CM10 link that you posted has over 600 pages...it's trusted lol. The nicest way to say this is...the most popular roms may be the threads with the most pages.
Also, stick to downloading roms from XDA or Rootzwiki and download only what you feel comfortable with downloading to your phone. You mentioned a youtube video earlier, disregard it and refer to DroidStyle's Guide that I linked after your first question. Rooting may not be for you and that is perfectly fine because this is a hobby. As you can tell, there's a LOT to learn and I've barely scratched the surface.
To properly unlock the bootloader on the GSIII, you need to be rooted first then you need to download EZ Recovery v1.2. I provided and labeled that in a prior post. The "unauthorized software" message occurred because you (I am assuming btw) watched that youtube video from July which predates when our bootloader was officially unlocked (August) and followed its instructions. Since our bootloader was unlocked on August 15, 2012: you must be rooted and unlocked prior to flashing roms or kernels.
You can use that thread to root BUT for the sake of helping you, just download EZ Unlock v1.2 (bootloader unlock tool) that I linked to on Rootzwiki.
Because I do not want to confuse you further, the only bootloader unlock tool you need to know of is EZ Unlock v1.2 which is located on Rootzwiki. If you rooted with your laptop, just install EZ Unlock v1.2 and press "Unlock." You only need to do this one time and can uninstall the app afterwards.
To restore your CWM backup, you need to:
1) Root
2) Unlock via EZ Unlock v1.2
3) Install CWM using EZ Recovery
4) Reboot into recovery
5) Restore your backup in CWM recovery
6) Enjoy your backiup predating the triangle warning "Unauthorized software on this device" incident
Did I cover everything? haha
Click to expand...
Click to collapse
Lol. PERFECT. Last couple loose ends though.
1: Will the restore take me to the last time I did all this recovery mode backup crap? The main reason I'm concerned about all this is because I have a game I've put hundreds of hours into that I'm trying to recover my progress on. I'd like it though if when I do restore, I still remain rooted because once I retrieve my game I'd like to try once more to get JB.
2: Is there a way, if my recovery is successful, to get Jelly Bean and THEN recover all this?
Yet again, you rock man. Lol Thanks
Edit: I restored anyways and THANK GOD found that my game save data was still intact. Everything is exactly the way I had it, with root and everything. So NOW my only questions are:
1: Since i rooted my phone the way in the guide I linked to the first time and then the second time I did it the way your guide link said, but the restore was made from the first time I rooted, is that restore I just did from your guide completely gone and now my phone is 100% back to as if I hadn't done anything else after rooting it my way yesterday? If so, should I root my phone yet again except doing it the way your guide said to again because apparently the first way I did it from my guide is what messed my phone up initially, right? So what should I do? Just download EZ-Unlock and keep my phone like it is or start all the way over with your method?
2: Since it was possible to retrieve my game save data with my previous root, do you think if I root again successfully or w/e I need to do and then get Jelly Bean, that my save data and stuff will transfer over as is to Jelly Bean also?

gamer6592 said:
2: Is there a way, if my recovery is successful, to get Jelly Bean and THEN recover all this?
Yet again, you rock man. Lol Thanks
Click to expand...
Click to collapse
Yes, you just restored using CWM correct? First step would be to download "titanium backup" via the Play Store and now you can back up app data (don't do system data) so that when you wipe/flash roms you can restore that app data. Last time I used the free version (a year ago) the free version did app backups/restore but app restores were one at a time and you have to tap install for each app. The paid version (proud paid user here!) does app restore without you having to press "install" for each app you're restoring. There are other app backup utilities but this is likely the most popular and most powerful. You will have to manually recreate your homescreen layout.
Step 2 would be to download a rom, boot into recovery, factory reset then wipe dalvik cache, then flash your rom. Once the rom boots up and you've signed into Gmail, re-download Titanium Backup and restore your apps.
If you were to try this of course.
Edit: I restored anyways and THANK GOD found that my game save data was still intact. Everything is exactly the way I had it, with root and everything. So NOW my only questions are:
1: Since i rooted my phone the way in the guide I linked to the first time and then the second time I did it the way your guide link said, but the restore was made from the first time I rooted, is that restore I just did from your guide completely gone and now my phone is 100% back to as if I hadn't done anything else after rooting it my way yesterday? If so, should I root my phone yet again except doing it the way your guide said to again because apparently the first way I did it from my guide is what messed my phone up initially, right? So what should I do? Just download EZ-Unlock and keep my phone like it is or start all the way over with your method?
Click to expand...
Click to collapse
If you just did a restore via CWM, you're still rooted. Have any doubts? Download "Root Checker" from the Play Store and it will tell you if you're rooted. Your CWM backup is already rooted, you need to be rooted to install a custom recovery so you're set. The CWM restore file is actually located on sdcard/ClockWorkMod/Backup (or something to that effect) and onside should be a file name that contains "1970" and resembles a calendar date. The date is wrong, unfortunately that's just how recovery is. I'm not sure how to rename CWM backups because doing so incorrectly changes the file integrity and will cause your CWM restore to fail should you try restoring it. Your CWM restore file does not delete itself once you use it, it continues to take up space and sits there until you need it or you delete it using CWM.
What messed you up the first time was the fact that you didn't unlock your bootloader before flashing CM10. There's nothing wrong with the CWM backup that you have. Do you have just the one CWM backup or two?
TWRP recovery allows you to name backups but I wouldn't get into that until you're more familiar with CWM and the flashing process.
2: Since it was possible to retrieve my game save data with my previous root, do you think if I root again successfully or w/e I need to do and then get Jelly Bean, that my save data and stuff will transfer over as is to Jelly Bean also?
Click to expand...
Click to collapse
I definitely do and you don't need to root again btw.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Whenever you use Odin, it's primarily to return to stock or flash a modified image to your Samsung device. In essence what you want to only use Odin for, is to return to the way you purchased your phone: fresh out of the box. You "should" be on a stock image if that's what resolved your previous issue which led to you creating this thread. In all honesty, I'm amazed that you fixed your phone via youtube. Going forward, all that you need to know about the Verizon GSIII is here: http://forum.xda-developers.com/showthread.php?t=1762709
Stick to using XDA for now.
Nightlies = a new version of that rom is updated each night. Some things may break, some things may be fixed but from nightly to nightly, there are new things introduced and new things broken. A nightly is essentially a prolonged "beta" of the overall rom. You can update from one nightly to another or even choose to update weekly if that works best for you, it's all about choice. Now in regards to CM10, CM10 = CyanogenMod10. This is the most popular Android rom and is supported on the most amount of Android phones. The [OFFICIAL] Verizon GSIII CM10 rom is one rom that is pulling software and improvements that are being worked on hourly by the "lead" or primary CyanogenMod team. If that doesn't make sense, the Verizon GSIII version of CM10 is one branch from the giant, ever growing tree that is CyanogenMod.
The "OP" or original post is the very first post, on the first page of any thread. It is also labeled #1. So, the OP of your thread would be your initial post which I responded to. When reading rom threads, the OP is where all the primary information and download links are. People will use this term all the time. I'm just dropping knowledge on this for future reference.
Usually, developers or respected developers have that title just below their name. For example, look at my name and it does not say "recognized developer." This is a title granted by the awesome people that run XDA to people who apply for this title. If accepted, this is a label that informs new users that this is someone of knowledge. Now, if someone doesn't have this title, then this does not mean they did not develop said rom or that they do not know what they're doing. Anyone can be a developer, but just know that there are people here who will easily put you in your place if you pretend to be one.
The thing about XDA is, you download anything and everything at your own risk. By modifying your phone software, you and you alone voided your warranty and accept this. Now, to answer your question. The OP in any thread that is in the Development or Original Development section is supposed to be a "true and reliable" link. If there were ever a virus or malware posted in the Development section, this is unquestionably a website that will remove it. For any and every phone that has a forum on XDA, there are moderators (or mods) who patrol and work for XDA to keep this place awesome, concise, and welcoming to new and old users alike. If you look at any given world/regional/carrier phone, there are a team of moderators who govern those entire threads. Sure, someone can post a spam link at any time but you should feel relatively safe knowing that there are people in place to control for those things. Now, if you see links ANYWHERE else, then I don't suggest downloading it unless you see others have done so as well and provided significant feedback as well.
This is by no means a rule but if a thread has over maybe 30 pages, then it's something that many others have used. Read a few pages if you have any doubts. The most recent posts about the rom are always at the end of the thread. The CM10 link that you posted has over 600 pages...it's trusted lol. The nicest way to say this is...the most popular roms may be the threads with the most pages.
Also, stick to downloading roms from XDA or Rootzwiki and download only what you feel comfortable with downloading to your phone. You mentioned a youtube video earlier, disregard it and refer to DroidStyle's Guide that I linked after your first question. Rooting may not be for you and that is perfectly fine because this is a hobby. As you can tell, there's a LOT to learn and I've barely scratched the surface.
To properly unlock the bootloader on the GSIII, you need to be rooted first then you need to download EZ Recovery v1.2. I provided and labeled that in a prior post. The "unauthorized software" message occurred because you (I am assuming btw) watched that youtube video from July which predates when our bootloader was officially unlocked (August) and followed its instructions. Since our bootloader was unlocked on August 15, 2012: you must be rooted and unlocked prior to flashing roms or kernels.
You can use that thread to root BUT for the sake of helping you, just download EZ Unlock v1.2 (bootloader unlock tool) that I linked to on Rootzwiki.
Because I do not want to confuse you further, the only bootloader unlock tool you need to know of is EZ Unlock v1.2 which is located on Rootzwiki. If you rooted with your laptop, just install EZ Unlock v1.2 and press "Unlock." You only need to do this one time and can uninstall the app afterwards.
To restore your CWM backup, you need to:
1) Root
2) Unlock via EZ Unlock v1.2
3) Install CWM using EZ Recovery
4) Reboot into recovery
5) Restore your backup in CWM recovery
6) Enjoy your backiup predating the triangle warning "Unauthorized software on this device" incident
Did I cover everything? haha
Click to expand...
Click to collapse
Okay awesome. Haha. Perfect. I am wanting to try doing jelly bean again. I'm kinda lost though. That guide doesn't explain ****. So I go to that nightlies page and just download the top one, right? And then download the second from top GAPPS thing in that other link? I download them i.e throw them on my phone or ext SD card from my computer, right? If I do this I'd like to make another backup on my phone because I've even gotten more data on it since I just recovered my backup, but I don't want to have 2 backups just sitting there using up so much memory. How do I delete the old one and replace it with a new and more current one? Will anything mess up if I delete the old one? Also, I made both backups, the "backup" option one from the recovery mode screen, as well as the "backup to external SD card" option one from the same screen so I'd like to delete them both and just make a new one.
When I installed that app and just simply clicked the unlock button, that unlocked my bootloader, right? I keep hearing the word unlock so I can't help but feel like there's multiple things I need to be "unlocking."
So at this point, other than doing a fresher backup, the only thing I have to do is download the top nightly thing or w/e and that GAPPS thing to my computer, then drag them to the folder for either my internal memory or my EXT SD card? Then what do I do? I know I have to execute them from that recovery mode thing but which app do I use to enter recovery mode? Does it matter?
EDIT: Also, I downloaded and bought Titanium Backup and this thing is like trying to learn a foreign language. Wtf am I even supposed to be doing with it? Lol.

gamer6592 said:
Okay awesome. Haha. Perfect. I am wanting to try doing jelly bean again. I'm kinda lost though. That guide doesn't explain ****. So I go to that nightlies page and just download the top one, right? And then download the second from top GAPPS thing in that other link? I download them i.e throw them on my phone or ext SD card from my computer, right?
Click to expand...
Click to collapse
Aight, my question to you is do you like TouchWiz? Because any AOSP rom (CyanogenMod, AOKP, Codename Android, etc.) will basically have the interface/UI of a Google Galaxy Nexus or a Nexus 4. It will not have anything Samsung related. Is this ok? If so, read on.
GApps = Google apps. When you see the GApps page, there should be a few dozen to choose from.
You have the proper steps. Once you download the AOSP rom and respective GApps, move these two zips outside of any folder on either your internal or external sd card. I'm going to stop here and tell you to backup your IMEI, which you only need to do this one time. Everything you need to know is described in this thread. Backup your IMEI:
http://forum.xda-developers.com/showthread.php?t=1852255
If I do this I'd like to make another backup on my phone because I've even gotten more data on it since I just recovered my backup, but I don't want to have 2 backups just sitting there using up so much memory. How do I delete the old one and replace it with a new and more current one? Will anything mess up if I delete the old one? Also, I made both backups, the "backup" option one from the recovery mode screen, as well as the "backup to external SD card" option one from the same screen so I'd like to delete them both and just make a new one.
Click to expand...
Click to collapse
Nope, nothing messes up. Just boot into CWM, go to "backup and restore," and delete the previous backups. Once it deletes them, select the option for "Free up space" for your internal sd card, then do this once more for your external sd card if you deleted backups. Now, make a new backup. I suggest keeping at least an old CWM backup or this new CWM from today on a computer in case of unforeseen issues down the road. This file will still be incomprehensible in the sense that the date on the zip is from 1970 and is off by at least 2-3 months.
When I installed that app and just simply clicked the unlock button, that unlocked my bootloader, right? I keep hearing the word unlock so I can't help but feel like there's multiple things I need to be "unlocking."
Click to expand...
Click to collapse
Correct. It doesn't do anything more once you've selected "unlock." It serves one function, to unlock your bootloader.
So at this point, other than doing a newerbackup, the only thing I have to do is download the top nightly thing or w/e and that GAPPS thing to my computer, then drag them to the folder for either my internal memory or my EXT SD card? Then what do I do? I know I have to execute them from that recovery mode thing but which app do I use to enter recovery mode? Does it matter?
Click to expand...
Click to collapse
Yes, but first I need you to backup your IMEI. Once you've successfully done this, I or someone else will tell you how to wipe/install your first rom.
EDIT: Also, I downloaded and bought Titanium Backup and this thing is like trying to learn a foreign language. Wtf am I even supposed to be doing with it? Lol.
Click to expand...
Click to collapse
To backup app data
1) Open Titanium Backup
2)Tap "Backup/Restore"
3) Tap "Click to edit filters." Make sure "Filter by status" is set to "All", make sure "Filter by type" is set to "User" only. Press the green check mark on the upper right corner. What this does is filter the apps that show and limits them to just the user apps: apps that you downloaded and apps that came with the phone.
4) You should see a list of your apps now. Right? Good, now tap the grey checkmark on the top right then on this new screen tap "Run" for "Backup all user apps."
5) This new list of apps should have checkmarks next to them. Uncheck whichever apps that you do not want to backup. I usually Uncheck Google Apps because that data is backed up to the cloud. Everything checked will be backed up, tap the green checkmark to begin your backup and you're done.
To restore apps, do Step 3 but instead select "backed up" for "Filter by Status" and select "Uninstalled" for "Filter by type." Then for Step 4, scroll down and tap "Run" for "Restore missing apps with data." I strongly suggest only restoring just that one game's data and maybe a few apps to minimize any issues that will occur once you use the rom.
**This does not backup texts nor phone calls.
Most importantly, only download roms to your phone if it states: d2vzw or SCH-i535. This is our device's model name.

SlimSnoopOS said:
Aight, my question to you is do you like TouchWiz? Because any AOSP rom (CyanogenMod, AOKP, Codename Android, etc.) will basically have the interface/UI of a Google Galaxy Nexus or a Nexus 4. It will not have anything Samsung related. Is this ok? If so, read on.
GApps = Google apps. When you see the GApps page, there should be a few dozen to choose from.
You have the proper steps. Once you download the AOSP rom and respective GApps, move these two zips outside of any folder on either your internal or external sd card. I'm going to stop here and tell you to backup your IMEI, which you only need to do this one time. Everything you need to know is described in this thread. Backup your IMEI:
http://forum.xda-developers.com/showthread.php?t=1852255
Nope, nothing messes up. Just boot into CWM, go to "backup and restore," and delete the previous backups. Once it deletes them, select the option for "Free up space" for your internal sd card, then do this once more for your external sd card if you deleted backups. Now, make a new backup. I suggest keeping at least an old CWM backup or this new CWM from today on a computer in case of unforeseen issues down the road. This file will still be incomprehensible in the sense that the date on the zip is from 1970 and is off by at least 2-3 months.
Correct. It doesn't do anything more once you've selected "unlock." It serves one function, to unlock your bootloader.
Yes, but first I need you to backup your IMEI. Once you've successfully done this, I or someone else will tell you how to wipe/install your first rom.
To backup app data
1) Open Titanium Backup
2)Tap "Backup/Restore"
3) Tap "Click to edit filters." Make sure "Filter by status" is set to "All", make sure "Filter by type" is set to "User" only. Press the green check mark on the upper right corner. What this does is filter the apps that show and limits them to just the user apps: apps that you downloaded and apps that came with the phone.
4) You should see a list of your apps now. Right? Good, now tap the grey checkmark on the top right then on this new screen tap "Run" for "Backup all user apps."
5) This new list of apps should have checkmarks next to them. Uncheck whichever apps that you do not want to backup. I usually Uncheck Google Apps because that data is backed up to the cloud. Everything checked will be backed up, tap the green checkmark to begin your backup and you're done.
To restore apps, do Step 3 but instead select "backed up" for "Filter by Status" and select "Uninstalled" for "Filter by type." Then for Step 4, scroll down and tap "Run" for "Restore missing apps with data." I strongly suggest only restoring just that one game's data and maybe a few apps to minimize any issues that will occur once you use the rom.
**This does not backup texts nor phone calls.
Most importantly, only download roms to your phone if it states: d2vzw or SCH-i535. This is our device's model name.
Click to expand...
Click to collapse
Gosh this is a pain in my ass... I've been working on this ALL DAY. Kid you not.
I finally just figured out how to do everything with downloading that ADB crap and I am doing part B (SynergyROM's "Plan B" manual backup). I am really worried because I have a slight problem... Now whenever I boot into recovery mode (holding volume up+home+power) it doesn't look the same as when it did the previous times i had to boot into recovery. The options are completely different and there isn't one for "install zip from sd card". Following is a description of what it says/how it looks now:
(it says the following in blue letters)
"ANDROID SYSTEM RECOVERY <3e>
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache"
____________________________________________________________
(then it says the following in yellow letters)
# manual mode #
-- Applying Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC
And it has that picture of the android in the background with the thing that looks like you could twist it on it's back and the hologram coming out of it's front.
Why is my recovery mode different all of a sudden? It's like I'm just getting the standard Android version of RM now.
EDIT: I clicked "flash CWM Recovery" and now it boots into the regular CWM RM screen.
Okay. I'm all done with the IMEI backups and stuff.
I can haz Jelly Bean now?
Man I wish there was an IM or something I could contact you at so I didn't have to have you keep coming back to this thread so many times. Plus, I'm impatient. I want JB already! Lol. I appreciate it though!

Go haz your jellybeans! Lol sorry for the delayed response, I just got off work. Keep a backup of the Synergy folder (the backed up IMEI file) on your laptop for safe keeping.
As a reminder, this AOSP rom you're installing is stock Jellybean aka what's on a Galaxy Nexus or Nexus 4.
To flash a rom:
1) boot into CWM recovery
2) Factory reset, wipe cache, go into "Advanced" and wipe Dalvik Cache
3) Install rom. If you're installing CM10, AOKP, or any Android Open Source Project (A.O.S.P.) rom then install GApps as well.
4) Reboot and enjoy.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Aight, my question to you is do you like TouchWiz? Because any AOSP rom (CyanogenMod, AOKP, Codename Android, etc.) will basically have the interface/UI of a Google Galaxy Nexus or a Nexus 4. It will not have anything Samsung related. Is this ok? If so, read on.
GApps = Google apps. When you see the GApps page, there should be a few dozen to choose from.
You have the proper steps. Once you download the AOSP rom and respective GApps, move these two zips outside of any folder on either your internal or external sd card. I'm going to stop here and tell you to backup your IMEI, which you only need to do this one time. Everything you need to know is described in this thread. Backup your IMEI:
http://forum.xda-developers.com/showthread.php?t=1852255
Nope, nothing messes up. Just boot into CWM, go to "backup and restore," and delete the previous backups. Once it deletes them, select the option for "Free up space" for your internal sd card, then do this once more for your external sd card if you deleted backups. Now, make a new backup. I suggest keeping at least an old CWM backup or this new CWM from today on a computer in case of unforeseen issues down the road. This file will still be incomprehensible in the sense that the date on the zip is from 1970 and is off by at least 2-3 months.
Correct. It doesn't do anything more once you've selected "unlock." It serves one function, to unlock your bootloader.
Yes, but first I need you to backup your IMEI. Once you've successfully done this, I or someone else will tell you how to wipe/install your first rom.
To backup app data
1) Open Titanium Backup
2)Tap "Backup/Restore"
3) Tap "Click to edit filters." Make sure "Filter by status" is set to "All", make sure "Filter by type" is set to "User" only. Press the green check mark on the upper right corner. What this does is filter the apps that show and limits them to just the user apps: apps that you downloaded and apps that came with the phone.
4) You should see a list of your apps now. Right? Good, now tap the grey checkmark on the top right then on this new screen tap "Run" for "Backup all user apps."
5) This new list of apps should have checkmarks next to them. Uncheck whichever apps that you do not want to backup. I usually Uncheck Google Apps because that data is backed up to the cloud. Everything checked will be backed up, tap the green checkmark to begin your backup and you're done.
To restore apps, do Step 3 but instead select "backed up" for "Filter by Status" and select "Uninstalled" for "Filter by type." Then for Step 4, scroll down and tap "Run" for "Restore missing apps with data." I strongly suggest only restoring just that one game's data and maybe a few apps to minimize any issues that will occur once you use the rom.
**This does not backup texts nor phone calls.
Most importantly, only download roms to your phone if it states: d2vzw or SCH-i535. This is our device's model name.
Click to expand...
Click to collapse
SlimSnoopOS said:
Go haz your jellybeans! Lol sorry for the delayed response, I just got off work. Keep a backup of the Synergy folder (the backed up IMEI file) on your laptop for safe keeping.
As a reminder, this AOSP rom you're installing is stock Jellybean aka what's on a Galaxy Nexus or Nexus 4.
To flash a rom:
1) boot into CWM recovery
2) Factory reset, wipe cache, go into "Advanced" and wipe Dalvik Cache
3) Install rom. If you're installing CM10, AOKP, or any Android Open Source Project (A.O.S.P.) rom then install GApps as well.
4) Reboot and enjoy.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Lol. Okay thanks but.. I don't remember if you ever answered me on whether it matters if I drag the thing to my phone or my SD card. And also, if I just download and drag the top "nightly" thing and then download and drag the 2nd from top GAPPS thing. Should I create a folder and put them both in or just leave them out by themselves in the main directory or does it matter?

Just put both the nightly and Gapps on your internal storage for now. Leave them on the root of the sd card (in no folders).
If recovery let's you use your external sd card, then use that if you prefer cuz it doesn't matter. If recovery fails to see your external sd card (meaning it didnt let you perform a backup to the external sd) then it needs to be formatted to Fat32 before you can flash anything off of the external sd.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Just put both the nightly and Gapps on your internal storage for now. Leave them on the root of the sd card (in no folders).
If recovery let's you use your external sd card, then use that if you prefer cuz it doesn't matter. If recovery fails to see your external sd card (meaning it didnt let you perform a backup to the external sd) then it needs to be formatted to Fat32 before you can flash anything off of the external sd.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yay!!! I did it!! You rock man I owe you one. My only other question is how I get everything back on my phone like my apps and app data and stuff. Thanks dude!

gamer6592 said:
Yay!!! I did it!! You rock man I owe you one. My only other question is how I get everything back on my phone like my apps and app data and stuff. Thanks dude!
Click to expand...
Click to collapse
TB = Titanium Backup
Congrats! From my previous post on TB:
To restore apps with TB, do Step 3 but instead select "backed up" for "Filter by Status" and select "Uninstalled" for "Filter by type." Then for Step 4, scroll down and tap "Run" for "Restore missing apps with data." I strongly suggest only restoring just that one game's data and maybe data from a few other apps to minimize any issues that will occur once you use the rom. I rarely have force closes or random issues after restoring apps but that's a risk one takes when restoring apps and app data. If you notice an app is behaving unusually, uninstall it and then re-
download it from the Play Store.
Never restore system data.
Sent from my SCH-I535 using xda app-developers app

lol.. you're gonna hate me but... I'm pretty sure I want to switch back... TB messed up my game data so I can't recover it so I really want to at least recover my entire phone from the CWM backup and THEN maybe go back to jelly bean again because the game I'm playing let's you store your data on their servers so I'd rather do that and THEN come back to jelly bean and restore from their servers... but yeah my game is not working at all :'-( lol.. fml

Just restore your Nandroid backup in CWM then do whatever it was you needed to do
Sent from my SCH-I535 using xda app-developers app

[FAQ] [REF]★ All you need to know about Android | Read this before you post/root ! ★

[FAQ] [REF]★ All you need to know about Android | Read this before you post/root ! ★
Understanding the Android world before rooting your LG Nexus 5
Here is a *noob friendly* collection of information every user that wants to root their phone should know. Many people blindly follow guides without even knowing what "Rooting" means. Hopefully, this will help new users (and old ones, why not?) understand what is happening with their phone, and what they will put up with.
This may seem as a lot to read, but there are no shortcuts. You either read and learn what you're dealing with, or find out the hard way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Contents
Post 1:
★What does rooting mean?
★The advantages of rooting
★The disadvantages of rooting
★What about the internal memory? How does that work?
★Things you hear people talk about
★How to backup your stuff
★Flashing a custom ROM
★ADB and Fastboot
★Restoring your Nexus 5 to STOCK
Post 2:
★Tips and Tricks
★Questions and Misconceptions
Let's get started, shall we?
What does rooting mean?
To 'root' your phone means to gain administrative rights on the file system of your phone (in linux, root is the username of the master admin, kind of being an Administrator on Windows). With root access, you can install and uninstall anything you want on the phone. Android is, in fact, based on Linux.
Most phones come with limited access regarding what you can and can't do on it. This isn't necessarily a bad thing, because it can keep users from accidentally breaking something they shouldn't mess with on the phone, especially in regards to the operating system. However, many manufacturers limit your rights to things that aren't really so mission critical, too, and rooting the phone gets around this.
If you have a few unnecessary applications (bloatware) pre-installed on your phone that you cannot uninstall, rooting will give you this ability. It will also allow you to upgrade to newer versions of Android before your phone's manufacturer and/or cell provider make the updates available to you.
So now you know what rooting means. And I bet you are now thinking "Should I do it, or not?" Well, hope this helps you decide:
The advantages of rooting
-De-bloat your phone. Uninstall any unwanted system apps.
-More control over how the CPU acts. This can increase performance or battery life, depends on how you configure it.
-More control over power consumption. This implies undervolting your CPU, giving it less power, so it consumes less.
-More control over how apps start up. Prevent apps from starting up when they don't need to.
-Change your Baseband (Radio). Try different radio versions, with the purpose of reducing battery drain or improving your signal strength.
-Flash custom ROMs. Bored of the stock ROM and look? Browse through the hundreds of custom ROMs provided by this community, each having different features and looks.
-Backups. The ability to completely backup your phone, and fully restoring it to the time of the backup. This is done with a Nandroid Backup (we'll talk about this later)
-Mods and Inovations. Use many mods, fixes, tweaks or features created by the community!
-Custom Kernels. As a Nexus device, the Nexus 5 will have tons of kernels with different features, supporting better performance, or battery life! To see what a kernel is, keep reading.
-Run apps that need Root Permission. These apps can be very useful, like Titanium Backup, Root Explorer, Terminal Emulator and many others!
The disadvantages of rooting
-Rooting will void your warranty (Although reverting root is very easy)
-The process a bit dangerous. Something could (99.9% probably not, but still) go wrong, and end up bricking your phone. So, yes, the process is 0.1% risky. You can end up deleting everything on your phone. You'll have to handle this process gently and with care.
-You will be able to do a lot more mistakes. These may cause damage to your phone (But hey, that's why we have these kind of threads, eh?)
-No more over the air official updates. You'll have to update your phone manually, through your recovery. (Which isn't that hard)
Now that you fully know what rooting implies, let's continue exploring the Android world.
What about the internal memory? How does that work?
Now, as you might already know, each phone has an internal memory. In the Nexus 5's case, it's either 16GB or 32GB. This internal memory needs to hold a lot of things, not only your personal data. This is why you only have available to use 12.9 GB or 28 GB.
An Android's internal memory is partitioned into many chunks that have their separate purposes.
These are all the Nexus 5's partitions, and their names.
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system
/dev/block/platform/msm_sdcc.1/by-name/userdata /data
/dev/block/platform/msm_sdcc.1/by-name/cache /cache
/dev/block/platform/msm_sdcc.1/by-name/persist /persist
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware
/dev/block/platform/msm_sdcc.1/by-name/boot /boot
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery
/dev/block/platform/msm_sdcc.1/by-name/misc /misc
/dev/block/platform/msm_sdcc.1/by-name/modem /radio
/dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl1
/dev/block/platform/msm_sdcc.1/by-name/tz /tz
/dev/block/platform/msm_sdcc.1/by-name/rpm /rpm
/dev/block/platform/msm_sdcc.1/by-name/sdi /sdi
/dev/block/platform/msm_sdcc.1/by-name/aboot /aboot
/dev/block/platform/msm_sdcc.1/by-name/imgdata /imgdata
Yes, there are quite a lot. You, as a user, don't need to care about all of them. Here are the ones you will need to know about:
/system- size: about 0.5GB
This partition holds the Android OS itself. Kind of like the C:// disk on your every day Windows PC. This partition has many folders and files you cannot normally get to, due to safety reasons. For example, system/app is where all the system apps are installed.
If something gets deleted from this partition, Android will most probably won't work properly.
/data- size: either 12.9GB, or 28GB
This is where all your personal data is kept. This includes apps, sms, contacts, e-mails etc. It also stores your system settings, like wallpaper, and all those stuff you set up when you got your phone. The most important folders on this partition are data/app (where your apps are stored), data/data (where you app data is stored, like highscores and stuff), and data/media.
Data/media might be considered your sd-card. Yes, I know the Nexus 5 doesn't have an sd-card, but this folder works like one. When you connect your phone to your PC, this is the folder that pops up, with all your music, images, videos, and whatever else you keep on your phone.
Things are getting a bit more complicated, eh? Just bare with me. Next, I will be explaining the different terms you will be encountering throughout your Android experience.
Things you hear people talk about
Kernel
The kernel is an essential part of any Linux based operating system. It's the program that manages input and output requests of the operating system. Imagine you're at a restaurant. You give your order to a waiter. He takes it to the chef, the chef makes your food, then the waiter brings it back to you, and you enjoy it. In this case, you are the Android system, the waiter is the Kernel, and the chef is the hardware. The system gives the Kernel a request, like firing up another processor core when you play a heavy game, and the Kernel fulfills the request.
Here is an image for better understanding
Recovery
This is a secondary, mini operating system that has access to your internal memory. It contains a few commands that would normally help you recover your Android system in case of a failure, like factory resetting. You will see that, for rooting, you will need to install a custom recovery.
The stock recovery does not have the ability to write custom ROMs (I'll explain these later) on your internal memory. A custom recovery has this option, and many more.
Here are some images for you to fully understand:
Stock recovery:
Custom Recovery
You can see that the Custom Recovery has more options, including "Backup and Restore", Advanced, and Install zip from Sd-card.
You can get in Recovery by powering off your phone, then hold Power+Volume Down button until a black screen with colored text appears. Then, use the volume buttons to select 'Recovery", and then press the Power Button to select it.
Bootloader
The bootloader is the first thing that fires up when you open your phone. As the name says (Boot+Loader), this program loads the kernel, which when boots up the Android system.
The same bootloader can also boot in recovery, as explained above.
When you first get the phone, the bootloader is in a locked state. That means that you cannot use fastboot commands like "fastboot flash" or "fastboot boot". With other words, you cannot simply flash a custom recovery. Thankfully, Google gave us the option to unlock the bootloader very easily, and flash a custom recovery of our choice.
Custom ROMs
A custom ROM is a ZIP file that contains an altered version of the Android OS. There will be many custom ROMs for the Nexus 5, made by wonderful and skilled devs for the community. You can install a Custom ROM with your Custom Recovery. Custom ROMs contain the following folders and files:
META-INF- This folder holds the installation info and data. A custom recovery does not know on it's own how to install a ROM. In this folder, there's a txt file that contains a script, with the purpose of telling the recovery what to do.
System- This folder contains the stuff that will be installed on the /system partition that we talked earlier about.
boot.img- Among others, this file contains the kernel that comes with the ROM.
Dalvik Cache
Android is an open source OS, which supports many different architectures. While it's mainly used in the ARM architecture, it could run on x86. Even with in the ARM there are still some variations. Just like in x86, there are many extensions and SSE is an example of that; ARM is no different and there are some variations from one ARM CPU to another. Dalvik is basically a VM(Virtual Machine) engine, this keep the apps to be universal across many architecture. While this is good, this costs processing power. Meaning, if the apps have to run through VM everytime, they will be very slow. Dalvik cache is basically cache of those apps that's already gone through the VM thus it doesn't require to go through the VM everytime. And when an app run, it run from this version instead. Since each ROM may contain different version of app or optimization or even different kernel or Android version, using dalvik cache from different ROM can get you into trouble. Think of it like trying to run application designed for Windows XP on Windows 7 or Windows 8. It may work, it may not work, or it may even crash. Wiping the Dalvik cache will force the Android OS to optimize all the installed apps all over again.
Ok, so now, after you read all this stuff, you're probably thinking "Ok, I will never get the hang of this". Don't worry. With time, you will know all of these from reflex. And, after you got over that, and manned up again, you probably thought "Ok, let's root this damn thing!". Not quite yet. We aren't done. There are still some crucial things that you need to know. So let's continue.
How to backup your stuff
Before you do anything EVER, you'll always have to backup your stuff, even if you don't feel like it, or your dog died (in which case I'm truly sorry), but, no matter what you're about to do, always have a recent backup sitting around.
There are many ways and things you can and will probably have to backup.
1. Backup your entire phone, by creating a Nandroid Backup.
As you saw in the 'Custom Recovery" picture above, you have a "Backup and Restore" option. Here it is again:
With every occasion, it's best to use it as often as possible. It only takes about 2 minutes, but it could be a life saver.
A Nandroid will backup:
/system
/data (Except /data/media, where your "sd-card" is, because it's too large and not that important)
/cache (Yes, there is a cache partition, and it will be backed up, although not really necessary)
kernel (The kernel will be backed up too)
***Optional tip: I always keep a recent nandroid backup on my PC, in case I somehow wipe all my phone's contents, and my backup among with them. The Nandroid backup is saved at this location, which can be accessed with a root file explorer, like ES File Explorer : mnt/shell/emulated/clockworkmod/backup or sdcard/TWRP. If you want to copy it to your storage, just copy the latest backup, and then move it to your PC.
2. Your apps and data only
This can be very useful when changing ROMs. You just got bored of your ROM, and want to move to another one. The only way of taking your apps and data with you is by backing them up with an application like Titanium Backup. The backups will be saved in data/media, and will be restored using the same app with which you backup up on the new ROM.
3. Your SMS, Contacts, MMS etc.
These things can be backed up by special apps on the Play Store. Ok, contacts will be restored by Google Sync ( although not always done properly, that's why I still back them up), but SMS will not be restored. There are many free apps that back them up for you, nice an easily, for them to be restored in case of a ROM change or data loss.
4. Your storage (data/media, sd-card)
You just connect your phone to your PC, select all folders, and copy all over on your PC. This will be useful when you unlock the bootloader. A bootloader unlock will wipe all the stuff on your phone (This can be avoided, read guides). So keeping a copy of your sd-card contents on your PC isn't such a bad idea.
Now you know how to keep it safe by creating backups. I will say it again, you are never too safe! Backup when you do a modification, even if it's tiny. Now, after you've finished reading the above, you will probably attempt to root. You will use one of the guides out there ( I will link one at the end of this thread ) to install a custom recovery, and gain root access. But what to do with it? Well, you will most likely end up flashing a custom ROM.
Flashing a custom ROM
You will get bored of the stock ROM, and will decide to flash a custom ROM. But you haven't done it before, and you don't really understand the process.Before you do anything, you must:
-Make sure that the files are for your phone ! If you flash files that were made for another phone, you might end up with a brick!
-Never panic! There is always a way out! That's what backups are for!
-Read all the instructions! Every ROM thread has instructions. Read them!
{By the way, flashing = installing}
Now, let me take you through the whole flashing process. ( Use the steps in the ROM threads if instructed differently than here )
1. You will search far and wide in these forums for a custom ROM that fits your needs. Every ROM comes as a ZIP file. So when you decide on a ROM, download the zip. For copyright reasons, Google Apps (Play Store, Google Now etc) don't come included with the ROM. So you will have to download them too. They are usually linked on the ROM main thread.
Some ROMs might have addons too, so check them out, and download the ones you want.
2. You now downloaded the ROM, Google Apps, and some addons. The next step will be to put them on your sd-card. Connect your phone to your PC, and make an easy access folder, like "Root Stuffs" where you'll put all these zips.
3. Now, let the backup process begin. You first backup your apps, app data , SMS, Contacts etc., like I explained above. I recommend Titanium Backup for apps and SMS, MC Backup for contacts.
4. Now you are ready to go in recovery. Power down your phone. Then, press and hold the Power Button and the Volume Down button at the same time. You will be brought to the Bootloader Screen. Now, with the Volume Buttons, switch through the options until you find "Recovery". Then press the Power Button again.
5. Now you will be booted in your Custom Recovery. Depending on your recovery, you will have the options on your screen.
CWM Recovery:
6. You will go to the Backup and Restore menu, and select "Backup". If you made a backup before, you can select "Delete" first, and delete it, for space consumption purposes.
7. After the backup finished, you will return to the main screen. There, select 'Wipe data/ Factory Reset". This will wipe everything in /data except /media, so your sd-card will remain untouched. Don't worry, you have a Nandroid Backup!
8. After the wipe finished, you will go to "Install zip from sd-card". You'll have to navigate to the folder where you put the ROM, and select it. You'll see it will nicely install.
9. After the ROM finished installing, you will have to flash the Google Apps zip, and the mods. Install them the same way you installed the ROM itself.
10. After you have flashed everything, you can select "Reboot system now" . First boot will take longer to complete. Again, don't panic. You have a Nandoid bakcup . You will end up with the ROM booted, and you'll continue setting it up.
TWRP Recovery:
6. Go to the "Backup" menu, select "Boot", "System", and "Data", then swipe the thing on the bottom on the screen to start backing up.
7. Once you're done, use the home button to get to the main screen. Select "Wipe", and swipe the thing again to Factory Data Reset. This will wipe data, cache and dalvik cache. This will not wipe your internal storage (Music, photos, etc).
8. After the wipe finished, use the home button again to get to the main screen. From there, select the 'Install" option. You'll have to navigate to the folder where you put the ROM, and select it. Then, by using the "Add more zips" option, add the Gapps package, and and then any addons or mods, in this order. Then swipe the bottom thing to flash.
9. After you have flashed everything, you can select "Reboot" . First boot will take longer to complete. Again, don't panic. You have a Nandoid bakcup . You will end up with the ROM booted, and you'll continue setting it up.
***In case something went bad, like your phone doesn't boot for more than 10 minutes, or the animation endlessly repeats itself (Boot Loop), do the following:
11*. Hold down the Power +Volume Buttons until the phone shuts down. Then release them for a second, and immediately press them again. You will be brought to the bootloader screen. Enter recovery.
12*. In recovery, go to the "Backup and Restore" menu, and select "Restore" for CWM, or "Restore" for TWRP. Then pick the backup you did earlier, and wait for it to complete. Then, select "Reboot system now", and you should be booted back in your original ROM.
Now, let's say that after you flashed a ROM, it either did not boot, or you had some bugs with it. You will go to the thread ROM to report your problem. Here's how to not post:
"This ROM doesn't work"
You will have to be a lot more specific than that. In reporting a problem, you will have to do the following:
-Say what you did (Flashing process)
-What you flashed afterwards
-What you did to reproduce the bug
-What recovery you use
-ROM Version
-even provide a logcat <This is quite advanced> (http://forum.xda-developers.com/showthread.php?t=1726238)
You have to give as many details as possible, so the developer can sort things out.
ADB and Fastboot
ADB (Android Debug Bridge)
The Android Debugging Bridge is kind of a toolkit, that has many commands to control your Android from your PC. This is an essential part of your Android experience. With ADB, you can do many stuff that you couldn't normally do, like backup your apps, or push and pull packages from your phone.
ADB is also used by many of the useful tools out there, like toolkits, and all sort of programs that enhance your Android experience.
With ADB, you can also Logcat. Logcatting is creating a log of everything that happens on your Android phone while it's on. This is used to find the sources of bugs.
Example of ADB Commands:
Code:
adb pull /system/app/RANDOM APP = creates a copy of a system app on your PC
adb push app /system/app = Copies an app from your PC to your system partition
adb reboot bootloader/recovery = Reboots the phone in bootloader or recovery
adb logcat = Starts a logcat
Fastboot
Fastboot is also a toolkit of commands, but a bit different from ADB. While with ADB, you can do simple actions, with fastboot, you can do major ones, like flashing a whole partition, or formatting one. Fastboot is usually the preferred method to flash a recovery. Also, Fastboot usually works with .img files.
Fastboot is also a very easy method of bricking your phone. Always make sure you are flashing the right files for your phone. Furthermore, fastboot is not the preferred method for recovering your phone. It is the last resort. ADB and/or recovery is much easier and safer.
Example of Fastboot commands:
Code:
fastboot erase boot = Erases the kernel
fastboot erase recovery = Erases the recovery
fastboot flash system system.img = Flashes the System partition with an image
fastboot flash boot boot.img = Flashes kernel
fastboot flash userdata data.img = Flashes Data partition
fastboot flash recovery recovery.img = Flashes a new recovery
fastboot reboot = Reboots the phone
To use ADB and Fastboot, you must first have ADB drivers and Fastboot drivers installed. Here is a very good guide to set up these two useful things:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Restoring your Nexus 5 to STOCK
I moved the whole guide here:
http://forum.xda-developers.com/showthread.php?t=2513701
Check it out.
Now please proceed to the next post

Tips and Tricks
1. Try to not use toolkits. (I'm not disregarding any toolkit dev. They did a wonderful job)
Chromium_ said:
It has been proven that every time you use a toolkit, god kills a kitten. Save the kittens.
Click to expand...
Click to collapse
Due to the fact that people are lazy in nature , toolkits have been made so that users don't struggle with rooting their phone. But there are many reasons for you to not use one:
-->you won't learn anything from using a toolkit, and, if something goes wrong, a toolkit can rarely fix your problem. It's better if you rely on your own forces.
-->you put the fate of your phone in someone else's hands. If a bit of code is wrong, then your phone could get bricked.
-->you miss out all the fun. Why buy a Nexus device if you don't want to explore the depths of the Android OS?
2. Never panic
Whenever you don't know what to do, and you're stuck, don't panic. There are many people here that can help you. Don't try doing anything blindly. Search the forums, or start a thread in the Q&As section, and we will help you.
3. Read everything carefully!!
(If you read this, post a cat picture in this thread, and you will be rewarded with a thanks from me)
I might have said it a couple of times throuout this post, but always read everything. Someone wrote something for a reason. Usually, if you read everything, and do what you are told, you are bound to be failproof.
4. Battery pull emulation
If you hold the Power Button and both Volume buttons for 10-15 seconds, the Nexus 5 will power off, as if it had its battery pulled out. Useful when you get stuck.
5. Never try to make any system modification(root or flash ROM/recovery) without having enough time and resources to troubleshoot.
While most of the time, this is relatively painless when the you follow the instruction carefully. That said, things can go wrong. So, don't just say I saw a new ROM when I woke up and I wanna try it, and you have 30 minutes before going to work. Even if it only take 5 minutes to flash the ROM, if a thing goes wrong, those 25 minutes you have left may not be enough to fix your problem and you have no phone to use that day.
When you flash something, always make sure you have about an hour of free time, and a PC with ADB and Fastboot, ready to make us of if something goes wrong.
Ok, so now you know pretty much all a normal user should know. But there are still questions that are very frequently asked that need answering. Here are some questions and answers about popular problems and misconceptions. You might encounter these problems later, so give it one more minute of your time:
Questions and Misconceptions
1. My Nexus 5 is getting very hot. Hardware problem?
Nope. There are many reasons that contribute to your phone getting hot, like
-the fact that it doesn't have any way of cooling itself
-the fact that a quad core produces more heat
-etc.
Don't worry. Everything is working as it should. For example, the Ipad gets 3 times hotter than the Nexus.
2. If I am rooted, will I receive OTA updates? (See Return to stock section)
Yes, and no.
You will be able to download the update by having installed the Stock ROM with stock kernel, though it will not be installed automatically, due to the fact that you have a custom recovery. You will need to install it manually.
3. The Nexus 5 audio quality is horrible. Why?
It isn't horrible. It's normal, but the max volume isn't as loud as on other devices. I have been a piano player for 12 years. I have quite a sensitive ear, and I can tell you that the audio quality on the Nexus is comparable with that of an Ipod. The only major difference is that, with the Ipod, you can go deaf with the max volume.
4. Which kernel/ ROM should I use?
Don't ever ask this question. What's good for others isn't necessarily good for you. You'll have to try the many kernels and ROMs yourself.
5. Google Now doesn't activate with "Ok, Google". Why?
Make sure your language is English (United States) in Settings>Language & Input.
6. My battery life is short. What should I do?
-Use a custom kernel made for battery life (like Franco)
-Use the Greenify app from the play store (https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=ro)
-Don't use Automatic Brightness. Set the brightness to about 35%.
7. My Baseband and IMEI are unknown. What do I do?
Flash the factory images, and then boot in the stock recovery and do a factory data reset. If it does not solve the issue, repeat. I had to do it 3 times for it to work.
8. What's the difference between "Development" and "Original Development"?
Original Development - Usually original pieces of work, based on the original AOSP source, or coded by yourself.
Development - Projects based on works from the Original Development, or that don't include actual developing (Stock rooted ROMs)
This is all for now. I hope you understand what's up with this Rooting process. If you have any questions, don't be shy to ask in this thread
If there is anything to be added to this thread, please post below
Thank you for the time you allocated to reading this! You are now smarter :good:
Good day, and Happy flashing!!!
For credits, useful links and other stuff, see the post below.

Useful links
[GUIDE] Nexus 5 - How to Unlock Bootloader, Install Custom Recovery and Root
[INDEX] Google Nexus 5 - ROMs, Kernels, MODs, Recoveries, Themes
[HELP THREAD] Nexus 5 | Ask any question
[MODEM] [EFS] Nexus 5 Flashable Modems and EFS Backup
Nexus 5 OTA Help-Desk
Credits and Thanks!!
@rootSU
For providing me a template, inspiration, and much of the info. His original thread in the S3 forums: (http://forum.xda-developers.com/showthread.php?t=2362743)
@paxChristos
For the logcat part
@efrant
For pointing out some mistakes
@someone0
For this post: http://forum.xda-developers.com/showpost.php?p=47474453&postcount=81

Very good post. Im not new to rooting but I am when it comes to Nexus Devices. Im use to rooting phones with external SD cards so I have one question.
When Im going to flash a rom or zip or whatever in custom recovery, I know I have to "Wipe data/factory reset" then "wipe calivk". I know that the data wipe is for apps, app data and system settings. My question is will it also delete pictures, music, videos and other files/file folders like that on the device?

MMontanez347 said:
Very good post. Im not new to rooting but I am when it comes to Nexus Devices. Im use to rooting phones with external SD cards so I have one question.
When Im going to flash a rom or zip or whatever in custom recovery, I know I have to "Wipe data/factory reset" then "wipe calivk". I know that the data wipe is for apps, app data and system settings. My question is will it also delete pictures, music, videos and other files/file folders like that on the device?
Click to expand...
Click to collapse
A Factory Data Reset doesn't wipe the data/media folder, where all the things that should be on the sd-card are. You can use the option with no worries.

Very informative, didn't read the whole thing though. I stop at the advantage of flashing custom ROM. In my past experience, gaining root <> able to flash custom ROM. If I understand correctly, even if you can gain root access but not able to unlock the boot-loader, getting a custom ROM would be problematic. IMO, I wouldn't list that there. Sure this maybe beyond noobie scope and doesn't pertain to Nexus 5 specifically. But I wouldn't use that as a rule of thumb. Having used the Sprint Photon 4G, I have respectfully disagree with you on that. Gaining root, mean having admin privilege for the OS not the boot-loader.
---------- Post added at 11:29 PM ---------- Previous post was at 11:12 PM ----------
MMontanez347 said:
Very good post. Im not new to rooting but I am when it comes to Nexus Devices. Im use to rooting phones with external SD cards so I have one question.
When Im going to flash a rom or zip or whatever in custom recovery, I know I have to "Wipe data/factory reset" then "wipe calivk". I know that the data wipe is for apps, app data and system settings. My question is will it also delete pictures, music, videos and other files/file folders like that on the device?
Click to expand...
Click to collapse
From what I understand of basic android OS is that the system and apps are sitting on separate partition. And so is you normal partition for data, which usually the phone shown as SD card even though it's not a separate internal SD card. The phone usually have one large pool of storage space, think of it like an SSD drive. Then it got split into many partitions for many things. It has boot sector, recovery partition(for storing recovery method, either stock, CWM or TWRP), boot partition, system partition and maybe may other system relation usage partitions. Those partition are already planed out(fixed) by the people who create the ROM for the device. And the rest of the space will be given for the user to do other thing under one partition. And this partition usually won't get wipe. If you have used any custom recovery like CWM or TWRP, there usually be an option to wipe or not wipe certain things. This is possible because all those things are stored in separate partition.

someone0 said:
Very informative, didn't read the whole thing though. I stop at the advantage of flashing custom ROM. In my past experience, gaining root <> able to flash custom ROM. If I understand correctly, even if you can gain root access but not able to unlock the boot-loader, getting a custom ROM would be problematic. IMO, I wouldn't list that there. Sure this maybe beyond noobie scope and doesn't pertain to Nexus 5 specifically. But I wouldn't use that as a rule of thumb. Having used the Sprint Photon 4G, I have respectfully disagree with you on that. Gaining root, mean having admin privilege for the OS not the boot-loader.
Click to expand...
Click to collapse
Well yeah, but from being able to flash a custom ROM to being able to get root access in your current ROM, there is only one simple step, that is installing SU binaries, and a superuser app. I just didn't want to confuse new users by changing the term used only for one small step.

I'll just adding things as I read through, while I'm not a noob by any mean, that doesn't mean I don't see thing missing out. Since sometime the author fill in the missing gap in his/her head. I know I did that a few time. As I read, I though, hmm "Understanding the Android world before rooting" that's helpful. But after I start reading, it's more like a guide to understand the rooting world of android. I understand that's not the purpose here to teach people android, hopefully not to the general XDA members audience. But I would say the headline isn't exactly saying it right. The you start throwing the term Linux. Sure I understand what it is, at least to my understanding. But, it probably wouldn't hurt to stated the first time the term linux is use that Android is a linux based OS as well. Not just saying root is an equivalent of admin in linux. If you are going to assume that the intended audiences don't know what root is, then you should assume the audience know that the same targeted audiences don't know that Android has a deep relationship with linux as well.
I would put extra emphasis on dealing with fastboot. Yes you can do a major operation w/ fastboot. That said, greater power come greater responsibility. It's much easier to brick your device w/ fastboot and less chance of unbricking from using fastboot than recovery or adb.

someone0 said:
I'll just adding things as I read through, while I'm not a noob by any mean, that doesn't mean I don't see thing missing out. Since sometime the author fill in the missing gap in his/her head. I know I did that a few time. As I read, I though, hmm "Understanding the Android world before rooting" that's helpful. But after I start reading, it's more like a guide to understand the rooting world of android. I understand that's not the purpose here to teach people android, hopefully not to the general XDA members audience. But I would say the headline isn't exactly saying it right. The you start throwing the term Linux. Sure I understand what it is, at least to my understanding. But, it probably wouldn't hurt to stated the first time the term linux is use that Android is a linux based OS as well. Not just saying root is an equivalent of admin in linux. If you are going to assume that the intended audiences don't know what root is, then you should assume the audience know that the same targeted audiences don't know that Android has a deep relationship with linux as well.
I would put extra emphasis on dealing with fastboot. Yes you can do a major operation w/ fastboot. That said, greater power come greater responsibility. It's much easier to brick your device w/ fastboot and less chance of unbricking from using fastboot than recovery or adb.
Click to expand...
Click to collapse
Made some modifications. Thanks!
Credited you

Good thing to see this in the N5 section too.

Great job,dude:good:

Well done! Not a noob, but still learned some things.

jd1639 said:
Well done! Not a noob, but still learned some things.
Click to expand...
Click to collapse
They say we never stop learning

abaaaabbbb63 said:
They say we never stop learning
Click to expand...
Click to collapse
Very true, I am 76 and learn new things all the time.
Very good and informative post.
While I knew the subject, I read the whole thing just in case I missed something.
The list of ALL the partitions was something I did not know.
:good:

Rooting may or may not void your warranty, depending on where you are. In the EU they cannot refuse warranty for a rooted device, or even a fully 'hacked' phone with unlocked bootloader, rooted and custom ROMed or even in the case of HTCs super CID'ed devices. The exception is if the fault is software related, if you brick it, you lose it, but any hardware fault is still covered.

ChrisM75 said:
Rooting may or may not void your warranty, depending on where you are. In the EU they cannot refuse warranty for a rooted device, or even a fully 'hacked' phone with unlocked bootloader, rooted and custom ROMed or even in the case of HTCs super CID'ed devices. The exception is if the fault is software related, if you brick it, you lose it, but any hardware fault is still covered.
Click to expand...
Click to collapse
Still, it does not apply to the whole EU. In countries where the Nexus 5 isn't sold through Google Play, warranty policies may differ. Retailers tend to take advantage of their monopoly over these countries and strip down the warranty coverage, and say that if you modified the software, it goes in the "Unsuitable Usage" category, and they can't do anything to it, not even hardware wise.
Trust me. Retailers know how to crook you with every occasion.

abaaaabbbb63 said:
Still, it does not apply to the whole EU. In countries where the Nexus 5 isn't sold through Google Play, warranty policies may differ. Retailers tend to take advantage of their monopoly over these countries and strip down the warranty coverage, and say that if you modified the software, it goes in the "Unsuitable Usage" category, and they can't do anything to it, not even hardware wise.
Trust me. Retailers know how to crook you with every occasion.
Click to expand...
Click to collapse
They know how to try. Force the issue and they cave in. I went as far as starting court action over this and they then gave in because they know they would lose. Know your rights and use them.

Very useful info. Thanks.
Quick question. I am coming from htc one x. I have fastboot and drivers installed for that device. Will these work for the n5 or do I need to install new specific ones?

columbo67 said:
Very useful info. Thanks.
Quick question. I am coming from htc one x. I have fastboot and drivers installed for that device. Will these work for the n5 or do I need to install new specific ones?
Click to expand...
Click to collapse
They will work for the n5 (I think.... more like 80% sure). Try and see.

I had a question about the void warranty part. Do you know if it rooting/unlocking bootloader voids the warranty in Canada? I'll be getting the Nexus 5 as my first smartphone but would still like to mess around with rooting after a while, but would Google care if I rooted/unlocked the loader? Also, can you unroot/relock the loader?
Thanks.

[HowTo] THL W8 Beyond ROOT + ClockworkMod + GravityBox + Caller ID Fix

Hello to whoever is reading this thread.
First of all, I would like to point out that I may be posting on the wrong forum because I couldn't find an appropriate forum for this phone but I hope the mods will help me to redirect this thread where it belongs.
I am a simple user myself and to my experience, it has been a nightmare trying to root my phone and install a simple mod to fix one of the most annoying issues on 4.2.1 with the phone not recognising international numbers.
All the information is scattered across the internet and buried under huge amounts of threads, off topic user requests and so on.
So I thought that if it benefits even a single user, I will compile all the knowledge I have gained during the past few days, and compile everything into a single thread.
I will NOT be held accountable in case you brick your phone. If you need support, please read and post on the relevant threads provided for each step. Seriously.
So, here it goes.
In order to be able to know what I am talking about, you must know the basics:
1) What is rooting and why you need it:
In order to make changes to your phone's system (install mods, tweak special settings e.t.c) you need SuperUser rights. Rooting gives you these rights.
http://forum.xda-developers.com/wiki/Glossary#Root
2) What is Recovery and why you need it.
The changes you might be doing to your system may not always be successful and you might end up "bricking" your phone. i.e. corrupting the system and rendering it unbootable. Therefore you need some kind of emergency plan. Having a full system backup which you took before the changes, will enable you to overwrite the broken copy of your operating system with the healthy one in case things go tits up.
Beautiful post here:
http://forum.xda-developers.com/wiki/Recovery
3) What is ClockWorkMod and why do I need it?
The original recovery system of your phone which resides on a completely separate partition from your operating system, is usually referred to as "Stock Recovery". It does not provide you with the necessary rights to replace the complete device's primary Android operating system so you need a "Custom Recovery" which will allow you to do it. ClockworkMod will help you do just that, and it is also the BEST way to keep a complete system backup in case your tingling fails.
Amazing explanation here.
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
4) What is a custom ROM and what do I need it?
The operating system that your phone came with is called a "Stock ROM" and a modified version of it is called a "Custom ROM". In our case we are trying to install GravityBox, a custom ROM for our THL W8 that has quite a few nice fixes and improvements from our stock ROM including the Caller ID FIX I mentioned earlier. Our target in this tutorial is to install it and fix our OS bugs.
I read this article from Androidpolice and I found it very eye opening.
http://www.androidpolice.com/2010/05/01/custom-roms-for-android-explained-and-why-you-want-them/
5) What is Xposed and why do I need it?
Xposed is a platform, which will enable you to install parts of a ROM without having to flash your phone and lose your current operating system.
The techNinja has a very simple explanation of what it is right here:
http://www.youtube.com/watch?v=uRR0Flqx9M8
OK so let's get started.
1) Backup your data
Rule #1 before starting any process and I can not stress this enough is <<BACKUP YOUR PHONE!>>
Having an unrooted phone has it's limitations on how much you can backup but I used "Ultimate Backup Tool" to backup whatever I could.
http://forum.xda-developers.com/showthread.php?t=1844032
2) ROOT your THL W8 Beyond
There are THOUSANDS of threads out there with complex technical instructions, but I have some good news. THL W8 Beyond can be rooted without ODIN, USB cables and the rest, only by using Framaroot.
Marc has saved me literally hours of pain with this guide here.
http://playfuldroid.com/how-to-root-the-thl-w8-beyond-using-framaroot/
3) Install ClockworkMod and perform a nandroid backup of your system
C3C076 has the BEST guide on how to do this for our phone and the instructions are easy and crystal clear.
Follow the 9 simple steps on the Installation Instructions section
http://forum.xda-developers.com/showthread.php?t=2237779
When you install ClockworkMod, boot into recovery (as explained in the tutorial above) and follow the menus to fully backup your system
4) Install XPOSED and reboot your phone.
Follow the instructions on this tutorial below at the installation section (steps 1-7) or just watch the video on my Basics section above:
http://forum.xda-developers.com/showthread.php?t=2316070
5) Install GravityBox module from the tutorial below:
http://forum.xda-developers.com/showthread.php?t=1574401
Download the apk file at the bottom of the first post and load it onto XPOSED (as also seen on the video). Reboot your phone.
Once everything is nicely installed and phone boots, open Gravitybox app and go to:
General Fixes -> Fix Called ID for Phone
Reboot your phone, remove your google accounts and reimport them. Reboot your phone once more and enjoy.
Even if one of the steps above is proven useful for someone with the same problem as me, this thread will be worth it.
Peace :angel:
[EDIT1]: For the GPS fix click this link
http://www.thlmobilestore.com/news/gps-fix/
[EDIT2]: For waking up the phone with the Home button click this link
http://forum.xda-developers.com/showpost.php?p=45632410&postcount=1515

Backing up and Restoring - Stock ROM

is there a non intrusive (as in rooting not required) method
for "backing up" and "restoring" a Samsung S6 (SM-G920I) stock ROM.
thank you in advance.
note: not interested in any custom rom nor any tinkering. this is strictly for recovery option should the operating system ever get corrupt or get mal-ware.

UaVaj said:
is there a non intrusive (as in rooting not required) method
for "backing up" and "restoring" a Samsung S6 (SM-G920I) stock ROM.
thank you in advance.
note: not interested in any custom rom nor any tinkering. this is strictly for recovery option should the operating system ever get corrupt or get mal-ware.
Click to expand...
Click to collapse
Smart switch can backup every thing u need with out a custom recovey theres no way to make a complete img backup

given the lack of response here and limited results via any search engine/forum.
perhaps there is no such method available.
given that said. all these "stock" rom floating around available for download.
these must be all rooted stock rom then.
if not. how did the owners of these stock rom rips the original rom off the device?
for further clarification. simply looking to back up the original operating system and could care less about the latter data/updates.

UaVaj said:
given the lack of response here and limited results via any search engine/forum.
perhaps there is no such method available.
given that said. all these "stock" rom floating around available for download.
these must be all rooted stock rom then.
if not. how did the owners of these stock rom rips the original rom off the device?
for further clarification. simply looking to back up the original operating system and could care less about the latter data/updates.
Click to expand...
Click to collapse
As said before, Smart Switch is the tool to use. In case of emergency you factory reset your phone and use this tool to recover broken system files and restore your data.
Stock roms are compiled with the official firmwares you get from sammobile.

The following method has been used from the begging of the android i think.
http://www.techrepublic.com/article/how-to-create-a-full-backup-of-your-android-device-without-root/
(If external links are not allowed ,inform me and i will remove immediately! )
Please note that i have not personally tested the ADB backup method,but i dont see any reason to not work with user apps and data.
Dont know about system files on the other hand.
Also you dont need to install the whole Android SDK, just the adb files and drivers (google them).

nighthawk696969 said:
The following method has been used from the begging of the android i think.
http://www.techrepublic.com/article/how-to-create-a-full-backup-of-your-android-device-without-root/
(If external links are not allowed ,inform me and i will remove immediately! )
Please note that i have not personally tested the ADB backup method,but i dont see any reason to not work with user apps and data.
Dont know about system files on the other hand.
Also you dont need to install the whole Android SDK, just the adb files and drivers (google them).
Click to expand...
Click to collapse
This method works for the APKs off the installed Userapps but not for data. And it's definitely not working for system files because you would need root for that.
It's a good question how to backup data of userapps without root. But nowadays most apps sync their data to the cloud.

thank you all for trying to help. greatly appreciated.
however this is not getting anywhere.
one last time. "this is strictly for backing up and restoring the operating system (android 5.1.1) incase of corruption or malware." not the user application. not the user data. not user settings.
for restore - looks like odin can handle the restore. just have to root the device first. and then it will be back to factory stock.
for backup - want the current stock rom on the s6 in my hand and keep it 100.0% original. is seems to be a dead end.
why? have a "stock" note3 that got malware so bad. malware has embedded itself into the root. even a master reset does not get rid of the malware. just bought a S6. does not want history to repeat itself. hence looking for a non invasive backup/restore method.

Database Info

welcome