Database Users

[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

Dual/Multi Boot On the OnePlus 3T

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have looked around and haven't seen anyone mention this so I thought I would post about it. I hope others find this useful. I've used this tool on my Galaxy Note 4 to have two different OS's running (mostly due to bluetooth problems on CM, but I digress). This allows the user to dual boot and maintain safetynet with Magisk. I've used this a lot and was really excited to see that it is compatible with this amazing phone!
The thread that caught my interest on the subject (for Note 4): http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
The original thread quoted by @aukhan (for S4, but most of the discussion is here too): http://forum.xda-developers.com/showthread.php?t=2447534
All credit goes to the original developers for this tool, I had nothing to do with its development. This thread is made to troubleshoot our specific device without clogging up their threads for other devices.
Thanks to @aukhan, @rlorange, @chenxiaolong , and other contributors.
Download the Dual Boot Patcher snapshot apk from here. That is the only app that you should need to complete the process. Click on the latest build link and then click on the android file that ends in "snapshot.apk". The snapshots are the recommended version at the moment.
I made a video walkthrough of this process for the Note 4. A lot of it is similar, but I will try to get a new video up for the OP3T when I have time.
Basically you patch all of the .zip files that you would have flashed normally and then you flash them to a new ROM slot. If there are more questions that the video and my more specific instructions below don't answer I'll be happy to answer them or post a better walkthrough if needed.
It should be noted that to switch back and forth you'll need to install the Dual Boot Patcher apk on both ROMs. This does not affect TWRP Recovery.
So far I've only done this once on the 3T and I haven't had any issues. Obviously the 5 second delay is a little annoying when booting between ROMs, but I can get over that. I currently have RR Official installed as my primary with Open Beta 6 as my secondary. Normally the stock ROM is recommended for the primary boot slot, but this seems to work fine.
More Specific Instructions for recommended Data Slot:
1) Download all .zip files that you would flash if you were going to flash the ROM normally (ex. LOS, Gapps, SuperSu, XPosed, kernels, etc)
2) Download the Dual Boot Patcher apk: https://snapshots.noobdev.io/, install it on your phone, set the kernel, and update the ramdisk (ROMs page, three dots on Primary, scroll to bottom)
3) Open Dual Boot Patcher app and tap the three lines in the upper left then select "Patch Zip File"
4) Tap the plus button and find each of the .zip files that you will be flashing. After selecting one make sure to change "Partition Configuration" to "Data slot" and enter a number (be consistent with each file). Push continue.
5) A file browser will now open. Navigate to the place you'd like to save the file and select the location.
6) You may now repeat steps 4 and 5 to add the rest of the zip files
7) Tap the check mark in the upper right to "Patch" all of the .zip files
8) Tap the three lines in the upper left again and select ROMs
-Installation
--Option 1
9) Tap the phone icon in the lower right and push okay
10) Tap the plus button in the lower right and navigate to where you saved your patched files. Select the main ROM (the ROM you want to dual boot to) and tap "keep location" (this will put all data in the location it specified ie /data/multiboot/data-slot-1 for this case)
11) Repeat step 10 until all zips are added in the order you want them flashed (the order is important so get your ROM before your Gapps etc). If you mess up swipe the one that's in the wrong order to the right to remove it from the list
12) Tap the check mark in the upper right. A console should appear and it should virtually flash the ROM as you would expect in TWRP
13) Once it says "x/x completed" in cyan text and it has stopped you can just tap the back arrow in the upper left
14) If you go back to the ROMs page there should now be a "Secondary" ROM. To test it out you'll need to select it and then reboot the phone.
15) Once it has booted and you are past the setup you'll need to enable "unknown sources" in the menu and install Dual Boot Patcher. Once it's installed, open it. It should find the two ROMs and you'll be able to select Primary from the ROMs menu and reboot back
--Option 2 (best if your ROM doesn't report your device name like RR)
9) After patching the files reboot into TWRP
10) Flash the patched files like you would normally flash a ROM (order is important so flash the ROM before Gapps, su, etc)
11) Once the process has completed reboot into system
12) Since you haven't selected the secondary ROM at this point it should boot to your primary ROM (although I can't remember at the moment). Open Dual Boot Patcher, select the ROMs page, select the secondary ROM, and reboot your phone
13) It should reboot to your newly installed ROM where you can set it up and install DBP to boot back between ROMs.
This process can be done using any of the partition configurations listed when patching a Zip file. Secondary and Multi Slots go to the System partition and data slot goes to internal storage. I recommend not using the Multi Slots since more than two ROMs is a lot on the system partition. I would recommend the data slots.
If you have problems make sure to set the kernel and update the ramdisk before flashing
In the event of a bootloop you can recover your primary ROM by entering TWRP, tapping install, selecting image in the bottom right corner, navigating to the /sdcard/MultiBoot/primary folder, and selecting the "boot.img" file. This will return your phone back to the primary ROM.
There is a multiboot.log file that is very useful for debugging. Please post it if you have issues (found in the /sdcard folder)
If you later want to flash anything to the ROM that you're "dual booting" into then all you have to do is patch the zip files and flash them like before except you're flashing to a slot that already has a ROM now.
Tasker Integration
I've been using RR as my daily driver, but the BT doesn't work in my car. I did a lot of research to enable ROM switching in Tasker so that I could easily switch over ROMs when I get into my car. I use my android watch to trigger the task into my OOS ROM and then when BT disconnects I have it trigger a task to switch back to RR. Here it is:
Add action>system>send intent
Under "Action" enter
Code:
com.github.chenxiaolong.dualbootpatcher.SWITCH_ROM
Under "Cat": Default
Under the first "Extra" enter
Code:
rom_id:primary
(change primary to dual or whatever your other slot name is)
Under the second "Extra" enter
Code:
reboot:true
(this tells the app to reboot right after switching the ROM to the desired one)
Under "Target": Activity
I have found that the intent will trigger if the phone is locked, but won't do anything until the phone is unlocked. With swipe or smart lock enabled you can use secure settings to wake the screen and then run a shell with root to swipe up on the lock screen (Command: "input swipe X1 Y1 X2 Y2" replace the X's and Y's with numbers for your screen. Use developer settings to figure out where the start and stop should be.)
All of this allows me to trigger a ROM switch and reboot from my watch without taking my phone out of my pocket (i.e. while driving).
Backup/Restore/Move ROMs from/to specified slots
chenxiaolong said:
Wow, a lot has happened since my midterms started Once midterms are over, I'll start replying to posts here again (starting from around page 731 when I last posted).
I haven't been doing absolutely nothing over the past couple weeks though! We now have a very basic backup and restore implementation. This is still very much a work-in-progress and currently has no UI (nor does it work outside of recovery mode). But anyway, I figured some people who love bleeding edge stuff will want to give this a try. (And yes, backing up one slot and restoring to another already works!)
Like the installer, DualBootUtilities, and pretty much everything multiboot-related, backup and restore is handled by mbtool. I've compiled debug versions here with the new backup & restore features: https://snapshots.noobdev.io/misc/mbtool/mbtool_recovery_8.0.0.r1855.gfeb767e_DEBUG.tar.xz EDIT: Extract "mbtool_recovery" from the PC zip (easier) or from assets/data-8.0.0-rVERSION.tar.xz in the apk.
To give this a try, you'll want make sure your adb command is set up properly and reboot into recovery. Then you'll need to copy the appropriate mbtool_recovery binary to /tmp/:
Code:
# For 32-bit ARM devices
adb push armeabi-v7a/mbtool_recovery /tmp/
# For 64-bit ARM devices
adb push arm64-v8a/mbtool_recovery /tmp/
# For x86/x86_64 Intel devices, you guys probably already know what you're doing
Then, make sure /system is mounted because TWRP does not mount it by default.
Code:
adb shell mount /system
Now, to backup a ROM, run, for example (to backup extsd-slot-cm to a backup named "my_backup_name"):
EDIT: One thing to note because the tool doesn't detect this yet. If you want to backup the primary ROM, make sure to do a ramdisk update from the app first. Otherwise, the kernel will not have any multiboot code and won't boot if you decide to restore it to another slot.
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup -r extsd-slot-cm -n my_backup_name
To restore a ROM, run, for example (to restore "my_backup_name" to multi-slot-1):
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery restore -r multi-slot-1 -n my_backup_name
If you want to do partial backups (say, backing up the data and kernel only), you can add "-t data,boot" to the command. For more command arguments, see:
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup --help
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery restore --help
I expect there to be a lot of bugs, so feel free to blame me or yell at me for whatever issues you run into
Click to expand...
Click to collapse
Edit: Turns out I didn't look hard enough. There is a thread that has already been created to discuss this tool on this wonderful phone and it fixes an issue where some ROMs with 3/3T support won't flash in dual-boot.

I erroneously did the upgrade ramdisk on my 3t with OxygenOS and now phone is not booting anymore (5 vibration and then recovery)... Someone can help me in understanding what I can do to solve it?

mar.ste said:
I erroneously did the upgrade ramdisk on my 3t with OxygenOS and now phone is not booting anymore (5 vibration and then recovery)... Someone can help me in understanding what I can do to solve it?
Click to expand...
Click to collapse
It has been awhile since I've played with DBP, but I seem to recall that it stores a copy of the boot image before the ramdisk update that you can flash

[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

[GUIDE] ROOT LG G Pad V530 For Newbies!

[GUIDE] ROOT LG G Pad V530 For Newbies!
On August 1, 2021 I am giving up my Mediafire account. There will no longer be a link to the files. If anybody else would like to host the files, that is OK with me.
This is a Guide for those who have never Rooted a device. The Guide assumes no prior knowledge.
I had a young one in my family, a fifth grader, follows these instructions and she was able to root one of my LG V530
without a problem. Just print the Guide and READ THE WHOLE GUIDE BEFORE YOU START.
REQUIRED: (1.) Windows PC (2.) LG V530 Tablet (3.) USB Cable (4.) Stock boot.img
CREDITS:
Now before we get started I want to give credit to the following:
topjohnwu For Magisk Manager
Snoop05 For 15 Second ADB Installer
Vincen_vann For explaining how to extract the stock boot.img from our LG V530 or any other LG device.
(See below the link for how to extract Stock boot.img)
[WARNING!!] This ROOTING GUIDE will allow to ROOT you LG V530 or any LG device
SAFELY if you have the Stock “boot.img”
(V530 boot.img is included in the Download folder)
[WARNING!!] If you do not have a stock boot.img FOR YOUR DEVICE – STOP!!
[DO NOT ATTEMPT ROOT!] (See Extract Stock boot.img BELOW)
[WARNING!!] All user data and downloaded apps will be delete on ROOTING
We are going to use a step by step method. Please check off each step as it is completed.
____ 1.) Download whatever files you need from folder. The link is below .
If you are new to ROOTING then download the whole folder.
http://www.mediafire.com/folder/f9f1qfoazyc6g/ROOT LG G Pad V530 for Newbies
____ 2.) Open the Windows Driver folder in the extracted folder and install both
adb-setup-1.4.3 & LGMobileDriver_WHQL_Ver_4.2.0
____ 3.) On your PC Open the "GET ROOT Batch and ADB Command" folder and copy the
GETROOT.bat to your c:\adb folder.
____ 4.) On your LG V530 go to Setting -> About Tablet -> Hardware info -> Model number if is LG-530
go to step-5. If the Model is NOT LG-530 [ STOP! ]
____ 5.) On your LG-530 go to Settings -> Security -> Unknown sources Tap to set On
____ 6.) On your LG-530 go to Settings -> About tablet -> Software info -> Build number Tap 7 times
____ 7.) On your LG-530 go to Settings -> Developer options -> Enable OEM unlock and USB debugging
____ 8.) Connect USB cable to LG-530 and PC then Tap OK to Allow USB Debugging
Now change the USB mode from Charging to File Transfer
____ 9.) Open the LG-530 in the Windows explorer then open the folder → "Stock boot.img for LG Pad V530"
and drag and drop "boot.img" to your V530 tablets sd_card or to your Tablets Download folder if you don’t have an sd_card.
____ 10.) Remove the USB Cable from the LG-530
____ 11.) Re-Connect the USB Cable LG-530 then Tap the “OK” to Allow for USB Debugging.
Now change from Charging mode to PHOTO Transfer. Go to your C:\adb folder hold
down the shift key and right click the mouse and select Open a Command Prompt here.
Type -> adb devices then the press return key on your keyboard you should see your
LG-530 listed in the adb devices
____ 12.) Remove the USB cable from you LG-530
____ 13.) On LG-530 go to https://github.com/topjohnwu/Magisk/releases and download the latest version
of Magisk Manager (Always use the latest version)
____ 14.) Install Magisk Manager and select Patched Boot Image File from the 2 options. DO NOT Select Install ZIP!
{
"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"
}
Tap on the upper left corner of Magisk Manager
and Navigate to the folder where you copied boot.img and select boot.img
Now wait for Magisk Manager to finish creating the magisk_patched.img
Magisk Manager will have created the file magisk_patched.img in your download folder.
Once the magisk_patched.img is created exit Magisk Manager
____ 15.) Press the Power key on your LG-530 and select Power off and restart.
(I have found that after running Magisk Manager a restart is necessary,
so that you can select the usb transfer mode).
____ 16.) Connect the USB cable and select PHOTO Transfer mode.
Go to your C:\adb folder and open it.
Find the GETROOT.bat file in your C:\adb folder and right click
and select Run as Administrator.
[OPTION]
If would rather type the ADB commands instead of using the GETROOT.bat
they are in the “GET ROOT Batch and ADB Commands” folder and shown below.
adb devices
adb pull /sdcard/Download/magisk_patched.img
adb reboot bootloader
fastboot oem unlock
fastboot flash boot magisk_patched.img
fastboot reboot
____ 17.) You LG-530 will reboot. Don't worry about the LG unlocked bootloader message just
press the power button once and wait. it will take a little time to awhile to boot,
but you will see Android is Starting Screen (Be Patient).
____ 18.) After you LG-530 has boot you will have to enter all your user data again,
just like FOR a new tablet.
____ 19.) Now download Magisk Manager again and install it. After installing,tap on the SafetyNet Check
on the middle on the Magisk screen. Magisk will ask to Download and Install Proprietary Code.
Tap Allow. Once the code is installed, Re-Boot the tablet, REBOOT needed for Magisk to finish installing.
After reboot go to Magisk and tap on the SafetyNet Check it should be Green
and show that you have passed the SafetyNet.
This means you are ROOTED.
[CLEAN UP] From the File Manager go to the Download folder and delete magisk_patched.img
[ENHANCEMENTS] Go to F-Droid.com download and install F-Droid.
Once f-Droid is installed, use the F-Droid search to find AdAway.app
Setup AdAway and download the AdAway host files.
Now use F-Droid to find DNS66.app download and install it
Configure DNS66 to use the AdAway host files. Start DNS66.
Now NO MORE Google Ads in downloaded apps.
[EXACT Stock boot.img from LG devices] The Link below explains how to do it.
https://forum.xda-developers.com/g-...mo-lg-v530-t3715663/post76052694#post76052694
[UNROOTING] [WARNING NEVER UNINSTALL Magisk!]
Use the Magisk Uninstaller to UNROOT your LG G Pad.
If you just uninstall Magisk will no longer boot you device!
After Using Magisk Uninstaller
Then: If want to return your device to stock.
Copy the “Lock_Bootloader.bat” to your
c:\adb folder and right click Lock_Bootloader.bat and Run as Administrator.
On August 1, 2021 I am giving up my Mediafire account. There will no longer be a link to the files. If anybody else would like to host the files, that is OK with me.

You really should modify the script to incorporate functionality for people who do not have an external sd card and have downloaded the boot.img folder to their downloads folder as you descried in your tutorial.
Also the newest version of magisk 7.3.2 labels the patched file as "magisk_patched.img" not "patched_boot.img" as you had it in the script.
Since I didn't have an sd card inserted and assumed you had taken care of the possibility that a user may place the boot.img file in either place you suggested it obviously didn't work but i didn't know that till I went through the entire process and then downloaded and setup magisk again and it didn't say it was installed same as before.
I then ran each command in command prompt one by one to see where the error was occurring. I compared the file location and name you had in the script to the one magisk had in its flashing log screen and I fixed the script to match magisks log output. It then worked properly.
My original boot image and the patched boot file labeled as I descried above was located in "/storage/emulated/0/Download"
I wouldnt say anything if this tutorial didnt say specifically and I quote
"ROOT LG G Pad V530 For Newbies!
This is a Guide for those who have never Rooted a device. The Guide assumes no prior knowledge.
I had a young one in my family, a fifth grader, follows these instructions and she was able to root one of my LG V530
without a problem. Just print the Guide and READ THE WHOLE GUIDE BEFORE YOU START."
Change one variable such as not having and not thinking you need an sd card via your own guide text, and your guide for noobs is not for noobs any longer.

Guide and GETROOT.bat Updated
polygaryd said:
You really should modify the script to incorporate functionality for people who do not have an external sd card and have downloaded the boot.img folder to their downloads folder as you descried in your tutorial.
Also the newest version of magisk 7.3.2 labels the patched file as "magisk_patched.img" not "patched_boot.img" as you had it in the script.
Since I didn't have an sd card inserted and assumed you had taken care of the possibility that a user may place the boot.img file in either place you suggested it obviously didn't work but i didn't know that till I went through the entire process and then downloaded and setup magisk again and it didn't say it was installed same as before.
I then ran each command in command prompt one by one to see where the error was occurring. I compared the file location and name you had in the script to the one magisk had in its flashing log screen and I fixed the script to match magisks log output. It then worked properly.
My original boot image and the patched boot file labeled as I descried above was located in "/storage/emulated/0/Download"
I wouldnt say anything if this tutorial didnt say specifically and I quote
I believe everything should work, but if anybody finds a problem please let me know.
"ROOT LG G Pad V530 For Newbies!
This is a Guide for those who have never Rooted a device. The Guide assumes no prior knowledge.
I had a young one in my family, a fifth grader, follows these instructions and she was able to root one of my LG V530
without a problem. Just print the Guide and READ THE WHOLE GUIDE BEFORE YOU START."
Change one variable such as not having and not thinking you need an sd card via your own guide text, and your guide for noobs is not for noobs any longer.
Click to expand...
Click to collapse
I have updated the Guide and the GETROOT.bat file.
I use magisk_patched.img in the script per your post.
I have not tested the script. My tablet is being used right now and I don't have time to unrooted and than rooted it to test everything
Lastly please read step 9. You can copy the boot.img to your Download folder if you don't have and sd card.

whenever I install magisk, it says that my version is not supported but then when I download ANY older versions it says the file is corrupt?

Link to Download Newest Version Magisk Manager
spart0n said:
whenever I install magisk, it says that my version is not supported but then when I download ANY older versions it says the file is corrupt?
Click to expand...
Click to collapse
I am not sure what is happening.
Can you provide more details?
In the guide are you at Step 14?
I have list the URL to the newest version of Magisk Manager below.
You should be downloading the Magisk Manager.
The URL for Magisk -> https://github.com/topjohnwu/Magisk/releases/

I fixed it nevermind lol

xdaGerry said:
I am not sure what is happening.
Can you provide more details?
In the guide are you at Step 14?
I have list the URL to the newest version of Magisk Manager below.
You should be downloading the Magisk Manager.
The URL for Magisk -> https://github.com/topjohnwu/Magisk/releases/
Click to expand...
Click to collapse
My issue was that I had previously rooted this tablet and the newest version of magisk manager wouldn't use it so I had to go back and install a really old version of magisk manager, update magisk then update magisk manager.
Anyway I have a question for you.
So far i have FDE module installed through magisk and I'm looking for more ways to squeeze any last bit of performance out of this old thing, I also installed elementalx manager and made some manual tweaks to apply on boot. A larger swap file, CPU and GPU set to performance always.
Anything else I can do to extend the life and performance of this old tablet?

I was able to install Magisk manager, but Your "getroot" file is 7z. I need a windows file please.

kcohen67 said:
I was able to install Magisk manager, but Your "getroot" file is 7z. I need a windows file please.
Click to expand...
Click to collapse
The GetRoot folder is compressed as a 7z file.
You can download 7-Zip from here: -> https://www.7-zip.org/download.html
7-Zip is free and open source. Download it and install it. Right click on the 7z file and extract it.

Thank you for this guide!
I'm getting stuck on step 17. After running GETROOT the tablet switches to "Welcome to Fastboot Mode for bootloader unlock:"
I'm unable to select anything. The only thing I can do is hold power + volume down to force the device to restart. The CMD window says "waiting for device".
What am I missing?

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