Database Develop

[Q] OTA update on stock ROM, but custom recovery

Good morning, all:
I just got my HTC One the other day and, in the process of transferring content from my Galaxy SIII, I rooted and installed CWM recovery, but kept the stock ROM because I liked the change from what I'd been using on the SIII (CM).
Unfortunately, in the last day or so, an OTA update was released for the One and, as I found out (and you likely know), you can't perform OTA updates with a custom recovery. The constant notifications are enough to make me want to update, besides the obvious benefits of increased stability.
I was wondering if I could flash the recovery found in the [Recovery] Stock HTC One post (http://forum.xda-developers.com/showthread.php?t=2158763) to the device so that I could update? Also, would this break my root/superuser? The device is a TELUS model (if they differentiate by carrier) with software no° 1.29.661.5.
Any advice would be appreciated. Thanks!
------------------------------
UPDATE - 2:38 PM
------------------------------
Hey, guys:
Sorry for all of this noise, I figured things out and wanted to delete this thread, but can't seem to do that.
For those of you experiencing similar issues, who followed mike1986.'s Complete Flashing Guide post, the process for restoring your stock Recovery image to do OTA updates is actually super simple:
- Connect your phone to your computer and pull the backup you did of your device before flashing the custom recovery image.
- Open the folder and move the Recovery.img file to your Android SDK folder.
-Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
-Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
- Navigate to [your SDK directory] (type in Command Prompt: cd c:\[directory]).
- In the Command Prompt type following command: fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Using this method, you could flash your stock recovery back onto the device, perform the OTA, then flash the custom Recovery.img back onto your device all in the span of 5 minutes.
This is probably standard stuff for most people on this forum.

[DELETED]

Could you please post your custom recovery?
I need to do the same procedure as yours, and I am currently on same fw, from Telus.
Many thanks.
Sent from a pizza

millicent said:
Could you please post your custom recovery?
Click to expand...
Click to collapse
Sure thing, millicent.
Tried attaching it to the post, but that wasn't working so here's a DropBox link: HTC One Stock Recover (1.29.661.5). Happy OTA updating!

I've tried this, but the OTA update package won't install. Flashing the Recovery.img isn't enough.

Sonnyw said:
I've tried this, but the OTA update package won't install. Flashing the Recovery.img isn't enough.
Click to expand...
Click to collapse
I assume you're running a stock ROM, so did you delete any stock apps(i.e bloatware)? If so, you will need to NAND restore to a stock backup or get those apps back. First thing an official OTA does is check the signatures on all the files it'd expecting to be on the device and if any come back wrong or missing, update aborts.
Sent from my Galaxy S4

unremarked said:
I assume you're running a stock ROM, so did you delete any stock apps(i.e bloatware)? If so, you will need to NAND restore to a stock backup or get those apps back. First thing an official OTA does is check the signatures on all the files it'd expecting to be on the device and if any come back wrong or missing, update aborts.
Sent from my Galaxy S4
Click to expand...
Click to collapse
Remember that unlocking the bootloader automatically deletes a few apps, which you will need to install back

MacHackz said:
Remember that unlocking the bootloader automatically deletes a few apps, which you will need to install back
Click to expand...
Click to collapse
So I was just wondering, if i install the bloatware/default apps back manually (using the .apk files) and flash the recovery back to stock. Will I be able to do an OTA update Without loss of data? If that´s possible, I wil flash the custom bootloader back after performing the OTA update.

Guys, thanks for helping me out. I've done an OTA update without any data loss, you can read about it in thishttp://forum.xda-developers.com/showthread.php?p=42122514#post42122514 Thread.

MacHackz said:
Remember that unlocking the bootloader automatically deletes a few apps, which you will need to install back
Click to expand...
Click to collapse
Really? I did not know this! Out of my curiosity, do you know what apps get deleted?
Sent from my Galaxy S4

unremarked said:
Really? I did not know this! Out of my curiosity, do you know what apps get deleted?
Sent from my Galaxy S4
Click to expand...
Click to collapse
{
"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"
}

MacHackz said:
Click to expand...
Click to collapse
What a strange assortment of apps to be removed. Thanks for the info!

Can you tell me where to find the stock recovery I'm moto e
No one ever mentions where to find the stock recovery file for a noob like me
When I find it, Should I flash it via cmd and I'll get my stock recovery back?I want it back to install official lollipop 5.1 I downloaded.It won't install after downloading but just takes me to the TWRP Screen(ya I have TWRP installed)

HELP ME PLEASEEE said:
No one ever mentions where to find the stock recovery file for a noob like me
When I find it, Should I flash it via cmd and I'll get my stock recovery back?I want it back to install official lollipop 5.1 I downloaded.It won't install after downloading but just takes me to the TWRP Screen(ya I have TWRP installed)
Click to expand...
Click to collapse
This is the HTC One M7 forum, if you need help with your Moto E post in the Moto E forum.
http://forum.xda-developers.com/moto-e

[INFO] Nexus 5 OTA Help-Desk

..
{
"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"
}
OTA Help-Desk
*5.1.1 LMY48B Available*
*5.1 LMY47I Available*​
*5.1 LMY47D Available*
This thread is only for OTA help and nothing else!
Flash stock recovery before proceeding
​.​
NOTE: If You are a rooted non-stock user I suggest you look at @rootSU's thread before proceeding as his method for rooted users is far less prone to cause issues.
http://forum.xda-developers.com/google-nexus-5/general/info-rooted-user-learn-to-update-t2927876
First, let's talk about what an OTA is:
An OTA (Over the Air) update is the method of updating your phone's software. When the OTA is downloaded to your phone it will prompt you to reboot and install. It is not a complete image, but a series of patches to the OS. Patches in the OTA can include: bootloader, radio, system, recovery and kernel. While it's installing, the script checks the files it is patching to make sure the original files are correct. If everything is correct, the update will finish successfully. If it's not, the process will stop. That's why it is critical to make sure everything is in its "out of the box" state. Don't worry though. It is easy to get your phone back to a state where you will have it up and running, with the latest software.
We are also able to manually flash this file. When the URL of the OTA is discovered, you can download it and use adb or a custom recovery to apply it.
Now that you have read the important info above, Let's update your Nexus 5!
In order for the OTA to apply successfully without intervention; you must be completely stock
From 4.4.4 KTU84P
Current Bootloader: HHZ11k
Current Radio M8974A-2.0.50.1.16
Stock Kernel: 3.4.0-gd59db4e
All /system apps present
No modifications to existing /system files of ANY kind.
From 4.4.3 KTU84M
Current Bootloader: HHZ11k
Current Radio:M8974A-2.0.50.1.13
Stock Kernel: 3.4.0-gd59db4e
All /system apps present
No modifications to existing /system files of ANY kind.
Note: Literally any modification will break the OTA. Xposed, DPI, build.prop, volume mod, etc. ANYTHING!
Seriously, I'm not joking guys.
If you meet the above criteria, the OTA will complete successfully.
If you don’t meet the criteria or don’t want to wait for the OTA to hit your device then see below.
Current OTA's
5.1.1 LMY48B from LMY47D: https://dl.dropboxusercontent.com/u/33560221/OTA_update_from_lmy47d_to_lmy48b.zip
5.1 LMY47I from 5.0.1 LRX22C: http://android.clients.google.com/packages/ota/google_hammerhead/90bd789f499ea5ad33510c568ec920aae7214d34.signed-hammerhead-ota-LMY47I-from-LRX22C-radio-restricted.zip
5.1 LMY47D from 5.0.1 LRX22C: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX22C-radio-restricted.zip
5.1 LMY47D from 5.0 LRX21O: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX21O-radio-restricted.zip
Legacy OTA's
5.0.1 LRX22C from 5.0 LRX210: http://goo.gl/eoV0GE
5.0.1 LRX22C-from-KTU84: http://android.clients.google.com/packages/ota/google_hammerhead/6dadaf477bab65f42f5681b03bd535f431594b95.signed-hammerhead-LRX22C-from-KTU84P.6dadaf47.zip
5.0 LRX21O-from-4.4.4 r2 KTU84Q: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84Q.67fdc56d.zip
Thanks @pppp6071
5.0 LRX21O-from-4.4.4 KTU84P: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip
Thanks @saberdragon18
4.4.4-KTU84P-from-4.4.3-KTU84M:[/COLOR][/B] http://android.clients.google.com/p...ed-hammerhead-KTU84P-from-KTU84M.c08cce45.zip Thanks @sucro
http://forum.xda-developers.com/showpost.php?p=46289250&postcount=1 Thanks @oldblue910
These are the most common scenarios. If you aren't sure where you fit, feel free to ask.
NOTE: Starting with Android 5.0 (LRX21O) you MUST sideload the OTA in a STOCK RECOVERY. No exceptions.
Scenario #1
You are completely stock. Unlocked/locked bootloader. No root permissions.
Continue to Section A
Scenario #2
You are stock, with root. Custom Recovery without any modifications or deletions.
Continue to Section B
Scenario #3
You are stock, with Xposed Framework installed.
Continue to Section C
Scenario #4
You are stock, with a custom kernel and/or old radio and no other modifications.
Continue to Section D,1
Scenario #5
You are stock with any modifications to /system/ including removed system apk(s) and a custom kernel.
Continue to Section D,2 or See 2nd Post (Special Scenario #1) **Special Scenario #1 is not updated yet**
Scenario #6
You are running a Custom ROM
Continue to Section D,3
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. It's attached at the bottom of this. Also Starting with Android 5.0 you must sideload the OTA through a stock recovery. Custom recoveries for now will error out.
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press and hold POWER, and then press volume up and release. The menu will appear. Select “apply update from adb
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
Section B: Flashing in a Custom Recovery (TWRP- CWM)
(For Flashing 4.4.4 OTAs and Below ONLY!)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Section C: Uninstalling Xposed Framework
Use the Xposed Framework Installer to remove the framework before applying the OTA.
Go into Xposed Framework, Framework-> Uninstall (it will restore the original file "app_process") then reboot.
NOTE: If you just uninstall Xposed Framework (the app itself), even after a reboot the "app_process" file (in /system/bin) is still the modified one by Xposed Framework, the original file is not restored.
Xposed Installer and info can be found here.
Once Xposed is uninstalled; jump back up to Section A on stock recovery (5.0 and above) and Section B on custom recovery (4.4.4 and below).
Thanks @Hammer_Of_The_Gods & @C3C076
Section D: Let’s get back to stock
1) Flash the stock boot.img and/or radio.img (whatever is applicable) from the factory image using fastboot. Also flash recovery.img if updating to 5.0
Fastboot commands used in this section would be:
Code:
fastboot flash boot boot.img
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.23.img
fastboot flash recovery recovery.img
NOTE: Some custom kernels will modify files in /system/ If this is the case you will see a status 7 error and the file modified. The easiest way to fix this is to flash the system.img
2) Replace the stock kernel or .apk(s) you removed or modified.
If you don't have a backup of removed or modified apk(s) flash the system.img
Note: These must be the exact versions that shipped with the rom.
Fastboot commands used in this section would be:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
3) Flash the KOT49H stock image. Follow abaaaabbbb63's guide if you need help.
--------------------------------------------------------------------------------------------------------------------
After completing the steps needed to return to “stock” make sure you meet all the criteria at the top of the page then revert to:
Section A if you are running stock recovery.
Section B if you are running a custom recovery (for 4.4.4 OTAs and below only).
Feel free to ask any questions you may have. I’ll do my best to answer them as quickly as possible. Perhaps others may answer them as well. Please read to see if your question has been answered before asking.
FAQ
Q: When in Recovery/Bootloader the phone isn't listed in Windows Device Manager.
A: Uninstall all current N5 drivers and install the Universal Naked driver. Turn on USB Debugging in Developer Settings and boot to recovery
Q: I'm seeing a status 7 error when trying to install the OTA
A: Look at the error closely. It will describe on the file it is failing at. Post the file path so we can help resolve the issue.
Q: The ota applied successfully but I lost my custom recovery and I want to re-root. How do I get root back?
A: Flash the custom recovery of your choice in fastboot and use it to regain root permissions
Q: I've tried everything, but I'm still getting status 7 errors.
A: Unfortunately you may have to start from scratch. Follow Section C1.
Q: I flashed a .zip file that modified (insert mod here.) Will I the OTA install successfully?
A: No, any modification at all will cause the OTA to fail.
Q: Why do I get a "cannot read update.zip" error when trying to sideload?
A: If you named the file update.zip, the actual name would be update.zip.zip. Windows auto names extensions by default. That could be your problem. If not try another usb cable or a different usb port. If that still doesn't work, make sure you type exactly what you renamed the file. You may have made a typo. It is also case-sensitive.
UPDATED: 6/19/14 - Updated for KTU84P

..
Special Scenario #1
If you are running the stock ROM, rooted, with a custom kernel, and you want to retain root after the OTA; follow this great detailed walkthrough by @Lettuce!
If it helps you, make sure you thank him on the original post, located here:
http://forum.xda-developers.com/showpost.php?p=48212456&postcount=2681) downloaded factory image from https://developers.google.com/android/nexus/images#hammerhead
2) extract the tgz, the tar within that, then extract the the zip within that to get the system.img and boot.img files
3) moved these two files into the adb folder (for the fastboot/adb method)
4) download Latest SuperSU from http://download.chainfire.eu/supersu
5) put SuperSU.zip on your phone's internal storage
6) download the 4.4.1 OTA update zip from http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
7) rename it to ota.zip
8) move ota.zip onto your phone's internal storage
9) boot into bootloader
10) open command prompt from your adb folder
11) connect USB cable
12) type 'fastboot devices' to check the connection
13) type 'fastboot flash system system.img'
14) type 'fastboot flash boot boot.img'
15) use volume and power buttons to boot into recovery (TWRP)
16) install ota.zip
17) install latest SuperSu.zip
18) clear dalvik and cache
19) reboot phone​UPDATED: 1/25/15

Good job :thumbup:Nice to see you here
Sent from my NEXUS 5

Scenario #2: Will I receive a message ?
Thanks for this thread. It's just what I've been trying to figure out.
So, if I'm Scenario #2, will I received a message on the phone when the OTA is available? Can I let it download then install through TWRP ?
If I'm reading correctly, the custom recovery will not let it install automatically (and maybe I don't want it to since it could wipe out TWRP). On reboot will TWRP prompt me to root the phone (that's how I got to root the first time).

If you're rooted, but with stock ROM, do you know for sure OTA updates won't go through? Thanks.

david31262 said:
Thanks for this thread. It's just what I've been trying to figure out.
So, if I'm Scenario #2, will I received a message on the phone when the OTA is available? Can I let it download then install through TWRP ?
If I'm reading correctly, the custom recovery will not let it install automatically (and maybe I don't want it to since it could wipe out TWRP). On reboot will TWRP prompt me to root the phone (that's how I got to root the first time).
Click to expand...
Click to collapse
I believe the new versions of recovery will ask to keep the custom recovery and/or root. We'll see how the custom recoveries handle the OTA on the N5 and I'll update the post accordingly.
BirchBarlow said:
If you're rooted, but with stock ROM, do you know for sure OTA updates won't go through? Thanks.
Click to expand...
Click to collapse
It all depends on how you gained root access. If you used cf-super boot it will not go through because it modifies the kernel.
Sent from my Nexus 5 using Tapatalk

What about cf auto root? From the description it looks like that only adds the root apps and nothing else.

El Daddy said:
It all depends on how you gained root access. If you used cf-super boot it will not go through because it modifies the kernel. Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
WHen you say cf-super boot you mean installing SuperSU through TWRP right? Thanks.

Evo_Shift said:
What about cf auto root? From the description it looks like that only adds the root apps and nothing else.
Click to expand...
Click to collapse
BirchBarlow said:
WHen you say cf-super boot you mean installing SuperSU through TWRP right? Thanks.
Click to expand...
Click to collapse
Cf-auto root and super su should be fine as they don't modify the kernel.
Sent from my Nexus 5 using Tapatalk

Nice!!
Every time someone mentions me, I regret choosing this username.

abaaaabbbb63 said:
Nice!!
Every time someone mentions me, I regret choosing this username.
Click to expand...
Click to collapse
Yeah, I regretted mentioning you.
Thank you copy & paste.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Hi I would just like to confirm if the Nexus 5 is like my old HTC One in that I would receive OTA updates on a stock rom and stock recovery with a unlocked bootloader.

maxal said:
Hi I would just like to confirm if the Nexus 5 is like my old HTC One in that I would receive OTA updates on a stock rom and stock recovery with a unlocked bootloader.
Click to expand...
Click to collapse
As long as everything is stock an unlocked bootloader does not effect an OTA.
Sent from my Nexus 5 using XDA Premium 4 mobile app

El Daddy said:
Nexus 5 OTA Help-Desk​
Scenario #3
You are stock, with custom kernel, any modifications or removed system apk(s)
Continue to Section C
Scenario #4
You are running a Custom ROM
Continue to Section C
Section C: Let’s get back to stock
You have two options to do this:
Option #1 Flash the KRT16M stock image. Follow @abaaaabbbb63 guide if you need help.
If you want to keep data intact flash only the boot.img, system.img, and recovery.img (optional)
OR
Option #2 Replace the stock images or .apk(s) you removed or modified.
Note: These must be the exact versions that shipped with the rom.
Click to expand...
Click to collapse
Just to be sure, flashing only boot.img and system.img will keep my apps and all user data, correct? I can live without the center clock mod and battery % for now.

Synyster06Gates said:
Just to be sure, flashing only boot.img and system.img will keep my apps and all user data, correct? I can live without the center clock mod and battery % for now.
Click to expand...
Click to collapse
That is correct.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
That is correct.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did it... everything booted correctly, my apps and settings were still there, but for what ever reason - my APN settings will not stay. I save it, and it takes me back to an empty menu. Any ideas?

Try pressing the menu button in apn's and reset to default.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Try pressing the menu button in apn's and reset to default.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Tried that. Says it's done, nothing comes up.
I tried searching for network as well but that didn't work either. The wifi works, but no network.
I restored a backup I made last night and it still isn't working. Any ideas?
Tried to do a system wipe then restore again
E: Unable to mount '/cache'

Hmmmm. I've never heard of that issue before. I'm not sure what else to try.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Hmmmm. I've never heard of that issue before. I'm not sure what else to try.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed it. I went ahead and flashed the stock cache.img as well and all is working. Some how I guess the cache corrupted or deleted.

[Q] How to upgrade bootloader to 10.26.1.18 ?

Hi,
I bought today a 701T ww, with bootloader version 10.26.1.7.
I've been able to unlock the bootloader, root the rom, and install a custom CWM (now 6.0.4.6).
I installed the custom rom CROMi-X 6.0b2
But I'm now unable to upgrade the bootloader to 10.26.1.18.
I reverted to stock 10.27.1.7 rom thanks to the nandroid backup I made prior CROM install, I've tried downloading the official update package from Asus, which is supposed to be the only way to upgrade the bootloader. I've put the UL-K00C-WW-10.26.1.18-user.zip file on the root of a MicroSD, the tablet recognized the update file, and rebooted to install it. Problem is that, after reboot, the tablet enters in the CWM with the following error :
{
"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"
}
Off course if I try "Yes - install untrusted.zip" it doesn't rework, and the tablet reboots ....
many thanks if you can help !

Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]

berndblb said:
Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]
Click to expand...
Click to collapse
Hi Berndblb, thanks for your reply.
Toggling the signature verification didn't help, I've already tried that.
I didn't miss this, but as I've never been able to upgrade the bootloader thanks to the official update, I thought that with CROMI the bootloader would be upgraded too. I noticed that was'nt the case, that's why I restored my nandroid backup to revert to the stock 10.26.1.7.
Now I'm in 10.26.1.7, and precisely want to upgrade the bootloader to be able to install CROMI with the correct bootloader. Therefore my question.
Would a "fastboot flash boot boot.img" using the boot.img file included in the official asus 10.28.1.18 package be a good idea ?

Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:

usoska said:
Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:
Click to expand...
Click to collapse
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?

Calp said:
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?
Click to expand...
Click to collapse
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go

berndblb said:
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go
Click to expand...
Click to collapse
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!

Calp said:
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!
Click to expand...
Click to collapse
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.

berndblb said:
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.
Click to expand...
Click to collapse
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!

Calp said:
THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
You're very welcome !
That looks correct.

Calp said:
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
WooHoo! excelent. Glad you got everything all sorted out.

Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.

sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
2 days, how dare you. You should be concentrating on b4 and only b4.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
Wow, you're crazy! I really appreciate your help, mate.
For anyone else needing to do these stips, here's the download link for the stock recovery which you have to flash first: http://droidbasement.com/db-blog/?p=3210 ( i also tried a different one but only this one did work in the end)
Also, thanks a lot for the ROM, sdbags. I've been using it for a couple of hours now and it seems to work like a charm. Great work, mate!
Sent from my K00C using xda app-developers app

How can I tell which bootloader (BL) and firmware (FW) I run currently? When I hold power/volume down, the top of the screen says user BL released by "US_epad-10.26.1.7". When I boot into Android and go into settings -> about -> software, I see Build number "JSS15J.US_epad-10.26.1.18". Is the 1.18 the firmware (FW) version?
Finally, is there a way to upgrade BL/FW to ...1.18 version without using an external SD card?

US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card

Thanks. Just to verify, you don't think doing "fastboot flash boot boot.img" will work? (using boot.img from UL-K00C-US-10.26.1.18-user.zip).
Also, by SD-card method, are you talking about the rename “WW_10_26_1_18_SDupdate” to “T4_SDUPDATE.zip" process etc.? It seems that I have the US SKU, and not sure if this would work, being that it mentions WW in the file name.
Sleeepy2 said:
US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card
Click to expand...
Click to collapse

I am no expert but I am pretty sure that the fastboot method doesn't work as there have been several people with the wrong bootloader issue and and the only way to do it was with the official update.
I am not sure about using the WW file or not. I am in canada and I used the other file to update and that did the bootloader also. With the status your in now I am not sure if the US one will work or not. I would try the US one first and then if not go with the steps from pershoot
http://forum.xda-developers.com/showpost.php?p=52187532&postcount=87

Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.

MilesWilford said:
Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.
Click to expand...
Click to collapse
It's still there, try this link
http://droidbasement.com/asus/tf701t/stock/

stock rom to able update ota, for m7 unlocked

this for htc one m7 s-on international, dont know may be others too
first download odexed zip frome here >>> http://stockroms.net/file/HTCOne/rooted/4.4Sense/One_4.06.1540.2_odexed.zip
Then copy to phone to install it
You must have custum recovery twrp or clockworkmod
after you installed odexed zip Rom, in twrp will ask u install supersu to root selct dont install
and then flash stock recovery to phone in cmd fastboot on pc,and now u can update ota
i just want help those who cant update ota ,

ahmed blue said:
this for htc one m7 s-on international, dont know may be others too
first download odexed zip frome here >>> http://stockroms.net/file/HTCOne/rooted/4.4Sense/One_4.06.1540.2_odexed.zip
Then copy to phone to install it
You must have custum recovery twrp or clockworkmod
after you installed odexed zip Rom, in twrp will ask u install supersu to root selct dont install
and then flash stock recovery to phone in cmd fastboot on pc,and now u can update ota
i just want help those who cant update ota ,
Click to expand...
Click to collapse
set_metadata recursive: some changes failed
E: Error executing updater binary in zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Error flashing zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Downloaded and followed all your instructions, tried to flash using TWRP as I am having problems installing OTA on my rooted stock rom but debloated.
Any further assistance would be greatly appreciated.

Big Bread said:
set_metadata recursive: some changes failed
E: Error executing updater binary in zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Error flashing zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Downloaded and followed all your instructions, tried to flash using TWRP as I am having problems installing OTA on my rooted stock rom but debloated.
Any further assistance would be greatly appreciated.
Click to expand...
Click to collapse
Read this info on OTA: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9

Big Bread said:
set_metadata recursive: some changes failed
E: Error executing updater binary in zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Error flashing zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Downloaded and followed all your instructions, tried to flash using TWRP as I am having problems installing OTA on my rooted stock rom but debloated.
Any further assistance would be greatly appreciated.
Click to expand...
Click to collapse
try removing all the spaces from the file name .. or just rename it rom.zip

majmoz said:
Read this info on OTA: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
Click to expand...
Click to collapse
The modifications I made are mostly for battery and performance purposes:
- Disable services app to disable 73 google play store services. 3 google play services services, 6 google services framework services
- System tuner to disable some google play services receivers
- Team seven kernel to downclock cpu and gpu, hotplug e.t.c. (I have used a stock kernel reset to reset back to stock)
- TWRP (Flashed stock recovery)
- Disabled some bloatware crap preinstalled including htc weibo, google play newsstand, books, e.t.c. (Didn't delete them on titanium backup)
- Rooted (SuperSU not sure if it modified any system files)
- Unlocked bootloader
- S-On
Perhaps also some other things I have missed.
Is there anything else that might be interferring with my OTA update?
---------- Post added at 01:45 PM ---------- Previous post was at 01:02 PM ----------
clsA said:
try removing all the spaces from the file name .. or just rename it rom.zip
Click to expand...
Click to collapse
Renamed it to rom and i'm still receiving the same error notification.

Big Bread said:
The modifications I made are mostly for battery and performance purposes:
- Disable services app to disable 73 google play store services. 3 google play services services, 6 google services framework services
- System tuner to disable some google play services receivers
- Team seven kernel to downclock cpu and gpu, hotplug e.t.c. (I have used a stock kernel reset to reset back to stock)
- TWRP (Flashed stock recovery)
- Disabled some bloatware crap preinstalled including htc weibo, google play newsstand, books, e.t.c. (Didn't delete them on titanium backup)
- Rooted (SuperSU not sure if it modified any system files)
- Unlocked bootloader
- S-On
Perhaps also some other things I have missed.
Is there anything else that might be interferring with my OTA update?
---------- Post added at 01:45 PM ---------- Previous post was at 01:02 PM ----------
Renamed it to rom and i'm still receiving the same error notification.
Click to expand...
Click to collapse
just unlocking the bootloader alone will stop any OTA updates
post your fastboot getvar all so i can find the stock rom you need
also how old is you version of TWRP and adb / fastboot, if your using old versions you can have problems

clsA said:
just unlocking the bootloader alone will stop any OTA updates
post your fastboot getvar all so i can find the stock rom you need
Click to expand...
Click to collapse
{
"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 used TWRP 2.8.1.0 (I think this is the latest). Not sure how can how old the adb/fastboot is, how can i check?

Big Bread said:
I used TWRP 2.8.1.0 (I think this is the latest). Not sure how can how old the adb/fastboot is, how can i check?
Click to expand...
Click to collapse
Flash TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and push this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
adb push One_6.09.401.5_odexed.zip /sdcard
install that and you should be up and running
in the meantime you need 6.09.709.5 HTC__621 Nanadroid and stock recovery to return to stock for OTA updates
This is all i found for your phone
http://translate.google.com/transla...2014/10/sai-onem7v30-6097095.html&prev=search

clsA said:
Flash TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and push this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
adb push One_6.09.401.5_odexed.zip /sdcard
install that and you should be up and running
in the meantime you need 6.09.709.5 HTC__621 Nanadroid and stock recovery to return to stock for OTA updates
This is all i found for your phone
http://translate.google.com/transla...2014/10/sai-onem7v30-6097095.html&prev=search
Click to expand...
Click to collapse
Do you mean a current nandroid backup of the my current system or a fresh stock unmodified nandroid backup for my software number?

Big Bread said:
Do you mean a current nandroid backup of the my current system or a fresh stock unmodified nandroid backup for my software number?
Click to expand...
Click to collapse
yes that one ... unlocking the bootloader deletes the pirv-app folder you need those back

clsA said:
yes that one ... unlocking the bootloader deletes the pirv-app folder you need those back
Click to expand...
Click to collapse
Thank you for the help thus far, I initially tried to search for the nandroid backup yesterday for HTC__621 and couldn't find a specific one. Do you know of any other nandroid backup that could also work for the HTC__621 CID version?

Big Bread said:
Thank you for the help thus far, I initially tried to search for the nandroid backup yesterday for HTC__621 and couldn't find a specific one. Do you know of any other nandroid backup that could also work for the HTC__621 CID version?
Click to expand...
Click to collapse
No but you should try the Stock odex rom I posted above. It may work out fine

clsA said:
No but you should try the Stock odex rom I posted above. It may work out fine
Click to expand...
Click to collapse
Downloaded, pushed, flashed, success!
Reinstalled all those crapware apps i disabled/deleted, reinstalled stock kernel, seems to have reverted my root access somehow, but maintained my data, installed apps e.t.c.
So far, so good except the previous pending OTA notification is now saying there is no update available to be installed.
Thanks a lot for the help, much appreciated. Do you know if I will be receiving my OTA back anytime soon? lol

Big Bread said:
Downloaded, pushed, flashed, success!
Reinstalled all those crapware apps i disabled/deleted, reinstalled stock kernel, seems to have reverted my root access somehow, but maintained my data, installed apps e.t.c.
So far, so good except the previous pending OTA notification is now saying there is no update available to be installed.
Thanks a lot for the help, much appreciated. Do you know if I will be receiving my OTA back anytime soon? lol
Click to expand...
Click to collapse
hopefully your fully up to date .. only time will tell if the next OTA will work or not

clsA said:
hopefully your fully up to date .. only time will tell if the next OTA will work or not
Click to expand...
Click to collapse
When i reboot into TWRP it provides me with the opportunity to install root by installing SuperSU, would doing so affect any possibilities of installing future OTAs?

Big Bread said:
When i reboot into TWRP it provides me with the opportunity to install root by installing SuperSU, would doing so affect any possibilities of installing future OTAs?
Click to expand...
Click to collapse
Root is no problem ..TWRP is

clsA said:
Root is no problem ..TWRP is
Click to expand...
Click to collapse
Another question, I already have the OTA downloaded on my phone prior to flashing the odexed ROM. Would it be possible for me to apply the update via adb sideload? Would this be feasible regardless of the unlocked bootloader with stock rom, stock kernel and stock recovery?

Big Bread said:
Another question, I already have the OTA downloaded on my phone prior to flashing the odexed ROM. Would it be possible for me to apply the update via adb sideload? Would this be feasible regardless of the unlocked bootloader with stock rom, stock kernel and stock recovery?
Click to expand...
Click to collapse
what update ? isn't 6.09.709.5 the last version ?
but yes with s-off you can manually flash OTA.zip with a totally stock system

clsA said:
what update ? isn't 6.09.709.5 the last version ?
but yes with s-off you can manually flash OTA.zip with a totally stock system
Click to expand...
Click to collapse
My HTC One was purchase from taiwan, the latest update is 6.09.709.7, I was running 6.09.709.5 before. now with this odexed rom, it seems I have been downgraded to 6.09.401.5.
I have tried to S-OFF but my HBOOT is 1.57 and so only the firewater method could work for me, I also discovered that the firewater method won't work because my eMMC begins with 4501xxx so therefore, I'm in a position where I can't install updates or S-OFF to revert completely to stock.

Big Bread said:
My HTC One was purchase from taiwan, the latest update is 6.09.709.7, I was running 6.09.709.5 before. now with this odexed rom, it seems I have been downgraded to 6.09.401.5.
I have tried to S-OFF but my HBOOT is 1.57 and so only the firewater method could work for me, I also discovered that the firewater method won't work because my eMMC begins with 4501xxx so therefore, I'm in a position where I can't install updates or S-OFF to revert completely to stock.
Click to expand...
Click to collapse
I thought you were using this file - SAI-OneM7_v3.0 | 6.09.709.5
http://translate.google.com/transla...2014/10/sai-onem7v30-6097095.html&prev=search
it's no big deal you can flash roms your fine ...getting OTA is not everything

[TOOL][OP6T] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the OnePlus 6T's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

mauronofrio said:
This is the OnePlus 6T's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Install APKs
Uninstall APKs
Take a Screenshot
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​
Click to expand...
Click to collapse
YESSSSSSS!!!! will try that soon ))))

spaziomilano said:
YESSSSSSS!!!! will try that soon ))))
Click to expand...
Click to collapse
Waiting for a working TWRP

I mean, props to OP. The device isn't even out yet and there is still tools for it!

Nice to see! Kudos

When do you think the root is gonna be available?

pcplayer said:
When do you think the root is gonna be available?
Click to expand...
Click to collapse
It's not a problem of root, Magisk works certainly here, it's a problem of patching the boot image.
Either you wait for a TWRP port on this phone, either you want to use the hard way and patch your boot manually like it's explained here https://forum.xda-developers.com/android/software-hacking/root-recovery-root-device-magisk-t3779454
But you need a minimum experience in playing with adb and fastboot

Striatum_bdr said:
It's not a problem of root, Magisk works certainly here, it's a problem of patching the boot image.
Either you wait for a TWRP port on this phone, either you want to use the hard way and patch your boot manually like it's explained here https://forum.xda-developers.com/android/software-hacking/root-recovery-root-device-magisk-t3779454
But you need a minimum experience in playing with adb and fastboot
Click to expand...
Click to collapse
I updated the tool to automatically root 9.0.4 version

mauronofrio said:
I updated the tool to automatically root 9.0.4 version
Click to expand...
Click to collapse
Wow, this means to simplify our lifes!!
Just enable oem unlock and usb debug in settings, connect the OP 6T to pc, reboot in bootloader mode and we can unlock BL, root without adb commands.
Mauronofrio #1

awesome stuff, thanks

Getting my 6t tomorrow, will be unlocking the bootloader and will root it. Is there a official twrp for this device yet?

vineet381 said:
Getting my 6t tomorrow, will be unlocking the bootloader and will root it. Is there a official twrp for this device yet?
Click to expand...
Click to collapse
Unfortunately no

@mauronofrio what magisk's root version is pushed up from your tool? 17.1 or 17.3?

gnam said:
@mauronofrio what magisk's root version is pushed up from your tool? 17.1 or 17.3?
Click to expand...
Click to collapse
The tool will automatically flash a patched boot.img and will install the magisk manager. The boot.img is patched with magisk 17.3

Will this tool work with the TMobile version of the 6t?

mauronofrio said:
The tool will automatically flash a patched boot.img and will install the magisk manager. The boot.img is patched with magisk 17.3
Click to expand...
Click to collapse
do we need to restore stock book img before installing new OTA ?
Can we install a custom kernel through this tool currently?

Let me get this staright. I've been out the game ever since I got stuck with the T-Mobile Galaxy S7 edge. This tool will sim and bootloader unlock without having the need to wait on T-Mobile sending you the the boot loader token or even your phone isn't paid for yet to be even sim unlocked???

cultofluna said:
do we need to restore stock book img before installing new OTA ?
Can we install a custom kernel through this tool currently?
Click to expand...
Click to collapse
No, when there will be a new update you should flash the stock full rom and from magisk manager keep the root
b0ricuaguerrero said:
Let me get this staright. I've been out the game ever since I got stuck with the T-Mobile Galaxy S7 edge. This tool will sim and bootloader unlock without having the need to wait on T-Mobile sending you the the boot loader token or even your phone isn't paid for yet to be even sim unlocked???
Click to expand...
Click to collapse
ichardy said:
Will this tool work with the TMobile version of the 6t?
Click to expand...
Click to collapse
This tool actually doesn't support t-mobile version

mauronofrio said:
No, when there will be a new update you should flash the stock full rom and from magisk manager keep the root
This tool actually doesn't support t-mobile version
Click to expand...
Click to collapse
I just realized I was on the wrong forum, my apologies.
Edit: everything is different now, new layout, I'm confused I guess it's AIO now. ??*

I Made a video on how to use the tool kit
#Oneplus6T #Unlock #TWRP #Root #Easy&Simple #Toolkit Method #Under4Minutes