Related
Your a noob and need help then dont worry this guide will help you
ALWAYS UPDATING(STILL NOT COMPLETE)
Android Dictionary
If you're new to Android, you are likely seeing a lot of unfamiliar words being thrown about... from CID to RUU to ROM. This dictionary will help you understand what these words actually mean, and when you would expect to see them.
ADB
ADB (Android Debug Bridge) is a PC command-line tool included with the Google Android SDK. ADB provides an interface for managing and debugging a USB connected Android device. Common ADB tasks include: *Collecting a log via logcat* Installing APK packages* Pushing or pulling files* Accessing the device shell.
For additional details about ADB please see the ADB guide.
APK
An APK is an Android application package (Android Package). It is commonly used to store an app, or program run on the device. These files are essentially zip files, in that they contain other files which make up the program. They can be obtained through various methods, such as installing an app through the market, downloading from a website, or creating yourself in Java. If you have an apk file on your computer, and wish to install it on your phone, you can run the command 'adb install apkname.apk' to copy the file over USB to your phone.
The APK files reside on the phone in the directory /data/app/filename.apk. This directory is not normally accessible unless a #root|rooted ROM is used on the phone, in order to protect paid-for applications. On a rooted ROM, it is possible to copy applications manually into this folder using the command 'adb push' or similar. Once a file is in the /data/app directory, it is installed on the phone. There is not normally an installation process for apps on Android.
It is also possible to install an app to the system partition of a rooted phone. This has the added benefit that the application cannot be uninstalled from the device, making it useful for security/anti-theft applications such as WaveSecure and MobileDefense. These [[#system]] applications are stored in /system/app. The applications in this folder are normally part of the Android operating system, and should not be modified or deleted unless you either put the file there yourself, or know what you are doing.
APK files can be uninstalled using the market application (if the application was installed from the market), the 'adb uninstall apkname.apk' command, the Settings | Applications | Manage Applications menu, or by manually removing the files from the /data/app directory as a last resort. Normally, the preferred method is through the market or applications menu.
Bart
Bart is used from Recovery to backup your phone or to restore a backup.This basically creates an exact copy of your phone (Sdcard + Sd-Ext excluded, unless it says it will backup SD-Ext), which later can be restored with no losses in data.
Boot
In contrast to other linux-based operating systems, Android has a boot partition (containing the contents of a boot.img file), as opposed to a direct booting system. This partition contains a read-only 'ramdisk', and a couple of other files. The ramdisk contains files critical to booting, such as init.rc and default.prop. This 'partition' actually sets up the directory structure of the device, having empty folders for /data, /dev, /proc, /sbin, /sys and /system.
Bootloader
The bootloader, or HBOOT, is firmware on the phone which runs on every startup.
Since the bootloader controls access to Fastboot, it can be desirable to change the version of the bootloader on a phone. The current version of the bootloader can be viewed by entering bootloader mode. To do so, turn on the phone with the back button held down. Release the back button after about 1 second. The version information will be displayed at the top of the screen next to the word HBOOT, and will appear in the form 'V1.76.0004' or similar.
From within the bootloader, Fastboot can be used to execute an img file stored on your PC or flash an img file to the device.
If your device has HBOOT version 1.73.007, it is no longer possible to use Fastboot, so it is often desirable to downgrade the HBOOT using the Goldcard method in order to get the 1.73.004 version, which is Security-Off, allowing Fastboot.
CID
The Carrier ID is a number embedded in your Phone's SPL that identifies what if your phone is a network branded Hero. For example, T-Mobile UK phones have a different CID to generic HTC phones. The CID prevents you from [[#Flash|flashing]] an 'incorrect' [[#RUU]] to your phone. Note that the RUUs will all function on any of the phones, but the CID locking prevents you from 'debranding' your phone by installing a generic [[#RUU]]. Additionally, the CID-related software also prevents you from installing an older RUU than what you are currently running.
It is possible to bypass the CID check on an [[#RUU]] using a [[#Goldcard]]. This pretends your phone has the 'Super-CID', which allows any branding of ROM to be installed, and allows you to downgrade the software on your phone.
Data
The data partition on the device contains the user-related data, such as installed applications and settings for those apps, as well as your SQLite database containing Android settings and messages. Normally, the directory /data/app is off-limits through the 'adb shell' command, as well as other terminal applications that can run on the device, since this directory contains the apk files for apps. On a rooted phone, using the [[#su]] command will allow full access to this partition. This partition can be flashed using Fastboot or Nandroid.
Ext
Ext is an abbreviation of the extended filesystem, one of the filesystems supported by Android and other Linux based systems. An ext filesystem partition is required for using Apps2SD or Dalvik2sd.
Fastboot
Fastboot is a means to execute or Flash an img file on your device. First, set up your PC for ADB, and ensure that it works correctly. After putting your phone into Bootloader mode, and selecting Fastboot by pressing back (if you let go of the back key early), the device awaits a command via USB.
On your computer, execute the command 'fastboot devices', which should display your device serial number. This confirms you are ready to use Fastboot. To execute (ie. run without changing your system) and img file, type the command 'fastboot boot imagename.img'. This command allows you to run a custom recovery image without flashing it to the device.
If you wish to flash an img file to the device, the command 'fastboot flash IMGTYPE imgtype.img' should be used. Note that IMGTYPE should be replaced by the type of img file you are flashing. For example, to flash a recovery image, the command 'fastboot flash recovery patched_recovery.img' should be used. The following are valid types of image to flash; boot, recovery, system,
Flash
Flashing is the process of writing data to the internal memory on your phone. Normally, you would flash a [[#ROM]] image to the phone, which would give you a different version of system software on your phone. Flashing can also refer to updating/writing to any of the other parts of the phone, such as the SPL, Radio etc.
Flash Memory
Flash memory, also known as NAND memory, is nonvolatile - keeping information even when the device is off. Flash memory in the device is equivalent to the hard drive in a computer. This is where the device's operating system (sometimes called firmware) and applications are stored. Flash memory is slower than RAM, but is (almost always) faster than SD cards.
Flashrec
Flashrec is an application/tool you use to flash the recovery image to your phone. (Found on http://zenthought.org/content/project/flashrec)All current firmwares are patched so you can not use flashrec on these, you will receive the error message "Could not run command"Most 1.5 (cupcake) firmwares can still use this, but some has been patched already.The current version is 1.1.3 and was updated 2009-08-16.Note: Do not flash cyanogen's theme templates after you have started the installed recovery image, this will brick your phone!
Goldcard
A goldcard is the name given to a specially modified microSD memory card for your phone that allows you to install software to your phone that is in an RUU file, but not from the same network provider as your phone is from. It does this by bypassing the CID check of the RUU update. Additionally, the goldcard allows you to install an earlier version of system software onto your phone than what is already on it (called downgrading). This can make it easier to root a phone and install a custom ROM on it, if the software installed on it at present cannot easily be rooted.
HBOOT
See Bootloader.
logcat
Using adb (see ADB), type in "adb logcat >logcat.txt". This will help us when resolving issues and bugs.There is also a tool in the market you can use for this, called aLogcat. It can show different categories (severity of errors ect.) too, adb logcat can not do this.
Market
The market on Android is a place where you can purchase or download applications for your phone in the [[#APK]] format. When you download through the market, the installation process is transparent (as in you don't have to deal with the APK files yourself), and there is the facility to rate apps and post comments which are visible to other users. Frequently, the developers of apps actually take onboard the feedback in the comments (mainly the smaller apps with slightly less feedback to sift through).
When an app is installed from the market, it is copied to '/data/app/apkname.apk', as the act of 'installing'. An app can store its data in the folder '/data/data/apkname'. It is possible to clear the data stored by an application by using the Manage Applications feature in Settings | Applications | Manage Applications.
Nand
See Flash Memory.
Nandroid
Nandroid is used to backup or restore backups from Recovery.You can chose to either do a regular backup (Phone only) or a backup + sd-ext (Phone + Apps2sd ext.)Both will backup your whole system, the second will include apps saved on your sdcard's sd-ext.
Radio
The Radio on a Hero is the part of the phone that deals with mobile connections. It handles talking to the GSM/3G network, Bluetooth, WiFi and GPS. The radio contains software that controls how it operates, and newer versions of radio firmware are made available from time to time in [[#RUU]] updates. These updates are transparent to the user, although users who elect to install custom software can update their radio using an update.zip file made available by members of the modding community.
Flashing the radio is potentially risky, and you should NEVER pull the battery out of a phone that is [[#Flash|flashing]] the radio. If you do so, it is possible your phone will be bricked. Nevertheless, it can give improved battery life, signal strength and data performance, so is often done by users moving to later versions of ROMs.
Care should be taken to only flash the correct type of radio to a phone. NEVER attempt to flash a CDMA phone with a GSM radio or vice-versa. It is likely you will brick the phone if you attempt to do so.
ROM
ROM is literally "read-only memory" but it's usage has changed over time. Today ROM can refer to the non-volatile area of a device's flash memory on which read-only data resides or the packed image to be written to that flash area.
Root
Root is the name of the highest level superuser (su) on Unix-like systems such as Android. The root user, and applications run by the root user, have administrative access to protected files and services which makes it dangerous for normal daily use.
A 'rooted' device one which has been hacked to provide privilege escalation from a standard user to superuser. Rooting a device is usually the first step in installing cooked ROMs.
RUU
An RUU is a ROM Upgrade Utility, which is a Windows executable (exe) file that upgrades the software on your phone. Using the USB connection with the phone, the RUU communicates with the phone's SPL, checking the CID of the device to ensure the user is not installing the ROM on a network branded device (since the networks release their own RRUs with customisations and branding). The RUU is capable of flashing almost everything on the phone, including System, Data, Recovery, HBOOT and Boot. As such, an RUU is a good way to return your phone to the way it came out the box if a warranty repair is needed (be aware that using a new RUU could make it difficult, or even prevent you from rooting the phone in future. It is normally better to upgrade using update.zip files to prevent this, as they do not update the HBOOT to prevent Fastboot in future.
S-OFF/S-ON
This refers to an unlocked/locked NAND drive. HTC lock the NAND on some phones to prevent writing to the /system. S-OFF can generally be obtained by an exploit, by flashing an engineering SPL, or by using an XTC Clip.
SPL
The Secondary Program Loader is a piece of bootcode that initiates the startup of the phone, displaying the initial splashscreen for the device, and loading the initial files from ROM.
It checks to see if a button combination is pressed on bootup (such as that to enter Recovery Mode or the bootloader ), and loads the relevant system software. If no special instruction is given by holding keys, the bootloader loads the normal system software by initialising the boot process from the boot partition.
Flashing your SPL is risky, as the process failing will probably result in a broken, or bricked phone, since the SPL is executed very early on in the boot process, and any error here will prevent access to the recovery or bootloader features.
If you do flash the SPL though, it unlocks the Carrier-ID CID from the device, essentially allowing any RUU to be installed to the device, and allows flashing alternative or custom bootscreens.
Stock
The term stock is often used to refer to a file or part of the software which is unmodified or untouched by developers. For example, a stock ROM would be one which was produced by HTC and which had not been modified or rooted by someone. The term is often used when comparing performance of different ROMs, as a way to refer to the phone as it came out the box.
su
su (substitute user) is a Linux command which, when run without a username parameter, gives the user full 'root' permissions. By default, this command binary (ie. Linux equivalent of an executable file) is not included on Android systems, but the process of "rooting" a phone copies this file to the '/system/bin/' directory thereby enabling the command. Since root privileges can be abused by malicious applications it's highly recommended to install an app to grant and manage access to su, similar to UAC on Windows. VillainROM includes the app called "Superuser" for this.
System
The /system directory on your device is where the main operational software for the Android OS is stored. It has a number of sub-direcories of which /system/apps (where application apk's are stored) is probably the only one users would have need to access. The /system folder is read-only by default and needs remounted via 'adb' to allow write access.
Recovery
The recovery partition is a boot-mode for your phone that allows you to wipe your settings from the Data partition of the phone (a hard wipe), or perform an update using an update.zip file on the root of the microSD card. It is common (although not necessary) to flash a patched Recovery image, such as Amon RA's one. This allows you to run Nandroid backup from the device, and flash modifications, such as [[#update.zip]] files to the device, essentially becoming a means to install sotware to the device. Recovery mode is separate from 'normal' mode, and can be entered by holding down home whilst turning the phone on.
update.zip
An update.zip (does not have to actually be called update.zip if you have a patched Recovery image) is a file containing some files which will be copied to the phone's internal memory. Normally, a new system update or ROM is stored in the file, but update.zip files are commonly used to install modifications such as themes or applications that are installed on the System partition to prevent uninstallation.
To flash one of these files, which commonly would contain a custom ROM for your phone, you would boot your phone to a patched recovery image (whether using Fastboot, or the home+power method if you have a patched Recovery image flashed on your phone)
Update.zip files are cryptographically signed, and more information on how to sign your own files can be found online.
WWE
Stands for World Wide English version of the ROM. There can be local versions of ROMs too. For example VR10 is based on the Taiwan version, VR12 on the WWE one. Interestingly, WWE excludes the English (US) locale.
Now we are done with the definitions
HOW TO ROOT YOUR HTC One V PHONE
This guide may also work for rooting the HTC Wind / HTC Desire S (T328w). If you decide to try rooting your Wind / Desire V, make sure you first download the stock HTC RUU (ROM Update Utility) to recover if there are any issues.
Please note that unlocking your phone’s bootloader does involve the possibility of voiding your warranty, so be certain that you are willing to risk that to root your phone. Moreover, you proceed at your own risk. I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble.
You will need much patience and time, and you’ll need to know how to use SDK tools for Android (see below). If you are a total noob, I do not recommend this for your first project! If you try anyway and get confused with terminology, try looking here for answers: Terminology - CyanogenMod Wiki.
Quote:
Before you begin, make sure that your computer can properly recognize the phone:
You will need SDK tools for Android, Java runtime, and HTC Sync installed on your Windows computer. If you run Mac, I can’t help you. I avoid all that narcissistic iStuff like the plague.
1. You only need to install HTC Sync for the drivers that come with it. But the program sometimes causes conflicts, so during this procedure, make sure it is not running. Open Task Manager in Windows and kill it. If you don’t use HTC Sync, you may also open Control Panel and uninstall it without uninstalling the drivers.
2. With the phone on, connect the USB cable. Make sure the phone is connected in Charge only mode.
3. Enable USB debugging by going to Settings > Development > USB debugging.
1. Perform a full backup your phone’s data
Unlocking the bootloader will involve doing a factory reset. This will result in the loss of all accounts, emails, texts and apps installed on the device. However, data on the SD card such as music, photos and videos will be safe. The device will not format the SD card.
2. Update your software version
To update your software after rooting, you will have to go through hassle of re-flashing the stock recovery and re-locking the bootloader. The phone will lose root and you’ll have to go back through steps 3C-5F, so make sure you’ve updated first. To manually check if a software update is available, go to Settings > About > Software updates > Check now.
3. Unlock your bootloader at htcdev.com
The next step is to head over to htcdev.com and follow the procedure there to unlock your bootloader. This is the step that can void your warranty!
3A. Getting started
Create an account at htcdev.com and login. Click the Unlock Bootloader icon and Get Started button. On the next screen, drop down the “Select Your Device” list, choose All Other Supported Models and click the Begin Unlock Bootloader button. Then, fill out the two nasty forms telling HTC that it’s perfectly fine with you to possibly lose your warranty by going through with this process.
3B. Obtaining your unlock token
The first page of instructions shows you how to boot the phone into HBOOT, select FASTBOOT and connect the phone to your computer via USB. But the instructions are not right for the One V since it doesn’t have a removable battery. So here’s the replacement procedure:
Step 1 – No need to shut the phone down.
Step 2 – To enter HBOOT (or “bootloader mode”), the power button for longer than 10 seconds. As soon as the screen turns black, hold down volume and let off the power button. At the top of the screen you will see ***_LOCKED_***.
Step 3 – Use the volume rocker to select FASTBOOT if it’s not selected already. You may have to wait for the device to run through a routine check for zip files to update.
Step 4 – Connect the phone to your computer using the USB cable.
If you followed the directions above regarding SDK tools, Java Runtime and HTC Sync, you can skip page 2 of the instructions (steps 5-7) and move onto page 3.
In Step 8, you open a command prompt in Windows and navigate to the folder where you installed SDK Tools (it should be c:android-sdk-windows or c:Android) and type the command
Code:
fastboot oem get_identifier_token
Step 9 is where most people get hung up. Make sure that you do not select any spaces next to the identifier token, or any lines above or below the Identifier Token Start/End.
Paste the identifier token copied from the command window above into the box at the bottom of htcdev.com’s page 3 in your browser and click the Submit button. You will receive an email from htcdev.com with the subject “The key to unlocking your HTC Device” that has an attached file named “Unlock_code.bin” and a link to continue the unlock process. Download the attachment into the folder you installed Android SDK tools and click on the link to continue from page 4. You may have to log back in.
3C. Unlock the bootloader
For Step 12, go back to the command prompt and make sure you are in the folder where you installed Android SDK tools and downloaded the file “Unlock_code.bin” above. Now you will flash “Unlock_code.bin” to the phone using the following command:
Code:
fastboot flash unlocktoken Unlock_code.bin
You will see the following warning screen on the phone, again confirming that you are willing to waive your warranty rights to unlock the bootloader:
Use the volume rocker to select Yes (up one click) and press the power button once. The bootloader will proceed to erase all your data, unlock itself and reboot the phone.
After running through the setup wizard, go back into HBOOT (turn the phone off with the long press, hold down volume and press the power button) and confirm that you’ve unlocked your bootloader successfully. You should see ***_UNLOCKED_***. Success!
4. Install ClockworkMod Recovery
A custom recovery allows you to backup and restore ROMs including all user apps, data and cache to the SD card. It is also used to flash scripts, custom kernel and custom ROMs, which will come in handy at step 5 below where we root the phone.
1) There are two types of One V - the international GSM version (uses a sim card) and the U.S. Sprint/Virgin Mobile CDMA version (no sim card), and there are custom recoveries for both types that aren't interchangeable.
If your phone uses a sim card, download recovery-clockwork-5.8.4.5-primou.img from ClockworkMod's index of recoveries.
If you have a U.S. Cellular/Sprint/Virgin Mobile (U.S.) device that doesn't require a sim card, download cwmrecovery.img. Be sure to click the thanks button for Android Forums member jmz for his handy work.
As an alternate, PrimoC/CDMA users (no SIM) can download and install jmz's TWRP2 Recovery. See the directions in his thread: [VM/PRIMOC][RECOVERY] TWRP2 Recovery 7-10-2012
2) Reboot the phone into bootloader, select Fastboot and connect the USB cable.
3) Open a command prompt and navigate to the folder where you saved the recovery image in step 1 above. Type the following command:
Code:
fastboot flash recovery recovery-clockwork-5.8.4.5-primou.img
or
Code:
fastboot flash recovery cwmrecovery.img
4) Reboot the phone back into bootloader using the following command:
Code:
fastboot reboot recovery
You should see the new Recovery.
5. Now on to root the phone!
5A. Head over to XDA Developers and download the SuperSU access management tool. You'll want to grab the attached file at the bottom of the OP called CWM-SuperSU-v0.9x.zip. This will root your phone and install the SuperSU app in one smooth motion. Much thanks, credit and kudos go out to XDA user Chainfire. Login over at XDA and hit the thanks button for him somewhere or donate to his Paypal account and buy him a Coke.
5B. Copy CWM-SuperSU-v0.9x.zip to your SD card.
5C. Restart the phone into HBOOT again and select Recovery. After Recovery has launched, choose install zip from sdcard > choose zip from sdcard and select CWM-SuperSU-v0.9x.zip.
5D. Reboot the phone. It is now rooted!
5E. Go to the app drawer and click on SuperSU. Update the binary when prompted. It’s icon looks like this:
5F. Install and open any app requiring root access to confirm that the phone is rooted.
6A. Backup your stock HTC ROM in CWM5 Recovery!! Before you make changes to your stock ROM or decide to install a custom ROM, this is a must! Reverting back to a stock HTC ROM after installing a custom ROM can cause massive headaches. Restoring from a backup is MUCH easier. It will also help if you've ruined your ROM causing a softbrick. You just boot into CWM5 Recovery, do a factory reset and clear cache (including Dalvik) and do a restore from your previously backed-up ROM.
So, reboot the phone into bootloader, use volume down to select Recovery and press power to select. When Recovery comes up, select Backup/Restore > Backup. Then find the backup you just made on the SD card (under sdcard/clockworkmod/backup) and copy that to your computer for safekeeping in case you loose or format your SD card.
6B. Install custom ROMs Now we play the waiting game and wait for overclockable kernel and custom ROMs. I’ll be updating this section as things happen so come back and see what’s new.
The procedure for flashing a custom ROM is as follows:
1) Boot into Recovery and backup your stock ROM if you haven't already. If you don't and something goes wrong, you'll have a major headache on your hands. *DO NOT* skip this step.
2) Download the ROM and copy it to the root directory of your SD card.
3) From Recovery, o a factory reset, wipe the cache partition and wipe dalvik cache (under Advanced).
4) Install the update from the SD card.
5) Reboot the device.
How To Install Custom Roms
1.Boot into recovery
2.Do a nandroid backup
3.wipe
a.cache
b.dalvik cache
c.data
d.system(isnt necessary)
3.Select install zip from sd card
4.select the rom and put yes
And the rom will install
How to install custom kernels
1.Boot into bootloader
2.enter fastboot and plug your phone into your computer
3.open cmd and type cd and navigate to to where you placed the fastboot.exe and boot.img
then type:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
AND the custom kernel would be installed
How to Make a Nandroid Backup
1.boot into recovery
2.enter backup and restore
3.select backup
So it will backup all your rom
How to restore stock rom after installing custom rom
1.Boot into bootloader flash stock kernel(DO THIS ONLY IF YOU HAVE INSTALLED A CUSTOM KERNEL WITH THE ROM)
2.Enter recovery
3.select backup and restore
4.select restore
And stock rom will be installed
How to partition your sd card and make internal storage bigger
Partitioning is the act of dividing into parts and with SD Card it means to divide sd card into different virtual parts. So, you might be asking why we need to divide our sd card into two parts. This need has come into existence with devices such as Samsung Galaxy Pop/Mini GT-S5570, Samsung Galaxy Ace, Galaxy Fit and other smart phones that have relatively low internal storage (only about 180 MB or 250 MB) as a result it has been very difficult to manage our apps and data within the internal storage. So, to remove such low internal memory problem we are going to partition our sd card and then install the Darktremor Apps2SD Script so applications and games will install to this sd-ext partition that we are going to create by default and we won’t have to worry about low internal memory problem.
Before beginning it is assumed that you have a custom clockwork mod recovery and a custom rom is installed on your device. Alternatively, if you are in a stock firmware/rom and want to partition your sd card please Install Clock Work Mod Recovery and Flash a Custom Rom on your device. Also since partitioning your sd card will erase all your data stored in sd card, it is recommended that you backup your data to your computer. Now that you have backed up your data please follow these simple instructions to partition your sd card and install Darktremor App2sd script on your android smart phone.
1. Reboot your device into Clockwork Mod Recovery.
2. Go to Advance>>Partition SD Card option on your recovery and select a size for ext 3 partition. This will create an ext 3 file system partition on your sd card called sd-ext. The size of your sd-ext partition should be determined on the basis of how much apps and games you are going to install on your device. If you are not of type who wants to test every app or a normal user 2 GB of sd-ext partition should be enough. Determine the size that best suites you and proceed.
3. Also, select swap partition size as 0 Mb.
4. [Optional] Format your sd-ext from mounts and storage>>fromat /sd-ext option in CWM recovery.
5. Reboot your device and open a terminal emulator or shell commander and type in the following command to make sure that your second partition (aka sd-ext partition) is mounted at boot.
mount | grep sd-ext
You should see the following code:
/dev/block/mmcblk0p2 on /sd-ext type ext3 (rw,noatime,nodiratime,barrier=1,nodelalloc,data=ordered)
6. Now download Darktremor Apps2SD and copy it to your sdcard.
7. Reboot your device in CWM recovery and then mount your data and system by going to mounts and storage>>mount /data and mounts and storage>>mount /system options respectively.
8. Now go back to main menu and go to install zip from sd>>choose zip from sdcard option and select the dtapps2sd-2.7.5.3-beta04-signed.zip file you downloaded from above.
9. After the script is installed reboot your device.
That’s all. You have successfully installed Darktremor Apps2SD on your device. Note that the device will reboot again after you reboot your device. This is just to move all your apps to the second partition (sd-ext partition) and is normal. Also if you want to manage your Apps2SD settings you can either use commands in terminal emulator or download this APPS2SDGUI application from market and manage everything from there. One of the useful command can be a2sd help. Try it on any terminal to see the help file that comes with Darktremor A2SD.
Here are some commands that you can run in terminal emulator for configuring a2sd. You can find more info about them as well as other commands by typing a2sd help command.
a2sd check : Checks a2sd status; displays information incl. where your apps, cahce and data are stored.
a2sd cachesd : Moves dalvik cache to sd-ext partition.
a2sd nocache : Moves dalvik cache back to internal storage.
a2sd data2sd : Move /data/data to /sd-ext/data .
a2sd nodata : Move /sd-ext/data back to internal storage.
a2sd remove : Moves apps back to internal storage and sets no a2sd flag.
Now some precautions tips you should take in mind. After installing Darktremor Apps2SD don’t move your apps to sdcard either from Manage Applications Settings or by using app2sd pro or similar applications because it will ruin all your settings and your script will not work. Also you may notice that your used space in internal storage shown in Manage Applications Setting is not decreasing even after you install Apps2SD and you may think that the script is not working. But remember if you followed all the instructions from above and got the same results as explained above then the script is working. It is shown so because system is fooled to believe that the apps are in internal storage but in reality they are stored in the secondary partition we created (i.e. in /sd-ext/app folder) on your device.
How to install recovery
1.grab the recovery file and put it in thre folder where fastboot exists
2.open cmd and type cd and navigate to the folder where they both exist
3.Then type:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache
RESERVED
RESERVED2
RESERVED3
RESERVED4
RESERVED5
RESERVED6
Maybe if you used the search function on the site,before you posted this,you would'nt be the author,fan and publisher of your own thread...... http://forum.xda-developers.com/showthread.php?t=1466228
Heya,
Since there is not enough info on the web regarding the rooting procedure for Videocon A55 HD and custom recovery for this awesomely smooth device, I'm uploading the necessary files and step by step guide. Hope it helps all the users of this device.
Remember rooting would tamper the warranty of the device and should be exercised carefully. The procedures mentioned below have been personally tested by me however I take no responsibility in case you ruin your device although I would be here to help you in such a scenario. Besides this the rooting script was not created by me and all the credit goes to the respective developer.
1. Rooting Procedure
Make sure you have enabled "USB Debugging" under Developer Options on your phone.
Keep your phone disconnected from computer via USB
a) Download and Install the ADB Interface driver for MTK 6589
Link to ADB Drivers
b) Download and extract the rooting package
Link to the Rooting Package
c) Now go to the extracted package and open a command prompt to that location as Administrator.
d) Type run.bat in Command Prompt and a message must appear "Press enter to root your phone..."
e) Press any key
f) Now after a few seconds the message should be " * daemon started successfully *"
g) Now connect your phone via USB to the computer
h) The cmd would automatically start pushing the necessary files onto your phone and when the process completes your phone will restart
Now you are rooted.To check install any Root checker application from playstore. Remember to grant permission while running Root Checker app when a pop up appears. It is suggested to update the SuperSU app from playstore and execute it at least once after that to update the su binary. You can also update the busybox package from playstore because busybox supplied with the rooting package is pretty old.
2. Installing CWM Recovery
Okie, since you are now rooted, most likely you would require a custom recovery to create full nandroid backups or test different ROMs. The CWM recovery provided here was created using MTKDroid Tools and is version 5.x (Non Touch). Again all credit goes to the developer of MTKDroid Tools for making such a powerful piece of software.
a) Download and extract the recovery package.
Link to CWM 5.x and Original Recovery for A55 HD
b) There are two files in the package , one is the custom CWM recovery and the other one is Stock Recovery (Names are pretty self understood)
c) Copy "Custom_Recovery_CWM_A55HD.img" to the root of your SD card
d) Rename it to "recovery.img"
e) Install Mobile Uncle Tools [MUT] from the playstore.
f) Open MUT and go to recovery update
g) Now you must see the recovery.img in a list. Just select it and follow the pop ups.
h) Now your phone would restart.
i) To check if the recovery update was successful, go to MUT and select "Reboot into Recovery" and your phone would most likely start in CWM recovery..
Alternative to get into recovery mode is to Press Power button + Volume Down key together when switched off.
3. Stock ROM for Videocon A55 HD
Okie, here we go, as I mentioned that I had got hold of the stock rom, so here I'm publishing it. The credit goes to Pratap Solunke (psolunke) for providing the Factory ROM zip.
I have just divided it into update.zip and files for SPFT for ease of downloading. Besides I have splitted each section into 4 parts and reuploaded it so you can download them at your ease. I'm providing the link for the whole folder which includes the changelog, update.zip and files for SPFT.
The ROM version is V7 (2013.07.15) which is different from the original ROM which was V5 (2013.06.08).
You can read the changelog for the updates in this ROM.
Link to ROM Folder
If using update.zip to flash this ROM, then
Step 1. Open the update.zip with winrar, Do not extract.
Step 2. Navigate to \META-INF\com\google\android\updater-script and extract this file only, then use "Notepad++" to open the file.Don't use default notepad.
Step 3. Delete assert(getprop("ro.product.device") == "A55HD" || getprop("ro.build.product") == "A55HD");
Step 4. Save the file, put it back to the same location in archive (It will take some time to add to archive)..Done...then proceed as usual.
a) update.zip is for reinstalling Factory Image of the ROM from recovery mode. The zip file is signed.
b) Files for SPFT are to be used with SP Flash Tool and can be used in case your phone is bricked. Do not flash the preloader unless you know what you are doing.
c) To download the files just go to the respective folder and right click on each file and hit download. After all four parts are downloaded, extract Part 1 of the downloaded splitted files and the files would be ready to be used as is.
d) Keep all four parts of the splitted files in a single folder and do not rename the splitted files.
If you have any questions related to A55 HD you can ask them here and I would try to help you the best way I can.
I'm still testing some custom ROMS but none seem to work . So far I've tested LEWA OS and MIUI ROM for xiacoao G6 Youth. However I'll keep trying and update once I have a working Custom ROM.
One more project in mind is to port Custom ROMS to A55 HD if none is available as is on the web.
If anyone of you is able to find a working Custom ROM for A55 HD kindly post it here so that we can have a repository of successful and useless attempts. I'm sure it would help others.
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries
nanachitang420 said:
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries
Click to expand...
Click to collapse
I forgot to mention , rename the recovery image to "recovery.img" and then put it in root of SD card and it would get detected by MUT...It will get detected instantly...Thankyou for bringing it to notice...Just updating the post...
done but some observations!!!!
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only. NOTE, CANT SEE INTERNAL SD CARD ONLY WHEN TRY TO MOUNT INTERNAL PHONE STORAGE IN CWM. WHILE NORMAL WORKING NO PROBLEM.
2. Deleted.
3. Deleted.
4. Deleted,
5. Deleted.
6. The font size of Stock and CWM recovery is very small still it can serve the purpose.
Do any body have original/stock update.zip from Company?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man. The phone is working very nice after rooting.
nanachitang420 said:
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only.
2. After rooting, before even installing CWM, got some irratic behavior with touch. Like, while USB is connected, touch was not working as expected, it took long time to make USB storage active as after touching a specific required operation, like pulling down task bar it was doing something else like opening play store, opening game, or opening date and time settings. While unlocking lock screen, it was just opening any random phone application and is not even allowing to go back with back button or home button. Don't know this is related with what?
3. Irratic application were opening while touching different application but after removing USB, things were working better.
4. Rebooted in CWM and first tried to "fix permissions" to avoid that irratic touch behavior, thinking there was problem with permissions. Took nandroid back up, after fixing permissions. Wiped cache and dalvik cache and restarted.
5. Now, till now phone is not connected to PC with USB cable or connected to charging; it behaves better with touch but it is very troublesome to perform any operation after phone connected to PC with USB or to charger.
May be you have faced these issues or may not! Any suggested solution? Do any body have original/stock update.zip from Videocon?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man.
Click to expand...
Click to collapse
For me the touch works without any problems...and as for detecting internal sd card...that also works flawlessly..i don't have the phone with me right now...Yesterday I was trying something and the nvram got corrupted [No baseband]...so right now it is resting at service center...Hope to get it next week...
One suggestion never install Carliv Touch Recovery on this phone...it messes with the baseband and display...Stick to this recovery until I build a more updated CWM...
Latest V-Store attached
Attached
nanachitang420 said:
Attached
Click to expand...
Click to collapse
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..
update.zip
Aaaaanuj1 said:
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..
Click to expand...
Click to collapse
The current version of my phone is 08062013. Can I flash this latest version through CWM and upgrade?
Tried to flash update.zip through CWM...
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.
nanachitang420 said:
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.
Click to expand...
Click to collapse
Okie it is an easy fix...
Step 1.Open the update.zip with winrar, Do not extract.
Step 2.Navigate to \META-INF\com\google\android\updater-script ,use "Notepad++" to open the file.Don't use default notepad.
Step 3.delete assert(getprop("ro.product.device") == "A55HD" ||
getprop("ro.build.product") == "A55HD");
Step 4.Save the file, update to archive..Done
Done
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,
nanachitang420 said:
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,
Click to expand...
Click to collapse
Nice...Yeah, people at Videocon forgot to change the version number i guess...and loss of root and cwm was due to restoring of system.img and recovery.img in the ROM file...so it's normal..
Besides one should always perform a clean install from CWM..i.e. Clear Data, Clear Cache, Clear Dalvik Cache, Format /system/ and then install ROMS..
And yes this ROM is a bit better then the one on phone..I received my phone today from service center and software was updated to this ROM..It felt much better .And the version was same , so this seems to be the latest ROM for A55 HD.. Enjoy
How to flash phone with sp flash tools
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589
nanachitang420 said:
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589
Click to expand...
Click to collapse
You must understand that the recovery partition is of 6 mb....and most likely the recovery you received from CWM online builder was more than 6 mb..hence your secro.img was also overwritten...hence the problems with baseband and imei....same thing happened with me 7 days back when I had to submit my phone to Service center. Unfortunately i didn't had the flash image then but it is good to know that it can also recover baseband and imei. And congrats for recovering your phone and I'm glad my contribution helps you...
Just remember one thing...if the boot, recovery,secro partitions are of more than 6mb then don't flash them as they would mess one thing or other...and hopefully you had disabled preloader in SPFT.....if not then from next time onwards please do it....because rarely you need to flash preloader...and a wrong flash can make your device a brick which can only be recovered by Test points.Hence never flash preloader until unless you know what you are doing.....And yes, I already use Gravity Box along with Xposed Framework...Great mod...Besides them I also use xhalofloatingwindow with bubble launcher and lwinrecent ...Both are xposed modules and work as expected.I also have init.d support which allows to make boot persistent changes on device....Along with that a few build.prop tweaks that take my ROM to the custom level...Let me know if you need any of this...
Please
Thanks for preloader advise. was not that much aware and will take care next time. Please share init.d support, build.prop tweaks and their usefulness.
For init.d, use term-init by ryuinferno.
http://forum.xda-developers.com/showthread.php?t=1933849
This is the link to the thread. Do not use zip-init or uni-init. Follow the guide on the thread. It works flawlessly.
Sent from my A55HD using Tapatalk
Which other phones has MTK6589 and same config ?
Tell me model number and brand, i will try to upload stock firmware.
it will help us built custom rom with custom features.
@anuj - Anyways if it brick again and need to send service center, please text me imei and location, i will make it done fast for you dear.:fingers-crossed:
Thank you Pratap bro. I'll let you know next time if I get to the point where I need to go to service center but I'm sure that with the ROM you provided I wouldn't need to go to one. And yes people you can ask for stock ROM from Pratap. He has excellent connections and can get you at least the Videocon ROM and may be others . Don't forget to thank him. Besides he is an excellent person who wouldn't shy away from helping you if he can. Ciao Pratap brother.
Sent from my A55HD using Tapatalk
Any new updates from Videocon for our A55HD?
File not found
File not found bro
Hello guys, i'm new on the world of Android and i need a little help. I'm newbie but i learn fast.
I got a new phone with android 4.4.2 China honor 3 (fake), after uninstalling some China app the operation system started to stuck at logo at the start.
So to solve the problem i red that i could restore the old OS using ROM file. The factory where i bought the phone sent me the official ROM file for my phone.
Now i entered on Recovery mode, first i did "wipe data/factory reset", then with ADB i loaded the file .zip "adb sideload update.zip". But how the file is uploaded it says "Installation aborted", without any error.
So now i need your help how can i restore this system... I tried also to buy an SD card 8 gb and upload the file on the SD, but same error.
Thank you for your help!
try this guide
http://forum.xda-developers.com/showthread.php?t=2517943
bcuz you can;t flash rom with stock recovery so you install cwm mod from this guide:fingers-crossed:
3lo0sh said:
try this guide
http://forum.xda-developers.com/showthread.php?t=2517943
bcuz you can;t flash rom with stock recovery so you install cwm mod from this guide:fingers-crossed:
Click to expand...
Click to collapse
Thank you for the answer. But wheni try to run TouchRecoveryLoader.zip from recovery, it says "installation aborted" like for the ROM.
I dont know if the phone got root access, i think this can be the problem.
Can youhelp me?
Thank you
Bump! Need help guys
SUMMARY:
I unistalled wrongly MIUI (MiHome app) and the phone stopped working correctly.
Phone is a fake honor 3c with MTK 65xx processor.
1 - Phone doesnt load the main theme, after the android logo i see a black page. (i see the top bar where there are wifi, time etc)
2 - The phone is not rooted. (i think)
3 - I can enter in Restore Mode and Factory Mode.
4 - I got the official ROM file. (the factory gave me it)
5 - All file zip (that i try to use in recovery from SD or ADB) give me "Installation aborted" without any error.
6 - I haven't USB DEBUG enabled, and i can't enable it cause i can't load the Operation system.
shayolz said:
Bump! Need help guys
SUMMARY:
I unistalled wrongly MIUI (MiHome app) and the phone stopped working correctly.
Phone is a fake honor 3c with MTK 65xx processor.
1 - Phone doesnt load the main theme, after the android logo i see a black page. (i see the top bar where there are wifi, time etc)
2 - The phone is not rooted. (i think)
3 - I can enter in Restore Mode and Factory Mode.
4 - I got the official ROM file. (the factory gave me it)
5 - All file zip (that i try to use in recovery from SD or ADB) give me "Installation aborted" without any error.
6 - I haven't USB DEBUG enabled, and i can't enable it cause i can't load the Operation system.
Click to expand...
Click to collapse
if you open the zip file you got, whats inside it? is it a .tar file, or a .md5 file?
Sorry, i didn't write that i SOLVE the problem!
I userd flash tool selecting only "ANDROID" and pointing to the system.img of the ROM that the factory gave me.
Android reinstalled, all working fine.
/closed
thanks
(Rooting guide at post #5 http://forum.xda-developers.com/showpost.php?p=63803008&postcount=5)
(Stock ROMS at post #7 http://forum.xda-developers.com/showpost.php?p=63939728&postcount=7)
Hi,
The new flagship from Wiko, the Wiko Fever, it's a great device. :good:
Here my research with it:
- MT6753 with 16GB ROM and 3G RAM
- Bootloader LOCKED (you can unlock it using one option in the developers hidden menu (you know how to enable it!) and then after reboot in the bootloader execute "fastboot oem unlock" (note, that selecting OK you will erase your data!).
:good:
- You can download an EXPERIMENTAL (=ALPHA) custom Recovery (CWM-Carliv) from here (you need to flash it to use it):
***removed***
- Also you can download the original DUMP of the boot.img and recovery.img from here:
http://www.sendspace.com/file/zy9q6g
:silly:
You can pack/unpack the recovery/boot using the CarlivImageKitchen selecting "normal" (not MTK) version!
..
Hi,
This device (Wiko Fever) is the same as Micromax Canvas 5 E481:
http://www.micromaxinfo.com/mobiles/smartphones/canvas/canvas-5-e481
Also, is identical to Blue Life ONE X:
http://www.bluproducts.com/index.php/life-one-x-2016
Follow the thread (with custom Kernels) at:
http://forum.xda-developers.com/general/device-reviews-and-information/blu-life-one-x-2016-t3287428
Then the same firmware and rooting procedure will be shareable between both!
Here a great guide for Wiko Fever & Clones:
http://forum.xda-developers.com/android/general/guide-clones-t3421539
Hi,
Here the scatter file for Wiko Fever Lollipop 5.1.
Two versions: a) extracted from stock update (scatter_stok); b) made by hand (scatter3).
Rooting GUIDE
Hi,
Good news: Rooting is done! :victory:
Here is the guide for rooting your Wiko Fever:
Warning (for newbies): First copy all indicated files to your SD card using your phone in normal state. Or use a PC and a SD reader for copy them when indicated.
1) Unlock bootloader:
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.
1.2) Power on the device in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
2) Install custom Recovery:
2.1) Download from here the BETA 1 of CWM BETA 2 of CWM BETA 3 of CWM: http://www.sendspace.com/file/4g87bj
OR Download TWRP Beta 1 for Lollipop 5.1 from Hanuma: http://www.sendspace.com/file/y4jel8
(Original post: http://forum.xda-developers.com/showpost.php?p=64543542&postcount=45)
OR Download TWRP 3.0.2.0 for Marshmallow from Hanuma: https://www.sendspace.com/file/9ms9zz
(Original post: http://forum.xda-developers.com/showpost.php?p=67531723&postcount=217)
2.2) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Then execute command “fastboot flash recovery recovery-custom-wiko-fever.img”; and then “fastboot reboot”.
3) Rooting:
3.1) Copy last beta of SuperSU v2.52 to your SD Card (file BETA-SuperSU-v2.52.zip).
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3.2) Boot in the CWM with “Vol+” and “Power” buttons.
3.3) Install ZIP from external-sd card.
3.4) Reboot and don’t select “fix root”, only “Yes”.
3.5) After boot, start SuperSU and configure it. Root done!
4) Xposed install:
4.1) Copy last release of Xposed Installer to your SD Card. Use files from here:
http://forum.xda-developers.com/showthread.php?t=3034811
* xposed-v78-sdk22-arm64.zip
* XposedInstaller_3.0_alpha4.apk
* xposed-uninstaller-20150831-arm64.zip (in case of errors).
4.2) Boot in the Recovery, and install the framework (file xposed-v78-sdk22-arm64.zip).
4.3) After reboot, install the Xposed APK (file XposedInstaller_3.0_alpha4.apk).
4.4) Reboot. The Xposed framework is running.
Enjoy!
Notes: Before starting to root your device I recommend to do a full DUMP of the firmware using the SP Flash Tool. Use my handmade scatter file. :angel:
Thank you to all developers & supporters! :highfive:
ChangeLog:
- Beta 3: Fixed ADB shell with root uid.
- Beta 2: Fixed SELinux context support in ext4 filesystem. Full woking for rooting!
Note: If you like to use adb shell in recovery but an error like "exec '/system/bin/sh' failed: No such file or directory" then first mount /system partition.
- Beta 1: Don't use this version, has a bug with SELinux contexts!
- Alpha(1,2,3): Pre-releases.
List of stock ROMs (for flashing with SPFlashTools) for Fever V8 (16GB/3GB) only:
- Lollipop v39 (last version until 5/2016): http://world.wikomobile.com/scripts/telecharger.php?id=140&type=MAJ
- Lollipop v22 (update 02.12.2015): http://fr.wikomobile.com/scripts/telecharger.php?id=105&type=MAJ
- Lollipop v18 (update 10.11.2015): http://fr.wikomobile.com/update-918-FEVER-4G
In case you need it!
List of stock OTA ROMs (for flashing with CWM/TWRP Custom Recovery):
If you have rooted your device, you can upgrade using these ROMs...
- Lollipop v39 (pre-rooted, with Xposed and ViPER Audio):
part 1: http://www.sendspace.com/file/d0js30 md5: e8706e0f5860e907fb8169856fc5e3b9
part 2: https://www.sendspace.com/file/iv4mnb md5: dd76926221ef40c872e4548a9b9e1f19
part 3: https://www.sendspace.com/file/6lfd18 md5: 838e6e608983a296611a284831fffd47
WARNING: At time this is untested! Give feedback with a post in the thread!
Decompress it using 7zip in your PC, copy files to your SD Card TWRP/Backup folder, and restore this backup with TWRP
Probably you want to use these versions!
Hi,
God news! I de-bricked my device... ****ing erroneous selinux context attributes in /system/lib64/ and /system/bin/ are the reason!
So, I don't futher need the stock SYSTEM partition. I'll continue with the rooting process... soon I'll publish it.
this device can support cm12-cm13?
djsolidsnake86 said:
this device can support cm12-cm13?
Click to expand...
Click to collapse
I hope!
Maybe will be easy for some developer to port one CM13 firmware for MT6753 to this device.
The opensource package for this device isn't at time available. Sorry!
Verify that the bootloader is unlocked
Hi manos78, first of all thanks for this guide and all the efforts you are putting into this.
manos78 said:
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.
1.2) Power on the device in the BOOTLOADER mode. Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
Click to expand...
Click to collapse
I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?
Thanks again!
hi guys, i followed the guide and all worked also with the last update
cippaciong said:
I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?
Click to expand...
Click to collapse
After the command "fastboot oem unlock" If you see the Warning message and the device is rebooted and formating the data partition, then you have for sure unlocked the bootloader.
But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.
Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?
Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/
manos78 said:
But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.
Click to expand...
Click to collapse
Unlocked
You have been really helpful, thank you!
oile said:
Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?
Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/
Click to expand...
Click to collapse
Hi,
I try to boot the custom recovery image with fastboot without flash and it fails. So for rooting, at time, the only way is: unlock->flash custom recovery->install superSU. But after that, you can try to: flash stock recovery->re-lock, if you like (not tested by me! Be carefull!). However, with the custom recovery you can do full backups, so I recomend it. The side effect is that you can't upgrade with OTAs.
Another option is use the original stock firmware and readback/flash the SYSTEM partition and modify it using an external computer (modify the IMG). But, this solution is quite complex.
Finally, related to the SD-CARD. The "internal memory" is only for "media", not for Apps. I use one 64GB SD on my Fever and I store in it: photos, music & ISO/IMG images. Any other data is in the internal storage (emulated sdcard). Also, I "installed" (=moved) some huge games (>100MB) to the sdcard (the real SD); and I store my Google Kiosk and Music files on the sdcard (also the real SD). Please, don't care about the sd storage, is working right on the stock firmware.
:good:
Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.
About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)
oile said:
About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)
Click to expand...
Click to collapse
In stock Fever ROM:
/sdcard --> the REAL SD Card (the Sygic data, Google Music & Kiosk, etc. are in the REAL SD Card)
/storage/sdcard1 --> the EMULATED SD (internal memory)
Then you can use the SD as real one with Apps, and use alternative (emulated) when you like. The "media" Apps can use sdcard0 (real) or sdcard1 (emulated).
Related to this sentence: "hese apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)"
Please, remember: both, external memory and internal memory, have LIMITED life (write operations). Then, what you prefer: write more on the internal and not interchangable memory, or in a removable and inexpensive memory?
Please, think well! :angel:
Also, FYI, in my current Wiko Fever I use a 64GB SDXC UHS-II, far away than a simple class 10 (x15 reads/x30 writes).
oile said:
Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.
Click to expand...
Click to collapse
I'm quite accustomed to filesystems and partitions since I've been using Linux for many years but I've got almost zero experience with Android internals, so please help me to understand if I got this right.
Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?
I'm sorry if my questions might sound dumb to you but I'd like to start tinkering with Android a bit more but having a hard time finding a good starting point.
cippaciong said:
Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?
Click to expand...
Click to collapse
Hi,
Unlock bootloader is for booting NON-SIGNED kernels (the boot or the recovery), not for partitions.
When you unlock the bootloader you can install (or boot) a CUSTOM recovery. In the custom recovery you can mount and modify the SYSTEM partition (where is included the root).
For "flash" or "dump" the internal memory of the device, if it's using a MTK cpu (like the Fever) then you can use SP FLASH TOOL. You have the scatter file in this thread!
I have almost finished setting up new Redmi 6.
After rooting, getting TWRP on the phone I have reinstated all apps trough TitaniumBackup. I have reinstated too many apps from TB and at some point I have removed 1 or 2 apps too many that I thought are only from TB...
Inside TB I went into system apps and deleted apps wit: Backup copy [APK + backup]. Before I realised that apps with backup were actually original Xiaomi appswas too late, I had few warnings later and phone rebooted but couldn't boot into system.
This way I got rid of:
com.android.providers.telephony
com.android.phone
I could recreate what I have removed going into old phone and seeing which apps are backed up from system...
Can you help me to get apps back trough TWRP or FASTBOOT?
USB debugging was still on last time
My SD card is formatted as part of internal storage
TWRP File Manager can browse ROOT folder
It is newest ROM for Redmi6, [V10.3.6.0.OCGMIXM_], can someone provide copy of APKs please?
When in TWRP I mount system only, and try to [wipe dalvik] I get messages:
Failed to wipe dalvik
Updating partition details...
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
...done
Unable to mount storage
I almost will not loose any data, but:
if I can I'd like to move missing apps back to /app/data/ OR /system/app/ ? to recover system so it starts
if need be I will flash Xiaomi ROM and start from scratch but will loose many h of hard work on de-bloating etc [I hope that flashing original ROM will be easy since TWRP is working fine]
During TWRP - ADB sideload:
HTML:
adb install com.android.phone.apk
error: device '(null)' not found
- waiting for device -
What can I do???
-------------------------------------------------------------------------------------
Turns out I had to flash original stock
Xiaomi guide is terrible and out of date, so:
there are prerequisites required, like ADB, drivers, that is well explained on Xiaomi site, then...
download original stock for fastboot >>> unpack folder XXX sitting inside 2 archives [it's not zip] >>> download/install and run XiaoMiFlash.exe >>> SELECT button - navigate to unpacked folder XXX >>> attach mobile >>> refresh = device will appear on list >>> FLASH
Read official xiaomi instructions on flashing original ROM just in case something will get updated
Why not any other way?
In TWRP it asked me for a password at the start
I couldn't get /system/ or /data/ mounted, wiped or formatted.
I have seen folks giving advice on how to do it, but often it didn't make sense or it didn't work.
I would be risking bricking new device by other methods & I had no more than 3 pictures to loose on flashing ROM and hours spent on doing up.
Interesting is, there really wasn't even one working advice on how to mount i.e. /system in TWRP when password is missing in booted operating system [like my case, I couldn't find any info on that, all at some point were going to advice to do something that required mounted /system or /data]
But then I just finished whole process of flashing stock ROM; I have set [1. simple password] then [PIN], went to TWRP, tried to use OS password/PIN and it didn't work, it didn't remove encryption .
----------------------------------------------------------------------------------------------------------------------------------------------
Found a solution on how to root the phone after all above.
After another Original stock ROM 10.3.6.0.OCGMIXM flash with XiaoMiFlash.exe, phone will automatically restart and start OS
But... I didn't let it to boot
Once it restarted I have pressed Vol- [button down] and waited for fastboot to load [no need to hold power button]
Installed TWRP 3.0.0.0
Restarted
Hold Vol+ [button up]
TWRP loads
CANCEL if asks for password
----------------------
INSTALL boot.img [when you flash stock ROM it is inside folder, just copy it across]
in MOUNT tick /vendor & /system
use back button to exit MOUNT
INSTALL Magisk 19.3.zip
clean dalvik cache and swipe
I have once again restarted to RECOVERY/TWRP
------------------------
When OS booted I couldn't run/start Magisk APK/aplication. Screen blinked and that's all. Root not working.
download Magisk Manager [7.3.4 in my case] from web & install
I could start application this time & it asked me to install something extra - I have chosen to install it right away
Magisk reboots phone
Now phone was finally rooted
---------------------
I used external USB attached to phone with files so I didn't need to copy files to phone.
This is much more convenient as after restarting to TWRP first time there is nothing on the phone and you would have to sideload.
---------------------------
Below is LibreOffice doc with ADB commands to uninstall bloatware. In the column next to uninstalling commands, are commands to instal same app back [I do not know will this always work since I tried only on few] [some missing - you can create it yourself]
Potentially further down the list there are more necessary apps. Uninstalling them did not cause problems in my set up, but sometimes they might be needed for less important stuff...
https://www.dropbox.com/s/xpfeh4wx1nv5dlf/Bloatware removal + SD as internal.ods?dl=0