Guide requested by my Dear friend @karanrajkapur :good:
Click to expand...
Click to collapse
I'll go straight to the point:
A - How to unlock your bootloader ♣
♣ Nexus devices are the easiest to unlock so don't worry about that part (Caution: All your personal data will be erased in the process!)
♣ ♣ Download and install the latest ADB & Fastboot in C:\Windows [Why?] (Link in Useful Links section.)
♣ ♣ Download and install the latest USB drivers (Link in Useful Links section.)
♣ ♣ Power off your phone, then hold Power + Volume Down to enter the boot menu.
♣ ♣ Connect your USB cable and use the volume keys to go to Reboot to Bootloader then press the Power button to reboot.
♣ ♣ Open a command-prompt window on your PC and use this command to unlock the bootloader: (Fastboot.exe must in be the work path of the command-prompt)
Code:
fastboot oem unlock
♣ ♣ Check your phone screen and confirm the unlock process. (All your personal data will be gone in the process.)
♣ ♣ ♣ Done You have unlocked your bootloader, you can now flash a custom kernel and a custom recovery
B - How to flash a custom recovery ♣
♣ You will also need fastboot to flash a custom recovery for the first time. (You can use GooManager from the PlayStore instead if you are rooted)
♣ ♣ Download TWRP* Recovery or CWM Recovery .IMG file. (* Recommended)
♣ ♣ Power off your phone, then hold Power + Volume UP + Volume Down to enter the boot menu.
♣ ♣ Connect your USB cable and use the volume keys to go to Reboot to Bootloader then press the Power button to reboot.
♣ ♣ Open a command-prompt window on your PC and use this command to flash the custom recovery. (Fastboot.exe must in be the work path of the command-prompt)
Code:
fastboot flash recovery [color=green]recovery.img[/color]
fastboot reboot
♣ ♣ ♣ Done! Now to access recovery mode reboot your phone and keep holding Volume Down before the GOOGLE logo shows up, you will then access the boot menu, select recovery mode from there and hit the power button.
♣ ♣ ♣ You can now flash SuperSu and gain root privilege on your device, you can also flash custom ROMs and custom kernel zips from recovery without the need of a pc.
C - How to Root your Nexus 4 ♣
♣ The best and fastest way to root is by using a recovery zip, toolkits can cause problems.
♣ ♣ Download SuperSU installable zip >> SuperSU
♣ ♣ Place the zip on your phone storage and install it from recovery.
♣ ♣ ♣ You are now rooted! You can benefit from many cool apps and tools, you can find some in the Useful Links section.
D - How to flash a kernel ♣
♣ There are two ways to do it, either using a PC with fastboot or by installing the kernel using a recovery installable zip (Most - if not all - kernels come zipped and ready to install from recovery // easier.)
♣ ♣ If you wish to flash the kernel .IMG file using fastboot, the command you need is the following:
Code:
fastboot flash boot [COLOR="green"]boot.img[/COLOR]
Useful Links
♣ Minimal ADB and Fastboot
♣ USB drivers (Look for LG in this page, download the universal drivers)
♣ TWRP Recovery for Nexus 4
♣ CWM Recovery for Nexus 4 (Look for Nexus 4 \ Normal & touch recoveries are available)
♣ SuperSU
♣ LMT Launcher
♣ Touch control - Double-Tap-to-wake \ Swipe-to-Wake \ Swipe-to-Sleep
♣ Trickster MOD [Kernel Settings and Tweaks]
♣♣ Nexus 4 - List: ROMs, Kernels, Recoveries and More
♣♣ [APP / Tool] Universal kernel flash
♣♣ [NEXUS 4 TOOLKIT V2.0.0] Drivers, Backup, Unlock, Root, Recovery, Flash, Mods + MORE
Click to expand...
Click to collapse
♣
♣♣
♣♣♣
♣♣
♣
♣ Don't forget to hit Thanks :good: and guide the noobies who need help to this thread ♣
Click to expand...
Click to collapse
♣Reserved♣
♣ Why install ADB and Fastboot in C:\Windows ♣
You MUST read this:
PATH environment variable in Windows OS
On DOS, OS/2, and Windows operating systems, the %PATH% variable is specified as a list of one or more directory names separated by semicolon ( ; ) characters.
The Windows system directory (typically C:\WINDOWS\system32) is typically the first directory in the path, followed by many (but not all) of the directories for installed software packages. Many programs do not appear in the path as they are not designed to be executed from a command window, but rather from a Graphical User Interface.
When a command is entered in a command shell or a system call is made by a program to execute a program, the system first searches the current working directory and then searches the path, examining each directory from left to right, looking for an executable filename that matches the command name given. Executable programs have filename extensions of EXE or COM.
Once a matching executable file is found, the system spawns a new process in which to run it.
The PATH variable makes it easy to run commonly used programs located in their own folders.
--Source: Wikipedia, Edited.
Click to expand...
Click to collapse
♣ You still don't get it? ♣
♣ So, instead of installing adb and fastboot in some random folder and going into that folder to call fastboot every time you want to use it, you can add the folder directory to %PATH% variable, or you can install adb and fastboot in a directory already listed in the PATH variable, such as C:\Windows and C:\Windows\System32
♣ PS: It is completely harmless to add a couple of executables to Windows system directory.
How to open Command prompt window????
Sent from my Nexus 4
jokermithun said:
How to open Command prompt window????
Sent from my Nexus 4
Click to expand...
Click to collapse
Search for cmd.exe in your pc :fingers-crossed:
jokermithun said:
How to open Command prompt window????
Sent from my Nexus 4
Click to expand...
Click to collapse
If you're using Windows 7 or later:
Go to the folder where fastboot.exe is located and hold shift + Right-Click and select Open command window here
Well thanks Mikey for considering my request!
You Rock!!
About unlocking bootloader it seems that this method avoids loss of data.
(until 4.2.2)
Primokorn said:
About unlocking bootloader it seems that this method avoids loss of data.
(until 4.2.2)
Click to expand...
Click to collapse
i dont think there's anyone using 4.2.2 anymore anyway thanks for mentioning this pal :good:
If you buy a Nexus unlock it right away that's what I did, and i didn't loose my data, cz there wasn't any
Sent from my Nexus 4 using xda premium
themike10452 said:
i dont think there's anyone using 4.2.2 anymore anyway thanks for mentioning this pal :good:
If you buy a Nexus unlock it right away that's what I did, and i didn't loose my data, cz there wasn't any
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yeah I'll buy the new Nexus and I hope that the process will be as easy as mentioned in your guide
Primokorn said:
Yeah I'll buy the new Nexus and I hope that the process will be as easy as mentioned in your guide
Click to expand...
Click to collapse
yes all nexus phones are the easiest to manipulate
Sent from my Nexus 4 using xda premium
Thanks for this. Just got a Nexus 4 and this works great for me!
islandboy_2000 said:
Thanks for this. Just got a Nexus 4 and this works great for me!
Click to expand...
Click to collapse
gooo0oo00oooo0oo00oood
Sent from my Nexus 4 using xda premium
I am using 4.3 stock, is there anyway to unlock the bootloader without loosing my data or any way to backup my data and apps as tb wud not work widout root
Sent from my Nexus 4 using xda app-developers app
Yu583 said:
Your guides are awesome. Thanks, now I just need a Nexus 4 and I'll be all set
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
:good:
Wyse793 said:
Looking for more information on Android 4.3? Here you go:
An In-Depth Look At The Big (And Small) Additions To Android Jelly Bean 4.3
App Ops: Android 4.3's Hidden App Permission Manager, Control Permissions For Individual Apps!
Another Android 4.3 Change: Photo Spheres Look A Lot Better Now
Android 4.3 Feature Focus: Multi-User With Restricted Profiles
Android 4.3's New Notification Service: Read, Dismiss, And Press Action Buttons From Other Apps; Imagine The Wearable Computing Possibilities!
XXXHDPI Spotted In 4.3 Source: Prepare Your Eyeballs For Android In 4K Resolution
Root On Android 4.3 Is Still A Bit Broken, But Chainfire's SuperSU Works, And Here's Why
[Developer Changelog] Here's A Really, Really Detailed Look At What's New In Android 4.3 (JSS15J)
Click to expand...
Click to collapse
Sent from my Nexus 4 using xda premium
rohit297 said:
I am using 4.3 stock, is there anyway to unlock the bootloader without loosing my data or any way to backup my data and apps as tb wud not work widout root
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure of there's a way to avoid data loss or even backup with no root.
edit: try to flash twrp recovery on locked bootloader, it might get flashed. If it does, enter recovery and backup system and data and whatever you want then unlock the bootloader :good:
Sent from my Nexus 4 using xda premium
Related
Hi there!
I'm trying hard to get the custom rom RomAur running at my Xperia Z but I'm having some trouble to finally installing it.
Thread to the Rom: http://forum.xda-developers.com/showthread.php?t=2167064
What has to be done:
1 - Unlock bootloader - http://unlockbootloader.sonymobile.com/
2 - Copy rom to ext sdcard
3 - This rom if come without kernel , to get recovery flash DooMLoRD advanced stock kernel - http://forum.xda-developers.com/show....php?t=2167381
4 - Enter to recovery
5 - Make sure to do a Factory Reset/ Wipe data / system/cache before installing ROM
6 - Install rom
7 - Reboot system
8 - On disable flash recovery stock say no to get init.d support
9 - Enjoy
What I managed so far:
1 - Unlock bootloader - http://unlockbootloader.sonymobile.com/
2 - Copy rom to ext sdcard
3 - This rom if come without kernel , to get recovery flash DooMLoRD advanced stock kernel - http://forum.xda-developers.com/show....php?t=2167381
4 - Enter to recovery
Problem is: After doing a factory reset I don't know how to finally install the custom rom. Could somebody help me with that? If I manage to get it working on my Xperia Z I will write a step by step-guide to install custom rom with that phone.
Hi There,
Maybe you should have posted this into the forum of the Rom.
But to install it - once you have copied the Zip file to your device - you select 'Install from Zip' from the main menu of the recovery - select the Zip file and wait while it installs - reboot - Done!
Cheers
Paul
harrytipper said:
Hi there!
I'm trying hard to get the custom rom RomAur running at my Xperia Z but I'm having some trouble to finally installing it.
Thread to the Rom: http://forum.xda-developers.com/showthread.php?t=2167064
What has to be done:
1 - Unlock bootloader - http://unlockbootloader.sonymobile.com/
2 - Copy rom to ext sdcard
3 - This rom if come without kernel , to get recovery flash DooMLoRD advanced stock kernel - http://forum.xda-developers.com/show....php?t=2167381
4 - Enter to recovery
5 - Make sure to do a Factory Reset/ Wipe data / system/cache before installing ROM
6 - Install rom
7 - Reboot system
8 - On disable flash recovery stock say no to get init.d support
9 - Enjoy
What I managed so far:
1 - Unlock bootloader - http://unlockbootloader.sonymobile.com/
2 - Copy rom to ext sdcard
3 - This rom if come without kernel , to get recovery flash DooMLoRD advanced stock kernel - http://forum.xda-developers.com/show....php?t=2167381
4 - Enter to recovery
Problem is: After doing a factory reset I don't know how to finally install the custom rom. Could somebody help me with that? If I manage to get it working on my Xperia Z I will write a step by step-guide to install custom rom with that phone.
Click to expand...
Click to collapse
at CWM..please select install zip from external sd. then you will finally install the rom. did u managed to go into CWM interface? i assume yes since u already done factory reset.
doki81 said:
at CWM..please select install zip from external sd. then you will finally install the rom. did u managed to go into CWM interface? i assume yes since u already done factory reset.
Click to expand...
Click to collapse
So far I managed to install the advanced stock kernel and get root on my device (using fastboot.exe and BusyBox). So after that I enter recovery mode using Quick Boot. Then I have to do factory reset as found in preferences on my device. So far I think I got it.
But after that I have to wipe my data, system and cache. How do I do that and go on with the steps upcoming? After doing that I normally have to configure the device again for letting me use Recovery Manager and stuff like that, or don't I? So how should I do the full wipe?
Thank you for your suggestions so far!
harrytipper said:
So far I managed to install the advanced stock kernel and get root on my device (using fastboot.exe and BusyBox). So after that I enter recovery mode using Quick Boot. Then I have to do factory reset as found in preferences on my device. So far I think I got it.
But after that I have to wipe my data, system and cache. How do I do that and go on with the steps upcoming? After doing that I normally have to configure the device again for letting me use Recovery Manager and stuff like that, or don't I? So how should I do the full wipe?
Thank you for your suggestions so far!
Click to expand...
Click to collapse
the next step you should do is to flash the CWM..
follow guide in this post http://forum.xda-developers.com/showthread.php?t=2167381
afterward you can do full wipe from the CWM and proceed to use CWM install zip function to flash the new aur rom.
paulrgod said:
Hi There,
Maybe you should have posted this into the forum of the Rom.
Paul
Click to expand...
Click to collapse
Sorry, I thought this was the right place to ask, because I don't want to spam in other forums. Maybe you could move it?
paulrgod said:
But to install it - once you have copied the Zip file to your device - you select 'Install from Zip' from the main menu of the recovery - select the Zip file and wait while it installs - reboot - Done!
Paul
Click to expand...
Click to collapse
I tried both ways, copying the zip file to root of the device itself and onto sd card (RomAur V1.1 XZ C6603.zip, FAT32 formatted 16 gb sd card). But Recovery Manager doesn't show any of these files when I chose to install from sd card.
sorry for my english, I'm not a native speaker :silly:
doki81 said:
follow guide in this post http://forum.xda-developers.com/showthread.php?t=2167381
Click to expand...
Click to collapse
ok, I'll do that again. I tried this yesterday already and so I do have a few questions:
from the guide you sent me:
download the advanced stock kernel (contains recovery)
reboot device into fastboot mode
Code:
adb reboot bootloader
now flash the recovery using
Code:
fastboot flash boot kernel.img
[where kernel.img is the name of the file image u downloaded]
thats it!
As I use "adb reboot bootloader" it keeps telling me "error: device not found", even though its connected to PC using fastboot mode and "fastboot devices" shows my Xperia Z as connected in fastboot mode. What do I do wrong?
Second question: Is the advanced stock kernel with recovery the one I already installed? Z_DooMLoRD_insecure_FW-350.img? Or Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img? So which kernel do I use in the last step?
I finished it and I just made some stupid mistake in my procedure (I was alredy wondering how Xperia Z can be so hard to put a new rom into..). I'll write a How-To for newbies the until monday. Thanks for your help so far!
How to install RomAur (and other ROMS) on Sony Xperia Z
This is how I managed to install RomAur at my Xperia Z. After realizing my mistake I noticed it's not much different to other android devices.
1. So first to install kernels and get root I unlocked the boot loader using this really good descriptions:
http://unlockbootloader.sonymobile.com/
http://www.techethon.com/root-sony-xperia-z-tutorial-easy-how-to/
http://forum.xda-developers.com/showthread.php?t=2153261
2. Then I started the device in fastboot mode by pressing volume + while connecting to PC and used fastboot.exe (shift+right click in the containing folder to start cmd) typing in this:
fastboot flash boot Z_DooMLoRD_AdvStkKernel_FW-350_v2.img
IMPORTANT Z_DooMLoRD_AdvStkKernel_FW-350_v2.img was contained in the same folder as fastboot.exe. Maybe there is already another new kernel to do this with, this one worked for me. Starting the device in fastboot mode can also be achieved by usind this command before flashing with the new kernel: adb reboot bootloader
3. Anyway after flashing I typed in this: fastboot reboot
4. Then I've put the zip file onto my micro sd (fat32 formatted, 16gb) and restarted the device disconnected from PC. This is what I've done wrong :silly:
While the device went on I pressed volume + when the SONY screen showed up and the led started to flash in several colors.
5. Now in the menu wiped/cleared/formatted everythin except the external sd-card and installed the "update" by using volume buttons to navigate and power button to confirm.
This is what worked for me. I might have forgotten some stuff so in case there might be something to add, just reply on this!
[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY NOTE 8.0 [2012 MODEL] - Drivers, Root, Recovery + MORE
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports a multitude of Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
SUPPORTED MODELS
GT-N5100 3G/WIFI MODEL
GT-N5110 WIFI ONLY MODEL
GT-N5120 LTE MODEL
Click to expand...
Click to collapse
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.3 [8TH DEC 2014]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
Enable Developer options for usb debugging
Go to Settings, System section, About device and tap on 'Build number' 7 times until it says you are now a developer. You can now go to Settings, System section, Developer options and enable USB debug.
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the device.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the device.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.2).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry).
This feature will be added to the Toolkit after testing has been completed.
----------------------------------------------------------------------------
Q. Does flashing a custom image increase my flash counter?
Any image that is flashed via Odin that has been modified will increase the flash counter that can be viewed in the Download Mode on your device (if booted by holding the Volume Down, Home and Power buttons). You can reset the flash counter using an app by Chainfire called Triangles Away and can find instructions on how to use that in the Downloads section in the Toolkit.
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.
*reserved if needed*
Mskip
thanks for this
is your version of cwm working properly?
thanks
jocko6872 said:
Mskip
thanks for this
is your version of cwm working properly?
thanks
Click to expand...
Click to collapse
I think that's for us us to test and tell him
sefrcoko said:
I think that's for us us to test and tell him
Click to expand...
Click to collapse
It's the same version as provided in the development thread.
i flashed the cwm
but cant do anything
cant even reboot
jocko6872 said:
Mskip
thanks for this
is your version of cwm working properly?
thanks
Click to expand...
Click to collapse
CWM is the experimental port from emwno in *THIS* thread.
I need people to test if the insecure boot image flashes and whether the root process works.
Mark.
madsatan said:
i flashed the cwm
but cant do anything
cant even reboot
Click to expand...
Click to collapse
Flashing custom recovery shouldnt affect the boot process have you tried just holding the power button for about 15 seconds to force a hard reboot?
Are there any lights or anything on the screen?
Mark.
Sorry that i didnt make myself clear
What i was saying is that i boot into cwm
Cant press any fuctions (cant back up or reboot etc)
I had to use power buttom to restar the tablet
Sent from my GT-N5110 using XDA Premium HD app
madsatan said:
Sorry that i didnt make myself clear
What i was saying is that i boot into cwm
Cant press any fuctions (cant back up or reboot etc)
I had to use power buttom to restar the tablet
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
As stated the cwm port is still experimental but it is being worked on by emwno and im sure he will get there.
Has anyone tried the root procedure yet with the insecure boot image? I really need some feedback here.
Mark.
Hey mskip,i just downloaded the toolkit and went through the insecure kernel process with no problems,tho i had already rooted using the Framaroot app. I also installed cwm and booted into it,although it's a little buggy it's useable ,just need something to flash in it now
ktmman said:
Hey mskip,i just downloaded the toolkit and went through the insecure kernel process with no problems,tho i had already rooted using the Framaroot app. I also installed cwm and booted into it,although it's a little buggy it's useable ,just need something to flash in it now
Click to expand...
Click to collapse
Glad its all working ok. Did you go through the ALL-IN-ONE process? Just wondering if you had installed busybox as I need someone to make a NAND backup from the backups section. If you can do that and then post a screenshot of the files (filenames and file sizes) then I can update it to a public version
Mark.
mskip said:
Glad its all working ok. Did you go through the ALL-IN-ONE process? Just wondering if you had installed busybox as I need someone to make a NAND backup from the backups section. If you can do that and then post a screenshot of the files (filenames and file sizes) then I can update it to a public version
Mark.
Click to expand...
Click to collapse
ok,i downloaded Busybox from the market,it looks like its going well,here's the data.
ktmman said:
ok,i downloaded Busybox from the market,it looks like its going well,here's the data.
Click to expand...
Click to collapse
Looks good
Now I just need someone with a full stock firmware flashed that can test the ALL IN ONE process and perform a NAND backup to make sure it works from scratch. Any takers?
Mark.
I will try once I'm home
Sent from my GT-N5110 using Tapatalk HD
n5120
got n5120, lte. can I use tools or I have to wait for n5120 version?
thanx in advance for answer.
goo.im seems to be down. Got a mirror?
thanks mskip
i use your nexus 4 tool kit a lot and was excited to see this one
i had already rooted via the framaroot app. was able to successfully load up CWM recovery (although it needs some help but i see in the other thread its being worked on).
also ran a backup successfully.
Sardo Numspa said:
thanks mskip
i use your nexus 4 tool kit a lot and was excited to see this one
i had already rooted via the framaroot app. was able to successfully load up CWM recovery (although it needs some help but i see in the other thread its being worked on).
also ran a backup successfully.
Click to expand...
Click to collapse
Flash Experimental #4 for your specific device (from my thread). Its working properly now.
Nexus 4 Guide-Unlock Bootloader, Root, Install Custom Recoveries & Custom ROMs/Kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings XDA Members and Guests
We are honored to have an addition of a bunch of new members every day, of which a decent lot is new to our Android custom world. So, if you're viewing this thread, it is because you need guidance in context to Root, Install Custom ROM/Kernels & Custom Recoveries on your LG branded Google Nexus 4. I may have spent tons of hours at this N4 section but I also have my history with Android, going way back when I was also a noob (new comer). Though, I was lucky enough because my fellow community members imparted me with sufficient knowledge to bring on to the basics of the Android custom world i.e Rooting the device, Installing Custom ROMs and Mods. Here I am to give out an helping hand and I want our new entries to feel the way I felt in the beginning; never ignored and forever helped.
So if you’re a noob and you’re reading this, don’t you worry at all, I will take care and hit all the basics inside your head, step by step. I have already done this at the Nexus S section (look here).
I’m sure you’re more curious to get into the Android Development section and flash your desired ROM, I have felt that curiosity but I would advise you to stay calm and give these things some time and little bit of importance too, as then this knowledge will defend you from messing up your devices in the future. Please do not be in a haste, understand the steps or information carefully and then only care to process it. Remember, haste makes waste (someone told me the very same and trust me, I could be the most experienced in making a practical example of this).
Terminology
What is Bootloader and Why do we need to Unlock?
A bootloader is a boot initializing component which is generally locked by the device manufacturer to avoid any messing around with the OS. We need to unlock it for the same reason. Once unlocked it will allow us to change the boot sequence and modify the OS in accordance of our needs.
What is Rooting?
It is a process of gaining root privileges over an Android subsystem. Rooting an Android device is easy in most cases. If you will to Install custom ROMs, kernels, other patches or addons to your Android device, rooting is what you will need. It can be achieved in two ways; either by manual method (using Recoveries) or by automatic method (using toolkit or software) . Here, I am going to follow the manual method.
ClockworkMod & TWRP, what are these?
These are secondary recovery systems created by Koush (Koushik Dutta) & TeamWin, respectively. These add enormous features like wiping partitions, flashing flash-able .zip files like ROMs, kernels, patches etc to the stock AOSP recovery. Visit ClockworkMod website & TeamWin website for more detailed information.
What is a Custom ROM?
These are the aftermarket Android firmware which are not official supported by the OEM (Original Equipment Manufacturer). They are made available to the Android public by Android developers and contributors all around the world. Custom ROMs are either built from Google’s source code i.e AOSP (Android Open Source Project) or are modified versions of the device manufacturer’s ROM (Stock ROMs or Factory ROMs) with additional tweaks and extend functions which are not delivered with the Stock ROMs. Some of the popular Custom ROMs include CyanogenMod (CM), Android Open Kang Project (AOKP), MIUI, Codename Android (CNA), Oxygen, ParanoidAndroid and many more.
What is Custom Kernel?
A Kernel is a bridge between the applications and the actual data processing done at the hardware level, In simple words, it is the communication between the hardware and software of an Operating System. In Android world, Custom Kernels play a vital role since they provide the users with several features including changing CPU frequencies, modifying the boot sequence and boot scripts and other features too.
What are Google Apps (GApps)?
The name speaks for itself. Gapps are Google apps for Android available in flash-able zip format. Most of these applications can now be found and updated via the Google Play Store.Some of the apps include the Google Play Store itself, Google Talk, Google Sync (for adding and synchronizing Google accounts), Google Backup Transport, Car Home, Gmail, Google Maps, YouTube, Google Search, Google Voice Search, Google Music, and Google Docs. In some Custom ROMs, the Google Apps are included. These are usually stock ROMs, smaller or less-common ROMs, or those from areas where intellectual property laws are less commonly obeyed. But many AOSP ROMs, most famously CyanogenMod and AOKP, do not include the Google Apps due to licensing issues. They are after all proprietary code owned by Google and not included in the Android Open Source Project.
Now, lets begin. The first thing we’ll be doing here, is to unlock the bootloader of your Nexus 4, followed by Installing a Custom Recovery, so that later on you can root and Install Custom ROMs/Kernels/Mods easily.
Prerequisites
USB drivers configured properly. You may either use these amazing toolkits [WugFresh?s tookit | mskip’s toolkit] or do it manually using the Google USB drivers delivered with Android SDK (Do it the way you find it easy). Remember, USB drivers in this case doesn’t mean only the drivers to mount the device storage but rather the fastboot and adb drivers too.
Compatible USB data cable.
Android SDK configured (Follow this guide to setup Android SDK and thus it itself configures ADB and all other SDK components)
USB Debugging enabled (Don’t know how? Take a look here)
Backup Device Storage, Messages, Contacts, Calendars etc.
60% or above battery life (This is a recommendation to avoid any uncertain shutdowns during the mentioned process, it might cause issues)
Fastboot binary (Put the file in <sdk_directory>/platform-tools)
Once you have filled in all the requirements, you shall follow further. If you have problem with setting up the prerequisites, please comment and get your issue resolved. Always remember, the more you ask, the more put up to your knowledge and the more you learn.
Unlock Bootloader
Don't want to lose your data after unlocking? Read this.
Reboot your device into bootloader mode. Either manually, by powering off and then pressing Volume Down + Power buttons simultaneously or using the following command in CMD/Terminal.
Code:
adb reboot bootloader
Connect the device to your PC using USB data cable.
Open CMD/Terminal and confirm that the drivers are properly installed and the device is detected by entering the following command
Code:
fastboot devices
The device ID shall be displayed as the output in your shell. If it is so then the response is positive but in case it shows something else, please make sure to properly install the drivers using a different method than that you used earlier.
Type in the following in CMD/Terminal to initiate the unlocking process
Code:
fastboot oem unlock
You will now be prompted with a warning message, use the volume keys to highlight Yes and select it using the power button. Then within a matter of seconds, your device shall be unlocked.
To confirm that it is unlocked, look over to the text in front of Lock State and it should be unlocked.
You’ve successfully unlocked.
What? Too easy? Yes, indeed. The following is as easy too.
Install Custom Recovery
We’ve 2 custom recoveries available yet for our Nexus 4 viz ClockworkMod and TWRP. ClockworkMod or CWM (in short) comes in 2 variants (Touch UI based & Non-Touch UI based). Below I have mentioned on how to flash each one of them using fastboot. For more info about these two recoveries, visit ClockworkMod and TeamWin websites.
Reboot your device into bootloader mode. Either manually, by powering off and then pressing Volume Down + Power buttons simultaneously or using the following command in CMD/Terminal.
Code:
adb reboot bootloader
Download the latest build of your desired recovery [CWM | TWRP]
Place the downloaded recovery image (.img) file on your desktop.
If in Windows, open CMD and cd it to the desktop using the following command
Code:
cd Desktop
If in OS X or Linux, open terminal and cd it to the desktop using the following command
Code:
cd ~/Desktop
To flash ClockworkMod Non-Touch, type in the following command:
Code:
fastboot flash recovery recovery-clockwork-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
To flash ClockworkMod Touch, type in the following command:
Code:
fastboot flash recovery recovery-clockwork-touch-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
To flash TWRP, type in the following command:
Code:
fastboot flash recovery openrecovery-twrp-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
Once flashed, you will prompted on the CMD/Terminal itself.
Now, either reboot your device by using volume keys to highlight Reboot and select using Power button or reboot into the recovery by selecting Recovery mode.
Voila! The next to follow is to root or directly flash a Custom ROM, which is already rooted.
Rooting
Not everyone and each one of us like Custom ROMs. Some users might prefer high stock stability over the features offered by Custom ROMs. and that’s completely normal. But, what if you have an App that requires Root privileges or may be, you need to access the System partition of your device to make certain modifications of your own? This is where the process of Rooting enters. Now when you already know what Rooting is, we shall head further and follow another set of very-simple instructions to root your Nexus 4.
Download the latest SuperSU flash-able root package. [Chainfire's SuperSU Thread]
Connect your device to the PC via USB cable.
Transfer the downloaded file to a suitable location in the device.
Do not disconnect the device.
Open CMD/Terminal and type in the following command:
Code:
adb reboot recovery
This will boot your device directly into recovery mode.
You may now disconnect the device.
If you are using CWM, tap on install zip from sdcard > choose zip from sdcard and select the CWM-SuperSU-v0.93.zip. When prompted select Yes to start the flashing process.
If you are using TWRP, tap on Install and select the CWM-SuperSU-v0.93.zip. Slide the circular button to start the flashing process.
When the flashing process has finished, select reboot system now (In CWM) or Reboot > System (In TWRP) to reboot your device.
Congrats! You have successfully rooted your device. Go ahead and use any App that requires Root permissions.
Installing Custom ROM
Its simple, very much simple. All you got to do, is to choose a Custom ROM and simply flash it via your custom recovery.
The very first step is to choose a Custom ROM that fits all your needs and serves you with your desires. When chosen, download the ROM file (flashable zip).
NOTE: Every ROM here at this section is worth and is a result of hardwork of developers/team. Please do not criticize any ROM for any reason. Maintain the forum spirit by encouraging people.
Download the suitable GApps package corresponding to the Android version of your ROM [Link]
In case, the developer has provided specific modified GApps package, download that. Then there is no need to download the GApps package from step #2
Connect your device to the PC via USB data cable.
Transfer the ROM & GApps zip to the device. Its is recommended to put the files in the root of your device storage for convenience.
Disconnect the device,
Power off. Press the Volume Down and Power keys together to boot into the Bootloader mode.
Use the volume keys to highlight Recovery mode and select it using the Power button. Your device will then boot itself into Recovery mode.
Flash using CWM
wipe data/factory reset
wipe cache partition
Go to "mounts and storage" > "format /system" "format /boot"
Go to "install zip from sdcard" > "choose zip from sdcard" > select your ROM .zip file that you placed in step #6. Flash it.
Gapps are the next to be flashed just after flashing the ROM. So, flash Gapps following the same way as the ROM. further if your are provided any add-on in a flash able zip format you can flash it the same way after flashing the ROM and GApps successfully.
Once everything has flashed successfully, select "reboot system now".
Flash using TWRP
Go to "Wipe" > "Advanced" and "Factory Reset".
Go to "Install" > choose the ROM .zip file and flash it.
Gapps are the next to be flashed just after flashing the ROM. So, flash Gapps following the same way as the ROM. further if your are provided any add-on in a flash able zip format you can flash it the same way after flashing the ROM and Gapps successfully.
When flashed, go to "Reboot" > "System".
Your phone will now boot into the custom ROM.
Install Custom Kernel
People often prefer using a Custom Kernel rather than that already delivered with the ROM. For the available kernels, head over to Nexus 4 Original Development section. Every kernel is unique in its own terms, so make a choice. If you’re not satisfied with the combination, move on and try some other kernel.
Choose a custom Kernel and download its flashable zip.
Connect your device to the PC via USB data cable.
Transfer the Kernel flashable zip to the device. Its is recommended to put the file in the root of your device storage for convenience.
Disconnect the device.
Power off. Press the Volume Down and Power keys together to boot into the Bootloader mode.
While on the Bootloader screen, use the volume keys to highlight Recovery mode and select it using the Power button. Your device will then boot itself into Recovery mode.
Flash using CWM
- Select "wipe cache partition"
- Tap on "advanced" and select "Wipe Dalvik Cache"
- Tap on "install zip from sdcard" > "choose zip from sdcard". Now browse and select the kernel zip package that you placed in your storage root during step #3.
- Select "Yes" when prompted to start the flashing process.
- Your Kernel will now flash to your OS and replace your current kernel.
- When it has successfully flashed, select "reboot system now".
Flash using TWRP
- Tap "Wipe" > "Advanced Wipe" and tick "Dalvik Cache" & "Cache".
- Slide the button at the end of the screen to start the wiping process.
- Tap on "Install" > now browse and select the kernel zip package that you placed in your storage root during step #3.
- Slide the button at the end of the screen to start the flashing process.
- Your Kernel will now flash to your OS and replace your current kernel.
- When it has successfully flashed, tap to "Reboot" and select "System".
You now have Custom Kernel installed on your Nexus 4.
NOTE: Before choosing and flashing any Custom Kernel, make sure its compatible with your present Android version.
I hope this guide has helped you. I would be proud, if anyone has received any kind of fruitful knowledge/guidance from this thread.
In case you get stuck anywhere, feel free to comment and ask. Or if I've missed something or may if I am wrong somewhere, please do let me know.
:good:Good Luck with going custom on your Nexus 4:good:
Hey awesome tutorial....nice and detailed.....plz can u make a tutorial using the automatic method(toolkit)
Thanks
dsjd said:
Hey awesome tutorial....nice and detailed.....plz can u make a tutorial using the automatic method(toolkit)
Thanks
Click to expand...
Click to collapse
You won't learn anything using a toolkit and if something goes wrong you won't know how to fix it. XDA is a place to learn
Sent from my Nexus 4
spaceman860 said:
You won't learn anything using a toolkit and if something goes wrong you won't know how to fix it. XDA is a place to learn
Sent from my Nexus 4
Click to expand...
Click to collapse
So its safer to do it manually ?
dsjd said:
So its safer to do it manually ?
Click to expand...
Click to collapse
Everything is safe for a Nexus. But, this guide will provide you with suitable knowledge. :good:
dsjd said:
So its safer to do it manually ?
Click to expand...
Click to collapse
Yes and if you need help just ask
http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4
Nice guide. I have one question.
In this guide: http://forum.xda-developers.com/showthread.php?t=2018179 it mentions that after flashing the custom recovery, the stock recovery may restore itself and overwrite the custom one. Is it necessary to do anything to stop this from happening ?
Sent from my HTC Desire using xda app-developers app
Can u plz giv little more detailed steps on installing drivers?
chromium96 said:
Nice guide. I have one question.
In this guide: http://forum.xda-developers.com/showthread.php?t=2018179 it mentions that after flashing the custom recovery, the stock recovery may restore itself and overwrite the custom one. Is it necessary to do anything to stop this from happening ?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
The newest versions of custom recovery prevents that from happening
Sent from my Nexus 4
Hey ...i just wanted to know if there are any safety-nets that i can use ...like backups or something?
dsjd said:
Hey ...i just wanted to know if there are any safety-nets that i can use ...like backups or something?
Click to expand...
Click to collapse
The first thing to backup is your contacts, messages and storage. Up after flashing a Custom Recovery, it is highly advised to take a nandroid backup using the recovery.
DJBhardwaj said:
The first thing to backup is your contacts, messages and storage. Up after flashing a Custom Recovery, it is highly advised to take a nandroid backup using the recovery.
Click to expand...
Click to collapse
Thanks for the reply....do u think this is a safe tool to use http://www.nexus4forum.com/forum/ne...ck-up-your-entire-device-without-rooting.html ? or plz can u suggest sum good ones ...
dsjd said:
Thanks for the reply....do u think this is a safe tool to use http://www.nexus4forum.com/forum/ne...ck-up-your-entire-device-without-rooting.html ? or plz can u suggest sum good ones ...
Click to expand...
Click to collapse
Its good to go.
Here are other two of the very famous toolkits; mskip's toolkit & Wug's toolkit.
DJBhardwaj said:
Its good to go.
Here are other two of the very famous toolkits; mskip's toolkit & Wug's toolkit.
Click to expand...
Click to collapse
and how can u make out if the drivers are installed properly ?Do i enable usb thenthering mode before or after i install the drivers ?
Thanks for your very good job!
Sent from my Nexus 4 using xda premium
Does bootloader version, or android version matter? Or will everything work regardless of any versions?
Sent from my HTC Desire using xda app-developers app
chromium96 said:
Does bootloader version, or android version matter? Or will everything work regardless of any versions?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Doesn't matter it will work
Sent from my Nexus 4
dsjd said:
and how can u make out if the drivers are installed properly ?Do i enable usb thenthering mode before or after i install the drivers ?
Click to expand...
Click to collapse
Connect your device to the PC. Make sure USB Debugging is switched on.
Open CMD/Terminal window and type the following command:
Code:
adb devices
If it shows a device ID, then you've your drivers properly setup.
I have another question. Will unlocking the bootloader and flashing twrp wipe the phone?
Sent from my HTC Desire using xda app-developers app
chromium96 said:
I have another question. Will unlocking the bootloader and flashing twrp wipe the phone?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Yes unlocking the bootloader will wipe the phone completely.
Sent from my Nexus 4
[ROM][LB&UB][4.3] Rooted, Deodexed & Zipaligned Stock 10.4.1.B.0.101 V3 [19/02]
Rooted, Deodexed and Zipaligned Sony stock 10.4.1.B.0.101 4.3 Flashable Rom V3 (19/02)!
For Locked and Unlocked Bootloaders
Hi Everyone,
Here is a rooted, deodexed and zipaligned stock 10.4.1.B.0.101 (Based on Generic UA) rom. A deodexed rom makes it easier to modify apks and jars without having to worry about those pesky odex files.
Hope you like it
Xposed
Xposed Framework has been integrated into the ROM. Xposed allows ROM modification without having to go through the daunting process of modifying APKs. After you've flashed the ROM, see the second post for instructions on how to activate Xposed.
Rom features:
> Based on the official 4.3 Generic UA firmware
> Rooted with the latest SuperSU
> Deodexed for easier modding
> Zipaligned for optimised RAM usage
> Init.d script support (scripts can tweak system settings for better performance)
> Xposed Framework included for the ultimate tweaking experience
> Stable, smooth and fast
> XZDualRecovery included
Changelog
Stock 10.4.1.B.0.101 Rooted, Deodexed & Zipaligned V3 (19/02)
-Based on the official 4.3 10.4.1.B.0.101 Generic UA firmware
-Changed Settings layout
-Removed GravityBox
-Cleaned up some stuff
Click to expand...
Click to collapse
Stock 10.4.B.0.569 Rooted, Deodexed & Zipaligned V2 (07/01)
-Based on the official 4.3 Generic UK firmware
-Bug fixes, including the infamous Language & Input FC!
-Added Xposed Framework and GravityBox in Settings
-Latest SuperSU v1.86 and root fixed
Click to expand...
Click to collapse
Installation instructions:
Root:
Before you can start flashing ROMs you need root. First you need to download a stock 10.3.1.A.2.67 FTF, this one for example - http://forum.xda-developers.com/showthread.php?t=2512422
After you've flashed it, use this guide to root it - http://forum.xda-developers.com/showthread.php?t=2386405
Fresh installation, if you're coming from any 10.3.1.A.2.67/.244 stock based ROMs:
*Install the latest version of Dual Recovery before flashing.*
Copy Stock_10.4.1.B.0.101_deodexed_V3_SuperHanss.zip to your microSD
Download this file C6603_10.4.1.B.0.101_Stripped.ftf and drop it into your Flashtool/firmwares folder on your PC
Backup any important data to your microSD
Boot into recovery and do a nandroid backup first
Do a Factroy Reset
Flash the ROM but DON'T REBOOT AFTER IT'S FINISHED, instead turn off the phone, in CWM it's in Advanced>Power Off, in TWRP it's in Reboot>Power OFF *if after pressing "Power Off" it says "Disable Recovery Flash?" just select 'No'*
Connect your phone in Flashmode (hold volume key down while plugging in USB)
Open Flashtool and flash everything in the 'C6603_10.4.1.B.0.101_Stripped.ftf' file
Turn on the phone and enjoy!
See the second post for instructions on how to activate Xposed
Fresh installation, if you're coming from any CM or AOSP based ROMs:
Copy Stock_10.4.1.B.0.101_deodexed_V3_SuperHanss.zip to your microSD
Download this file C6603_10.4.1.B.0.101_Stripped.ftf and drop it into your Flashtool/firmwares folder on your PC
Backup any important data to your microSD
Boot into recovery and do a nandroid backup first
Do a full wipe
Flash the ROM but DON'T REBOOT AFTER IT'S FINISHED, instead turn off the phone, in CWM it's in Advanced>Power Off, in TWRP it's in Reboot>Power OFF *if after pressing "Power Off" it says "Disable Recovery Flash?" just select 'No'*
Connect your phone in Flashmode (hold volume key down while plugging in USB)
Open Flashtool and flash everything in the 'C6603_10.4.1.B.0.101_Stripped.ftf' file
Turn on the phone and enjoy!
See the second post for instructions on how to activate Xposed
If you're coming from my previous version (V2) or any other 10.4.B.0.569 based ROM:
Copy Stock_10.4.1.B.0.101_deodexed_V3_SuperHanss.zip to your microSD
Download this file C6603_10.4.1.B.0.101_Stripped.ftf and drop it into your Flashtool/firmwares folder on your PC
Backup any important data to your microSD
Boot into recovery, wipe cache and dalvik cache
Flash the ROM but DON'T REBOOT AFTER IT'S FINISHED, instead turn off the phone, in CWM it's in Advanced>Power Off, in TWRP it's in Reboot>Power OFF *if after pressing "Power Off" it says "Disable Recovery Flash?" just select 'No'*
Connect your phone in Flashmode (hold volume key down while plugging in USB)
Open Flashtool and flash everything in the 'C6603_10.4.1.B.0.101_Stripped.ftf' file
Reboot and enjoy!
See the second post for instructions on how to activate Xposed
Downloads:
Stock_10.4.1.B.0.101_deodexed_V3_SuperHanss.zip (773 MB)
Mirror - Thanks @mlm1102003
Credits:
@[NUT] for Dual Recovery
@rovo89 for the Xposed Framework
@Chainfire for SuperSU
Please hit the thanks button if you like this rom!
Add-ons & Mods
Add-ons/Mods:
AOSP style nav bar buttons - Download
5 button nav bar. Thanks to @Rajeev for his tutorial - Download
Stock 3 button nav bar - Download
Xposed:
Xposed Framework v2.5 update - Download
How to activate Xposed Framework:
Go to Settings>Xposed
Select 'Framework' then 'Install/Update' and Grant it root permission
Then select 'Reboot' from the same screen
That's it!
How to activate Xposed Modules:
*Before activating Xposed modules (GravityBox etc.) you need to activate Xposed Framework, follow the steps above*
Go to Settings>Xposed Installer
Select 'Downloads' and download the desired modules
Select 'Modules'
Tick the box next to the module
Then go to back to the Xposed Installer menu
Select 'Framework' then select 'Reboot'
That's it!
Xposed Updates:
At this current time only Xposed Installer v2.4.1 is working with 4.3 for the XZ. Only use the current version and ignore future Xposed Installer updates. If there is a new version that works with 4.3 I will provide an OTA update.
You can still update the Modules, just not the Xposed Installer
CWM Failed with error7
in TWRP - install failed
in CWM - aborted (status 7)
Doh, not working mate... Will try next version
Sent from my C6603 using XDA Premium 4 mobile app
Damn it sorry about that guys, I'll fix it today and reupload.
Sent from my Nexus 5 using XDA Premium 4 mobile app
nkhater said:
CWM Failed with error7
Click to expand...
Click to collapse
JediRAMA said:
in TWRP - install failed
in CWM - aborted (status 7)
Click to expand...
Click to collapse
Does it give a specific error, like a message of some sort?
Drummerjed said:
Does it give a specific error, like a message of some sort?
Click to expand...
Click to collapse
If you get error 7 you probably need to update your recovery to the latest version.
Sent from my LG-V500 using Tapatalk 4
Can't wait!
i believe status 7 error is a device id check. so if your using a 6602 and this is for 6603 you will get an error. i think the dev needs to take the device id check out of the updater script
skinsfanbdh said:
i believe status 7 error is a device id check. so if your using a 6602 and this is for 6603 you will get an error. i think the dev needs to take the device id check out of the updater script
Click to expand...
Click to collapse
The script didn't have that from the start, Android Kitchen doesn't add device check to the the script. The problem is that there are multiple reasons for a Status 7 error, which is why I asked if there was an error message that states the problem.
I'm uploading it again, it sucks not being able to test it myself
about kernel : does this rom work with Doomkernel v18 ?
Worked here.
Screenshots please
Enviado do meu C6603 através de Tapatalk
rsimas said:
Screenshots please
Enviado do meu C6603 através de Tapatalk
Click to expand...
Click to collapse
Still uploading the fixed ROM! In the meantime see here - http://www.flickr.com/photos/[email protected]/sets/72157638591600843/
Drummerjed said:
Still uploading the fixed ROM! In the meantime see here - http://www.flickr.com/photos/[email protected]/sets/72157638591600843/
Click to expand...
Click to collapse
wait for your fixed rom with patient, before that can I use this as my ROM's base?
@Drummerjed
The kitchens binary will not work with the Z (if it that is the one you used), you will need a good Z binary to replace it with (like from any other ROM in this section)
The script also needs to detail the right partitions, again, lots of Z updater scripts to use to make sure it's doing the right thing for this device
Look forward to your new version.
OP updated with download links
Hope it works better How to root latest 259 stock?
Sent from my C6603 using Tapatalk
bariz143 said:
Hope it works better How to root latest 259 stock?
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Follow the instructions in the OP, this ROM includes root but requires a root fix that you need to flash after flashing the ROM
dat response time
The Gionee M2 has a MT6582 Mediatek chipset.
Follow the Gionee guide on their site for upgrading to KitKat, before you start the process, replace the recovery.img file in the ROM file you downloaded and extracted and replace it with a CWM or Carliv touch recovery file that works for the JB versions, this will give you a custom recovery (power button + up key when booting)
The 800Mb+ KitKat ROM update file has about 300mb of pure bloatware, unknown games etc.
ROOT:
Enable USB debugging
Download SuperSU from the playstore (we will use it to replace the chinese SU file later)
Download RootMaster (google it), this is an apk file probably made by the same chinese dev's who made Vroot
Make sure wifi is on, run RootMaster, all text is chinese, but the press to root button is english, it works, if it doesnt the first time try again (dont press anything else, it has a ton of crapware)
It should prompt that your phone is rooted, give it some time, it actually downloads a chinese version of SU
Now run SuperSU, it will replace the chinese version with the familiar english SuperSU ( although the chinese SU app with the lion emblem and chinese text will still be on your phone)
I recommend doing a full factory reset at this stage and using a root uninstaller app to remove all traces of this chinese RootMaster SU
Xposed Framework:
The amigo system resources interferes with Xposed you can still get it to install the framework by first installing the Xposed apk and then going to the settings of the Xposed installer and checking the box "Disable resources API", this will mean GravityBox WILL fail.
-------------------------------------------------------
Framaroot Doesn't work anymore
The best way to root this is to use Framaroot, Barahir exploit.
Although the Framaroot page on XDA does not list this as a compatible device (yet) it works really well.
All credits for Framaroot go to alephzain : here
------------------
This still works
BACKUP ROM WITH MTKTOOLS:
Download the awesome MTK Droid Root & Tools by rua1 from here
There are many detailed tutorials for using the actual tool ( I used v2.5.3) with detailed pictures etc., I wont reproduce them here, but before you read and follow the tutorials, make sure, your phone is rooted, you have the ADB drivers for your MT6582 chipset and the microsd card you put inside your phone is formatted inside the phone otherwise the backup will throw an error
Create & Install CWM:
Dev rua1's MTKTOOLS can also create a CWM image automatically from the boot.img that is created in the above step. There are detailed tutorials already available on many sites that show step by step how to do this. Installing CWM is up to you, either via Mobile Uncle Tools from the playstore (recommended) and the freshly minted CWM image or via SP Flash Tools using the Backup of ROM created with MTKTOOLS
Getting to Recovery - Hardware Keys
Getting directly to CWM when the phone is shutdown requires the following key press combination:
For KitKat:
Power button + UP volume button gets you to a custom recovery (should you have one)
Power button + down volume button gets you into Factory Mode (Gionee Factory Mode)
For JB:
Press Volume Keys UP/DOWN and Power button simultaneously
Let go once you reach a screen that shows 3 options, here choose recovery, it will then boot directly to CWM
Can u provide M2 Stock Rom Link ???
Sent from my M2 using XDA Premium 4 mobile app
---------- Post added at 06:34 PM ---------- Previous post was at 06:10 PM ----------
MTK droid tool 2.5.3
http://www.mediafire.com/?6z9acf5um65cuj2
Sent from my M2 using XDA Premium 4 mobile app
Want rom for m2
i want custom rom for my gionee m2
Xposed Framework & Stock / Custom ROM's
Xposed Framework works fine on the rooted Gionee M2.
While several modules (like Xprivacy) work, GravityBox via Xposed download fc's, use the GravityBox Apk instead
As for M2 Stock ROM, I suggest take a backup of your own phone ROM, there is little chance that Gionee will make stock ROM's available for M2 (a very new device) anytime soon.
For other Gionee ROM's (stock) external sites like androidXDA have a few ROM's for download but none for M2
There are no custom ROM's for M2, if you want a smoother/cleaner experience try uninstalling some bloatware and change the DPI using an Xposed module.
Request
Hey, it would be nice if you could customize the backing up ROM and re flashing tutorials for the for the m2. It would be quite helpful, you know which set of options to choose etc... beginners like me could make a mistakes with regards to those, since you have already done these procedures your experience could prove valuable. also do you know if the bootloader is unlocked on this phone? and how to check that?
rjspark89 said:
Hey, it would be nice if you could customize the backing up ROM and re flashing tutorials for the for the m2. It would be quite helpful, you know which set of options to choose etc... beginners like me could make a mistakes with regards to those, since you have already done these procedures your experience could prove valuable. also do you know if the bootloader is unlocked on this phone? and how to check that?
Click to expand...
Click to collapse
Being a long time lurker on XDA, I've not managed to rack up enough posts to link to external sites, I tend to find most answers by lurking
But here goes (credits go to the original tuts on other sites): Warning, you may brick your device. This will void your warranty. You should know the risks.
Pre-requisite Steps:
Enable debugging mode on your phone. From your homescreen, tap the Menu button > Settings > Development. Tap 'Debug Mode' and make sure it's checked
Root your M2 using Framaroot, use Barahir exploit
Install Busybox from the Playstore on M2
Download MTK Droid Tools v2.5.3 from XDA, chrome tags this as malware (its not), if your AV detects this as malware then dont worry, its a false positive , disable your Anti Virus tool for good measure for the remainder of your backup job, unzip the MTK tools you downloaded
Make sure the microsd card you put inside your phone is formatted inside the phone otherwise the backup will throw an error - this step is impt.
Connect M2 via USB cable to your PC,Download the ADB drivers for M2, use PDANet (google it) and run it, ADB drivers should get automatically installed; this step is critical, so make sure it works
BACKUP ROM WITH MTKTOOLS:
Go into the extracted MTK Droid Tools folder and right-click on 'MTKdroidTools.exe'. Select 'Run as administrator'.
Wait while MTK Droid Tools communicates with your phone. You'll eventually see the main screen come up with all of your phone's information. Look in the bottom left hand corner of the main window, you should see a green square (if it's yellow, click the 'root' button in MTK Droid Tools, this may trigger SuperSU on your phone to ask you for granting it root, grant it)
In the main menu of MTK Droid Tools select the 'Root, Backup, Recovery' tab
Click the 'Backup' button. MTK Droid Tools will start to read all the data from your phone - this takes a long long time, the log is shown on screen, (if it hangs for very very long time (>45mins) on some step (like backup of system.img) you can pull the USB cable out of the phone and restart it)
After it's finished reading back the ROM, another window will pop up asking you if you'd like to compress the image. Select 'Yes'. This will pack it up into a zip and then let you know it's finished.
CREATE YOUR CWM & INSTALL:
Go to the playstore and download Mobileuncle MTK Tools
Connect the phone to PC via USB (if not connected already) and run the MTKDroidTool as administrator
Go to 'root, backup, recovery' tab
Tick the 'To choose the boot.img file' option - the boot.img got created when you took the backup of your ROM, all files from the ROM backup process are saved inside the MTK Tools folder
Click the 'Recovery and Boot' button
Look for the 'boot.img' file and then open it
You will be asked whether to create the CWM recovery automatically, select 'yes'
MTKDroidTools will prompt you whether to install patched files to the phone, say 'No, then it will prompt you if you want to install the CWM recovery that was created, say "No" - we will use MobileUncle Tools for this, its much cleaner
The process fill be finished, and you can now quit MTKDroidTools
In MTKDroidTools folder, you will see a new folder named 'recovery', and in the folder, you will see two .img files; one with the prefix 'boot' in it, and another one with the prefix 'recovery' in it, copy just the .img file with the prefix 'recovery' to the root of your microSD card
Start MobileUncle Tools in your phone, give it root, its a chinese app, but has english title names as well, select the 'Recovery Update' option, select the recovery .img file you have copied to the root of your microSD card, it will prompt you if you really want this, say 'OK'
The flashing process will run, and then you will be asked whether to boot into recovery mode, say yes and you will boot to CWM, you can now take a nandroid backup as well
Like I mentioned earlier, I'm a lurker on XDA, not a dev, so I may not be able to help beyond this
I have problem in CWM whenever I tried to mount Usb storage it gives error as :
"E:unable to open ums lunfile(no such file or directory)"
I have tried to port Cannibal Open touch recovery as well as Carliv but I think in our phone mout points are conflicting with default CWM mount points. If anyone have any solution most welcome for solution I am ready with Custom Roms for our Phone Gionee M2 but strucked in CWM ,if CWM will not work than we will be not able to flash any ROM.
Re:EDIT
ALL PROBLEM SOLVED!!!!!!
New Touch Based Carliv Recovery
Click HERE
NEW ROM LINKS ADDED
CLICK HERE
OR
CLICK HERE
Shivam Bhalla said:
New Touch Based Carliv Recovery
Click HERE
Click to expand...
Click to collapse
Successfully flashed this Carliv recovery img, in my Gionee m2. want to try new OS:laugh:
Guys check out Miui ported by Arnab
http://forum.xda-developers.com/showthread.php?t=2711816
OP plz mention these 3 roms in the first post! i hope more development is seen for Gionee M2
very good
very good thread helped me alot
rishiandri said:
Guys check out Miui ported by Arnab
http://forum.xda-developers.com/showthread.php?t=2711816
OP plz mention these 3 roms in the first post! i hope more development is seen for Gionee M2
Click to expand...
Click to collapse
installed today but reverted back to ASOP Rom, this rom needs some updates and bugfixs,
Scatter File of Gionee M2
Can anyone please give me scatter file of Gionee M2...
Kalpesh Sharma said:
Can anyone please give me scatter file of Gionee M2...
Click to expand...
Click to collapse
enjoy
Thanks for the scatter file.....
Anyone plz. port SamFlare V5 to gionee m2
Here is the link for the ROM
http://forum.xda-developers.com/showthread.php?t=2530755
Error with borohir with frama 1.9.2 su
Sent from my M2 using XDA Premium 4 mobile app
Try with Framaroot 1.9.0 "barahir".. I rooted my phone with this version and also rooted 3 more with same.
Sent from my Gionee M2.
Use Framaroot 1.9.2 And Click Barahir to root your gionee m2....
Hit THANKS if i helped u....