Related
{
"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"
}
Setup, Preparation and Prerequisites
Basic tasks that I may refer to throughout this guide:
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
Enter the bootloader - Turn the phone off. Hold volume down + power. The bootloader is also known as fastboot mode.
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long (5-15 minutes), but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Driver Installation - Try this first, but if that doesn't work look here. Still having issues? Give this a try. None of these working? Hopefully this does the trick.
Downloads
Download a custom recovery of your choice and the SuperSU zip below. Place both files (recovery image and root zip) in the platform-tools folder located on your desktop within the android-sdk-windows folder.
Custom Recovery:
TeamWin Recovery Project (TWRP) or ClockworkMod (CWM)
Root:
SuperSU
Information
Rooting a nexus device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in my opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has. Using a toolkit will only make things worse in the long run...learn to do it properly. It has been proven that every time you use a toolkit, god kills a kitten. Save the kittens.
If you are confused by anything in this guide, I would highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also I'd suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understand? Good...lets begin:
1. Unlocking Bootloader
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Plug the phone into your PC, then open a command prompt window window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
On the phone a screen should pop up asking whether or not you would like to unlock the bootloader. Use the volume rockers to highlight "Yes" then press power to confirm the action.
After the above command has finished excuting, run the following (DO NOT skip this step, it is more important than you think):
Code:
fastboot reboot
The phone will reboot. Next you will be presented with a screen containing an android logo and a progress bar (this may take up to ten minutes to complete). Wait until the phone has fully booted up into android, then proceed onto the next section of the guide.
Close the command prompt window.
2. Installing a Custom Recovery
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that you should place the file in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it. After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Close the command prompt window.
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock rom
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. Leave the phone at the home page of the custom recovery.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Instructions for ClockworkMod (CWM):
install zip from sdcard > choose zip from sdcard.
Next, browse to the location where you previously copied the SuperSU zip and select the it.
To confirm the installation, scroll down to "Yes" and select it. The installation shouldn't take very long, and once it has completed you may reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the Nexus 5 Android Development and Nexus 5 Original Android Development section) onto the phone (remember the location where you copy it to)
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. To install a custom rom the general procedure to follow is: factory reset, wipe cache + dalvik cache, flash ROM, flash GApps. Here are the recovery specific instructions:
Instructions for TeamWin Recovery Project (TWRP):
Wipe > Swipe to Factory Reset
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Instructions for ClockworkMod (CWM):
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
install zip from sdcard > choose zip from sdcard > navigate to the location of the rom > select the rom > confirm the installation by selecting "Yes"
After that you may install the GApps using the same method for flashing the rom, and finally reboot the phone.
Keep in mind that the first boot after installing a custom rom & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted...Plus you saved a kitten. Enjoy
Troubleshooting & FAQ
Why am I seeing a red triangle with a dead android when booting into recovery even after I flashed a custom recovery?
What you are seeing is the stock recovery, meaning that the custom recovery that you flashed did not install correctly. Try the following suggestions:
Make sure you are using the USB cable that came with your phone. Only use other ones, if the stock one isn't working
Try using different USB ports. USB 2.0 ports (the ones that ARE NOT blue) are preferable. USB 3.0 ports (the blue ones) may cause problems with connectivity.
If you are on a desktop, use the ports on the back of the tower instead of the ones in the front. These ports are directly connected to the motherboard, rather than the ones in the front which are usually attached to a header cable which then indirectly connects to the motherboard.
My phone wont boot into android. I can only access the bootloader and custom recovery. What do I do?
Suggestion 1: Factory reset via recovery.
TWRP Instructions:
Boot into recovery
Wipe > Swipe to Factory Reset
Reboot
CWM Instructions:
Boot into recovery
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
Reboot
If that doesn't work continue onto Suggestion 2.
Suggestion 2: Push a ROM to your phone and flash it.
Download a ROM onto your computer. If you don't have time to look for a ROM, just download the stock ROM.
Move the downloaded ROM onto your desktop, and rename the file to "ROM.zip" (without the quotation marks)
Boot phone into recovery
Open command prompt and run the following commands:
Code:
cd Desktop
adb push ROM.zip /sdcard/
Wait for it to finish copying the file, then flash the ROM. If you need further details on how to flash a ROM take a look at the OP, section 3. Rooting, Option B)
If that doesn't work continue onto Suggestion 3.
Suggestion 3: Flash the factory images.
Flash the factory images
My phone wont boot into android. I can only access the bootloader. What do I do?
Flash the factory images
My phone exploded. What do I do?
Tape it back together then flash the factory images
Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk
dombera said:
Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
Awesome, thx
Sent from my Nexus 4 using Tapatalk
This is awesome, will come in handy.
Sent from my HTC Desire using XDA Premium 4 mobile app
Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
---------- Post added at 01:43 AM ---------- Previous post was at 01:41 AM ----------
Xero258 said:
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!
Click to expand...
Click to collapse
If you unlock bootloader & root, and modify some system files, OTAs may not be able to pass some pre-install checks, at least this has happened to me on N4 before. I added one line to /etc/build.prop, also one of the older SuperSU versions had to be uninstalled for pre-install OTA checks to pass.
Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
Click to expand...
Click to collapse
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.
I see some Desire folks
Did u order one chromium?
Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.
talz13 said:
Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.
Click to expand...
Click to collapse
If you wipe cache exactly after you unlock the bootloader, without booting, no.
Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
Not yet. Hoping to eventually get it though.
Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful
Click to expand...
Click to collapse
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app
Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
I'm not a really famous desire user but yes I bought it. Did you buy it to? Happy to see some other desire users.
Sent from my HTC Desire using XDA Premium 4 mobile app
Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?
boysetsfire said:
Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?
Click to expand...
Click to collapse
It should work fine, but whats wrong with booting it up for the first time?
Chromium_ said:
It should work fine, but whats wrong with booting it up for the first time?
Click to expand...
Click to collapse
Nothing wrong, just the laziness of not wanting to do the initial setup two times
Chromium_ said:
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app
Click to expand...
Click to collapse
abaaaabbbb63 said:
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.
Click to expand...
Click to collapse
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?
Whyzor said:
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?
Click to expand...
Click to collapse
Yes that is correct, they do not boot. I will update the OP now, sorry for the confusion.
Originally I had read the following threads and it seemed that they were somewhat functioning, but it is now confirmed that neither one boots.
TWRP
CWM
Hello,
I know there are some tutorials for this already but I felt like they missed out a few steps that might not be obvious to some who are new to this.
This tutorial applies to all of Android One Device (Micromax Canvas A1, Karbonn Sparkle V Blue, Spice Mi-498 Dream Uno).
Unlocking bootloader will lead to formating of your phone. The stuff inside your sd card is safe but all your apps and their data will be deleted.
Unlocking bootloader:
1. Download Universal ADB Driver installer from here.
2. Connect your phone and run the Universal ADB Driver installer. Click 'Install' button and a warning should pop up. Just click "Install anyway" and it should look like this:
{
"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"
}
3. Download ADT Bundle from here for Win-32 Bit and from here for 64-Bit . If you are unsure which version of windows you have just download the 32-Bit one.
4. Extract the zip file in your C:\ drive like this (You can install it wherever you like but this tutorials assumes this location for simplicity). Add adb and fastboot to system path by following this tutorial . This will allow you to run adb and fastboot commands from any location on cmdline.
3. Switch off your phone. Now, Press POWER BUTTON + VOLUME UP button for about 5 seconds. A menu should appear. Note: VOLUME UP allows to navigate the menu (move down the menu). Press VOLUME DOWN button for selecting/choosing fastboot. On your phone, it should say something like
Code:
=> FASTBOOT MODE...
Connect your phone to the computer if it wasn't already.
4. (Assuming Win 7) Click on start menu > Search for 'Command Prompt' and right click and select 'Run as Administrator'.
5. On command prompt, Type:
Code:
fastboot devices
If it shows something, that means we can proceed to unlocking bootloader. Otherwise, it means that the driver was not installed correctly.
6. Now, Type the following commands:
Code:
fastboot oem unlock
fastboot format userdata
fastboot reboot
Now, your bootloader is unlocked.
Install a custom recovery.
1. Download custom recovery from this thread.
2. Place the download file, 'recovery.img' file in C:\ drive. (Again, you can place it anywhere but this tutorial assumes this path).
3. Run the following command (Assuming already in fastboot mode again. If not, follow the above steps to go to fastboot mode). :
Code:
fastboot flash recovery c:\recovery.img
After doing so, it should look like this:
4. Reboot your phone and you are done by typing:
Code:
fastboot reboot
Now, you have installed CWM custom recovery. On to installing root.
Rooting your phone:
1. After installing custom recovery, download Super-Su .zip file.
2. Place the .zip file on your sd-card. If your computer doesn't show your phone as MTP device, download the drivers from here.
3. Boot into recovery, by pressing POWER OFF + Volume UP button for 5 secs and choosing Recovery by pressing Volume Down (NOTE: Use Volume UP for menu navigation)
4. After booting into recovery, Choose 'Install Zip'. You can use Volume UP and Volume Down for navigating here and Power Off button for selecting a menu item.
5. Now, select 'choose zip from /external_sd' and not '/sdcard'
6. Select the Super-Su zip file you placed on your sd card and install it.
Now, Reboot your phone. It might say something like 'su may have been removed' but ignore and press 'No'.
Tutorial Complete
Let me know if there are any errors in this Tutorial.
Hi, thanks for the tutorial. Can you explain the necessity for using "fastboot format userdata" given "oem unlock" command in addition to unlocking the bootloader clears user data.
littleromeo said:
Hi, thanks for the tutorial. Can you explain the necessity for using "fastboot format userdata" given "oem unlock" command in addition to unlocking the bootloader clears user data.
Click to expand...
Click to collapse
Someone in this thread reported that they got stuck on the recovery, meaning the phone boot normally.
The port maker for recovery for our phone mentioned formatting userdata command in his post, so I did the same. I didn't want newbies to experience any trouble.
nice guide ..
but I guess "add adb and fastboot to system path " shall be made optional .. this will make guide little simpler and shorter ..
Hey
Can anybody please insure any android device that has been successfully rooted by this method ? Also is waiting for towelroot worth it ??
tanuj123 said:
Can anybody please insure any android device that has been successfully rooted by this method ? Also is waiting for towelroot worth it ??
Click to expand...
Click to collapse
I have used this method myself, but I am also the OP so.... :victory:
Iam in a weird situation , I did flash many times before but I dont know how it made my device like this ... THE PROBLEM IS WITH DRIVERS and also SDcard
First I unlocked my bootloader then flashed cm11 on it ( Which was on lollipop official) and I forgot to download gapps so in connected my phone to pc only to find my computer doesnt recognise my phone it make sound but nothing shows up I tried clicking MTP again and again but nothing happens , WHEN I TRIED ADB it shows no devices in the list , I took out the sd card to copy files manually and the sd card says its write protected ..... GUYS HELP @stirredo
What are you using to read your SD card on your computer?
If you are using SD card adapter, make the sure write lock is turned off.
Man thankyou but After installing the driver you gave my phone gets detected by pc but only when I turn on usb debugging @stirredo
Sent from my Xperia P using XDA Free mobile app
Kaushik124 said:
Man thankyou but After installing the driver you gave my phone gets detected by pc but only when I turn on usb debugging
Sent from my Xperia P using XDA Free mobile app
Click to expand...
Click to collapse
That is the same issue faced by me .
Saurabh K said:
That is the same issue faced by me .
Click to expand...
Click to collapse
Did you find any solution
Sent from my Xperia P using XDA Free mobile app
Not yet, but trying....
Sent from my Sparkle V
thanks for this awesome tutuorial.... But i have a problem in unlocking the tutorial
The problem is that how can i unlock my bootloader when oem unlocking is turned off...
Recently i tried to flash CM12.1 on my YU YUNIQUE YU4711 without turning on OEM unlocking and now I am stuck at the Fastboot mode so i cant start up my phone.... So i wanted to know that how i can unlock the bootloader when OEM unlocking is turned off..
PS- I cant even go to recovery moded
thanks in advance
Format Userdata
stirredo said:
Someone in this thread reported that they got stuck on the recovery, meaning the phone boot normally.
The port maker for recovery for our phone mentioned formatting userdata command in his post, so I did the same. I didn't want newbies to experience any trouble.
Click to expand...
Click to collapse
I did got stuck at bootloader when I dedn't format Userdata. Thanx for the tip.
---------- Post added at 03:01 PM ---------- Previous post was at 02:53 PM ----------
When I opened SuperSu after installing SuperSu through recovery, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
What do I do now?
stirredo said:
Hello,
I know there are some tutorials for this already but I felt like they missed out a few steps that might not be obvious to some who are new to this.
This tutorial applies to all of Android One Device (Micromax Canvas A1, Karbonn Sparkle V Blue, Spice Mi-498 Dream Uno).
Unlocking bootloader will lead to formating of your phone. The stuff inside your sd card is safe but all your apps and their data will be deleted.
Unlocking bootloader:
1. Download Universal ADB Driver installer from here.
2. Connect your phone and run the Universal ADB Driver installer. Click 'Install' button and a warning should pop up. Just click "Install anyway" and it should look like this:
3. Download ADT Bundle from here for Win-32 Bit and from here for 64-Bit . If you are unsure which version of windows you have just download the 32-Bit one.
4. Extract the zip file in your C:\ drive like this (You can install it wherever you like but this tutorials assumes this location for simplicity). Add adb and fastboot to system path by following this tutorial . This will allow you to run adb and fastboot commands from any location on cmdline.
3. Switch off your phone. Now, Press POWER BUTTON + VOLUME UP button for about 5 seconds. A menu should appear. Note: VOLUME UP allows to navigate the menu (move down the menu). Press VOLUME DOWN button for selecting/choosing fastboot. On your phone, it should say something like
Code:
=> FASTBOOT MODE...
Connect your phone to the computer if it wasn't already.
4. (Assuming Win 7) Click on start menu > Search for 'Command Prompt' and right click and select 'Run as Administrator'.
5. On command prompt, Type:
Code:
fastboot devices
If it shows something, that means we can proceed to unlocking bootloader. Otherwise, it means that the driver was not installed correctly.
6. Now, Type the following commands:
Code:
fastboot oem unlock
fastboot format userdata
fastboot reboot
Now, your bootloader is unlocked.
Install a custom recovery.
1. Download custom recovery from this thread.
2. Place the download file, 'recovery.img' file in C:\ drive. (Again, you can place it anywhere but this tutorial assumes this path).
3. Run the following command (Assuming already in fastboot mode again. If not, follow the above steps to go to fastboot mode). :
Code:
fastboot flash recovery c:\recovery.img
After doing so, it should look like this:
4. Reboot your phone and you are done by typing:
Code:
fastboot reboot
Now, you have installed CWM custom recovery. On to installing root.
Rooting your phone:
1. After installing custom recovery, download Super-Su .zip file.
2. Place the .zip file on your sd-card. If your computer doesn't show your phone as MTP device, download the drivers from here.
3. Boot into recovery, by pressing POWER OFF + Volume UP button for 5 secs and choosing Recovery by pressing Volume Down (NOTE: Use Volume UP for menu navigation)
4. After booting into recovery, Choose 'Install Zip'. You can use Volume UP and Volume Down for navigating here and Power Off button for selecting a menu item.
5. Now, select 'choose zip from /external_sd' and not '/sdcard'
6. Select the Super-Su zip file you placed on your sd card and install it.
Now, Reboot your phone. It might say something like 'su may have been removed' but ignore and press 'No'.
Tutorial Complete
Let me know if there are any errors in this Tutorial.
Click to expand...
Click to collapse
bro, my bootloader is already unlocked, so i was using the flash recovery command directly, and i was unable to flash recovery, everytime i go into recovery it opens stock recovery, what should i do to flash recovery now, no method is working, is it compulsary to unlock bootloader every time flashing recovery, mine is already unlocked, but cant able to flash recovery, please help ,its urgent.
I am on a custom ROM right now( Resurrection ) and have unlocked the bootloader
Can I relock the bootloader using Androidone tool
Will it format userdata?
Can I keep the Custom ROM after relocking?
Please help
Device-Mi-498
hi my device is not boot after restart.always need to run fastboot continue. have you any idea how to resolved ?
my phone showing device not found error in ADB driver installer. actually phone is unable to start, it is continuously looping in start logo
is the fastboot format userdata command required? what will happen if i fail to issue the fastboot format command following fastboot oem unlock command?
hello i want the unlocked bootloader file for my Micromax e313 please send me the link to get it please help me
AnandMore's How-To Guide For Beginners
Xiaomi Redmi 2
{
"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"
}
Intro:
This thread will serve as a location for basic how-to guides for the Xiaomi Redmi 2. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index:
Post #1 - Rooting your Redmi 2
Post #2 - Flashing Custom Recovery
Post #3 - Flashing Custom ROMs
Post #4 - Flashing Custom Kernels
Resources:
Everything you need for Xiaomi Redmi 2 is available in the below given thread -
[INDEX] Xiaomi Redmi 2
Rooting your Redmi 2:
This guide will root your device through Stock MI Recovery(Works with TWRP also), but this is not Native Root. A new app named SuperSU will be installed, which will give root Permission.
Note:
Rooting does not Void Warranty.
Caution:
This is a safe process, but I am not responsible for anything bad that happens to your phone.
In most cases this approach of rooting should not block OTA updates.
Steps to follow for rooting:
Download the Root.zip and Copy the file to the folder 'Internal storage' (root of internal storage).
(File at the end of thread)
Open the Updater app, Press the 3 dots at Right Top Corner, A menu will open. Tap on “Choose Update Package“ and select the Root.zip File.
Wait until device will reboot.
After reboot a new app SuperSu will be installed.
Open the app and Choose "Continue".
Choose "Normal", Don't Choose TWRP/CWM, device will go into Boot Loop.
Note - Don't Choose TWRP/CWM, it will brick your device.
After sucessful updation , press ok.
Your Phone has now Root Permission.
Open any app using Root permission and SuperSU will ask for Permission.
Enjoy your rooted Redmi 2.
Un Root The Device:
For Un Root , open the SuperSU app,tap on Settings, Choose Full Unroot.
Your Device is Un Rooted Sucessfully. The SuperSU app will be removed.
Flashing Custom Recovery:
From Mobile:
Install Flashify app from Playstore
Once installed, access the application through app drawer.
Allow root access now and get navigate to Flashify’s home screen.
First take a backup of your recovery in case something goes wrong. (RECOMMENDED)
Now tap on recovery image and by "Choose the file" menu locate the .img file you want to flash.
After successful flashing it will ask you to reboot your device.
Done! You have custom recovery on your phone.
From PC:
Enable USB debugging, go to settings>about phone and then tap on Android/MIUI version 5 times. Developer Options will be enabled. Now go back to settings>Developer options and enable USB debugging.
ADB and Fastboot Drivers installed on your PC. I can provide you the drivers but it would be a better option to install MiFlash to get all the necessary drivers and Miflash software with you for future use.
Install Miflash on your PC. Lets suppose we installed it in C:\Xiaomi folder.
You can see two folders, proceed to "adb' folder
Then proceed to "Google" folder.
Proceed to "Android" Folder.
We are at our destination.
Now Hold down "Shift" button on your computer keyboard and right click with mouse on an empty part of the window. You will see that in the menu that appears, you have an option - "open command window here". Click on that
To verify if ADB is working and installed correctly, type "adb version" in the command window that opened without the code. You should get the adb version which means its working fine.
Turn off your Phone. When its completely switched off, press and hold "Volume Down" and "Power" button together and then the phone will turn on in Fastboot mode.
Use the USB cable to connect Phone to PC.
Copy the Recovery.img in the Android folder where we are running the Command prompt. (C:\Xiaomi\adb\Google\Android in my case as i installed Mi flash in C:\Xiaomi folder)
Now go back to command promt and enter the following commands -
Code:
fastboot devices
Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command to flash recovery image -
Code:
fastboot flash recovery recovery.img
Once you enter this command, the recovery image will be flashed on your device. Once it is completed, enter the final command to reboot your phone -
Code:
fastboot reboot
Your phone will reboot.
You have have now completed flashing custom recovery replacing Stock Mi recovery on your Xiaomi Redmi 2.
Flashing custom ROMs:
Steps to Follow:
Download and transfer the custom ROM you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
Select “Wipe” from TWRP main menu and do a “Swipe to Factory Reset” on the bottom of screen.
Note: This will factory reset your device. If your custom ROM doesn’t require a factory reset, then simply skip this step.
Go back to TWRP main menu, tap on “Install” and select the custom ROMs .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom ROM installation process. This may take some time.
Once your ROM is successfully flashed, you’ll see “Wipe cache/dalvik” option, select it and then do “Swipe to wipe” on bottom of screen.
Once cache & dalvik wipe completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom ROM you just flashed. Since this will be the first reboot after flashing a new ROM, it might take some time to rebuild cache and finish boot, have patience.
Flashing Custom Kernels:
Steps to Follow:
Download and transfer the custom Kernel you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
In the TWRP main menu, tap on “Install” and select the custom Kernel .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom Kernel installation process. This may take some time.
Once flashing completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom Kernel you just flashed. Since this will be the first reboot after flashing a new Kernel, it might take some time to rebuild cache and finish boot, have patience.
For list of all available Roms visit this thread :
http://forum.xda-developers.com/redmi-2/how-to/available-custom-marshmallow-roms-redmi-t3278535
Click to expand...
Click to collapse
Better if you make lollipop ROMs thread too
Superb work bro thanks ...u
Isn't MIUI rooted out of the box already? [emoji52]
Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
Developer ROMs are. Global ROMs aren't.
Device comes with global ROM :3
noobpremium said:
Better if you make lollipop ROMs thread too
Click to expand...
Click to collapse
I made both lollipop and marshmallow roms in one thread. So you think i should make seperate one for lollipop.
Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
All roms(Beta,developer,stable) for Redmi 2 are not Pre rooted.
Added videos tutorials for better understanding.
Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?
my phone also rebooting. please help me. how to go to recovery?
srmohanrajan said:
my phone also rebooting. please help me. how to go to recovery?
Click to expand...
Click to collapse
1) Switch off the phone.
2) Press the Volume Down, Volume Up and the Power Button at the same time, about 2-3 seconds until the mi logo shows up.
3) Recovery mode menu will appear.
Fr3ak23 said:
Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?
Click to expand...
Click to collapse
Follow the same steps to boot into recovery and flash SuperSU v2.4.6 zip via recovery
(And remember you are responsible if anything happens to the device)
omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!
Fr3ak23 said:
omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!
Click to expand...
Click to collapse
No problem bro !
✌
Great !
New CM 12.1 is awesome, finally the camera works
I am curious on why I keep on losing root access. I never had that issue with any other phones and custom ROMs.
Stock Android 6.0.1 Marshmallow for TextNow
Device Compatibility: Moto G (3rd Gen) 2015 (xt1548 ONLY)!
Android Version: 6.0.1
Build No. MCI24.107-70
System Version: 24.62.70.osprey_sprint.sprint.en.US.sprint
Kernel Version: 3.10.49
Baseband: M8916_2020632.44.321.54R
Carrier/Provider: TextNow (Sprint MVNO Subsidiary)
Android Security Patch Level: January 5, 2017
Build Version SDK: 23
PRL Version: 25060
ROM & FIRMWARE FILES:
DOWNLOAD LINK: https://drive.google.com/folderview?id=0B7-zQU1VihD3aHZ4N1VJelY0d2c
This link provides download access to the following files: bootloader.img, gpt.bin (Partition Updater), NON-HLOS.bin (Modem, AKA "Baseband"), fsg.bin (Radio Firmware), recovery.img (Stock 6.0.1 Recovery), boot.img (Stock 6.0.1 Kernel/Ramdisk), system.img_sparsechunk files (a series of /system image files which, when flashed, comprise the ROM itself) An executable flash-all.bat file is also included, which is basically a script instructing fastboot as to each and every partition to be flashed.
Because the TextNow Moto G3 was shipped with Android 5.1.1 firmware, and because no firmware update or OTA has since been released for the TextNow variant, many key firmware components are outdated (e.g., Baseband, Bootloader, Partition Index, Radio Firmware, WLAN Drivers, etc). I have compiled this stock MM ROM in fastboot flashable format to ensure that all relevant firmware partitions are updated during installation of the stock ROM. Future releases of this ROM, which will center on bug fixes and stability improvements, will be compiled in TWRP flashable zip format.
REQUIREMENTS & INSTRUCTIONS:
1. An Unlocked Bootloader;
2. A Windows PC or Mac;
3. The Android SDK Platform Tools, or, preferably, the latest version of Minimal ADB & Fastboot. Download the program from this link for Windows PC and install once download is complete. https://drive.google.com/file/d/0B7-zQU1VihD3TnhTNVVVZGZ4bVU/view?usp=drivesdk
4. On your PC or Mac, install the most recently released version of "Motorola Device Manager." This piece of software installs and periodically updates the correct USB Drivers for your Motorola smartphones or tablet. A current version can be downloaded here, on the Motorola/Lenovo website: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
5. Power on and allow your Moto G3 to boot into the OS. Go to SETINGS, then select ABOUT PHONE, find BUILD NO. and tap it approximately 7 or 8 times until you see a toast confirming that DEVELOPER OPTIONS is enabled. In DEVELOPER OPTIONS, enable OEM Unlocking and USB Debugging.
6. Once you have downloaded the stock ROM installation & firmware files from the above link, place these files on your PC Desktop, in the same directory/path as ADB/Fastboot. Connect your Moto G3 to your PC or Mac using an OEM or high quality equivalent micro USB to USB syncing/charging cable. In your ADB/Fastboot directory, open a command window by holding the SHIFT key and simultaneously right clicking with your cursor in the folder/directory of the path sought. In this instance, the ADB/Fastboot directory would be correct. In the command window type: "adb reboot bootloader" .....Your device should boot into AP Fastboot mode from the Android OS. If it doesn't, you may manually boot into fastboot mode by first powering off your Moto G3. Then, hold Power and Volume Down simultaneously until the recovery menu appears. From recovery (if stock recovery) simply use Volume Down to navigate to Bootloader option then press Power to select. Once in Fastboot Mode, open another command window in the ADB/Fastboot directory, then type,: "fastboot devices". The command window will return with a string of numbers under an entry titled "connected devices". The numbers are actually your device serial number. (If no numbers are returned following the command, or if a prompt appears saying "waiting.....", then your device is not properly communicating with ADB/Fastboot via your PC or Mac. Try switching USB Ports, switching syncing cables and/or uninstalling/reinstalling Motorola Device Manager.
7. Upon establishing a proper connection between your PC and Moto G3, click on and run the executable file titled "flash-all.bat" (located n the directory of files from the below link), sit back & wait a minute or two. Your Bootloader', Partition Index, Modem, Radio Firmware & Stock Recovery will be updated to Stock Android 6.0.1 Marshmallow. Your /system partition will also be flashed with a series of img_sparsechunk files, updating your Android OS to Stock 6.0.1.
** It should be noted here that once your partition index & bootloader have been updated, you will not have the option to downgrade either of these partitions at a later time. In fact, attempting to downgrade bootloader.img or gpt.bin has been known to result in a hard brick. Your Modem (NON-HLOS.bin) and Radio Firmware (fsg.mbn) may be downgraded with no reported adverse effects.
8. Now, you will need to root your stock Marshmallow OS. (Many of the addon pre-installed applications on this stock ROM require superuser access.) To root the ROM, you will need to flash SuperSU v2.79 systemless root .zip via TWRP recovery. Links for both files are here:
@squid2's TWRP v3.0.2-r5: https://drive.google.com/file/d/0B7-zQU1VihD3ajYwR25xZ3dFT3c/view?usp=drivesdk
@Chainfire's SuperSU v2.79 Systemless Mode zip: https://drive.google.com/file/d/0B7-zQU1VihD3VFBidGk4SjFkQUE/view?usp=drivesdk
9. Upon initial boot, setup, etc., go ahead and update your PRL & Data Profile to ensure your versions are the most recent. Under SETTINGS, scroll down to SYSTEM UPDATES. Turn WiFi off and Cellular Data on. First choose the option to update your PRL. Once successfully updated, choose the update Profile option. A reboot will be necessary in order for these changes to take effect.
Add-ons Included (in /system/apps) & Credits:
TextNow v5.3.0 by TextNow, Inc.
SuperSU v2.79 by @Chainfire
BusyBox v49 by @denys Vlesenko
Fast Cleaner v3.2.8 by the @OPDA Team
Kernel Adiutor-Mod v1.0-07/18/2016 by @yoinx
CyanogenMod 13 File Manager v3.0.0 by The CyanogenMod Team
Google Nexus MM Boot Animation (Dark Theme)
Nova Launcher v 5.0.3 by @teslacoil Software
Candy Icons v2.3.3 @Vukasin Andelkovic
VIPER4ARISE FX v2.5.0.5 by VIPER ACOUSTICS & A.R.I.S.E SOUND SYSTEMS
Esira Music Player v1.0 by @A.R.I.S.E SOUND SYSTEMS
I also want to say a huge thanks to @dearmasfamily for his TextNow based stock Android compilations on the Moto E LTE 2015 (xt1526). His modifications to apns-config.xml and eri.xml on the Moto E LTE were a lifesaver during my network configurations for TextNow on the Moto G3. And thanks to @squid2 for his hard work on custom kernels for Osprey. His detailed explanations on boot image support have given me a much broader understanding of the systemless root methodology. Finally, @ResistanceIsFutile, your keen eye for detail, research, and general editing skills have been invaluable. Thank you.
Sent from my Lenovo TB3-850F using XDA-Developers Legacy app
Also for XT1543 please !
Heyner_Gomez said:
Also for XT1543 please !
Click to expand...
Click to collapse
I agree -- TextNow subscribers would benefit from a stock 6.0.1 MM ROM for the T-Mobile (or GSM unlocked) variant of Osprey. Unfortunately I do not own a xt1543. I would need a device at least tentatively in order to flash & dump firmware partitions for a stock MM build.
Looking Good
Easy to understand and presentation looks very much polished
- Good Job Sir :good:
Hark do I see special editing as well. . .
Build it and they will come
The OP download link for the ROM & Firmware files - if you use the "Download All" tab "top Right" corner there, will Zip all files together in an easy all at once download of them in two zipped parts.
Thank you @ResistanceIsFutile. Been messing around on XDA Forums Premium for Android to create my post. You taught me a great deal on thread composition & I am grateful for it. I'll be linking the ROM & firmware files within an hour or so. Also i will be including a patched boot.img for systemless root support. Simply flash SuperSU v2.79 via TWRP (files to be included in link) and root access should be without issue. My messaging settings are undoubtedly the culprit. Please send me a friend request. I'll fix the PM issue shortly.
@MotoJunkie01 Your certainly welcome, as I've learnt many things from you as well.
Friend request sent out. Don't know why I've waited so long really. I believe your the first.
I see your due a celebration on a couple counts, hope Saturday is the best for you.
RIF
{
"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"
}
I need testers to install and provide input on this.
I'm currently running LineageOS 14.1. I read this bit of your post:
"attempting to downgrade bootloader.img or gpt.bin has been known to result in a hard brick."
I'm not sure I understand it fully. I apologize if this is a rather basic question, but if I install this from Lineage, will I have any problems? If I choose to install this, what should I avoid in the future to prevent a hard brick?
Thanks for your hard work!
tsakowich6217 said:
I'm currently running LineageOS 14.1. I read this bit of your post:
"attempting to downgrade bootloader.img or gpt.bin has been known to result in a hard brick."
I'm not sure I understand it fully. I apologize if this is a rather basic question, but if I install this from Lineage, will I have any problems? If I choose to install this, what should I avoid in the future to prevent a hard brick?
Thanks for your hard work!
Click to expand...
Click to collapse
No. You should have no problems at all. In a nutshell, stock firmware packages contain files to flash the bootloader (bootloader.img) and a partition table updater file (gpt.bin). Once these two partitions are updated, downgrading isn't an option. This doesn't mean you can't downgrade a stock ROM, say from 6.0.1 to 5.1.1. Downgrading is no issue at all as long as you avoid bootloader.img and ,gpt.bin.
Installing custom ROMs, like LineageOS, doesn't put you at any risk in this regard. You may upgrade or downgrade at your leisure. My warning in the thread merely cautioned against downgrading the bootloader and partition table in stock firmware packages.
@MotoJunkie01 : AFAIK holding down power+volume down button boots directly into the bootloader mode (not recovery) and fastboot is accessible.
In OP, point 6:
Then, hold Power and Volume Down simultaneously until the recovery menu appears. From recovery (if stock recovery) simply use Volume Down to navigate to Bootloader option then press Power to select.
Click to expand...
Click to collapse
Normally it's the other way around. Probably a typo? Just curious.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
@MotoJunkie01 : AFAIK holding down power+volume down button boots directly into the bootloader mode (not recovery) and fastboot is accessible.
In OP, point 6:
Normally it's the other way around. Probably a typo? Just curious.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Hello @Gravemind2015
I'm limited as I no longer have a Moto G (3rd Gen) 2015 (xt1548).
I've just looked as to the manufactures steps (as these questions interests me).
These are for an External Reset and Clear Cache Partition though, but share common steps,
I couldn't find as steps called out solely to enter Recovery Mode specifically other than these sets of instructions .
External Reset.
https://mobilesupport.lenovo.com/us/en/products/CELL-PHONES/ANDROID-SERIES/MOTO-G-3RD-GEN/documents/MS105537
Android 5.x (Lollipop)/Android 6.x (Marshmallow) External Reset Steps
1.With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
2.Press the Volume Down key to highlight Recovery mode.
3.Press the Power key to restart into Recovery mode.
4.The screen will display an Android robot with a red exclamation mark.
5.While holding down the Power key, press and release the Volume Up key, then release Power.
6.Use the volume keys to scroll to Wipe data/factory reset and press the Power key to select it.
7.Scroll down to Yes - erase all user data and press the Power key to select it.
Clear Cache Partition.
https://mobilesupport.lenovo.com/us/en/Solution/MS112729
Android Version 6.0 (Marshmallow) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Down button. While still holding Volume Down button, press and release the Power button.
3.Press and release the Volume Down button until you reach Recovery Mode.
4.Press and release the Power button to select Recovery Mode. The device will restart. An image of an Android robot with a red exclamation mark will appear.
5.Press and hold the Power button, press the Volume Up button once and then release the Power button.
6.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it. If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Once the cache wipe has completed, press the Power button to select Reboot System Now.
Android Version 5.0 (Lollipop) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Up and Volume Down buttons and the Power button at the same time until the device turns on.
3.From the Boot Mode selection menu, press the Volume Down button to scroll to Recovery and the Volume Up button to select it. The device will restart. An image of an Android robot with a red exclamation mark will appear.
4.Press and hold the Power button, press the Volume Up button once and then release the Power button.
5.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it.
6.If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Press the Power button to select Reboot System Now.
Hope this helps and clears as with what the Moto site instructs.
ResistanceIsFutile said:
Hello @Gravemind2015
I'm limited as I no longer have a Moto G (3rd Gen) 2015 (xt1548).
I've just looked as to the manufactures steps (as these questions interests me).
These are for an External Reset and Clear Cache Partition though, but share common steps,
I couldn't find as steps called out to enter Recovery Mode specifically other than these sets of instructions .
External Reset.
https://mobilesupport.lenovo.com/us...ROID-SERIES/MOTO-G-3RD-GEN/documents/MS105537
Android 5.x (Lollipop)/Android 6.x (Marshmallow) External Rest Steps
1.With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
2.Press the Volume Down key to highlight Recovery mode.
3.Press the Power key to restart into Recovery mode.
4.The screen will display an Android robot with a red exclamation mark.
5.While holding down the Power key, press and release the Volume Up key, then release Power.
6.Use the volume keys to scroll to Wipe data/factory reset and press the Power key to select it.
7.Scroll down to Yes - erase all user data and press the Power key to select it.
Clear Cache Partition.
https://mobilesupport.lenovo.com/us/en/Solution/MS112729
Android Version 6.0 (Marshmallow) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Down button. While still holding Volume Down button, press and release the Power button.
3.Press and release the Volume Down button until you reach Recovery Mode.
4.Press and release the Power button to select Recovery Mode. The device will restart. An image of an Android robot with a red exclamation mark will appear.
5.Press and hold the Power button, press the Volume Up button once and then release the Power button.
6.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it. If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Once the cache wipe has completed, press the Power button to select Reboot System Now.
Android Version 5.0 (Lollipop) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Up and Volume Down buttons and the Power button at the same time until the device turns on.
3.From the Boot Mode selection menu, press the Volume Down button to scroll to Recovery and the Volume Up button to select it. The device will restart. An image of an Android robot with a red exclamation mark will appear.
4.Press and hold the Power button, press the Volume Up button once and then release the Power button.
5.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it.
6.If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Press the Power button to select Reboot System Now.
@MotoJunkie01 states this-
Hope this helps and clears as with what the Moto site instructs.
Click to expand...
Click to collapse
Well, the lenovo support link you provided seems to have the accurate process. Bootloader unlocking page also has the same instructions. [Power off> power+volume down and it goes into bootloader(fastboot) mode rather than to recovery]
Anyways, this will be off-topic for this rom thread so I'd hope someone with access to this particular model with this carrier can test which method is correct Thanks for replying.
Broadcasted from Zeta Reticuli
Removed My own Content
ResistanceIsFutile said:
It could be the hard buttons keying sequences (power and volume) and then the use the Volume button to scroll and then which one (button) is needed to be used to select Recovery.
As I'm remembering getting into Recovery required to do it multiple of times when I had the phone - again using the proper keying of the hard buttons in the right orders.
At Least these buttons are side mounted on Moto's and not on the back as another phone I have.
Click to expand...
Click to collapse
Yes they are hard button combination.
The instructions I outlined (works with my XT1550 ) are the general instructions which are identical in rest of osprey thread except in this tutorial.
I had assumed that the firmware of these models were identical except for radio.
I was just wondering if this model really has a different mechanism or it's just a mistake in original post
Broadcasted from Zeta Reticuli
Gravemind2015 said:
@MotoJunkie01 : AFAIK holding down power+volume down button boots directly into the bootloader mode (not recovery) and fastboot is accessible.
In OP, point 6:
Normally it's the other way around. Probably a typo? Just curious.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Hi ©Gravemind2015....thank you for pointing out my clerical error. Instead of "recovery" I should have said "bootloader' or " fastboot" menu in that particular instance. I'll edit the instructions accordingly.
So i can just go and flash this via twrp?
MimzyDesigns said:
So i can just go and flash this via twrp?
Click to expand...
Click to collapse
This build is not a TWRP flashable zip. Needs to be flashed via fastboot. The next release will be TWRP flashable.
I ran flash-all, but now I'm stuck at "fastboot flash -u system system.img_sparsechunk.1"
Had been sitting there for about 30 minutes before I gave up and unplugged to try again. Same result.
Any advice?
Edit:
Error message before it hangs up:
(bootloader) has-slot:system: not found
target reported max download size of 268435456 bytes
sending 'system' (131082 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.247s
tsakowich6217 said:
I ran flash-all, but now I'm stuck at "fastboot flash -u system system.img_sparsechunk.1"
Had been sitting there for about 30 minutes before I gave up and unplugged to try again. Same result.
Any advice?
Edit:
Error message before it hangs up:
(bootloader) has-slot:system: not found
target reported max download size of 268435456 bytes
sending 'system' (131082 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.247s
Click to expand...
Click to collapse
Did the partitions up until that point successfully flash?
This does happen before that as well. But besides boot and sparsechunk.0 everything else works fine.
Edit:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash -u system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
target reported max download size of 268435456 bytes
sending 'system' (131082 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.244s
OnePlus 5: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup & More !!
{
"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"
}
Before you start, OTA up to the latest System Update available.
Settings > System Updates > Download & Install the latest available
Introduction
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps:
Unlocking the Bootloader
Installing a Custom Recovery
Gaining Root Access
Each new step relies on the previous step so please follow the entire process and a basic summary of each part is described as below:
Unlocking BootloaderOpens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom RecoveryA custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your device (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Gaining Root AccessYou can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries or by Flashing Magisk Zip for a system less root. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed and an unlocked bootloader. This, in my opinion, is the a practical and beneficial method for rooting your phone. It will give you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of the entire process. This method will work regardless of any android version on the phone.
If you are confused by anything in this guide, I highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also we would suggest that you read over the whole thread a few times before actually doing anything to the phone.
Setup, Preparation & PrerequisitesBasic tasks that may be referred to throughout this guide:Open Command Prompt: Press Shift + Right Click anywhere on the screen and select Open Command Window here
Enter Fastboot/Bootloader Mode: Turn the phone off. Hold volume up + power until the "fastboot" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot > Bootloader from the power menu.]
Enter Recovery Mode: Turn the phone off. Hold volume down + power until the "OnePlus Logo" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot -> Recovery from the power menu.]
ADB and Fastboot Installation1. Download the ADB For Windows from here Credits @Snoop05 his Original XDA Thread Here
Or You can manually update Fastboot and ADB binaries here Credits @lj50036 his Original XDA Thread Here
2. Run the .exe file downloaded from above as Administrator.
3. Press 'Y' every time the installer asks for.
4. Continue Driver Installation.
Now, ADB and Fastboot have been installed on your PC and should be Working as desired.
Things To RememberShow File Extensions :good:
Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery :good:
Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long , but its best to have enough charge in case something goes wrong.
Backup (Optional) :good:
Unlocking the bootloader will/should completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
USB Debugging :good:
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking :good:
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option. Also make sure that from now on, OEM unlocking option is enabled before you reboot as sometimes, it might get disabled itself.
Enable Advanced Reboot :good:
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
Unlocking Bootloader
Turn the phone off. Then boot it into fastboot mode by holding volume up + power or select reboot to bootloader if advanced reboot is activated via developer options. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here) and type:
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember this Step will WIPE EVERYTHING off the phone so Backup all your Data
Code:
fastboot oem unlock
You would be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection
Your device will reboot, show you a Secure boot warning, reboot into stock recovery and wipe all data. Once done, your phone will reboot into the OS.
Please continue and follow the next post to install Custom Recovery
Flashing TWRP Recovery
Downloads:
Recovery:
Codeworkx TWRP | Blu_Spark TWRP
Magisk
Wait until the phone has fully booted up into android, then adjust the following settings on the phone:
USB Debugging:
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking:
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option and make sure that from now on, OEM unlocking option is enabled before you reboot. Sometimes, it might get disabled itself.
Enable Advanced Reboot:
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
Download all the files, place SuperSU or Magisk on Device Internal Memory and TWRP img in the Android Folder under the Platform Tools folder in C Drive
Then boot it into fastboot/bootloader mode by holding volume up + power or selecting the reboot to bootloader via advanced reboot options.
Open a new command prompt in the same location and run the following commands:
Code:
fastboot flash recovery (file name).img
Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed or you can also use the command:
Code:
fastboot boot recovery.img
PS: DO NOT BOOT IN OS JUST YET & CONTINUE TO THE ROOTING POST
Gaining Root Access
This is a continued post from the above post...
For Users who want to remain Encrypted: :fingers-crossed:
1. Boot into TWRP Recovery and allow system modifications.
2. Swipe right and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk Or SuperSU to root OnePlus 5.
5. Swipe to confirm the flash
6. Reboot System
Keep in mind that the first boot after wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot and would reboot a few times due to SuperSU Flash.
For Users who want to Decrypt Data have to Format Data & Flash No Verity OP5 Zip :fingers-crossed:
1. Boot into TWRP Recovery and allow system modifications.
2. Swipe right and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
Go to “Wipe” section and tap “Format Data”, and type “yes” to mount internal storage
4. Download & Transfer no_verity_op5.zip to the device over MTP from here Credits @snowwolf725
5. Go to “Install” section, select no_verity_op5.zip, and swipe to confirm the flash
6. Transfer latest Magisk/SuperSU to the device over MTP to your Oneplus 5 & Swipe to confirm the flash
7. Reboot System
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
Congrats! That is all! Your Device now has an unlocked bootloader, a custom recovery installed and is rooted along with your preference of staying encrypted or decrypted.
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery.
Enjoy :fingers-crossed:
Making a Nandroid BackupWarning: before you make a backup with TWRP you must remove all Lockscreen Security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin/pattern/password will result in an "incorrect pin/pattern/password" message), you'll be forced to perform a factory reset to boot into Android.
To remove lockscreen security go to
Settings > Security > Screen Lock and set it to Swipe/None.
A Nandroid Backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back.
You can also use Nandroid Bckup to create a backup of your favorite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
To Create Nandroid Backup:
1. Boot into TWRP Recovery .
2. Go to Backup Menu and select all the listed partitions.
3. Name the Backup if needed (Optional)
4. Swipe to take Backup.
This proces should take 4 to 8 minutes depending upon the size of data.
5. Reboot System when done.
Your Nandroid will be stored in the Backup Folder inside TWRP Folder /sdcard/TWRP/BACKUPS
Restoring a Nandroid Backup
1. Boot into TWRP Recovery
2. Go to Restore Menu and select the backup you want to restore.
3. Select the partitions you want to restore.
4. Swipe to Restore. The process will take 6 to 10 minutes.
5. Reboot system once done
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Password) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue.
Boot into TWRP
Use the TWRP File Manager and Navigate to /data/sytem/ and delete the following files:
locksettings.db
locksettings.db-shm
locksettings.db-wal.
gatekeeper.password.key
gatekeeper.pattern.key
You may or may not have all the above files so delete the ones you have.
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Upon Boot > Go into Settings > Security > set your preferred unlock method
Android will ask you if you want to set a boot-time code too so select as per convenience.
Making an EFS BackupAll too often, we've seen folks who have a corrupted or missing EFS Partition. This results in your IMEI being lost and no cellular activity on the device at all. This can be a royal PITA to fix, and some folks haven't been able to fix it at all. You can take a precautionary measure to safeguard yourself against this by taking a couple of minutes to back up your modemst files.
Download & Open up Terminal Emulator on your phone from here
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.
Now enter these two commands:
Code:
dd if=/dev/block/sdf1 of=/sdcard/modemst1.bin bs=512
Code:
dd if=/dev/block/sdf2 of=/sdcard/modemst2.bin bs=512
This will place two files (modemst1.bin & modemst2.bin) on your internal storage.
Make sure you copy them to your PC and Cloud immediately so that you have a backup there to use if you need to restore it in future.
That's it !! In case you ever need to restore Nanroid or EFS Backups, please continue and follow the next post...
Restoring an EFS BackupIf by chance you end up with a corrupt EFS partition all you need to do is flash the files back to your device using fastboot.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Keep modemst1.bin and modemst2.bin (backed up earlier) on your desktop and open command window there.
These fastboot commands will restore the files:
Code:
fastboot flash modemst1 modemst1.bin
Code:
fastboot flash modemst2 modemst2.bin
Reboot your device.
Code:
fastboot reboot
Now disconnect phone from PC. Your IMEI should be back.
That's it for this guide, Enjoy :highfive:
Thank you for your support !!
First OTA 4.5.1
Theoretically unlocking the bootloader and flashing TWRP should be identical to the OnePlus 3/3T and previous devices, i.e. just like a Nexus (R.I.P.).
jmazzamj said:
Theoretically unlocking the bootloader and flashing TWRP should be identical to the OnePlus 3/3T and previous devices, i.e. just like a Nexus (R.I.P.).
Click to expand...
Click to collapse
Indeed its similar. Just making it clear for the new users here in one thread so there is no confusion.
Funk Wizard said:
Indeed its similar. Just making it clear for the new users here in one thread so there is no confusion.
Click to expand...
Click to collapse
Thank you for this! I'm going to get this device as soon as it's back in stock. It will be my first ever OnePlus device (coming from a Pixel XL). I'll still be using that but the dev support seems to be the highest with these devices.
Definitely going to use this guide to get all setup, so thanks again!
Just wondering though, I've never dealt with this dm-verity thing, what is this exactly?
Also, the day I decide to sell this phone for the next generation OnePlus (6), is it relatively simple to get back to stock and relock the bootloader?
Sorry for all the questions, just want to be thorough before doing all of this and potentially bricking my new device lol
Thank you!
Link to TWRP?
Sent from my OnePlus 3T using XDA Labs
rickysidhu_ said:
Thank you for this! I'm going to get this device as soon as it's back in stock. It will be my first ever OnePlus device (coming from a Pixel XL). I'll still be using that but the dev support seems to be the highest with these devices.
Definitely going to use this guide to get all setup, so thanks again!
Just wondering though, I've never dealt with this dm-verity thing, what is this exactly?
Also, the day I decide to sell this phone for the next generation OnePlus (6), is it relatively simple to get back to stock and relock the bootloader?
Sorry for all the questions, just want to be thorough before doing all of this and potentially bricking my new device lol
Click to expand...
Click to collapse
First of all Welcome to the Oneplus Community Buddy, hope your get the device soon, i am also waiting for my unit likewise :fingers-crossed:
DM Verity is just another screen warning just like the secure boot screen, which depicts an unlocked bootloader and a modified recovery, it can be taken care off easily and even if you dont it wont harm in any way just take some addition 5 to 7 seconds on boot. I am here to help so it will be taken care off.
Also its easy to get back to stock as all full zips and both TWRP and Stock Recovery Flashable so just a process of 5 minutes to be precise once you have the required downloads and once stock bootloader can also be locked again via fastboot command.
If you just follow the steps on the guide, everything will be fine. Just wait for the official TWRP source to be released, should not be long though.
Thanks again for supporting Oneplus and Welcome to the Community :highfive:
MrMeeseeks said:
Link to TWRP?
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Will update when released, waiting for the official maintainer to be assigned, or if someone can build an unofficial build to begin with :fingers-crossed:
Funk Wizard said:
Thread Under Construction...
Waiting for hands on experience with the device !!
Click to expand...
Click to collapse
So fast?
You guys are the best!
Hey, many thanks for the guide.
I will be coming from an LG G6.
Question: since there is no external SD card, if we place SuperSU, DM-Verify etc on our internal memory...when we unlock the bootloader will the phone also wipe the internal sd memory??