[Complete Guide] What Is ClockworkMod And How To Use It - Galaxy S 4 Mini General

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 bootloader 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 S4 mini LTE/3G 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 S4 mini GT I9195/I9190/I9192
Online Nandroid - Supported Devices
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.
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

Reserved, for future.
I will complete with more info's and screenshots in few days.
Please, keep thread clean and don't post "Thanks".
Regards

I assume this guide was written for nexus devices because the nexus one and nexus s are mentionend and you wrote that the bootloader has to be unlocked (Which has to be done on most devices. Only Samsung(?) has unlocked bootloaders. You could add that unlocking wipes user data.)
The second thing is: Your phone doesnt have to be rooted to install a custom recovey. Either you flash a recovery with Odin (add this aswell) and wipe everything to install a custom rom or you the superuser app to root your stock firmware.
But excuse me if you weren't finished with the post

Did you read carrefully OP and the note from the end?
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!
Click to expand...
Click to collapse

Excellent guide, thank you!

R_a_z_v_a_n said:
Online Nandroid Backup - FULLY SUPPORTED with our Samsung S Advance GT I9070 (Janice)
Click to expand...
Click to collapse
Are you saying that the onandroid Partition Script for I9070 works perfectly fine with S4 Mini i9195?

impactor said:
Are you saying that the onandroid Partition Script for I9070 works perfectly fine with S4 Mini i9195?
Click to expand...
Click to collapse
Yep its fully supported, that post its copy/paste from my previous phone/thread. :highfive:
Edited my post, thanks for report.
Check here compatibilities:
Online Nandroid - Supported Devices

Nice really great information Thanks again:good:

Related

Flashing - Noob needs help

Hey,
I read a lot over the last months and am now willing to flash the overcome rom.
Situation:
- Euro Galaxy Tab (german, unbranded)
- Rooted (with z4root)
- Do not want to lose current configuration (backup?)
Step-by-Step:
- As I still use RFS file system, I need to convert first. Besides that, I need a CWM to flash overcome and a SD-Card for the auto-backup.
1. - Flash Modaco Kernel Full to convert file system and to get CWM (with Odin, activate repartition and select Kernel)
3. - Reboot in recovery (CWM) - backup and conversion will be done
2. - Wipe Data (in CWM)
3. - Install instructions from overcome:
INSTALL INSTRUCTIONS
BACKUP first! (The install script WILL wipe your data partition, but NOT your SD cards)
Copy ROM to SD Card.
Reboot into CWM
Choose Install zip from SD Card
Choose zip from SD Card
Install and reboot!
If you're system was not already ext4, on reboot enter recovery mode and the automatic conversion of your file system will happen
Click to expand...
Click to collapse
Is this the way to go? As I nowhere could find some really detailled instructions to flash this, I hope this is all right.
if u follow these instructions everything will work fine! good job on looking this up. i dont mind people asking questions but only after they TRIED finding the answers themselves. i have hope in people again.
You are definately on the right track, but for completeness sake, I have thrown together a tutorial for exactly what you are after. Check it out over here: http://forum.xda-developers.com/showthread.php?t=973402
I hope it is useful to you.

[MOD]OpenRecovery XT720 01 (2011-08-30) based on Androidiani

This is a modified OpenRecovery (Skrilaz_CZ) based on Androidiani Recovery (89luca89&Azhad) with some enhanced features for Milestone XT720.
Features:
Main OR menu streamlined
Most Androidiani menu options have been moved into OR > Other Utilities
Add ext3/4 support (thanks fjfalcon)
Added SD Card Utility (OR > SD Card Utility)
Added preference for display brightness in OR (OR > Settings > Brightness)
Added utility to reinstall orbootstrap (OR > "Other Utilities" > "Re-install orbootstrap")
New sh hijack binary will boot to fastboot bootloader if volume-down is held (OR > "Other Utilities" > "Re-install orbootstrap" to enable). This should be compatible with all ROMs and stock.
nandroid: removed ability to backup partitions that always fail (this means "Backup All" works now)
Fixed OR > "Wipe Dalvik Cache" bugs (previous OR/AOR don't clear them all)
Added OR > "Power Off" (helpful when phone is being stupid about charging)
Minor update to sdcard-info.txt output
XT720 basebands added (OR > Change Basebands)
Please note that although most Androidiani menu options have been included in the Other Utilities menu item, that does *not* mean I have tested them on XT720.
Installation:
Download link: http://www.multiupload.com/J8Q15SHP4S
Root the phone
Download OpenRecovery-XT720-01.zip (it contains /sdcard/OpenRecovery and /sdcard/OpenRecovery.zip)
Extract OpenRecovery-XT720-01.zip onto the SD card. This will create a /sdcard/OpenRecovery directory and an /sdcard/OpenRecovery.zip file.
Make sure you're not in USB access mode and install the bootstrap (using adb or Terminal):
Code:
su
cp /sdcard/OpenRecovery/orbootstrap/install_script.sh /tmp
chmod 755 /tmp/install_script.sh
/tmp/install_script.sh STR
Upgrading from OpenRecovery:
Download link: http://www.multiupload.com/J8Q15SHP4S
Make a nandroid and backup your sdcard
Download OpenRecovery-XT720-01.zip (it contains /sdcard/OpenRecovery and /sdcard/OpenRecovery.zip)
Rename the old /sdcard/OpenRecovery folder to /sdcard/OpenRecovery.bak
Extract OpenRecovery-XT720-01.zip onto the SD card. This will create a new /sdcard/OpenRecovery directory.
Optional: Move/copy all files from /sdcard/OpenRecovery.bak/updates to the new /sdcard/OpenRecovery/updates directory
Optional: Reboot into OR. Select "OR" > "Other Utilities" > "Re-install orbootstrap"
Github: https://github.com/Mioze7Ae/openrecovery_xt720
Thanks: skrilax_cz, 89luca89, Azhad, fjfalcon
Is this the same update that was posted in other topics?
No, it's not the same, its the next version. The biggest difference is this one merges Androidiani (the previous one was based on vanilla OpenRecovery). Maybe I should bold the new stuff.
Sorry about this but what does Reinstalling the Bootstrap mean? Don't we already use that for getting in the bootloader? Is it is it gets broken somehow?
Woodrube said:
Sorry about this but what does Reinstalling the Bootstrap mean? Don't we already use that for getting in the bootloader? Is it is it gets broken somehow?
Click to expand...
Click to collapse
If the bootloader gets broken, you won't be in OpenRecovery
Anyway, I see two reasons to use it. (1) to make 100% sure you can get back to OpenRecovery after you've flashed something experimental (say a Milestone A853 update-based ROM) or (2) you want to upgrade your bootstrap to the new version that lets you hold volume-down to boot directly into the fastboot bootloader. (i.e. in the new version volume-up==OpenRecovery, volume-down==fastboot)
Edit: that reminds me... I should make a version of the bootstrap that fixes volume-down to boot OR on Milestone XT720 running Motoroi 50R...
Mioze7Ae said:
If the bootloader gets broken, you won't be in OpenRecovery
Anyway, I see two reasons to use it. (1) to make 100% sure you can get back to OpenRecovery after you've flashed something experimental (say a Milestone A853 update-based ROM) or (2) you want to upgrade your bootstrap to the new version that lets you hold volume-down to boot directly into the fastboot bootloader. (i.e. in the new version volume-up==OpenRecovery, volume-down==fastboot)
Edit: that reminds me... I should make a version of the bootstrap that fixes volume-down to boot OR on Milestone XT720 running Motoroi 50R...
Click to expand...
Click to collapse
Very very nice... thx man
Ok so I may have run into a glitch. Hopefully it is just mine, but it has been awhile since I had updated many of the apps from the market and let me tell ya, there was a shopping list. Haha get it. Anyways, I updated them all and decided it has also been some time since I had made a backup as well.
So I went in and "tried" to make a backup of the usuals (system, data, cust, cache, cdrom and sd). I probably tried 3 or 4 times and it never backed anything up. I even deleted the openrecovery folder and re-unzipped and replaced it and tried maybe another 3 times. It would just hang on the system dumping part for 15+mins (which is way too long).
I rebooted and put the original MZor back in there (the one w/o all the AOR stuff in it-for reference). Booted into recovery and boom, made the full backup in normal time. I ran checks on sd and sd-ext several times throughout and never a problem.
Has anyone else encountered this? I had been using this since it first came out and some of the utilites and all worked fine, but now that I think of it, hadnt tried to make a back up until last night.
***Side question: Since the beginning when I first learned how to make a backup, I read that you should backup system, data, cust, cache, cdrom and sd(if neccessary). My question is why do we and does it matter if we back up the cust, cache and cdrom parts? Wouldn't these get repopulated anyways at first boot? Would everything work if we just restored system, data and sd (again if neccessary)
Woodrube said:
Ok so I may have run into a glitch. Hopefully it is just mine, but it has been awhile since I had updated many of the apps from the market and let me tell ya, there was a shopping list. Haha get it. Anyways, I updated them all and decided it has also been some time since I had made a backup as well.
So I went in and "tried" to make a backup of the usuals (system, data, cust, cache, cdrom and sd). I probably tried 3 or 4 times and it never backed anything up. I even deleted the openrecovery folder and re-unzipped and replaced it and tried maybe another 3 times. It would just hang on the system dumping part for 15+mins (which is way too long).
I rebooted and put the original MZor back in there (the one w/o all the AOR stuff in it-for reference). Booted into recovery and boom, made the full backup in normal time. I ran checks on sd and sd-ext several times throughout and never a problem.
Has anyone else encountered this? I had been using this since it first came out and some of the utilites and all worked fine, but now that I think of it, hadnt tried to make a back up until last night.
***Side question: Since the beginning when I first learned how to make a backup, I read that you should backup system, data, cust, cache, cdrom and sd(if neccessary). My question is why do we and does it matter if we back up the cust, cache and cdrom parts? Wouldn't these get repopulated anyways at first boot? Would everything work if we just restored system, data and sd (again if neccessary)
Click to expand...
Click to collapse
I don't backup cust or cdrom. I made a backup with Mz's new O.R. yesterday and good thing I backed up ext cause my XDA Special backup would not boot without it. Not much help for ya sorry bud Hope you get it worked out.
@Mioze7Ae
can you please compile a standalone APK installer version of the new open recovery for XT720?
after reading the instructions i noticed, it requires an existing open recovery already installed to apply the above updates
AllGamer said:
@Mioze7Ae
can you please compile a standalone APK installer version of the new open recovery for XT720?
after reading the instructions i noticed, it requires an existing open recovery already installed to apply the above updates
Click to expand...
Click to collapse
I tried but my re-compiled version of the OpenRecovery.apk just FC'd.
Thanks for this Mioze7Ae, this is really sweet!
Am I missing out something here? I don't seem to be able to get the additional OR menu to convert to EXT4. I flashed back to Singapore 2.1 and have rooted. Removed the previous Open Recovery folder but where do I get the OpenRecovery.apk? Do I use back the previous version?
You can use Dexter's OpenRecovery.apk to install Open Recovery & then follow Mioze7Ae's instructions in the OP to update it.
Not sure what effect it even has, but the set timezone seems to be backwards ... Selecting GMT-7 runs /bin/timezone.sh GMT+7 and selecting GMT+7 runs /bin/timezone.sh GMT-7
Hey guys, hope you can provide me with a clearer instruction. I have done exactly as per the instructions and now when I boot into recovery, I don't see the extra option to convert to EXT4. The only things I see in the menu is:
Motorola MILESTONE XT720 Open Recovery
Version 1.46
Created by Skrilax_CZ
Use Volume Up/Down to highlight:
Camera_Mode key to select.
Main Menu
Reboot Menu
Settings
USB Mass Storage Mode
Nandroid
Application Menu
Run Script
Apply Update
Wipe Dalvik Cache
Wipe Data / Factory Reset
Wipe Cache Partition
What am I doing wrong? The phone is still running 2.1 update 1 but it's rooted.
It looks like you're running the original OpenRecovery. You need to replace the OpenRecovery folder on the sdcard with the version from the OpenRecovery-XT720-01.zip.
I think I can see how the instructions about renaming might be confusing so I tweaked the phrasing a little bit.
Thanks for the reply Mioze7Ae but I followed exactly as your instructions. Here's what I've done:
-Flashed singapore_STR_U2_01.1E.0
-Rooted with SuperOneClick
-Extracted and transferred to SD the OpenRecovery folder, OpenRecovery.zip and the original OpenRecovery.apk file.
-Ran OpenRecovery.apk
-Install Recovery System. Install Sucess.
-Recovery Boot and that's where it boots into the old OR.
It's the same if I use the OpenRecovery folder provided by hellmonger in The XT720 XDA Special Final RC2 "Hellmonger Edition"
ranggie4 said:
Thanks for the reply Mioze7Ae but I followed exactly as your instructions. Here's what I've done:
-Flashed singapore_STR_U2_01.1E.0
-Rooted with SuperOneClick
-Extracted and transferred to SD the OpenRecovery folder, OpenRecovery.zip and the original OpenRecovery.apk file.
-Ran OpenRecovery.apk
-Install Recovery System. Install Sucess.
-Recovery Boot and that's where it boots into the old OR.
It's the same if I use the OpenRecovery folder provided by hellmonger in The XT720 XDA Special Final RC2 "Hellmonger Edition"
Click to expand...
Click to collapse
Change this:
Extracted and transferred to SD the OpenRecovery folder, OpenRecovery.zip and the original OpenRecovery.apk file.
Ran OpenRecovery.apk
Install Recovery System. Install Sucess.
To this:
Transferred to SD the the original OpenRecovery.apk file.
Ran OpenRecovery.apk
Install Recovery System. Install Sucess.
Extracted and transferred to SD the new OpenRecovery folder, OpenRecovery.zip
R-D said:
Not sure what effect it even has, but the set timezone seems to be backwards ... Selecting GMT-7 runs /bin/timezone.sh GMT+7 and selecting GMT+7 runs /bin/timezone.sh GMT-7
Click to expand...
Click to collapse
I think it only affects the naming of the nandroid directories, but I'll give it a look. Nice catch!
Thanks Mioze7Ae. The last instruction made it clear. It works now. Thank you so much!!!!!!!!
Mioze7Ae said:
I think it only affects the naming of the nandroid directories, but I'll give it a look. Nice catch!
Click to expand...
Click to collapse
it was like this in all the versions of open recovery...
+++++++++
Mioze, can you also add a wipe battery stats in your modified openrecovery? comes in handy when we flash a new rom or restore a nandroid so we dont have to use the battery calibrating app.

[Guide] Ultimate Nexus 4 Root Guide

Post One: Unlocking and Rooting
Post Two: Installing Roms / Kernels / Tweaks
Post Three: Panic Section / FAQ / Miscellaneous
Unlocking The Bootloader And Obtaining Root
*This part of the tutorial is geared towards Windows users. The MAC instructions are very similar, from what I understand. Install the package the same way. All ADB/Fastboot commands may need to start with "adb-mac" (no quotes) rather than "adb" (no quotes). Due to the vast amount of Linux distros available; instructions will vary for your device. Once ADB/Fastboot are set up all command will begin with "./adb" (no quotes) rather than "adb" (no quotes). Once ADB/Fastboot are set up; this guide is relevant to everyone.*
Time required:
20-40 minutes.
Setting up ADB for our device:
Download the AndroidSDK onto your computer.
Note: Google changes their mind every other week as to if this will be distributed as a .zip or an .exe. If you get an .zip file, simply extract the contents to your C:\ drive. For an .exe install it like you would any other program, but set the path directly to the C:\ drive when the installer asks.
Or...you can use this page to download the "ADB for Dummies AIO App."
This will automatically install ADB for you to your C:\ directory. It's very very simple this way.
If your platform-tools folder doesn't have a fastboot.exe, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder.
Now you have ADB installed! Congratulations.
Unlocking the Bootloader:
***NOTE***
This will perform a factory reset on your device. You will lose all applications. Even the data on your SD Card! I'd recommend making a Backup to your computer BEFORE performing this. There is a method for backing your data up, detailed HERE.
For the time being, there is a method available that will allow you to unlock your device (and root it) without losing your data.
For instructions, click HERE. Please note: this is a hack and isn't the "conventional" and "accepted" way of unlocking your bootloader on a nexus device. The wipe requirement is there for your safety, really, and I'm certain this will be patched in the upcoming releases.
Get the drivers:
Uninstall any previously attempted drivers if they don't work and move to the next.
Option One:
Navigate to the "Device Manager" (Control Panel > Device Manager) in Windows and Select the android device. Open the properties and select the "Install Driver" option. Pick the driver with "Install from disk." Ignore any warnings about the driver not being signed properly.
PDAnet's drivers may work if the above options don't. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
While that is downloading, on your Nexus 4: turn USB debugging on.
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Once the drivers are installed, navigate to the C:\android-sdk-windows\platform-tools folder on your computer.
Hold shift and right click. Select "Open Command Window Here."
Plug your phone into the computer. Now in this command window type:
Code:
adb reboot bootloader
(Hit Enter)
Your phone should now boot into a screen with a green android with his chest exposed.
Type this:
Code:
fastboot oem unlock
(Hit Enter)
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Driver with the newest date and install it. Now retry the code above.
Your phone will ask if you want to unlock it. Select "Yes" by using the volume keys and use power to select it.
Now, navigate to "Recovery Mode" with the volume keys. Use power to select.
A screen with another Android will pop up. Press Volume Up and Power at the same time.
Select Factory Reset. This process may take a few minutes. Be patient and let it work.
Once finished, select "Reboot."
Your phone is now unlocked!
Obtaining Root Access and Custom Recovery:
Turn on USB Debugging.
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Download the following:
SuperSU (CWM .zip)
CWM (Pick the version for your device)
Place the recovery-clockwork-VERSIONNUMBER-mako.img file into your C:\android-sdk-windows\platform-tools folder.
Put the SuperSU.zip on your phone.
Open another Command Prompt if it isn't still open. (Navigate to C:\android-sdk-windows\platform-tools and shift + right click. Select "Open Command Window Here.")
With your phone plugged in type:
Code:
adb reboot bootloader
(Hit Enter)
And wait for your phone to boot into the android again.
Now type:
Code:
fastboot flash recovery IMAGENAME.img
(Change the file name to the correct file name and Hit Enter)
Once that is finished: select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the SuperSU.zip that you transferred earlier and select "Yes" to installing.
Navigate back to "Reboot" and reboot your phone.
You're now rooted!
However, ClockworkMod Recovery won't continue to load after this.
To fix this, find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option.
If your recovery still doesn't stick around after a reboot, you have another couple options. Find a file explorer that allows root access, such as Root Explorer. Use this program to rename /system/etc/install-recovery.sh to /system/etc/install-recovery.bak. You'll need to mount the system as r/w to do this. Root Explorer provides a button at the top to do so.
Or, you can do this completely manually by firing up ADB again and running a few commands:
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
(Hit Enter)
Congratulations!
Your phone is now unlocked, rooted, and has a custom recovery!
Continue reading the next posts for info on getting custom roms, kernels, tweaks, and more!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Thanks:
Google, for making Android a reality.
VanillaTbone, for the ADB AIO app.
Efrant, for posting about a bootloader locking utility without USB.
ClockworkMod team, for being a part of making our phones as awesome as they are.
The assorted developers, who continue to push out amazing material for us to use.
The awesome community, for endlessly supporting both Android itself and its users.
Installing Custom Roms Kernels and Tweaks
All of the instructions below require your bootloader to be unlocked. Please follow the guide above and return here when you're done.
Backing Your Files Up:
Time required:
15-25 minutes.
Making a Nandroid
The first thing you're going to want to do is back up your phone's entire system. This is done by making a "nandroid."
To do this, boot into ClockworkMod Recovery. To accomplish this: Turn your phone off. Once it is completely off: hold both volume buttons and the power button until the Android with his chest exposed is displayed. Navigate to the "Recovery Mode" option and select "backup."
This will take some time. Be patient and let it finish. This process is important! You should always have a recent nandroid available on your device.
Backing Your Data Up
Install Titanium Backup from the market.
Open Titanium Backup. A Superuser request should pop up. Allow it. Note: if Titanium Backup then says it failed to obtain root access; press the menu button and select more>reload application.
Press menu>batch. Select "Backup all User Apps." Select all and "Run the Batch Operation."
Let the process complete. This may take quite some time: depending on how many applications you have installed.
You can now backup your Text Messages, Bookmarks, and WiFi addresses with Titanium Backup as well.
Press Menu>Backup Data To XML to do so.
Backing Your Contacts Up
Note: This process may or not be useful to you. The Google servers should automatically import any contacts you have stored back whenever you install a new rom. Also note that Facebook/Google+/etc contacts will need to be synced again through their respective applications.
Open the Contacts application.
Press the Menu button.
Select import/export.
Export to storage.
Installing A Rom (Or Kernel/Radios/Tweaks/Themes/etc.)
Time Required:
5-10 minutes.
Note:
Follow the guide above about backing your phone up before attempting!
This guide will also work for flashing kernels/radios/themes/tweaks/etc. Simply ignore the part about wiping data and wipe whatever the thread says you should. You only need to restore data after a rom install.
Find a Rom You'd Like To Try:
Nexus 4 Original Development
Nexus 4 Development
Download the rom you'd like to try on your device.
Most roms also require you to install "gapps" as well.
You can find the correct ones for the rom you're using in the rom thread.
Make sure the Rom and Gapps are on your SD card.
Now, open Google Wallet (if you have it installed) and press Options>Settings>Reset Google Wallet. This will prevent the "Secure Element" errors some users have experienced.
Boot into ClockworkMod Recovery by turning your device completely off. Hold volume up, volume down, and power until the green Android with the open chest is displayed. Navigate to "Recovery Mode" with the volume buttons and select using the power button.
Remember to have a recent nandroid before continuing!
Navigate to "wipe data/factory reset" and select it. Select "yes."
Wait for the process to complete. This may take some time. Be patient!
Once complete: Navigate to "Install Zip from SD card" and "Choose zip from SD card."
Find the rom's .zip and install it. Once that completes install any applicable gapps' .zip.
Select the "Reboot" option.
Congratulations! Your phone should now boot into the custom rom!
Follow the prompts to re-activate your phone.
Restoring Your Applications / Contacts / Nandroid
Time Required:
5-15 minutes.
Restoring Your Applicaions
Install Titanium Backup. Note: you may want the pro key. If you have it, you won't have to manually click "install" on each application. The process is completely automated. Open Titanium Backup (grant root access. If titanium says it failed to obtain root access, press menu>more>reload application). Press menu>batch>restore missing apps with data. Now, here you have a choice to make. Do you want a completely clean install? Select "app only" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). Do you want all of your application data (saved games/settings/etc)? Select "app+data" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). This MAY cause you problems or it may not. Personally, I often restore application data and seldom run into any trouble. If you do find that restoring data caused problems, follow the guide above to re-install your rom and restore without data. This process will take some time. Be patient (I'd suggest turning your screen off so the screen doesn't burn, but that's just me.) It will vibrate upon completion.
You can now restore your Text Messages, Bookmarks, and WiFi addresses if you backed them up by pressing Menu>Restore Data From XML.
Note:
Overclocking/CPU tweaking applications should never be restored with data. Simply deselect it from the list.
Facebook/Haxsync/Google+ may have problems restoring your contacts when installed through Titanium Backup. Simply uninstall and reinstall through the market (and be sure to log in and select to sync your contacts again).
Also, if you have NFC Task Launcher successfully launching Tasker tasks with your stickers: they may not immediately work.
Through my testing, it's as simple to fix as uninstalling NFC Task Launcher and Tasker. Restore Tasker first. Then restore NFC task launcher.
Restoring Your Contacts
If google fails to restore your contacts (not facebook/haxsync/google+/etc) you may import them manually if you backed them up.
Open the contacts application and press menu>import/export>import from storage.
Restoring A Nandroid
If your phone is acting funny or won't boot...restore a nandroid from a previous rom or working set-up.
You may also use a Nandroid to switch back to a previous rom if you decide you don't like the one you're on.
Do this by booting into ClockworkMod Recovery (hold volume up, volume down, and power while your phone is off and navigate to "Recovery Mode").
Simply select "restore" and find the most recent (or relevant) backup.
This process will take some time. Be patient and let it complete! Once done, select "Reboot."
Note:
Nandroids are stored in the "clockworkmod" folder on your SD card. They take up quite a bit of space. ALWAYS have at least one recent one on your SD card. However, since these are huge files: you may like to delete old ones to save space. You must delete backups by booting into CWM and navigating to Backup and Restore>Delete.
Important Notes About Restoration
I outline the method of using Titanium Backup above for a reason. Restoring system applications and data is the most common cause of problems on custom roms. For this reason, always ONLY restore "missing applications" from "user applications" that were backed up when restoring onto a new rom. Every time you restore system data or applications a narwhal sodomizes your favorite childhood cartoon. This is FACT.
Installing Alternate Custom Recoveries
If you find a custom recovery (such as the touch-recovery options) that came as a .img file:
Use these instructions to flash. Plug your phone into the computer. Open up ADB. Move the .img to the C:\android-sdk-windows\platform-tools folder.
Type the following:
Code:
adb reboot bootloader
(Hit Enter)
You can also manually boot to the bootloader by powering off and holding volume down, volume up, power buttons until the green Android with his chest exposed is displayed.
Then type:
Code:
fastboot flash recovery FILENAME.img
(Replace the file name with whatever the .img is called and Hit Enter).
Wait for the process to complete and reboot.
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu). Navigate to recovery and select it with the power button.
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Code:
adb push NAMEOFZIP.zip /sdcard/NAMEOFZIP.zip
(Hit enter)
You may have to reboot recovery to get the file to show up. Now follow the guide above for flashing a rom to get you booting again.
Did you install a tweak that modified only a file or two on your phone? (Find this out by opening the .zip and looking in the folders (ignore META-INF). Good news! We MAY be able to recover you completely. If this doesn't work...you'll have to follow another method.
Get your phone into fastboot (the boot-menu that allows you to select recovery/reboot/etc). Navigate to Recovery. Start up ADB. Pull the files that were modified out of the stock rom's .zip (using whatever tweak you were installing as reference to find what was changed) that you're on into the C:\android-sdk-windows\platform-tools folder. Now we're going to push these files onto your phone...replacing the tweaked ones and hopefully getting you booted again. Use this code, but change the values of the file name and where it should reside. This is only an example!
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
This will mount your system so you can write to it.
Code:
exit
(Hit Enter)
This should exit shell and allow the use of adb commands again. You may need to type it a couple of times (until the #_ changes back to the platform_tools> prompt).
Code:
adb push framework-res.apk /system/framework/framework-res.apk
(Press enter after each file that you need to replace).
Note: This last option probably won't work. I'd just skip over it unless you're absolutely adamant about restoring your current setup and want to try everything possible.
Q: I want my SDcard files from my phone...but I'm in a situation where I need to flash stock images! This will erase my SD content. What can I do to save it?
A: Do you have a custom recovery installed? If not, download a custom recovery from post one in this guide and flash it using those instructions. You'll need to be in a custom recovery in order to obtain ADB access without booting your phone. Boot into recovery (With phone turned off: hold Power and Volume+ and Volume- until the bootloader pops up and navigate to "Recovery"). Run the command:
Code:
adb pull /sdcard/ /SDCARD/
(Hit Enter)
This will put all of your files into a folder called "SDCARD" in your C:\ drive. Keep in mind that this will take a LONG time. Maybe a couple of hours.
To restore once you're booting again:
Move the "SDCARD" folder you created from your C:\ drive to the platform-tools folder. *Then input:
Code:
adb push SDCARD /sdcard/
(Hit Enter)
Q: How do I make an "ADB Backup?"
A: An ADB Backup will backup your phones data (applications and their settings). Follow the guide HERE about ADB Backups.
Q: My phone gets really sluggish and often turns off or reboots on its own.
A: Without knowing anything about your situation...I'd say you either have severely bad data somewhere or some bad kernel tweaks. Use the rom install guide above, paying close attention to the part about backing up and restoring if you haven't already. In the case of a kernel problem, you're likely undervolting too low. Restore the stock kernel values and see if your problems subside.
Q: My phone screen won't turn on! This requires a battery pull to fix.
A: This is called a "Black Screen of Death" or BSOD. This is generally due to using a hotplug governor (one that turns cores off with the screen off) or possibly undervolting your device too low. Change governors or up your slots a bit.
Q: My phone is doing really weird things. Regardless of kernel/rom and even if I don't restore any data at all! Either that or I simply cannot boot up! My phone is possessed no matter what I do!
Download the stock IMAGES for your device and extract the files using 7-zip. Move all of the extracted files to your platform-tools folder. Open the flash-all.sh file with a text editor. Copy and paste the commands (one by one) and wait for each process to complete for continuing.
FAQ
Roms/Kernels
Q: What is the best rom?
A: The "best" rom is a matter of opinion. Do you like a certain customization and can't live without it? Use a rom that has that option.
Q: What is the best rom for battery life?
A: Roms themselves really shouldn't impact your battery all that much. They can have an impact, but if you're really looking for better battery I'd suggest swapping kernels or tweaking yours.
Q: What is the best rom for stability?
A: All of the roms out are "stable." They may have options that don't work correctly, but generally: this is user error. If you follow my advice on installing a rom, you'll end up with MUCH fewer bugs.
Q: What is the best kernel?
A: The best kernel is a matter of opinion. Some users may love one, while others swear by another. Find one you like and tweak it accordingly.
Q: How do I tweak a kernel for better battery?
A: Generally, you'll want to either change your governor and or undervolt and or underclock your kernel. This is done either by using SetCPU or similar apps, or with an option in your rom (usually labeled "performance" or something similar). Take note: extremely high/low voltages may cause instability. Never "set at boot" until you've thoroughly tested the options you've set. Testing includes low strain (like turning your screen off for an hour) and high strain (like playing a game for an hour) scenarios. To be extra safe: run the values for a couple days before setting them at boot. Follow the users ideas in the kernel's threads for some guidelines. However, remember that not all values will play nicely with all phones.
Miscellaneous
Q: Why isn't Google Wallet working at [store]?
A: I'm not sure if it's a Google Wallet problem, or a problem with the terminal. But I personally struggle to find a terminal that consistently works in my area. Something that has generally worked for me is to open wallet and go to Options>Reset Google Wallet. You must then re-add any cards you had.
Q: Does my ass look good in these shorts?
A: Yes.
Neat Ideas / How to Show Off the Nexus 4
-Get some NFC stickers. Tagstand has them available.
You can use these to make your phone perform certain tasks when you touch the sticker. Use NFC Task Launcher to define the tasks. These are capable of doing simple things like muting your volume to the more complex like turning on Tasker tasks that do things like auto-reply to text messages while you're at work.
-Do you have any suggestions? Submit them below!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
ADB Backups:
SDcard backup:
Code:
adb pull /sdcard/ /sdcard/
(This will pull all of your sdcard contents to an "sdcard" folder in your C:\ directory)
Applications and their data:
Take note, that you'll need to be using CyanogenMod's method for setting up ADB to do this. The ADB AIO application installs an older SDK without this functionality. First, get your drivers installed (detailed in post one). Once you get ADB installed (post one), navigate to the C:\android-sdk-windows\platform-tools folder on your computer. Hold shift and right click. Select "Open Command Window Here."
Input this while your phone is turned on and USB Debugging is Enabled:
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Type this:
Code:
adb backup -apk -noshared -all -nosystem
(Hit Enter)
Your phone will ask for a password. Input one and remember it.
Once the process completes: continue with unlocking and rooting your phone.
Restoration:
Upon unlocking and rooting your phone: open up ADB again.
Enter this code:
Code:
adb restore backup.ab
(Hit Enter)
Input the password you saved to this file earlier, and wait for the restore to complete.
To restore your SDcard backup, first move the "sdcard" folder that was made in the backup process to your platform-tools folder.
Then run:
Code:
adb push sdcard /sdcard/
Do you have to install "ADB" ?
As far as like...clicking it and letting the windows installer install...no.
The exe file will read the commands in cmd without "installation."
Nice Work!
I've just added this guide to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
Great work!!! nice and clean reading!
Can this guide include information on how to re-lock bootloader and unroot the device? Does this informaiton exist?
I need to RMA my phone due to dead pixels and I want to make sure I dont have any issues with the warranty.
jayluke said:
Can this guide include information on how to re-lock bootloader and unroot the device? Does this informaiton exist?
I need to RMA my phone due to dead pixels and I want to make sure I dont have any issues with the warranty.
Click to expand...
Click to collapse
Post 3.
fastboot oem lock
Locks the device.
How long is the first boot, after unlocking the bootloader, supposed to take? Mine's sitting there for quite a while already. (I had a lot of stuff installed, but still, this is really long.)
EDIT: When rebooting the custom recovery, you have to say "yes" to the message it gives you, something about keeping some recovery. I had originally said no because I didn't flash it, I just booted it once.
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
Edit: Got an app to enable it... still not in the menu though.
wizshaw said:
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
Edit: Got an app to enable it... still not in the menu though.
Click to expand...
Click to collapse
Oh geeze!
I forgot.
Settings>about>version number I think...
Click 7 times to enable developer options.
Will update op soon.
Quick question: is there a reason the first post links to SuperSU version 0.98, when version 0.99 is the most recent? If version 0.99 has known issues with the Nexus 4, I don't want to use it on my device.
The 0.99 version came out after this guide was posted. I was offered to upgrade to the new version of supersu from 0.98 and so far no problem at all.
Does this work on the latest version of JB (4.2.1)?
When installing a new ROM it says to perform a factory reset through CWM, which will remove all apps and data but should keep all your pictures, videos, songs etc.
It doesn't mention to wipe the System partition as well. Is this not necessary when flashing ROMs on a Nexus?
Prior to owning the N4 I had the Galaxy S 2 and it was always stated in the OP instructions to wipe data/factory reset, wipe system, clear cache, clear dalvik and then flash ROM and Gapps.
However, I don't notice in any guides or instructions for N4 ROMS to wipe the system partition, just the data partition. Is there a reason for this or is it not necessary to wipe the system partition? Thanks. Great guide by the way.
Peace
thank u for ur effort
Chochiwpg said:
When installing a new ROM it says to perform a factory reset through CWM, which will remove all apps and data but should keep all your pictures, videos, songs etc.
It doesn't mention to wipe the System partition as well. Is this not necessary when flashing ROMs on a Nexus?
Prior to owning the N4 I had the Galaxy S 2 and it was always stated in the OP instructions to wipe data/factory reset, wipe system, clear cache, clear dalvik and then flash ROM and Gapps.
However, I don't notice in any guides or instructions for N4 ROMS to wipe the system partition, just the data partition. Is there a reason for this or is it not necessary to wipe the system partition? Thanks. Great guide by the way.
Peace
Click to expand...
Click to collapse
I actually have a question along these lines.
I just came from a LG G2X so things were different for me whenever I flashed ROM's/kernels. For one thing, I had an external sd card so whenever CWM made it's backups, they went to that automatically and I didn't have to worry about wiping since everything was on the external. This phone doesn't have an external so where do the backups go? From the looks of the new CWM 6.0.2.0, the backups (and blobs now apparently) go to /data/media/clockworkmod. Well I guess my question here is if you have to wipe /data for installing new ROM's, how would I restore a backup because they would have been deleted off the /data partition. I tried adb pulling /data/media/clockworkmod to my computer but it won't go. Don't know if it's because that partition is mounted while the phone is in use or what. I tried the mount/umount command that OP listed but it won't work for me. Don't want to flash ANYTHING on this phone until I know for a fact I can get to the backups that I'm creating.

HTC Desire 820 Root Easily

HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
If you would like to send me a bear my Paypal donation link
Source
will system changed after reboot ?
will system changed after reboot ?
I rooted my HTC Desire 820U mobile successfully
I rooted my mobile easily just following the steps posted in the below page they are perfect :good: and also i followed yours too.
Now i am waiting for Custom ROM in English and android lollipop 5.0 update.I attached some of my mobile screenshot after rooting.
guys i wiped system data, and its saying no OS installed
Penish said:
I rooted my mobile easily just following the steps posted in the below page they are perfect :good: and also i followed yours too.
Now i am waiting for Custom ROM in English and android lollipop 5.0 update.I attached some of my mobile screenshot after rooting.
Click to expand...
Click to collapse
please anyone send me OS backup or guide me to install Stock ROM back :crying:
To install a custom ROM(OS) on your HTC DESIRE 820
Lenin Reddy said:
please anyone send me OS backup or guide me to install Stock ROM back :crying:
Click to expand...
Click to collapse
To install a custom ROM on your HTC DESIRE 820, here’s a brief tutorial guide:
---------------------------------------------------------------------------------------
Step 1. You will need to first download the custom ROM you want to install. These ROMs come in a “zip” file format (so DO NOT UNZIP them) and usually 1 large file around 200MB to 1GB. Some ROMs may require you to install multiple files.
You can download these zip files straight to your phone or use your computer to download (as downloading on your computer may be more stable/effective/faster) then copy over to your phone’s storage.
Step 1. Once ROM zip files are downloaded/copied to your phone, get into TWRP RECOVERY MODE BY PRESSING volume down+power button together for about 3 seconds to enter bootloader menu.Choose “RECOVERY” using Volume Down key then hit Power button to enter TWRP recovery.
Before installing a ROM, you will want to do a “data wipe/factory reset” by hitting the “Wipe” button. This will erase all your settings, apps, and app data (but not personal photos/videos on your storage). I highly recommend using Titanium Backup app to backup your apps, SMS Backup & Restore app to backup your SMS text messages, and use an online service such as GMail or Facebook to backup your contacts. Most online service providers like GMail or Facebook offer built-in ability to auto backup/restore your contacts.
*Optional – You can try installing a custom ROM without wipe, but this is considered risky and dangerous as sometimes the ROM may not boot. You can make a backup ROM if you are going to try this route so you can restore easily. Also, this can keep your settings, apps, and app data without restoring them.
Step 2. Once wipe is done (or you have decided not to wipe but have backup ROM), simply use the “Install” option in main menu and find the ROM zip file you need to install. If there’s multiple files, simple install them one by one until you are done.
Step 3. Once done installing custom ROM, reboot and cross your fingers your phone will boot. If your phone boots within 5-10 minutes you should be good to go. If not, you can try re-installing ROM, especially if you did not wipe, try re-installing after wiping.
To copy ROM file into SD card:
-------------------------------------
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC DESIRE 820 to your computer with usb debugging enabled.
Then download fastboot.zip and unzip, you probably will find a new directory called fastboot under your Downloads directory.
Copy the ROM you want to install to the fastboot folder.
Open a command prompt then type:
cd Downloads\fastboot
adb push ROM.zip /sdcard/.
Replace ROM.zip with the ROM filename you copied earlier to fastboot folder.
This will copy your ROM to the internal storage so once it’s done, just use TWRP to install ROM.
To backup the ROM after installing:
----------------------------------------------
Backing up a ROM will backup everything on your phone including your settings, apps, app data, kernel, and the whole ROM. It will not backup your personal photos or videos stored in your internal storage but it will backup everything else.
This can be handy later down the road your HTC DESIRE 820 malfunctions. For example, if your phone stops booting for some reason (due to bad custom ROMs or apps), you can easily restore your phone to a previous state by restoring your ROM.
If you “still” haven’t made a backup ROM, I highly suggest you to follow this tutorial to make a backup ROM.
Step 1. Make sure “Fast boot” is checked OFF under Settings->Power.
Step 2. Power off your HTC DESIRE 820. Then hold down Volume Down and Power buttons together for about 3 seconds to enter bootloader menu.
Step 3. Choose “RECOVERY” using Volume Down key then hit Power button to enter TWRP recovery.
Step 4. Once inside TWRP recovery, you can easily choose “Backup” or “Restore” to backup or restore ROM, it’s that simple.
Step 5. If you are backing up ROM, make sure “Boot”, “Data”, and “System” are checked and swipe to start backup. Backup process should take about 5-10 minutes or longer depending on how many apps you’ve installed on your phone.
Backups are usually large between 1-5GB depending on how many apps you’ve installed. They are stored in your internal storage under TWRP/BACKUP directory. You can easily save space by moving these files to your computer and move them back to the same location when you need to restore your phone.
Step 6. When restoring ROM, you will find your backups organized by folders. You can name your folders while backing up otherwise they will be stored with the timestamp of the time you backed them up.
Download ROM file from HTC deire 820 android development forum they given your orginal ROM for installing.
About warranty
I want to know that if if i root my phone then i ll loose my phone warranty. . . .
because we work on softwere not in hardware. . .
so i jast want to knw so canyou plz tell me?????
jainam0932 said:
I want to know that if if i root my phone then i ll loose my phone warranty. . . .
because we work on softwere not in hardware. . .
so i jast want to knw so canyou plz tell me?????
Click to expand...
Click to collapse
It just the general rule of all companies to void warranty if the user root its device and same goes for HTC also, atleast in my country (India).
Do you have any rom for desire 820u dual sim?
Penish said:
To install a custom ROM on your HTC DESIRE 820, here’s a brief tutorial guide:
---------------------------------------------------------------------------------------
Step 1. You will need to first download the custom ROM you want to install. These ROMs come in a “zip” file format (so DO NOT UNZIP them) and usually 1 large file around 200MB to 1GB. Some ROMs may require you to install multiple files.
You can download these zip files straight to your phone or use your computer to download (as downloading on your computer may be more stable/effective/faster) then copy over to your phone’s storage.
Step 1. Once ROM zip files are downloaded/copied to your phone, get into TWRP RECOVERY MODE BY PRESSING volume down+power button together for about 3 seconds to enter bootloader menu.Choose “RECOVERY” using Volume Down key then hit Power button to enter TWRP recovery.
Before installing a ROM, you will want to do a “data wipe/factory reset” by hitting the “Wipe” button. This will erase all your settings, apps, and app data (but not personal photos/videos on your storage). I highly recommend using Titanium Backup app to backup your apps, SMS Backup & Restore app to backup your SMS text messages, and use an online service such as GMail or Facebook to backup your contacts. Most online service providers like GMail or Facebook offer built-in ability to auto backup/restore your contacts.
*Optional – You can try installing a custom ROM without wipe, but this is considered risky and dangerous as sometimes the ROM may not boot. You can make a backup ROM if you are going to try this route so you can restore easily. Also, this can keep your settings, apps, and app data without restoring them.
Step 2. Once wipe is done (or you have decided not to wipe but have backup ROM), simply use the “Install” option in main menu and find the ROM zip file you need to install. If there’s multiple files, simple install them one by one until you are done.
Step 3. Once done installing custom ROM, reboot and cross your fingers your phone will boot. If your phone boots within 5-10 minutes you should be good to go. If not, you can try re-installing ROM, especially if you did not wipe, try re-installing after wiping.
To copy ROM file into SD card:
-------------------------------------
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC DESIRE 820 to your computer with usb debugging enabled.
Then download fastboot.zip and unzip, you probably will find a new directory called fastboot under your Downloads directory.
Copy the ROM you want to install to the fastboot folder.
Open a command prompt then type:
cd Downloads\fastboot
adb push ROM.zip /sdcard/.
Replace ROM.zip with the ROM filename you copied earlier to fastboot folder.
This will copy your ROM to the internal storage so once it’s done, just use TWRP to install ROM.
To backup the ROM after installing:
----------------------------------------------
Backing up a ROM will backup everything on your phone including your settings, apps, app data, kernel, and the whole ROM. It will not backup your personal photos or videos stored in your internal storage but it will backup everything else.
This can be handy later down the road your HTC DESIRE 820 malfunctions. For example, if your phone stops booting for some reason (due to bad custom ROMs or apps), you can easily restore your phone to a previous state by restoring your ROM.
If you “still” haven’t made a backup ROM, I highly suggest you to follow this tutorial to make a backup ROM.
Step 1. Make sure “Fast boot” is checked OFF under Settings->Power.
Step 2. Power off your HTC DESIRE 820. Then hold down Volume Down and Power buttons together for about 3 seconds to enter bootloader menu.
Step 3. Choose “RECOVERY” using Volume Down key then hit Power button to enter TWRP recovery.
Step 4. Once inside TWRP recovery, you can easily choose “Backup” or “Restore” to backup or restore ROM, it’s that simple.
Step 5. If you are backing up ROM, make sure “Boot”, “Data”, and “System” are checked and swipe to start backup. Backup process should take about 5-10 minutes or longer depending on how many apps you’ve installed on your phone.
Backups are usually large between 1-5GB depending on how many apps you’ve installed. They are stored in your internal storage under TWRP/BACKUP directory. You can easily save space by moving these files to your computer and move them back to the same location when you need to restore your phone.
Step 6. When restoring ROM, you will find your backups organized by folders. You can name your folders while backing up otherwise they will be stored with the timestamp of the time you backed them up.
Download ROM file from HTC deire 820 android development forum they given your orginal ROM for installing.
Click to expand...
Click to collapse
##############################
Do you have any rom for desire 820u dual sim?
hi,
why my htc toolkit not found my phone? drivers are installed and i find my phone on windows 8 but toolkit not found it...thamks a lot
Desire 820s
Anyone managed to root the 820S? i cant seem to find the fastboot option in the settings or in recovery mode..
I dont find any custom ROM's available for the device currently its too early and we dont have any Dev trying to improve the STOCK ROM also... Not sure how your tutorial will help
Thanks for your Root Easily Tutorial i have successfully routed my phone
custom rom
I found a rom while searching in google however not able to acess it.anybody wanna try.here is the link
http://www.upgrade-lollipop.org/mp3-0/htc-desire-820-6636.html
I actually rooted booloper unlocked but cannot enter into the recovery anymore. Gives error
How to UN-Root the Device ??
hapticc said:
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
If you would like to send me a bear my Paypal donation link
Source
Click to expand...
Click to collapse
Unable to download twrp recovery.zip please help me..
Be carefull of links which state there is 5.0 available for our device
drsobhan -
Please refrain from using or downloading ROM or any other files from other websites. The website you listed did not look genuine.
- HTC should provide us the with an update and source code will be available
- Cynaogen or other third party would provide us with an update
- XDA senior developers can provide link
One CM launches the rom there could be other providers like MIUI etc... but till the time please refrain from such websites
Refer to the following side for all builds supported by CM
http://wiki.cyanogenmod.org/w/Unofficial_Ports
Nauju said:
Unable to download twrp recovery.zip please help me..
Click to expand...
Click to collapse
Wish I could but I am outstation in remote area with 2G connectivity... will upload somewhere else after returning in 3-4 days
Guys, do you have original stock recovery? Can someone post a dump of their stock recovery so I can flash it into my phone with TWRP? Cant update with OTA due to TWRP constantly booting after making an attempt to update my firmware.
---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------
A simple stock rom would also help
can anyone give me following files from stock!!
just pull them from stock.
adb pull system/build.prop
Click to expand...
Click to collapse
and
system dump
adb pull system/lib
Click to expand...
Click to collapse
adb pull system/vendor
Click to expand...
Click to collapse
i know this is off topic but i need it.
thank you
BTW some vietnamees guys make custom rom for this device
http://translate.google.co.in/trans...k-4-4-4-sense-6-0-tieng-viet.347/&prev=search
looks valid link of mediafire
htc 820q root
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?

Fool-proof, 100% squeaky clean oneplus 2 custom rom installation for max stability

​Welcome to a simple tutorial that will help OnePlus 2 (OP2) owners and possibly other device owners install custom ROMs in such a way that eliminates most, if not all possibility of system errors, resulting in the longest lasting and most stable custom ROM installations!
DISCLAIMER: Your Warranty was voided long before you were ever even ready to complete this tutorial.
Therefore, I am not responsible for a broken or bricked device, especially if your rage towards a bricked device caused you to throw your device into a wall. This tutorial is actually designed to reduce the amount of "Rage Quitting" on modifying your device.​
This Tutorial assumes you have already completed OEM Unlock, Root, installed TWRP or other Custom Recovery, and are basically ready to install a custom ROM on your OP2.
Before beginning, backup any files you may need, I upload mine to my Google Drive then download after completing the ROM install. You can also use Nandroid to backup your current system (optional as there are methods to restore even the most bricked OP2 that doesnt even have a working recovery or OS, trust me I have done it at least 5 times because I constantly try new ROMs and mods). There are three necessary prerequisite steps required to complete before using this method to install your custom ROM. These prerequisites are listed below:​
Prerequisite One: Ensure your OnePlus 2 has been FULLY updated on the stock Oxygen OS ROM before you install your TWRP or other Custom Recovery. If not, Return to factory ROM, Un-Root, and update until you cannot update any more, then return to this tutorial afterwards.
Prerequisite Two: Ensure your OnePlus 2 has the latest update of the TWRP or other Custom Recovery. The Latest TWRP for the OP2 can be found here: https://twrp.me/oneplus/oneplustwo.html
Prerequisite Three: Ensure your device can receive files via ADB PUSH while in custom recovery. To do this, reboot your phone into recovery, connect to PC, hold down the "Shift" key and while holding, right-click in a window containing a file you wish to transfer, and select "Open Windows PowerShell Here" or "Open Command Prompt Here". Use the command "adb push Lin15.zip /sdcard" (remove the quotes, "Lin15.zip" is an example file) to push the file onto your device. Then, if your custom recovery has a file explorer as TWRP does, use it to navigate to /sdcard and see if the file is there. Also, your windows should show a successful transfer and should say "Okay" underneath your command line. If unsuccessful, install OnePlus 2 Drivers along with Universal ADB drivers and then try again. If still unsuccessful, try TWRP 3.1.1-0 (Download Link Below 2 Paragraphs in Blue Text Section). If unsuccessful at this point, there is something wrong as Win 10 with OP2 Drivers, Universal ADB Drivers, and TWRP 3.1.1-0 is my exact setup.
There are many custom ROMs available for the OP2. The method for installing custom ROMs is generally the same, but can differ in certain ways. This method SHOULD work for your custom ROM, but is not guaranteed. If this method fails, then visit your custom ROM's development page, and follow their instructions instead.
In this Example, I will be installing the latest (at the time of writing) Lineage 15 Android Oreo 8.0 Third Alpha Build OS/ROM and will be including instructions for the proper installation of the A.R.I.S.E. Magnum Opus System Sound Mod (Based on Viper4Android). I will include links to downloads, but their main XDA page can be found here: https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 This installation will use the latest (at the time of writing) TWRP 3.1.1-0 Custom Recovery.
INSTALL TIME:​
Begin by rebooting into recovery. Under "Wipe" options, you will first want to format data, select the option and type "yes" when prompted to confirm the operation. Repeat this step once again to ensure a squeaky clean wipe.
Next, also under "Wipe" Options, select the "Advanced Wipe" Options. You will then select EVERY BOX (Yes, this includes Internal Storage and will wipe EVERY SINGLE FILE from your device, this is INTENTIONAL and is why you MUST have a device that can accept ADB PUSH files in recovery!). This will wipe every file from existence, completely. This is what allows such a stable, squeaky clean install, as not a single piece of evidence from any other ROM/OS will be left behind, leaving basically no chance for errors or conflicts during installation of new ROM. You will want to complete this step again to ensure a squeaky clean wipe.
Navigate to the TWRP Home/Start-Up Screen and connect your device to your PC (WARNING: DO NOT USE ADB SIDELOAD MODE!!! I HAVE NEVER, EVER HAD A SUCCESSFUL ROM INSTALL FROM SIDELOAD!!!). Simply leave the device at this screen, and do not touch it. At this point, if you do not have all the necessary files to install your custom ROM and mods, you will need to download them now. I ALWAYS recommend the "Pico" Gapps package if installed in a ROM (some ROMs include Gapps). The reason for this is because the Pico package includes the bare minimum to get Google Play Services and Google Play Store up and running. This eliminates unwanted Gapps and reduces the chance of installation conflicts. The golden rule is: The less you install in TWRP, the better. If you want more Gapps, then after setting up the phone at the end of the ROM install, just search for them in the Google Play Store, its how I get mine every time. In the case of Lineage 15, the list of downloads is below:
Lineage 15 OS/ROM: https://www.androidfilehost.com/?fid=961840155545594199 (Dev Page: https://forum.xda-developers.com/oneplus-2/development/rom-lineageos-15-0-t3668056)
Android Oreo 8.0 Pico Gapps Package: https://www.androidfilehost.com/?fid=817550096634796662
Super SU 2.82 Root Installer (Select the Flashable 2.82 ZIP file): http://www.supersu.com/download
BusyBox Flashable Zip Package (Large page with many tools, scroll down to find the BusyBox tool): https://forum.xda-developers.com/showthread.php?t=2239421
A.R.I.S.E. Magnum Opus System Sound Mod (Select the "ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip" Option): https://www.androidfilehost.com/?w=files&flid=176171
Once all necessary files are downloaded, give them their own folder inside Windows and rename all of them to something simple as shown here:
View attachment 4273530
(Lin15.zip, Gap.zip, SU.zip, Busy.zip, Arise.zip)
Ensure your device is in custom recovery at the home/startup screen and is plugged firmly into your PC. DO NOT navigate ANYWHERE inside custom recovery or touch the device.
Now we will ADB PUSH these fresh install ZIP files over to your device. Inside the window containing your downloaded ROM files, hold down the "Shift" key and while holding, right-click and select "Open Windows PowerShell Here" or "Open Command Prompt Here". To ADB PUSH files, simply type "adb push FILE.zip /sdcard" where "FILE" is the target file and "/sdcard" is the target destination. Correct capitalization of letters is IMPORTANT! My window looked like this when finished:
View attachment 4273532
(adb push Lin15.zip /sdcard, adb push Gap.zip /sdcard, adb push SU.zip /sdcard, adb push Busy.zip /sdcard, adb push Arise.zip /sdcard)
Your ROM files should now appear on your device at your target destination. Disconnect your device and use the Custom Recovery File Explorer to navigate to the destination to confirm. "/sdcard" is the easiest to use destination.
Now we will install ALL of the ROM files, back-to-back with NO REBOOTS, NO WIPES, NO OPERATIONS WHATSOEVER INBETWEEN INSTALLS, THIS IS EXTREMELY IMPORTANT!!! Navigate to the Custom Recovery "Install" Section and navigate to your destination for your files. Flash the ZIP files in this order EXACTLY: Lin15, Gap, SU, Busy, Arise.
The A.R.I.S.E. Instillation is an AROMA style installer. It is a HUGE Sound Mod suite containing many options. Select the sound mods you like, but there is a module that is REQUIRED and 4 others that are highly recommended, listed below:
CORE Module is REQUIRED!!! Uninstall MusicFX, Remove Deep_Buffer, Set SELinux to Permissive, and SD Card Permissions fix are all highly recommended no matter what the ROM or mods, just in case. If these problems do not exist, selecting the options will not change anything, so do not worry.
My personal A.R.I.S.E. install included the following modules and delivers absolutely AMAZING sound quality while keeping installed modules to a minimum (otherwise known as a "Lightweight" install): Core Module, Viper4Arise 2.5.0.5, Viper4Arise Profiles, Uninstall MusicFX, Remove Deep_Buffer, Set SELinux to Permissive, and SD Card Permissions Fix. Its a highly recommended package
ONLY AFTER ALL FILES HAVE BEEN INSTALLED, navigate to Custom Recovery "Wipe" section, select "Advanced Wipe" and then check the "Dalvik Cache" and "Cache" options, DO NOT SELECT ANYTHING ELSE OR YOU WILL NEED TO START COMPLETELY OVER, WIPE PHONE AND RE-ADB PUSH FILES TO ENSURE A SQUEAKY CLEAN INSTALL!!! Perform this step again to ensure a squeaky clean wipe.
YOU ARE NOW FINISHED WITH A SQUEAKY CLEAN ROM INSTALL BUT THERE ARE A FEW MORE RECOMMENDED STEPS!
Recommended: DO NOT immediately reboot into system after install. Instead, navigate to Custom Recovery "Reboot" Section and select "Power Off" Instead. Once device is off, plug into A/C Outlet charger (DO NOT USE A PC, DETECTION OF PC WILL CAUSE DEVICE TO BOOT), and allow to fully charge, then cool off. This will ensure that Battery Calibration is set to 100% upon Initial Boot
Initial Boot: Boot Device, Initial boot will take around 5-10 minutes. DO NOT TOUCH THE DEVICE DURING THIS TIME. When you see the startup screen, STILL DO NOT TOUCH THE DEVICE! Instead, allow device to sit and idle, allowing the ROM to "Settle" for a MINUMUM of 5 minutes, 10 is recommended. Then, BEFORE setting up the device, reboot and allow another 5 minutes of "settling".
Run through the Device Initial Setup. You will want to select any desired options now, and avoid having to search settings later. Once at Device Home Screen, immediately open app drawer and select SuperSU app. Inside SuperSU, navigate to settings and apply the following options:
Disable Re-Authentication, Default Access: Grant, Enable SU During Boot, Trust System User
These SuperSU options will allow mods to function with complete stability and no interference, leading to a smoother experience. After, completing this step, Reboot your phone and ENJOY YOUR NEW, ROCK-SOLID, STABLE ROM INSTALL!!!
Nice job bro thanks working here!
Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?
Why are people recommending using adb push to get the files on the phone.
I always just drag and drop them on the phone in windows explorer, never had any problems.
Only time I ever need adb is for flashing recovery.
shailinder said:
Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?
Click to expand...
Click to collapse
Now I tried it again and this time flashed busy box as well but the same error.
Screen shot for your reference. Is there another way to install it?
shailinder said:
Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?
Click to expand...
Click to collapse
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.
pops106 said:
Why are people recommending using adb push to get the files on the phone.
I always just drag and drop them on the phone in windows explorer, never had any problems.
Only time I ever need adb is for flashing recovery.
Click to expand...
Click to collapse
Well we all know performing this method of install is not a requirement for installing ROMs, but it is the most fool-proof method and ensures there are no file conflicts between old and new ROMs/OS's. I cannot even tell you how many times I have done quick, minimal work installs and end up with tons of errors, laggy or freezing screens at random times, force closing apps, busybox system link failures, the list goes on and on. After using the "Squeaky Clean" method, I can honestly say Lineage 15 is as stable as the Stock/Factory Oxygen OS.
wallacengineering said:
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.
Click to expand...
Click to collapse
Thanks. I got it install using a different method and it is working wonderfully.
wallacengineering said:
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.
Click to expand...
Click to collapse
Fair enough
And thanks to the opp for the thread
pops106 said:
Fair enough
And thanks to the opp for the thread
Click to expand...
Click to collapse
No problem, the thread was a random idea after accidentally stumbling across the fact that TWRP can accept ADB PUSH files. I honestly had no idea, and was stuck in a bootloop after a custom ROM failed to install correctly. I had no backup and was getting ready to just give up, enter Qualcomm Diagnostics Mode and perform the Oxygen OS Firmware/Software OEM install when I decided to reboot into Recovery and attempt SideLoad of a previous ROM that had worked.
This did not work, as sideload is apparently a dumb way of doing things. I never understood why sideload tries to install a file that is in the middle of transferring. Just seems like a flawed concept to me. Anyways the install was very slow, buggy and laggy, and when finished had installed such a corrupt system, due to installing a partially transferred file while it is being transfered and then sticking all the pieces together, was so unstable that more than a minute idling at the home screen or any attempt to open ANY app caused the phone to reboot.
Sideload is a worthless feature in my opinion and I will never use it for any operation ever again so long as I live. So all of a sudden I decide to plug the phone into my PC while in recovery and observe how Windows detects the phone when you turn Sideload mode on and off, as to try and troubleshoot my sideload to get an effective install (which by the way will never happen, to this day I have never had a sideload install work correctly), and noticed when I turned it off, the device still showed up as a recognized Android device under Windows Device Manager. Then, you may not believe me on this, but I did actually randomly decide that more than likely, it was interfaced on Universal ADB, and that it I typed "adb devices" into a windows command prompt, it should show, and it did. The rest is history.
I know the feature had been around for some time as I found out later on, but I had never seen any information about it anywhere on any thread, and even when I asked for ideas for troubleshooting, while XDA users helped for sure, I guess they just didnt have that idea, and gave me alternative routes as well such as the Qualcomm Diagnostics full OEM wipe method which I was already familiar with. This does show, however; that experimenting and troubleshooting on your own can be a great way to learn new things!
Hi, thank you for the post.
I am enjoying v4a bcoz of you only.
I got a query btw, can I install dolby & atmos along with v4Arise?
Please add a note for HaruhiOS
HaruhiOS checks if a clean flash is required before flashing and will abort to tell the user that a clean flash is necessary if ever. It is my design goal to avoid the need for clean flashing as much as possible
Due to this the user should avoid unnecessary clean flashing, which actually ruins performance and battery life and reduces device health when using my ROM
if already.....
hey,
if one would already go thus far to wipe internal storage as well, i'd say that it's making sense to format storage by changen from ext4 to ext2 and back to ext4. wiping is not always getting us rid of all residues while changing the file system and going back to the one we want/need does indeed reformat everything, this is a procedure that is useful once the storage card is corrupted.
magnamentis said:
hey,
if one would already go thus far to wipe internal storage as well, i'd say that it's making sense to format storage by changen from ext4 to ext2 and back to ext4. wiping is not always getting us rid of all residues while changing the file system and going back to the one we want/need does indeed reformat everything, this is a procedure that is useful once the storage card is corrupted.
Click to expand...
Click to collapse
Apparently e2fsck and fsck.f2fs is too hard
Once the storage card is corrupt no formatting will help you anyways
Just stop believing in dumb stuff. If you have to clean flash every other build a ROM developer releases they messed up big time and they should fix their code

Categories

Resources