Complete wipe and recovery? - Captivate General

Ive been hacking away at my phone since I got it and I see how to use the Odin and flash to the stock firmware and use clockwork etc but how does one completely wipe everything and get to factory settings including erasing all the media you've put in it, all the backups and little folders you've installed and tweaked and literally start like its out of the box. Also on a side note, as a guy that has studied a bit of minor scripting and barely touched on some c# other than the Android SDK resources, where are some good resources to begin to understand the fineries of android development literally from step one.

Related

Trying to understand these instructions... (Android, SD Card default, EXT3, re-flash)

I have an LG Optimus T. Not the most ground breaking phone ever, but a heck of a deal for the money. Nonetheless, it's my phone, and I'm not really happy with the internal memory barrier I'm facing. For what it's worth, I have it rooted. I heard a way to partition your SD card (with part of it being allocated to ext3 file system) and re-flashing your phone somehow so the phone utilizes your ext3 partition on the SD card for housing applications. I heard several users in the IRC chat confirm this works well.
However, now that it's show time and I'm trying to do it, I'm a little confused. So please, be gentle, and I apologize if I'm re-hashing simple steps. I'm just trying to make sure I get what I'm supposed to do.
I'm working from this link here:
http://forum.xda-developers.com/showpost.php?p=10692249&postcount=1299
So from what I understand, the factory ROM can do fine, so I don't need to locate a custom ROM. That said, I just need to reset the phone to factory settings (thereby getting the factory ROM), run A2SD (is A2SD any different from A2SD Killer that they speak of in this post? I never heard of it), then go through the motions of the initial setup as it suggests (language choice, time zone, etc).
Then, prior to setting up my gmail account, I'm supposed to reboot to recovery. What does it mean reboot to recovery? Am I supposed to hold down the keys to do a factory reset? Is that what they mean by recovery?
I hate to ask these questions in a form of hand holding, but I just want to make sure I'm doing it right. After re-hashing this post several times and talking to 2 buddies about it without any further progress, I figured I'd just ask.
That said, can anyone help guide me in the proper direction? I'd greatly appreciate it.
Thanks!
make sure that you are looking at the right forum next time that link was for htc desire (use it only if it says its compatible for your phone)
before you start worrying about a2sd, you need a custom recovery, found here. once you flash recovery and boot into it, everything will be clear (ext, partition, flashing, etc)
for apps2sd, id suggest using ungazes data2sd (apps2sd and data2sd are basically the same thing, at least thats my understanding)
follow the steps there. if anythings unclear, post any questions and ill check back later
I did notice it was an HTC forum, but I was speaking with users who had other devices and claimed they used the same method, so I didn't think much of it. At that point I figured it was more of an Android thing vs an actual manufacturer thing.
When you speak of the custom recovery, what *exactly* does that entail? I was told Android phones have the hard factory reset that cannot be altered as long as you don't mess with /system under root terminal. That said, this phone is pretty much brand new. I have nothing on it that isn't already stored in the cloud somewhere (google contacts, gmail, work's email, etc).
What I'm trying to get at is, is a custom recovery needed only to get my phone back the way it was before I screwed with it? Or if I'm accepting to doing a hard factory reset, is that acceptable as well?
Thank you very much for the link. This seems a little more straight forward than the last one was. I'm also trying to understand the differences between handsets and Android versions here. For example, you mentioned the previous post was for HTC. It's a difficult thing for me to grasp because I come from a very heavy Linux background. If I mess with Ubuntu on one machine, then mess with Ubuntu on a top end server, then tinker with it on a laptop, it's still Ubuntu no matter what machine it's on. So it's hard for me to grasp the concept of Android acting differently on different machines (phones) and having different methods to different devices.
That said, it sounds like the link you posted to me is more of a generic "everything should work" type of scenario. After all, it's just moving /data. It would make sense that it would work that way, right? If not, please correct me, as I'd rather be wrong 1,000 times over again and be corrected than make 1 mistake and mislead someone or brick my phone.
Thanks for your response. Hopefully the recovery thing isn't too much of a hassle and I hope this ext thing can do the trick! What kind of difficulty is involved here? Is this fix, say, grandma approved? Or is that asking for a lot?
EDIT - Also, I noticed you spoke of Apps2SD. I have that installed... is that not acceptable to what I'm running? After all, it just seems to move what parts of the apps it can to the SD card. I was aiming to have the entire application base MOVED to the SD card. Is that what it does and I'm just a little confused??
i understand what you mean (how ubuntu on one machine is the same as ubuntu on another)
its the same thing with android EXCEPT that each android device is made different by the hardware (i.e. my phone is limited by the fact that its cpu is not powerful enough to run some apps; different components make up each device in contrast to lets say iphone, where each iphone is the same; my understanding is that each rom utilizes and has commands for each of these components so if they're different then youll need a rom unique for each device)
heres a general scope over recovery:
custom recovery - allows you to flash a rom, make/restore a nand backup, well it allows you to do a lot of things
stock recovery - only a hard reset (done automatically)
a hard reset wont cut it if you screw up your phone. youll need a custom recovery (which allows you to back up your entire system as a nand backup)
when you say apps2sd, i think you are talking about moving the app to the sd card in settings. thats not true apps2sd. true apps2sd moves the whole app to the sd card, giving you unlimited space to store apps (well actually you are only limited by your sd card)
if i missed anything, tell me. im multitasking right now (sorry)
Hahah, no you're doing quite well for multitasking! I understand what you mean, and it makes sense to me. I mean, after all, isn't it still the same analogy to Ubuntu? (at first I didn't think so, but now I think it may be more relevant) After all, if I'm running a dual proc 6 core system with 24gb of RAM, it'll certainly move Google Earth (aka, an app) faster than a Pentium 3 with 128mb of RAM would, even though they're both packin Ubuntu, Fedora, Debian, or whatever your flavor may be. So in theory, I suppose you can apply the same analogy from Ubuntu as you do Android. The catch is, Ubuntu (or any Linux distro for that matter) runs on old hardware great, so the gap between old computer vs super computer is less relevant than today's Android based smart phones, where 300mhz could mean whether or not you can run a certain app. Compared to real life, Ubuntu operates just as quick to me on my dual proc 6 core (12 core total) server with 24gb of RAM as it does my P4 1gb RAM box on my test bench.
Anyway, going back on topic a bit more... yeah I was thinking of the Apps2SD from the market. So I suppose the "real" Apps2SD is a true "mv -R" type of application (linux recursive move of data).
Okay, so get the market based App2SD out of my head. Gone. Done. Okay... the thing I'm still not understanding is the recovery. I mean, I'm looking at the hard factory reset as, say, a recovery "Ghost based" partition that some Windows computers often come with.
Example - Windows gets fubar'd. Reboot. F8. Recover system. And it dumps the recovery image on the main partition. Ta da! Just like it was when you bought it at Best Buy!
I mean, if I could get it back to factory, then I could just start over, right? Trying to put it into words as best I can... I was thinking of it like this.
Hard factory reset = Windows recovery image from Dell factory (back to day 1).
Nandroid custom reset = Own "self made" Clonezilla/Ghost image (customized with your stuff as a backup you made yourself)
That's what I was thinking. So that being said, am I absolutely positively required to do a custom backup? Can I not just rely on the hard factory reset to take me back to day 1 from when I got it from T-Mobile and (if I so desire) start the process over if I tank it? You see, I was told that it's nearly impossible for me to permanently brick an Android phone, as the hard reset, while inconvenient since it would wipe my stuff, would at least get me back to a bootable, functional ROM.
If I'm re-hashing unnecessary things and just need to focus on the fact I have no choice, by all means, e-slap me. Thanks for your help so far. I'm just trying to learn what I can! Your time is appreciated.
the thing is, a time may come when you cannot even boot your phone (lets say you were messing around and modding and all of a sudden you get stuck in a bootloop) and you try doing a factory reset but it doesnt work. this might be because something is corrupted. for android, a factory reset only wipes the data but does not restore anything. this is where custom recovery comes in handy. not only can custom recovery do a factory reset, it can restore a backup if your phone ever gets screwed up (unless you screw it up so much that you cant even access your recovery, then things get much more complicated). think of this backup as a system restore on windows (creating a restore point on windows is like creating a nand backup in custom recovery)
and dont worry about all the questions a few months back i never knew this myself so i understand
Well my friend, your patience is certainly appreciated. I understand a little better now. So let me throw out another analogy just to further solidify what little understanding I feel I have.
Factory reset = Windows restore point
Nandroid reset = Self made recovery image via Clonezilla/Ghost
Your point is a Windows restore point is only good as long as the system is solid. If your hard drive dies, suddenly your backed up restore point is useless. But... dump on that Clonezilla/Ghost image you have saved elsewhere and you're good to go.
That said, how should I get started? How do I make a Nand backup? Any guides you recommend? Will this back up my current apps, settings, etc?
Once done, how would I go about the actual Apps2SD method for making the SD card act as app storage? I assume it's that ungazes link you provided earlier?
Again, thanks for your help!
Figure this is where I should come in to help. You can install Amon_ra's recovery or clockworkmod onto your device (you can choose if there is both) but you should be able to do all that from a backup and restore menu in the custom recovery. You can go get the free version of rom manager and it should be able to install clock work recovery all without that much input from you, then you boot into recovery from rom manager. It shows you this simple yet amazing GUI that you never thought possible with something so small such as your android device. You are then given choices, do you want to flash a zip to mod your system such as custom roms, new keyboards, etc. Backup and restore (nandroid backup) or even mount it in USB mode which is useful if you never backed up, and didn't keep a copy of a custom rom on your SD card. (I never made that mistake of atleast the latter option. lol) So basically, the recovery is the "safemode" of android, only you don't get to access all of your stuff until you leave "safe mode"
and a bit of advice: NEVER flash anything without 50% or more battery.
It probably will atleast softbrick your device if it dies mid-flash.
oh, I see. Yeah I thought recovery was the actual PROCESS of pulling an old backup over, not so much operating in a sterile system environment such as safe mode.
About flashing, I would suspect it would best be done plugged in with AC power. I've had a laptop or two nearly die on me in my flashing days (went to the bathroom, came back, flashing red light, uh oh!) so I think I'll be good there.
So which applications do I need to get started? The problem I face is when I google something, there's no less than 600 ways to do all sorts of various tasks. So I have a hard time separating which one is best practice, which one is the old method, which one is definitely a bad idea, etc. So you say I can choose which ROM to use. Are they pre-built into whatever recovery software I need to use to get this job done? Or do I have to download them somewhere and put them on my SD card and then boot into recovery?
EDIT - hey how about this lil guy here?
http://code.google.com/p/android-roms/wiki/SPL
Came across it when I was googling for Nandroid Backup.
EDIT 2 - Or this guy. Looks to be the same step as the Nandroid step within the first link. Looks like the first link, while a bit more dated, is also a bit more thorough.
http://theunlockr.com/2010/02/06/how-to-backup-and-restore-your-android-phone/
Since you're rooted, you can run thiss https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en and it will be able to install clocwork mod recovery. Then you just boot into it and whatever rom you want to use (found in the android development forum for your device) you install that zip from SD card and voila! You're golden with a new rom on your phone. It isn't completely needed though. lol
if i were you, i wouldnt use rom manager (it is known to cause problems). for now, use the recovery i posted in the second post. if you want to flash a rom, heres a list of most (if not all) roms for our phone.
as you start getting familiar things, you should start referring here
heres a general scope of things when it comes to flashing a custom rom:
1. boot into recovery
2. make a nand backup
3. you MUST wipe data/factory reset, cache, and dalvik cache. wiping the sd card is not necessary
4. flash the rom
5. boot normally (first boot can take awhile)
and remember, never flash more than one file without rebooting normally in between or else you might run into some problems
When you say wipe the dalvik, cache, etc, is that done during a factory wipe or do I need to do that in a separate step?
Edit- which rom would you suggest? I hear a lot about cm7. Thats the only one I recognize.
they are separate processes but they are found under the same category
so itll be like this:
wipe
wipe data/factory reset
wipe cache
wipe dalvik cache
wipe rotation settings
wipe battery stats
something like that (at least this is how it works for amonra recovery. for clockwordmod recovery, i believe they are categorized differently but its still the same idea)
Ahh, I gotcha. I remember reading instructions on clearing the dalvik-cache, so that's why I thought maybe I'd have to re-hash those links I found and do that in a separate step. But it sounds pretty streamlined!
Well, I'll give this a shot tonight. I'm still going back and forth on which ROM to use. I hear a lot about CM7, but I also heard of 1 or 2 users saying on CM7 they lost their Google Navigation or Google Latitude functionality, both things I utilize. I also had no idea the Opt T was supported on CM7. But then again, if it's anything like Linux distros, using one of the more popular ROMs has its benefits as those are normally the highest supported.
People weren't lying when they said stop googling and just go to XDA forums. Thanks for the help yet again, bro.
im using cm7 and both google navigation and latitude work for me. and i know that the link i gave you said optimus p500 roms, but all p500 roms work for the p509 (since they both use the same hardware). just remember not to flash any roms from any other forums, flash only from the p500 forum
glad i could help. if you need any more help, just refer to that forum or pm me (since i have the same phone as you)
Sweetnsour, I was just suggesting Rom manager to be able to flash clockwork, then he could flash amon_ra from inside clockwork. I think that's possible? It was more of a hint for a newer user. I remember being on the other side and since I don't personally own your device, I was just offering general android advice. Glad to see you corrected me though, anyway, good luck OP. Hope you enjoy your device modifications.
I come here with my tail between my legs ducking from any backlash I may get from any users here. I spent the better part of the evening Googling around, asking in IRC, and trying to get this part working.
I ran into several issues. Some of them are quite comical to me.
I Googled around, as well as utilized the links that were provided to me in this thread. I learned that Clockwork and Rom Manager are from the same dev team, but they are two separate products. Likewise, I was hearing other users confirm that Clockwork is the bees knees but that Rom Manager is kind of "ehh" with predictability and reliability.
After I ran into some road blocks I ended up asking in the IRC Android chat room. Some users in there directed me to some guides. I read through them. Of course, each one was different. So to a user like me, I have no idea which one is the better one to go with. The one guide kept talking about how I need to run a .sh script. So, of course, I download the files supplied and extract them. No .sh script. I ask in the IRC chat and I caught hell because I should read the directions more clearly. I read through them several times and got no where. Ultimately, some users in the IRC chat decided to link me to the guide they recommended. Later, I too ran into a road block there.
Moving along, I went into the XDA-Devs chat once I found myself at the next road block. There some users spoke to me about what I was trying to do. I linked to them the guides the Android users told me to use and they were wondering why I was using such old guides to do this simple task.
This is where my frustration is brewing. There are a million and one ways to do everything. There's no structure. No consistency at all. I've done a ton of reading and I still feel like I know next to nothing about doing a "simple" recovery. I know phones are different. I know ROMs are different. But holy hell. Doing "xyz" task on one Android phone vs the same task on another Android phone is as different from driving a lawnmower vs a dump truck.
At this point I installed Android SDK on my Ubuntu machine. However, "adb shell" was yielding a command not found error. It's nearly 2 am. I'm packing it up for tonight.
That said, let's back up a bit here. My goal is this. I have an LG Optimus T. I have it rooted. I would like to utilize Clockwork in order to do a recovery as Clockwork came heavily recommended by many sources I read about. Then, I would like to utilize the XDA site for a list of available ROMs for my phone and choose one of my liking.
Is this guide, right here what I should be using to get this job done?
Along with that, how exactly do I need to install SDK on Ubuntu so it works without headache?
Thank you to everybody who has been patient with helping me learn this stuff so far.
that guide works. after you flash the recovery from that guide, don't think that you are always stuck with it. you can always flash another recovery in recovery. as for sdk, do you need it to flash recovery? those commands to flash recovery can be done on the phone using a terminal emulator. (about installing sdk on ubuntu, I will check on that tmrw because I'm doing this on my phone, and over where I'm at I should be sleeping)
EDIT: and here's a list of roms for our phone http://forum.xda-developers.com/showthread.php?p=16535249
EDIT: for sdk, have you tried this?
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Sent from my LG-P500 using XDA Premium App
Okay. I wasn't sure if it was safe to run those commands from the phone. I was tempted to but, ahh, figured I'd wait.
Now these instructions are exclusive to the Clockwork mod, correct? So if I get any other recovery (Amon Ra, for example) there will be specific instructions for that exact recovery too as well, right?
I'll give this a shot later and see where I end up. Thanks for your help!
Edit... It's a shame those commands aren't in an sh script already. Just a fun idea... What I'd add them to a blank text file and on the phone just chmod +x it and run it. Would that work??
the commands are fairly similar:
cwm (from your guide):
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
#cat /sdcard/flash_image > /system/bin/flash_image
#chmod 755 /system/bin/flash_image
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
#flash_image recovery /sdcard/recovery.img
#reboot recovery
amonra (from here):
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
# flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
# reboot recovery
after you flash either cwm or amonra, you wont have to do this again when you flash another recovery. to flash another recovery, you would just have to flash the recovery zip in recovery. these zips can be found here

[Rooting & ROM Flashing VZW GS3] Noob Questions

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?

Easy way to keep one's personal data when flasing a new ROM

Most of the time when one flashes a new ROM one has to do a data wipe (factory reset), and it erases all one's personal files like movies, music, pictures etc, quite annoying to say the least.
I found a way to avoid this, and it's pretty simple:
1-in CWM go to mount,
2-mount both data and system,
3-format them both.
This will perform the factory reset without erasing our precious files (the installed apks will be gone though, but no biggie if you backed up them with Titanium).
Then you can wipe cache + dalvik and flash your new ROM.
I used this method to go from ICS to CM 10.1, from CM 10.1 to Paranoid Android, and finally back to ICS, without loosing a single kb of my files.
Edit:
I have a p6210, no idea whether it works on other models or not. I guess it does but who knows...
Give it a try if you feel like it, but don't forget to make a back up before in case it goes wrong.
After flashing, your files won't be in the mnt/sdcard anymore but in a newly created folder in mnt/sdcard/0, or, depending the rom you are using, in storage/sdcard/0.
Or, some roms may create a file called legacy and stock everything there, or sometimes your files may be stocked before the sdcard folder, search for either /0 or /legacy.
Use a root browser and have a look, your files are still in your device (have a look as well at your storage in general settings, it will show how many gbs are in your tab).
Once you have found your files all what you have to do is to move them back where they belong, ie the /sdcard folder, it takes 10 seconds.
unclefab said:
Most of the time when one flashes a new ROM one has to do a data wipe (factory reset), and it erases all one's personal files like music, pictures etc, quite annoying to say the least.
I found a way to avoid this, and it's pretty simple:
1-in CWM go to mount,
2-mount both data and system,
3-format them both.
This will perform the factory reset without erasing our precious files.
Then you can wipe cache + dalvik and flash your new ROM.
I used this method to go from ICS to CM 10.1, from CM 10.1 to Paranoid Android, and finally back to ICS, without loosing a single kb of my files.
Give it a try if you feel like it...
Click to expand...
Click to collapse
Not cool man.Fu** lah.I lost everything.Around 7 GB of files.Fu** lah.I have no backup.I thought it would work.I was going from cm10.1 to cm10.What am I going to do?
Re: Easy way to keep one's personal data after flasing a new ROM
ALWAYS create a backup before erasing/flashing ANYTHING!! It's always as a precaution, to avoid losing something that you don't want to. And it only takes like 5 seconds literally. I lost some stuff when I unlocked the bootloader on my nexus10 by factory resetting, and I must say I didn't have a smile on my face. But it happened, u live n learn. I'm afraid if u wiped without making a nandroid backup your probably out of luck. Unless your skilled in using forensics techniques to try to recover it. Can't think of any options tho.
Sent from my SCH-I535 using xda app-developers app
Balaram12 said:
Not cool man.Fu** lah.I lost everything.Around 7 GB of files.Fu** lah.I have no backup.I thought it would work.I was going from cm10.1 to cm10.What am I going to do?
Click to expand...
Click to collapse
What did you do?
Did you follow the exact procedure?
I flashed again some roms today and it worked again.
But one thing is that the files are not in the mnt/sdcard anymore but in a newly created folder in mnt/sdcard/0, or, depending the rom you are using, in storage/sdcard/0.
Or, some roms may create a file called legacy and stock everything there, or sometimes your files may be stocked before the sdcard folder, search for either /0 or /legacy.
Use a root browser and have a look, your files are still in your device (have a look as well at your storage in general settings, it will show how many gbs are in your tab).
Once you have found your files all what you have to do is to move them back where they belong, ie the /sdcard folder, it takes 10 seconds.
This said, meishkov is right, one should allways have a back up in case anything goes wrong, I should have mentioned it in the OP but I forgot, my bad...
Edit:
OP edited.
Oh well, noone tried?
Would be nice to hear some reports...
Balaram, it would be fair from you to detail a bit what happened and to tell if you found back your files.
Anyway, this method worked for me and I thought that it might have interested some people here, roms flashers and devs alike, but if that s not the case then no worries.
If someone feels that I should erase the whole thread just tell me and I ll do it...

[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.

[Q] Exchange the whole UI stack on Android

Hi
I am new to hacking android. I have built linux distros in the past, and have worked with Linux for 15 years,
I have just rooted a ZTE V965. It doesn't come pre-installed with Play store, and has all sorts of ZTE-specific Chinese apps. It has a good baseband circuit, a good screen, reasonable camera and I think is a great value phone, apart from the awful UI.
It is an android phone, although heavily customised. It has an MTK6589 processor coupled with 4Gb ROM and 512Mb RAM.
I have other phones which operate a much more "Vanilla" android. For example, the Guophone 9105 which also uses an MTK6589. This has a troubling tendency to reboot every random interval. Approx 6 times a week.
I have had success in the past running Linux systems built for much earlier kernels on later kernels. This suggests the ABI (application binary interface) for the Linux kernel changes rather slowly.
I am wondering how well the userland apps are separated from the kernel and drivers on Android.
Specifically, is it feasible to dump all the UI stuff from one phone onto another then change the init to launch the other UI?
Would this risk bricking the phone, or would the shell commands and ADB infrastructure still likely operate?
I guess I should change the bootloader to one that supports fastboot first, right? Is ther a how-to on achieveing this from the root shell?
Thanks for any thoughts
Nick.
Nick Hill said:
Hi
I am new to hacking android. I have built linux distros in the past, and have worked with Linux for 15 years,
I have just rooted a ZTE V965. It doesn't come pre-installed with Play store, and has all sorts of ZTE-specific Chinese apps. It has a good baseband circuit, a good screen, reasonable camera and I think is a great value phone, apart from the awful UI.
It is an android phone, although heavily customised. It has an MTK6589 processor coupled with 4Gb ROM and 512Mb RAM.
I have other phones which operate a much more "Vanilla" android. For example, the Guophone 9105 which also uses an MTK6589. This has a troubling tendency to reboot every random interval. Approx 6 times a week.
I have had success in the past running Linux systems built for much earlier kernels on later kernels. This suggests the ABI (application binary interface) for the Linux kernel changes rather slowly.
I am wondering how well the userland apps are separated from the kernel and drivers on Android.
Specifically, is it feasible to dump all the UI stuff from one phone onto another then change the init to launch the other UI?
Would this risk bricking the phone, or would the shell commands and ADB infrastructure still likely operate?
I guess I should change the bootloader to one that supports fastboot first, right? Is ther a how-to on achieveing this from the root shell?
Thanks for any thoughts
Nick.
Click to expand...
Click to collapse
Hi Nick, I have the same phone. I'm also very new to android, last phone was iOS and before that windows. I managed to root the V965 using Vroot. I also managed to install SuperSU and CWM. However, the CWM is not fully functional, I can only do a factory reset, not install any packages or roms. Probably the phone has a locked bootloader. I can't check, because the USB driver with the phone doesnt support fastboot.
I really need to get google play working in this phone, read a lot of stuff, tried many things, but I havent succeeded yet. Please let me know if you make any progress.
In China they are flashing this phone, found some ROMs even, but I am not sure how they manage and google translate isn't much help there.
http://www.romjd.com/Device/zte-v965/hot/all/1
Hmmm my V965 is having some issues now
After a factory reset, the setup wizard keeps crashing. Even after another resest. So I can't get in the phone anymore.
Any chance you can send me the USB drivers that are on the phone? My phone isnt deteceted anymore, so I can't access the drivers, which I want to reinstall. And of course they are not on the ZTE website.
Byte_Me said:
Hmmm my V965 is having some issues now
After a factory reset, the setup wizard keeps crashing. Even after another resest. So I can't get in the phone anymore.
Any chance you can send me the USB drivers that are on the phone? My phone isnt deteceted anymore, so I can't access the drivers, which I want to reinstall. And of course they are not on the ZTE website.
Click to expand...
Click to collapse
Hi
You can temporarily download the ZTE v965 USB drivers from
www dot nickhill dot co dot uk forward slash ztev965usb dot zip
Byte_Me said:
Hi Nick, I have the same phone. I'm also very new to android, last phone was iOS and before that windows. I managed to root the V965 using Vroot. I also managed to install SuperSU and CWM. However, the CWM is not fully functional, I can only do a factory reset, not install any packages or roms. Probably the phone has a locked bootloader. I can't check, because the USB driver with the phone doesnt support fastboot.
Click to expand...
Click to collapse
Fastboot and ADB appear to be standard protocols, at least on my Ubuntu, which don't need special drivers. However, it does appear that the stock boot loaader on the v965 does fail to incorporate the fastboot option.
If you remove the battery, replace it then turn on holding the volume down, you will get a menu, but fastboot is not there.
I don't know for a fact, but I do suspect that if you have access to the running android system as root, then you could in principle change any of the internal flash data. Therefore, in principle, I guess you could replace the boot loader or anything else in the running android system. Anyone please correct me if I am wrong, or confirm if I am right.
The feature set of this phone seems to be the same as the feature set of my Guophone. MTK6589, dual SIM, etc. So this image may be a good place to start if considering a transplant.
If you have ROMs, then perhaps it is possible to flash the ROM from a root terminal. I'm thinking add the uncompressed ROM to the Micro SD card, then using the dd command, block copy it to the appropriate image area on the internal ROM, reboot, reset to factory defaults.
If anyone more experienced than me with the nuts and bolts of Android can confirm or deny this will work, or where it should be put, please let me know.
An important factor is that the NAND is not locked on the ZTE V965. So if you have a root shell on the phone, you can issue the following command:
mount -o remount,rw /[email protected] /system/
Once you have done this, you will have read/write access to the system partition.
The only thing I then need to know is what should I avoid changing that may break the ADB bridge/root console?
And is all the UI stuff kept together, if so, where?
Shuffle it around a bit, make a new ROM
Thanks for the driver!
Unfortuntely it doesn't help
I found out the culprit, I tried to install gapps (google apps package) to the system app folder. I thought these changes would be reversed with a factory reset, but they are not. Setupwizard.apk keeps crashing and is preventing me from accessing my phone, so I must find a way to remove it from the system app folder. However, since this error occurred, I am not able to contact the phone in any way from the PC. Adb toolkit does not detect it, even when I reinstalled your driver. It's quite puzzling, I dont understand why in recovery mode I cannot connect adb-toolkit anymore.
Got my V965 working again, but it was a lot of hassle with shell access. Still not fully functional, no drives detected when i connect to USB, which is quite annoying, but not more than that. If you ever make any progress with google apps or flashing, please keep me informed, that would make this phone much more useable. I'll also keep hacking away at it, but without a bootloader unlock (I still think this is the problem), I don't think it will be possible.
I'm convinced it's possible to flash the phone, it seems they do it a lot in China.
I found a website with a couple of custom ROMs specific for the V965:
http://www.romjd.com/Rom/Detail/17086
And what I suspect is a rooting & flashing tool. Rooting works, I haven't figured out flashing yet.
http://dl.vmall.com/c0xa12brvo
I've also tried flashing from the settings - update menu in the phone, but it never finds the ROM (update.zip)
I did find another problem, I can't be reached on my phone, it always goes to voicemail. Same SIM in another phone works fine. No idea what's causing this.
Byte_Me said:
Got my V965 working again, but it was a lot of hassle with shell access. Still not fully functional, no drives detected when i connect to USB, which is quite annoying, but not more than that. If you ever make any progress with google apps or flashing, please keep me informed, that would make this phone much more useable. I'll also keep hacking away at it, but without a bootloader unlock (I still think this is the problem), I don't think it will be possible.
Click to expand...
Click to collapse
Hi
I might be able to help you with the problem.
I have a mint, unused ZTE v965. I have used MTK Droid root and tools to extract a backup of the entire new phone. It is currently uploading to www dot nickhill dot co dot uk forward slash ZTE-V965_new_backup.zip
You should be able to write this back to your phone using flashtool.exe.
I don't know for sure if this will work, so entirely at your own risk! Just trying to help. If unsure, ask around.
I am new to this forum, so please remember to click the thanks button if you find anything I have done helpful!
Meanwhile, the MTK droid root and tools has a function to remove much of the chinese stuff (once the system has been installed) and there is always the cyanogenmod gapps package. This may be worth investigating.
Nick Hill said:
Hi
I might be able to help you with the problem.
I have a mint, unused ZTE v965. I have used MTK Droid root and tools to extract a backup of the entire new phone. It is currently uploading to www dot nickhill dot co dot uk forward slash ZTE-V965_new_backup.zip
Click to expand...
Click to collapse
The file size should be 635,972,093 bytes and should finish uploading at 04:00 GMT
md5sum 17ecfdd1040d5dbfab70a3adbc24e07a
Thanks for the ROM, i'll give it a go. I will try to install it using the update option in the settings, that seems the safest.
Be careful with gapps. setupwizard.apk + factory reset = a lot of problems (if you install in system app folder)
OMG that tool is awesome. created CWM boot, installed your ROM, then installed a clean ROM, then installed gapps, all working!!!
Byte_Me said:
OMG that tool is awesome. created CWM boot, installed your ROM, then installed a clean ROM, then installed gapps, all working!!!
Click to expand...
Click to collapse
Firstly, I'm glad it's working for you.
Secondly, which tools did you use? Did you unpack the zip, open flashtools, select the scatter file then program the phone, or did you use some other method?
Which clean ROM did you then install, and how did you install it?
Did you then use MobileUncle to install CWM then use the cyanogenmod 10.1 gapps, or did you do something different?
It is useful to remember that MTKdroidtools has a useful function to remove chinese stuff. I think if more people contributed to the list of Chinese files that are safe to remove, that would be blade.
A detailed step-by-step guide might be helpful for anyone else with the same problem. One of the general problems I find is that there are plenty of guides around referring to this program, or that program, but few are detailed enough for someone who doesn't already know about those programs to use.
I pretty much bricked a Lenovo A766 yesterday, and it took several hours to learn about the tools to eventually unbrick it.
I would have rather spent my time understanding what is really going on, rather than spending my time learning vaguely what tool achieves what end result. If I understood more about the Android system, and built that knowledge on my understanding of Linux, I reckon I could achieve much more.
One thing I notice is that tablets and smartphones are actually replacing desktops and laptops. February this year, windows machines were down 7% YOY. I use Ubuntu for my main computer. Using these tools on Windows led me to significant frustration! This has led me to understand why there is a move. Maybe the tools provided for windows need to eventually move to android. We could then potentially use USB OTG to service other android devices. MTKdroidtools and flashtools runnng as a host on a separate Android system would be cool.
Nick Hill said:
Firstly, I'm glad it's working for you.
Click to expand...
Click to collapse
Thanks, me too
Secondly, which tools did you use? Did you unpack the zip, open flashtools, select the scatter file then program the phone, or did you use some other method?
Click to expand...
Click to collapse
I used MTK tools as described in that topic, rooted, made backup, installed CWM
Which clean ROM did you then install, and how did you install it?
Click to expand...
Click to collapse
I used the update tool from CWM to flash this ROM:
http://www.romjd.com/Rom/Detail/17086
That ROM is not very clean though, You might as well clean your own ROM
Did you then use MobileUncle to install CWM then use the cyanogenmod 10.1 gapps, or did you do something different?
Click to expand...
Click to collapse
CWM is installed using MTK Droid Root and Tools:
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
This gapps version I installed: gapps-jb-20121011-signed
It's installed using CWM bootloader: install .zip package
It is useful to remember that MTKdroidtools has a useful function to remove chinese stuff. I think if more people contributed to the list of Chinese files that are safe to remove, that would be blade.
Click to expand...
Click to collapse
I used the delete China function, but it didnt catch very much. But with all the functions available now, it's quite easy to clean manually.
A detailed step-by-step guide might be helpful for anyone else with the same problem. One of the general problems I find is that there are plenty of guides around referring to this program, or that program, but few are detailed enough for someone who doesn't already know about those programs to use.
Click to expand...
Click to collapse
Yes, I plan to make a topic for this phone, but at the moment I am still testing many things.
I pretty much bricked a Lenovo A766 yesterday, and it took several hours to learn about the tools to eventually unbrick it. I would have rather spent my time understanding what is really going on, rather than spending my time learning vaguely what tool achieves what end result. If I understood more about the Android system, and built that knowledge on my understanding of Linux, I reckon I could achieve much more.
Click to expand...
Click to collapse
I know how you feel, I was ready to toss this phone in the trash
One thing I notice is that tablets and smartphones are actually replacing desktops and laptops. February this year, windows machines were down 7% YOY. I use Ubuntu for my main computer. Using these tools on Windows led me to significant frustration! This has led me to understand why there is a move. Maybe the tools provided for windows need to eventually move to android. We could then potentially use USB OTG to service other android devices. MTKdroidtools and flashtools runnng as a host on a separate Android system would be cool.
Click to expand...
Click to collapse
I have no idea about the possibilities there. I'm not a programmer, just someone who is good with computers and knows a little bit of everything.
PS. I could also use some thanks as well, maybe get some respect around here
Nick Hill said:
...
Click to expand...
Click to collapse
Did you give it a try yet? Another user did and google apps are working for him, so thats 2 for 2.
Are you still on your original ROM? If so, I have a question for you. Do you get notification badges on your icons, for instance, when you have a missed call, is there a red box with a 1 on the phone icon? Also, do your contacts get ID-ed when they call you? I have some problems with that, caused by the country code prefix. I am still running that ROM I downlaoded from the Chinese forum, but if your ROM doent have these issues, I will switch back ASAP.
Nick Hill said:
Firstly, I'm glad it's working for you.
Click to expand...
Click to collapse
as you are a Lenovo a766 owner, may you help me with this?
http://forum.xda-developers.com/showthread.php?p=49076877#post49076877
Where are configuration settings stored accross factory resets?
I have come to the (perhaps erroneous) conclusion that the user interface and what the user will experience is governed primarily from:
the APKs in
/system/app/
/system/vendor/operator/app/
and the configuration files pertaining to the installed apps, which is located at:
/data/user/0/
I guess that when the android device is factory reset, the /data partition is completely cleared, right?
Is there a set of standard configurations which are unpacked from somewhere into /data/user/0/ after a factory reset, or is it normal for all configurations to be stored in their respective APKs?

Categories

Resources