Database Users

[Q] Android 4.4 OTA fails on Status 7 system bin debuggerd

I am currently running Nexus 7 (2012) Wifi Android 4.3 Build JWR66Y rooted with CWM and stick mount but when I try to update Android 4.4 OTA it fails on status 7 system bin debuggered. As I was able to just run the Android 4.3 OTA when I upgraded from Android 4.2.2 without any problems this Android 4.4 update is certainly very frustrating. Since I am still a newbie at this could you please provide a step by step of how to get this to work using NRT? Do you have to unroot before installing the update and then reinstall all your apps after? Any help would be greatly appreciated.
Thanks,
KodachromeBob

I'm in the same boat. Trying not to have to start from scratch so I really prefer to run the update instead of flashing the entire device. Vague recollection was that debuggerd gets replaced by stickmount but I tried reverting to the backup file that I had and it still gave me the same (Status 7) error.
I think we just have to find the correct version of debuggerd and overwrite it, then sideload. Let me know if you make any progress.

If I remember correctly you have to be completely stock. If you changed anything the update will not work.
Sent from my HTC6500LVW using Tapatalk

skiman10 said:
If I remember correctly you have to be completely stock. If you changed anything the update will not work.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
It's only aborting on that one file as far as I can tell. Would love to get an original copy and just overwrite the one that's on my Nexus 7 to try if it would work.
Is there a way to get back to stock but not lose all the installed apps and data? I don't mind not using the update file, I just do not want to go through the hassle of setting everything back up (reloading apps, wifi, etc.) again.

Wayno-san said:
It's only aborting on that one file as far as I can tell. Would love to get an original copy and just overwrite the one that's on my Nexus 7 to try if it would work.
Is there a way to get back to stock but not lose all the installed apps and data? I don't mind not using the update file, I just do not want to go through the hassle of setting everything back up (reloading apps, wifi, etc.) again.
Click to expand...
Click to collapse
Is there anything you changed when you were messing around with it? Like adding the stock browser or flash? Something like that...
Sent from my HTC6500LVW using Tapatalk

skiman10 said:
Is there anything you changed when you were messing around with it? Like adding the stock browser or flash? Something like that...
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
No, I just recall having to change the debuggerd file to get stickmount to work. I don't remember the details exactly (it was a long time ago) but I'm pretty sure that is all it was.

Wayno-san said:
No, I just recall having to change the debuggerd file to get stickmount to work. I don't remember the details exactly (it was a long time ago) but I'm pretty sure that is all it was.
Click to expand...
Click to collapse
Sorry then I can't help you. I would titanium backup and go completely stock or flash or something. Hope you get it worked out buddy.
Sent from my HTC6500LVW using Tapatalk

skiman10 said:
Sorry then I can't help you. I would titanium backup and go completely stock or flash or something. Hope you get it worked out buddy.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
No worries. I just found another post (sucks that search is down) that says that if we just flash the boot, system, and bootload img files from KK that it should update without deleting programs or data... I think I'll give that a try.
---------- Post added at 02:42 PM ---------- Previous post was at 02:10 PM ----------
Apparently I flashed in the incorrect order and just flashed boot and system. Nexus 7 appears to have booted up and my apps/data are still present. About screen shows
Android: 4.4
Kernel version: 3.1.10-gee1a0b2
Build: KRT16S
Do I still need to flash bootloader?
---------- Post added at 03:13 PM ---------- Previous post was at 02:42 PM ----------
KodachromeBob said:
I am currently running Nexus 7 (2012) Wifi Android 4.3 Build JWR66Y rooted with CWM and stick mount but when I try to update Android 4.4 OTA it fails on status 7 system bin debuggered. As I was able to just run the Android 4.3 OTA when I upgraded from Android 4.2.2 without any problems this Android 4.4 update is certainly very frustrating. Since I am still a newbie at this could you please provide a step by step of how to get this to work using NRT? Do you have to unroot before installing the update and then reinstall all your apps after? Any help would be greatly appreciated.
Thanks,
KodachromeBob
Click to expand...
Click to collapse
The method of flashing boot, bootloader, and system img seems to have worked. Might want to give that a shot if no one uploads the proper debuggerd file. Best of luck!

Step by Step Required For This Noob PLEASE
Wayno-san said:
No worries. I just found another post (sucks that search is down) that says that if we just flash the boot, system, and bootload img files from KK that it should update without deleting programs or data... I think I'll give that a try.
---------- Post added at 02:42 PM ---------- Previous post was at 02:10 PM ----------
Apparently I flashed in the incorrect order and just flashed boot and system. Nexus 7 appears to have booted up and my apps/data are still present. About screen shows
Android: 4.4
Kernel version: 3.1.10-gee1a0b2
Build: KRT16S
Do I still need to flash bootloader?
---------- Post added at 03:13 PM ---------- Previous post was at 02:42 PM ----------
The method of flashing boot, bootloader, and system img seems to have worked. Might want to give that a shot if no one uploads the proper debuggerd file. Best of luck![/Q
Did you use NRT to accomplish this and would you mind providing the step by step procedure and files that made this successful for you? Being new at this I just don't want to screw it up.
Thanks in advance
KodachromeBob
Click to expand...
Click to collapse

KodachromeBob said:
Did you use NRT to accomplish this and would you mind providing the step by step procedure and files that made this successful for you? Being new at this I just don't want to screw it up.
Thanks in advance
KodachromeBob
Click to expand...
Click to collapse
Yes, just download the 4.4 image from google here:
https://dl.google.com/dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
Unzip it until you can pull out the 3 image files I mentioned above. Then use NRT to Flash the files one at a time. You should be good to go. (fingers crossed)

Yesterday my nexus downloaded the update and asked me to press 'ok' to shut down tablet and install.
Just like after every system update the following happend:
Nexus turns off
... thats it, it simply turns off and nothing happens! Device is 2 weeks old now and i am thinking of returning it.
I'm on 4.3 and system tells me that there is no update available...
Nexus 7 2013 sucks!
Sent from my XT910 using xda app-developers app

Wayno-san said:
Yes, just download the 4.4 image from google here:
https://dl.google.com/dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
Unzip it until you can pull out the 3 image files I mentioned above. Then use NRT to Flash the files one at a time. You should be good to go. (fingers crossed)
Click to expand...
Click to collapse
Yes, you have to unzip the .tgz file, then unzip the .tar file to get the folder with the image files. 7zip works great. If you are on the stock rom/kernel rooted with a custom recovery (CWM or TWRP) you can fastboot flash on both the system.img and boot.img. Those are the only ones you need. It doesn't look for file verifications in system, it just puts the latest system image there. Flash the latest supersu in custom recovery and you get back root.

Successfully Updated to KRT16S
Could not have done it without the help of Wayno-san. I flashed Boot, Boot Loader and System images with NRT and voila a successful update to KRT16S. I had to ROOT again and reinstall Busy Box but that was not a problem. Thanks again Wayno--san for all your support.
KodachromeBob

My nexus does not even have the Option to start in bootmenue.
As i told, this tablet sucks.
Sent from my XT910 using xda app-developers app

KodachromeBob said:
Could not have done it without the help of Wayno-san. I flashed Boot, Boot Loader and System images with NRT and voila a successful update to KRT16S. I had to ROOT again and reinstall Busy Box but that was not a problem. Thanks again Wayno--san for all your support.
KodachromeBob
Click to expand...
Click to collapse
You're welcome Sir!

Can anyone send me the JWR66Y debuggerd?
I'm also stuck trying to update to 4.4 and I'm hoping to avoid reflashing back to the stock /system. I've reverted all of the system files I touched so it's only debuggerd that's holding up the update. Thanks!
--
kcc

I also had to update manually because of Status 7 update in CWM during OTA flash. Slight inconvenience yes, but nothing major as I didn't flash "Data" via Fastboot command. Had all my apps retained in the next boot
Missing ART though. I don't really want to flash a custom ROM for it.

Anyone willing to send me the KRT16S debuggerd?
If no one has the JWR66Y version, I can just edit the install script to not check (and not patch) debuggerd, then load the KRT16S debuggerd after the update completes. Thanks!
--
kcc

Lollipop Root Achieved

And HERE it Is!!!! I'm too tired to make a long thread.. I need to sleep hahah I'll make a proper thread tomorrow if he doesn't..
quickist way... be bootloader unlocked and then boot the image in the image folder of the zip
Unzip the zip to your computer.
fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
Make sure it's fastboot boot.. not fastboot flash.
It will reboot, reboot again and then you're good
Now go buy chainfire a beer
http://download.chainfire.eu/596/CF-Root/CF-Auto-Root/CF-Auto-Root-victara-victaratmo-xt1095.zip
This is not a flashable zip

What state does the phone have to be in to fastboot? I get waiting for device in normal phone OS and in recovery.
I can adb reboot to recovery, so I know everything is set up PC wise.
From bootloader I get "cannot load _______.img : no error"
---------- Post added at 01:10 PM ---------- Previous post was at 01:04 PM ----------
Got it I think. Your command in the OP has it ending in .img not .zip
EDIT....still getting binary not installed. I've got to go to work, but idk why this is the first phone I've ever struggled with so many things. Could be because we still don't have ANY working official images.
---------- Post added at 01:13 PM ---------- Previous post was at 01:10 PM ----------
Got it. Had to unzip the file and flash the image like you said.... I read wrong my bad.
Thanks

graffixnyc said:
And HERE it Is!!!! I'm too tired to make a long thread.. I need to sleep hahah I'll make a proper thread tomorrow if he doesn't..
quickist way... be bootloader unlocked and then boot the image in the image folder of the zip
Unzip the zip to your computer.
fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
Make sure it's fastboot boot.. not fastboot flash.
It will reboot, reboot again and then you're good
Now go buy chainfire a beer
http://download.chainfire.eu/596/CF-Root/CF-Auto-Root/CF-Auto-Root-victara-victaratmo-xt1095.zip
This is not a flashable zip
Click to expand...
Click to collapse
Is the boot.img for Lollipop based on the .5 or .6 release?

BrokenWall said:
Is the boot.img for Lollipop based on the .5 or .6 release?
Click to expand...
Click to collapse
It's boot img agnostic.. meaning you boot this boot.img, it actually takes the current boot.img on the device and injects root into it. So it uses whatever boot.img is currently on the device. So if you are on the .5 kernel it should work, if you're on the .6 kernel it works

graffixnyc said:
It's boot img agnostic.. meaning you boot this boot.img, it actually takes the current boot.img on the device and injects root into it. So it uses whatever boot.img is currently on the device. So if you are on the .5 kernel it should work, if you're on the .6 kernel it works
Click to expand...
Click to collapse
Awesome, and I will make sure I give Chainfire some money, I will probably just pickup SU Pro
Didn't want to run into boot loop because it was meant for a particular kernel

Is it just for xt1095 or will also work with 1092?
Sent from my XT1092 using Tapatalk

blinkin said:
Is it just for xt1095 or will also work with 1092?
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
It was made for the 1095. You can give it a try and let us know. If it fails it doesn't screw up anything (I don't think, since in testing it failed for me many times before he got the bugs worked out) Theoretically it should work as I said it's boot.img

graffixnyc said:
It was made for the 1095. You can give it a try and let us know. If it fails it doesn't screw up anything (I don't think, since in testing it failed for me many times before he got the bugs worked out) Theoretically it should work as I said it's boot.img
Click to expand...
Click to collapse
Running Lollipop on XT1097, and rooted with this. Everything going good.
Thx u all

beelzebu said:
Running Lollipop on XT1097, and rooted with this. Everything going good.
Thx u all
Click to expand...
Click to collapse
Can confirm on XT1097. Man this is amazing!
Anyone has flashed twrp?
Anyway thank you all!

Thanks.

Is there a step-by-step for this? I never rooted any of my Note series phones, so it's been a while.

1. unlock bootloader from moto site (follow instructions there) ALL OF YOUR DATA WILL BE WIPED - BACKUP EVERYTHING FROM INTERNAL STORAGE
2. ensure that you have fastboot / mfastboot / android SDK installed and setup (including PATH)
3. enable usb debugging on your phone
4. ensure that you have the appropriate drivers for your device installed
5. reboot to bootloader
6. check to make sure you have the correct drivers installed
7. type fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
8. phone will reboot.
All of this is in the OP. good luck
Disclaimer
you alone are responsible for the health of your device, if you are at any point worried about causing damage, do not proceed. I will not buy you a new phone if you break yours.

byt3b0mb said:
1. unlock bootloader from moto site (follow instructions there) ALL OF YOUR DATA WILL BE WIPED - BACKUP EVERYTHING FROM INTERNAL STORAGE
2. ensure that you have fastboot / mfastboot / android SDK installed and setup (including PATH)
3. enable usb debugging on your phone
4. ensure that you have the appropriate drivers for your device installed
5. reboot to bootloader
6. check to make sure you have the correct drivers installed
7. type fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
8. phone will reboot.
All of this is in the OP. good luck
Disclaimer
you alone are responsible for the health of your device, if you are at any point worried about causing damage, do not proceed. I will not buy you a new phone if you break yours.
Click to expand...
Click to collapse
Muchas gracias! Here we go. I saw others had success with XT1097, so I'm going for it.

Working on XT1092 with XT1095 5.0 firmware

Any Canadians with a Telus model try this out? I believe Telus Moto X (2014) is XT1097 as well.

graffixnyc said:
And HERE it Is!!!! I'm too tired to make a long thread.. I need to sleep hahah I'll make a proper thread tomorrow if he doesn't..
quickist way... be bootloader unlocked and then boot the image in the image folder of the zip
Unzip the zip to your computer.
fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
Make sure it's fastboot boot.. not fastboot flash.
It will reboot, reboot again and then you're good
Now go buy chainfire a beer
http://download.chainfire.eu/596/CF-Root/CF-Auto-Root/CF-Auto-Root-victara-victaratmo-xt1095.zip
This is not a flashable zip
Click to expand...
Click to collapse
Thank u... It is working perfectly
We now need to wait for Exposed and the fun begins with a lollipop taste....

beelzebu said:
Running Lollipop on XT1097, and rooted with this. Everything going good.
Thx u all
Click to expand...
Click to collapse
You just ran these steps and good to go? no problems with modem/radio and or imei? I also have an xt1097 but I'm afraid to brick my beloved X in the process haha

JoaoGuiPan said:
You just ran these steps and good to go? no problems with modem/radio and or imei? I also have an xt1097 but I'm afraid to brick my beloved X in the process haha
Click to expand...
Click to collapse
Just need to backup modem fsb and pds and then flash tmo factory images, after that sideload de OTA, refresh your modem an from there you are good to go.

blyndfyre said:
Any Canadians with a Telus model try this out? I believe Telus Moto X (2014) is XT1097 as well.
Click to expand...
Click to collapse
Did you get lollipop running on your telus moto x? If so what process did you follow.

Jesus, will non unlocked ever get root?

Rooted 5.0.... how to upgrade to 5.1.1

Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433

WiFivomFranMan said:
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I'm on the same boat, but I think our answer will come soon. Today I found out that WugFresh will be updating the NRT Toolkit to support the Nexus Player. See this post.

Why not just download the image and flash it? Plenty of guides on how to do this

lafester said:
Why not just download the image and flash it? Plenty of guides on how to do this
Click to expand...
Click to collapse
I didn't know that there were difficulties with 5.1.1. I used Wugfresh's tool to install 5.1.1 with the "no wipe" option and I had 5.1.1 just fine - but can't figure out how to get root back!! And I need root to expand the storage!! Right now I have a fresh, clean, 5.1.1 install on my NP.
I tried Wugfresh's tool, I sure wish it told me that it didn't work with the firmware that it had already detected!!
I also tried the Chainfire root.img that I used back on 5.0 and it seems to work until I tell SuperSU to update the binaries. At that point it basically times out and asks me to reboot.
What next?! Wait for Wugfresh? Is there another way to root?

I flashed the cm recovery from dhacker and used it to flash the newest beta of supersu. After that the app didn't show up until I installed it from the store but now it works fine

I just want to upgrade it without losing all my stuff (Saved games for my NES ROM, etc...)

Why don't you locate the save data in es file explorer and copy it to the cloud. Reimage nexus player and set up es file explorer, cloud and copy the saved data back to where you stored it.

would anyone be so kind to point me to one of the guides on how to use factory image/OTA to update from 5.0 rooted to 5.1.1? I don't care about keeping my settings, and I don't care about root. just want the latest and greatest.
thanks in advance

The Nexus Player is a Nexus device, and you can always upgrade to the latest version by using the factory images found here: https://developers.google.com/android/nexus/images. The procedure to flash a factory image on any Nexus device has not changed since the Nexus One was released, so you can look at any of the guides for Nexus devices.
Essentially it boils down to this: The factory image contains a few files in an archive format. There are a few images within that you need: bootloader (I can't remember what the name of the file is but it's something like xxxxbootloaderxxx.img), system.img, boot.img, recovery.img). Extract those images from within the archive and flash them. You do this by booting into the bootloader, opening a command prompt in the same folder that you downloaded the image files) on your PC and type the following commands:
fastboot flash bootloader bootloader.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
If you also want to start fresh and wipe all your data, execute the following command: fastboot format userdata
Then execute: fastboot reboot
Done.
Notes:
1) You need to extract these files in the same directory as where you downloaded the images before proceeding.
2) if you are using Windows, you need to install the the driver (found here: http://developer.android.com/sdk/win-usb.html)
3) The procedure above assumes your bootloader is unlocked. If not, you will need to unlock it (using: fastboot oem unlock) and it will wipe all your data.

efrant said:
1) There is currently no way to get root on 5.1.1 without modifying the kernel (so that it boots SELinux in permissive mode).
Click to expand...
Click to collapse
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053

etnpnys said:
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
Click to expand...
Click to collapse
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.

efrant said:
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
Click to expand...
Click to collapse
Ok - whew! I know that I went through the process but I couldn't be 100% sure because I have tried so many things to get expanded storage working to no avail that I've kinda given up for the time being...

It's a nexus - use custom recovery to flash supersu and your rooted.... Done

Toneman07 said:
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Click to expand...
Click to collapse
Not necessarily... You still need a modified boot.img to get the whole thing working...

etnpnys said:
Not necessarily... You still need a modified boot.img to get the whole thing working...
Click to expand...
Click to collapse
Thats interesting considering both my nexus phone and samsung tablet are running stock kernels (boot.img) and rooted just fine using the above method.

Bootloop Help After Trying To Root 7.1.1

So I flashed the 7.1.1 update and everything was fine. I then tried to root through TWRP with the most recent version of recovery and and SuperSu and when I went to reboot it would get to the "Google" splash screen and go back to the warning. I then tried to restore to my Nandroid that I made right before the 7.1.1 flash but it does the same thing. I ended up doing a factory reset, still looping. I tried flashing an old firmware but it still would loop. I got desperate and did a full wipe and then flashed the old firmware from September's update but it still will not boot. I'm a long time lurker I just don't post much. Any help will be appreciated. Thanks in advance!

http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club

jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Ahh, great. I tried searching to see if anyone else posted anything, couldn't find it.

jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Wait are you able to get into Recovery?

ChazLanier said:
Wait are you able to get into Recovery?
Click to expand...
Click to collapse
Nope. And so are other folks.
But if you can, there's still hope to save your device.

What version of twrp were you using?? Also what company makes the storage (not memory) on your device?

jamaniek said:
Nope. And so are other folks.
But if you can, there's still hope to save your device.
Click to expand...
Click to collapse
I can still get into recovery. I just can't get it past the Google splash screen.

ChazLanier said:
I can still get into recovery. I just can't get it past the Google splash screen.
Click to expand...
Click to collapse
Have you tried installing custom ROM, instead of a stock one?
And tell us what @ArminasAnarion asked for. There may be a pattern here. :good:

I haven't tried a custom ROM. I'll try that if I get any down time at work. Also, I'll check for you @ArminasAnarion in a bit.

Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?

ChazLanier said:
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
Click to expand...
Click to collapse
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!

ArminasAnarion said:
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
Click to expand...
Click to collapse
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.

ChazLanier said:
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
Click to expand...
Click to collapse
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.

ArminasAnarion said:
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
Click to expand...
Click to collapse
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.

ChazLanier said:
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
Click to expand...
Click to collapse
Oh okay cool! Good luck!

ArminasAnarion said:
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
Click to expand...
Click to collapse
Samsung storage, and I thought I was on -2 but it seems like I was on -1.

ArminasAnarion said:
Oh okay cool! Good luck!
Click to expand...
Click to collapse
Newest image didn't work either..

Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.

FWIW, I successfully updated to 7.1.1 NPF10C and rooted by using fastboot to flash bootloader, radio, boot, system, and vendor. Then used TWRP 3.0.2-2 to flash SuperSU 2.78 SR1. No issues.

Howie Dub said:
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
Click to expand...
Click to collapse
No luck on this either.

[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.