Database Info

[guide]for noobs!!(includes everything to make you not a damn noob anymore):)

Your a noob and need help then dont worry this guide will help you
ALWAYS UPDATING(STILL NOT COMPLETE)
Android Dictionary
If you're new to Android, you are likely seeing a lot of unfamiliar words being thrown about... from CID to RUU to ROM. This dictionary will help you understand what these words actually mean, and when you would expect to see them.
ADB
ADB (Android Debug Bridge) is a PC command-line tool included with the Google Android SDK. ADB provides an interface for managing and debugging a USB connected Android device. Common ADB tasks include: *Collecting a log via logcat* Installing APK packages* Pushing or pulling files* Accessing the device shell.
For additional details about ADB please see the ADB guide.
APK
An APK is an Android application package (Android Package). It is commonly used to store an app, or program run on the device. These files are essentially zip files, in that they contain other files which make up the program. They can be obtained through various methods, such as installing an app through the market, downloading from a website, or creating yourself in Java. If you have an apk file on your computer, and wish to install it on your phone, you can run the command 'adb install apkname.apk' to copy the file over USB to your phone.
The APK files reside on the phone in the directory /data/app/filename.apk. This directory is not normally accessible unless a #root|rooted ROM is used on the phone, in order to protect paid-for applications. On a rooted ROM, it is possible to copy applications manually into this folder using the command 'adb push' or similar. Once a file is in the /data/app directory, it is installed on the phone. There is not normally an installation process for apps on Android.
It is also possible to install an app to the system partition of a rooted phone. This has the added benefit that the application cannot be uninstalled from the device, making it useful for security/anti-theft applications such as WaveSecure and MobileDefense. These [[#system]] applications are stored in /system/app. The applications in this folder are normally part of the Android operating system, and should not be modified or deleted unless you either put the file there yourself, or know what you are doing.
APK files can be uninstalled using the market application (if the application was installed from the market), the 'adb uninstall apkname.apk' command, the Settings | Applications | Manage Applications menu, or by manually removing the files from the /data/app directory as a last resort. Normally, the preferred method is through the market or applications menu.
Bart
Bart is used from Recovery to backup your phone or to restore a backup.This basically creates an exact copy of your phone (Sdcard + Sd-Ext excluded, unless it says it will backup SD-Ext), which later can be restored with no losses in data.
Boot
In contrast to other linux-based operating systems, Android has a boot partition (containing the contents of a boot.img file), as opposed to a direct booting system. This partition contains a read-only 'ramdisk', and a couple of other files. The ramdisk contains files critical to booting, such as init.rc and default.prop. This 'partition' actually sets up the directory structure of the device, having empty folders for /data, /dev, /proc, /sbin, /sys and /system.
Bootloader
The bootloader, or HBOOT, is firmware on the phone which runs on every startup.
Since the bootloader controls access to Fastboot, it can be desirable to change the version of the bootloader on a phone. The current version of the bootloader can be viewed by entering bootloader mode. To do so, turn on the phone with the back button held down. Release the back button after about 1 second. The version information will be displayed at the top of the screen next to the word HBOOT, and will appear in the form 'V1.76.0004' or similar.
From within the bootloader, Fastboot can be used to execute an img file stored on your PC or flash an img file to the device.
If your device has HBOOT version 1.73.007, it is no longer possible to use Fastboot, so it is often desirable to downgrade the HBOOT using the Goldcard method in order to get the 1.73.004 version, which is Security-Off, allowing Fastboot.
CID
The Carrier ID is a number embedded in your Phone's SPL that identifies what if your phone is a network branded Hero. For example, T-Mobile UK phones have a different CID to generic HTC phones. The CID prevents you from [[#Flash|flashing]] an 'incorrect' [[#RUU]] to your phone. Note that the RUUs will all function on any of the phones, but the CID locking prevents you from 'debranding' your phone by installing a generic [[#RUU]]. Additionally, the CID-related software also prevents you from installing an older RUU than what you are currently running.
It is possible to bypass the CID check on an [[#RUU]] using a [[#Goldcard]]. This pretends your phone has the 'Super-CID', which allows any branding of ROM to be installed, and allows you to downgrade the software on your phone.
Data
The data partition on the device contains the user-related data, such as installed applications and settings for those apps, as well as your SQLite database containing Android settings and messages. Normally, the directory /data/app is off-limits through the 'adb shell' command, as well as other terminal applications that can run on the device, since this directory contains the apk files for apps. On a rooted phone, using the [[#su]] command will allow full access to this partition. This partition can be flashed using Fastboot or Nandroid.
Ext
Ext is an abbreviation of the extended filesystem, one of the filesystems supported by Android and other Linux based systems. An ext filesystem partition is required for using Apps2SD or Dalvik2sd.
Fastboot
Fastboot is a means to execute or Flash an img file on your device. First, set up your PC for ADB, and ensure that it works correctly. After putting your phone into Bootloader mode, and selecting Fastboot by pressing back (if you let go of the back key early), the device awaits a command via USB.
On your computer, execute the command 'fastboot devices', which should display your device serial number. This confirms you are ready to use Fastboot. To execute (ie. run without changing your system) and img file, type the command 'fastboot boot imagename.img'. This command allows you to run a custom recovery image without flashing it to the device.
If you wish to flash an img file to the device, the command 'fastboot flash IMGTYPE imgtype.img' should be used. Note that IMGTYPE should be replaced by the type of img file you are flashing. For example, to flash a recovery image, the command 'fastboot flash recovery patched_recovery.img' should be used. The following are valid types of image to flash; boot, recovery, system,
Flash
Flashing is the process of writing data to the internal memory on your phone. Normally, you would flash a [[#ROM]] image to the phone, which would give you a different version of system software on your phone. Flashing can also refer to updating/writing to any of the other parts of the phone, such as the SPL, Radio etc.
Flash Memory
Flash memory, also known as NAND memory, is nonvolatile - keeping information even when the device is off. Flash memory in the device is equivalent to the hard drive in a computer. This is where the device's operating system (sometimes called firmware) and applications are stored. Flash memory is slower than RAM, but is (almost always) faster than SD cards.
Flashrec
Flashrec is an application/tool you use to flash the recovery image to your phone. (Found on http://zenthought.org/content/project/flashrec)All current firmwares are patched so you can not use flashrec on these, you will receive the error message "Could not run command"Most 1.5 (cupcake) firmwares can still use this, but some has been patched already.The current version is 1.1.3 and was updated 2009-08-16.Note: Do not flash cyanogen's theme templates after you have started the installed recovery image, this will brick your phone!
Goldcard
A goldcard is the name given to a specially modified microSD memory card for your phone that allows you to install software to your phone that is in an RUU file, but not from the same network provider as your phone is from. It does this by bypassing the CID check of the RUU update. Additionally, the goldcard allows you to install an earlier version of system software onto your phone than what is already on it (called downgrading). This can make it easier to root a phone and install a custom ROM on it, if the software installed on it at present cannot easily be rooted.
HBOOT
See Bootloader.
logcat
Using adb (see ADB), type in "adb logcat >logcat.txt". This will help us when resolving issues and bugs.There is also a tool in the market you can use for this, called aLogcat. It can show different categories (severity of errors ect.) too, adb logcat can not do this.
Market
The market on Android is a place where you can purchase or download applications for your phone in the [[#APK]] format. When you download through the market, the installation process is transparent (as in you don't have to deal with the APK files yourself), and there is the facility to rate apps and post comments which are visible to other users. Frequently, the developers of apps actually take onboard the feedback in the comments (mainly the smaller apps with slightly less feedback to sift through).
When an app is installed from the market, it is copied to '/data/app/apkname.apk', as the act of 'installing'. An app can store its data in the folder '/data/data/apkname'. It is possible to clear the data stored by an application by using the Manage Applications feature in Settings | Applications | Manage Applications.
Nand
See Flash Memory.
Nandroid
Nandroid is used to backup or restore backups from Recovery.You can chose to either do a regular backup (Phone only) or a backup + sd-ext (Phone + Apps2sd ext.)Both will backup your whole system, the second will include apps saved on your sdcard's sd-ext.
Radio
The Radio on a Hero is the part of the phone that deals with mobile connections. It handles talking to the GSM/3G network, Bluetooth, WiFi and GPS. The radio contains software that controls how it operates, and newer versions of radio firmware are made available from time to time in [[#RUU]] updates. These updates are transparent to the user, although users who elect to install custom software can update their radio using an update.zip file made available by members of the modding community.
Flashing the radio is potentially risky, and you should NEVER pull the battery out of a phone that is [[#Flash|flashing]] the radio. If you do so, it is possible your phone will be bricked. Nevertheless, it can give improved battery life, signal strength and data performance, so is often done by users moving to later versions of ROMs.
Care should be taken to only flash the correct type of radio to a phone. NEVER attempt to flash a CDMA phone with a GSM radio or vice-versa. It is likely you will brick the phone if you attempt to do so.
ROM
ROM is literally "read-only memory" but it's usage has changed over time. Today ROM can refer to the non-volatile area of a device's flash memory on which read-only data resides or the packed image to be written to that flash area.
Root
Root is the name of the highest level superuser (su) on Unix-like systems such as Android. The root user, and applications run by the root user, have administrative access to protected files and services which makes it dangerous for normal daily use.
A 'rooted' device one which has been hacked to provide privilege escalation from a standard user to superuser. Rooting a device is usually the first step in installing cooked ROMs.
RUU
An RUU is a ROM Upgrade Utility, which is a Windows executable (exe) file that upgrades the software on your phone. Using the USB connection with the phone, the RUU communicates with the phone's SPL, checking the CID of the device to ensure the user is not installing the ROM on a network branded device (since the networks release their own RRUs with customisations and branding). The RUU is capable of flashing almost everything on the phone, including System, Data, Recovery, HBOOT and Boot. As such, an RUU is a good way to return your phone to the way it came out the box if a warranty repair is needed (be aware that using a new RUU could make it difficult, or even prevent you from rooting the phone in future. It is normally better to upgrade using update.zip files to prevent this, as they do not update the HBOOT to prevent Fastboot in future.
S-OFF/S-ON
This refers to an unlocked/locked NAND drive. HTC lock the NAND on some phones to prevent writing to the /system. S-OFF can generally be obtained by an exploit, by flashing an engineering SPL, or by using an XTC Clip.
SPL
The Secondary Program Loader is a piece of bootcode that initiates the startup of the phone, displaying the initial splashscreen for the device, and loading the initial files from ROM.
It checks to see if a button combination is pressed on bootup (such as that to enter Recovery Mode or the bootloader ), and loads the relevant system software. If no special instruction is given by holding keys, the bootloader loads the normal system software by initialising the boot process from the boot partition.
Flashing your SPL is risky, as the process failing will probably result in a broken, or bricked phone, since the SPL is executed very early on in the boot process, and any error here will prevent access to the recovery or bootloader features.
If you do flash the SPL though, it unlocks the Carrier-ID CID from the device, essentially allowing any RUU to be installed to the device, and allows flashing alternative or custom bootscreens.
Stock
The term stock is often used to refer to a file or part of the software which is unmodified or untouched by developers. For example, a stock ROM would be one which was produced by HTC and which had not been modified or rooted by someone. The term is often used when comparing performance of different ROMs, as a way to refer to the phone as it came out the box.
su
su (substitute user) is a Linux command which, when run without a username parameter, gives the user full 'root' permissions. By default, this command binary (ie. Linux equivalent of an executable file) is not included on Android systems, but the process of "rooting" a phone copies this file to the '/system/bin/' directory thereby enabling the command. Since root privileges can be abused by malicious applications it's highly recommended to install an app to grant and manage access to su, similar to UAC on Windows. VillainROM includes the app called "Superuser" for this.
System
The /system directory on your device is where the main operational software for the Android OS is stored. It has a number of sub-direcories of which /system/apps (where application apk's are stored) is probably the only one users would have need to access. The /system folder is read-only by default and needs remounted via 'adb' to allow write access.
Recovery
The recovery partition is a boot-mode for your phone that allows you to wipe your settings from the Data partition of the phone (a hard wipe), or perform an update using an update.zip file on the root of the microSD card. It is common (although not necessary) to flash a patched Recovery image, such as Amon RA's one. This allows you to run Nandroid backup from the device, and flash modifications, such as [[#update.zip]] files to the device, essentially becoming a means to install sotware to the device. Recovery mode is separate from 'normal' mode, and can be entered by holding down home whilst turning the phone on.
update.zip
An update.zip (does not have to actually be called update.zip if you have a patched Recovery image) is a file containing some files which will be copied to the phone's internal memory. Normally, a new system update or ROM is stored in the file, but update.zip files are commonly used to install modifications such as themes or applications that are installed on the System partition to prevent uninstallation.
To flash one of these files, which commonly would contain a custom ROM for your phone, you would boot your phone to a patched recovery image (whether using Fastboot, or the home+power method if you have a patched Recovery image flashed on your phone)
Update.zip files are cryptographically signed, and more information on how to sign your own files can be found online.
WWE
Stands for World Wide English version of the ROM. There can be local versions of ROMs too. For example VR10 is based on the Taiwan version, VR12 on the WWE one. Interestingly, WWE excludes the English (US) locale.
Now we are done with the definitions

HOW TO ROOT YOUR HTC One V PHONE
This guide may also work for rooting the HTC Wind / HTC Desire S (T328w). If you decide to try rooting your Wind / Desire V, make sure you first download the stock HTC RUU (ROM Update Utility) to recover if there are any issues.
Please note that unlocking your phone’s bootloader does involve the possibility of voiding your warranty, so be certain that you are willing to risk that to root your phone. Moreover, you proceed at your own risk. I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble.
You will need much patience and time, and you’ll need to know how to use SDK tools for Android (see below). If you are a total noob, I do not recommend this for your first project! If you try anyway and get confused with terminology, try looking here for answers: Terminology - CyanogenMod Wiki.
Quote:
Before you begin, make sure that your computer can properly recognize the phone:
You will need SDK tools for Android, Java runtime, and HTC Sync installed on your Windows computer. If you run Mac, I can’t help you. I avoid all that narcissistic iStuff like the plague.
1. You only need to install HTC Sync for the drivers that come with it. But the program sometimes causes conflicts, so during this procedure, make sure it is not running. Open Task Manager in Windows and kill it. If you don’t use HTC Sync, you may also open Control Panel and uninstall it without uninstalling the drivers.
2. With the phone on, connect the USB cable. Make sure the phone is connected in Charge only mode.
3. Enable USB debugging by going to Settings > Development > USB debugging.
1. Perform a full backup your phone’s data
Unlocking the bootloader will involve doing a factory reset. This will result in the loss of all accounts, emails, texts and apps installed on the device. However, data on the SD card such as music, photos and videos will be safe. The device will not format the SD card.
2. Update your software version
To update your software after rooting, you will have to go through hassle of re-flashing the stock recovery and re-locking the bootloader. The phone will lose root and you’ll have to go back through steps 3C-5F, so make sure you’ve updated first. To manually check if a software update is available, go to Settings > About > Software updates > Check now.
3. Unlock your bootloader at htcdev.com
The next step is to head over to htcdev.com and follow the procedure there to unlock your bootloader. This is the step that can void your warranty!
3A. Getting started
Create an account at htcdev.com and login. Click the Unlock Bootloader icon and Get Started button. On the next screen, drop down the “Select Your Device” list, choose All Other Supported Models and click the Begin Unlock Bootloader button. Then, fill out the two nasty forms telling HTC that it’s perfectly fine with you to possibly lose your warranty by going through with this process.
3B. Obtaining your unlock token
The first page of instructions shows you how to boot the phone into HBOOT, select FASTBOOT and connect the phone to your computer via USB. But the instructions are not right for the One V since it doesn’t have a removable battery. So here’s the replacement procedure:
Step 1 – No need to shut the phone down.
Step 2 – To enter HBOOT (or “bootloader mode”), the power button for longer than 10 seconds. As soon as the screen turns black, hold down volume and let off the power button. At the top of the screen you will see ***_LOCKED_***.
Step 3 – Use the volume rocker to select FASTBOOT if it’s not selected already. You may have to wait for the device to run through a routine check for zip files to update.
Step 4 – Connect the phone to your computer using the USB cable.
If you followed the directions above regarding SDK tools, Java Runtime and HTC Sync, you can skip page 2 of the instructions (steps 5-7) and move onto page 3.
In Step 8, you open a command prompt in Windows and navigate to the folder where you installed SDK Tools (it should be c:android-sdk-windows or c:Android) and type the command
Code:
fastboot oem get_identifier_token
Step 9 is where most people get hung up. Make sure that you do not select any spaces next to the identifier token, or any lines above or below the Identifier Token Start/End.
Paste the identifier token copied from the command window above into the box at the bottom of htcdev.com’s page 3 in your browser and click the Submit button. You will receive an email from htcdev.com with the subject “The key to unlocking your HTC Device” that has an attached file named “Unlock_code.bin” and a link to continue the unlock process. Download the attachment into the folder you installed Android SDK tools and click on the link to continue from page 4. You may have to log back in.
3C. Unlock the bootloader
For Step 12, go back to the command prompt and make sure you are in the folder where you installed Android SDK tools and downloaded the file “Unlock_code.bin” above. Now you will flash “Unlock_code.bin” to the phone using the following command:
Code:
fastboot flash unlocktoken Unlock_code.bin
You will see the following warning screen on the phone, again confirming that you are willing to waive your warranty rights to unlock the bootloader:
Use the volume rocker to select Yes (up one click) and press the power button once. The bootloader will proceed to erase all your data, unlock itself and reboot the phone.
After running through the setup wizard, go back into HBOOT (turn the phone off with the long press, hold down volume and press the power button) and confirm that you’ve unlocked your bootloader successfully. You should see ***_UNLOCKED_***. Success!
4. Install ClockworkMod Recovery
A custom recovery allows you to backup and restore ROMs including all user apps, data and cache to the SD card. It is also used to flash scripts, custom kernel and custom ROMs, which will come in handy at step 5 below where we root the phone.
1) There are two types of One V - the international GSM version (uses a sim card) and the U.S. Sprint/Virgin Mobile CDMA version (no sim card), and there are custom recoveries for both types that aren't interchangeable.
If your phone uses a sim card, download recovery-clockwork-5.8.4.5-primou.img from ClockworkMod's index of recoveries.
If you have a U.S. Cellular/Sprint/Virgin Mobile (U.S.) device that doesn't require a sim card, download cwmrecovery.img. Be sure to click the thanks button for Android Forums member jmz for his handy work.
As an alternate, PrimoC/CDMA users (no SIM) can download and install jmz's TWRP2 Recovery. See the directions in his thread: [VM/PRIMOC][RECOVERY] TWRP2 Recovery 7-10-2012
2) Reboot the phone into bootloader, select Fastboot and connect the USB cable.
3) Open a command prompt and navigate to the folder where you saved the recovery image in step 1 above. Type the following command:
Code:
fastboot flash recovery recovery-clockwork-5.8.4.5-primou.img
or
Code:
fastboot flash recovery cwmrecovery.img
4) Reboot the phone back into bootloader using the following command:
Code:
fastboot reboot recovery
You should see the new Recovery.
5. Now on to root the phone!
5A. Head over to XDA Developers and download the SuperSU access management tool. You'll want to grab the attached file at the bottom of the OP called CWM-SuperSU-v0.9x.zip. This will root your phone and install the SuperSU app in one smooth motion. Much thanks, credit and kudos go out to XDA user Chainfire. Login over at XDA and hit the thanks button for him somewhere or donate to his Paypal account and buy him a Coke.
5B. Copy CWM-SuperSU-v0.9x.zip to your SD card.
5C. Restart the phone into HBOOT again and select Recovery. After Recovery has launched, choose install zip from sdcard > choose zip from sdcard and select CWM-SuperSU-v0.9x.zip.
5D. Reboot the phone. It is now rooted!
5E. Go to the app drawer and click on SuperSU. Update the binary when prompted. It’s icon looks like this:
5F. Install and open any app requiring root access to confirm that the phone is rooted.
6A. Backup your stock HTC ROM in CWM5 Recovery!! Before you make changes to your stock ROM or decide to install a custom ROM, this is a must! Reverting back to a stock HTC ROM after installing a custom ROM can cause massive headaches. Restoring from a backup is MUCH easier. It will also help if you've ruined your ROM causing a softbrick. You just boot into CWM5 Recovery, do a factory reset and clear cache (including Dalvik) and do a restore from your previously backed-up ROM.
So, reboot the phone into bootloader, use volume down to select Recovery and press power to select. When Recovery comes up, select Backup/Restore > Backup. Then find the backup you just made on the SD card (under sdcard/clockworkmod/backup) and copy that to your computer for safekeeping in case you loose or format your SD card.
6B. Install custom ROMs Now we play the waiting game and wait for overclockable kernel and custom ROMs. I’ll be updating this section as things happen so come back and see what’s new.
The procedure for flashing a custom ROM is as follows:
1) Boot into Recovery and backup your stock ROM if you haven't already. If you don't and something goes wrong, you'll have a major headache on your hands. *DO NOT* skip this step.
2) Download the ROM and copy it to the root directory of your SD card.
3) From Recovery, o a factory reset, wipe the cache partition and wipe dalvik cache (under Advanced).
4) Install the update from the SD card.
5) Reboot the device.

How To Install Custom Roms
1.Boot into recovery
2.Do a nandroid backup
3.wipe
a.cache
b.dalvik cache
c.data
d.system(isnt necessary)
3.Select install zip from sd card
4.select the rom and put yes
And the rom will install
How to install custom kernels
1.Boot into bootloader
2.enter fastboot and plug your phone into your computer
3.open cmd and type cd and navigate to to where you placed the fastboot.exe and boot.img
then type:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
AND the custom kernel would be installed
How to Make a Nandroid Backup
1.boot into recovery
2.enter backup and restore
3.select backup
So it will backup all your rom
How to restore stock rom after installing custom rom
1.Boot into bootloader flash stock kernel(DO THIS ONLY IF YOU HAVE INSTALLED A CUSTOM KERNEL WITH THE ROM)
2.Enter recovery
3.select backup and restore
4.select restore
And stock rom will be installed
How to partition your sd card and make internal storage bigger
Partitioning is the act of dividing into parts and with SD Card it means to divide sd card into different virtual parts. So, you might be asking why we need to divide our sd card into two parts. This need has come into existence with devices such as Samsung Galaxy Pop/Mini GT-S5570, Samsung Galaxy Ace, Galaxy Fit and other smart phones that have relatively low internal storage (only about 180 MB or 250 MB) as a result it has been very difficult to manage our apps and data within the internal storage. So, to remove such low internal memory problem we are going to partition our sd card and then install the Darktremor Apps2SD Script so applications and games will install to this sd-ext partition that we are going to create by default and we won’t have to worry about low internal memory problem.
Before beginning it is assumed that you have a custom clockwork mod recovery and a custom rom is installed on your device. Alternatively, if you are in a stock firmware/rom and want to partition your sd card please Install Clock Work Mod Recovery and Flash a Custom Rom on your device. Also since partitioning your sd card will erase all your data stored in sd card, it is recommended that you backup your data to your computer. Now that you have backed up your data please follow these simple instructions to partition your sd card and install Darktremor App2sd script on your android smart phone.
1. Reboot your device into Clockwork Mod Recovery.
2. Go to Advance>>Partition SD Card option on your recovery and select a size for ext 3 partition. This will create an ext 3 file system partition on your sd card called sd-ext. The size of your sd-ext partition should be determined on the basis of how much apps and games you are going to install on your device. If you are not of type who wants to test every app or a normal user 2 GB of sd-ext partition should be enough. Determine the size that best suites you and proceed.
3. Also, select swap partition size as 0 Mb.
4. [Optional] Format your sd-ext from mounts and storage>>fromat /sd-ext option in CWM recovery.
5. Reboot your device and open a terminal emulator or shell commander and type in the following command to make sure that your second partition (aka sd-ext partition) is mounted at boot.
mount | grep sd-ext
You should see the following code:
/dev/block/mmcblk0p2 on /sd-ext type ext3 (rw,noatime,nodiratime,barrier=1,nodelalloc,data=ordered)
6. Now download Darktremor Apps2SD and copy it to your sdcard.
7. Reboot your device in CWM recovery and then mount your data and system by going to mounts and storage>>mount /data and mounts and storage>>mount /system options respectively.
8. Now go back to main menu and go to install zip from sd>>choose zip from sdcard option and select the dtapps2sd-2.7.5.3-beta04-signed.zip file you downloaded from above.
9. After the script is installed reboot your device.
That’s all. You have successfully installed Darktremor Apps2SD on your device. Note that the device will reboot again after you reboot your device. This is just to move all your apps to the second partition (sd-ext partition) and is normal. Also if you want to manage your Apps2SD settings you can either use commands in terminal emulator or download this APPS2SDGUI application from market and manage everything from there. One of the useful command can be a2sd help. Try it on any terminal to see the help file that comes with Darktremor A2SD.
Here are some commands that you can run in terminal emulator for configuring a2sd. You can find more info about them as well as other commands by typing a2sd help command.
a2sd check : Checks a2sd status; displays information incl. where your apps, cahce and data are stored.
a2sd cachesd : Moves dalvik cache to sd-ext partition.
a2sd nocache : Moves dalvik cache back to internal storage.
a2sd data2sd : Move /data/data to /sd-ext/data .
a2sd nodata : Move /sd-ext/data back to internal storage.
a2sd remove : Moves apps back to internal storage and sets no a2sd flag.
Now some precautions tips you should take in mind. After installing Darktremor Apps2SD don’t move your apps to sdcard either from Manage Applications Settings or by using app2sd pro or similar applications because it will ruin all your settings and your script will not work. Also you may notice that your used space in internal storage shown in Manage Applications Setting is not decreasing even after you install Apps2SD and you may think that the script is not working. But remember if you followed all the instructions from above and got the same results as explained above then the script is working. It is shown so because system is fooled to believe that the apps are in internal storage but in reality they are stored in the secondary partition we created (i.e. in /sd-ext/app folder) on your device.
How to install recovery
1.grab the recovery file and put it in thre folder where fastboot exists
2.open cmd and type cd and navigate to the folder where they both exist
3.Then type:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache

RESERVED

RESERVED2

RESERVED3

RESERVED4

RESERVED5

RESERVED6

Maybe if you used the search function on the site,before you posted this,you would'nt be the author,fan and publisher of your own thread...... http://forum.xda-developers.com/showthread.php?t=1466228

Honor 8: Nougat (Android 7.x) B360 - TWRP and Root HOW TO

I'd like to create a new thread on installing TWRP and rooting Android Nougat (7.x) on version B360 of the Honor 8. All the threads I see are people frantically trying to restore their phone to their previous glory. To keep people from asking "will this work on yada yada model, *I* have a FRD-L04 which is the 32gb unlocked SINGLE SIM variant sold locally at Best Buy here in the states and I'm pretty sure the FRD-L09 is the international DUAL SIM version with 64GB and I believe firmware for both of these are different? If not, please correct me. The process should be the same for all variants, but the files used will be different.
I want to update this OP and keep it as up to date as possible. If we can get 3 or more people to confirm a certain process works in this thread, I will update it with the proper links to all tools/files/versions of TWRP and SuperSU as well as firmware that's needed. I think I currently count eleven different threads all over the place on this and would be nice to have it centralized. Let's help out and get this phone going with a working root on Nougat!!!
Here are the questions I propose:
1. What is the actual steps to root the Honor 8 running a FULL STOCK version of B360 (Android 7.x)?
A. Unlock Bootloader (This process should be the same as always)
B. Flash TWRP (Which version?) This should be a simple flash with fastboot
C. Flash SuperSU (Which version?) This should be a simple flash with TWRP
D. What are the current issues with this process? (encryption issues, formatting, unable to access the Data partition, etc)
E. How to revert back (and when I say back, I mean ANY working state of Nougat (Android 6.x) or Marshmallow(Android 7.x))
F. How to install extras (Xposed for example, etc)
If I can have answered the questions above, I will clean it up and move it over to the guide section. As it stands now we have no guide. We just need clarification on what works, what doesn't and the process.
Also, PLEASE be kind to those who don't speak English as their primary language. The Honor 8 is an international phone and I see many people getting angry because they don't understand or don't follow instructions correctly because the OP didn't clearly state what they did. Let's help each other out!
Here's an example step by step for unlocking the bootloader below. This is what I'd like to do for each of the questions above.
A: Unlocking the bootloader (UNDERSTAND THAT BY UNLOCKING THE BOOTLOADER ALL YOUR DATA ON THE PHONE WILL BE ERASED AS IF YOU'RE PULLING IT OUT OF THE BOX FOR THE FIRST TIME)
1. Go to Huawei's EMUI site and log in. If you need to create a new account, do so. Link here: http://www.emui.com/en/plugin/hwdownload/download
2. Click on the DOWNLOAD link at the top of the site.
3. Underneath the search field you will see a green link that says "Unlock Bootloader". Click it and follow the instructions. You will be asked to enter in several pieces of information about your phone.
4. Once you've filled out all the information, you will receive your unlock code at the bottom of the screen. Write this down and save it. This number will NEVER change.
5. On your Honor 8, go to Settings > About and tap on the Build Number seven times until you unlock the Developer Settings.
6. In Developer Settings, check Enable OEM Unlock.
7. Scroll down a bit more and check USB Debugging.
8. Go to Huawei's site and download their HiSuite and install it. This installs the OFFICIAL Honor 8 USB driver. Link here: http://consumer.huawei.com/minisite/HiSuite_en/index.html Once the app is installed, you can unselect start with Windows under settings.
9. Plug in your Honor 8 with the provided USB cable. Give it about 45 seconds to install the driver and recognize it. You may need to go to your phone and tap on "Allow File Access". You will be presented with a question asking if you'd always like to trust the computer you just connected to. Select yes, if this is your primary computer you will be working with.
10. Now download the most up to date ADB drivers. A Google employee has created one link to get that and make it easy. Link here: https://developer.android.com/studio/releases/platform-tools.html
11. Open the zip file you just downloaded and create a folder on your computer easy to get to (I recommend c:\ADB) and paste those files there so they are extracted.
12. Now open the folder up in Windows Explorer if you closed it and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
13. Type adb devices and hit enter. You should see a device ID as a response in the window.
14. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
15. Now type fastboot devices and hit enter. You should see your device ID appear again.
16. LAST CHANCE before it wipes everything and unlocks the booloader!!! Type fastboot oem unlock XXXXXXXXXX (where XXXXXXXXXX is the unlock code you received on step 4) and hit enter. It will ask if you're sure. Once this is done, the phone will wipe your data, unlock the phone and reboot. Your Honor 8's bootloader is now unlocked.
B. Flash TWRP (Which version?) This should be a simple flash with fastboot. This is already discussed in another post, but I will put here for reference.
1. Grab a working copy of TWRP for the Honor 8 here: https://forum.xda-developers.com/showpost.php?p=70893767&postcount=408
2. Download TWRP into the same folder you used in step A above (where you're keeping all your files)
2. Navigate in Windows Explorer to this location and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
3. Type adb devices and hit enter. You should see a device ID as a response in the window.
4. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
5. Now type fastboot devices and hit enter. You should see your device ID appear again.
6. Type fastboot flash recovery frd-twrp.img and hit enter.
7. Once this is complete, unplug your phone.
8. Hold Volume UP and Power at the same time. Release ONLY the Power button after the blue Honor logo appears.
9. You now are booted into TWRP and it's been successfully flashed.
C. Flash SuperSU (Which version?) This should be a simple flash with TWRP. This is a crazy process because of the encryption on the Data partition. Below is the exact steps I can confirm works from the help of others on here.
1. Boot into TWRP
2. Once there, when asked to keep system read only? - swipe to allow modifications
3. Tap Install
4. Tap Select Storage - Select your SD card
5. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
6. Swipe to confirm flash
7. Ignore the multiple errors: "Failed to mount '/data' (Invalid argument)
8. Go back to the main menu
9. Select Reboot to Recovery
10. When asked to keep system read only? - swiped to allow modifications (again)
11. Tap Wipe
12. Tap Format Data
13. Type YES then hit enter
14. It will format data using make_ext4fs..
15. When finished, tap Reboot System
16. Reboot back into TWRP
17. Swipe to allow modifications (You can check the box to never show this again)
18. Tap Install
19. Select storage
20. Select your SD card
21. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
22. Swipe to confirm flash
23. You should see NO ERRORS now when installing SuperSU
24. Wipe cache/dalvik
25. Swipe to wipe
26. Reboot system
Once here, you can download root checker and it will verify you have root access - BUT.. see section D below!
D. What are the current issues with this process? (encryption issues, formatting, unable to access the Data partition, etc)
Some applications like Root Checker will verify that you have root. Other applications will even prompt you (like any of the basic quick reboot apps that easily let you back into recovery) but other major apps like BusyBox and Viper4Audio (when asking to load the driver) will simply fail upon installation. I'm not sure why, since you have R/W access to both the system and the newly unencrypted data partition. I'm really hoping someone can help with this one!
E. How to revert back (and when I say back, I mean ANY working state of Nougat (Android 6.x) or Marshmallow(Android 7.x))
F. How to install extras (Xposed for example, etc)

I know and have done A, B, and C, but as for the rest I'm not too sure about those.

Maybe in the wrong section but thank you.

joesee said:
14. It will format data using make_ext4fs..
Click to expand...
Click to collapse
The Honor 8 defaults file system for /data is F2FS. Do you see any performance changes going back to EXT4? Is it possible to keep F2FS?

joesee said:
15. When finished, tap Reboot System
Click to expand...
Click to collapse
When I wipe then reboot I get stuck in the bootup screen
EDIT； Nevermind I just didn't wait long enough for my phone to boot up

KevinN206 said:
The Honor 8 defaults file system for /data is F2FS. Do you see any performance changes going back to EXT4? Is it possible to keep F2FS?
Click to expand...
Click to collapse
Yes, but twrp read it as ext file, i tested both format f2fs and ext4, i dont feel any different between those 2.
Yes, you can changed the data format to f2fs with twrp but if you reverted back to MM, its requred to changed the data to ext4 format, if not, you'll get bootloop. (dont know if its twrp bugs or not)
Worst scenario, you'll lost all stock recoveries and everything.
I've been there... Lol

faizalotai said:
Yes, but twrp read it as ext file, i tested both format f2fs and ext4, i dont feel any different between those 2.
Yes, you can changed the data format to f2fs with twrp but if you reverted back to MM, its requred to changed the data to ext4 format, if not, you'll get bootloop. (dont know if its twrp bugs or not)
Worst scenario, you'll lost all stock recoveries and everything.
I've been there... Lol
Click to expand...
Click to collapse
Are you saying I can format /data with F2FS to remove the encryption? I am assuming TWRP does not support the encryption yet. Bootlop sux but most important stuffs on my phone is stored on the SD card anyway so it's not too bad to start over.
Maybe it's just me but it seems encryption adds a bit of risks when playing around with rooting. Has there been a scenario where you *can't* recover from bootloop permanently?

KevinN206 said:
Are you saying I can format /data with F2FS to remove the encryption? I am assuming TWRP does not support the encryption yet. Bootlop sux but most important stuffs on my phone is stored on the SD card anyway so it's not too bad to start over.
Maybe it's just me but it seems encryption adds a bit of risks when playing around with rooting. Has there been a scenario where you *can't* recover from bootloop permanently?
Click to expand...
Click to collapse
So far, i've experienced with bootloop and no recoveries available,
As long as you have fastboot mode and bootloader key, you're safe.

faizalotai said:
So far, i've experienced with bootloop and no recoveries available,
As long as you have fastboot mode and bootloader key, you're safe.
Click to expand...
Click to collapse
I am afraid of running into this issue from a fellow xda. The person still doesn't have a solution. https://forum.xda-developers.com/mate-8/help/encrypted-data-mount-t3537645

I'm running into issues with Bluetooth activation, and previously NFC, which i fixed by reflashing the hw_update package, but still no Bluetooth.
I've followed each and every single step on this guide, and BT was working perfectly before.
Any ideas where this may be coming from ?
Still, thanks or the guide

For the SuperSU instructions, you don't have to reformat /data. Yes, TWRP won't be able to access it, but you really only need that for making full system backups. You can access everything in /system/ and then ADB push to /data/ after boot, or fastboot flash an image to /data/ from bootloader. It's not ideal, but it saves you from having to wipe out your configuration.
I'll echo the above poster, as long as you're bootloader unlocked and can issue fastboot commands I'm not sure you're truly bricked. Worst case scenario you ought to be able to flash individual partition images to recover, I unpacked the Nougat update zip to extract the partition images and I've been using those when my tinkering results in a bootloop -- corrupted boot and corrupted recovery I fixed easily.

Hello. Im coming from general topic on Honor 8 rooting but my issue is related to Android MM.
So i had stock EMUI 4.1 (Android 6.0) which i unlocked, flashed TWRP and SuperSU.
Today EMUI 5 (Android 7 ) update came by air so i installed it. After update - no TWPR neither SuperSU.
I enabled Developer options and saw "Enable OEM unlock" switch in OFF state and grayed out (impossible to switch ON).
So now i cannot flash TWPR as fastboot gives error "Command not allowed".
During boot phone says that it is unlocked, FRP lock. Otherwise it boots and works fine but no root.
Any solution possible?
Thank you.

Telperion said:
For the SuperSU instructions, you don't have to reformat /data. Yes, TWRP won't be able to access it, but you really only need that for making full system backups. You can access everything in /system/ and then ADB push to /data/ after boot, or fastboot flash an image to /data/ from bootloader. It's not ideal, but it saves you from having to wipe out your configuration.
I'll echo the above poster, as long as you're bootloader unlocked and can issue fastboot commands I'm not sure you're truly bricked. Worst case scenario you ought to be able to flash individual partition images to recover, I unpacked the Nougat update zip to extract the partition images and I've been using those when my tinkering results in a bootloop -- corrupted boot and corrupted recovery I fixed easily.
Click to expand...
Click to collapse
can u please tell more or make a step by step tutorial on rooting? I'm stuck in rooting, when I format data and boot agai into recovery and flash su It still ends with error 1, dnt know which error it is..

I have FRD-L09 C432B360 Honor 8 (Sweden) with EMUI 5.0, i have TWRP 3.1.0.0, unlocked bootloader
I could not root my phone since it uppdated to nougat (EMUI 5.0)
I tried everything what i could find on the net, but nothing worked yet, any suggestions ?
thanks

Is there any way to do this without rooting?
I recently got my phone and I didn't get the update. I am still running on EMUI 4.1

ajmdrh said:
I have FRD-L09 C432B360 Honor 8 (Sweden) with EMUI 5.0, i have TWRP 3.1.0.0, unlocked bootloader
I could not root my phone since it uppdated to nougat (EMUI 5.0)
I tried everything what i could find on the net, but nothing worked yet, any suggestions ?
thanks
Click to expand...
Click to collapse
Update to latest TWRP and try again

Shehzaan said:
I recently got my phone and I didn't get the update. I am still running on EMUI 4.1
Click to expand...
Click to collapse
Indian version?? Frd-l02?

venugopalu007 said:
Indian version?? Frd-l02?
Click to expand...
Click to collapse
Nope, it is FRD-L09C636B130. I think this is the Middle East version.

Shehzaan said:
Nope, it is FRD-L09C636B130. I think this is the Middle East version.
Click to expand...
Click to collapse
Yes, it is middle east variant

PalakMi said:
Yes, it is middle east variant
Click to expand...
Click to collapse
Do you have any idea how can I get EMUI 5.0 without rooting?

Lenovo P2 (NEW OWNERS: Click Here)

[SIZE=+3]Lenovo P2[/SIZE]
[SIZE=+2][INDEX][/SIZE]
[SIZE=+2]Helpful Information[/SIZE]​[SIZE=+1]Welcome, this thread has been created to encompass everything you may need for your device. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread, or create your own thread in the Q&A forum. Do not use this as a general help thread.[/SIZE]​

Basic Device Information
Released in November 2016, the Lenovo Vibe P2 is a 5.5" smartphone with mid-range specifications and a budget-friendly price. It is the successor to the Lenovo Vibe P1, offering an even higher battery capacity fitted inside a thinner and lighter body.
There are two variants of the Lenovo P2; the international (or global variant) and the Chinese variant. Therefore, it is very important to know which one you have or which one you should buy. If you bought your device from retailers in India/UK/Europe, it is very likely that you bought the international version. The international version has the code name P2a42, whereas the Chinese version is labelled P2c72. The easiest way to distinguish between the two is to check the storage size. Only the Chinese variant (P2c72) of the P2 comes with a 64GB storage. Hence, if your P2 has only 32GB of internal storage, your P2 is the international variant (P2a42).
Aside from differences in storage, the two P2 variants differ in the bands they support. Courtesy of user @911-Future_Maker, the differences are highlighted in red.
P2a42
GSM: GSM850/ GSM900/ GSM1800/ GSM1900
3G: UMTS2100 (B1)/ UMTS1900 (B2)/ UMTS850 (B5)/ UMTS900 (B8)
4G: LTE2100 (B1)/ LTE1800 (B3)/ LTE1700/2100 (B4)/ LTE850 (B5)/ LTE2600 (B7)/ LTE900 (B8)/ LTE800 (B20)/ LTE700 (B28)/ TD-LTE2600 (B38)/ TD-LTE2300 (B40)
P2c72
GSM: GSM850/ GSM900/ GSM1800/ GSM1900
3G: UMTS2100 (B1)/ UMTS900 (B8)/ CDMA800 (BC0)/ TD-SCDMA2000/ TD-SCDMA1900
4G: LTE2100 (B1)/ LTE1800 (B3)/ TD-LTE2600 (B38)/ TD-LTE1900 (B39)/ TD-LTE2300 (B40)/ TD-LTE2500 (B41)
Despite the differences in the internal storage and radio bands, both variants share common partitions, aside from the data partition, of course. As a result, many global Chinese shops, such as bangggod and gearbest, sell the P2c72 preflashed with the P2a42 firmware; the reason being that the P2a42 firmware supports more languages, whereas the P2c72 firmware supports only English and Chinese, among other reasons. Even though the P2c72 can run the P2a42 firmware, the bands that it supports remain those of the P2c72.
NOTE : Do not flash your device with files that are intended for the other variant. You will very likely end up with either a bricked phone or a phone that does not recognize the sim or your carrier's network. You have been warned!

Official Stock Firmware
You should only flash the full firmware when it is the method of last resort. The choice of which firmware version to use should be based on the variant you own and the version of Android installed. It has been reported that if you flash the full firmware intended for Android 6 on the P2 that is already on Android 7, then you will have modem issues. Be warned.
P2a42 Firmware
Downloads (Thanks to @abhayruparel. Password: lenovo-forums.ru)
P2a42_S048_161111_ROW_fastboot.7z
P2a42_S062_170117_ROW_fastboot.7z
P2a42_S232_170320_ROW_fastboot.7z
P2a42_S233_170404_ROW_fastboot.7z
P2a42_S244_170725_ROW_fastboot.7z
P2c72 Firmware
Downloads (The files below are hosted on baidu servers; download speed is very slow.)
联想VIBE P2 P2c72_USR_ST1637_官方原厂固件ROM线刷包下载 首发
联想P2 P2c72_VIBEUI_V3.5_1652_5.1342.1官方固件ROM线刷包下载
联想P2c72官方线刷固件VIBEUI_V3.5_1706_5.1599.1_ST安卓7.0首发

Official Stock Updates
Upon receiving the P2, it will most likely still have Android 6 installed. You can either update your device automatically to Android 7.0 via OTA updates or manually by downloading the files below and flashing them one after the other. Please note that these files are intended only for owners of the P2a42 or the P2c72 with the P2a42 firmware.
Downloads
From S048 to S062 (Android 6 minor update)
From S062 to S232 (Android 6 to Android 7.0 update)
From S232 to S233 (Android 7.0 minor update)
From S233 to S244 (Android 7.0 minor update)
In order to manually upgrade, you must have a sdcard. The upgrading process has to be done in the numerical order in which the files are listed above. For example, you download the first file, move it to the root of your sdcard, rename it to update.zip, reboot into recovery, upgrade, restart the phone, and repeat the same process for the second file and so on.
To manually install updates:
Shut down the phone.
Hold Vol Up + Vol Down + Power Button to boot into the recovery menu. Release the buttons when the screen turns on.
In the recovery menu, Select Install Update Package > Yes.
After the last upgrade is installed, it is advisable to do a factory reset. Enter the recovery menu. Choose Wipe User Data. First do Fuse Wipe Data, then Fuse Format Data, and finally Wipe Cache, all the while selecting Yes when asked.

USB Drivers, Root, Custom Recoveries + Stock Recoveries
USB Drivers
Lenovo USB driver 1.1.34
Qualcomm USB driver 2.2.0.0
Unlocking the Bootloader
The bootloader must be unlocked before any modding can be done on the P2. Please be aware that unlocking the bootloader voids your warranty and formats your data partition (don't forget to backup important files). Unlocking the bootloader on the P2a42 or the P2c72 running the P2a42 firmware is a simple process.
Go to Settings > About phone > Tap 7 times on Build number > Go back > Enter Developer options > Enable OEM unlocking
Accept the terms that you understand that you're voiding your warranty by choosing to unlock your bootloader
Login with your Lenovo account (if you already have one) or create a new one
Wait for 14 days. A countdown timer will begin that is specifically associated with your device.
After the waiting period, go back to OEM unlocking so that the Lenovo servers can toggle the bootloader unlock switch.
At this point you must have installed the Lenovo USB drivers and Minimal ADB Fastboot on your Windows computer.
Shut down the phone. Enter into fastboot mode by holding Vol Down + Power Button until the screen turns on.
Connect the P2 to your computer and open Minimal ADB Fastboot.
Type: fastboot oem unlock
Recoveries
TWRP 3.2.1-0 (latest custom recovery)
Stock Recovery for Android 6
Stock Recovery for Android 7
If you're going to be installing custom ROMs, it is better to replace the stock recovery with TWRP. Check this page for more information or the latest updates. The procedure below works for both the P2a42 and the P2c72 running the P2a42 firmware.
Rename the TWRP file to twrp.img and move it to both the root of the internal storage of your P2 and the folder where Minimal ADB Fastboot is installed (usually C:\Program Files (x86)\Minimal ADB and Fastboot).
Boot the P2 into fastboot mode.
Open Minimal ADB Fastboot and type : fastboot boot twrp.img
Inside TWRP, choose Install > Install Image > Look for twrp.img > Select recovery > Slide to install.
TWRP will now be installed over the stock recovery. At this point, it makes sense to do a full backup of your partitions. Backup everything except System Image and Cache. In the event you want to return to stock recovery, either restore only the recovery from the Restore menu in TWRP, if you had saved a backup, or flash it as in step 4 above. You should download the stock recovery for the Android version installed on your P2.
Rooting
Files for Magisk method
Files for SuperSU method
The methods described here are only applicable for the P2 running on stock Android 7. Check this post for more details or instructions on how to root the P2 on stock Android 6.
There are basically two methods that can give you super user privileges on the P2. If you have apps that won't allow you to use them if your device is rooted (such as Android Pay), then the Magisk method is for you. This method roots your device without modifying Android's system partition at all. This means that fewer of Android's built-in security measures need to be bypassed in order to gain root access. At the moment, for the Magisk method to work, you need to format the data partition to EXT4. This will obviously erase all your files; so, backup important files before going ahead with it. Download the latest version of Magisk from the link above and move the zip file to the P2's internal storage.
Shut down. Boot into TWRP.
In TWRP, select Wipe > Advanced Wipe > Select Data > Repair or Change File System > Change File System > Select EXT4
Go back to the main menu: Select Install > Look for Magisk-vx.y.zip > Slide to install.
There's also another method you can root the P2 with, but this method is deprecated; it is advisable to use Magisk to provide root privileges as described above. Rooting via the SuperSU method is only presented here for the sake of reference.
You will find two files in the "Files for SuperSU method" linked above.
Install the me.phh.superuser.apk file.
Move the superuser-r259.zip file to the root of the P2's the internal storage.
Shut down. Boot into TWRP.
Select Install > Look for superuser-r259.zip > Slide to install.

Reserved

MODS, GUIDES, and Misc
Decryption the internal storage
The only reason I could think of why someone would want to decrypt the internal storage is to be able to multiboot as one of the requirements of DualBootPatcher is for the internal storage, or more specifically the data partition, to be unencrypted. It's important that you understand that decrypting the internal storage makes it very easy for anyone with access to your phone to access all your data. You're warned: your phone is the most personal and most portable device you have, don't be reckless with your data.
It is very likely your P2 is already encrypted. You can easily verify that by going to settings > security. If you see "Encrypted" under "Encryption", the internal storage is encrypted. If you had not set the phone to require a pin/password to boot, the phone would be encrypted using the default password. If TWRP doesn't prompt you for authentication, it may be because it tries the default password at first and succeeds with that. So, getting access to your internal storage in TWRP does not necessary mean the internal storage is not encrypted.
You need to format data (under TWRP) to remove the encryption. This obviously deletes everything on your phone; so, backup your important stuff first. Reboot the phone back into recovery after formatting data. If TWRP doesn't detect the the partitions of your internal storage, boot/flash the stock recovery. The stock recovery will properly format the partitions. Boot/Flash TWRP one more time and you will see all the partitions again. At this point, you should change the format of the data partition to ext4 and install Magisk. Installing Magisk will modify the boot partition and will prevent the phone will automatically re-encryp itself.
Getting back to Stock Firmware
In the event you can no longer boot into the phone, or your phone is bricked, you may want to reinstall the stock firmware. After downloading and extracting the zip file, you will find a file called flashall.bat inside the SW folder. All what is required then is putting the phone in fastboot mode and executing this file. However, if you've already unlocked your bootloader, running flashall.bat will fail. What you need to do is to flash the partitions manually.
In the extracted zip file, you will find files labelled systemchunkx.img (probably around 15 of them), boot.img, and recovery.img. Put your phone in fastboot mode, open Minimal ADB Fastboot and do the following:
Flash the boot image: fastboot flash boot boot.img
Flash the recovery image: fastboot flash recovery recovery.img
Flash the system chunks one after the other, starting with the first one until the last one. For example, to flash the first system chunk: fastboot flash system systemchunk1.img

medwatt said:
Official Stock Firmware
You should only flash the full firmware when it is the method of last resort. The choice of which firmware version to use should be based on the variant you own and the version of Android installed. It has been reported that if you flash the full firmware intended for Android 6 on the P2 that is already on Android 7, then you will have modem issues. Be warned.
P2a42 Firmware
Downloads (Thanks to @abhayruparel)
P2a42_S048_161111_ROW_fastboot.7z
P2a42_S062_170117_ROW_fastboot.7z
P2a42_S232_170320_ROW_fastboot.7z
P2a42_S233_170404_ROW_fastboot.7z
P2a42_S244_170725_ROW_fastboot.7z
P2a72 Firmware
Downloads (The files below are hosted on baidu servers; download speed is very slow.)
联想VIBE P2 P2c72_USR_ST1637_官方原厂固件ROM线刷包下载 首发
联想P2 P2c72_VIBEUI_V3.5_1652_5.1342.1官方固件ROM线刷包下载
联想P2c72官方线刷固件VIBEUI_V3.5_1706_5.1599.1_ST安卓7.0首发
Click to expand...
Click to collapse
P2c72 * in firmware

Add blankflash tool also to recover from hardbrick
Sent from my Lenovo P2a42 using Tapatalk

Add advice as to how to safely flash TWRP and root a P2c72 hardware device running P2a42 firmware.

Add twrp installation and root method on nougat

Im a new owner of P2, recently i upgraded my firmware to the latest(S244) and doing so upgrade ended up with something wrong i mean process/recovery didn't gave any error and even phone booted up normal but process wasn't 100% phone rebooted from like 88%, so after bootup from recovery i wiped all data and did a factory reset and used it like normal, everything was working perfect but after a week i facing random issues like battery drain, signal not sticking to 4g network, low wifi reception etc, i tried factory resetting again from recovery but that didnt solved my problem so i want flash factory firmware(android 7 S244) given above.my device is P2a42, locked bootloader, so can anyone tell me how should i flash those images, because i dont want to end up messing with modem files

After the waiting period, go back to OEM unlocking so that the Lenovo servers can toggle the bootloader unlock switch.
Click to expand...
Click to collapse
I am at this step. When press "Next" nothing happen. What do I do? Latest update, pa42 version
Found, I needed internet access.

Nice work! Helpful for new users!
Also include QCN backup method.
Sent from my Lenovo P2 using Tapatalk

Hi @medwatt,
Is there an official link to those official OTA updates please?

Bump

I rooted with super su I want to unroot and try magisk
How do I unroot?

Hello I have a P2 p2c72 with rom p2a42 bought at gearbest.
I just want to root it to use titanium backup (root access), should I use twrp recovery or can I stay with the original recovery and flash magisk after unlock bootloader ?
I don't want custom rom.
Thank you.
[EDIT] Thanks for the guide, it's good for me, twrp ok and root with magisk !

Just want to say great work on this thread!
The information for the P2 has become convoluted in the past 12 months and a summarization and write up such as this is helpful for everyone to benefit from!

Big Thanks.

Infinix Zero 5/Zero 5 pro (X603) TWRP Recovery 3.1.1 With OTA Support

Touch is Working Now. (Finally) with OTA Support only for zero5 indian varient
Join Telegram group for further development : https://telegram.me/infinixzero5
This is Ported TWRP Recovery from a same Mt6757 chipset model. which i used to port it for our Infinix X603.
Thanx @topjhonwu for magisk.
Thanx for @majorkid for making OTA supportable
TWRP for non indian and global version for necessary changes. (Need to test)
Warning:-
I am not responsible for bricked devices.
Your warranty will void now. Do it at your own Risk.
Unlocking Bootloader
- Make sure your Bootloader is Unlocked. If already unlocked jump to how to flash.
Process to unlocking.
1. go to settings/about phone/build number (tap build no for 7 time now developer option available in settings)
2. go to developer option turn on usb debugging and OEM unlocking.
3. then go to pc download and extract and copy adb fastboot driver folder in Drive C. (or install form net.)
4. Go in fastboot folder which is copied to C. press and hold shift key on your key board and click right key on your mouse it will show option open cmd here or open power shell window here.
5. Click it, A cmd or power shell window will open.
type "adb devices" - it show some no of your device just give permission from your phone screen)
type "adb reboot bootloader" your phone reboot in bootloader mode.
type "fastboot oem unlock" follow onscreen instruction on phone, press volume + to confirm. thats it but it will erase all your data.
Reboot phone by pressing power button for 10 sec. setup it as temporarily.
Flashing of TWRP
1. Download the Latest TWRP Recovery Image and extract it (Attached). Use correct version for your device for OTA support.
For India (Indian) For Global (Global)
(Insert a SD card in your phone to take stock boot.img backup it will required for OTA in Future.)
2. Go in adb fastboot folder which is copied to C. copy twrp_recovery.img here then press and hold shift key on your key board and click right key on your mouse it will show option open cmd here or open power shell window here.
3. Click it, A cmd or power shell window will open.
4. Flash it via fastboot cmd (fastboot flash recovery Twrp_recovery.img) don’t use bracket.
It will flash recovery on your phone. Now type fastboot reboot in cmd window and press and hold vol+ button and hit enter.
Phone will reboot in twrp recovery.
Note : After flashing first time it will ask for password due to phone is encrypted.
a. just cancel it and allow to modify system by swiping arrow at down and select 2nd last option at right side then select globe icon on right and chose your language English.
(First take Boot.img backup Via backup option in TWRP in SD Card. (bcz internal storage shows 0 mb here at this movement.) It will use for OTA so save it.
b. then flash magisk manager.zip file attached here. (it will remove dm-verity and force encryption from boot.img) and give root access.
c. then go to Wipe and select format Data it will erase all data on your internal storage. remember it will erase your data in ext4 format so go to wipe advance select data and change file system to f2fs. Ext4 data not supported by kernel so you got loop to recovery so It must to repair data in f2fs.
d. Done Reboot to recovery and you got mounted storage.
Another Method.
- Flash it via SP flash tool. (use version 5.1744 recommended)
How to use SP flash tool :
Install Vcom media tek driver on your pc.
More detail and download available on following link
https://spflashtool.com/
IF ANYONE GOT LOOP IN BETWEEN TO RECOVERY MEANS PROCESS NOT FOLLOWED PROPERLY.NOT BOOTING PHONE JUST FLASH STOCK RECOVERY. YOUR PHONE WILL BOOT THEN DO PROCESS AGAIN.
OTA-
1. When ota available just download it. Don’t start flashing.
2. Location of OTA downloaded file in Root so use any root file explorer.
3. File can be found in :-
a. Root/cache/update.zip
b. Root/data/data/com.google.android.gms/app_download/update.zip
4. Copy file name is update.zip to your sd card or phone memory.
5. Reboot to recovery and flash first stock boot.img which you already taken backup and saved before when flashing twrp.
6. now flash update.zip via TWRP (dont reboot after flashing otherwise you will currept your system)
7. After flashing update.zip, first again take backup of your boot.img for future ota update.
8. After taking backup of boot.img flash magisk.zip and reboot. (If you did not flash magisk then your data again encrypted and u lose all data)
6. Done you are on latest version.
Note:- Always remember to flash magisk.zip at last before reboot.
OTA SUPPORTABLE TWRP Link for zero 5 global varient by @majorkid -
https://androidfilehost.com/?fid=890129502657578792
OTA SUPPORTABLE TWRP Link for zero 5 pro global varient by [MENTION=7078341]majorkid[/
https://androidfilehost.com/?fid=890129502657578807
Update: Last updated on 27/01/2018 (With almost all stock stuff with OTA support)

Thank you for your efforts I don't know why but it didn't work (i searched and downloaded alot and it's the only recovery that gave me a response but the screen was flipped and the touch was disabled, also the stock recovery is working well)

XDAdeveeloopers said:
Thank you for your efforts I don't know why but it didn't work (i searched and downloaded alot and it's the only recovery that gave me a response but the screen was flipped and the touch was disabled, also the stock recovery is working well)
Click to expand...
Click to collapse
flip screen was old but i updated it with working twrp. is it showing vernee mix 2 name on top?
can you send screen shot.
its working perfectly.
just match the zip size which you downloaded (if it is 13.23 mb then it is old)
download current version attached above is 15.31 mb in size.
Screen Shot is also updated
Let me know your success.............................

flipped screen fixed !
Ok, now it's not flipped but the touch is still disabled
again, thank you for your efforts. I've attached the screenshots. it tells me to enter the password but the touch is disabled and i couldn't type anything.

At this stage only cancle button will work. Dont type anything just press cancle button.
It shows next screen.
I chek if issue is there.

Cancle is not working too

XDAdeveeloopers said:
Cancle is not working too
Click to expand...
Click to collapse
just use it as temp. bcz after flash touch not working.
Touch is disabled in kernel for recovery partation by infinix.
for temp use cmd.
fastboot boot recovery.img
will update soon..........

when i connect my mouse via otg or flash it temporarily it works fine except that it shows that the internal storage is 0mb and when i try to install something it tells me that it's unable to mount /data as rw
also can you tell me how to get the password required in the first screen ?

XDAdeveeloopers said:
when i connect my mouse via otg or flash it temporarily it works fine except that it shows that the internal storage is 0mb and when i try to install something it tells me that it's unable to mount /data as rw
also can you tell me how to get the password required in the first screen ?
Click to expand...
Click to collapse
Read OP carefully. You need to format data partition completly first time and need to patch boot img via lazy flasher.
Showing 0mb bcz it is encrypted. You can use memory card.
If you want root then go for magisk root till recovery updated.

OK, now I removed the encryption, installed magisk and the root worked but when I try to install busybox and some other apps it doesn't work. When I try to install supersu zip it doesn't work (extracting ramdisk failure aborting) , isn't there any way to install supersu in order to get apps working correctly?

XDAdeveeloopers said:
OK, now I removed the encryption, installed magisk and the root worked but when I try to install busybox and some other apps it doesn't work. When I try to install supersu zip it doesn't work, isn't there any way to install supersu in order to get apps working correctly?
Click to expand...
Click to collapse
which busybox your trying and what error.
currently supersu have some error with new devices. which version you tried it should be 2.82 or above.

I downloaded SuperSU-v2.82-201705271822.zip
Busybox pro 61
MagiskManager-v5.4.3.apk

XDAdeveeloopers said:
I downloaded SuperSU-v2.82-201705271822.zip
Busybox pro 61
MagiskManager-v5.4.3.apk
Click to expand...
Click to collapse
Use busybox form playstore stericson.

I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.

Finally the Touch is updated and working now.
I enabled touch in kernel which is disabled for recovery partition.

XDAdeveeloopers said:
I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.
Click to expand...
Click to collapse
System is encrypted.
Use magiskmanager beta 14.5 or flash lazyflasher via twrp then one time you need to wipe data partition.
Always remember when you flash orignal boot.img you need to flash lazyflasher or magisk otherwise your system will become encrypted again.

Thank you, now touch is working perfectly <3

XDAdeveeloopers said:
I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.
Click to expand...
Click to collapse
you can use ndk busybox from magisk app there is option download module.
But currently there is problem with module with this phone. the data partition is in F2FS format and its kernel is not handling f2fs properly.
TWO option for use magisk module.
1. wait for kernel update via infinix. or
2. format data partition as Ext4 from twrp.
Super su does not work correctly with f2fs currently.

But when I format data partition it resets my phone

XDAdeveeloopers said:
But when I format data partition it resets my phone
Click to expand...
Click to collapse
yes formatting data will reset it.

[Error][fix][Solution][Guide]Errors in flashing custom rom in Lenovo A2016a40 and ways to tackle/fix them

CASE: After flashing lineageOs 14.1 on my Lenovo A2016a40 (chipset: MT6735M) using TWRP, I lost my IMEI and Baseband version which made my phone just like a screen with no calls, no connection, no internet. so, basically I had no option than to flashing the stock ROM (eventually I need that custom ROM as that is an upgraded one). I flashed only secro.img on the custom rom using SP Flash Tool that caused a bootloop ( I again had to took help of the stock rom ).
Now, the question is:
1. Can I flash secro.img on that custom Rom, if yes, how?
2. If not, how can I get back my baseband version?

today I flashed ressurection remix 5.8.4 on the mentioned device and that caused the exact same problem as mentioned.

Well, today I succeed after 2 weeks of sleepless nights in search of a solution that elaborates how to flash a custom rom successfully on the mentioned device(i.e. Lenovo A2016a40 (also known as Lenovo vibe B)). Now, as I felt the frustration of seeing the phone without network and everything else, I want to mention the whole process I've gone through.
Here is the step-wise guide on how to flash a custom ROM on Lenovo A2016a40 (Hope it works with other devices too)
NOTE: Here in this tutorial I'm not asking you to try a custom rom, it's upon u to use custom rom or not. this tutorial is to guide those who has already stepped into the process and get into an error or so(hope not so). any damage to your device is solely your responsibility, try in your own risk if you want.
GOOD LUCK
BEFORE FLASHING:
1. Take your normally functioning device.
2. Root that device.
For Lenovo A2016a40 I've followed this neat and clean page and found it helpfull.
Here is the summary of that really clean page (the page is a bit outdated follow my paths for updated method (as in December 2020) ).
a) Download and install Magisk Manager app on your andrid device.
b) Launch the app and tap on "install" that is on the same slide as the logo, and then choose to patch boot image by tapping on "Patch Boot Image File" after which the patching process will start which will create a image file called "magisk_patched.img".
c) Transfer that magisk patched image file on your PC.
d) Connect your device to your pc where you have stored magisk patched image.
e) Now enable "USB Debugging" and "Enable OEM unlock" from Settings>Developer's option (or, Settings>About Phone>7x tap on Build Number>Settings Home> Developer's option)
e) (Assuming you have ADB and Fastboot installed, if not follow whatever google says.) Now, open cmd on the folder where you have kept that magisk pathced image by
Code:
Shift+Right Click
and selecting "Open Command window Here" and check for your device's connectivity by typing
Code:
adb devices
in cmd, and after confirmation(seeing device's serial number) type
Code:
adb reboot bootloader
to enter fastboot mode (Fastboot Mode written on screen), confirm connectivity by
Code:
fastboot devices
, being confirmed type
Code:
fastboot oem unlock
to unlock bootloader and then do press
Code:
Volume up
button to unlock bootloader.After seeing "Okay " on command window, type
Code:
fastboot flash boot magisk_patched.img
and finally
Code:
fastboot reboot
and then press and hold
Code:
power + volume 'up'
buttons of your phone for about 10 seconds and then navigate to 'Normal mode' by using
Code:
volume up
button and confirm by using
Code:
volume down
button and wait for device to start.
f) Check Root status using Root Checker like apps
2. Backup some important system files.
This step is essentially important. I got into this from this thread.
a) Install Root Manager or similar apps and grant them root permisions.
b) Head to /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
c) Copy the mentioned files into a safe place(generally in external sd card) or newly created folder.
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
d) Now, head to /data/nvram/md/NVRAM/NVD_IMEI and copy the file named
Code:
MP0B_001
to another safe place generally in external sd card.
NOTE: All the above mentioned files are important for your device's network functioning.
e) Now, backup or replace whatever you want to keep (personal things).
FLASHING:
1. Download your preferred custom rom(.zip file) strictly for your device and transfer them into the inserted sd card or phone internal memory.
2. Install a custom reecovery.
Download your preferred custom recovery. I've used TWRP custom recovery and going to describe processes for that only.
a) Connect your device to pc and confirm connect by above mentioned method from the downloaded folder and then unlock bootloader the same way as mentioned above.
b) After unlocking bootloader run the commands as mentioned below (press "Enter" after each line)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
c) Now, enter the menu containing "Normal mode" option by the same mentioned method and this time select "Recovery mode" and you will get into TWRP custom recovery.
NOTE: Critical error can occur if you do pull out the battery and power off the device by any other means.
NOTE. After entering TWRP you can face an error saying
Code:
/data not mounting
or something like that, in that case head toward wipe section, select "Advanced wipe", select 'Data' and select 'Repair File system', then change partition style to "ext2" and then back into "ext4" and this solves the problem.
3. Backup your system and whatever you like. (generally "secro" "nvram" & "nvdata")
4. Free space for new custom rom by entering Wipe section and selecting the following
Code:
Dalvik/ART
system
Data
Cache
Internal Stoage (if you want to or optional)
5. Install your custom rom (with Gapps and Root if you want).
Enter "Install" section select and install .zip files for custom rom, gapps and root one by one or at once, whatever you want.
AFTER FLASHING:
Welcome to your literally new phone.
while you are expecting to celebrate it, you will find some of the most frustrating errors like Unknown Basband, Null IMEI.
Now to solve those errors follow the below mentioned points one by one
1. install root manager like app and grant root permission.
2. copy and paste the 7 files that you have copied earlier (expdb, proinfo, protect1, protect2, nvdata, nvram, secro ) to the path as " /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name", if prompted select "Overwrite", then select the files and provide them all 9 permissions you will get in permission section for those files.
3. Reboot Device.
4. now, delete the folder named "nvram" in path "/data/nvram" to get your baseband version back, as mentioned in this thread, and it worked for me, you may have to try deleting it 3-4 times continuously.
5. Reboot device.
6.Now, copy and paste the copied 'MP0B_001' file to the path as "/data/nvram/md/NVRAM/NVD_IMEI" and similarly assign all the 9 permissions asked in permission window.
7. Set APN if needed. follow this tutorial and you may not be able to save changes (hope not), if so, try putting some random name in the 'Name' field like "avghbejugcbjnsjckln".
8.Reboot Device.
Enjoy the fresh new customization.
NOTE: Keep your device's stock firmware and sp flash tool with you. it will help you get your device back from a bricking type error. try in your own risk.