Database Users

[Q] lost root access

Hi, forgive me if this is a stupid question but after flashing the latest t0lte nightly I have lost root access.
How has this happened?
I've been flashing CM nightlies for weeks but fancied a change after reading up about omnirom.
Im running an international note 2 LTE using cwm, rooted with Odin.
How do I get root access back? Is it case of me having to flash via Odin again?
More than grateful for any help here!
Cheers

cbryant said:
Hi, forgive me if this is a stupid question but after flashing the latest t0lte nightly I have lost root access.
How has this happened?
I've been flashing CM nightlies for weeks but fancied a change after reading up about omnirom.
Im running an international note 2 LTE using cwm, rooted with Odin.
How do I get root access back? Is it case of me having to flash via Odin again?
More than grateful for any help here!
Cheers
Click to expand...
Click to collapse
Flash SuperSU in recovery
We haven't yet integrated SuperSU into the package itself, and fixing that has been low priority since:
1) You can't flash Omni without a custom recovery
2) If you have a custom recovery that can flash Omni, you can flash SuperSU in recovery
3) Once you've flashed SuperSU, you can go to its Settings->Custom ROM and enable the backup script

Entropy512 said:
Flash SuperSU in recovery
We haven't yet integrated SuperSU into the package itself, and fixing that has been low priority since:
1) You can't flash Omni without a custom recovery
2) If you have a custom recovery that can flash Omni, you can flash SuperSU in recovery
3) Once you've flashed SuperSU, you can go to its Settings->Custom ROM and enable the backup script
Click to expand...
Click to collapse
Ah makes sense! is the latest superSU.zip listed on XDA? I can't locate it.
Thanks for your help!!!:good:
---------- Post added at 09:57 PM ---------- Previous post was at 09:20 PM ----------
Ok, i've pulled the superSU zip from chainfire and flashed it, however it is giving me a error message.
"There is no SU binary installed and superuser cannot install it. This is a problem!"
So I am unable to run step 3
Please help :crying:
Cheers again :good:

craigbryant said:
Ah makes sense! is the latest superSU.zip listed on XDA? I can't locate it.
Thanks for your help!!!:good:
---------- Post added at 09:57 PM ---------- Previous post was at 09:20 PM ----------
Ok, i've pulled the superSU zip from chainfire and flashed it, however it is giving me a error message.
"There is no SU binary installed and superuser cannot install it. This is a problem!"
So I am unable to run step 3
Please help :crying:
Cheers again :good:
Click to expand...
Click to collapse
That's strange - 1.80 works perfectly for me.

craigbryant said:
Ah makes sense! is the latest superSU.zip listed on XDA? I can't locate it.
Thanks for your help!!!:good:
---------- Post added at 09:57 PM ---------- Previous post was at 09:20 PM ----------
Ok, i've pulled the superSU zip from chainfire and flashed it, however it is giving me a error message.
"There is no SU binary installed and superuser cannot install it. This is a problem!"
So I am unable to run step 3
Please help :crying:
Cheers again :good:
Click to expand...
Click to collapse
Yesssssss.
Ok I got there in the end, grabbed Chainfire's latest SU from his G+ page (ver1.80)
Flashed this version and it allowed me to access settings and in turn run the backup script
Thank you so much for your help, much appreciated

I came right thankyou!
Sent from my GT-I9295 using XDA Premium 4 mobile app

[ROM][FACTORY-OTA][4.3][Nvidia Tegra Note 7][zip]

Hi here is the download link to the OTA Android 4.3 zip file for Nvidia Tegra Note 7
Fully factory, not modified... (NO SuperSU, Root, Busybox included, pulled stock OTA from device)
For Root download and install SuperSU from chainfire website and install zip straight after installing FACTORY OTA ROM
NOTE: I AM NOT RESPONSIBLE IF YOU DAMAGE YOU DEVICE SOFTBRICK, HARDBRICK OR YOUR DEVICE FLYIN OUT YOUR WINDOW!
Clockworkmod found here - http://forum.xda-developers.com/showthread.php?p=48866275#post48866275
Download link flashable zip via Clockworkmod:
Devhost - Temp removed
Enoy!

How do you flash it? Prerequisites?

lalitindoria said:
How do you flash it? Prerequisites?
Click to expand...
Click to collapse
Do not Download, updating OP with flashable ZIP via clockworkmod and YOU WONT HAVE ROOT SUPERSU OR BUSYBOX keep that in mind its totally factory pulled ota, just modified to make it flashable via CWM...
Recovery can be found here... - http://forum.xda-developers.com/showthread.php?p=48866275#post48866275

CWM requires root, how can one update to 4.3 without root access?

lalitindoria said:
CWM requires root, how can one update to 4.3 without root access?
Click to expand...
Click to collapse
1. unlock bootloader
2. flash supersu.zip
3. flash recovery
4. flash OTA.zip
5. flash supersu.zip
= 4.3 rooted
OP Updated with flashable 4.3 OTA FACTORY ZIP via Clockworkmod...
Enjoy!!
Edit: Temporary removed download link until further testing.... thank you for your patience

Shaky156 said:
1. unlock bootloader
2. flash supersu.zip
3. flash recovery
4. flash OTA.zip
5. flash supersu.zip
= 4.3 rooted
OP Updated with flashable 4.3 OTA FACTORY ZIP via Clockworkmod...
Enjoy!!
Click to expand...
Click to collapse
Hi,
Tried installing it in recovery but got error message that says ""Error in /data/media/0/tegranote_7...zip (Status 7) Installation aborted."
Wonder what went wrong?
Updated:
Okay, Didn't get to see the edit. Will wait.
---------- Post added at 10:01 PM ---------- Previous post was at 09:49 PM ----------
Shaky156 said:
1. unlock bootloader
2. flash supersu.zip
3. flash recovery
4. flash OTA.zip
5. flash supersu.zip
= 4.3 rooted
OP Updated with flashable 4.3 OTA FACTORY ZIP via Clockworkmod...
Enjoy!!
Edit: Temporary removed download link until further testing.... thank you for your patience
Click to expand...
Click to collapse
Got into an endless boot loop. What shall I do to get out of it?
---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------
Shaky156 said:
!
Edit: Temporary removed download link until further testing.... thank you for your patience
Click to expand...
Click to collapse
Got into an endless boot loop. What shall I do to get out of it? I still have access to recovery and fastboot modes.

Freeje said:
Hi,
Tried installing it in recovery but got error message that says ""Error in /data/media/0/tegranote_7...zip (Status 7) Installation aborted."
Wonder what went wrong?
Updated:
Okay, Didn't get to see the edit. Will wait.
---------- Post added at 10:01 PM ---------- Previous post was at 09:49 PM ----------
Got into an endless boot loop. What shall I do to get out of it?
---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------
Got into an endless boot loop. What shall I do to get out of it? I still have access to recovery and fastboot modes.
Click to expand...
Click to collapse
for now restore your backup
Nvidias OTA flashable zip seems to have a few errors which I'll need to take a look at which I am doing so now

Okay successfully installed OTA android 4.3 with ROOT and CWM preserved no overriding of stock recovery update will arrive soon then I shall rest
Edit: whoops dont flash rom and kernel without updating binaryblob, touchscreen not working...

Working on apx nvflash mode to fix my device if successfull will create a thread and procedure on how to unbrick devices

Is it possible to ROOT TN7 without unlocking bootloader? After OTA update to JB 4.3 I've lost ROOT.
Unfortunately NVIDIA decide to lock boot ...

Phenomeno said:
Is it possible to ROOT TN7 without unlocking bootloader? After OTA update to JB 4.3 I've lost ROOT.
Unfortunately NVIDIA decide to lock boot ...
Click to expand...
Click to collapse
If you can boot into the recover can't you issue;
adb oem unlock

Shaky156 said:
for now restore your backup
Nvidias OTA flashable zip seems to have a few errors which I'll need to take a look at which I am doing so now
Click to expand...
Click to collapse
Was able to get the tablet working by flashing a boot image. Now I'm back to square one. No root and still waiting /looking for a way to flash the new ROM from EVGA.

Freeje said:
Was able to get the tablet working by flashing a boot image. Now I'm back to square one. No root and still waiting /looking for a way to flash the new ROM from EVGA.
Click to expand...
Click to collapse
Flash supersu to get root, i have 4.3 rooted zip but wont release until ive unbricked my device and tested myself, incase same thing happens to other e.g. touchscreen not working (cause i didnt flash the nvblob which is very important, i can release with a disclaimer but nah not risking it)

Phenomeno said:
Is it possible to ROOT TN7 without unlocking bootloader? After OTA update to JB 4.3 I've lost ROOT.
Unfortunately NVIDIA decide to lock boot ...
Click to expand...
Click to collapse
Enable debugging
Adb reboot bootloader
Fastboot oem unlock

Shaky156 said:
Enable debugging
Adb reboot bootloader
Fastboot oem unlock
Click to expand...
Click to collapse
Thank you but I don't want to void my warranty unlocking bootloader that's why I asked how to root without it...
In my opinion it's not fair selling device without unlock and then put lock on it.

Phenomeno said:
Thank you but I don't want to void my warranty unlocking bootloader that's why I asked how to root without it...
In my opinion it's not fair selling device without unlock and then put lock on it.
Click to expand...
Click to collapse
We are lucky to recieve devices with an unlocked bootloader without having void warranty etc, either void warranty and get custom optimizrd stuff or not void warranty and stay on stock, sorry bud cant help much

Could you please update the OP for android 4.4?

I also received here in India. I was on stock, unrooted device. I have captured the OTA. The file name is tegra_note_7_system_update_3.0__5.1.zip and is 446 mb.

Got stuck trying to root, just want to return to stock/factory settings.

I'm new so please forgive me and my ignorance through all of this. I had a great root experience with my old LG G3, so when I got my Axon 7 (A2017U) I thought I'd try to root it too. I tried to follow DrakenFX's guide (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204) but I bit off more than I could chew. I got to the point where I had TWRP up, but this is where I think things started to fall apart. I was confused by the instructions and in a haste I continued anyway. In TWRP I went to Wipe>Format Data typed in yes like TWRP said and boom, I had no idea what happened. Rebooting only got a screen that said "Type in your password" but my passcode I had on the phone before it bricked didn't work. So by now I start panicking a bit. I thought I made a mistake earlier so I went back and tried to reinstall TWRP by putting the phone into EDL. The phone got stuck that way for a while, but I now I have it in TWRP. Right now, I just want to get back to safe stock android.
I'm 200% sure I messed with something I wasn't supposed to and I believe that is the system image(?)which Draken also linked (http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53). I'm downloading it as I type. I'm going to do my best to leave my phone just like it is right now, in TWRP, and wait for more advice on this before I do anything else.. What I'm curious about is where did I go wrong and what do I need to do to get my phone working again, preferably without returning it? Thank you for any advice you have to offer.
Update: It's worth noting I didn't know to enable OEM Unlocking when I was in stock android. Dumb move I know. I'm new here.

What software version are u on?

xiong77 said:
What software version are u on?
Click to expand...
Click to collapse
As far as I know I (was) on Android 6.0 A2017U B29. TWRP version 3.0.2-0

Get DrakenFX b29 mergeboot stack and b29 stock system and flash it then u should be OK. I did this too.

xiong77 said:
Get DrakenFX b29 mergeboot stack and b29 stock system and flash it then u should be OK. I did this too.
Click to expand...
Click to collapse
I tried, but the downloads take extremely long and are unreliable for me. I was downloading the stock system file at around 14 kbps and it eventually failed. Any other suggestions?

Wipe cache dalvik data and system reboot, ignore error message and reboot
---------- Post added at 06:54 AM ---------- Previous post was at 06:53 AM ----------
Try through ur computer
---------- Post added at 06:57 AM ---------- Previous post was at 06:54 AM ----------
Try go back to twrp and wipe like the op said

xiong77 said:
Wipe cache dalvik data and system reboot, ignore error message and reboot
---------- Post added at 06:54 AM ---------- Previous post was at 06:53 AM ----------
Try through ur computer
---------- Post added at 06:57 AM ---------- Previous post was at 06:54 AM ----------
Try go back to twrp and wipe like the op said
Click to expand...
Click to collapse
I've done the wipes multiple times. It's mostly the downloads I'm having trouble with. How and where do you get them? The links I found were dead or had a slow speed.

video_dewd said:
I've done the wipes multiple times. It's mostly the downloads I'm having trouble with. How and where do you get them? The links I found were dead or had a slow speed.
Click to expand...
Click to collapse
Did you save the recovery backup? If you did then use the axon7root.exe to flash the stock recovery. Then download the stock B20 from ZTE.

tabletalker7 said:
Did you save the recovery backup? If you did then use the axon7root.exe to flash the stock recovery. Then download the stock B20 from ZTE.
Click to expand...
Click to collapse
I've been able to find some recovery images that I found on other threads. The thing is, when I try to flash them on TWRP, I get an error about "/dev/block/sde14" being read-only.

video_dewd said:
I've been able to find some recovery images that I found on other threads. The thing is, when I try to flash them on TWRP, I get an error about "/dev/block/sde14" being read-only.
Click to expand...
Click to collapse
no no no no ..................... put phone in EDL mode. Copy the stock image into the folder with the axon7root.exe file you used to flash TWRP. Make sure the stock file is named recovery.img (or whatever the TWRP file is named in that folder, it has been a long time since I did this). Then use the axon7root.exe program the exact same way you did before. It will flash the stock recovery. Then in stock recovery you can flash the B20 from ZTE

tabletalker7 said:
no no no no ..................... put phone in EDL mode. Copy the stock image into the folder with the axon7root.exe file you used to flash TWRP. Make sure the stock file is named recovery.img (or whatever the TWRP file is named in that folder, it has been a long time since I did this). Then use the axon7root.exe program the exact same way you did before. It will flash the stock recovery. Then in stock recovery you can flash the B20 from ZTE
Click to expand...
Click to collapse
Ok, I will try this.
Update: I got the stock recovery back, but now I'm lost as to how to flash the stock b20 from zte. Thank you for all your help so far though.

video_dewd said:
Ok, I will try this.
Click to expand...
Click to collapse
got stock recovery working?

tabletalker7 said:
got stock recovery working?
Click to expand...
Click to collapse
Yes, I'm in the process of getting the update from sdcard feature working.
Update: Trying to use the update.zip file or unpacking it into the sdcard hasn't worked. Trying to use adb sideload returns "Cannot read 'update.zip'"

video_dewd said:
Yes, I'm in the process of getting the update from sdcard feature working.
Click to expand...
Click to collapse
ok - download it from zte. Put it on your SD card. In recovery select update from SD card. Be warned it will work but it is slow. Also note that while I will not say the bootloader unlock doesn't work on B29, I can say it worked flawlessly on B20. If you want unlocked I recommend doing so on B20.

tabletalker7 said:
ok - download it from zte. Put it on your SD card. In recovery select update from SD card. Be warned it will work but it is slow. Also note that while I will not say the bootloader unlock doesn't work on B29, I can say it worked flawlessly on B20. If you want unlocked I recommend doing so on B20.
Click to expand...
Click to collapse
I have the zip but it says, "Sorry,you can't sdcard upgrade".

video_dewd said:
I have the zip but it says, "Sorry,you can't sdcard upgrade".
Click to expand...
Click to collapse
try using adb sideload
---------- Post added at 07:48 AM ---------- Previous post was at 07:45 AM ----------
also people reportd sucess on the z-communities by placing the B20 on the internal sd card (phone storage)

tabletalker7 said:
try using adb sideload
---------- Post added at 07:48 AM ---------- Previous post was at 07:45 AM ----------
also people reportd sucess on the z-communities by placing the B20 on the internal sd card (phone storage)
Click to expand...
Click to collapse
I tried that. It won't accept the zip file and it's unclear which file to sideload. Would you happen to know? This is what files are in the unpacked zip. https://gyazo.com/c7546c3ed0dcb0972653eaeba42fcb40

video_dewd said:
I tried that. It won't accept the zip file and it's unclear which file to sideload. Would you happen to know? This is what files are in the unpacked zip. https://gyazo.com/c7546c3ed0dcb0972653eaeba42fcb40
Click to expand...
Click to collapse
Maybe - I'd have to download it to find out. If you can't get stock recovery to take it this post http://forum.xda-developers.com/showpost.php?p=69434328&postcount=17 gives you instructions on what lines to remove from the updater-script to make it flash in TWRP (I didn't have a problem making the stock B20 go in stock recovery, but I was unlocked at the time). You could reflash TWRP and try that.
Or just try this in TWRP http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2

tabletalker7 said:
Maybe - I'd have to download it to find out. If you can't get stock recovery to take it this post http://forum.xda-developers.com/showpost.php?p=69434328&postcount=17 gives you instructions on what lines to remove from the updater-script to make it flash in TWRP (I didn't have a problem making the stock B20 go in stock recovery, but I was unlocked at the time). You could reflash TWRP and try that.
Or just try this in TWRP http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Click to expand...
Click to collapse
I'm going to try the first option. The second option's link take horrendously long to download.
Update: Trying to flash from TWRP results in error "Could not find 'META-INF/com/google/android/update-binary' which makes no sense since update binary is exactly where it should be.
Further Update: It seems that the problem might have been that when I compressed "update.zip" to fix "updater-script" it changed to file path by adding the title of the folder "update" to the beginning. I think that messed with the path giving the the meta-inf error.

video_dewd said:
I'm going to try the first option. The second option's link take horrendously long to download.
Update: Trying to flash from TWRP results in error "Could not find 'META-INF/com/google/android/update-binary' which makes no sense since update binary is exactly where it should be.
Click to expand...
Click to collapse
OK. How did you do that?
---------- Post added at 10:09 AM ---------- Previous post was at 09:54 AM ----------
Just suck it up and download the 2 b29 files. If it is that slow pick a different mirror

got and downloaded security update

hi all
im running rooted stock rom, and received the security update, but when im trying to install , phone boots to twrp.
now phone keeps rebooting ' how do i stop this?
is there a way i can install it via twrp, or only when a zip file will come up, i will be able to update?
thx in advance for helping

I'm in the same boat. I knew not to let it. My wife had my phone and thought she was helping. It's looking for the stock release keys. It generates a log file in /system/tmp
From what I can recall, stock recovery has to be reflashed. I just need to kill the forced reboot so I can use the phone temporarily.

I was stupid enough not to backup before trying to update..
Is there a way to flash this thing?

Use TWRP to wipe cache. That will delete the OTA file and break the bootloop.

the-light said:
I was stupid enough not to backup before trying to update..
Is there a way to flash this thing?
Click to expand...
Click to collapse
Yeah, go back to stock...
OTA updates are only for a pure stock device... No TWRP, no root, no Xposed, nothing, must be ABSOLUTELY stock or it will/can fail.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
jason2678 said:
Use TWRP to wipe cache. That will delete the OTA file and break the bootloop.
Click to expand...
Click to collapse
Yes, exactly... And I would also recommend disabling the notification in system app Motorola Update Services so you are no longer nagged about the update.

acejavelin said:
Yeah, go back to stock...
OTA updates are only for a pure stock device... No TWRP, no root, no Xposed, nothing, must be ABSOLUTELY stock or it will/can fail.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
Yes, exactly... And I would also recommend disabling the system app Motorola Update Services so you are no longer nagged about the update.
Click to expand...
Click to collapse
will do that
thanks for the help

i went the systemless root method, thinking i would be able to update via ota's, guess not. however, clearing the cache did stop the reboot loop, thanks!

[Tutorial][OOS]Proper Way to Update OOS Through OTA on Rooted OnePlus 3/3T

This is what I found accidentally by myself. There is actually an easy way to flash the OTA update if you are too lazy to find a download link for the zip file(like me).
Required: TWRP(Always use the latest version to avoid problems), Any file manager
1. Download the update in settings through OTA. (Make sure full zip file is downloaded which normally exceeds 1GB.)
2. After finishing the download, open your file manager and enable the Show Hidden Files function.
3. Go to Internal Storage and find the folder named .Ota then copy the zip file to any directory you like.(Visible one which is not hidden.)
4. Reboot to TWRP and flash the zip file you downloaded, Magisk/SuperSU and other mods you like.
5. Wipe Dalvik and Cache
6. Reboot
7. Enjoy the update.
Ps: You should root your device before rebooting to prevent the TWRP from getting overwritten by stock recovery.

Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct? I guess that could be the blah blah blah part of Step 4

counterfeit187 said:
Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct? I guess that could be the blah blah blah part of Step 4
Click to expand...
Click to collapse
No, TWRP remains. Flash the full rom, flash magisk/su and reboot to recovery then to system.
And isn't this the simple basic procedure to flash the rom on a rooted device(?) I wonder how to used to do it before and also that you can find the latest rom update on downloads.oneplus.net - can't you?
Plus won't this trigger dm verity and encryption? Because I usually wait for the modified boot.img for the latest update which disables dm verity and forced encryption.

DawoodSahi said:
No, TWRP remains. Flash the full rom, flash magisk/su and reboot to recovery then to system.
And isn't this the simple basic procedure to flash the rom on a rooted device(?) I wonder how to used to do it before and also that you can find the latest rom update on downloads.oneplus.net - can't you?
Plus won't this trigger dm verity and encryption? Because I usually wait for the modified boot.img for the latest update which disables dm verity and forced encryption.
Click to expand...
Click to collapse
The DM Verity is usually okay because of magisk patching the boot image

counterfeit187 said:
The DM Verity is usually okay because of magisk patching the boot image
Click to expand...
Click to collapse
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?

DawoodSahi said:
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?
Click to expand...
Click to collapse
Yes, usually. Just make sure you don't let it reboot before you flash magisk or SuperSU

what if we have flashed a kernel?

DawoodSahi said:
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?
Click to expand...
Click to collapse
Yes, what @counterfeit187 said was right. I have personally tried it last night by flashing only magisk after the update and after the bootup my device is still unencrypted.
Ramith96 said:
what if we have flashed a kernel?
Click to expand...
Click to collapse
You mean you're currently on a custom kernel? If so just follow the exact procedures and flash back your kernel which is the "blablabla" in the instruction.

Diatomix98 said:
Yes, what @counterfeit187 said was right. I have personally tried it last night by flashing only magisk after the update and after the bootup my device is still unencrypted.
Click to expand...
Click to collapse
Yup I updated last night, just flashing the open beta 14 zip and magisk in TWRP before reboot.

counterfeit187 said:
Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct?
Click to expand...
Click to collapse
If you root before rebooting (after flashing the full update zip), TWRP will remain. If you don't root, it will overwrite TWRP with stock recovery.
The whole process is already described (and in better detail) here: https://forum.xda-developers.com/showpost.php?p=70084260&postcount=3
Although admittedly, the info is not that obvious to find.
---------- Post added at 11:48 AM ---------- Previous post was at 11:44 AM ----------
Diatomix98 said:
This is what I found accidentally by myself. It's been told countless time that we should not update through OTA if our phone is rooted which will most probably brick the phone. However there is actually an easy way to flash the OTA update
Click to expand...
Click to collapse
What is meant by this (the sentence I've highlighted in red font), is if you try to flash the "partial" or "patch" OTA (less than 1 GB), it will soft brick the phone (fixable if you flash the full update zip). Therefore, rooted and/or TWRP users should only flash the "full" update zip (> 1 GB).
If you get the update notification, the system should detect you have TWRP, and download only the full zip.
---------- Post added at 11:57 AM ---------- Previous post was at 11:48 AM ----------
Diatomix98 said:
If so just follow the exact procedures and flash back your kernel which is the "blablabla" in the instruction.
Click to expand...
Click to collapse
It's completely unclear what is meant by "blablabla"
If the intent is to post a useful tutorial, the steps should be clear for everyone.

When we flash again doesn't it replace the twrp with the stock recovery?

redpoint73 said:
What is meant by this (the sentence I've highlighted in red font), is if you try to flash the "partial" or "patch" OTA (less than 1 GB), it will soft brick the phone (fixable if you flash the full update zip). Therefore, rooted and/or TWRP users should only flash the "full" update zip (> 1 GB).
If you get the update notification, the system should detect you have TWRP, and download only the full zip.
---------- Post added at 11:57 AM ---------- Previous post was at 11:48 AM ----------
It's completely unclear what is meant by "blablabla"
If the intent is to post a useful tutorial, the steps should be clear for everyone.
Click to expand...
Click to collapse
Yep, you are right it was a misunderstanding as I have been reading quite some posts mentioning how their phones got bricked when updating through OTA. I should have understood the whole situation better, my bad here. That "blablabla" actually means other mods that we are flashing along like Arise Sound and etc which are neither important nor will they affect the update. Anyway, I am going to edit the op. Thanks for the advic though.

Ramith96 said:
When we flash again doesn't it replace the twrp with the stock recovery?
Click to expand...
Click to collapse
If by "it" you mean the recovery, then as it was mentioned a few posts earlier, NO, TWRP remains.
Unleashed by ONEPLUS 3T rooted

Diatomix98 said:
Yep, you are right it was a misunderstanding as I have been reading quite some posts mentioning how their phones got bricked when updating through OTA. I should have understood the whole situation better, my bad here.
Click to expand...
Click to collapse
No worries. I understand the confusion, as I agree the info in some threads isn't specific enough.
Diatomix98 said:
That "blablabla" actually means other mods that we are flashing along like Arise Sound and etc which are neither important nor will they affect the update. Anyway, I am going to edit the op. Thanks for the advic though.
Click to expand...
Click to collapse
You're certainly welcome. Again, your tutorial will most certainly be useful to a lot of folks; as it will make the info easier to find. So having the best info (and easy to understand) is good all around. :good:
---------- Post added at 08:57 AM ---------- Previous post was at 08:55 AM ----------
Ramith96 said:
When we flash again doesn't it replace the twrp with the stock recovery?
Click to expand...
Click to collapse
Already answered a couple times in this thread.
If you update and immediately root, TWRP will remain.
If you update, and don't root, then yes TWRP may be replaced with stock recovery.

failed
I tried that exact procedure but couldn't get past the boot animation for about half an hour so reverted back to the nandroid backup.
Note: I have the latest twrp and it worked on previous update but couldn't execute this time.

thesishir said:
I tried that exact procedure but couldn't get past the boot animation for about half an hour so reverted back to the nandroid backup.
Note: I have the latest twrp and it worked on previous update but couldn't execute this time.
Click to expand...
Click to collapse
Did you verify the downloaded update file was larger than 1 GB?

redpoint73 said:
Did you verify the downloaded update file was larger than 1 GB?
Click to expand...
Click to collapse
Yes I did! The file size is 1.43 gb to be exact but still no luck

thesishir said:
Yes I did! The file size is 1.43 gb to be exact but still no luck
Click to expand...
Click to collapse
Not sure why it's not booting. But you might try to download the full update again, and install in TWRP (wipe Dalvik and cache, then flash): http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/

redpoint73 said:
Not sure why it's not booting. But you might try to download the full update again, and install in TWRP (wipe Dalvik and cache, then flash): http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
Click to expand...
Click to collapse
I have tried it several times with official downlaod provided by my phone and also with official op website but it tries to boot and freezes at the boot logo (the one where two dots follow each other) so I am here at last in a hope to fix this.

thesishir said:
I have tried it several times with official downlaod provided by my phone and also with official op website but it tries to boot and freezes at the boot logo (the one where two dots follow each other) so I am here at last in a hope to fix this.
Click to expand...
Click to collapse
Only other think I can think of, is to do a full wipe (data, Dalvik, cache - the default wipe in TWRP). But you may not like that.
Or make sure you are on latest TWRP 3.1.1-2, or reflash TWRP.