What are the most common troubles one can run into when installing cutom roms, rooting etc.
How to solve them!
And how to AVOID them!
Firstly, flash a custom Recovery. Nothing much can be done before this.
TWRP is a good choice. It has an Auto Root feature. Alternatively, you can flash SuperSU through TWRP to gain root access.
Nothing can possibly go wrong till this step.
Next, take a nandroid backup of your phone.
Anytime you run into any major errors, you can restore this backup to get back a working state. Take regular backups to avoid having to restore very old ones.
neomanu said:
Firstly, flash a custom Recovery. Nothing much can be done before this.
TWRP is a good choice. It has an Auto Root feature. Alternatively, you can flash SuperSU through TWRP to gain root access.
Nothing can possibly go wrong till this step.
Next, take a nandroid backup of your phone.
Anytime you run into any major errors, you can restore this backup to get back a working state. Take regular backups to avoid having to restore very old ones.
Click to expand...
Click to collapse
Hey...which recovery is better in terms of features & usability...CWM or TWRP...i think most of the features are the same right?
Personally, i would recommend TWRP. It has a very convenient touch-based interface, as opposed to the traditional CWM. Although, there is a touch-based CWM also available.
how to install twrp recovery on A116
leo.riv said:
how to install twrp recovery on A116
Click to expand...
Click to collapse
TWRP tutorial : [PORT] TWRP 2.5.0.0 For Micromax A116 Touch Recovery + Auto Root
Related
1. How to install nandroid backup?
2. Can i install it in my phone xperia min st15i rooted ics .587 (locked BL)?
3. where can i download the latest official/working nandroid backup for my xperia min st15i?
4. If Im installing custom ROM's and failed, and having boot loop problems.. Can i use nandroid backup to restore where I saved? that means from all files settings? will be back to what state you saved?
5. And If I successfuly installed and boot new ROM, then after many restart/reboot or after tomorrow, can I still use nandroid backup to restore to its previes ROM/OS? without having any problem? Is that how nandroid backup work?
Please answer THANKS!
1.)Nandroid backup is Total Disk Image(think dd command) of the partitions of a phone .This may or may not include ,/system,/data,/cache,/sd-ext,android-secure,kernel and recovery depending on the recovery and phone ...
2-3.)Nandroid Backup is created by the user and should not be shared amongst each other for security and privacy reasons ...So basically they are hard to find and probably it's not a good idea to flash one to your phone...
4-5.)Basically you create the Nandroid backup of your phone from the recovery ...Then you can install a custom ROM ...If you have a problem then you can restore the original backup
So there is no "install" as such of a nandroid backup ....It's Backup from your phone via recovery and restore to your phone via recovery ....
A point to ponder is that the recovery for the Locked BL lies in /system ...If the Custom ROM doesnt flash the recovery to /system properly then in case of a boot loop ,you have to go for Downgrade-Upgrade Root-Recovery-Backup cycle ...
This is relevant to you...
Fastboot, Custom ROMS & ClockworkMod Recovery:
A custom ROM is a fully standalone version of the OS, including the kernel (which makes everything run), apps, services, etc - everything you need to operate the device, except it's customized by someone in some way.
So what does the "customized" part mean? Since Android is open source, developers are free to take stock ROMs, modify them, strip them of garbage, optimize them, add things, and pretty much do whatever their imagination and skills allow.
Click to expand...
Click to collapse
- Custom ROMS for Android Explained And Why You Want Them
In the Development Section you will find a variety of Custom ROMs, some require you to have an an Un-Locked Bootloader and some don't, it's usually stated in the thread title if it's required or not but modding your Phone with an unlocked Bootloader is much simpler. Most ROMs usually come in .zip format which require ClockworkMod (CWM) to install them.
You can find a great Guide HERE that will show you how to use Fastboot which is the method used for installing Kernels required by certain Custom ROMS.
Got a Mac? - [GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!)
ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device
Click to expand...
Click to collapse
- What Is ClockworkMod Recovery And How To Use It On Android
To use CWM on an XPERIA then it's recommended to unlock your Bootloader because then you can simply flash Custom Kernels that come with CWM pre-installed, it's also safer imo because it's separate from the system, but if you haven't unlocked your Bootloader for whatever reason then you're going to have to use [APP]/[RECOVERY]x-Parts [CWM Installer] [Version 7.0] 29/6/12 which is installed to the Phone's system, although it's less effective should you accidentally wipe your system while trying to flash a new ROM as you won't be able to access it.
Click to expand...
Click to collapse
...
Some background info: I got my phone used, so the rooting and stuff was done for me.
When I got the phone, the top of the recovery said Semaphore CWM 6.something, I don't know what I did to it but now the recovery says CWM based recovery. I also notice that fix permissions is not there anymore, there is probably more things missing that I never noticed. My question is, How do I get back to the original Clockworkmod?
Also, does anyone want to give me the basics on flashing stuff? I see people talking about Titanium Backup and ROM Manager. Every time I want to make a backup I just go into the recovery and make a backup there. What's ROM Manager? What's the best way to do this kind of stuff?
EDIT: I just booted back into recovery since a while (when I flashed my current rom) and noticed that it's back to normal. It says Semaphore CWM Recovery 6.0.3.8, when it used to say CWM-based recovery 6.0.3.6. Back then, it also gave me a warning called Warning: no file_contexts. That's gone now, should I have anything to worry about?
oneupe1even said:
Some background info: I got my phone used, so the rooting and stuff was done for me.
When I got the phone, the top of the recovery said Semaphore CWM 6.something, I don't know what I did to it but now the recovery says CWM based recovery. I also notice that fix permissions is not there anymore, there is probably more things missing that I never noticed. My question is, How do I get back to the original Clockworkmod?
Also, does anyone want to give me the basics on flashing stuff? I see people talking about Titanium Backup and ROM Manager. Every time I want to make a backup I just go into the recovery and make a backup there. What's ROM Manager? What's the best way to do this kind of stuff?
EDIT: I just booted back into recovery since a while (when I flashed my current rom) and noticed that it's back to normal. It says Semaphore CWM Recovery 6.0.3.8, when it used to say CWM-based recovery 6.0.3.6. Back then, it also gave me a warning called Warning: no file_contexts. That's gone now, should I have anything to worry about?
Click to expand...
Click to collapse
Usually your ROM comes pre-packaged with a version of recovery.
ROMs that use the Semaphore kernel also generally come pre-packaged with a modified version of Clockworkmod recovery designed to compliment the kernel.
for reference:
if your recovery says: CWM recovery X.X.X.X then its usually the official version
Semaphore CWM Recovery 6.0.3.8 is a modified version for use with Semaphore kernel
CWM-based recovery 6.0.3.6 - is a modified version likely for use with another kernel (They dont always specify)
I would recommend just sticking with whatever version comes with your ROM.
there is rarely a need to change it.
ROM manager is an App that makes flashing clockworkmod recovery easy as well as downloading and flashing ROMs.
but for the most part if you know how to use recovery already your probably better off doing stuff manually in my opinion.
Titanium backup - is an app that lets you back up and restore all of your installed apps and data.
so for instance if you wanted to install a new ROM. you could back your apps and data up with Titanium backup and then install your new ROM and even wipe user data and still be able to get all of your apps back just as they were before you switched ROMs.
in comparison a nandroid backup (the backup done through recovery) backs up everything including your current ROM so restoring from that would also restore whatever ROM you were using when you made the backup.
as an example if you do both a Nandroid and Titanium backup while running android 2.3
then you decide to update to android 4.1
after the update if you restore from the nandroid backup you will be back at android 2.3 with all of your apps and everything back the way it was.
if you restore from a titanium backup you'll still be on android 4.1 but you'll have all your apps back as they were before.
I successfully flashed the new Cyanogenmod 12 5.0 ROM via Philz (first time using Philz btw) and I couldnt back up anything because I lost root and cannot get access to Titanium Backup or Quick Boot to get back into my custom recovery. I tried getting back to Philz via hardware buttons but it takes me to the default recovery instead... I really want to go back to 4.4.4 KK but idk how to get back without having any root or custom recovery access... Someone please help!
BaylorBear2014 said:
I successfully flashed the new Cyanogenmod 12 5.0 ROM via Philz (first time using Philz btw) and I couldnt back up anything because I lost root and cannot get access to Titanium Backup or Quick Boot to get back into my custom recovery. I tried getting back to Philz via hardware buttons but it takes me to the default recovery instead... I really want to go back to 4.4.4 KK but idk how to get back without having any root or custom recovery access... Someone please help!
Click to expand...
Click to collapse
When you go into Recovery via the Hardware button combo, it will take you back to default recovery, if you click through it . it will then load your installed (Philz) recovery, that is being you did properly install Philz correctly. You can then flash the Nandroid back up you made before installing another rom... you did make a Nandroid? If not you have a lot of reading to do.
Addon: The link below is something you should know forward and backwards before ever flashing anything. Good Luck.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
So just so I'm 100% clear.. after I KDZ method back to 10B from 11C and obtain root with Stump and grab SuperSu... I can then use flashify to flash Philz.. then Use Philz.. instead of TWRP to Flash CM12... right?
Hi guys
Apologies if this has been posted in the wrong section.
I have recently inherited a Galaxy S2 (GT-I9100) running the CyanogenMod 12.1, Android Version 5.1.1
I have spent the last two day trying to and failing miserably to install Xposed Installer V3.0 Alpha 2, I have searched Google and read through numerous forums on how to resolve this, but the more I read the more confusing it becomes. I would really appreciate any help/assistance in helping me fix the problem, so that I can run the app without any issues. When I access the app's log it states:
data/data/de.robv,android,xposed.installer/log/error.logpen failed. ENOENT (No such file or directory)
Also, when I try to run Titanium Backup 6.1.0, I get an error stating:
Sorry, I could not acquire root privileges. This application will *not* work! Please very that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command.
I have gone into Developer Options and set Root Access to Apps and ADB.
As I new to Android my understanding (please correct me if I am wrong) that the CyanogenMod 12.1 was actually a ROM and therefore Titanium Backup should work. FYI SD Maid not working.
Any help on both of these issues would be most appreciate, please bear in mind I am a noob where Android and Galaxy S2 are concerned.
Thanks in advance.
The forum for the i9100 is located here, but because it's so close to the i777 we can probably help a bit.
Sounds to me like your phone isn't rooted, as none of the apps you mention will work without root privileges. Install the latest SuperSU; you should be getting access prompts if you're correctly rooted.
If you are not prompted for root access when opening apps such as Titanium Backup, you'll need to install Framaroot and use the Aragorn exploit in order to easily root your device. Let us know if either of these work for you.
Hi Steve
Thanks for the reply.
I should have mentioned that I already have Super SU installed and for certain apps it does ask me to grant access. If open Super SU it displays the following apps:
Titanium Backup
Root Explorer
pops1368 said:
Hi Steve
Thanks for the reply.
I should have mentioned that I already have Super SU installed and for certain apps it does ask me to grant access. If open Super SU it displays the following apps:
Titanium Backup
Root Explorer
Click to expand...
Click to collapse
Strange. In that case have you tried doing a complete wipe in recovery, then reinstalling the ROM? In your case you would boot into recovery, wipe /system and dalvik cache, then install ROM and gapps. Just make absolutely certain you're running a custom recovery before doing this, such as CWM (ClockworkMOD) or TWRP (TeamWin), or you could damage your device if you're on stock recovery. And, of course, make sure you have the ROM/gapps already on your device before wiping everything!
Because you inherited the device the best method would normally be to flash back to stock and start all over - if for nothing else it's a good learning experience. Hope this helps.
Hi Steve
Thanks for the reply and your advice/information, very informativinformativ.
I was trying to avoid a complete wipe and reinstalling the ROM again, as Android is new to me and I don't want to mess up the installation and wreck the phone, even it was free. However, I think I have no choice and will have to bite the bullet and do it.
Thanks once again.
pops1368 said:
Hi Steve
Thanks for the reply and your advice/information, very informativinformativ.
I was trying to avoid a complete wipe and reinstalling the ROM again, as Android is new to me and I don't want to mess up the installation and wreck the phone, even it was free. However, I think I have no choice and will have to bite the bullet and do it.
Thanks once again.
Click to expand...
Click to collapse
As long as you have a custom recovery there's very little that can go wrong with a full wipe. I would suggest booting into recovery first (power button + both volume keys, then release at the Samsung logo) and make sure you're running either CWM or TWRP. While in recovery do a backup first, as a "just in case". You can always restore your device fully from a backup.
The next thing to remember is to make sure your ROM/gapps are compatible with one another. For instance, if you're installing a CM12 (Android 5.0+) ROM make sure your gapps are also 5.0+.
Best of luck!
When I attempt to go into Recovery Mode it does so, but opens a CyanogenMod screeb, it dies not show any options to backup/restore, it foes however have the complete wipe option. When I run ROM Manager I have done the following Recovery Setup, which now shows Recovery Already Installed:
ClockworkMod Recovery
TWRP
But I don't understand what I'm doing wrong, for neither option to be available in Recovery Mode?
pops1368 said:
When I attempt to go into Recovery Mode it does so, but opens a CyanogenMod screeb, it dies not show any options to backup/restore, it foes however have the complete wipe option. When I run ROM Manager I have done the following Recovery Setup, which now shows Recovery Already Installed:
ClockworkMod Recovery
TWRP
But I don't understand what I'm doing wrong, for neither option to be available in Recovery Mode?
Click to expand...
Click to collapse
Best option for you is to go to the i9100 forum and download a kernel for your phone that is compatible with the OS version you want to install (CM12, which is 5.1. in your case). With your device (as well as our i777), the kernel and recovery are fused together, so you cannot use ROM Manager to install a recovery to a separate partition.
Once you have an i9100 5.1 kernel downloaded on your phone you can flash it through the current recovery you have, then immediately reboot back into recovery. You'll then have the correct recovery and can proceed as normal with the ROM installation.
CWM absolutely has a backup/restore option, but it's hidden in a sub menu. My personal recommendation is to use TWRP recovery, as it's still being developed and is more robust/user friendly.
So as a general rule stay away from ROM Manager for system specific changes.
Thank you so much for the information/advice, I really do appreciate all of it.
Hi guys. I've been using custom ROMs for a few years now and I always used TWRP.
But lately, my banking app and some other important apps simply won't work because of my custom recovery.
Having that said, can I keep my LineageOS AND flash via Odin JUST the stock recovery to "bypass" the security these apps need? I'm using Magisk and I'm hiding root access from these apps.
What would happen if I flash the stock?
Thanks in advance!
This sounds like a device specific issue, as I use TWRP and LOS on my V20 with no issues. I'd say the banking apps aren't working because you are rooted which means MagiskHide might not be working properly.
This can also happen if you fail the SafetyNet test in Magisk depending on certain apps.
I'm not aware of a way for you to use a custom ROM with a stock recovery. It may be possible but hasn't been as far as I've seen.
I recommend asking this question in the proper Q/A section for your device (which I assume is a Samsung since you mentioned ODIN) to see if other users of that device can help you. Then, report this thread to have it closed/deleted once you have done so.
Also: Backing up with Titanium Backup isn't enough, in almost any case. Do a FULL backup from TWRP of your device, store it somewhere else like an SD card or PC and then mess around.
Redline said:
This sounds like a device specific issue, as I use TWRP and LOS on my V20 with no issues. I'd say the banking apps aren't working because you are rooted which means MagiskHide might not be working properly.
This can also happen if you fail the SafetyNet test in Magisk depending on certain apps.
I'm not aware of a way for you to use a custom ROM with a stock recovery. It may be possible but hasn't been as far as I've seen.
I recommend asking this question in the proper Q/A section for your device (which I assume is a Samsung since you mentioned ODIN) to see if other users of that device can help you. Then, report this thread to have it closed/deleted once you have done so.
Also: Backing up with Titanium Backup isn't enough, in almost any case. Do a FULL backup from TWRP of your device, store it somewhere else like an SD card or PC and then mess around.
Click to expand...
Click to collapse
Thanks for that. I wiped the whole thing and installed a stock ROM. Will only root now and see where it goes.
Titanium backup crashes on this phone (yes, it's a Samsung J7 Prime) if I use Magisk anyway.
I trusted my Google syncing and I kinda got a lot of backups back from the cloud. Not perfect, but acceptable.
yea you can use it
Following is the procedure :
A Nandroid Backup
The quickest way to revert your phone back to its stock ROM is to restore your Nandroid backup. Assuming you have an up-to-date one available it shouldn’t result in much — or any — data loss.
A Nandroid backup creates a complete snapshot of your phone: the operating system, apps, data, and everything else. Restoring it, therefore, restores the ROM you were using at the time. If you have a backup you took when using the stock ROM, then you’re set.
How to Restore a Nandroid Backup
Boot your phone into your custom recovery. We recommend TWRP.
Select Restore. You’ll see a list of all the available backups.
Pick a backup made using the stock ROM.
Select the partitions you want to restore. Normally this means you should check all the boxes.
Finally, swipe the bar labelled Swipe to Restore. It takes a few minutes to complete, then you can reboot.
Flash a Stock ROM
If restoring a Nandroid backup isn’t a viable option, then the next best bet is to flash a stock ROM. This comes with the added inconvenience that you will probably need to perform a factory reset along the way
There are benefits, too. You might be able to find a version of the ROM that is pre-rooted. Flashing ROMs is also really easy to do.
How to Flash a Stock ROM
Find a stock ROM for your phone. Go to forum.xda-developers.com and locate the forum for your device. Stock ROMs are often found in stickied posts at the top of the development boards.
Download the ROM to your phone.
Backup all your data.
Boot into recovery.
Select Wipe to reset your phone. This is optional (if you don’t want to bother with backing up and restoring), but you may encounter bugs or even get stuck in a bootloop if you don’t do it. Swipe the bar to begin the wipe.
From the recovery home screen, select Install and navigate your way to the stock ROM you downloaded.
Swipe the bar to begin installation. You can reboot your phone when it’s finished.
Flash a Factory Image
The ultimate method for getting your phone back to stock is to flash a factory image. This reverts your phone almost to the state it was in when you first unboxed it. All you need to do afterwards is lock the bootloader, and your device will be completely factory fresh.
How to Flash a Factory Image
The procedure to flash a factory image can differ from one device to another. In the case of a Pixel, the steps are simple:
Download and setup the ADB and Fastboot tools.
Download the factory image from the Android website. Unzip the download on your desktop.
Connect your phone via USB and boot into Fastboot mode.
Launch the command line or terminal app.
At the command prompt run flash-all.bat on Windows, or flash-all.sh on Mac or Linux.
Wait for it to finish, then reboot.