Database Users

How To: Unlock bootloader and Root using a Mac

This process is very similar to how its done on Windows but I thought I would go ahead and post it here for those who have never rooted or used terminal before. I know the first time I rooted an Android device I was very happy to have a Mac specific guide to follow . Many of you may think this is simplified too much but, like I said, I created this with first time rooters in mind. If a Mod would like to sticky it thats fine. Also, I've tried to be very careful and thorough with the instructions, but if anyone notices a problem please let me know.
As always, I am not responsible if something goes wrong and your device gets bricked. I will try to be as specific as possible and this process worked for me. Also, I don't claim to have the knowledge to fix any problems you may encounter along the way. There are a lot of very talented people here who have extensive knowledge of Android, but I am not one of them. I can unlock my bootloader and root my device but that's about it. So if you do encounter a problem I will try to help but there is no guarantee I can fix the issue (in fact the odds are that I can't fix the issue). Proceed with caution!
Important: Unlocking your bootloader will wipe your device! Please backup anything that is important (pics, vids, documents, etc)!
This guide only applies to the 2013 Nexus 7
A. Prep
1. Charge the Nexus 7 to at least 80% so it doesn't turn off during the process
2. Unlock developer options by navigating to -- settings > about tablet -- and then click the build number 7 times
3. Enable USB Debugging by navigating to -- settings > developer options -- and select the USB Debugging box
4. Download the Android SDK for Mac here and unzip it once it has downloaded. DO NOT use the link posted below for the sdk. It does not contain fastboot and you will not be able to complete the rooting process. Please use the full sdk from Google that I have linked here. EDIT: Google has changed the download for the SDK. Please see posts 73-75 on page 8 for instructions regarding how to get everything you will need for the SDK.
5. Download the latest TWRP for your device here and place it in the platform-tools folder of the SDK. Make sure the TWRP file you download is for the 2013 Nexus 7...not the 2012 version. To find the platform-tools folder -- open the adt-bundle-mac folder you downloaded and unzipped > sdk > platform-tools -- place the TWRP file here. Other files in the platform-tools folder should include adb, api, fastboot, notice.txt, and a few others.
B. Unlock the Bootloader - Warning--This will wipe your device! Backup anything important!
1. With your device powered on, plug it into your Mac
2. Open up terminal and navigate to the platform-tools folder which has the adb, fastboot, and TWRP files. An easy way to do this is to type "cd" (without the quotes) into terminal, add a single space, and then drag and drop the platform-tools folder onto terminal and then press enter.
3. Type this command into terminal: ./adb reboot bootloader
4. If you correctly navigated to the platform-tools folder, you should get an error message saying the device is unauthorized. Go to the Nexus 7 and there should be a dialogue box asking you to authorize the computer. Authorize the computer.
5. Re-type the command: ./adb reboot bootloader
6. Your device should now boot into fastboot mode. On your N7, the word "start" will be at the top in green and you can also see a lot of your device information on this screen
7. Type into terminal: ./fastboot oem unlock
8. Your Nexus 7 will now display a message about unlocking your device. Use the volume button to select the option to unlock the device and then press the power button to confirm the choice.
9. Your device will return to the fastboot mode screen and you can now see in the device information section near the bottom that the device is unlocked. While on this screen, press the power button to select the green "start", which will reboot your device. You must restart your device here or you will run into a softbrick issue during the root process!
10. Congrats! Your device is now unlocked. If you want to root proceed to the next section.
C. Rooting
1. Once your device has rebooted from the unlocking process, everything will have been wiped and reset. You will have to go back and unlock developer options again and you will also have to enable USB debugging again, which can be found part A. Prep of this guide.
2. Download the current version of SuperSU to your Nexus 7. It will go to the download folder on your N7. It can be found here. (Note: The version of SuperSU I have linked to is 1.93, but it gets updated from time to time. You might want to look around and see if a more current version is available. The thread for SuperSU can be found here.)
3. Turn your N7 off and then boot into fastboot mode by pressing the Volume Down button while also pressing the Power Button to turn the device on. If done correctly you should see the green "start" again at the top and the device information near the bottom.
4. Plug the N7 into the computer and make sure terminal is still directed to your platform-tools folder. For instructions on how to navigate to the platform-tools folder see part B. Unlock the bootloader.
5. Type the following into terminal: ./fastboot flash recovery nameofTWRPrecovery.img
5a. For the nameofTWRPrecovery.img part above, you must type the exact file name of whatever TWRP (or other) recovery you've decided to use. This is the same file that you downloaded and placed in the platform-tools folder in Part A. Step 5. above. For me the file name I had to type was openrecovery-twrp-2.6.0.0-flo.img and the total command looked like this: ./fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
6. In terminal you should see the process taking place and it will tell you when its finished and how long it took (less than a second).
7. Now, while still in fastboot mode, use the volume button to navigate to Recovery and press the power button.
8. The N7 will boot into TWRP which we just installed.
9. Using the touch screen, select install and then navigate to the download folder where you saved the SuperSU file
10. Select the SuperSU file using the touchscreen and then swipe to flash it. You will see the rooting process occur on the screen.
11. Congrats! You are now rooted. Select Reboot System and you are done!

Your instructions couldn't be any simpler. I am unlocked and rooted now. This is my first Android device. Thank you very much.

Glad it was helpful for you!

Is there any step involved to install drivers here which I saw mentioned while using Windows system?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Very nice guide! Well done
Sent from my Nexus 7 2013 using xda app-developers App

redhat_123 said:
Is there any step involved to install drivers here which I saw mentioned while using Windows system?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
No, you don't need any drivers for the Mac (which makes it simpler than the Windows process in my opinion). I've included links in the how-to for everything you will need .

geckocavemen said:
No, you don't need any drivers for the Mac (which makes it simpler than the Windows process in my opinion). I've included links in the how-to for everything you will need .
Click to expand...
Click to collapse
Thanks a lot. This is the first time I used MAC to unlock and root a device and it was very quick. Appreciate your effort in putting up the detailed steps.

I just saw this post so I figured I may as well chime in. I've been rooting devices and using adb for years, so the issues wasn't a lack of experience.
I was having an issues with my device being reported as 'Offline'. Despite downloading the SDK several times I was unable to get the latest version.
I posted a thread last week with the updated version of adb needed for OS X in case anyone runs into this same issues that I did: http://forum.xda-developers.com/showthread.php?t=2390999

wad3g said:
I just saw this post so I figured I may as well chime in. I've been rooting devices and using adb for years, so the issues wasn't a lack of experience.
I was having an issues with my device being reported as 'Offline'. Despite downloading the SDK several times I was unable to get the latest version.
I posted a thread last week with the updated version of adb needed for OS X in case anyone runs into this same issues that I did: http://forum.xda-developers.com/showthread.php?t=2390999
Click to expand...
Click to collapse
Hi wad3g, was the problem you ran into related to the link for the Mac sdk I posted in the guide? If it was with my link I'd like to fix it so others don't have the same issue. Thanks!
EDITED TO ADD: Please only use the link in the how-to for the full sdk from Google. wad3g's link only has adb but not fastboot. To complete the rooting process you will need fastboot also.

geckocavemen said:
Hi wad3g, was the problem you ran into related to the link for the Mac sdk I posted in the guide? If it was with my link I'd like to fix it so others don't have the same issue. Thanks!
Click to expand...
Click to collapse
Yes, it is from the same link as above on Google's developer site. They hadn't updated the SDK yet, so each time I downloaded ADB v1.0.29 - ADB for 4.2. I was finally able to find ADB & Fastboot v1.0.31 for Android 4.3. Also, just so you know, the .zip on my thread is not the full SDK. If you're not a developer you don't need the full SDK, so for most the rooter's here my zip will be all that is needed.
You may just want to mention checking what version of ADB you're running prior to start or if you're having any issues. If you're running an older version than 1.0.31 you need to update.
{
"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"
}
Hope this helps! Let me know if you have any other questions.

Thanks wad3g. But just to clarify, Google updated the Mac version of the sdk on the 29th of July so the link in the original how-to will work for any version of Android. It's the same thing I used to download the sdk and I'm running version 1.0.31. Also, as mentioned it does contain more than is strictly necessary for unlocking and rooting. However, the original link in the how-to will provide you with the most up-to-date version of the Mac sdk that Google has released, should they update it in the future.

Please Help!!!
Hi I followed all your instructions and right when i was ready and tried to flash the recovery, I get this list of options after waiting for device:
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
format <partition> format 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 (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-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. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
I don't understand what I should pick or if I should pick any. Please help as soon as possible.
EDIT: The reason I got this list is because I dragged in the fastboot into the terminal because when I tried to enter ./fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img, it said this: -bash: fastboot: command not found

Don't worry you haven't broken anything. What you saw is basically just a message that says you entered an incorrect command and then it presents a list of acceptable commands. Just start the section C. Rooting over again and don't move the recovery file into the command window...just type the full name of the recovery file instead.
EDIT...I think I didn't understand your edit properly the first time. I think you got the bash message because terminal was no longer pointed at the platform-tools folder. To do the rooting process you must make sure terminal is still directed at platform-tools folder. It should still be if you didn't close terminal or do anything else in terminal after the unlocking process. However, if terminal is not directed to the platform-tools folder you can use the "cd" command found in part B. of the how-to to get terminal pointed to the right place again. Once you've done that you can just start Part C. again and all should be fine. When I rooted I just left terminal open after completing the unlocking process and it was still directed at platform-tools. If you closed terminal it wouldn't be pointed at the right location where fastboot is.
One other thing: Are you sure there is a fastboot file in your platform-tools folder? It should look just like the adb file except it will be named fastboot instead.
LAST EDIT PLEASE READ: I'm assuming you used wad3g's download because I just checked and it does not have a fastboot file in it and that is why you got the -bash message. Please use the link in the how-to to download the full sdk from google. Pull out the fastboot file from Google's sdk and put it wherever you put your adb file that you got from wad3g. At that point you will be able to continue with Part C. Rooting.

Hope that last edit of mine helped out. Just follow the how-to step by step (including my links) and you'll be ok.

Thanks So Much But One Last Question
geckocavemen said:
Don't worry you haven't broken anything. What you saw is basically just a message that says you entered an incorrect command and then it presents a list of acceptable commands. Just start the section C. Rooting over again and don't move the recovery file into the command window...just type the full name of the recovery file instead.
EDIT...I think I didn't understand your edit properly the first time. I think you got the bash message because terminal was no longer pointed at the platform-tools folder. To do the rooting process you must make sure terminal is still directed at platform-tools folder. It should still be if you didn't close terminal or do anything else in terminal after the unlocking process. However, if terminal is not directed to the platform-tools folder you can use the "cd" command found in part B. of the how-to to get terminal pointed to the right place again. Once you've done that you can just start Part C. again and all should be fine. When I rooted I just left terminal open after completing the unlocking process and it was still directed at platform-tools. If you closed terminal it wouldn't be pointed at the right location where fastboot is.
One other thing: Are you sure there is a fastboot file in your platform-tools folder? It should look just like the adb file except it will be named fastboot instead.
LAST EDIT PLEASE READ: I'm assuming you used wad3g's download because I just checked and it does not have a fastboot file in it and that is why you got the -bash message. Please use the link in the how-to to download the full sdk from google. Pull out the fastboot file from Google's sdk and put it wherever you put your adb file that you got from wad3g. At that point you will be able to continue with Part C. Rooting.
Click to expand...
Click to collapse
Again in a bit of a sticky pickle. I got it to work because my problem was that I didn't direct the terminal to the folder. Now I am booted into TWRP but I don't understand what you mean by the SuperSu file. I it just the whole folder titled UPDATE-SUPERSU-v1.51?
EDIT: OMG IT WORKED!!! Thanks so much I got it rooted and it works awesome now!!!

Best tutorial for mac ever
I found this so helpful and easy! My nexus 7 is rooted now!:good:

:good::good::good::good:
thanks a lot

Thanks for the guide.

Want to say thanks for your very detailed explanations.
If I may, I would like to suggest one more step after the final step. Make a Nandroid backup. That really helps a lot for people who screwed stuff up.

Yes, creating a nandroid backup is very important and can definitely save you when flashing Roms and stuff if something goes wrong. Creating a nandroid before rooting could get you back to stock with an unlocked botloader too. But I guess that isn't as important now that Google has released the factory images.
Sent from my Nexus 7 using xda app-developers app

Guide for updating to 4.4 KitKat

Hello,
i have been reading guides all the day and no-one had a solutions to my problems so i would like to write my own to help out others who are encountering my same issues.
----------------------------------------------------------------------------------------
This guide is for Windows and explains everything you need to update your Nexus 7 (2013) Wifi (flo) from 4.3 JSS15R to 4.4 KRT16O
----------------------------------------------------------------------------------------
1) disconnect table from USB cables if it is connected to the pc
2) go http://developer.android.com/sdk/index.html and download the SDK
3) unzip the SDK in C\
4) go in C:\adt-bundle-windows and start the SDK Manager
let is load and scan for all possible updates.. when it has finished click on Deselect All then choose only these to packages:
Tools --> Android SDK Platform Tools
Extra --> Google USB Driver
if the Android SDK Platform tools are updated then you will only have 1 package to download else you will see Install 2 Packages, click it, then select Accept Licence and click Install.. wait it to finish and then close
5) let's now download the factory image
Nexus 7 2013 only WIFI (flo) "razor" is here: https://developers.google.com/android/nexus/images#razorkrt16o and download the first link of the page (4.4 (KRT16O) Link)
Nexus 7 2013 MOBILE/LTE (deb) "razorg" is here: https://developers.google.com/android/nexus/images#razorgkrt16o and download the first link of the page (4.4 (KRT16O) Link)
for some reason the MD5 checksum and SHA1 for the flo version dont match but i read people have been able to install this image anyway (i installed the OTA so i did'nt try this install)
unzip the downloaded file and you should get a .tar file.. unzip it again and you should get a bunch of files.. i got the following ones:
1)bootloader-flo-flo-03.14.img
2)flash-all.bat
3)flash-all.sh
4)flash-base.sh
5)image-razor-krt16o.zip
place all these files in C:\adt-bundle-windows\sdk\platform-tools\
6) now let's install the drivers correctly and flash the update
First thing, keep the Nexus 7 not connected to the USB cable. Then switch it on and go into Settings --> Storage click on the Options and choose USB computer connection and make sure to have the CAMERA (PTP) selected.
Now go into developer options and select Stay Awake and USB Debugging
Go back to the home screen and connect the tablet to the PC.. let the PC try to install it by himself.
Now press WINDOWS+R and run devmgmt.msc
If you see a device called Nexus 7 with a yellow sign then right click on it and choose Update software driver.
Then select the second option (find a driver on the computer), then select the second option (choose manually a driver from a list), now click first option (show all the devices), then click Driver disk button, then browse to C:\adt-bundle-windows\sdk\extras\google\usb_driver\ and choose android_winusb.inf and do ok.
The box should fill with a device called Android Composite ADB Interface, choose that and do next
To check if you have done right do:
WINDOWS+R and run cmd
in cmd do cd.. until you get into C:\
then do cd adt-(tab) to autocompile and enter
then do cd sdk enter
cd platform-tools enter
adb.exe devices enter
the daemon should start and you should get a list of devices attached showing you a code made of numbers and letters.. this is your nexus 7.
if cmd says the device is unauthorized then look at your tablet and allow the computer to operate
let's now install the driver also in fastboot so to do this always in cmd type
adb.exe reboot-bootloader
the tablet will reboot into the bootloader and you will see an android with the open tummy
now inside the command prompt window run the following commands:
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-krt16o.zip
if everything has gone right you should have updated using the factory image and the tablet should reboot by now...
else continue reading:
if you had any issues we can then try to update through OTA which means you will need to download another package
the nexus 7 ONLY WIFI OTA: http://android.clients.google.com/p....signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
not sure if the nexus 7 LTE OTA url has been released or not because i can't find it.. if anyone has the link and can point it out to me i would be glad to add it here
download it and place it always in
C:\adt-bundle-windows\sdk\platform-tools\
rename it to something easier and redo
adb.exe sideload ota_zipfilename (enter)
everything should go fine now, so it will reboot.. configure the tablet again if it is the case
7) changing recovery
download latest recovery from here http://techerrata.com/browse/twrp2/flo
place the download img into C:\adt-bundle-windows\sdk\platform-tools\
then reboot to bootloader using adb or simply switch the table on keep vol down down
in cmd type
fastboot.exe flash recovery recoveryimagefile
8) rooting the tablet
btw sideloading the zip for rooting requires a custom recovery such as TWRP so step 7 must be achieved in order to root this way
download the latest superSU from here http://download.chainfire.eu/supersu
go into recovery mode passing by the bootloader
do another adb sideload passing this time the zip for supersu
everything done hopefully
hope this helps others which had issues with drivers and had issues with the original factory image 4.4 (KRT16O) giving the E: signature verification failed

Great guide!
The package for the link https://developers.google.com/android/nexus/images#razorkrt16o fails verification for me as well and does not install once its side loaded. So it's probably beneficial to just point to the other link.:good:

haet said:
Great guide!
The package for the link https://developers.google.com/android/nexus/images#razorkrt16o fails verification for me as well and does not install once its side loaded. So it's probably beneficial to just point to the other link.:good:
Click to expand...
Click to collapse
The factory image isn't meant to be side loaded. It needs to be installed using fastboot/bootloader.

If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.

cincibluer6 said:
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
Click to expand...
Click to collapse
Gotcha.
There is quite a size difference between the the zip and the tgz format. Is this only because of compression format? Or is it more beneficial to flash one over the other?

cincibluer6 said:
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
Click to expand...
Click to collapse
There are zips and then there are ZIPS
It isn't the type of archive that is critical but the contents of the zip. Zip is just a generic archive format and can store anything.
The OTA zips include specific content. In particular they are
signed by google
include an install script to handle patching, replacing files, and setting up permissions
include an install utility to run the script
include individual patch files
include whole files if the patches would be too large
have a specific directory structure where everything is supposed to be located
The factory images are also delivered in an archive. They are first archived in a tar format, which just collects a bunch of files and doesn't compress. Then they are gzip'd which is a Gnu archiver which performs a similar job to zip, but uses a different format and algorithm. Within the original tar archive there is also a zip archive. That zip contains images of the kernel, recovery, rom, user and data partitions, but it doesn't include the aforementioned items that make a zip into an OTA-style zip.
The factory images are NOT meant to be flashed in recovery. Recovery will be expecting the stuff above that OTA-style zips have. If you try to flash the factory image, the first point of failure is the signature verification fails, because it isn't signed (and even if it were signed, it wouldn't be signed in the way recovery is expecting)
So what is the difference between flashing via Recovery and the OTA-style zip vs running flash-all and the factory image?
The OTA-style flash will go and examine each file it needs to patch to make sure it is stock JSS15R. It must do this because it doesn't have the complete KRT16O file, only a patch (difference between the JSS15R and KRT16O versions of the file) that only makes sense if applied to the original JSS15R file. Even if there is a one space difference in the file, the patch would fail.
Since the OTA-style patches files (in general) it will leave files you have added in place. In particular the files installed to keep root are left in place and so are apps, sounds, images, etc. you added to the ROM (/system) partition. So you ask why do you lose root? You don't lose the root files that were installed, they are neutered because at the end of the OTA-style install, it resets the permissions in all the directories to what they are supposed to be. This drops the special permissions you gave the root files to do their job. Also the OTA-style patch does not directly overwrite your recovery. Upon first boot, there is a script that runs which builds the new recovery using the installed kernel. This is why if you immediately (prior to reboot) run the SuperSU install script after the installation of the OTA-style update.zip, you can restore root and keep your recovery. The SuperSU install script replaces the script that builds the new recovery, with its own file. It also reinstalls and sets the permissions on the root files. So in effect, you have root and have prevented stock recovery from being installed over your custom recovery.
The Recovery that you use to run the OTA-style update.zip is just special program that boots up on the linux kernel and accepts certain actions. The source code for Recovery along with the kernel is published. People can easily replace Recovery with their own custom program and that is why you have custom recoveries.
The factory images on the other hand install through the bootloader. This is a low-level program similar to BIOS on PCs. It has more limited functions and the code is proprietary. It is harder to do custom bootloaders because the source code isn't published.
The bootloader has a more limited set of functionality and you communicate with bootloader using a different program called fastboot.
The bootloader expects the files you give it to be .img files or you can give it a zip archive full of .img files. These are not patches of files like the OTA. These are complete images to replace the existing partitions. It is like a Norton Ghost image (factory image style) of your entire hard drive vs an incremental backup (OTA-style) of just the files that changed.
Given they are full images, they will overwrite the partitions completely so anything you had on them before is wiped out and overwritten.
Also full images are always larger than OTA patch-style updates because they contain everything rather than just the changed file patches.
By default they use the -w option in the fastboot install instructions, which will wipe your user data as well, but you can remove the -w option and keep your user data, though there are always a small percentage of upgrades where it won't work to keep your user data (same with the OTA).
Anyway that is just a brief summary. There are many more details and nuances I didn't list.

^^ I won't go ahead and quote you but thanks for the full on summary. I knew what .tgz was and all that (using Linux for a few years now) but I'm new to most of the Android like stuff.
Thanks for clarifying and explaining it so well.

Just gave the sideload of SuperSU a shot and was given two errors:
failed to verify whole-file signature
signature verification failed

haet said:
Just gave the sideload of SuperSU a shot and was given two errors:
failed to verify whole-file signature
signature verification failed
Click to expand...
Click to collapse
You cannot sideload the SuperSU update.zip using stock recovery because it isn't signed by Asus/Google.
It is signed, but using a generic cert.
You need to use custom recovery like TWRP or CWM to install it. You can use their menu system to choose the file or if they have sideload, you can sideload using custom recovery.

sfhub said:
You cannot sideload the SuperSU update.zip using stock recovery because it isn't signed by Asus/Google.
It is signed, but using a generic cert.
You need to use custom recovery like TWRP or CWM to install it. You can use their menu system to choose the file or if they have sideload, you can sideload using custom recovery.
Click to expand...
Click to collapse
Makes sense. Thanks for the help!

Windows 2008 server usb drivers?
This guide was great, and everything worked fine until I reboot into recovery and choose to adb sideload an image. Then, the device doesn't get recognized, and the google drivers don't work. So, I can't see the device with the ADB interface driver.
Does any have experience with this? Am I out of luck? I couldn't find anyone talking about drivers for windows server 2008 anywhere -- but usually win7 drivers work fine -- just not here.
I don't have another windows installation anywhere, so if there isn't an answer, I will just have to wait for OTA
** UPDATE **
I found some universal drivers from Koushik Dutta: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked! Then I used the OTA download (your second option), sideloaded it, and got the update. Now running KitKat, so thanks a bunch! hopefully someone else will find this driver option useful.

I'll give those universal drivers a go. Hell, I've tried everything else on the Internet with complete failure. One last try before I give up.
Sent from my SM-P600 using XDA Premium HD app

jbwray said:
This guide was great, and everything worked fine until I reboot into recovery and choose to adb sideload an image. Then, the device doesn't get recognized, and the google drivers don't work. So, I can't see the device with the ADB interface driver.
Does any have experience with this? Am I out of luck? I couldn't find anyone talking about drivers for windows server 2008 anywhere -- but usually win7 drivers work fine -- just not here.
I don't have another windows installation anywhere, so if there isn't an answer, I will just have to wait for OTA
** UPDATE **
I found some universal drivers from Koushik Dutta: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked! Then I used the OTA download (your second option), sideloaded it, and got the update. Now running KitKat, so thanks a bunch! hopefully someone else will find this driver option useful.
Click to expand...
Click to collapse
You sir are a genius (and the driver author). I had the exact problem and looked everywhere. I am low tech, too. So following these two guides;
http://phandroid.com/2013/11/13/how-to-install-kitkat-nexus-7/
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I am now on 4.4. And everything is intact. Thank you!

I also ran into Google USB driver problems after the Nexus dropped into recovery mode. So I gave up trying to use Windows 8 and switched over to using Ubuntu workstation. Getting ADB to run on Ubuntu is very easy and so flashing the Kit Kat OTA file was a breeze.
On Ubuntu there's no need to install the full SDK just to get ADB and Fastboot; the process is outlined here: http://forum.xda-developers.com/showthread.php?t=1860108. From there it's just simple command line entries from a terminal i.e. "adb devices."
I was disappointed to see Google has kept the black top and bottom bars for tablets. I usually run Teslacoil's launcher and installed their beta launcher with transparent bars a welcome relief.

doorunrun said:
I also ran into Google USB driver problems after the Nexus dropped into recovery mode. So I gave up trying to use Windows 8 and switched over to using Ubuntu workstation. Getting ADB to run on Ubuntu is very easy and so flashing the Kit Kat OTA file was a breeze.
On Ubuntu there's no need to install the full SDK just to get ADB and Fastboot; the process is outlined here: http://forum.xda-developers.com/showthread.php?t=1860108. From there it's just simple command line entries from a terminal i.e. "adb devices."
I was disappointed to see Google has kept the black top and bottom bars for tablets. I usually run Teslacoil's launcher and installed their beta launcher with transparent bars a welcome relief.
Click to expand...
Click to collapse
If you install the latest Google search apk and GEL from the nexus 5, you will have transparent nav bar.
{
"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"
}
Sent from my Nexus 7 using Tapatalk 4

Hi. This will wipe the device right? We should have a backup before proceeding?

ganstar said:
You sir are a genius (and the driver author). I had the exact problem and looked everywhere. I am low tech, too. So following these two guides;
http://phandroid.com/2013/11/13/how-to-install-kitkat-nexus-7/
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I am now on 4.4. And everything is intact. Thank you!
Click to expand...
Click to collapse
You should also know that Google has drivers as well located at http://developer.android.com/sdk/win-usb.html, which is what you would have downloaded right after you installed the SDK package.

For those who can't get their devices recognised even after doing everything correctly. Just boot the tablet and change from MTP to PTP. Worked for me.
Sent from my Nexus 7 (2013)

I was on PTP. still didn't work
BreakShadow said:
For those who can't get their devices recognised even after doing everything correctly. Just boot the tablet and change from MTP to PTP. Worked for me.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I was on PTP. Still didn't work until I found those drivers. The drivers from Google were what I was using, but they didn't support the device in fastboot mode for the version of windows I was using. (2008 server R2)

haet said:
You should also know that Google has drivers as well located at http://developer.android.com/sdk/win-usb.html, which is what you would have downloaded right after you installed the SDK package.
Click to expand...
Click to collapse
I had those, they didn't work for me, as others have noted as well.

[GUIDE] OnePlus One - How to Unlock Bootloader, Install Custom Recovery and Root

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Setup, Preparation and Prerequisites
I know there are already a few root guides out there for this phone, but I found that they weren't very detailed. This guide is thorough and explains each and every step in a noob-proof manner.
Basic tasks that I may refer to throughout this guide:
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
Enter fastboot mode- Turn the phone off. Hold volume up + power until the "fastboot" screen appears.
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here
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.
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long (5-15 minutes), but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Driver Installation - Download and install the Universal ADB Driver. Alternatively, use this method.
Downloads
Download a custom recovery and the SuperSU zip below. Place both files (recovery image and root zip) in the platform-tools folder located on your desktop within the android-sdk-windows folder.
Custom Recovery:
TeamWin Recovery Project (TWRP)
Root:
SuperSU
Information
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in my opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has.
If you are confused by anything in this guide, I would highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also I'd suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understand? Good...lets begin:
1. Unlocking Bootloader
Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window 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
After the above command has finished excuting, run the following
Code:
fastboot reboot
The phone will reboot. Wait until the phone has fully booted up into android, then adjust the following settings on the phone:
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Disable CM Recovery Protection - On your phone go to Settings > Developer options. Then disable the 'Update recovery with system updates' option.
Close the command prompt window and proceed onto the next section of the guide.
2. Installing a Custom Recovery
Turn the phone off. Then boot it into fastboot mode by holding volume up + 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 this file should be placed in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open a new command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
Once the flash has completed type the following command to reboot the phone:
Code:
fastboot reboot
After the phone has booted back up, turn it off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode. Now that you have a custom recovery, you may continue to the final step.
Close the command prompt window.
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into recovery mode by holding volume down + power. Leave the phone at the main screen of the custom recovery for now.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Instructions for ClockworkMod (CWM):
install zip from sdcard > choose zip from sdcard.
Next, browse to the location where you previously copied the SuperSU zip and select the it.
To confirm the installation, scroll down to "Yes" and select it. The installation shouldn't take very long, and once it has completed you may reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the ONE Android Development and ONE Original Android Development section) onto the phone (remember the location of where you copy it to)
Turn the phone off then boot into recovery mode by holding volume down + power. To install a custom ROM the general procedure to follow is: factory reset, wipe cache + dalvik cache, flash ROM, flash GApps. Here are the recovery specific instructions:
Instructions for TeamWin Recovery Project (TWRP):
Wipe > Swipe to Factory Reset
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Instructions for ClockworkMod (CWM):
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
install zip from sdcard > choose zip from sdcard > navigate to the location of the ROM > select the ROM > confirm the installation by selecting "Yes"
After that you may install the GApps using the same method for flashing the ROM, and finally reboot the phone.
Keep in mind that the first boot after installing a custom ROM & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted. Enjoy

Reserved.

Thanks Dude For making this Helpful... Sure it will help us with our one plus one..........

Nice guide!!
Sent from Mallorca to your face

Great guide! Will definitely follow when my OPO arrives! :victory:

Thanks a lot for the thread sir ! Btw have some problems I m running and old XP and seems the commands don't work for me .. Would you show me a pics of your root folder on your desktop for the sdk please ?
And I have kies installed before .. Maybe drivers aren't working together ?

pro castinato said:
Thanks a lot for the thread sir ! Btw have some problems I m running and old XP and seems the commands don't work for me .. Would you show me a pics of your root folder on your desktop for the sdk please ?
And I have kies installed before .. Maybe drivers aren't working together ?
Click to expand...
Click to collapse
What do you mean the commands don't work? Could you explain if you are getting an error, what the error is, etc.

Chromium said:
What do you mean the commands don't work? Could you explain if you are getting an error, what the error is, etc.
Click to expand...
Click to collapse
Hum , so I will try to translate my commands from French lol
First I try to install 15 seconds adb installer and failed . Told me all files already copied and "stex" is missing .
After I install the sdk as you said , I put the folder on my desktop and try to get adb worked with the test entry . But my command said that there is a invalid way

pro castinato said:
Hum , so I will try to translate my commands from French lol
First I try to install 15 seconds adb installer and failed . Told me all files already copied and "stex" is missing .
After I install the sdk as you said , I put the folder on my desktop and try to get adb worked with the test entry . But my command said that there is a invalid way
Click to expand...
Click to collapse
Could you post a screenshot of the command prompt output? Thanks.

Chromium said:
Could you post a screenshot of the command prompt output? Thanks.
Click to expand...
Click to collapse
Yeah of course man , let me an hour I will show you all with pics . Thanks a lot again for helping us and for the thread sir ! I just received my One 64GB official this morning . Damn I love CM11S and this beast don't leave my hand since this morning ahah . Hope your like yours too ...
Can't wait for great PA , Carbon , Omni roms on dat crazy phone

pro castinato said:
Yeah of course man , let me an hour I will show you all with pics . Thanks a lot again for helping us and for the thread sir ! I just received my One 64GB official this morning . Damn I love CM11S and this beast don't leave my hand since this morning ahah . Hope your like yours too ...
Can't wait for great PA , Carbon , Omni roms on dat crazy phone
Click to expand...
Click to collapse
Nice, you're lucky I dont even have the phone yet...hopefully I can get my hands on it in the next couple of weeks or so, otherwise I'll probably have to go with a Nexus 5. Once you've installed a custom recovery check out my SlimRom build. I'm also planning on compiling Carbon, but first I'd like to make sure that Slim is functioning properly.

Chromium said:
Nice, you're lucky I dont even have the phone yet...hopefully I can get my hands on it in the next couple of weeks or so, otherwise I'll probably have to go with a Nexus 5. Once you've installed a custom recovery check out my SlimRom build. I'm also planning on compiling Carbon, but first I'd like to make sure that Slim is functioning properly.
Click to expand...
Click to collapse
Awesome man! Thanks for the help and ports ! If you need I should get like 3 invites this week or less so if you need one let me know , give me your mail address and I will send one your way to thank you

Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..

pro castinato said:
Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..
Click to expand...
Click to collapse
>macbook:android NikonografferZ$ fasboot devices
>fasboot

pro castinato said:
Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..
Click to expand...
Click to collapse
You are missing the "t" in fastboot. You wrote "fasboot", but it should be "fastboot". If that doesnt work, try adding the ./ prefix. ie: "./fastboot devices".

Chromium said:
You are missing the "t" in fastboot. You wrote "fasboot", but it should be "fastboot". If that doesnt work, try adding the ./ prefix. ie: "./fastboot devices".
Click to expand...
Click to collapse
Man I win i Unlock Bootloader and I flash TWRP but is it normal when I restart in recovery I still have the Cyanogen Simple Recovery ?? Damn .....
EDITED !!!! FINALLY ROOTED MY ONE PLUS ONE !!!!!!! Finally read read read 18536 threads and I win ahahha

pro castinato said:
Man I win i Unlock Bootloader and I flash TWRP but is it normal when I restart in recovery I still have the Cyanogen Simple Recovery ?? Damn .....
Click to expand...
Click to collapse
Open settings > developer options. Then look for an option that says 'Update recovery with system updates' and disable it.

Thank you for this guide, it was very easy to follow. I am now rooted and ready to spice this phone up
Sent from my One using Tapatalk

pro castinato said:
l
EDITED !!!! FINALLY ROOTED MY ONE PLUS ONE !!!!!!! Finally read read read 18536 threads and I win ahahha
Click to expand...
Click to collapse
Haha, nice. What got it to finally work?
Sent from my HTC Desire using XDA Free mobile app

Chromium said:
Haha, nice. What got it to finally work?
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Some problems with the T of fastboot lol nope some drivers weird to install .. I needed to install driver even for fastbooted device with Pda.net app who work really fine !! I really thanks the pdanet software <3

[Guide] Tired of EMUI ? Here's a full guide on how to install a Treble Rom

So I was tired of EMUI, the UI design isn't really that bad but it really clashed with Android's Material Design, so since our Mate 9 is Treble compatible, I decided to try a few Treble ROMs. After many fails and factory resets, I finally settled on Havoc-OS. Here I made a guide on how to switch to a Treble Rom.
So a few things to note :
There's no (fully) compatible TWRP recovery for Kirin devices. Either they work but cannot flash OpenGApps or they simply don't work with Treble ROMs.
Huawei's eRecovery seems to work. For me at least, it didn't work before. So as usual, BACKUP ALL OF YOUR DATA(Titanium Backup or HiSuite for apps if needed). You can also use TWRP with stock EMUI if you want to backup your partitions in case something goes really bad.
Make sure you're using stock kernel, ramdisk and recovery_ramdisk before starting anything.
A Micro SD card is optional but useful for restoring things or if you don't want to transfer all of your backup data to your PC
USB Debugging isn't really needed.
-------------------Requirements-------------------
- Your phone, obviously. Has to be a Mate 9 (Pro) updated to Android 8.0 Oreo.
- An unlocked bootloader (Since Huawei stopped giving unlock codes, I can't help you on that one. Sorry boys)
- A PC and a USB Type-C cable.
-------------------A. First things first-------------------
Enable OEM Unlocking
An easy thing to do, otherwise you won't be able to flash anything on your phone (FRP will be "Lock" on bootloader screen). You may think that this is kind of a mandatory thing to do since you've unlocked your bootloader, but you can get it back to disabled and greyed out anytime, so here's a reminder.
1. Enable developer options by going to Settings > System > About Phone and taping multiple times on Build Number
{
"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"
}
2. Once that's done, go to Developer Options and enable OEM Unlocking.
-------------------B. Downloads-------------------
1. Download and install Minimal ADB
Click here to download Minimal ADB
2. Download your ROM, right now there are two fully compatible ROMs :
- OpenKirin Builds : https://openkirin.net/download/
- Havoc-OS : https://forum.xda-developers.com/mate-9/development/rom-havoc-os-t3826470
You'll get an img file that you must put inside where you installed Minimal ADB.
3a. For later : Download Huawei Firmware Finder and Huawei Update Extractor
- Huawei Firmware Finder
- Huawei Update Extractor > If you're not running Windows (Mac, Linux) (Thanks to irony_delerium)
- Also download Magisk Manager (This is an APK)
--- OR ---
3b. Download this patched Ramdisk with Magisk included so that you don't have to download all of the above. CREATED WITH BUILD NUMBER MHA-L29 8.0.0.370(C432). USE AT YOUR OWN RISK IF IT DOESN'T EXACTLY MATCH YOUR PHONE BUILD.
Here (name is patched_boot.img)
-------------------C. Installation-------------------
Now that you've got your Rom img and Minimal ADB, we can start installing it.
1. Turn off your phone.
2. Plug your phone into your PC AND hold down the volume down button until you get a (terrible) white screen saying you're in fastboot&rescue mode.
3a. Open a command prompt (with admin rights if possible) on your PC and get to your Minimal ADB directory. By default, it should look like this :
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
3b. If you installed Minimal ADB on a different drive, then type this :
Code:
cd /d {DRIVELETTER}:/{MINIMAL ADB DIRECTORY/}
4. Make sure your phone is detected by typing :
Code:
fastboot devices
This should show up.
5. Now you can start flashing your ROM by typing :
Code:
fastboot flash system {IMGFILE}.img
Your ROM should start flashing with the message 'target reported max download size of 494927872 bytes'
It should take a minute.
Once you see 'finished. total time: times', that means your ROM has been flashed.
Don't reboot just yet. Things won't work
6. Reboot to recovery by turning off your phone (hold down power button for ~5 seconds) and holding volume up.
7. Now that you are in EMUI recovery, do the following :
- Wipe cache
- Wipe data/factory reset
You MUSTdo this otherwise you will have multiple issues.
8. You're done for the installation. Now reboot to system and start your phone first config (again).
-------------------D. Root-------------------
Your Treble Rom isn't rooted by default. But the Treble Rom itself triggers the SafetyNet flag, which means even if your phone is super clean, it is not certified. So it is obviously completely optional, by it is extremely recommended to install Magisk.
If you downloaded the patched_boot.img file in the attachment
The install process will be extremely easy. It will install Magisk 16.7 (only Beta works with Treble right now). So all you have to do is :
Get to fastboot mode by turning off your phone, plugging it to your PC while holding volume down button. Then, type the following command in the same command prompt window :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and download Magisk Manager. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
If you're not using the attachment
1. Check your phone Android version and build number. It is in Settings > About phone. Write it down, you'll need it.
2. (Install and) Open Huawei Firmware Finder. Get in the 'Common Base' tab and type in your phone build number.
3. Find the matching build number in the list. Make sure its type is 'FullOTA-MF' and its size is 2Go+. Then click on the blue link in the 'Filelist' column. Copy paste the first (ending with 'update.zip') in your browser to download the zip file. It should take some time.
4. Once it's downloaded, open it with 7Zip/WinRar and extract the file named 'UPDATE.APP'.
5. Open Huawei Update Extractor, go to the Settings tab and untick everything.
6. Now, go to the Extract tab and click on the dots on the right and select your extracted 'UPDATE.APP'. A ton of files should appear.
7. Right click on 'RAMDISK', and 'Extract selected'. Put it somewhere on your PC, you'll need it.
8. Plug your phone on your computer and put your RAMDISK.IMG in a folder on your phone.
9. On your phone, download and install Magisk Manager. If it prompts you to do so, do not install it. Then go to Settings tab and change 'Update Channel' to 'Beta'.
10. Now go back and tap 'Install', then choose 'Patch Boot Image File' and select your RAMDISK.IMG that you transferred to your phone. Then let Magisk do its thing.
11. Once it's done, on your PC, go to Your Phone/Internal Store/MagiskManager, and transfer the file 'patched_boot.img' to your Minimal ADB folder.
12. Turn off your phone and get to fastboot mode. You know how to do it now, don't you ?
13. In the same command prompt on your PC, type :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and BAM, you're rooted. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
-------------------E. SafetyNet-------------------
Magisk may be installed, but with a Treble Rom, SafetyNet should trigger anyway. So you'll have to do a few things.
1. In Magisk Manager, go to the Downloads tab and search for 'MagiskHide Props Config'. Install it, then reboot your phone.
2a. Once your phone is rebooted, download Terminal Emulator on the Play Store
--- OR ---
2b. Go to developer options and enable 'Local Terminal'.
3. Open your terminal, then type :
Code:
su
(Accept root request)
Code:
props
Things should appear. Woah.
4. Type 1 (Edit device fingerprint), then f, then choose a vendor and a model by typing the right number, then press y. Don't reboot yet (press n)
5. Type 6 (Script settings), then 1, then y. Now you can reboot (press y). Once it's done, make sure that 'boot stage' is 'currently post-fs-data'. Otherwise SafetyNet will still trigger.
THERE YOU GO ! Your phone should pass SafetyNet. You can check this by trying to search for the Netflix app on the Play Store or going into the Play Store settings and making sure your device is Certified'.
If you have any question/bug, do ask/report all of dem to me.

I haven't rooted or done anything with this device since I've bought it coming from all Samsung devices previously. This guide is awesome! Nice work!

About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".

i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages

irony_delerium said:
About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".
Click to expand...
Click to collapse
Yup, I'm aware of the Play Store app, but IMO, having everything directly on your PC is more convenient. Also what you said is useful for people not running Windows, so kudos to you for that.

aureliomilitao said:
i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages
Click to expand...
Click to collapse
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.

Deytron said:
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.
Click to expand...
Click to collapse
i extract system.img in update.app ...and lost Brazil language

aureliomilitao said:
i extract system.img in update.app ...and lost Brazil language
Click to expand...
Click to collapse
Well... I'm sorry, but I can't help you on that one. It just doesn't make sense. You can't "lose" a language. As I said, try to use Huawei eRecovery to completely restore your phone.

Solved

How To Guide [GUIDE][HowTo]Pushing an OTA.zip Update with ADB Sideload - via Recovery - via Local Update

ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK.
THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)
GOOD CONTINUATION TO ALL
Installing an OTA.zip Update with ADB Sideload​
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine - ​
Click to expand...
Click to collapse
In this thread you will find different ways to install an OTA update :
Via ADB SIDELOAD (this post) - Via Recovery Mode - Via Local Upgrade
​I am writing this tutorial on ADB Sideload, one more on this topic, in order to be able to push an OTA Zip update, which for some reason could not be done properly.
Sometimes manufacturers allow users to make links or zip files of OTA updates available to other users. Once you have downloaded the OTA zip file, you will need this tutorial to proceed with the installation.
I borrowed the first two screenshots from the web so that I could explain clearly with pictures.
In the end it is very simple and requires little command line knowledge. But you will need to check some things:
- Firmware stock
- Unmodified system partition
- Third party apps like Magisk, Xposed Framework, and as a precaution TWRP Recovery should not be installed on your smartphone
Before starting, here is the list of prerequisites to perform the sideloading of the OTA package.
1. Have a backup of your data, even if theoretically performing a sideload will not erase your data,
2. Download the USB Drivers from the manufacturer, or the latest one from Google ( Link )
3. If you haven't already done so, you must download and install Android SDK Platform-tools (platform-tools_r33.0.2-windows.zip)
4. Don't forget to push on this folder "platform-tools" the file named "Global full Nothing OS 1.1.0.zip" - for example- that you need
4. And finally you will have to activate the USB debugging of your Phone(1) : to do so, you have to go to : Settings => System => Advanced => Type 7 times on the build number => once done, a pop-up will appear and will tell you that you have become a "Developer" => On some devices you will have to type in the Pin code.
5. Once you have become a developer => go back to System => Developer Options => Enable the USB Debug toggle
6. That's it if you are ready to do a Sideload, but also other operations!
{
"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"
}
​
These prerequisites are essential for this and a number of other operations.
You are ready, the tension is rising! You will succeed!
To do this, you must reboot your Phone(1) into the standard recovery system and you have 2 ways to reboot into Recovery.
1. You can use the hardware key combination specific to your smartphone.
2. Or use the ADB command
Booting into Recovery Stock mode with the ADB command
You go to the start screen of your PC and in the search bar you type:
Code:
cmd
and then press Enter. The command prompt starts.
Depending on where you have placed your "Platform-tools" folder you type:
Code:
C:\WINDOWS\system32>cd c:\platform-tools
and you should see on your command line screen
Code:
c:\platform-tools>
Once you are in your Platform-tools folder, connect your smartphone to your PC, making sure that USb debugging is effective.
Type the following command: adb devices and you should see the identification of your smartphone
When you run an ADB command, you should see an RSA key prompt on your smartphone screen asking you to allow USB debugging. Press OK to allow it.​
Type the following command: adb reboot recovery​
Then the command: adb sideload "file name".zip - For the example, I typed the full name of the file, but you can rename the file shorter like "nothing_ota".zip
That's it, normally the installation is started and you just have to wait for the update to be installed on your device. Once the installation is successful, you can restart your device.
I hope this tutorial has helped you to push an OTA.zip update.
Go ahead now

Installation via recovery mode​
The recovery mode of the Phone(1) is similar to that of the Google Pixel. This allows you to easily sideload the update packages via the recovery interface.
To perform this process, here are the steps and requirements:
Have downloaded the .zip file of the update to your computer
Your Phone(1) must be recognised by the ADB command on your computer
The Process:
Go to your Shell terminal, then run the recognition command:
Code:
adb devices
then the command :
Code:
adb reboot recovery
On your Phone(1) screen, you should see this "No command"
While pressing the Power button, press the Volume Up button then release both buttons quickly. The Android recovery menu should be visible.
Nothing Phone 1 recovery mode
On your Phone(1) screen, select the option: Apply update from ADB.
On your computer, run the command:
Code:
adb devices
This should return the serial number of the device with the 'sideload' next to its name, indicating that your device is connected to the computer in sideload mode.
On your computer, run the command:
Code:
adb sideload "filename".zip
The "filename" part should be replaced with the full path, followed by the name of the file downloaded in step 1.
The update will be installed on your phone.
Once the installation is complete, select "Reboot system now" on your phone to reboot into the new version.
Well done, you have installed the new update of Nothing OS to your Phone(1) with success
To date I still haven't received my phone(1). Once I have it in my hands, I will make screenshots about this tutorial.

Install OTA using Local Upgrade method​
Create a folder named “ota” (without the quotes) at the root of the internal storage. Meaning outside every folder.
Copy the OTA update ZIP file from above to that folder.
Open the phone app and Dial ##682##
This should launch an offline update tool.
The tool will scan for an OTA file from internal storage and install it.
If that fails, you can manually browse for the OTA package.
After selecting the OTA file, the wizard will apply the update.
Reboot the device and you are on the latest firmware.

Reserved 3

I think also after update, reboot, redo the step and sideload also Magisk for keep root

Pho3nX said:
I think also after update, reboot, redo the step and sideload also Magisk for keep root
Click to expand...
Click to collapse
Yes I agree, but those tutos are for everyone, and everyone doesn't rooted his smartphone like us
So I won't confuse them

hello, thanks for the guide, when I do all the steps without any problems and reboot, it opens with the old version, where could I be doing wrong?

This will work to downgrade the phone also?

pankspoo said:
This will work to downgrade the phone also?
Click to expand...
Click to collapse
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone

sh4tteredd said:
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone
Click to expand...
Click to collapse
So we can use your Windows tool to downgrade ?

pankspoo said:
So we can use your Windows tool to downgrade ?
Click to expand...
Click to collapse
I won't downgrade this phone at all. Btw maybe I'm wrong and it can work but I'm not sure and I don't suggest to do it

Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.

demiii said:
Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.
View attachment 5716899
Click to expand...
Click to collapse
Which version of ADB Sideload do you use ?
Post 1 or Post 2

Sib64 said:
Which version of ADB Sideload do you use ?
Post 1 or Post 2
Click to expand...
Click to collapse
What I did was reboot to recovery, navigate to Apply Update via Sideload through the recovery interface and from there entered the command adb sideload filename.zip so i guess it is the method in post 2
UPDATE:
I have tried the method in Post 1 and this error shows up:
UPDATE 2:
I have tried revoking USB DEBUGGING authorization, adb kill-server, adb start-server and authorizing again
I have tried deleting adbkey and adbkey.pub files in C:Users/$Name/.android
I have tried following suggestions about solving this error both from this and this StackOverflow thread
Nothing worked for me.

You don't need to use ADB to sideload an OTA, the nothing phone contains an OTA updater In the phones os already, the only thing you need the computer for is to move the OTA to the phone

Here is what someone on the nothing discord said to do and it worked
dont sideload
Create a folder named “ota” (without the quotes) at the root of the internal storage of your phone. Then copy the update ZIP file to that folder.
Dial `*#*#682#*#* `to open up the offline update tool.
You can also use an activity launcher app to locate and execute the “OfflineOTAUpgrade” tool. The package name of the tool is com.nothing.OfflineOTAUpgradeApp.

Hi, I have just tried your method but an error window pops up:

Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?

Ky0sHiR0 said:
Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?
Click to expand...
Click to collapse
You can only upgrade not downgrade

demiii said:
Hi, I have just tried your method but an error window pops up:
View attachment 5717197
Click to expand...
Click to collapse
If you go on nothing discord and put that error maybe they can help