I found I was repeating myself a lot when helping out people new to rooting their Evo. I also found that this knowledge I'm putting into this doc doesn't really exist in one place, but is spread throughout the entire Evo Forum. So below is some information to help out people with backing up their device, some backup tips, some general information on flashing, and tips and best practices for flashing. Hope this helps!!
Assumptions:
This guide assumes you are fully rooted at this point. If not follow any one of the guides in the Wiki that has been stickied on the main page of the Evo Dev forum. My personal recommendation is the Unrevoked. Very easy to use, just read up and make sure your phone is compatible.
To test root type "su" into a terminal. You should get a "#" back. You can use a terminal emulator from the market or ADB. To get ADB up and running follow this guide here. If that seems confusing than take a look at this guide I wrote for Notion Ink Adam Tablet users here. That guide is for Windows users, but Mac and *nix users shouldn't be much more difficult.
Backing up
NAND Backup:
Once rooted you can use the app quickboot to boot into recovery to do a NAND backup. If your ROM doesn't have this app installed, download from Marketplace. Open app and choose "Recovery". Once into your recovery use the volume buttons on the side to scroll up and down and power button to select to get to the option to backup. I have clockwork installed so my screen looks different, but you should be able to find the NAND backup option. This will take awhile so be patient.
Once done you can reboot and continue on as normal. This is an essential step (or using Rom Manager below). If you ever screw up something major or you try a new ROM and want to go back, this will allow you to restore easily and get back to a point where things worked fine. It would also be highly recommended to do one of these backups before doing something major that has potential to break things. Use best judgment here.
Rom Manager:
Even easier than the above is to use Rom Manager. Download it from the marketplace, run it, and let it update your recovery image for you. Once this is done go to the bottom of this app and choose "Backup Current ROM" This should do a full NAND backup. I would recommend buying this app for the other features it has, but it is up to you.
Titanium Backup (TB):
Once you have your NAND backup I would also recommend installing Titanium Backup from the Marketplace (I would also pay for the license because you get better performance and the dev deserves some green for this awesome app!). Once installed open it. The first time it will ask you to update Busybox. Let it and wait for this to download. When done it will ask you reboot app from the notification area. Do this and then wait for app to fully load, two messages should appear, the second one indicates it is fully loaded. Then hit menu and go to the batch section. Choose " Backup all user apps + system data".
This will backup everything on your phone for you to your SD card. This will take a while so go get some coffee and check back in. Do not close the app or turn off your phone, the screen can go blank and you can let it sit, but it will need time to run. I think when the screen turns off it puts an icon in notification that should be updating the progress of the batch. Once done, it should tell you in the notification area. For me it takes awhile with my 228 some elements I'm backing up. Your mileage will vary.
SMS/MMS
I recently came across a thread that mentions using Handy Backup for backing up SMS/MMS messages. I have not tried this app or used it so I don't have any directions to give on it. But I have had people ask and I have seen folks ask in other threads. So if TB doesn't give you enough, try this one too.
Backup to Computer:
I'm still looking for a better method for this one. I'm sure someone has something and if you do please let me know so I can update this section.
Currently I backup files and folders to my local NAS at home after major changes. Incremental changes I let TB handle. This is just a simple process of setting the SD card to storage and copy/paste. Works fine and I have only done this once so far after everything was set to my liking.
You might wonder why this important? Well if you are going to play around a lot with different ROMs and constantly read/writing info to your SD card, it is important because SD cards are not perfect. They can be corrupted and can fail from too much writing of info. It usually takes a lot of work to get one to the point of failure, but I managed to do it with my HTC Mogul so I can vouch that it can happen.
Important folders on SD card:
- /sdcard/clockwork/backup
This will get all backups performed by clockwork. If you grab the entire clockwork folder then you will get ROM downloads and such too. I don't really recommend this as it never takes more than 25 minutes for me to download any image. Plus with a secure NAND backup, you can always restore quickly.
- /sdcard/nandroid
This should backup the folder used by AmonRa recovery.
- /sdcard/TitaniumBackup
Folder used by TB for backing up of apps.
Of course throw in any other folders you deem important. What that is depends on you. Making a backup of everything else probably wont take long too. For me I rarely have more than 7gb of data on my card so backing up takes roughly 30-50 minutes.
All of this may seem like a lot of work, but once done you will have a robust system in place. And will allow you the opportunity to safely play!!
Restoring
Restoring is a simple process but can be time consuming. To speed things up you can pay for the full version of TB, which I highly recommend.
TB
Follow the directions below for what I do after flashing. If you have already read that and are ready to restore then do the following...
Open up TB and let if fully load, you will get two small popup messages. The second one means that TB has fully loaded the OS information. Then hit the menu key and choose batch. Scroll down and look for "Restore all apps with data". Run this batch to restore everything. Keep in mind if you backed up everything and are now changing ROMs that you might run into problems. I have yet to run across issues, but this is just an FYI. Also another reason to have a full NAND backup with Rom Manager. If you run into too many problems just restore with it and problem solved.
Restores and backups take awhile with TB, but are worth the wait. Once done with the full restore you can then do incremental backup and restores in the future.
Also don't forget to open up the apps after restoring and make sure the apps are setup how you want. Then double check with TB to make sure things are fully backed up, just click "Backup all new apps & newer versions". Once done with this reboot.
After a TB restore always reboot. After the reboot go into Rom Manager and NAND backup following the steps above in the backup section. This will ensure you have a full system backup with the settings you want.
Rom Manager
This one is pretty simple. Just open Rom Manager and choose "Manage and Restore Backups". Then choose your backup to restore. If you named the files by date and time you might have to do some guess work, but you should have a rough idea. Once you click the one you want just sit back and wait.
Flashing Tips and Problems
Watch Girls Gone Wild for help with this...
Many people have asked "Why flash custom ROM" or "What are the advantages"? Well I think one of the biggest reasons is performance gain from phone and apps. But for Evo users the number 1 reason should be better battery utilization. This can mean you see same amount of battery life, but with increased phone and app performance, or same performance, but longer battery life.
I think some people might be hesitant because it was one hell of a process rooting their device. Well to those people I say, you are over the mountain now. The hard part is done, flashing is relatively easy. I recommend doing it cause stock can cause some people minor issues and your are missing out on a lot of cool and useful customizations. And if you backup your phone as detailed above, you do not need to worry about losing anything.
Stock ROM with Root (back to defaults) or Completely Unroot:
To flash a stock ROM with root, download one from the wiki of ROMs. Then follow advice in below sections for flashing.
To unroot (This is the "I need to take my phone to Sprint" conundrum...) Follow the wiki link. Or go to HTC's website. Then go to the support section for the HTC Evo. Download the file from them and run it. You will be good to go. And if you followed the backup section above you do not have to worry about anything. Just re-root when you get your new phone or old phone back. And restore.
Also, I recommend taking out your SD card with all the root files on it. No need to bring this up or have to explain things any Sprint tech could easily see. Also if you used Unrevoked Forever you should follow this unroot guide here.
I Just Flashed with no Backups:
Below is what I did before I had Titanium Backup in place and after flashing a custom ROM...
Once booted right after flashing I make sure things look fine, fully sync to Google, then reboot. When I come back from that I turn on WiFi and go to Marketplace and Download section. Any apps I previously downloaded will be in that section waiting for me to download. Download them all at once, DO NOT leave that section before downloading everything, or you will lose that list and it will only show apps currently downloaded and installed.
Once done, open apps and customize to liking. Then download Rom Manager if you don't already have it and follow the above section. Once done with that follow the above section on Titanium Backup. Then enjoy your custom ROM.
Flashing in general:
ALWAYS make sure your battery is at least 50% full. The last thing you want is your phone to die on you in the middle of flashing.
Use Rom Manger and pay for the full version. It is a lot easier and can remove a lot of headaches and problems. If you really want to do it yourself you shouldn't have any problems, this is typically what I do and I haven't run any issues that couldn't be solved yet.
Follow the above backup guides before flashing another custom ROM. Save yourself time and trouble. Also I have read about people using NAND backups to sort of switch between different ROMs. In the short term that shouldn't be a problem, but long term that can make your SD card unstable. Make sure you follow the above section for backing up your SD card to computer.
If changing from one ROM to another it is best practice and almost always recommended to wipe data and dalvik cache. This also will alleviate many issues people run into. And if you follow my backup recommendations then it shouldn't be an issue to do either of these.
If not using Rom Manager, then put the zip of the ROM you want to flash on your SD card, and DO NOT unzip the zip file. Leave it on the root of your SD card as a zip file. Boot into recovery if you are not there already. Find the option to flash from SD card. Then choose the zip file or ROM you want to flash. Wait for everything to flash, then reboot using the option from the recovery menu. Wait for phone to boot. This can take a long time after flashing any new ROM so be patient.
Some ROM devs have other items you can add to their ROM. Follow their directions for flashing those items. Some devs want you to boot first than go back and flash, others allow for you to just start flashing right away with no waiting. Pay attention to the directions on your ROM thread. If you screw something up, try flashing the package again. If things look worse or it didn't work, re-flash your ROM or restore your backup and try again.
Otherwise, flash the ROM following directions above, flash the other packages and themes and items you want, and reboot. All should be well.
Once booted up follow guides above for backing up or restoring. Otherwise if you have problems look below before asking questions. If you can't find it here try searching before asking questions. If you still can't find it feel free to ask for help, but keep the question in the thread for your ROM you are flashing, or if you think it is a rooting issue, in the thread of the root process you followed.
Bootloop Issue:
This can be caused by a few things. For one, make sure you wipe data and dalvik cache before flashing a custom ROM. Even if the dev says it is not necessary do this before flashing a new ROM. It can help with these issues. The only exception here is if you are updating to a new version of the same ROM and the dev says there is no reason to wipe in between...
Also you can experience this if you are not fully rooted. Look toward the top of this guide for rooting advice.
Sometimes the ROM can take a while to boot after flashing a new ROM. Be sure you really do have a stuck boot or bootloop before doing a battery pull and troubleshooting. Give it some time to see if it fixes itself. If you are waiting over 30 minutes for something, you probably do have a legit issue.
Exclamation Point with Android Guy Screen
I got this when attempting to upgrade once. To get out of it, battery pull and put battery back in. Hold down "Volume Down Button" and then press power. KEEP HOLDING DOWN volume down button till white screen (Hboot) appears. Release volume down button. Wait for it scan. If it finds your PC file choose no and also no on reboot. NEXT CHANCE YOU GET remove, rename, or move the PC file from the root of your SD card. Choose "Recovery" from menu using volume buttons and power button to select. Once in recovery, choose flash from SD card and choose your ROM.
If you cannot find an image or do not have one, just go back and toggle USB. Then copy paste ROM to SD card. Keep in mind that you might need to wipe data and dalvik cache before flashing as mentioned above.
Another user commented this screen appeared when attempting to go into recovery from Quickboot app. This might mean the recovery image didn't install correctly, or could mean you do not have a recovery image flashed or installed. If this is the case, follow one of the guides in this wiki link to flash a recovery.
If you need to get out of this screen, just do a battery pull. Your ROM should boot up fine.
Battery Issues After Flashing:
Some have claimed issues with battery after flashing. To try recalibrating click here for Cyanogen's guide.
That's all for now!
I'm sure there is plenty more to add to this down the road, but for now this is all the dumping my brain can handle. Leave comments and suggestions and let's make this a strong guide with the right information to help those in need.
Very nice, hopefully you just saved someone a lot of heartache
Just added a section for un-rooting. Can someone please help me verify this is correct.
Thanks!
Awesome guide!
Thanks for the info in the Simple Root thread.
One question that was unanswered (and per your response I ask it here):
Are SMS/MMS info backed up using Nandriod or Titanuim??
I'm a little confused by which can do this.
Thanks again for the help.
ucf.elk said:
Awesome guide!
Thanks for the info in the Simple Root thread.
One question that was unanswered (and per your response I ask it here):
Are SMS/MMS info backed up using Nandriod or Titanuim??
I'm a little confused by which can do this.
Thanks again for the help.
Click to expand...
Click to collapse
Very good question on SMS/MMS. I think I have noticed that when using Handcent SMS app for sending and receiving SMS/MMS messages they are somehow backedup. I think Handcent has a folder on the SD card.
Otherwise if you are using stock messaging app, I am not sure it TB backs that up or not. If you want to verify this for me and let me know your results I would be happy to update my guide.
webs05 said:
Very good question on SMS/MMS. I think I have noticed that when using Handcent SMS app for sending and receiving SMS/MMS messages they are somehow backedup. I think Handcent has a folder on the SD card.
Otherwise if you are using stock messaging app, I am not sure it TB backs that up or not. If you want to verify this for me and let me know your results I would be happy to update my guide.
Click to expand...
Click to collapse
Just wanted to say thanks for the breakdown, and with my experience Tb has backed up my sms when backing up "all system data and apps"
Thanks again OP
epmacman said:
Just wanted to say thanks for the breakdown, and with my experience Tb has backed up my sms when backing up "all system data and apps"
Thanks again OP
Click to expand...
Click to collapse
Great info! Thanks epmacman and thanks webs05 for the great guide!
epmacman said:
Just wanted to say thanks for the breakdown, and with my experience Tb has backed up my sms when backing up "all system data and apps"
Thanks again OP
Click to expand...
Click to collapse
Were you using stock messaging app? Or a third party one from Marketplace?
Thanks for the information. About to start this whole process soon so this really helped Just a quick question though, do classes of the sd card matter? Have a class 2 card atm but about to buy a 16gig class 6 and figured I should do everything then.
Reanimatedshad0w said:
Thanks for the information. About to start this whole process soon so this really helped Just a quick question though, do classes of the sd card matter? Have a class 2 card atm but about to buy a 16gig class 6 and figured I should do everything then.
Click to expand...
Click to collapse
Yes, a higher class makes a big difference in speed. Make sure you wipe the new SD card from within the Evo before doing anything.
Dumb question (I'm new to Android):
When switching ROMs, both of which you have a backup for, do you have to wipe, flash the rom, then flash the nandroid backup?
Or would wiping and then flashing the backup work the same?
I have Fresh and Avalaunch's Froyo with all my apps both backed up. I realize it won't save much time, but I wouldn't have to keep both ROMs on my SD card if I could just use the backup to switch.
Thanks for the guide.
elr0y said:
Dumb question (I'm new to Android):
When switching ROMs, both of which you have a backup for, do you have to wipe, flash the rom, then flash the nandroid backup?
Or would wiping and then flashing the backup work the same?
I have Fresh and Avalaunch's Froyo with all my apps both backed up. I realize it won't save much time, but I wouldn't have to keep both ROMs on my SD card if I could just use the backup to switch.
Thanks for the guide.
Click to expand...
Click to collapse
you should wipe. the backup will save everything you had on the respective rom
Yes awesome guide thanks, just what I was looking for. Stupid question but when I do a "Backup Current ROM" in ROM Manager, does this also back up texts, apps, games etc?
Thanks again webs
elr0y said:
Dumb question (I'm new to Android):
When switching ROMs, both of which you have a backup for, do you have to wipe, flash the rom, then flash the nandroid backup?
Or would wiping and then flashing the backup work the same?
I have Fresh and Avalaunch's Froyo with all my apps both backed up. I realize it won't save much time, but I wouldn't have to keep both ROMs on my SD card if I could just use the backup to switch.
Thanks for the guide.
Click to expand...
Click to collapse
To switch ROM by restoring nand backups all you should have to do is go into recovery and restore the one you want. If you wanted to be safe you could wipe first. As far as flashing that rom before nand backup no. There would be no point of that. The nand backup restores ALL, everything that was on that phone previously. It is a full backup.
huzvi88 said:
Yes awesome guide thanks, just what I was looking for. Stupid question but when I do a "Backup Current ROM" in ROM Manager, does this also back up texts, apps, games etc?
Thanks again webs
Click to expand...
Click to collapse
Yes, it should backup everything. Upon restore your phone should look and act just as it was when you created that backup. The backup system in Rom Manager boots the phone to recovery and does a nand backup for you.
webs05 said:
Yes, it should backup everything. Upon restore your phone should look and act just as it was when you created that backup. The backup system in Rom Manager boots the phone to recovery and does a nand backup for you.
Click to expand...
Click to collapse
Haha that was my next question. Thanks really appreciate it!
huzvi88 said:
Haha that was my next question. Thanks really appreciate it!
Click to expand...
Click to collapse
Your welcome, and the same goes to everyone else.
I'm an idiot i think and just bricked my phone.
I used revoke website to root my phone I did not do a nand unlock. I then installed rom manager because I wanted to backup the current stock rom. I used the option to flash in something from rom manager and then back up. after that my phone restarted and all I see is a picture of a phone with and exclamation point. am I bricked? anything I can do? sorry I'm a noob.
-U
usctrunks said:
I'm an idiot i think and just bricked my phone.
I used revoke website to root my phone I did not do a nand unlock. I then installed rom manager because I wanted to backup the current stock rom. I used the option to flash in something from rom manager and then back up. after that my phone restarted and all I see is a picture of a phone with and exclamation point. am I bricked? anything I can do? sorry I'm a noob.
-U
Click to expand...
Click to collapse
Lol! You are fine. Fortunately HTC makes their phone tough to brick.
You are at that screen because you only did part 1 of Unrevoked's system. They have released part 2. Follow that and you should be good to go. Post questions on their threads. Good luck.
lol thanks
Please bear with me and my noob questions. I have a rooted and unlocked Infuse 4 G. At the moment I am using t mobile monthly 4 g unlimited pre paid.
I have never done anything to the phone besides using the bml3.bk file in the hex editor to unlock the phone. I have some apps installed, and I have installed titanium back up but have not ran any back ups.
I have read the instructions but I am still confused and worried I might brick my phone. I do not have any warranty on it.
I have had others tell me that the Infused 2.1.0 and infusion 1.1 kernel running 1.6ghz would be the best way to go.
And that CMW recovery is the safest way to install it.
It says not to back anything up with titanium recovery. Does that mean that I will lose all of my apps? Or that I will lose all of my contacts or progress in apps, such as games and kindle books?
Will I lose my APN settings?
Also if I have not backed anything up, what happens if I make a mistake in the installation? Is there a way to get my stock settings back?
Also, just to be sure, I would download the zip files directly to my phone, from my phone correct? Just making sure I do not download them to my PC and then transfer them to my sd card.
Also what about the updates and beta versions? Should I use the most updated file or an older one?
Also, I do use facebook, so I can reinstall that after the ROM is installed?
I really appreciate the help and patience with all my questions.
Export your contacts to your SD card.
Myself, I backed up my apps, then restored apps & data.
(note: do "NOT". restore system data)
The apps that you have can be redownloaded if need be.
Yes to Facebook.
My suggestion would be to just install the Infused 2.1.0 first. Get used to it before going in deeper.
Yes, you can download or transfer the Infused 2.1.0 to your SD card and install from there.
Go directly to Infused 2.1.0. No need to install the beta's.
I'd say that the safest & easiest way to install Infused 2.1.0, is by using Rom Manager, especially if you're new at this.
Truckerglenn said:
Export your contacts to your SD card.
Myself, I backed up my apps, then restored apps & data.
(note: do "NOT". restore system data)
The apps that you have can be redownloaded if need be.
Yes to Facebook.
My suggestion would be to just install the Infused 2.1.0 first. Get used to it before going in deeper.
Yes, you can download or transfer the Infused 2.1.0 to your SD card and install from there.
Go directly to Infused 2.1.0. No need to install the beta's.
I'd say that the safest & easiest way to install Infused 2.1.0, is by using Rom Manager, especially if you're new at this.
Click to expand...
Click to collapse
Thank you! Is it better to download the zip files directly to sd card using my phone or using the PC? And is it safe to use titanium back up to back up the apps? And I guess I am just confused. Do I back up the apps I have that I want to keep that are not in the ROM? Or do I back up ALL of the apps I have? Im sorry, Im sure I seem like an idiot, but I want to make sure I am clear on what to do......thank you so much!
Also If I do not back up my stock system, will I be able to go back to stock if something messes up?
emeralds5668 said:
Thank you! Is it better to download the zip files directly to sd card using my phone or using the PC? And is it safe to use titanium back up to back up the apps? And I guess I am just confused. Do I back up the apps I have that I want to keep that are not in the ROM? Or do I back up ALL of the apps I have? Im sorry, Im sure I seem like an idiot, but I want to make sure I am clear on what to do......thank you so much!
Click to expand...
Click to collapse
I downloaded them to PC and transfered them sd. Yes, its safe to backup apps with titanium, when you go to reinstall them, just restore apps and data, NOT system data. Just back all of them up, you can restore each that you want later. Just read all the installation instructions a couple of times until you understand the process. Once you do it, you'll realize its not hard. Install the ROM first, then, the kernel. If you do brick your phone, you can use Odin-to-Stock to return the phone to its stock. You'll be glad you upgraded to a custom ROM, its much faster. Only downfalls on Infused 2.1.0, (latest version) is that there is no HDMI support, and the video recording is not 30fps like it should be, but these problems will be fixed soon.
Do NOT run Infusion (or any other overclock/undervolt kernel) until you're perfectly satisfied with the stability of the ROM in question without the modded kernel.
Overclock/undervolt kernels can cause instability that may be misdiagnosed as a ROM bug.
Entropy512 said:
Do NOT run Infusion (or any other overclock/undervolt kernel) until you're perfectly satisfied with the stability of the ROM in question without the modded kernel.
Overclock/undervolt kernels can cause instability that may be misdiagnosed as a ROM bug.
Click to expand...
Click to collapse
True, only reason I say this is because they work great together. But he's right, once you install you may not like the ROM or something else, like have problems with it. You can install the kernel anytime. You will need a overclock app like voltage control or setcpu in order to get it overclocked.
Sent from my SAMSUNG-SGH-I997 using XDA App
Hey guys, I'm rather new to the world of customising Android devices. I just have SO MANY QUESTIONS right now. And I'm sure I'm not the only one, which is why I created this thread to help myself and other people.
Basically, I'll be asking a bunch of questions related to the topic, and this can help other people who are new to all this too.
So, I've got a rooted device. It's on lollipop 5.0, has an unlocked bootloader, TWRP recovery, and Xposed framework.
A few questions to start off with:
1) Can I flash multiple .zip/.img files one after another? Or do I need to always wipe my phone's cache after each flash?
2) Say I wanna update TWRP recovery. Do I have do something before flashing it? CAN I flash a newer version over the previous one?
3) Same question as 2) but for Xposed framework instead.
4) I have Xposed framework installed with some modules running on my phone. Should I disable these modules before updating my Xposed?
5) The latest version of Xposed is v86 as given here: http://forum.xda-developers.com/showthread.php?t=3034811
Can v86 work for lollipop?
6) Similarly, can one download any TWRP version and flash it for their device? Or do each build have a different, specific version of TWRP?
7) Are the latest recovery mods and Xposed frameworks always guaranteed to be stable? Or is it safer to stay on the older ones? Which ones would you recommend?
8) Now, the custom ROMS. What are the necessary things to do before flashing one of these?
9) After flashing a custom ROM, can you flash another on top of it? Or do you have to restore back to your original stock ROM?
10) Does flashing and switching between custom ROMs cause any damage to the phone? Or is there any such potential?
11) Since backing up is a must, I'll ask some about that too. Which would you suggest to be the best backing up method?
12) Does creating a NANDroid backup or a backup from within custom recovery(TWRP in my case) equal to creating a backup of stock ROM?
13) Do I need to copy that backup into PC(to restore later), or will it be safe in my phone's memory after flashing a custom ROM?
I guess that's about it for now. Everyone, please answer if you have done these before. And of course, add your own questions too. This can save a lot of time for a lot of people. I could add more questions in if people request it.
**Answer mentioning the question number for simplicity of searching.
Answers!
1) Can I flash multiple .zip/.img files one after another? Or do I need to always wipe my phone's cache after each flash?
Click to expand...
Click to collapse
You can, but it is more recommended to wipe cache and dalvik cache with each flash.
2) Say I wanna update TWRP recovery. Do I have do something before flashing it? CAN I flash a newer version over the previous one?
Click to expand...
Click to collapse
You'll have to wipe dalvik cache and cache and just flash it normally. It might be stuck at 90% but a force reboot fixes it. It is because you are already in recovery. If it is stuck, leave it for 15 mins and come back. This is just to ensure that it really is stuck.
3) Same question as 2) but for Xposed framework instead.
Click to expand...
Click to collapse
Yep, works, except you wont be stuck.
4) I have Xposed framework installed with some modules running on my phone. Should I disable these modules before updating my Xposed?
Click to expand...
Click to collapse
No need
5) The latest version of Xposed is v86 as given here: http://forum.xda-developers.com/showthread.php?t=3034811
Can v86 work for lollipop?
Click to expand...
Click to collapse
Yup, just flash it via recovery
6) Similarly, can one download any TWRP version and flash it for their device? Or do each build have a different, specific version of TWRP?
Click to expand...
Click to collapse
Each build is different for each device, so for example, I can't flash a TWRP for s7 edge on my s4.
7) Are the latest recovery mods and Xposed frameworks always guaranteed to be stable? Or is it safer to stay on the older ones? Which ones would you recommend?
Click to expand...
Click to collapse
In example, xposed and supersu framework and binary lets you choose if you want a stable file or a test one for developers. TWRP and other stuff have (what I know) different versions and as stated, these versions behave different on different device. During testing with my S4, I found that TWRP 2.8.7.0 is the most stable build for my device.
8) Now, the custom ROMS. What are the necessary things to do before flashing one of these?
Click to expand...
Click to collapse
Make a nandroid backup of your whole device and back it up on you computer. Then wipe everything except your external sdcard and either store it on an sdcard or "adb sideload" it.
9) After flashing a custom ROM, can you flash another on top of it? Or do you have to restore back to your original stock ROM?
Click to expand...
Click to collapse
Not on top of it, you'll have to do as the answer to question 8, make a backup, wipe everything and then flash. No need to go back to stock ROM and then flash it
10) Does flashing and switching between custom ROMs cause any damage to the phone? Or is there any such potential?
Click to expand...
Click to collapse
There is always the risk of bricking but as far as software, it is always revertable. As long as you have a backup of course.
11) Since backing up is a must, I'll ask some about that too. Which would you suggest to be the best backing up method?
Click to expand...
Click to collapse
Nandroid backup is the best one.
12) Does creating a NANDroid backup or a backup from within custom recovery(TWRP in my case) equal to creating a backup of stock ROM?
Click to expand...
Click to collapse
It creates a backup of your current state, lets say, you are in Cyanogenmod 13, making a Nandroid backup will backup everything on cyanogenmod so that if you flash another ROM and still want to go back, you'll have everything restored, including app data and apps.
13) Do I need to copy that backup into PC(to restore later), or will it be safe in my phone's memory after flashing a custom ROM?
Click to expand...
Click to collapse
It will take up a lot of space on your device (since it is a backup of your whole device) so it is recommended to copy it to your computer and remove it from the phone. But, as always, make sure you copy the whole "BACKUPS" folder because the folder inside that folder has your device ID and it is required by TWRP to have the folder the exact ID of your phone to prevent anything bad from happening (bricks).
Hope, I answered all the questions as you wanted and if you have a new question, post it here and I'll reply as soon as possible
Hey, thanks a lot for answering. It helps a lot.
A few other questions I have:
14) So if I were to get CM13, and then create a backup of it, and then get another rom, say ASOP, create a backup of that too, and then switch to yet another rom, say Resurrection Remix, create a backup of that too.
Now, is it possible for me to be able to SWITCH between multiple roms, with ALL my data saved individually on each rom perfectly the way I wanted?(of course, wipe cache and data before restoring the backup)
If so, then I could just keep Nandroids of my favorite roms, can keep switching between them, never having to flash and start from scratch ever again!
Sent from my ASUS_T00J using XDA-Developers mobile app
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
16) Suppose I flashed CM13, and it's really buggy. Can I switch back to the previous rom whose nandroid I had just by restoring it? Is it really that simple?
Sent from my ASUS_T00J using XDA-Developers mobile app
ShinraTensei04 said:
Hey, thanks a lot for answering. It helps a lot.
A few other questions I have:
14) So if I were to get CM13, and then create a backup of it, and then get another rom, say ASOP, create a backup of that too, and then switch to yet another rom, say Resurrection Remix, create a backup of that too.
Now, is it possible for me to be able to SWITCH between multiple roms, with ALL my data saved individually on each rom perfectly the way I wanted?(of course, wipe cache and data before restoring the backup)
If so, then I could just keep Nandroids of my favorite roms, can keep switching between them, never having to flash and start from scratch ever again!
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
14) You can, but you would need tons of space.
Sent using a ks01lte (gt-i9506) running cm 13
---------- Post added at 05:59 AM ---------- Previous post was at 05:56 AM ----------
ShinraTensei04 said:
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
You do not have to have an sdcard reader to view your sdcard on your PC. You know how when you make a backup it is stored in /sdcard/TWRP/BACKUPS/CERIALNM/nameofbackup? Well, connect your phone to your pc and move the "backups" folder, then, when you need to restore it, add it to the twrp folder and restore it.
Sent using a ks01lte (gt-i9506) running cm 13
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
ShinraTensei04 said:
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
Also, on the titanium backup part, not a bad idea... You can then copy the data and system or boot to your pc and bam.
Sent using a ks01lte (gt-i9506) running cm 13
What I meant was: Let's say I bricked my phone. Now, according to you, I place backup on pc. Okay. But now, how do I place this backup onto the sd on my phone when my pc can't even detect the phone(cuz it's dead yo). Doesn't this impose on me to keep the backup in sd(as I don't have reader or otg).
About the titanium, so you're saying I can do that? Backup only user apps+data and restore after restoring only system+boot.
Another question:
16) Can the backup of user apps+data made on, say, 'X' rom, be restored on 'Y' rom via titanium, on condition they are same Android version(suppose 5.0), without ANY chance of incompatibility. More importantly, can it have any chances of leading to a brick/bootloop.
* I read somewhere that if you backed up system apps of 'X' rom, then changed to 'Y' rom, and restored the system apps of 'X' rom onto 'Y' rom, it bricks the phone.(which is why I ask this question)
17) "Backing up 'system' in TWRP is completely different from backing up 'system' on titanium. This is because TWRP backs up entire system with system apps, while titanium only backs up the apps." This is true, right?
Sent from my ASUS_T00J using XDA-Developers mobile app
ShinraTensei04 said:
What I meant was: Let's say I bricked my phone. Now, according to you, I place backup on pc. Okay. But now, how do I place this backup onto the sd on my phone when my pc can't even detect the phone(cuz it's dead yo). Doesn't this impose on me to keep the backup in sd(as I don't have reader or otg).
About the titanium, so you're saying I can do that? Backup only user apps+data and restore after restoring only system+boot.
Another question:
16) Can the backup of user apps+data made on, say, 'X' rom, be restored on 'Y' rom via titanium, on condition they are same Android version(suppose 5.0), without ANY chance of incompatibility. More importantly, can it have any chances of leading to a brick/bootloop.
* I read somewhere that if you backed up system apps of 'X' rom, then changed to 'Y' rom, and restored the system apps of 'X' rom onto 'Y' rom, it bricks the phone.(which is why I ask this question)
17) "Backing up 'system' in TWRP is completely different from backing up 'system' on titanium. This is because TWRP backs up entire system with system apps, while titanium only backs up the apps." This is true, right?
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
You adb sideload a functioning ROM and once you boot you copy the backup you can flash it via twrp. As for the second question, I have not tested it but it sounds possible.
16) You should not be in a bootloop if you backup like that, the fact that it is even the same android version is making it more likely to work and what I know, you can even switch the backup via phones. I don't use titanium because I always do nandroid backups.
17) Yup, that's true, twrp sees "system as the partition system while titanium sees it as the whole phones software, hence why it is called " system".
Thanks for asking these question and hopefully some day, you can teach others.
RAZERZDAHACKER said:
You adb sideload a functioning ROM and once you boot you copy the backup you can flash it via twrp. As for the second question, I have not tested it but it sounds possible.
16) You should not be in a bootloop if you backup like that, the fact that it is even the same android version is making it more likely to work and what I know, you can even switch the backup via phones. I don't use titanium because I always do nandroid backups.
17) Yup, that's true, twrp sees "system as the partition system while titanium sees it as the whole phones software, hence why it is called " system".
Thanks for asking these question and hopefully some day, you can teach others.
Click to expand...
Click to collapse
Hm... so whenever I brick my phone, I MUST adb sideload to a working rom first, and only then restore the backup I made? Even if I already have a backup saved onto the sd card of my bricked phone? Can I not restore that via TWRP instead? I ask this because if I were to adb sideload first, I'd lose root, unlocked bootloader, and yes, TWRP. So, I'd have to get ALL that done again, and only then restore my backup.
18) Does restoring a backup I made(when I had root access, unlocked BL, custom recovery, xposed) RETAIN all that? Meaning after I restore to that backup, I will still have all that.
Thanks for answering, I'm learning quite a bit. And yeah, I'll make sure to help others with this information too.
ShinraTensei04 said:
Hm... so whenever I brick my phone, I MUST adb sideload to a working rom first, and only then restore the backup I made? Even if I already have a backup saved onto the sd card of my bricked phone? Can I not restore that via TWRP instead? I ask this because if I were to adb sideload first, I'd lose root, unlocked bootloader, and yes, TWRP. So, I'd have to get ALL that done again, and only then restore my backup.
Click to expand...
Click to collapse
You won't lose TWRP or unlocked bootloader, but I will try today by making backup of "cache" and flash it via my sdcard as soon as possible.
18) Does restoring a backup I made(when I had root access, unlocked BL, custom recovery, xposed) RETAIN all that? Meaning after I restore to that backup, I will still have all that.
Click to expand...
Click to collapse
Yup, it makes a backup of every little part of the system (if you include cache and dalvik, I don't, but some do).
Thanks for answering, I'm learning quite a bit. And yeah, I'll make sure to help others with this information too.
Click to expand...
Click to collapse
Okay, made a backup of "cache and the flashing went fine, my hypothesis is that you have to make the backup on the sdcard and not on the phone and move it to the sdcard.
RAZERZDAHACKER said:
You won't lose TWRP or unlocked bootloader, but I will try today by making backup of "cache" and flash it via my sdcard as soon as possible.
Click to expand...
Click to collapse
Actually, when you adb sideload, you need to flash stock fastboot and recovery .img files(at least for my phone), and the bootloader does in fact get locked again, along with losing root. I know cuz I already have done adb sideloading before. So, doesn't that make flashing backup via sd card and TWRP without sideload the only thing I can do? I'm just trying to keep a backup without losing root, unlocked BL, TWRP, even if I gotta give up some space... Just wanna make sure it's safe to do it like that.
RAZERZDAHACKER said:
Yup, it makes a backup of every little part of the system (if you include cache and dalvik, I don't, but some do).
Click to expand...
Click to collapse
I only have "System(1125 mb)", "Data(3480 mb)", and "Cache(0 mb)" listed in TWRP. My cache is 0 mb.... nothing to backup on there?
19) Do I have to unlink my linked apps before creating a Nandroid, or will creating one while linked allow me to retain the link even after wiping data and then restoring the Nandroid?
ShinraTensei04 said:
Actually, when you adb sideload, you need to flash stock fastboot and recovery .img files(at least for my phone), and the bootloader does in fact get locked again, along with losing root. I know cuz I already have done adb sideloading before. So, doesn't that make flashing backup via sd card and TWRP without sideload the only thing I can do? I'm just trying to keep a backup without losing root, unlocked BL, TWRP, even if I gotta give up some space... Just wanna make sure it's safe to do it like that.
Click to expand...
Click to collapse
You wont lose anything during a complete nandroid backup, and, apparently, some devices loose stuff during adb sideload.
I only have "System(1125 mb)", "Data(3480 mb)", and "Cache(0 mb)" listed in TWRP. My cache is 0 mb.... nothing to backup on there?
Click to expand...
Click to collapse
Nothing....... Yet.
19) Do I have to unlink my linked apps before creating a Nandroid, or will creating one while linked allow me to retain the link even after wiping data and then restoring the Nandroid?
Click to expand...
Click to collapse
Unlink? What do you mean? (Not quoting Justin Bieber)
RAZERZDAHACKER said:
Unlink? What do you mean? (Not quoting Justin Bieber)
Click to expand...
Click to collapse
There's this thing you can do where you move your apps from internal storage to sd card COMPLETElY, thereby saving a lot of space on internal memory. It works because a 'link' is created between the app+data(now in sd) back to it's internal location counterpart(where it would have been otherwise). This way, the apps and system think your apps are in internal, but in fact are in sd(you can see that more internal is free by checking space used up via any file manager though).
In order to do this, a second partition on the sd card is to be made with an ext2/ext4 format, and use a linking app( like Apps2sd).
ShinraTensei04 said:
There's this thing you can do where you move your apps from internal storage to sd card COMPLETElY, thereby saving a lot of space on internal memory. It works because a 'link' is created between the app+data(now in sd) back to it's internal location counterpart(where it would have been otherwise). This way, the apps and system think your apps are in internal, but in fact are in sd(you can see that more internal is free by checking space used up via any file manager though).
In order to do this, a second partition on the sd card is to be made with an ext2/ext4 format, and use a linking app( like Apps2sd).
Click to expand...
Click to collapse
Yea I've used one of those, I first thought the app used the "MV" Unix command but yea you need a sec. Partition to do that on the sdcard, but you don't have to do that on your nandroid backup.
RAZERZDAHACKER said:
Yea I've used one of those, I first thought the app used the "MV" Unix command but yea you need a sec. Partition to do that on the sdcard, but you don't have to do that on your nandroid backup.
Click to expand...
Click to collapse
So can I backup linked apps with their links' data saved, so when I install the linking app again, they can be relinked automatically?
Sent from my ASUS_T00J using XDA-Developers mobile app
Thanks for those questions and answers. I posted this before but appearantly in the wrong place. It seems to be quite right here. Thanks to helping people!
Hi XDA experts
I am newly registered in the forum, but experienced in modding (more or less). But I am (for now) strictly a user, not developer.
So far I got along very well, with my beloved Galaxy S4 jfltexx. I got from stock to rooted stock, from there to cm, instantly back to stock, used it for a long time and am just now on cm13 nightly, which is truly awesome!
It is so awesome that I would really like to help other people out, even if they have no idea about this. Meaning I wish to modify other peoples phones for them. However, when it comes to other peoples property I can't really fight my way through technical terms I don't understand anymore, hoping that the outcome will be as I wished. I pretty much know what most of all these technical terms mean, but I don't always understand how they are related to each other. I know, explaining this will take a while, but I would REALLY appreciate it if someone would take the time...
1) The bootloader, can it be replaced? What would be the purpose of that? UNLOCKING does not mean REPLACING, does it??
What do custom ROMs typically consist of? An entire working system? Parts of a working system? Sometimes this sometimes that?
I'm asking the question because I got the impression that some custom ROMs require the user to have a certain (usually stock) ROM in order to flash it. For example, if I had a Galaxy S6 edge running 5.1.1, could I upgrade to noble ROM Marshmallow?
I also have the feeling that the ROM or system or whatever is somewhat seperate from the kernel. What is this relation? Do custom ROMs not always come with a compatible kernel? Is there only one kernel compatible to the rest of the system, or is there a chance to run a system with a kernel not particularly designed for it? How to get a 'wrong' kernel?
Where to get stock ROMs and who provides them? If I wanted to upgrade from Lollipop to Marshmallow, but am rooted and don't get OTA updates, what do I do? Assuming that Nandroids are bound to a single device (e.g. MY phone) who can provide a stock ROM that runs on my device and how does he get it?
Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Is there ANY phone SOLD with open bootloader and root? A phone that actually wants its users to play with the system?
Thanks guys
NoBullsh1t said:
Thanks for those questions and answers. I posted this before but appearantly in the wrong place. It seems to be quite right here. Thanks to helping people!
Click to expand...
Click to collapse
It happnes alot that people post in wrong section
Hi XDA experts
I am newly registered in the forum, but experienced in modding (more or less). But I am (for now) strictly a user, not developer.
So far I got along very well, with my beloved Galaxy S4 jfltexx. I got from stock to rooted stock, from there to cm, instantly back to stock, used it for a long time and am just now on cm13 nightly, which is truly awesome!
Click to expand...
Click to collapse
Yup, kinda same, excpet im ks01lte but I moved from stock to rooted stock (5.1.1) then cm13, then stock + xposed 4.4.2 then cm11 and now back to cm13 nightly
It is so awesome that I would really like to help other people out, even if they have no idea about this. Meaning I wish to modify other peoples phones for them. However, when it comes to other peoples property I can't really fight my way through technical terms I don't understand anymore, hoping that the outcome will be as I wished. I pretty much know what most of all these technical terms mean, but I don't always understand how they are related to each other. I know, explaining this will take a while, but I would REALLY appreciate it if someone would take the time...
Click to expand...
Click to collapse
1) The bootloader, can it be replaced? What would be the purpose of that? UNLOCKING does not mean REPLACING, does it??
Click to expand...
Click to collapse
The bootloader can be replace, however, if you fail here, there is no comming back (you'll need a complete board replacement because the bootloader acts as a BIOS), the purpose of replacing it is various reasons, change of splash screen during boot etc. Some bootloaders are locked to only be able to flash certain ROMs (OEMs do this to not allow people to tinker with their devices) but it is nearly always un-lockable (except for some devices, I own an Acer tablet that has a locked bootloader that cant be un-locked) and no, unlocking it does not mean changing it.
What do custom ROMs typically consist of? An entire working system? Parts of a working system? Sometimes this sometimes that?
Click to expand...
Click to collapse
Yea, sometimes this sometimes that, in example, ported marshamllow touchwiz ROMs rely on some files in the stock ROM so the "update" doesn't take up much space.
I'm asking the question because I got the impression that some custom ROMs require the user to have a certain (usually stock) ROM in order to flash it. For example, if I had a Galaxy S6 edge running 5.1.1, could I upgrade to noble ROM Marshmallow?
Click to expand...
Click to collapse
That is because of the bootloader (again lol), from my experience with the s4, before flashing cm13, I had to go to 5.1.1 because of the bootloader was changed during the OTA, so as stated before, it only allowed a certain type of ROMs to be flashed.
I also have the feeling that the ROM or system or whatever is somewhat seperate from the kernel. What is this relation? Do custom ROMs not always come with a compatible kernel? Is there only one kernel compatible to the rest of the system, or is there a chance to run a system with a kernel not particularly designed for it? How to get a 'wrong' kernel?
Click to expand...
Click to collapse
The kernel tells the system what to do, some kernels are specified for battery optimization, so the kernel tells the cpu to slow down and save juice, while some other kernels offer the ability to overclock the device (mostly used on older devices to make it faster, but it drains more juice and can result into app crashing), the kernel, is not separated from the system, in fact, you can't even compile a ROM without a kernel. There is not only one kernel for lets say cm, you can flash another kernel, just make sure it is compatible with your android version. To get a wrong kernel, flash one that isn't for your device or android version.
Where to get stock ROMs and who provides them? If I wanted to upgrade from Lollipop to Marshmallow, but am rooted and don't get OTA updates, what do I do? Assuming that Nandroids are bound to a single device (e.g. MY phone) who can provide a stock ROM that runs on my device and how does he get it?
Click to expand...
Click to collapse
Your OEM provides them, samsung has a website called sammobile and uploads all the stock ROMs there. If you want to upgrade, just flash it via recovery or in your case, odin (for samsung phones). To give your backup to someone else, the other person must have the exact same phones, in example, you (jfltexx) can't give it to me (ks01lte), I must have jfltexx and then (assuming you did the backup on twrp) I'd have to change the serial number to my device.
Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Click to expand...
Click to collapse
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features.
Is there ANY phone SOLD with open bootloader and root? A phone that actually wants its users to play with the system?
Thanks guys
Click to expand...
Click to collapse
There are a few devices like that, one plus was a company that wanted to do that, it came with root, unlocked bootloader and cyanogenmod running, they separated unfortunatly and evolved to using "oxygen os" and does nor provide a un-locked bootloader but provides a simple tool to root and unlock. I don't know any companies that have unlocket bootloaders because they don't want the average consumer to mess up their device and blame it on the OEM.
"Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features."
I mean is there like a website from google where I can dowoad a non device specific aosp and flash that to my S4 to make it run? Wouldn't there be for example drivers missing? Isn't that what I have to be greateful to Cyanogenmod for, making up to date android compatible with older devices?
---------- Post added at 07:49 PM ---------- Previous post was at 07:42 PM ----------
So I can actually make a jfltexx Nandroid and install it on another jfltexx by easily changing the serial number???
NoBullsh1t said:
"Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features."
I mean is there like a website from google where I can dowoad a non device specific aosp and flash that to my S4 to make it run? Wouldn't there be for example drivers missing? Isn't that what I have to be greateful to Cyanogenmod for, making up to date android compatible with older devices?
Click to expand...
Click to collapse
Yes, be greatful, it is free, open source and full of active devs and memebers. I'm still not sure what you mean, do you mean on-screen navigation bar? Because you can change that in cyanogenmod settings.
---------- Post added at 07:49 PM ---------- Previous post was at 07:42 PM ----------
So I can actually make a jfltexx Nandroid and install it on another jfltexx by easily changing the serial number???
Click to expand...
Click to collapse
Yea, you know how your backup is located in /sdcard/TWRP/BACKUPS/SERIALNO? The device you want to flash it to should make a backup of the tiniest partition (usually cache, it's 5mb) and youll get acces to the serial number, then you just swap it and delete the tiniest partition.