[Guide] Dual Boot Any MMC Block Based Device with separate recoveries [NOOBS Welcom] - General Topics

Ok guys this is my first tutorial, so bare with me. This all started when I wanted to dual boot my Note 10.1(N8013), & came across this thread. If I hadn't found that thread, I would never have come up with this, so thanks are owed to the author. Now then, enough with my ramblings, lets get to the point.
What will this guide get you?
With this guide, you'll get two completely separate ROMs, each with their own recovery menu, so you will be able to use the recovery menu on each ROM individually. You'll also get scripts for switching between roms, & recoveries.
What is required?
*Android Device with MMC Partitons(Ex: mmxblk0p1)
*Computer with Windows
*USB Sync Cable
*8 GB or larger MicroSD Card
Prepping SD Card:
Backup your sd card if you want to keep your data. Install AParted onto you device from the Play Store. Open Aparted, granting root access when prompted. Decline the "Agreement" because it will just try to install junk. Tap "configuration", then tap the drop box under "Detected devices". You should see "mmcblk0", "mmcblk1", and possibly "usbdisk". If you don't have both "mmcblk0", & "mmcblk1", then stop here, because this guide isn't for you. If you do, then select "mmcblk1" from the list, tap "Save", then "OK". Tap "TOOLS", you should now see parts 1 through 4, "Part: 1" should say fat32 or similar, and say the size in MB of your external SD card. If it does, then tap the checkbox next to "Part: 1", next tap the drop box that says "Create", select "Delete" and tap apply. Once done, all parts should say empty, now for the semi-hard part. We're going to create 4 partitions. The first partition is going to be the standard external sd partition, that will show up in both roms, lets make it. Tap "CREATE" on the top, tap "+", tap the box with "0MB" in it, set it to the size you want the card to be, keeping in mind, that we need at LEAST 4972MB of space for the second ROMs' partitions. Also the more space you leave, the more space you can put into the second ROMs' "Internal" memory. Tap "+" once more, tap the "0MB" box again, this time putting in "1537", tap "+", this time put 839. On the next one put the rest of the remaining space into the box, this one is the data partition, aka the internal memory of the second rom. Tap the menu button, and tap "Apply changes", when done we are finished with the partition setup.
Getting Necessary Files:
You'll need to dump your boot.img, so you can switch between the ROMS(Google is your friend.). Download the ROM you want to use as the second(Has to be CWM flashable). Be sure this ROM has a boot.img included, if it doesn't, then take the boot.img you dumped, and put it into the root of the ROM. Next we need to get the proper GAPPS for the ROM we're installing (If it's a ROM that requires GAPPS.). Next we want to get a recovery, cwm, stock, etc. We need to get the recovery.img of the recovery we want to use, for cwm, you can just open the tar.md5 in WinRAR, and extract this file. Finally you need to download the attached Application I've created especially to convert ROMs to run from the SD Card, it also modifies recovery.img to apply any changes to the SD card ROM, instead of the Internal ROM. I haven't scanned it for viruses, but I don't think it should be a problem, of course you're free to check it if you like, in fact I encourage that you do.
Getting Important Info About Device:
We need to find out what block corresponds to what partition of the devices' internal ROM to input into the application, so it can replace them in the ROM. If your device is a Note 10.1(N8013) then you can skip this section, because the configuration file for that device is already in the attached archive. You need the block numbers for, System, Data, Cache, Boot, & Recovery(Ex: mmcblk0p1). If you can't find them on Google, then you can find it using adb. With the device connected, and with usb debbuging enabled. In cmd type "adb shell cat /proc/emmc", you should see a list of blocks(Ex: mmcblk0p1), with corresponding labels(Ex; /system). Take note of the blocks with the labels,System, Data, Cache, Boot, & Recovery, or similar. If typing "adb shell cat /proc/emmc" doesn't give you labels or doesn't show any information at all, then you'll need to find the labels for the blocks on google.
Using ROM 2 SD:
Extract "ROM-2SD.rar", copy the ROM you with to install into the "Original ROMs" folder, copy GAPPS into "GAPPS" folder(If ROM requires GAPPS) , & copy the "recovery.img" file into the "Recovery" folder. Run "ROM 2 SD.exe", check "Create modified recovery", don't check "Flash boot.img on install", check "Merge GAPPS" (If the ROM requires GAPPS, this will make sure GAPPS are installed when the rom is.). Click "Browse...", select rom from the menu. If you have the N8013 click the "Device:" drop down menu, and select "Note 10.1 (N8013)". If not type "mmcblk1" into "SD Mount:', and put the appropriate block into the corresponding text box. Click convert rom, click "Ok". Select GAPPS, and recovery when prompted to. when you get the prompt that its done, close the application.
Installing the ROM:
First, copy the unmodified/dumped boot.img to the EXTERNAL sd card. as bootStock.img. Next, copy the boot.img from the "Converted ROMs\[ROM_NAME]" folder to the EXTERNAL sdcard as bootSD.img. Now, copy the recovery.img from the "Converted ROMs\[ROM_NAME]" folder to the EXTERNAL sdcard as recoverySD.img. Finally, copy the unmodified recovery.img to the EXTERNAL sd card. BACKUP YOUR ROM BEORE GOING ANY FURTHER! Copy the converted ROM from "Converted ROMs\[ROM_NAME]\[ROM_NAME].zip" to the EXTERNAL sd card. Install the ROM as you usually would. After installing the ROM reboot, your device should boot into an unchanged Internal ROM, as if nothing has changed. Now we will create a script to boot into the newly installed ROM. Open notepad and copy the following(Replacing path to external sd, boot block, & recovery block.)
Code:
#!/system/bin/sh
#Flash boot
dd if=/path/to/extsd/bootSD.img of=/dev/block/[BOOT_BLOCK_HERE]
#Flash recovery
dd if=/path/to/extsd/recoverySD.img of=/dev/block/[RECOVERY_BLOCK_HERE]
reboot
Save the file as "Boot_SD.sh", and copy it to the EXTERNAL sd. Don't Run it yet, because it'll flash the recovery, we want to make sure the second ROM will boot first so you can use the recovery menu to fix it if not. Connect the device to the computer, open cmd, & type "adb shell", "su", "dd if=/path/to/extsd/bootSD.img of=/dev/block/[BOOT_BLOCK_HERE]", if that finishes successfully, then type "adb reboot". the device should reboot into the second ROM, if it does then the install was successful, and we can now proceed to create the Boot Stock script, path to external sd will be different on a custom ROM from the stock ROM:
Code:
#!/system/bin/sh
#Flash boot
dd if=/path/to/extsd/bootStock.img of=/dev/block/[BOOT_BLOCK_HERE]
#Flash recovery
dd if=/path/to/extsd/recoveryStock.img of=/dev/block/[RECOVERY_BLOCK_HERE]
reboot
Save as Boot_Stock.sh, copy to EXTERNAL sd. Then run the script as root using Root Browser, or whatever you usually run scripts with. The device should then reboot, if it doesn't then you probably need to search Google on how to root of adb. Once it reboots, I should boot back into the first ROM. You can now run the script we created first at any time to get back to the second ROM. We're almost done run the script to boot sd, then boot into recovery, the way you normally do. This recovery should only affect the Second ROM, to test this clear the davlik cache, & reboot into the ROM if it has to prepare a number of apps, then you know it works, and its safe to use the recovery, whenever you run a script the corresponding recovery will be flashed, so you can use the recovery on the second ROM, as you would on the stock ROM.
Notes:
Whenever you want to install an updated version of your ROM, you must run the ROM through ROM 2 SD, just like we did earlier. After you know this is compatible with your device, you can check "Flash boot.img on install" which will automatically flash the boot.img when you install the ROM. Don't forget to copy the converted boot.img to the external sd as bootSD.img, any time you install a new ROM/Update. GAPPS can be installed from recovery without modification, just make sure you do it when the recovery is on the second rom. Let me know of any bugs in my application, or with this tutorial, I will make the necessary changes ASAP.
​

Related

[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

[Complete Guide] What Is ClockworkMod And How To Use It

Schedule Post:
#1 - What Is ClockworkMod Recovery And How To Use It On Android
#2 - Nandroid Backup & Restore
#3 - Onandroid Backup
What Is ClockworkMod Recovery And How To Use It On Android
ClockworkMod – also known as Clockwork or 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 that aren’t possible with the stock recovery. In what follows, we will cover all that this recovery is capable of doing, and how to do it. We do not discuss about TWRP (TeamWin Recovery Project) in this thread.
1.All About Android Recovery
All Android devices ship with a recovery console that is basically a partition on the device’s internal memory and can be booted into. The stock recovery of almost all Android devices provides a few basic yet handy options that allow you to factory reset your device and also to recover its operating system using an official ROM in zip format, but that’s all you can do with it. That’s where a custom recovery comes handy.
A custom Android recovery basically replaces the stock recovery with one that lets you do all you can do with the stock recovery, plus a plethora of more options to give you a lot more control on your device. With a custom recovery, you can install official and unofficial ROMs as well as other updates including apps, themes, kernels etc. using zip files, wipe not just user data but pretty much every partition on your device, mount the storage card for USB mass storage access without leaving recovery, partition your SD card, wipe Dalvik cache and battery stats, fix permissions, perform, manage and restore backups and so on.
2.Introduction to ClockworkMod
ClockworkMod recovery is one of the most widely used custom Android recoveries that is available for most mainstream Android devices. It is the needed recovery for AOKP, AOSP, CM. ClockworkMod recovery has been developed by Koushik Dutta (also known as Koush) – the same guy who brought us the Android ROM Manager.
3.Booting into ClockworkMod
On most Android devices including ones by Samsung, you can enter recovery by powering your device off and then powering it back on while keeping either the Volume Up+Home+Power buttons pressed in the same time. This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
Tour
1. reboot system now
Reboot/restart your phone.
2. apply update from sdcard
This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. That is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option (and most of the options featured below) will bring up a rather annoying confirmation prompt but this has saved us on multiple occasions from a lot of trouble we would have been into due to accidental key presses. This is what we are talking about:
3. wipe data/factory reset
This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have setup (more on this later).
4. wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
5. install zip from sdcard
This option brings up the following sub-menu:
a. apply /sdcard/update.zip
This one is essentially the same as the ‘apply update from sdcard’ option of the main menu.
b. choose zip from sdcard
Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format. This is the most widely used option for installing a ROM that you have downloaded and copied to your SD card.
c. toggle signature verification
Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
d. toggle script asserts
Seldom-used option for a vast majority of users. It simply turns script asserts on or off. If you don’t know about these (we don’t), it’s best not to change this option.
e. +++++Go Back+++++
Takes you back to the main recovery menu, obviously!
6. backup and restore
Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a snapshot of your phone’s entire internal memory including all partitions, and save it on the SD card.
a. Backup
Takes a Nandroid backup, as explained above.
b. Restore
Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
c. Advanced Restore
This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions.
7. mounts and storage
Allows you to perform maintenance tasks on all the internal and external partitions of your android device
a. mount/unmount /system, /data, /cache, /sdcard or /sd-ext
These options let you toggle between mounting or unmounting these respective partitions. Most users don’t need to change these options.
b. format boot, system, data, cache, sdcard or sd-ext
These let you directly format any of these partitions. Take extreme care with this option as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device.
c. mount USB storage
Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
8. advanced
This section contains a few options most users will not require, though these can come handy quite often, especially wiping Dalvik cache, which is required before most ROM installations.
1. Reboot Recovery
Lets you directly and very conveniently reboot from recovery right back into recovery. This is useful option for certain back-to-back installations that require the device to at least boot once between them.
2. Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine (the custom-built Java virtual machine for Android).This is required before most ROM installations and at other occasions too, for fixing some problems.
3. Wipe Battery Stats
Wipes the saved battery usage statistics and effectively recalibrates the battery. Useful in various scenarios when Android isn’t showing correct battery levels.
4. Report Error
In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later report from Android using ROM Manager.
5. Key Test
Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
6. Partition SD Card
This option gives you a no-frills way to partition your SD card properly for use with ROMs that support data2ext (a very handy hack for low internal memory devices that enables an /sd-ext partition on the SD card to be used as the internal user data storage i.e. as the /data partition). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
7. Fix Permissions
Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force-Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.
4.Using ClockworkMod for ROM, kernel, apps, theme or mod installation
While in the complete feature tour we have already shown you how to install a ROM, kernel, app, theme or any similar mod from a recovery-flashable zip file using the recovery options, those of you who jumped straight to this section expecting to get just this information quickly are at the right place!
This guide is primary focused on a full feature tour of CWM but in our previously written guide on how to flash a ROM or app from a zip to an Android device file from recovery, we have already covered in detail how to use ClockworkMod for installing any ROM, kernel, app, theme or mod using a recovery-flashable zip file. While that guide is based on an older version of ClockworkMod recovery, everything in it still applies to the latest versions and should work flawlessly.
5.How To Install A ROM or App from zip file to Android device from recovery
Please note that the terms ‘installing’ and ‘flashing’ can be used interchangeably here and will mean the same thing.
Rooting your device renders its warranty void.
ALWAYS take backups before rooting or flashing a custom ROM or app to your phone.
Flashing a defective ROM or app to your phone might brick it so choose the ROMs and software that you flash wisely and never install a ROM or application from an untrusted source.
AddictiveTips will not be liable if your device gets damaged or bricked during the process.
Official ROM updates from device manufacturers or carriers are released in conveniently packaged installation files that you can run on your computer while your Android device is connected to it, and they automatically take care of updating your phone’s system. Similarly, most applications are available directly in the Android Market for easy installation, or come packaged as convenient ‘.apk’ files that you can just run on your Android phone to install. The case is not the same with most custom ROMs and several custom applications, which come in .zip files rather than PC installers or .apk files.
The idea of installing a customized operating system to their smartphone can be quite intimidating for inexperienced users. Though once they get used to it, some of them end up trying out different ROMs for their devices several times a day. While I don’t exactly recommend that you flash every new ROM that is made available for your Android phone, we are here to help you get over the fear of flashing a ROM that enhances the capabilities of your device so that you can use it to its fullest potential.
Here is a quick look at what we will be covering in this guide. Feel free to skip to the real deal if you already meet the prerequisites.
• Before We Begin: Battery Check
• Before We Begin: Unlocking the Bootloader (Stock Android Devices Only)
• Before We Begin: Rooting
• Before We Proceed: Installing a Custom Recovery
• The Real Deal: Installing a Custom ROM to your Phone
• The Real Deal: Installing an App From a Zip File to your Phone
There are certain steps that you might not require, and we shall be mentioning them in each section.
Before We Begin: Battery Check
Before you proceed with any of the following steps, make sure your phone’s battery level is not too low. It is recommended to have it at 50% or more. Do NOT take this lightly. If your phone’s battery runs out while you are attempting to flash a custom ROM, there is a significant chance of your phone getting bricked and becoming unusable PERMANENTLY.
Before We Begin:Unlocking the Bootloader (Stock Android Devices Only)
Note: This step applies only to Android devices with stock version of Android installed. At the moment, Google Nexus One and Nexus S are the only two such devices available. You may skip this step if you are using any other Android device.
Users of stock Android devices such as the Google Nexus One or Nexus S also need to unlock its bootloader before they can proceed. Once you have done this, you may proceed to the next step.
Before We Begin: Rooting
Note: You may skip this step if your device is already rooted, or if you already know how to root it.
Before you can install a custom ROM to your device, your phone needs to be rooted. Rooting is basically administrator or root level access required to perform administrative tasks on your Android device. Once you are done with the rooting process, you may proceed to the next step.
Before We Proceed: Installing A Custom Recovery
Note: You may skip this step if you already have a custom recovery installed on your device.
Rooting grants you the necessary access level to execute administrative tasks on your Android device but it is the recovery that provides the tools necessary to actually perform those tasks. While every Android device ships with a recovery, the stock recovery is quite limited in what it lets you do, and you need a custom recovery image to perform advanced operations on your device. Once you have a custom recovery installed on your phone, you will be ready to proceed to the next step.
The Real Deal: Installing a Custom ROM to your Phone
Now that you have a custom recovery installed on your phone, you can perform all sorts of wonderful advanced operations on your device and this includes the ability to flash a ROM or application from a zip file. The procedure is pretty standard for most ROMs, though there are certain ROMs which require additional steps for their installation. Since those steps differ from ROM to ROM, pay attention to instructions and this includes only the standard instructions here.
• Manually
1. Download the ROM from the link given in the article featuring that ROM. It should be a zip file.
2. Connect your phone to your computer via USB and mount its storage card.
3. Copy the downloaded ROM to the root of the storage card.
4. Power your phone off and reboot it into recovery. This will involve using a combination of your device’s hardware keys. Once in recovery, you can navigate its menu using the volume up and volume down hardware keys or your phone’s trackball / optical track pad if it comes equipped with one.
5. Use the ‘backup and restore’ feature of recovery to backup your existing ROM installation, software and data. This step is known as performing a nandroid backup. ALWAYS perform a backup before flashing a custom ROM, UNLESS you can afford to lose everything that’s on your phone at the moment.
Note: ALWAYS choose to perform the following steps 6, 7 and 8 UNLESS the ROM you are attempting to flash is an updated version of the same ROM that you are currently using, and is compatible with the current installation’s data. It is usually mentioned with the update whether you can install it over a previous version without wiping its data or not.
6. Get back to the main recovery menu and use the option ‘wipe data/factory reset’. You will be prompted to confirm this action. Select “Yes – Delete all user data”.
7. From the main recovery menu, select ‘wipe cache partition’. You will be prompted to confirm this action. Select ‘Yes – Wipe Cache’.
8. From the main recovery menu, enter the ‘advanced’ menu. From this menu, select ‘Wipe Dalvik Cache’. You will be prompted to confirm this action. Select ‘Yes – Format/System’.
9. From the main recovery menu, enter the ‘Mounts and Storage’ menu. From this menu, select ‘Format/System’. You will be prompted to confirm this action. Select ‘Yes – Wipe Dalvik Cache’.
10. Go back to the main recovery menu by pressing the back button and select the ‘Install zip from SD card’ option.
11. Select ‘choose zip from sdcard’ to get a list of the files and folders on your SD card. Scroll to the ROM’s file that you copied there in step 3, and select it. You will be prompted to confirm this action. Select ‘Yes – Install file_name.zip’ where file_name.zip is the name of the zip file that you are trying to install.
12. Wait patiently while the ROM is flashed to your phone via recovery.
13. Once the installation is complete, head back to the main recovery menu if you aren’t there, and select ‘reboot system now’. Your phone will now boot into the newly installed ROM.
The Real Deal: Installing an App From a Zip File to your Phone
While most apps for Android devices are available at the app store for direct download and installation or as .apk files for direct installation, there are certain apps which are only available as zip files installable from recovery. Their installation procedure is the same as installing a custom ROM that we just featured above. However, there are a few minute differences.
• When installing an app from a zip file, you do NOT need to perform the ‘wipe data/factory reset’ or ‘wipe/system’ step so NEVER do that unless you know what you are doing, have a complete backup and want to start using your ROM as a fresh installation with the new app added.
• You might or might not need to wipe the cache and the dalvik cache for installing apps from zip file. This varies from app to app and the developers of such apps as well as many reviewers including us mention when featuring an app whether it requires a cache and dalvik cache wipe or not. However, it never hurts to wipe these caches anyway, and it does not effect the data on your device or its storage card.
There you go, this concludes the guide on how to flash a ROM or app from a zip file to your Android device using a custom recovery. To try out the skills that you just learned, search our site for custom ROMs for your phone and start flashing, always remembering to take backups first!
Important note: This guide is retrieved from the VeNum Complete Guide with only few additions and corrections by me, so All thanks should go to him!
PS: If you see any error, please contact me to edit the OP.
Nandroid Backup - CWM
What is a Nandroid Backup?
It is a full backup of the partitions on your device’s NAND flash (NAND actually stands for NOT AND, which in simple terms means an electronic gate). Basically a backup of your phones hard drive if you will...
The Nandroid Backup is a snapshot of your device (it means everything on your phone – your apps, data, your current ROM and even the kernel is backed up) at the time you do the back up. If you restore the back up, it changes your phone BACK to that state. You will need custom recovery (CWM/TWRP). So make sure you have CWM or TWRP on your device.
The SD Card data is not backed up in the process. Although, the Nandroid Backup itself is created on your SD card. Make sure you have enough space on your SD card to make a COMPLETE copy of your phone.
It’s highly recommended that once you have done a backup, you manually copy it to your computer in case your sd card is wiped or corrupted.
Pre-requisites:
1. Rooted Device:
2. Custom Recovery (CWM or TWRP)
While the OS is running you cannot do a backup. The boot loader in the recovery enables you to take a backup of the OS while it’s not running.
How to Make a Nandroid Backup via CWM:
Backup via CWM:
1.Boot into Recovery pressing in the same time Volume Up + Home + Power buttons for our Galaxy S Advance phones
2. Select ‘Backup and Restore’ from the recovery.
Once you are in recovery, scroll down to the option ‘Backup and Recovery’ with volume Up/Down and select it (Power button for select).
3. Start the backup.
Once you are on the Nandroid screen, select ‘Backup’ to start the backup process. You have the option to ‘Restore’ backup on the same screen.
The backup process may take a while. Take a break for a coffee.
4. Transfer the backup to your computer (recommended).
Once you reboot, you can see the backup in the ‘clockworkmod/backup/…’ (or similar file) directory on your SD card.
Move, copy, or paste this folder on your PC safely.
Restore from a Nandroid Backup via CWM:
1. Boot your device into CWM and navigate to the Nandroid screen.
2. Choose ‘Restore’ and begin the process.
If you select ‘Advanced Restore’ option, you may select which part of the backup to restore – i. e. the boot,system, data or cache. Or choose the whole backup.
3. Reboot your device. Your system is now restored and is exactly the same as the time when the backup was taken.
Video guide (ignore phones from videos ) :
CWM guide
TWRP guide
[app] Online Nandroid Backup
Online Nandroid Backup - FULLY SUPPORTED with our Samsung S Advance GT I9070 (Janice)
Nandroid backups are usually performed in recovery mode. This means you would have to turn off your phone and reboot in recovery mode, which wastes a whole lot of time rebooting and a lot more time offline. With this tool you can do nandroid backups without switching off your device.
Requirements:
1. Rooted android phone
2. A terminal emulator installed on phone
3. Latest version of Busybox
4. A working CWM or TWRP
5. Patience
Features:
* Creates backups in the CMW 5 and 6 style or TWRP!
* Full support of the onandroid script.
* Create custom names for your backups.
* Choose what partitions get backed up.
The onandroid script was developed by Ameer Dawood. The original XDA post can be found at: http://forum.xda-developers.com/show....php?t=1620255
Important: This tool requires a rooted phone with busybox to work!
Download from market: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
Or from original thread: http://forum.xda-developers.com/showthread.php?t=1620255
Thank u so much
Sent from my GT-I9070 using Tapatalk 2
I have attached some printscreen of CWM for greater understanding of the console.
I have given you ownership of post #2 and 3 and moved all your material from your other thread [Guide] Nandroid Backup - backup & restore into post #2. You can edit that if you want, all I did was Copy/Paste.
Thread Stuck
Woody said:
I have given you ownership of post #2 and 3 and moved all your material from your other thread ...
Thread Stuck
Click to expand...
Click to collapse
Many thanks, Woody! :good:
R_a_z_v_a_n said:
Many thanks, Woody! :good:
Click to expand...
Click to collapse
Hey I have one suggestion. Instead of showing everything and giving the info a stretched out look, you should only show the headings and hide data using spoilers. That way people can read what they want to without too much scrolling!
Sent from my GT-I9070 using xda premium
this is a must-have for (almost) new users, thanks!
No blackouts in the guide. Tnx a lot
1 question, can i use your guides to translate it to spanish and place it in another forum?
Enviado desde mi GT-I9070 usando Tapatalk 2
Thnx
Thanks
xessus said:
No blackouts in the guide. Tnx a lot
1 question, can i use your guides to translate it to spanish and place it in another forum?
Enviado desde mi GT-I9070 usando Tapatalk 2
Click to expand...
Click to collapse
Your welcome but is not my guide. Read the first post and see the note about VeNom.
Sent from my GT-I9070 using xda premium
Thanks!!!
Brainiac.shri said:
Hey I have one suggestion....
Click to expand...
Click to collapse
Done that. Its ok or ...?
Any suggestions to make improvements is welcome. :good:
R_a_z_v_a_n said:
Done that. Its ok or ...?
Any suggestions to make improvements is welcome. :good:
Click to expand...
Click to collapse
right on bro its perfect now
we can do back up and restore by using shaan's temporary CWM right?..
with stock rom and kernel?..
just to make sure..
jaycm1130 said:
we can do back up and restore by using shaan's temporary CWM right?..
with stock rom and kernel?..
just to make sure..
Click to expand...
Click to collapse
YES 101%
Thanks
Thanks for the info, was very helpful!
I also thank you, but dont use QUOTE for all original post.
So for TWRP, click on Backup to make a NAND Backup! ??/

[TUTORIAL][GUIDE][HOW TO] Root Alcatel One Touch Pop S3 5050 | Every Android version

Hi everyone,​I have been in possession of an Alcatel One Touch Pop S3 5050 for quite a long time and was not able to root it until recently.
I will share my method in this topic but first of all, I have to thanks Decker.Kaluga for developing a custom CWM recovery image that kind of work on this device. You can find a good tutorial on how to install CWM on OT-6036Y or OT-6050Y on his website.
My second thanks goes to morgs640 for the idea of adapting Decker's work on Alcatel Pop S3.​
This method may work with other Alcatel devices, see last question in the FAQ section for more informations.
This method should not arm your device but as any root operation, there is always a risk. I am not responsible if anything goes wrong.
Click to expand...
Click to collapse
Step One
- Download Decker's custom CWM recovery here: cwm_alcatel_6050y.7z
- Unzip it
- Install adb drivers
Step Two
- Download latest zip version of Supersu from Chainfire, currently the 2.46
- Rename the archive as update.zip
- Put this file in the CWM recovery folder
Step Three
- Connect the device in USB, activate debug option and make sure adb is working by going to the folder where you have unziped the custom recovery
Code:
adb devices
- Navigate inside the device memory to identify the location of the internal and external memory:
Code:
adb shell ls /storage/
For internal memory, it should be:
Code:
/storage/sdcard0
And for external memory (sdcard):
Code:
/storage/sdcard1
- Push the Supersu zip file to external memory
Code:
adb push update.zip /storage/sdcard1/
- Take note of the position of the update.zip file inside the external memory
Code:
adb shell ls /storage/sdcard1/
In my case, this command returns:
Code:
- Android
- DCIM
- Documents
- Download
- LOST.DIR
- Pictures
- Ringtones
- data
- media
- update.zip
My update.zip file is in 10th position.​
Step Four
- Reboot the device in fasboot by pressing Volume Down and Power until logo Alcatel pop S3 appears
- Verify the device is connected:
Code:
fastboot -i 0x1bbb devices
Boot the device with the custom recovery:
Code:
fastboot -i 0x1bbb boot cwm_recovery_6050y.img
NOTE: This does not install the custom recovery on the phone so pressing Power during 5 seconds will reboot the phone normally.
The screen will turn white, wait until it stabilizes.
The screen will remain white as the recovery is not specially developed for this device but it should work anyway.​
Step Five
This is the tricky part, the menu does not display but the recovery is running anyway.
The menu you are not seeing is the following:
Code:
> reboot system now
> install zip
> wipe data/factory reset
> wipe cache partition
> backup and restore
> mounts and storage
> advanced
By default the cursor is on the first option.
- Press Volume Down once then Power to enter the install zip option.
This menu will be opened:
Code:
> choose zip from /sdcard
> choose zip from /storage/sdcard1
> choose zip from last install folder
> install zip from sideload
> toggle signature verification
+++++Go Back+++++
- Press Volume Down once then Power to enter the choose zip from /storage/sdcard1 option.
This will open the external memory folder:
In my case:
Code:
Android
DCIM
Documents
Download
LOST.DIR
Pictures
Ringtones
data
media
update.zip
- As you know exactly the position of the update.zip file from Step Three, press Volume Down accordingly.
In my case, 9 times to go from Android folder to update.zip​- Then press Power
It will prompt for a confirmation:
Code:
> No
> Yes - install update.zip
- Press Volume Down once then Power to install.
- Finally, Press Power one more time to confirm installation, then reboot manually the device by pressing Power during 5 seconds.
If the process has been successful, when rebooting it will display a text saying that the list of application is being updated.
--------------------------------------------------------------------------------------------​
Edit:
As neileverett suggested, the external memory sdcard could be recognized as sdcard0 instead of sdcard1.
To determine how the sdcard is named by the system, I recommend to use a browser as ES File Explorer or Astro Manager to write down all the content of the external memory and compare this list to the result of the ls command from Step Three.
--------------------------------------------------------------------------------------------​
FAQ
Q: My device never connect in adb.
A: First verify that adb drivers are installed.
In my case when I connect the phone, it first emulates a CD player device with a folder containing the generic drivers.
I have to safely remove this emulated CD first (right click on the System Tray icon -> remove device) before the phone accepts to connect itself with MTP or ADB.
Q: I do not have a sdcard.
A: You can try to do the process with internal memory.
First, you will need to navigate the memory with adb shell to find Internal memory
Code:
adb shell
Code:
shell#ls /storage/
shell#ls /mnt/
...
Some examples of the possible location of the internal memory
Code:
/storage/emulated/
/storage/sdcard0
/mnt/shell/emulated/0/
etc.
Sometimes, you get a menu like this prior the actual content of the sdcard0 (internal memory)
Code:
/0/
/legacy/
/obb/
After entering in /0/ or in /legacy/ you should get the actual content of the memory.​- Then push update.zip to internal memory
Code:
adb push update.zip $INTERNAL_MEMORY_LOCATION
- In Step FIVE, while in the second menu, choose choose zip from /sdcard by directly pressing Power
From a system point of view, it can open /storage/emulated/ or /mnt/shell/emulated/ that means the folder opened will not be the Internal Memory but a parent folder.
I recommend that you try every possibility by:
- First considering that pressing choose zip from /sdcard led you to the actual Internal Memory content and you shall proceed as normally by looking for update.zip in the current folder.
If it did not work:
- Consider that a parent folder is displayed and the actual memory is in the first sub folder
- Press Power to enter the first sub folder (which may be the Internal Memory) and try to install update.zip​- Consider that a parent folder is displayed and the actual memory is in the second sub folder
- Press Volume Down then Power to enter the second sub folder (which may be the Internal Memory)​- ...
After each try, reboot and look for the pop-up saying that the list of application is being updated.
You can go on with up to 2 levels of sub folders.​
Q: I tried everything, it still do not work.
A: If you have a lot of folders and files in the Memory, the list of content on the CWM recovery will be displayed on several pages.
Make a backup of the Memory, then empty it and add only the update.zip file.
Restart then from Step One.
It should be easier to find the update.zip file.
Q: I own a different Alcatel model, could this trick work with my device?
A: First you can try the other CWM Recovery image Deckter has developed: cwm_alcatel_6036y_v2.7z
To verify that the recovery is correctly booting on the device, when the white screen stabilizes, try to press Power twice.
If the recovery is working, it will enter in the first menu (reboot system now) then confirm the reboot.
In case, after this manipulation, the phone does not reboot, it means the recovery is not working for your device.
(Credits @Decker.Kaluga)
(Credits @morgs640)
(Credits @ModernWorld)
I have just successfully used this method to root my Pop S3 - thanks for the method!
One thing to note:
I found that the method didn't work initially, then with some digging realised that my sdcard was mounted as sdcard0 rather than sdcard 1. It turns out this is because I had changed the default install location under settings - storage to 'external sd card' rather than the default of 'phone storage'.
I temporarily changed this setting back to 'phone storage', and then your process worked first time! Might be worth adding this info to the post?
Thanks once again!
OMG !
So it works with the last update available ?
Possible to have a viewable recovery in the future ?
Draky50110 said:
OMG !
So it works with the last update available ?
Click to expand...
Click to collapse
This should work with any update
Draky50110 said:
Possible to have a viewable recovery in the future ?
Click to expand...
Click to collapse
Decker is willing to develop a CWM for Alcatel Pop S3 but does not possess the device. You can support it on his website. You'll find a link in the description of the Tuto.
Thanks
first thank you for the help. but my visit is to ask permission to make a video tutorial and so Decker.Kaluga to advertise can buy the pops3 and thus make the cwm for it.
negurras said:
first thank you for the help. but my visit is to ask permission to make a video tutorial and so Decker.Kaluga to advertise can buy the pops3 and thus make the cwm for it.
Click to expand...
Click to collapse
Of course, feel free to post the link.
I need help.
When I enter into the custom recovery, it displays a menu. First choose a language. Then a selection. It says:
Reboot system now
Apply update from ADB
Apply update from sdcard
wipe data/factory reset
wipe cache partition
Chose apply update from sd card, it only shows ../
I have a Alcatel pop s3. Please I really need help.
Did you put the update.zip into your SD card ?
DanIgnes said:
When I enter into the custom recovery, it displays a menu. First choose a language. Then a selection. It says:
Reboot system now
Apply update from ADB
Apply update from sdcard
wipe data/factory reset
wipe cache partition
Chose apply update from sd card, it only shows ../
I have a Alcatel pop s3. Please I really need help.
Click to expand...
Click to collapse
It's because you entered in the Alcatel Recovery mode not in Fastboot mode.
From Alcatel Recovery you can only install application signed by Alcatel.
Fastboot mode displays the Alcatel Pop s3 white logo on a black background (this is the first logo that appears when booting normally). Fastboot doesn't display anything else.
To enter Alactel Recovery it's: Power + Volume Up
To enter Fastboot it's: Power + Volume Down
You can also enter in Fastboot by entering the following while still in adb at the end of Step Three:
Code:
adb reboot fastboot
Once in Fastboot, go on with Step Four and so on.
Thanks for this
Any methods in sim unlocking? costum ROMs?
working recovery for 5050x
Hi! I ported recovery for 5050x. screen is work, you can install zip and backup you partitions.
1. extract
2. cmd to folder recovery
3. shutdown phone
4. press Power + vol- on phone it vibrate and connect phone to PC
5. type to run recovery
fastboot -i 0x1bbb boot recovery.img
or to flash recovery
fastboot -i 0x1bbb flash recovery recovery.img
i can't go in fastboot mode
I can not seem to come into fastboot mode POWER + Vol- and with code
Can somebody please make a video tutorial of this? I would love to root my One Touch Pop Icon.
Thank you good job
TWRP 2.6.3.0
amraouifathi said:
Thank you good job
Click to expand...
Click to collapse
You welcome
I ported TWRP 2.6.3.0, but I have not checked thoroughly.
Before backup you mast mount /system /custpack in Mount menu or you cant see backups in Restore menu.
All work good just the fast start don't work please upload the stock recovery
Stock recovery
amraouifathi said:
All work good just the fast start don't work please upload the stock recovery
Click to expand...
Click to collapse
Stock_recovery
Oh thank you i try now lol you are very fast
update TWRP 2.6.3.0
TWRP 2.6.3.0
+system and custpack backup and wipe like one partition
+you can backup persist и firmware
The stock work now i test the twrp

for G6-L11 LTE - modded B370 ( apps to sd card, can flash several recoverys )

29-03-2016
For Huawei Ascend G6 L11 LTE
Hi!
This is the ROM i have in my phone, it was changed by me and for now everything is working fine.
If you want default tutorial go here :
>>>DEFAULT TUTORIAL:
https://www.facebook.com/Huawei.Ascend.G6.L11.Kit.kat.B370/posts/1427876034188089.
My version still Kit kat B370 but edited by me, is a backup from my phone.
Please read all to understand and see what you need to do and how to do it.
This Version is diferent because if you have a ext4 partition in your external sd card it will install the apps there automatically!!!
Advantage of this? you will have a huge store space for the apps!!!
If not it will work like default ROM.
To create a primary ext4 partition in sd card with the size you want, you can use mini partition tool (for windows OS ).
http://www.partitionwizard.com/free-partition-manager.html
You can create the partition after flash but you CAN´T activate your Google account or install anything else, before your reboot the phone with the partition inside sd card.
Now, if you are using it default than you create the partition and reboot, the phone don´t delete the apps but will shutdown that apps creating errors...
To use it with sd card ext4 partition is better to start from factory reset with the partition already created in sd card!
This video shows how this ROM works with a external ext4 partition in sd card what means that all apps go to sd card and let internal storage free:
https://youtu.be/7st6838_aAg
It have Rashr from XDA, it is a app that easly can change/flash your recovery and some other things.
When you flash this ROM it will create in your sd card a folder called recoverys, inside you will find TWRP ( modde by me to ) and the default recovery.
How to use it? Open Rashr, give root permissions, selecte recovery, search in explorer for sdcard1, open recoverys folder choose the one you want and flash it! Is that simple.
>>>>>This Rom have:
-Rashr from XDA, its a flash tool to use in phone
-Custom bootanimation and shutdown animation
- One Hand UI ( helps to write in keyboard with one hand, you can find in shortcuts bar )
- Root
- Root tools (Root Browser, ES File Explorer, build.prop editor, etc...)
-Same cosmetic changes ( battery icon, signal reciver and wifi icons edited)
-Swap
- Governor set to performance
-Low cpu frequencie set to minimum ( 300000 )
- RAM tweaks
- Entropy tweaked ( https://en.wikipedia.org/wiki/Entropy_(computing) )
-Google Play updated
-Huawei backup app update
-Huawei File manager Update
-Only basic Google apps
-The Icons order was changed
-P8 Theme manager
- More options in Storage folder
- The sdext4 shortcut is to your external ext4 partition IF you have it in sd card, if not, is a regular folder.
And same other things...
I hope you enjoy it.
ADVISE!
Always do backup from the ROM you have in your device.
If you have root you can use this tool, it have a backup option.
G6Sknife for windows OS
https://mega.nz/#!WgoVWLjQ
Key:
!YV1JLOGvXX4rvYreDXP1Twwh-V5O65NjmMxBH_7unUI
My device is working properly without any problem so far, some times bugs only be noticed with use and i will update this post with the ROM fixed.
Install it by your own free will, I am not responsible for any damage that may appear in the device.
This is a European ROM but, like the default one, there are same country restrictions in providers that may affect the 4G reception, etc, etc.
If you want to install, you can try to unlock these restrictions since the ROM has root.
>>>>> FIX CUST, CHANGE PROVIDER AFTER INSTALL THE ROM<<<<
This ROM was edited to vodafone pt but can be changed to your provider.
When you flash it, if you are not from Portuguese Vodafone it will show a bootanimation that say " Change Cust after settings than do a factory reset ".
This is how to fix it with Root Browser, that you can find in ROM, go to folder /DATA and seek the custom.bin file, open it as a text file, you will see something such as example zt/rt, now we left the folder /DATA and go to the folder /CUST , we open it and we will find a folder with the name vodafone, we will change the name of it to the first name that we saw in custom.bin in our example will is zt, use small font, now we entered the zt folder and we will find another folder that his name is pt, let's switch to the second name of our exemple which will be rt, use small font!
Go back and exit the app, do a factory reset. Done!
.
.
>>>HOW TO INSTALL ROM.
Do backup from your data/apps with the default backup app from the phone to restore after install it.
->You need bootloader unlocked, search in this page to how to do it ( http://forum.xda-developers.com/ascend-g6/general/huawei-ascend-g4-4g-l-11-instant-t3190617/page2 ) , and need TWRP recovery FROM THIS POST, to install TWRP boot in bootloader ( fastboot - turn off the phone, press vol - and power, release power on boot than vol when you see the fastboot screen, must say in red unlocked) and execute this file to install TWRP recovery:
TWRP2d.exe
https://mega.nz/#!T9pygRAC
KEY:
!qVujE5A7RrQeQ1dqFFuRGYtUvBLWo-PfrEAGr6QoGsI
To install ROM, copy the zip file bellow ( ROM ) to sd card, turn off the phone, press vol + and power at same time, release the power on boot than vol + when you see the blue screen from TWRP, go to install and search for the zip, than swipe to install! Done. The ROM will install the default recovery again, if you want to stay with TWRP you must flash it again.
----->Before ROM flash, IF YOU WANT to win 2205MB more for apps and user data flash this zip file with TWRP like it was a ROM, you can read the steps in the end of flash, but i will write bellow. For you understand when you see "Insufficient storage available" is not the storage where music or pictures go, that is like a sdcard, is data partition storage. What this zip do? This will take from that storage where music and pictures go to give to data partition storage. Why this is good? Every one have a external sd card for pictures and music, i think and this will let to to install more apps in phone!!!
ADVISE: This do a factory reset!!
https://mega.nz/#!OgRzmDiK
KEY:
!zPrLPGzJPQOM1eTxX_L3SX1qiUyCs7ewkx-Fz77yM3U
->After zip Flash DON´T GO OUT FROM TWRP!
Go to main menu -> WIPE ->Advanced Wipe ->Select data -> go to repair or change file system -> change file system ->EXT4 Swipe to Change -> Now you can reboot.
.
-> My ROM have a swap ON ( https://en.wikipedia.org/wiki/Paging#SWAP-SPACE ).
Before flash see this video it shows a basic Flash with out changing the partitions size and with out a external ext4 partition and don´t show to how to change cust because it is already set to my provider.
It shows the flash from B118 than to Huawei_Ascend_B370_LTE_BB ROM:
https://youtu.be/duF3kWSpgsI
|
|
|
V
Now the ROM!
29-03-2016!
Huawei_Ascend_B370_LTE_BB.zip
https://mega.nz/#!ys4D3TYa
KEY:
!7PmY_vzI-i7a2P4wR6f5g15capGSZxFqIvFgri30aPA
Note:
This "MAYBE" works in same L22, L33 but not dual SIM. Only testing you can know it. The Only issue for sure that will be is the home key but can be fix it with a simple app from google play.
You can try to use this app with this ROM, for now, if you want it.
Notes:
Tap Tap App is to use light sensor to unlock the phone, open Tap Tap app, Install, go to setup sensor, select "Unlock when removing the cover", unselect "Tap Tap unlocks the screen" ( G6 don´t have this option in kernel).
Busybox, is a tool to install several Linux tools to use with Android, like cmd in Windows... if i can say like this... You can use them with terminal emulator.
GPS Status helps with GPS, it gets faster, better if data is ON.
>>>Multi-action Home Button<<<
https://play.google.com/store/apps/details?id=com.home.button.bottom
https://youtu.be/gv2bEPloL6Y
flash error ( Failed )
Hi...
How are you..??
I have flash error...
Checking device...
This package is for device: msm8226; tis device is hwG6-L11...
What i can do it..??
Bricked my device. Flashed it successfully via TWRP and after the automatic reboot, nothing came back on not even the screen

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

Categories

Resources