Related
This HOW-TO is meant for individuals who like to do things manually and see each process as they occur, versus using a toolkit. I prefer manually unlocking/rooting as I can confirm each step visually and I believe it makes for a more educational experience. Familiarity and confidence with fastboot/adb can be beneficial later on for restoring/troubleshooting/flashing etc down the road.
Unknown at this point if OTA updates will install after flashing CWM. There may be a check file in the OTA that could prevent installation if modified file structure is detected. I’ll edit when I confirm. At any rate, not really an issue as you can flash the OTA yourself as someone on XDA will most likely post it up, or you could re-flash the stock recovery using fastboot which you will now be comfortable with after using this guide! Additionally, if an OTA causes you to lose root you can revisit the appropriate steps to flash SuperSU again.
There are several ways to do these procedures, and I’ve certainly taken the long way on some of them. So by no means am I claiming this to the best or most efficient method, but my hopes are to make things a little more clear and simple based off some of the questions and challenges I’ve seen in a few threads.
This how-to was written for Windows and uses adb and fastboot for installation.
Please let me know of any corrections, additions or errors. Many thanks to the members and devs who made these files available.
1. Download all of the following files and place them in the same directory. I will note whether you need to extract them or not.
Download and extract platform-tools-v16.zip from here: (thanks to efrant)
http://forum.xda-developers.com/showthread.php?t=1626895
Download and extract [ADB/FB/APX Driver] Universal Naked Driver 0.72 from here:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Download SuperSU from here: (look for UPDATE-SuperSU-v1.25.zip or current version)
http://forum.xda-developers.com/showthread.php?t=1538053
Download ClockworkMod from here: (look for Galaxy Nexus 7, Download Recovery 6.0.3.1 or current version – Recommend non-Touch as of ver 6.0.10, some reported issues with the Touch version)
http://www.clockworkmod.com/rommanager/
2. Now we will install the drivers and verify they are working. If you cannot verify drivers are functioning in both normal boot and recovery you need to stop and figure out what you are doing wrong. Proceeding further would be pointless. If you are having trouble, visit the Naked Driver thread listed above or here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
a. Make sure you have USB debugging enabled on your Nexus: setttings ->develop options ->USB Debugging.
b. USB connect your Nexus to your Windows pc. If you get a notification for unknown/driver not found, look in Device Manager for the exclamation point, and right click for update driver software, then browse my computer, then point to where you saved and extracted the Universal Naked Driver folder. If you get a warning from Windows complaining the driver is not signed, hit ‘Install driver anyway’. After the driver installs, you should now have ‘Nexus 7’ listed under ‘Portable Devices’ with no exclamation point.
Now we will verify using adb. You will need to launch a command prompt from the directory you saved all the files from step 1 to. Easiest way is to navigate to the directory via file explorer, then hold down shift and the RIGHT mouse button, and select “Open command window from here”.
In the cmd prompt, type:
adb devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again. You should see something like:
List of devices attached
945d3339495 device
if instead you see:
List of devices attached
945d3339495 offline
then most likely you need to look on your nexus for a notice to allow the connected computer permissions to use usb debugging. If you don't see a notice, disable/enable usb debugging in "Settings -> Developer options" and then you should get the prompt. You should select 'remember this computer', if not you will have to do it again upon reboot.
c. Now we need to reboot into the bootloader and load the drivers again. So type:
adb reboot bootloader
and your Nexus should reboot into the bootloader. My laptop found the driver on its own, note that in Device Manager it is now listed as ‘Android Device’ instead of under ‘Portable Devices’. If your system does not find the driver, follow the same steps as above to update your driver after you located the exclamation point in Device Manager.
Now we will verify that the driver is installed correctly while in the bootloader. Again from a command prompt opened from the directory where you saved all the files from step 1, type:
fastboot devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again.
3. Perform device unlock. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! Please backup accordingly.
Your Nexus should still be in the bootloader. Type:
fastboot oem unlock
Your Nexus will prompt you to accept. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! After a short moment, the device should report unlocked under “lock state”. Reboot device by typing:
fastboot reboot
After rebooting, sign in, etc.
4. Copy over SuperSU . In windows explorer locate the UPDATE-SuperSU-v1.25.zip and copy it to your Nexus internal storage area. Don’t put it any of the folders, just dump it in there. Now reboot into the bootloader again by typing:
adb reboot bootloader
5. Flash CWM. Once in the bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
after you get ‘finished’ from the command window, reboot your Nexus into CWM recovery by navigating with the volume buttons to ‘recovery mode’, then press power button.
6. Root Nexus. Using the volume keys, navigate to ‘install zip from sdcard’ and hit the power button. Now select ‘choose zip from sdcard’ and hit the power button. Navigate down to UPDATE-SuperSU-v1.25.zip’ and hit the power button. Select ‘Yes’, hit power. Once done select ‘go back’, then ‘reboot system now’.
Congrats, you’ve unlocked and rooted your Nexus!
Now at this point CWM recovery may or may not still be present on your device. There have been mixed reports on whether it will ‘stick’ the first time you flash it. The stock ROM has a check file that will replace CWM with the stock recovery upon reboot. To determine if CWM is still present simply reboot into recovery and see if it is there. Type:
adb reboot recovery
Obviously if you see the droid with exclamation point CWM did not stick. If you have no need for CWM, and simply wanted root you could stop now. Wait a few minutes and your device will reboot on its own and you are all done.
However, if you desire CWM then proceed on.
7. Rename recovery-from-boot.p to prevent stock recovery re-installation. Your Nexus should be booted normally at this point.
a. Go to the Play store and install ES File Explorer File Manager. Under settings enable ‘up to root’, ‘root explorer’, and ’mount file system’.
b. Navigate to /system and rename:
recovery-from-boot.p
to
recovery-from-boot.bak
by long pressing and selecting ‘rename’. Note: Be careful while navigating your device with these options enabled, a typo or slip-up could cripple your device and require a restore. I suggest once this rename is competed to disable the above options to avoid any mistakes in future exploring.
8. Flash CWM again.
a. Reboot into bootloader by typing:
adb reboot bootloader
b. once in bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
c. reboot device by typing:
fastboot reboot
d. verify CWM stuck by rebooting into recovery:
adb reboot recovery
And that should be it!
Some additional notes: CWM does make notice on rebooting with a message ”ROM may flash stock recovery on reboot. Fix? This can not be undone”. I don’t know what CWM will do there, so I prefer to rename the recovery-from-boot file so that I could easily restore it if I wanted. But perhaps that is what CWM does, although the message persists even after I renamed the file. Maybe someone could clarify this.
Hope this helps some people out in enjoying this great device even more, thanks for reading.
4.1.2 and 4.2.1 updates...
Thought I would revisit the thread as we've had two updates since I wrote the above. I installed 4.1.2 OTA with no problems but as expected, I lost root and CWM.
Because I'm lazy, I didn't worry over it much and then 4.2.1 shows up and also installed perfectly. Finally got around to getting root back and here are the steps I used.
Notes:
* Need to make sure drivers are correctly installed. See first post.
* I never really used CWM so I elected not to permanently install it this time.
* This update is a brief synopsis of how I got root back. If the steps are not clear, review the first post as the procedure is very similar.
1.) Ensure USB debugging is still enabled. On 4.2.1 "Developers options" are hidden by default. To enable simply tap "Settings > About tablet > Build number" 7 times. Back out and "Developers options" should now be available. In my case USB debugging was still enabled.
2.) Download SuperSU v0.99 and CWM 6.0.1.9 from links in first post. I used non-touch version of CWM.
3.) Transfer SuperSU over to internal storage of your Nexus. Be sure you know where you dumped it.
4.) Reboot into bootloader: adb reboot bootloader
5.) Temporarily boot or permanently install CWM so we can install SuperSU zip.
for temp boot type: fastboot boot recovery-clockwork-6.0.1.9-grouper.img
for perm install type: fastboot flash recovery recovery-clockwork-6.0.1.9-grouper.img
6.) Once in CWM select:
a. install zip from sdcard
b. choose zip from sdcard
c. navigate to /0/ then wherever you put SuperSU
7.) Once finished back out and reboot system now. I selected "No" on allowing CWM to disable stock recovery. If you are only temp booting CWM then this likely won't matter either choice you make. If you perm flashed CWM then you may wish to choose 'Yes".
That should cover it. Thanks for reading, any questions or corrections be sure to let me know.
I have a question about this:
I rooted and installed CWM on my 4.2 N7, but now, then I try to install the 4.2.1 OTA update, I get this error:
Code:
assert failed: apply_patch_check("/system/lib/libweb rtc_audio_preprocessing.so", "bin_number", "big_number""),
E: error in /cache/jop40d-from-jop40c.zip
(Status 7)
It's wise to apply this if I already have a rooted+CWM N7?
Some root procedures, or third party apps like Titanium Pro can make changes to certain system files that will cause an official update to fail. In your case, it appears at least "rtc_audio_preprocessing.so" located in "/system/lib/libweb" has been altered.
The easiest solution is to flash the current factory image then root. You can find them here: https://developers.google.com/android/nexus/images#nakasi.
However, you will lose your data. So back up accordingly.
If that's not an option, you can try:
a.) figure out which app you have that caused the change, and see if it has a 'revert' option or if uninstalling will put the file(s) back to stock.
b.) find the unmodified contents of /system/app and /system/lib and replace yours. Needs to be from 4.2 in your case.
c.) find a modified manual update patch (either zip for CWM or .img for fastboot) that has been altered to ignore the integrity check.
Curious, just went looking for "rtc_audio_preprocessing.so" in a factory 4.2 system.img and can not locate it, or the lib/libweb directory. Perhaps a third party app made these additions and thus the integrity check is failing as the files are unknown/unaccounted for?
At any rate, I went ahead and sourced a 4.2 system.img and extracted the /app and /lib directories in case this helps you or anyone else searching along.
Extracted from: nakasi-jop40c-factory-6aabb391.tgz
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip.md5
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip.md5
so I factory-reseted my N7, but it didn't helped. I found the file /system/lib/libwebrtc_audio_preprocessing.so so I tried to replace it with the file you posted (thanks btw!), but while using a console (su, then cp file.so file.so.backup) I get the error saying it's a read-only system, so I can't replace that file
any other idea?
EDIT: So I was playing around with the N7 (although I can really remember, I think I formated /system ?):
So, yeah, I actually formated /system for some unknown reason and there is no OS to boot, so I'm downloading at 25 KBps (yes...I know) and I'll be installing the JOP40D version for the N7.
ah, so the file is actually:
/lib/libwebrtc_audio_preprocessing.so
not
/lib/libweb/rtc_audio_preprocessing.so
That makes a little more sense. On cp over the original file, as you discovered the /system partition needs to be remounted as writable before you would be able to make changes. You could easily accomplish this with one of the root file explorers from the market. I use "ES File Explorer" as its free. Then simply copy over your file.
Or if you prefer adb: mount -o remount rw /system
Regardless, you are starting over from scratch so no worries. One of the things I love about this device is the option to start fresh-from-factory with minimal fuss.
igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA
cub0ne said:
igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA
Click to expand...
Click to collapse
I am also on 4.2.1 unlocked and rooted with wugfresh toolkit. I downloaded CWM from the play store, the app can download the latest CWM recovery and flash it for you. That is what I did, All I have used CWM for is a nandroid backup, but have booted into recovery and wiped cache and fixed permission
Has anyone had issue is SuperSU and CWM running Fix Permissions in the CWM app? I get an error...
Thank you!
Thank you very much for the excellent guide, your explanations were very clear!
It was a lot of fun following it, and I am very happy for choosing this guide over the 'one-click' toolkits.
I'll give it a try
After trying a "all in one toolbox" to unlock and root I think I'll give this a shot. I got stuck at not being able to root and like your OP said, doing it manually would help with the learning curve.
Quick questions that has popped up is.
Do I lock my bootloader back to use your guide?
I've noticed drivers I have in device manager have different names. Does this mean there are dif drivers that do the same thing? Should i delete them and use the ones in the OP?
Late response, but I'll answer for future users following this thread...
Once your bootloader is unlocked by any means, no need to relock in order to follow this guide. We simply have to have it unlocked so we can gain root
Drivers are probably the most common issues people have in any instance of trying to interact with their device. While its not imperative that the names are the same, what is most important is that you can communicate with the device. There really isn't the right or wrong driver name, just that the driver works! Having said that, if you are wondering whether you have the correct drivers installed, simply follow the steps and attempt a "adb devices" or "fastboot devices" command depending on your device status as is outlined in the tutorial. If you do not have the appropriate response, then you need to stop and determine the issue.
Update after OTA 4.2.2
Lost root as expected, and followed procedure in post #2 to gain root back. Also updated OP file versions to current as of this post as they all worked successfully.
Only thing I would note: If you get a "offline" notice after trying 'adb devices', be sure to check your nexus for a notification to allow the connected computer access for USB debugging. If you don't see one, go to "Settings -> Developer options" and disable/enable USB debugging and it should pop up. I don't remember this behavior when I first wrote the tutorial, so it may be something new for 4.2.2. After reboot it will require approval again, so you may wish to select 'remember this computer'. I added this note in the OP as well in the appropriate step.
It's a bit urgent to get solved, I'm at college, and that's the only way to talk with my parents, being 1 or 2 days without answering them would be a problem, since they will start to get worried.
Phone: Motorola Moto G 2014, XT1063
Using Team Win Recovery Project v2.8.0.1
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
DIdn't understand why, but it f**ed up.
Basically I cleaned everything, and in an act of desperation I also lost my sdcard, I've been trying to install the ROM through sideload, but it's not working, I get the error *failed to write data protocol fault no status*, and the phone keeps rebooting, and stuck in the "WARNING BOOTLOADER UNLOCKED"
I appreciate any kind of help, as I said, it's really important to solve this ASAP.
Thanks in advance!
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
gouzzz said:
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
Click to expand...
Click to collapse
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.
Doppel u r right. follow doppel steps.
doppelhelix said:
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.
Click to expand...
Click to collapse
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.
gouzzz said:
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.
Click to expand...
Click to collapse
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
gouzzz said:
EDIT: Now it doesn't charge, or something. I connected it to charge, but it keeps appearing 0% for more than 30 minutes, I can't even access the menu from "Volume Down + Power On"
Click to expand...
Click to collapse
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.
doppelhelix said:
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.
Click to expand...
Click to collapse
On the MOUNT and UNMOUNT processing I don't see anything on my PC, I don't even know how to unmount it. It only appears Enable MTP and disable.
How am I supposed to load the ROMS?
Tried with sideload but got an errror : "Error executing updater binary in zip .."
Seems like the drivers aren't working properly, I have Windows 8.1, on the site it doesn't talk about it, this might be the problem? Cause I instaled motorola device manager, I scan for drivers but it doens't find anything, and the phone apperas with the yellow triangle on the Device Manager.
----------------------------------------------------------------------------
----------------------------------------------------------------------------
EDIT: I managed to boot the Titan 5.0.2, but now it's stuck in the 4 balls moving around, i waited for about 1hour.
hello xda people,i thought i might share this with you since i've tested and done it myself about rooting kitkat eu update.My bootloader was factory locked and proceeded unlocking it and i barely managed to install Hazou's unoficial twrp recovery(see this thread:http://forum.xda-developers.com/showthread.php?t=2278483) wich was done via fastboot,but mostly even after the custom recovery install i didn't managed to get root on kitkat,so i've tried ChainsDD superSU update pack witch seems to resolve the problem because the update package installs the propper package according to system specs,so if anyone there wishing to root or doesn't quite figure out,here's an simple how to:
1Make sure you have all the drivers installed.
2install or download android sdk
3 from the sdk,copy on your desktop platform-tools (for easier job)
4 download recovery image from Hazou thread,see: http://forum.xda-developers.com/showthread.php?t=2278483 extract and place it on platform-tools folder you copied on your desktop
5in platform-tools folder open cmd line and enter your phone in fastboot
6type "fastboot devices" without quotes
7 if your device is listed,type: fastboot flash recovery recovery.img
8now after cmd confirms if the flash was succesfull, either head to recovery from fastboot mode and see if twrp is installed,if it does keep your phone connected to pc
9 download chainsDD superSU update to external sd,link to download https://drive.google.com/file/d/0B8m4rdNFVU4_YjV4X2gtUjNhZVE/view?usp=sharing
10 install via twrp,wipe davik+cache, reboot and enjoy
You can get the latest CWM / TWRP / MobileODIN installable ZIP from here. It has x86 support and works on the Razr i.
drunk_ryder24 said:
hello xda people,i thought i might share this with you since i've tested and done it myself about rooting kitkat eu update.My bootloader was factory locked and proceeded unlocking it and i barely managed to install Hazou's unoficial twrp recovery(see this thread:http://forum.xda-developers.com/showthread.php?t=2278483) wich was done via fastboot,but mostly even after the custom recovery install i didn't managed to get root on kitkat,so i've tried ChainsDD superSU update pack witch seems to resolve the problem because the update package installs the propper package according to system specs,so if anyone there wishing to root or doesn't quite figure out,here's an simple how to:
1Make sure you have all the drivers installed.
2install or download android sdk
3 from the sdk,copy on your desktop platform-tools (for easier job)
4 download recovery image from Hazou thread,see: http://forum.xda-developers.com/showthread.php?t=2278483 extract and place it on platform-tools folder you copied on your desktop
5in platform-tools folder open cmd line and enter your phone in fastboot
6type "fastboot devices" without quotes
7 if your device is listed,type: fastboot flash recovery recovery.img
8now after cmd confirms if the flash was succesfull, either head to recovery from fastboot mode and see if twrp is installed,if it does keep your phone connected to pc
9 download chainsDD superSU update to external sd,link to download https://drive.google.com/file/d/0B8m4rdNFVU4_YjV4X2gtUjNhZVE/view?usp=sharing
10 install via twrp,wipe davik+cache, reboot and enjoy
Click to expand...
Click to collapse
I like this method, you're always left with a fallback or the option to the Rom flash again or use an alternate when using recovery, I've started to prefer TWRP over clockwork recently
Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks
Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!
Yeah that sorted it thanks a lot
Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,
jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!
Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it
@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.
The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
Mega
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx
MariosFFX said:
The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
https://mega.nz/#!zJhFCKRa!7FDyDKkqEL3bgz-lYBMf_Lj0RoMyzubg9tiZC3z9ttg
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx
Click to expand...
Click to collapse
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.
bluegrass55 said:
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.
Click to expand...
Click to collapse
check again, the link is with decryption key.
I have double checked and made sure it was with the key.
I've tried again on Chrome,IE and Firefox but still get Decrypt message.
Do you copy and paste the link or you click on it?
Seems to me you copy and paste it.
Because the link is way too big, xda forums shorten it (notice the dots).
Click the link don't copy and paste iit
Finally managed to download it.
I clicked on the link in Chrome & it worked. Firefox didn't like it.
Thanks for the help.
fastboot claims to work, but doesn't
Code:
[email protected] ~/Downloads> fastboot -i 0x2b4c flash recovery twrp.img
target reported max download size of 1610612736 bytes
sending 'recovery' (18372 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.145s]
finished. total time: 0.670s
[email protected] ~/Downloads> fastboot -i 0x2b4c reboot
rebooting...
finished. total time: 0.071s
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.
Philo.Phineas said:
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.
Click to expand...
Click to collapse
I am having problems with this Chinese twrp why not get fixed in the bootloader nor accept after even running without installing the program supersu via twrp
Hello All,
So originally I had TWRP 3.0 on my Z2 pro, and i attempted to just install the 3.1 img file from it(per another instructional video from the 7.1 mokee thread), and after installing the recovery file, my phone restarted, however now when I attempt to go into Recovery mode from the boot menu, my phone just goes to a blank screen.
I've tried to flash the image from CMD to see if i could essentially "re flash" 3.1 TWRP, but I always get this message(see attached image). What am i typing in wrong in CMD? As you can see, the directory name is right, as well as the fastboot code. I'm also IN fastboot mode on my phone already. I changed the file name of the folder containing the recovery from it's orginal name to make it shorter, but that should not matter at all. It seems as if CMD can't find the folder though?
Well XDA won't let me post a damn picture(how am i supposed to ask for help if i can't show people what im doing), so I guess if someone would PM me i can post the image.
People do you try to flash the recoveries right after unlocking your bootloader?
Because if you can't flash the recovery and it goes back to stock, it means you haven't fully unloxked your bootloader.
Make sure you run the last following command when you unlock your bootloader
Code:
fastboot -i 0x2b4c oem unlock-go
Then follow my guide here.
Also bootloader unlock tutorial here:
https://zukfans.eu/community/threads/zuk-z2--unlock.62/
Its for Zuk Z2, but the instructions are also for Z2 Pro.
MariosFFX said:
rl].
Click to expand...
Click to collapse
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.
which files about phone mobile data at a TWRP BACKUP ? i see a lot of files inside of a twrp backup . i need to learn that . thanks.
jsto69 said:
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.
Click to expand...
Click to collapse
Use directory names without spaces. Like c:\zuk and perform all operations from there.
Hello, this works fine very thx, but you have recent/new mix version?