19 May 2015: With the Fall of Goo.im I will be posting Mirrors OtterX files here:
Otter X Twrp and Bootloader Mirrors
Several people have had trouble Installing Cm12 and Slimpop Otter X Roms.
Seems to be a variety of reasons for this.
Did you watch my video? [YouTube] [How To] convert to OtterX ROM/TWRP/Bootloader
Did you read original OtterX thread? OtterX ROM/TWRP/Bootloader
Did you install otterx-u-boot_v2.05.zip and zip-otterx-twrp-2.7.1.0-recovery.zip in twrp?
Did you verify checksum(s) for all file(s) used? https://sites.google.com/site/sdshadowscollection/home/hash-checksums
Did you wipe cache, rebooted, Fomate Data, wipe partitions in wipe>advanced ?
-
For those having trouble with MTP on TWRP versions 2.8.X.X and Window 7
try Updating Windows Media Player
wicpp said:
I am having Windows XP SP3 and I was experiencing the same USB MTP installation failure, I updated my Windows Media Player and it fixed the problem. The option in Windows Media Player Help->Check for updates was not working, so I downloaded Media Player from Microsoft webiste and installed it and after that driver is now working fine.
Click to expand...
Click to collapse
Problem: Installed OtterX Bootloader, and now can't access bootmenu options with Power button, and just bootloops.
Solution 1: Try Disconnect from PC, Power off (Hold Power button for 10-20 secs), connect to wall charger
Solution 2 : Reflash TWRP
Solution 3 : Reflash 2.05 bootloader
Problem: Twrp Cannot connect to PC. Device not found. In the device manager, Amazon OtterX is listed, but has an exclamation next it.
Solution:If drivers were working before, try selecting drivers for device.
Fixing OtterX Drivers: I posted screenshots of how Kindle should look like in Device manager, once converted to OtterX in post #9 here
In Device manager>select unknown device or device with a yellow triangle or ! >Update driver software>
browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>
show all(uncheck show only compatible)>look for ADB interface or android phone
select yes to Ignore warning
may need to reboot both.
Problem: Twrp is recognized by PC, but neither MPT mount, nor ADB push works. May get an unauthorized device error/warning
Problem: Installed TWRP 2.8..X.X now whenever i try to get into recovery it goes to teamwin logo and goes back to the kindle fire screen
Solution:If you are using Twrp 2.8.XX, use a Linux or Mac machine, or downgrade to 2.7.1.0 Twrp:
Downgrade 2.8.X.X Twrp to 2.7.1.0 TWRP see Flashing TWRP in OtterX bootloader
Problem: When Installing Lollypop you get an :updater binary error"
Solution:If you are still using bootloader 2.04, upgrade to 2.05:
If you still can push files to Twrp, try pushing 2.05.zip, install, reboot, wipe cache, reboot, format data, wipe everything in wipe>advanced...
Partition Sizes and File System
It seems that if you use TWRP 2.8.XX when switching from Amazon to OtterX partitions, sometimes things are getting fouled up, could be that this was an issue before, but has been more noticeable with lollipop.
Partitions sizes for OtterX partitions with 2.05 bootloader should be ...
all should say Present: Yes
system: Current file System: Ext4 - Size: 751MB (768MB)
Cache: _Current File System: Ext4 - Size: 503MB (512MB)
Data:__Current File System: _ f2fs - Size: 5820MB (5880mb)
see post #2 for screenshots
If you have Twrp 2.7.1.0 and bootloader 2.05, and have wiped cache, rebooted, Fomated Data, wiped partitions in wipe>advanced and still have issues:
Solution:Reboot to bootloader, select Amazon partitions, select recovery, wipe cache, reboot to bootloader select OtterX partitions, select recovery, wipe cache, reboot, format data, wipe all partitions.
Verify Partition sizes match post #2
Of course, all this assumes that drivers are installed correctly on you PC, none of the above will work if drivers are not correct.
If adb commands were working correctly before, and/or fastboot commands are still working, likely drivers are correct.
Please reply if this Guide helped
Please include: What errors you were having, and steps you took to fix.
I made Some videos that cover most of the steps
Flashing TWRP in OtterX bootloader
[How-To] Revert from OtterX Project to Stock Kindle Fire Partitions/Rom
Don't use the EMMC corruption fix
Hashcode said:
Why did you try EMMC corruption fix? That wipes out every partition on the device and attempts to restore the barebones xloader, bootloader
You'll need to flash a recovery.img via fastboot to get back up and running.
Click to expand...
Click to collapse
Hashcode said:
I think I'm seeing a bootloader bug:
- If you power on the device w/o USB plugged in, there's a MUSB interrupt issue causes 1 of 2 things to happen: device hangs during boot entirely and/or the USB port is completely unresponsive (till you reboot).
Right now, I'm still debugging this as I get time. But, when I power on with USB connected, I don't see any issues. You can unplug immediately after the bootanimation ends and re-plug all day.
The reason I'm saying this is a bootloader issue:
I've never seen this behavior on the old bootloader. I might need to shutdown the USB port after the fastboot loop in a cleaner way.
If others have seen this, please chime in.
Click to expand...
Click to collapse
Partition Screnshots
{
"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"
}
Data Partition:
Cache Partition
System Partition
Hashcode said:
...And all of the other partitions will be ext4, only userdata will be formatted f2fs.
Click to expand...
Click to collapse
Hashcode said:
The v2.04 otterx partitions are smaller:
system = 512MB)
cache = 265MB
Vs the newer larger partitions in v2.05:
system = 768MB
cache = 512MB
The idea was to protect from future required wipes do to low system/cache space.
The bootloader doesn't need to support f2fs only recovery and the ROM/kernel.
Click to expand...
Click to collapse
Flashing TWRP in OtterX bootloader
see [Video] Flashing TWRP in OtterX bootloader
Check drivers before flashing see Post #9
Verify MD5 checksums https://sites.google.com/site/sdshadowscollection/home/hash-checksums
Download adb-fastboot.zip,
and an OtterX TWRP .IMG file like otterx-twrp-2.7.1.0-recovery.img -
Size: 7528448 bytes MD5: ec8e8a67492d5fd06494f854bb59b2ae
for flashing OtterX Bootloader use otterx-u-boot_v2.05.bin
Size: 238720 bytes MD5: 241a3fd1edad0a0d95886ddeb4693e1cStep 1:
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, and otterx-twrp-2.7.1.0-recovery.img to adb folder.Step 2
connect Kindle Fire to pc, via usb, power off KindleStep 3
Open a Command Prompt (start>all programs>accessories>Command prompt)
change directory to adb with
Code:
cd\adb
Send flash command
Code:
fastboot flash recovery otterx-twrp-2.7.1.0-recovery.img
Power ON Kindle
Code:
fastboot reboot
after reboot you should be able to enter recovery by pressing power button once and selecting recovery
if still unable to enter recovery, may need to reflash bootloader
same steps
Code:
fastboot flash bootloader otterx-u-boot_v2.05.bin
Code:
fastboot reboot
if unable to get partitions correct, or adb was working but now does not, could be that something wrong with the bootloader, flashing
otterx-u-boot_v2.04.bin may fix
download otterx-u-boot_v2.04.bin
verify md5: 30569AE834BAFD70D6E7EFB90338F4CB
Code:
flashboot flash bootloader otterx-u-boot_v2.04.bin
Code:
fastboot reboot
In Bootloader, select Amazon partitions
select recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
select reboot system (don't worry about system not rooted warning, or no rom installed, just select an option)
In bootloader>select OtterX partitions
reboot recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
reflash 2.05 bootloader
Code:
fastboot flash bootloader otterx-u-boot_v2.05.bin
Code:
fastboot reboot
In Bootloader, select Amazon partitions
select recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
In bootloader>select OtterX partitions
reboot recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
reboot recovery
Wipe>format data
Wipe>Advanced Wipe>check all>swipe to wipe
reboot recovery
if using 2.7.10 try adb push
if using 2.8.X.X try MTP
you have single handed saved so many kindles. thanks for your continued support. cheers steve. long live otterx
Sent from my Nexus 5 using Tapatalk
Thanks
Thanks so much @sd_shadow, your instructions saved my Kindle Fire. I flashed twrp v2.7.1.0 from v2.8.1.0 and it worked properly.
Still using TWRP 2.8.x.x
I have idea for using TWRP 2.8.x.x without error when flash new ROM
The steps to perform this is:
Step 1: Wipe Factory Reset
Step 2: Intall Slim-otterx-5.0.1.alpha.0.7-v0.3.zip
Step 3: Intall newest version: Slim-otterx-5.0.1.alpha.0.9-V0.8.zip
Step 4: Install Gapps and Restart
It is successful with me. You can try it and give me comment if you can't.
Partition info in TWRP 2.7.1.0 ?
Great stuff @sd_shadow, keep up the good work. Where in twrp are you seeing the screens in post #2?
Thanks,
The Don
DonDeLome said:
Great stuff @sd_shadow, keep up the good work. Where in twrp are you seeing the screens in post #2?
Thanks,
The Don
Click to expand...
Click to collapse
Good question,
Wipe> Advanced> check a partition (Cache, System, or Data) then select Repair or Change File System
Sent from my XT907 using Tapatalk
Screenshot of Device Manager and OtterX Drivers
If you have not used the install.drivers.bat from Kindle Fire Utility, download, unzip, run install.drivers.bat.
KFU mirrors: AFH - Mega
show all(uncheck show only compatible)>look for ADB interface or android phone
If that worked Kindle should now look like this
Hi,
i have a problem.... every step works fine until adb push after step 3.
when i try to push the zip files to my device i only get "error: device unauthorized. Please check the confirmation dialog on your device"
But after step 3 there is no OS anymore to boot in an confirm.
How to solve the problem?
OnkelKaethe said:
Hi,
i have a problem.... every step works fine until adb push after step 3.
when i try to push the zip files to my device i only get "error: device unauthorized. Please check the confirmation dialog on your device"
But after step 3 there is no OS anymore to boot in an confirm.
How to solve the problem?
Click to expand...
Click to collapse
use twrp 2.7.1.0
see Flashing TWRP in OtterX bootloader
Looks like I have the same problem as the other people do. In step 4 here:
http://forum.xda-developers.com/showthread.php?t=2671619
When I wiped the System, that's when I first noticed that my computer no longer recognized the device and a popup indicated that driver installation had failed. I continued on to Step 5 and went to ADB my files (I confirmed ADB worked at the beginning of the process) and no device was found. Per the original post, I'm running 2.05 for bootloader and 2.8.2.0 for recovery. I checked the partition sizes and they all match. I did manage to get the unrecognized device named Amazon Otterx to install drivers as an ADB interface. But now when I go look at ADB devices, mine is listed but it has an "unauthorized" next to it. I followed the instructions on the video to install 2.7.1 recovery but the device never goes into fastboot. It just boots into the bootloader, hangs out for a few seconds, then powers off.
I think I'm stuck.
Minjin said:
Looks like I have the same problem as the other people do. In step 4 here:
http://forum.xda-developers.com/showthread.php?t=2671619
When I wiped the System, that's when I first noticed that my computer no longer recognized the device and a popup indicated that driver installation had failed. I continued on to Step 5 and went to ADB my files (I confirmed ADB worked at the beginning of the process) and no device was found. Per the original post, I'm running 2.05 for bootloader and 2.8.2.0 for recovery. I checked the partition sizes and they all match. I did manage to get the unrecognized device named Amazon Otterx to install drivers as an ADB interface. But now when I go look at ADB devices, mine is listed but it has an "unauthorized" next to it. I followed the instructions on the video to install 2.7.1 recovery but the device never goes into fastboot. It just boots into the bootloader, hangs out for a few seconds, then powers off.
I think I'm stuck.
Click to expand...
Click to collapse
have access to a Linux or Mac?
2.8.2.0 should work with those.
Sent from my XT907 using Tapatalk
sd_shadow said:
have access to a Linux or Mac?
2.8.2.0 should work with those.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
I guess I could use a live cd. Any other option?
I've tried ADB sideload. That did nothing. Also, if I boot into bootloader from recovery, it comes up in Fastboot mode but I don't think that helps me.
could run flash command,
Code:
fastboot flash recovery filename
when in twrp, then select reboot bootloader
sd_shadow said:
could run flash command,
Code:
fastboot flash recovery filename
when in twrp, then select reboot bootloader
Click to expand...
Click to collapse
Yeah that's mostly the same thing as in your video. I've already tried that. Nothing happens. PC sits at waiting for device and kindle sits in Fastboot mode. Fastboot devices doesn't show anything. Oh, and strangely enough, when in recovery the ADB devices list no longer shows it as being unauthorized. It is now simply offline.
edit: killed and restarted the adb server and now it shows unauthorized again....
Minjin said:
Yeah that's mostly the same thing as in your video. I've already tried that. Nothing happens. PC sits at waiting for device and kindle sits in Fastboot mode. Fastboot devices doesn't show anything. Oh, and strangely enough, when in recovery the ADB devices list no longer shows it as being unauthorized. It is now simply offline.
edit: killed and restarted the adb server and now it shows unauthorized again....
Click to expand...
Click to collapse
Windows 7, 8?
you have used install.drivers.bat from Kindle Fire Utility v0.9.9?
Sent from my XT907 using Tapatalk
sd_shadow said:
Windows 7, 8?
you have used install.drivers.bat from Kindle Fire Utility v0.9.9?
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Windows 7. No, I didn't use the utility drivers because they didn't work. Instead, I used the drivers you showed in your video:
https://www.youtube.com/watch?v=WqY5AUcf0Vk
With them in place, I was able to do all adb fuctions perfectly fine.
Incidentally, the device currently shows an an "android composite adb interface" and not as an "adb composite device" as mentioned here:
http://forum.xda-developers.com/showpost.php?p=52595046&postcount=193
I don't know if that makes a difference. I've tried getting it to point to the folder where the unpacked kindle drivers are it doesn't like them. Something about the kindle is making it work with the wrong drivers. That's the only thing I can think of.
open device manager
reboot Kindle, at bootloader press power button once to open boot menu (stops boot process about 2 mins)
In Device manager>select unknown device>Update driver software>
browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>
show all(uncheck show only compatible)>look for ADB interface or android phone
select yes to Ignore warning
may need to reboot both.
then try fastboot devices
of that doesn't work Retry install.drivers.bat from Kindle Fire Utility v0.9.9 use alt download mirror.
sd_shadow said:
open device manager
reboot Kindle, at bootloader press power button once to open boot menu (stops boot process about 2 mins)
In Device manager>select unknown device>Update driver software>
browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>
show all(uncheck show only compatible)>look for ADB interface or android phone
select yes to Ignore warning
may need to reboot both.
then try fastboot devices
of that doesn't work Retry install.drivers.bat from Kindle Fire Utility v0.9.9 use alt download mirror.
Click to expand...
Click to collapse
FYI, when I use the drivers in the 0.9.9 utility, it installs as a Samsung Android phone and doesn't work. That's how I first went down this rabbit hole of "quickly" rooting the device and putting a non-stock rom on it. I was following your thread:
http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955
But the KFU drivers weren't working.
So I watched your video which showed to use these drivers instead (which worked):
http://forum.xda-developers.com/showthread.php?t=2544410
I've been uninstalling, rebooting, and installing drivers nonstop, trying small variations here and there. I don't know what's going on.
edit: so if I follow your directions, while in bootloader, nothing android or unknown shows up in the device manager. On my last boot, I uninstalled everything and nothing new has popped up. If I prompt to go into recovery, I finally get a single unknown device. If I browse to look for drivers, neither ADB interface nor Android phone are options. Next, I install the kindle fire drivers I linked above. Still unknown. Unplug and plug back in. Still unknown. I install the KFU drivers. And now I have a Samsung phone. ADB shows it attached but it is unauthorized.
edit: I finally got it to communicate in fastboot by NOT installing drivers. It was actually more functional as an unknown device. Flashed the older recovery and then ADB would communicate. Flashed CM11 and gapps. Everything is fine now (though dreadfully slow).
Related
This tutorial All In One is for all owners of the NEW NEXUS 7 FLO (2013 Edition). I've tried to be clear, helpful and simple
....-ox=O=xo-....POST #1 => [TUTO + VIDEO] AIO Unlock Bootloader, Flash Recovery (TWRP) and Root your Nexus 7 FLO
....-ox=O=xo-....POST #2 =>[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK with latest KK 4.4.4
....-ox=O=xo-....POST #3 => [HOW TO] FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND
....-ox=O=xo-....
Warning!
This guide and its guidelines are meant only and only for the new Nexus 7 "FLO" (2013).
Do not attempt to try this on the older Nexus 7 or any other device.
Applying this to any other variant might brick the device.
Read and understand the instructions carefully before proceeding any further.
Click to expand...
Click to collapse
....-ox=O=xo-....
Pre-requisites:
Click to expand...
Click to collapse
THIS GUIDE IS ONLY FOR WINDOWS
1) This point is really important. You’re going to lose all your datas on the device including the internal storage. So back everything up.
2) Download and Install 7zip or any other archive manager as WinRAR etc...
3) Download and install Android SDK
OR
3Bis)Download The ADB and Fastboot Tools in the same Tool ==> platform-tools.zip - md5: 15e771613370afe3c70e0be1454d2ef1 - size: 346.8KB
4) Put these 3 files in where your fastboot folder is installed; ex => => disk C: root
Unzipped this file on the folder "platform-tools" and you will find 11 files:
- aapt
- adb
- AdbWinApi.dll
- AdbWinUsbApi.dll
- aidl
- dexdump
- llvm-rs-cc
- fastboot
- dx
- NOTICE
- source.properties
5) Enable USB Debugging Mode on the tablet to connect it with the computer and use Android SDK with it.
{ Press Menu =>> Settings =>> Applications. From there navigate and click on Development option then check the USB Debugging Mode.}
If you don’t see the Development Options, you'll need to open the Settings app and scroll down to the bottom. Once you get there, tap “About Phone”. Scroll to the bottom again, until you see the Build Number entry.
Now tap Build Number a total of seven times. You'll see friendly developer messages starting with the fourth tap. After the seventh, you'll see a message congratulating you for unlocking Developer Options. “Now you are a developer".
6) At least 70% battery power to avoid uncertain shutdowns during the process.
7) The tutorial is compatible only with the Nexus 7 wifi (2013) FLO.
....-ox=O=xo-....
Process to unlock bootloader of your Nexus 7 FLO
Click to expand...
Click to collapse
-1: Connect the Nexus 7 to the computer using USB cable.
-2: Open a Command Prompt window and type the following command to reboot the device into booltoader mode:
Code:
adb reboot bootloader
-3: Type the following command to lauch the unlock process:
Code:
fastboot oem unlock
-4: You will now be prompted with a dialogue to confirm the process, go through it.
Use the Volume buttons to highlight Yes and select it using the Power button
-5: The tablet will go back to the bootloader screen. Press Power button to select Start to reboot into the unlock device
Before to install the TWRP recovery and applying the root, you need to download the latest version of the TWRP recovery and the latest version of SUPER-SU that you need to push to the root of your sd card - For downloading these files follow the links below
Click to expand...
Click to collapse
....-ox=O=xo-....
Process to install TWRP recovery on your Nexus 7 FLO
Click to expand...
Click to collapse
-1: Download the latest TWRP recovery image file
Download link- TWRP
-2: Open the folder where the recovery image file has been downloaded and rename your recovery "recovery-twrp" simply. Re-open your previous Command Prompt window.
-3: Type the following command to flash the recovery image file
Code:
fastboot flash recovery recovery-twrp.img
-4: The recovery will be flashed and the progress could be observed in the CMD window itself.
Note: To boot the Nexus tablet into Recovery, press the Volume keys (up/down) until Recovery Mode is displayed. Use the Power button to select it and the device will reboot into the TWRP recovery Mode.
....-ox=O=xo-....
Process to root your Nexus 7 FLO - Update
Click to expand...
Click to collapse
-1: Download the SuperSU root package for Nexus 7
or you can use Download link: CF-Auto-Root-flo-razor-nexus7.zip
Explanations for understand why you must use CF-Auto Root => Go to read here the Central Post
-2: Download the ZIP file (see the link above) and Extract the ZIP file
-3: Connect the tablet to your PC using USB cable.
-4:Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolDown+Power to turn it on.
-5:Connect your device to your computer using USB
-6: Open a new CMD window and type the following command:
For Windows
Code:
root-windows.bat
For Linux
Code:
chmod +x root-linux.sh
root-linux.sh
For Mac OS X
Code:
chmod +x root-mac.sh
root-mac.sh
Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your datas !
And if you have some problem with the process, go to see HERE
Now your Nexus 7 FLO running on Android 4.4.4. KitKat should have be rooted with latest TWRP recovery installed and bootloader unlocked. :victory: :good:
If you need more help, following my OP and this video from @clozecall
....-ox=O=xo-....
{
"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"
}
ISSUES
Click to expand...
Click to collapse
If you have some problem after to flash the recovery, and you stay stuck on during 5mn + You need to wipe data and factory reset on settings and normally all should be work perfectly after
Click to expand...
Click to collapse
....-ox=O=xo-....
USEFULL FILES:
Click to expand...
Click to collapse
Recovery_Stock_KK-4.4.4.img - Download link - Md5: 0ce33e5478a93f335f9be94c42057557 - size: 7.4MB ==> NEW
Recovery Stock -SS15QR.img - Download link
Recovery Stock -JSS15Q.img - Download link
Recovery_stock_JSS15J.img - Download link
Recovery_stock_ JRW66V - Download link
Google USB Drivers - md5: 1389bb2de0c9cacce27c76f1c71592ef - size: 8 MB
OEM USB Drivers
USB DRIVERS r_06 for Windows 7 & 8Thanks to @clozecall for his video
and all members for their help
And don't forget to RATE FOR THIS THREAD -
if it's helped you
"Thanks in advance
[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK
[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK - With latest version KitKat 4.4.4
Find your Factory image for your N7 FLO - KitKat KTU84P - Download Link - - is very useful if you need to restore back your device to Stock after any modification you’ve made. If you have rooted your N7 Flo, unlocked its bootloader, installed custom recovery and roms and finally you want decided to getting back to official firmware and then to get or accept future OTA updates again. It’s the best way to restore back your device to Stock.
Coming back to stock is also useful if you have some bugs (for fixing it), Bootloop, stuck in boot screen logo and freeeeezzziiiinnnngggg, etc....But before to going back to stock, you need to read completly the tutorial and need to know
Your bootloader will be “LOCKED or UNLOCKED” when you want.
1 - Where I can can find the right Factory Image for my Nexus 7 Flo and which files I need for proceed ?
But first download and install the necessary files prior to execute this properly. Download the full factory image corresponding to your exact mode which includes the full system, bootloader, recovery, kernel (boot.img).
Unpack the TGZ Version (tar/gz) or Zip Version Archive into its own directory. I use 7-Zip, but you can use any tool that reads gz and tar.
Factory Images "razor" for Nexus 7 [2013] (Wi-Fi) - 4.4.4 (KTU84P) - Download link
If you have already installed those files, just check theirs.
Java Runtime Environment.
Android SDK | Android Developers.
Platform tools
Fastboot files
2 - PREREQUISITES
First make sure that your battery is fully charge 100% and BACKUP ALL YOUR PERSONNEL DATA
[1] - Make sure you have USB debugging turned on. For security purposes, you can turn it off after we're done
[2] - Plug-in USB cable and If you are booted into Android, open a command prompt to your ADB and Fastboot directory,
[3] - In case you are not unlock, you need to unlock your bootloader, enter the following commands:
Code:
fastboot oem unlock
If your tablet hasn't already rebooted automatically, type:
Code:
fastboot reboot
NOW WE ARE READY FOR PROCEED TO RETURN STOCK
3 - RUNNING FACTORY IMAGE
If you want to keep your data intact, don't skip this step, (if you do your data will be wiped )
With your text editor (for me it's Notepad ++,
[1] - Edit (be careful not to run it by accident instead of editing)
[2] - flash-all.bat (if you're on Windows)
[2a] - flash-all.sh (Mac, Linux)
[2b] - and remove "-w" from the fastboot update command
For example, if the line reads fastboot -w update image-razor-ktu84p.zip, it should now read: fastboot update image-razor-ktu84p.zip. The -w option instructs fastboot to wipe data.
Click to expand...
Click to collapse
[3] - Reboot into the bootloader and run the appropriate flash-all script:
Code:
flash-all.bat
Done, your Nexus 7 Flo is now coming back and running Stock Android KK 4.4.4
In Case you want to come back completely to Stock, for warranty or security purpouses, you need to re-lock your bootloader now.
Enter the following commands
Code:
fastboot oem lock
If your tablet hasn't already rebooted automatically, type:
Code:
fastboot reboot
Done!
And don't forget to RATE FOR THIS THREAD -
if it's helped you and eventually click to "Newsworthy Thread? "Thanks in advance
Reserved
[HOW TO] FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES
FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip" or this tool : platform-tools.zip - md5: 15e771613370afe3c70e0be1454d2ef1 - size: 346.8KB
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
OR
Unzipped this file on the folder "platform-tools" and you will find 11 files:
- aapt
- adb
- AdbWinApi.dll
- AdbWinUsbApi.dll
- aidl
- dexdump
- llvm-rs-cc
- fastboot
- dx
- NOTICE
- source.properties
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
CD to where your fastboot or platform tools were installed
The line command is :
Code:
[B]C:\Users\R2D2>cd c:\platform-tools[/B]
Code:
[B]C:\platform-tools>[/B]
OR
Code:
[B]C:\Users\R2D2>cd c:\fastboot[/B]
Code:
[B]C:\fastboot>[/B]
Enter
Code:
[B]C:\fastboot>fastboot flash recovery recovery.img[/B]
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
From this part of your procedure:
"-5: The tablet will go back to the bootloader screen. Press Power button to select Start to reboot into the unlock device
Note: Those who wish to install TWRP and root the device further, do not reboot the device. Leave the device at the same screen."
I still say you have to start and boot before you install TWRP. If you don't you get 0 MB Internal Storage on screen and twrp needs password. Can you verify this?
I had to restore my system.img and start over.
Maybe your version of TWRP does not require a reboot (Start) after OEM unlock?
I've always used clockwork on my phones... can you use clockwork in place of twrp on the nexus 7 flo?
Bricked my N7
Not new to flashing, but I made a huuuuuuuuge mistake today. I accidently flashed the wrong recovery image for the 2012 N7 (yeah, I'm an idiot). I can boot into fastboot and recovery mode, but it fails to mount the sd card so I can't do **** anymore. Can't even get it back to stock t this point Any suggestions? I'm on a mac, but have access to PC. Have tried both CWM and TWRP. TWRP just gives me the password screen and 0mb storage. Can't figure out how to get around it or get my storage mounted. Help!
Stuck in boot screen
"I still say you have to start and boot before you install TWRP. If you don't you get 0 MB Internal Storage on screen and twrp needs password. Can you verify this?
I had to restore my system.img and start over."
Androidfr33k, can you specify how to restore system.img? I also do the following steps without rebooting, now I'm stuck in the boot screen.
Thanks in advanced!
Gareee said:
I've always used clockwork on my phones... can you use clockwork in place of twrp on the nexus 7 flo?
Click to expand...
Click to collapse
For the moment, TWRP recovery is the best way for most of my devices.
I've used CWM during a long time with my old devices (Htc Hero - Desire Z) - for my Desire S, I've used 4EXT recovery and now for all devices, it's TWRP
I'm waiting a CWM recovery for see.
But it's just my advice
Wwdcc said:
"I still say you have to start and boot before you install TWRP. If you don't you get 0 MB Internal Storage on screen and twrp needs password. Can you verify this?
I had to restore my system.img and start over."
Androidfr33k, can you specify how to restore system.img? I also do the following steps without rebooting, now I'm stuck in the boot screen.
Thanks in advanced!
Click to expand...
Click to collapse
I've updated the guide, so I advise you to reboot after unlock your Nexus 7, in order to validate the release.
philos64 said:
For the moment, TWRP recovery is the best way for most of my devices.
I've used CWM during a long time with my old devices (Htc Hero - Desire Z) - for my Desire S, I've used 4EXT recovery and now for all devices, it's TWRP
I'm waiting a CWM recovery for see.
But it's just my advice
I've updated the guide, so I advise you to reboot after unlock your Nexus 7, in order to validate the release.
Click to expand...
Click to collapse
Thanks philos64. My problem now is that I couldn't even boot into the OS, I can get into Bootloader mode or Recovery mode, but I couldn't factory reset (says "failed") or boot pass the Nexus screen. (stuck there for more than 15 minutes).
I'm sort of a noob, any help will be appreciated.
Wwdcc said:
Thanks philos64. My problem now is that I couldn't even boot into the OS, I can get into Bootloader mode or Recovery mode, but I couldn't factory reset (says "failed") or boot pass the Nexus screen. (stuck there for more than 15 minutes).
I'm sort of a noob, any help will be appreciated.
Click to expand...
Click to collapse
Ok, if you want you can try this process which works => For Those Who Semi-Bricked Their Nexus 7 0MB Interal Storage
Wwdcc said:
Thanks philos64. My problem now is that I couldn't even boot into the OS, I can get into Bootloader mode or Recovery mode, but I couldn't factory reset (says "failed") or boot pass the Nexus screen. (stuck there for more than 15 minutes).
I'm sort of a noob, any help will be appreciated.
Click to expand...
Click to collapse
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link
decksy said:
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link
Click to expand...
Click to collapse
Same here, and thanks for the tip!
decksy said:
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link
Click to expand...
Click to collapse
Ok sounds good
Thanks :good:
I will insert in my OP asap
decksy said:
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link
Click to expand...
Click to collapse
It worked! Thanks so much!
I unlocked and rooted my nexus 4 with this method. I already have SDK and fastboot on my Mac. I can go ahead with the N7, right? I don't need a different fastboot version? I'll make sure my SDK is up to date.
Sent from my Nexus 7
eep2378 said:
I unlocked and rooted my nexus 4 with this method. I already have SDK and fastboot on my Mac. I can go ahead with the N7, right? I don't need a different fastboot version? I'll make sure my SDK is up to date.
Sent from my Nexus 7
Click to expand...
Click to collapse
Yep, you should be all set
If "adb reboot bootloader" works when unlocking the bootloader but "fastboot flash recovery recovery-twrp.img" just sits there in Windows with "waiting for device" try using "adb reboot bootloader" again followed by "fastboot flash recovery recovery-twrp.img" to get the recovery image flashed. I don't take credit for it because it was said somewhere in this forum while trying to figure out the problem. My main rig has this problem but my HTPC does not. Same issue I had with my N7/2012.
Thank you OP!! I'm now running cleanrom 1.1 on my N7/2013. Let the ROM's rain!!!!
Video Tutorial
Hey guys, I've made a pretty simple video tutorial on how to Unlock the Bootloader and Root the new Nexus 7.
Here it is:
I know I don't have a well known name on the forums at all, but I thought it would at least be nice to post this. :good:
This guide worked well for me. I was able to unlock the bootloader, and it appeared that I was able to install the TWRP recovery image. However, when it went to reboot, the Nexus 'X' logo is looping. What's the best way to fix this? I can't access the device through the cmd prompt either.
EDIT: Nevermind, was able to get into the TWRP recovery image (I was panicking and didn't press the right buttons).
Note: I let TWRP install SuperSu for me, instead of downloading it and moving it on internal storage myself. Don't know that had anything to do with my issues but just wanted to share a heads-up.
{
"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"
}
Welcome to the Nexus 6 All-In-One Guide. If you are a new user that is looking for the opportunity to take advantage of your device and do it right the first time, this guide is here to point the way. This thread exists to keep all the necessary methods and material in one common place just for you. As always: Do your homework first.
If followed correctly, this guide can be a useful tool. These steps are listed in the order in which they should be completed. The intent is to seamlessly unlock, root, backup and/or flash, leaving as little room for error as possible. This process will erase and/or reset everything on your device. All steps are assuming you have backed up your contacts, texts, pictures, videos, etc. I do not take credit for any of this material or information.
This guide is a compilation of work from across XDA, most specifically users like @Chainfire and @Chromium, that I have simply brought together.
Step 1: Read. Read. Succeed.
Your journey down the Android path of rooting and modifying can be smooth, fun and educational, based on your attempt at learning everything you can before you begin. This is entirely up to you, the user. There is some excellent material here on XDA that I highly recommend reading over as part of step 1. Even though these 2 informational links were written for the Nexus 5, the knowledge still applies so don't skip this information!
A message from the moderators - All users please read
Yep, read it. It's for your own good. Included with some very useful general forum information, it also contains the forum rules which should also be read and understood.
[FAQ][REF]★All you need to know about Android | Read this before you post/root★
This awesome thread by @abaaaabbbb63 is a *noob friendly* collection of information every user that wants to root their phone should know. Many people blindly follow guides without even knowing what "Rooting" means. Hopefully, this will help new users (and old ones, why not?) understand what is happening with their phone, and what they will put up with. Get on over there and read it.
Be sure to checkout Post #2 below for additional information regarding your Nexus 6
Step 2: Installing The Necessary Desktop Tools
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only).
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.
Step 3: Unlock, Root & Custom Recovery
For those of you who want to get most out of your Nexus 6, you will certainly want to root it. Rooting your device provides you as the user many, many benefits. That's why you're here right now reading this. You want it all. Please note that there is always the chance of error during these processes. Bad or faulty USB cables, USB ports, bad/old device drivers on the computer, an active virus scanner. These are a few of the issues that can cause your device to fail to connect or prohibit a successful root/flash. Use good and original OEM USB cables. Uninstall any drivers you may have installed for previous mobile devices and disable your virus scanner.
>>>>>>Before you begin, make sure your N6 has USB Debugging Mode switched on<<<<<<
Before continuing, users must enable Developer Options in the devices settings and select the OEM Unlock option. To do so:
- Go into Settings
- Under About Phone, you'll be able to locate your Build Number
- Tap Build Number until you are notified that you have activated Developer options
- Go into Developer Options, ensure it is enabled and check the Enable OEM Unlock box
- While in Developer Options, ensure the USB Debugging box is checked
Unlock The 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 executing, 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.
Obtain Root
The instructions below and the zip file are the work of our beloved @Chainfire. CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmware and be the quickest and easiest way for your first root.
- Download the ZIP file
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
Follow the on-screen instructions - watch both the computer and the device!
**If you want to have root access only you can stop here.**
A word on custom recoveries: A recovery image is the system level software for your Android that lets you perform several maintenance and recovery tasks. The stock recovery image is quite limited in what it allows you to do and therefore, flashing a custom recovery image is required to gain full control of your device’s administration. A custom recovery image allows you to perform the following tasks:
- Wipe your phone’s data (Factory reset) and cache
- Make, restore and manage backups of your phone’s operating system and software
- Mount, unmount and format your phone’s internal as well as external storage partitions
- Install a custom ROM or application from a zip file to your phone
- Wipe Dalvik cache and battery statistics
- Make logs for error reporting and debugging
Additionally, you can download the Goo Manager app to install TWRP updates.
*NOTE: I do not recommend Rom Manager as a tool to do anything but just install and/or update your recovery Do not flash ROMs from this application.
Installing A Custom Recovery
Go HERE to download the latest TWRP recovery for the Nexus 6.
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.
STEP 4: Making A Backup
Making a Nandroid will allow you to try out new ROMs while still keeping a safe backup in the event you experience issues during or after a custom OS or kernel installation. Be sure your device is fully charged before proceeding to the backup and flashing procedures.
If you are not already booted into recovery then do so now.
1. Boot into fastboot mode (Volume Down + Power)
2. Browse with the volume keys to Recovery Mode and press the power button
3. You are now in custom recovery.
4. In CWM go to Backup and Restore and select Backup. In TWRP select Backup. Name and select the options you want. Swipe to backup.
5. In TWRP, go to Backup and proceed to the next step(s).
6. After backup is finished, select reboot system now or stay in recovery to continue with this guide.
*NOTE: Be sure to save a copy of these backups to your computer and/or micro sd card. Having a recent backup saved to your computer and micro SD card can be useful if something happens to your phones internal memory.
Step 5A: Wiping Your Device
When flashing any ROM, it is always important to follow the proper wipe procedures in order for everything to function properly. There are various levels of wiping based on what sort of transition you may be making. In this guide, I will list the procedures for a full wipe, presuming that you are coming from the stock firmware and changing your OS completely. This is all assuming you have made the appropriate backups. ALWAYS perform the appropriate wipe before flashing a new ROM or update!
1. If you are not already in recovery, boot in now.
In CWM:
2. Select Wipe data/factory reset
3. Select Wipe Cache
4. Select Advanced and Wipe Dalvik Cache
5. Select Mounts and Storage and format /system
6. If you are transitioning from Android versions (4.4 to 4.x, etc) you must also format /data. You will lose all personal data so back it up first.
In TWRP:
2. Select Wipe
3. Select Factory Reset and wipe
4. Select System and wipe
5. If you are transitioning from Android versions (5.0 to 5.x, etc) you must also select Wipe Data and wipe. You will lose all personal data so back it up first.
Step 5B: Flashing a Custom ROM
Once you have selected a ROM for your Nexus 6:
1. Download the ROM. Be sure to download the appropriate Gapps as well.
2. From your PC, place the ROM/Gapps on your internal storage. Remember where they are.
3. Boot into custom recovery.
4. Perform the wipe listed above if you have not already.
5. From the main recovery screen:
>>CWM - Choose the "install .zip from SD Card" and confirm.
>>TWRP - Choose Install and locate the desired ROM on your internal storage.
6. Repeat step 5 and select the Gapps package.
7. Reboot system. It will take several minutes to load so be patient and don't worry. Once the phone is booted, let it sit for 5 minutes, reboot and enjoy!
>>Additional Information
Want the performance boost available with disabling forced encryption? Check out @bbedward's guide linked below for more information and instructions.
[How-To] Disable Forced Encryption
Running Windows 8.x and having device detection issues? Be sure to grab the Google USB drivers and follow the instructions from the link below.
Nexus 6 Driver (ADB, Fastboot and MTP) for Windows and MAC
Need to return your Nexus 6 to stock for resale, OTA or warranty purposes?
Checkout @Mr hOaX's excellent guide. The procedures require the use of the fastboot tool from the Android SDK. See post #1 above for information on installing this if you have not done so already. In his guide, you have the option of returning completely to stock or select specific portions to flash (radio, recovery, etc).
[Guide][How To] Flash Factory Images For Nexus 6
Looking for stock recovery? If you need to revert to stock to receive an OTA, here's the LRX22C Android recovery:
Unzip the image and flash per the norm in fastboot.
View attachment recovery.zip
Maybe I missed it while skimming the guide, but shouldn't there be instructions for people to get Developer Options? Allowing the PC access to your phone on first plug in (ADB won't discover the device without this)? And, most importantly for Nexus 6 (and 9), checking the "OEM Unlock" option in Developer Options?
Added. Thanks for catching that, @Kusanagi Fire :good:
I was just wondering but where are there custom ROMs? Im assuming there are none, but I cant get many things to work
Thanks for all the great info! Would it be possible to add information about removing encryption to this guide?
welp,I got the phone in the mail yesterday and had plans to stay completely stock for a couple weeks,but just couldn't help myself,grabbed the chainfire and twrp files with this guide unlocked bootloader/rooted/ installed custom recovery so here we go ...made my first nandroid already[emoji4]
bogus83 said:
Thanks for all the great info! Would it be possible to add information about removing encryption to this guide?
Click to expand...
Click to collapse
i'll think about it.
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Are the steps the same for a mac?
gotsoot said:
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
yup, but you may lose root and your bootloader may be re-locked if they push a bootloader update with it. just fyi.
the likely (hopefully) worst case is likely that you you have to unlock it again (thus wiping your data) and you have to re-setup the phone and re-root.
i cant guarantee success or failure so you assume all risk when you begin ANY modifications on your device.
Are bootloader updates common for Nexus phones? I can't recall hearing about one (though this will be my first Nexus).
Sent from my Moto X using Tapatalk
There were one or two for the nexus 5
Fastboot
Can somebody confirm that fastboot is working on Windows 8.1 because last time I tried it didn't work and I had to use Ubuntu to fastboot my htc.
I'm running Windows 8.1 but my computer would detect my Nexus 6 after installing the drivers via SDK manager. I followed these additional steps and installed the google USB drivers, and that worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
Great stuff, thanks so much for putting this together!
No need for toolkit or drivers on Mac/Linux
Here's Mac/Linux way.
First create a file on your home folder named something like nexus 6. (This is where your going to save your files.)
Download su(I'll let op point to zip)
Download recovery (same as above from op)
Put them both in that file you created. (Make sure it is in home or you'll have to cd to wherever you put it)
OK make sure you back up your data(this will wipe everything.)
Boot into fastboot.
(Hold power and up/down button)
(Ensure you have adb and fastboot installed on your comp)
cd RootNexus (or whatever you named that folder you created)
*First things first...
./fastboot devices
Should see your device.(if not double check adb and fastboot are installed properly. Follow link. http://forum.xda-developers.com/showthread.php?t=1917237(make sure to click thanks button over there for easy setup.)
.
./fastboot oem unlock
(Follow on screen instructions, this will wipe data. )
./Fastboot restart bootloader.
(Linux users remove ./ in front of fastboot.)
Start up phone and sign in and let it completely boot. Then put SuperSU on device.
On your Mac/Linux
(Ensure you are still in root nexus folder)
./fastboot flash recovery recovery.img where recovery.img is the name of your recovery image file
Once that is done on your phone press the volume up (twice) until you see "Recovery". Then press the power button.*
Once inside recovery go to back up and back up your device.
Flash SuperSU after. Then restart and applaud yourself. Your now rooted. I've been doing it this way since forever
Because decrypting makes such a big change in performance, that would be good to have in this thread as well.
gamewarden234 said:
Because decrypting makes such a big change in performance, that would be good to have in this thread as well.
Click to expand...
Click to collapse
I'm putting together some additional information for post #2 of this thread. It will include decryption. :good:
gotsoot said:
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
I would like to know this also.
*nevermind*
Notice: Rooting your device will break OTAs because they require an unmodified system, so you might want to check for updates before rooting your X. However, there is a workaround:
Boot into TWRP via step 5E below, but DO NOT flash it (step 5D)!!
Do a backup of your completely stock, unrooted ROM
Root the device by flashing SuperSU...zip
When an OTA hits, you can get it by doing this:
Boot into TWRP again without flashing it (same as step 1 above)
Restore your stock, unrooted ROM (from step 2 above)
Apply the update from stock recovery
Backup the unmodified ROM with the update if you want, then re-root as above.
Note: You will lose any changes, mods or app data since you did the backup, but hey, at least the OTA is applied.
If you get stuck with an update that won't flash and you haven't backed-up your unrooted ROM as above, look here:
[Guide] How to Install OTA's with TWRP, and please hit thanks for @SpiritBreak3r :good:
_____________________
Disclaimer: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try. If you get confused with terminology, try looking here for answers or Google it. If you get stuck, post a question in the thread—we're here to help you.
Preliminary steps
1. Make sure that your phone is always charged above 50%!!!
Running out of battery in the middle of flashing something could brick your phone.
2. Make sure that your computer can properly communicate with the device:
We will be issuing commands to the phone from your PC via the USB cable using Android’s SDK tools, in particular ADB and fastboot. If you have not done so already, you must install the following on your Windows computer for this to work:
Java runtime
The Universal Android ADB Driver for Windows.
SDK tools for Android (alternately just ADB & fastboot). Remember where this is installed on your harddrive for later!
You can verify the connection between your PC and phone by running the following procedure:
A. With the phone booted normally, connect it to your computer with the USB cable.
B. Enable Android debugging by going to Settings > About phone and tapping on “Build number” 7 times.
C. Go to Settings > Developer options and check “Android debugging”. A dialogue box will appear asking you to authorize your computer’s RSA fingerprint. Click “Always allow...”
{
"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"
}
D. Open a command prompt in Windows and navigate to the folder where you put SDK tools for Android (ADB & fastboot) above.
E. Type the following command:
Code:
adb devices
You should get a return like this:
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
3. Know how to enter “fastboot mode” on the OnePlus X
To root the device, you must be competent at booting it into fastboot mode. There are two ways to accomplish this:
Power off the phone. Then simultaneously hold down the volume up & power buttons until it vibrates. When done correctly, you will see the words “Fastboot Mode” on a black screen. If not, you dumb-thumbed it, and the device will boot normally into Android. Power off the device and try again.
With the phone running Android normally and Android debugging enabled (see above), open a command prompt in Windows, navigate to the folder where you installed SDK tools (ADB & fastboot) and type:
Code:
adb reboot bootloader
Rooting the OnePlus X
There are three essential steps to rooting the device:
Unlock the bootloader
Flash or boot into TWRP custom recovery [For OxygenOS 3.1.3 use TWRP blu_sp★rk r175]
Flash SuperSU...zip from recovery [For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta]
However, we're going to add a few more to protect your data and device in case something gets borked.
1. Backup your phone’s data
Unlocking the bootloader will involve doing a factory reset resulting in the loss of all accounts, emails, texts, apps and app data, pictures, music, etc. on the device. Move anything you need to keep onto your PC or a cloud service like DropBox.
2. Unlock the bootloader
2A.Go into Developer Options and enable bootloader unlocking
2B. Boot the device into fastboot mode. (Simultaneously hold down the volume up & power buttons until it vibrates.) You should see a black screen with the words “Fastboot Mode”.
2C. Plug in the USB cable.
2D. Verify that your device is connected with this command:
Code:
fastboot devices
You should get a return like the image above under Preliminary Steps
2E. Unlock the bootloader using the following commands:
Code:
fastboot oem unlock
The device will unlock the bootloader, erase all user data and reboot itself into Android. You will have to set up everything from scratch.
3. Re-enable Android debugging
3A. Re-enable Developer options by going to Settings > About phone and tapping on “Build number” 7 times.
3B. Go to Settings > Developer options. Check “Android debugging” and re-authorize your computer’s RSA fingerprint.
4. Download SuperSU zip
4A. Head over to Chainfire’s CF-Root thread and download the SuperSU access management tool from the “CWM / TWRP / MobileODIN installable ZIP” link. It will probably called something like UPDATE-SuperSU-v2.XX.zip. This zip file will root your device and install the SuperSU access management app in one smooth motion. Hit the thanks button for Chainfire or donate to his Paypal account and buy him a Coke.
NOTE: For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta
4B. Copy UPDATE-SuperSU-v2.XX.zip to your phone’s SD card.
5. Flash TWRP custom recovery
5A. Download TWRP recovery.
NOTE: For OxygenOS 3.1.3 use TWRP blu_sp★rk r175
5B. Place file you downloaded above to the location where you installed SDK tools (ADB & fastboot).
5C. Boot the device into fastboot mode and connect it to your computer with the USB cable.
5D. In this step, we will replace your stock recovery with TWRP recovery.
Note: This step is optional. If you want to root but preserve stock recovery, skip straight ahead to step 5E below. Thanks @rockuppl for the reminder. :good:
Open a command prompt in Windows and navigate to the folder where you installed SDK tools (ADB & fastboot). Type the following commands:
Code:
fastboot flash recovery twrp-3.0.0-0-onyx.img
5E. Reboot into TWRP recovery with the following command.
Code:
fastboot boot twrp-3.0.0-0-onyx.img
You should now see the custom recovery you just flashed, not the stock recovery.
6. Backup your stock ROM before making any changes
In TWRP press “Backup.” <--- See how simple this is???
Don’t be a noob—backup your device!!! Right now we don't have stock boot debuggable image files for the OnePlus X, so borking your device could leave you with a nice paperweight until we do. :crying: Restoring from a backup in recovery is easy, and only works if you've backed-up first
7. Root the device
7A. The device should still be in recovery from step 6 above. Go back to the main menu and press “Install,” find UPDATE-SuperSU-v2.XX.zip on the SD card, then flash it.
7B. Reboot the phone. It is now rooted!
7C. Go to the app drawer and open SuperSU. Update the binary if prompted. Its icon looks like this:
7D. Download and install Root Checker from the Play Store to verify that you have root access.
Yes I already own the phone and I see the bootloader unlock switch in dev options. I also checked the stock recovery which gives options to flash files from phone memory or otg. So it must be fairly easy. But I still don't want to risk it without it being tried and tested. If there were a custom recovery I could have also backed up the factory image. Only choice is to wait and see I guess
I could try today evening... will update here.
@CafeKampuchia
Is it ok to flash supersu.zip with stock recovery.
Before flashing supersu.zip, will unlock bootloader . Will follow the guide from oneplue two procedure to unlock..
Flashing supersu is safe on hundreds of devices, but I don't have the X so I can't say one way or the other.
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
CafeKampuchia said:
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
Click to expand...
Click to collapse
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Knockys said:
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Click to expand...
Click to collapse
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
CafeKampuchia said:
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
Click to expand...
Click to collapse
My bad then ahah
mjose said:
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Click to expand...
Click to collapse
Yes it fails on stock recovery, we'll have to wait for a custom one indeed...
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Savya said:
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Click to expand...
Click to collapse
Hey i need your help, i installed the custom recovery in Mandarin but i don't understand anything! Could you please tell me where i should go in this recovery to wipe dalvik cache and flash super su? Step by step? Thanks!
Works for me too ! I'll try to install Xposed now ahah !
Hope they'll release TWRP in English soon !
EDIT : Xposed installed and working ! For those who don't know how to do, see here
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
CafeKampuchia said:
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
Click to expand...
Click to collapse
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Savya said:
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Click to expand...
Click to collapse
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
ukanth said:
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
Click to expand...
Click to collapse
Just flashed it now!
Confirmed that its working and its in English!
Thanks a ton mate!
Also do i have your permission to post your link in the oneplus forums? As there are many users there too waiting for an english version.
@ukanth : shared the recovery on my post on the OP forums
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
How to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission on the Latest MIUI 8 - V8.0.6.0.LHOMIDG. (as of 22-11-16)
Here you have the step by step procedures to successfully unlock your Redmi Note 3 SnapDragon global variant with latest global stable rom MIUI 8. Please follow the steps carefully.
The rom used for this procedure is the latest global stable fastboot rom MIUI V8.0.6.0.LHOMIDG.
This is the working guide for the Xiaomi redmi note 3 (SD) on latest MIUI 8.0.6.0 as on 22-11-2016. I did lots of experiments, bricked my device several times to find this working guide for latest rom, however you are free to link to this page for reference.
You dont need to apply for official unlocking and wait for a month or more to get the sms confirmation from xiaomi to officially unlock the bootloader, the problem with the official method is many users have reported that they did not receive the confirmation sms from xiaomi, even if they receive the confirmation sms the unlocking process stucks at some percentage and fails to unlock the bootloader. So for everyone here is the easy way to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission.
First of all take a backup of all important files from your phone to your PC before starting. Because all data will be formatted while flashing the rom.
I have simplified most of the procedures and complicated works for this guide. A good part of the credit goes to some other developers because their works were helpful to me for experimenting to find this working full unlocking guide for the latest miui rom for redmi note 3 (SD) as of 22-11-2016.
REQUIREMENTS:
Xiaomi Redmi Note 3 (SD) Mobile
Micro USB data cable (or) compatible usb cable
Desktop or Laptop (Widows based)
Download all the tools, rom and other files from this androidfilehost folder link and keep all files in one folder for easy access:
https://www.androidfilehost.com/?w=files&flid=137618Files List:
1. AnF.zip
2. fastboot_edl.zip
3. Fastboot Rom: "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz"
4. MiFLash_v2016.08.30.0.zip
5. minimal_adb_fastboot_v1.4_setup _working.exe
6. MiPcSuiteSetup_v3.2.1.3111_2717.exe
7. Root Checker Basic v5.9.7.apk
8. SR1-SuperSU-v2.78-SR1-20160915123031.zip
9. twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip
10. ADBdriversetup.zip (alternate use, in case device specific drivers are not properly installed)
***Carefully remove your sim card & sd card from mobile (if inserted) before you begin and do not connect to internet until all steps are completed, because the phone would automatically sync with Xiaomi servers at first boot and may cause problems.
Make sure your phone is charged 60% and above.
The complete video go through of step by step procedures in this guide is available in this YouTube video,
https://www.youtube.com/watch?v=rj4gVMk3y0o
FOLLOW THE STEPS CAREFULLY, IF YOU FACE ANY TROUBLE, START OVER AGAIN FROM STEP 1, IF YOU FACE ANY OTHER ERROR OR BOOTLOOP OR STUCK IN LOGO LOOK AT THE TROUBLE SHOOT SECTION AT THE BOTTOM.
Step 1:
Enable Usb Debugging, if not done before:
Open Settings in your device"Redmi note 3 (SD)", scroll to bottom in settings and click on "About phone" and now tap on MIUI version 7 times, it will show a message like "You are now a developer" and Developer options will be revealed.
Next go back to Settings main screen and then -> Additional settings -> Developer options -> Enable Developer options, Enable OEM Unlock, Usb Debugging.
{
"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"
}
Note: After that when you connect your phone to the Pc to execute adb commands, a prompt may appear on your phone with computer's fingerprint key, you should confirm it when it appears. In case if you already done this for your computer with proper adb drivers installed, you don't need to bother about this.
Step 2:
DISABLE DRIVER SIGNATURE ENFORCEMENT IN YOUR PC:
You now have to disable driver signature enforcement in your PC, to do this you have to open the settings window by pressing the shortcuts"Windows button + i -> Update & Security -> Recovery -> Advanced startup -> Restart now. Now the system will logout and show Recovery options, from there select Troubleshoot -> Startup Settings in Advanced options -> Restart. Your system will now reboot and show the "Startup settings" screen, a list of options will be available, you have to choose option number 7 to disable driver signature enforcement. Then the system will boot into the OS with driver signature enforcement disabled. After that do not restart your pc until all the below steps are completed, in case if you restart your pc for any reason you need to redo this step again because system reboot might enable driver signature enforcement again. That's it. Refer this video if you need further guidance.
Step 3:
To install ADB, Fastboot and other drivers in your PC:
Install the " minimal_adb_fastboot_v1.4_setup _working " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiPcSuiteSetup_v3.2.1.3111_2717.exe " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiFLash_v2016.08.30.0.zip " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Step 4:
Extract AnF.zip file and execute the commands:
Now extract the "AnF.zip" file downloaded from the link I provided above. Connect your phone to Pc using the Usb cable. Open the extracted AnF folder and double click on the cmd.exe file, which will open a adb command window from there.
Execute the below command through adb command window to check and confirm the phone is connected via adb interface. If connected properly it should show device serial like "******** device"
adb devices
Incase if your phone shows a prompt for computer's fingerprint key approval, allow it. Then execute the command again. You should see your phone serial number as shown in the image below, which means your phone is properly connected via adb. Incase if the device is not connect properly via adb, disable and enable USB debugging on your phone. If that also helping to install the phone's adb drivers, extract and run the"ADBdriversetup.zip" downloaded from the link I provided above to install the specific drivers for your phone.
Step 5:
Reboot the phone to EDL mode:
Now you have to reboot your phone to edl mode aka Emergency download mode. To do this execute the below command via adb window with phone still connected to Pc.
adb reboot edl
Your phone will now reboot into blank screen or edl mode and new driver named "qshusb qloader 9008" will be installed in your Pc, now only red led notification light will be blinking on your phone. Once the driver is installed properly, the phone is now connected in edl mode. Now close the adb command window.
Step 6:
Setup MiFlash Tool & Flash the ROM:
Open the MiFlash tool (MiFLash_v2016.08.30.0.zip) application you installed earlier, click refresh button and your phone will be visible as port number (ex: COM10) in MiFlash tool. Exe file is in this path,"C:\Xiaomi\XiaoMiFlash"
Now extract the "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz" fastboot rom file downloaded from the link I provided above. In your MiFlash tool window, click the Browse button and locate the extracted fastboot rom folder. Then select "clean all" button at the bottom of MiFlash window. The flash tool is now configured. Now click the Flash button.
Wait for few minutes for the flashing process to complete, once the process is complete and MiFlash tool window will show task finished. But do not disconnect the phone.
Step 7:
Reboot to Fastboot mode & execute Fastboot commands:
Now while the phone is still connected to your pc, reboot your phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the boot screen and release, the phone will now enter into fastboot mode.
Now double click and open the cmd.exe file from AnF folder you extracted earlier to open the command window. Then execute the below command.
fastboot oem device-info
This command will show you the current bootloader status. The bootloader status shows "Device Unlocked: False", execute the below command in command widow, it will Unlock the bootloader.
fastboot oem unlock-go
Your device might restart now, if restarts press Volume down button and Power button simultaneously to reboot phone to fastboot mode again to check your bootloader status again by executing the below command. It should show "Device Unlocked: True" in the command window. Which means the device's bootloader is unlocked.
fastboot oem device-info
Now to flash TWRP recovery and Supersu for root permissions, jump to step 8, or if your aim is to unlock the bootloader only, you may restart your phone and skip all below steps.
Step 8:
Flash TWRP:
Now restart phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the fastboot screen.
Extract the "twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip" file downloaded from the link I provided above to the AnF folder.
Then open the AnF folder, double click and open the cmd.exe file, paste the below command in the command window to flash twrp recovery.
fastboot flash recovery twrp-3.0.2-2-kenzo.img
After flashing the recovery image reboot the phone to TWRP recovery by pressing Volume Up button and Power button simultaneously until you see the boot screen. It will boot the phone into TWRP recovery, on the front screen just swipe the slider to mount system as read only. That's it now to flash supersu proceed to step 9.
Step 9:
Flash SuperSu:
While the phone is in TWRP recovery connect the phone to Pc, it will be detected as mass storage device, just copy the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" file downloaded from the link I provided above to your phone's mass storage device.
On the twrp menu click on Install option and locate the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" to install via twrp, now swipe the slider to right to install supersu to have root access in your phone's OS and then wipe dalvik cache using the button below in twrp.
If twrp shows any read/write error while flashing supersu, on the twrp mainscreen choose mount option and click on system in the next menu, then go back to main screen and try again to install.
That's it, now supersu is installed, to check the root status follow to step 10.
Step 10:
Check root status:
After completing all the steps successfully, reboot the phone into the system normally and complete the initial setup without Sim card, the first boot may take a little more time to boot into OS, In case if the phone stuck in boot screen for very long(10+ mins), go to troubleshoot section at the bottom and start over the steps. Otherwise you are good to go.
Connect device to Pc after initial setup completes, now copy the "Root Checker.apk" file to your phone and install it, open the root checker app and click on verify root, you will be prompted by Supersu for root permission, allow it, your root access will be verified. Voila, you have successfully rooted, flashed twrp and installed supersu on your Redmi Note 3 with latest rom installed.
That's it. Now you are ready to rock.
KNOWN ISSUES:
No issues found so far, in case if you find any issues after successfully unlocking using the above method, kindly let me know.
After successfully unlocking your bootloader, incase if you update your rom via official updates, your will lose root access and twrp custom recovery and may end up with locked bootloader again, if you face this situation by some reason, you may start over and follow this guide from step 1 to revert back to unlocked bootloader. Do not update the rom and turn off automatic updates in settings as a precautionary measure.
Troubleshoot:
If your device gets bricked or Stuck in Boot logo, try this,
Reboot your phone into edl mode by following below step.
If you are stuck on bootscreen, you may not be able to enter into edl mode using the normal method above because of bootloop or Stuck in Boot logo, in that case try this method to enter into edl mode from fastboot, download "fastboot_edl.zip" file from the link I provided above, extract the zip file and open the extracted folder, connect the phone to your Pc in fastboot mode(vol down + power), double click and run this file "edl.cmd", the phone will automatically enter into edl mode if the phone's drivers and adb drivers are installed properly.Now follow step 6 and follow on from this step.
If QHUSB_BULK drivers are not properly installed while the phone in edl mode,
If QHUSB_BULK drivers are not installed while the phone in edl mode, your device may not be visible in MiFlash tool(ex:COM10) even after you click refresh button, in this case open the device manager in your Pc, the phone will be visible as QHUSB_BULK with some alert sign, right click on it and select Update driver software. Then click browse my computer and browse to the location of the driver files in path "C:\Program Files\Xiaomi\MiPhone\Qualcomm\Driver" and proceed and when prompted to Install this Driver Software anyway, allow it and complete the driver installation. Now open MiFash tool and click refresh button your device will be detected in MiFash tool, now you can flash the fastboot rom by following the steps above.
Does this work for Kate version also? OP doesn't specify
Will I lose my warranty by using this method of bootloader unlock?
This method still works for Global Snapdragon phone. Finally got it last night after 2 days of torture (I didn't sleep).
The important part is firstly the image with the modified file you are going to flash to the phone. Here he is using v8.0.6.0 which is the newest (and now last) update for android 5.1 (which is needed, phone will not flash 6.0 without a proper Cache and data clear). I ended up using version 7.3.2.0 which is 1 patch before the version my phone came with (7.3.7.0). Then I replaced emmc_appsboot.mbn with the one from here then flashed the file in EDL mode.
After the flash is done is just as important I found. You place it in fastboot mode (power button + vol down) and run a script. I wasn't able to manually unlock the device via cmd line 'fastboot oem unlock-go'. Instead I found a script that worked from here called 'Root_Folder' (this site also has majority of the files needed). You use the script called 'Root' in the folder to finish the unlock. Notice there is a 'recovery.img' in the folder as well, I replaced it with ZCX TWRP.
Now run through the script after the flash in fastboot mode. Follow the instructions from script, sometimes you take cable out or force phone back into fastboot mode. The key goal here is to have the script boot into TWRP in the end. If this happens you can do all that's needed now.
Another thing I noticed was you have to give debug permission to computer your using and save permission. Debug mode/oem unlock - connect cable, on phone you should get a prompt to accept PC and save permission. If you don't get this prompt make sure you have ADB and Fastboot installed.
Important steps are:
1. Phone connect to computer via debug/oem mode.
2. Flash correct modified ROM with MiFlash in EDL mode.
3. Once flash is done hold power and volume down button for fastboot mode.
4. Run script to attempt to unlock bootloader and/or install TWRP.
MikeyLee said:
Does this work for Kate version also? OP doesn't specify
Click to expand...
Click to collapse
You would have to look it up for Kate specifically. If anything at all that changes it's the Image you use to flash the phone.
zeon321 said:
Will I lose my warranty by using this method of bootloader unlock?
Click to expand...
Click to collapse
Don't think so. You don't 'officially unlock it' and you can flash a stock image that relocks the phone automatically.
Thank you works 100% !!!! :laugh:
After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.
zeon321 said:
After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.
Click to expand...
Click to collapse
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).
Narcle said:
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).
Click to expand...
Click to collapse
Thanks, I flashed old version of twrp and formatted the storage. Now phone is working fine.
Can i use this tuto on a Redmi note 4 MTK?
Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !!
Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !! @Sci Subi
Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html
W7nstroll said:
Can i use this tuto on a Redmi note 4 MTK?
Click to expand...
Click to collapse
This method is for Redmi Note 3 pro, (Kenzo) variant.
can i use it for global stable 8.2.3 ??
The heart of this - the unofficial bootloader unlock - are taken from: http://en.miui.com/thread-345728-1-1.html (It's generally polite to link your sources).
This _does_ work on `kate`. However, this is using a modified 'emmc_appsboot.mbn'. If you flash an original emmc_appsboot.mbn, you may well find your bootloader no longer unlocked and you needing to reflash your device back to stock.
Also, for those wanting to use it on kate (because Xiaomi seems singularly incompetent when it comes to supporting the official bootloader unlock for that devcie): your device will identify itself as a kenzo, so you may have trouble flashing things like the 'miuifirmware_x.zip' updates for kate. Also, those 'miuifirmware_x.zip' files often include the emmc_appsboot.mbn, so be careful.
On another note, if anyone has an actual infallible method to get an official bootloader unlock for the kate device, please let me know.
Can I use this method for 2GB / 16 GB version of Redmi Note 3 Pro (Snapdragon)?
Thanks
Works Thanks
Tested On 18/05/17
This method works But You are stuck on a older rom with no OTA/Later Updates. Method Does not work with MM Roms.(Maybe with different emmc_appsboot.mbn it would work.
Some Pointers
I was on MIUI8 before using this.
1. This downgrades your ROM from the latest ROM, therefore Points to follow.
2. Use This Method Instead Works with latest firmware as on date.
Works, Simply Nicely Perfectly Done, Just follow the steps things will never goes wrong. :highfive:
Sci Subi said:
Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html
Click to expand...
Click to collapse
hi my phone was on miui 8 marshmallow i used the above method nd flashed the rom ( rom is 5.1.1) which is given after that unlocked bootloader nd installed twrp also but now i downloaded a new rom nd i want to flash it i placed the rom in micro sd card nd wiped everything in phone nd flashed the rom with gapps now phone boots but its stuck at the boot logo of the rom i also tried many other roms of 7.1.1 but same is happening phone is not going ahead its stuck in the rom boot logo what should i do also when i flashed that given rom when i charge the phone the red light blinks which seems like edl light help me out of this !! thanks in advance !!
You have flashed a recovery rom and that's why you are in bootloop.
Try to flash in EDL mode a fastboot rom.
PS: Hope you haven't tried to downgrade already because you can loose IMEI and baseband.
Hello,
I am new to phone rooting/modding, this is my first time trying to install a custom ROM (lineageOS) to my OnePlus 8 Pro.
First, I followed this guide for rooting, installing TWRP and then Magisk. The only different thing that I did was, when flashing TWRP, not usingfastboot flash recovery twrp-image-filename.img, but fastboot flash recovery_a/b twrp-image-filename.img, because I read that the former may lead to a boot loop.
Everything worked. Then I proceeded to Install LineageOS on instantnoodlep, where it said I needed to upgrade my stock OS to Oxygen 11/Android 11 first (it came with O10/A10). I did that successfully.
However, it turned out that O11/A11 had overwritten TWRP with the stock recovery. So I flashed TWRP again. This too was successful.
I decided not to install the LineageOS with the LineageOS recovery, as in the official guide, but through TWRP. I copied the LineageOS image to phone memory, booted to TWRP, selected Wipe and did a Factory Reset - Wipes Data, Cache and Dalvik (DID NOT choose Advanced Wipe, probably this was the problem?)
After the reset, I selected the LineageOS ZIP file and installed it.
After booting to system, LineageOS starts loading, but after 4-5 mins I see
QUALCOMM CrashDump Mode
--------------------------------------------------
Panic requested on external modem boot failure
mdm_force_reset
Any help for getting out of this?
It will be MUCH appreciated.
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
MaybeDontAsk said:
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
Click to expand...
Click to collapse
The unlock command would be:
Code:
fastboot flashing unlock
Thanks for the suggestions, I will try them when I get to my home PC, I'm at work now.
In the meantime: can someone explain to me what is the exact procedure for installing LineageOS with the latest TWRP image? More specifically, which options in "Advanced Wipe" should be checked, because in all the tutorials I found they were using old versions of TWRP which did not include the "system" option. Mine had it, so I decided not to use Advanced Wipe at all and use the default wipe options (this is also what they did in one of the tutorials). Could this be the cause for the crash dump error?
Also, I am kind of reluctant to re-lock the bootloader and go back to stock OxygenOS. I still have access to the (LineageOS) recovery mode (it overwrote TWRP). Can I try doing something from there, like maybe overwriting it with TWRP again, then wiping everything (the right way) and installing LineageOS again?
Well when ever I get a Qualcomm crash dump error I always like to go back to stock and re do everything fresh just in case something else goes wrong but if you just don't wanna go back to stock you can do this:
If you wanna overwrite lineage os recovery you can reboot into the bootloader, and just do fastboot flash recovery (drag and drop twrp image here)
So it will be something like:
Code:
fastboot flash recovery C:\Users\YourUsername\Desktop\(recovery name).img
Or if you have the twrp image in the same place at platform-tools you can do:
Code:
fastboot flash recovery (recovery.img)
Or a one time twrp boot:
Code:
fastboot boot C:\Users\YourUsername\Desktop\(recovery name).img
Or:
Code:
fastboot boot (recovery name).img
But like I said it's probably better to re-lock the bootloader to start fresh then you can unlock it again and do anything else. Good Luck.
Anyways in TWRP Navigate To:
Wipe>Advanced Wipe> Dalvik/Cache>Data>swipe to wipe
Go back to TWRP home
Advanced>Adb Sideload
Now in PC cmd do:
Code:
adb sideload (drag and drop lineage os zip here)
Hit Enter And Wait Until It Finishes Flashing
Now For The Google Apps (GAPPS):
Download Nik GAPP From:
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
Select "Download"
Then look through all packages and read what each one contains, I would go with either core or basic. But you may need another apps so just read and choose.
Once you choose, click "download now"
Navigate To Folder
Releases>NikGAPPS R if lineage is 18.1(Android 11)>Latest Version>then choose from here and download.
Back to TWRP
If the download for gapps Finished:
Navigate to:
Advanced>adb sideload
Back On CMD:
Flash Gapps:
Code:
adb sideload (drag and drop NikGAPPS zip)
once it finishes:
On TWRP go back to home menu and navigate to:
Wipe>Format Data>Type "yes">Hit Enter>Go Back To TWRP Menu>Reboot>System if it says "no rom is installed" just swipe to confirm reboot, Lineage OS Is Actually Already Flashed. Good Luck!
I know this is long but it's really not lol.
@MaybeDontAsk
Thanks a lot! I will try again via TWRP first. I don't want to re-lock the bootloader just yet, because I fear something may go wrong in the process and I may end up with a bricked phone AND a locked bootloader, and that will really be the worst scenario, from what I've read in forums.
As for the GAPPS part - I don't plan to install them. Just a LineageOS image will be fine.
Alright well hope everything goes well and yeah I also feared I may end up bricking my device with the msm download tool but I've already done it multiple times.
It has fixed a lot of issues for me wether it is that the device is booting straight into recovery or fastboot or that it's not even booting up!
Just something about TWRP: when I tried just booting to it, the phone froze on the "Fastboot Mode" splash screen and stopped there. So I had to use the flash option.
Also, about flashing: I should use
Code:
fastboot flash recovery (recovery.img)
and not
Code:
fastboot flash recovery_a (recovery.img)
fastboot flash recovery_b (recovery.img)
right?
Just double checking to make sure.
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
{
"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 forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
freeride01 said:
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
View attachment 5543241
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
Click to expand...
Click to collapse
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
MaybeDontAsk said:
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
Click to expand...
Click to collapse
Alright.
I gotta find a Windows PC though, I am on Linux/Fedora.
My OxygenOS before the wipe was 11.0.10.10.IN11BA, I guess from the list I should download "OOS 11.0.4.4", because its the latest.
I'll post again when there is some progress.
MaybeDontAsk said:
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Click to expand...
Click to collapse
OK, I got my hands on a Windows 10 PC. I downloaded and extracted the MSM tool and watched the video you linked.
There is no Win7 version of the .exe file, so I guess I'll use the "normal" one anyway.
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
freeride01 said:
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
Click to expand...
Click to collapse
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
MaybeDontAsk said:
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
Click to expand...
Click to collapse
Hi again,
I did the whole process again and when I did adb sideload I got this:
Code:
[[email protected] phone root]$ adb sideload lineage-18.1-20220214-nightly-instantnoodlep-signed.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Now what? There's a slide in TWRP that says "Swipe to start sideload", should I swipe it?
EDIT: Maybe Ishould use adb install as described here?
No, you need to reinstall the adb interface drivers, search up on how to do it on Linux.
Tht link you put is for installing apk directly from adb and not roms.
But adb seems to work, adb devices returns my phone ID.
It says something like "(Device ID) | Sideload?
If yes then reboot both the laptop/pc and phone.
Code:
[[email protected] phone_root]$ adb devices
List of devices attached
19356f32 recovery
(changed some digits in serial no. for privacy)