I haven't done a factory reset yet but I would love to avoid it if possible.
I went to take a picture of the wife's newly decorated Christmas tree and the stock camera fails to fully start. It behaves as if it can not use the hardware. When I look at the back there is a small red light/laser that refuses to go out unless the phone is rebooted.
I've rebooted the phone a few times and tried Manual Camera and a couple others .. same behavior.
The phone is running 6.0.1 and is rooted.
Anyone seeing this and have any ideas?
Are you using the stock kernel
I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.
SuperSmashedBro said:
Are you using the stock kernel
Click to expand...
Click to collapse
Yep. With the exception of being rooted and using a few utils like root explorer and recently ... nothing special. I did just notice Google Play Services *****ed and said there was an error but it wasn't specific about the error. I did bounce the cache for Google Play Services after seeing that.
Nothing odd about this phone ... it's been top notch for the last month.
fury683 said:
I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.
Click to expand...
Click to collapse
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.
aergern said:
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.
Click to expand...
Click to collapse
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------
Full reflash (without wiping userdata) with factory image seems to have worked... Now to try proceeding one step at a time with TWRP/root/Xposed to see if it breaks again.
fury683 said:
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
Click to expand...
Click to collapse
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
aergern said:
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.
Click to expand...
Click to collapse
No dice. Reflashing the 6.0.1 vendor.img did squat. I'll wait.
darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
So reflashing the system.img and waiting for Chainfire to make a new boot image could be the solution. That kinda sucks but it could be the only solution.
darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.
fury683 said:
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.
Click to expand...
Click to collapse
Same here. Using the same root method each time with my Nexus 6 was never an issue.
Damn. hmm.
Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera
edd247 said:
Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera
Click to expand...
Click to collapse
Oh. So just flash supersu 2.61 instead of using the boot.img and supersu 2.5x method. Good. I'll give that a whirl.
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I just erased and reflashed each partition except userdata so it's doing it's thing. Once it's back up then I'll just use 2.61 and be done with it.
Thanks. Just hope I don't have to look at the boot animation much longer ...
Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?
fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I did this ...
fastboot erase system
fastboot erase cache
fastboot erase boot
fastboot erase vendor
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot reboot
Seems to be stuck at the bootloader animation ... so far .. 20 minutes? I shouldn't have to wipe userdata .. right?
captainwahid said:
Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?
Click to expand...
Click to collapse
I used the only Angler boot.img in the list and it worked to root but the camera was screwed.
this one? http://forum.xda-developers.com/showpost.php?p=64004628&postcount=1195
Related
I received a Motorola OTA notification for a minor maintenance update which patched the "stagefright" vulnerability in my Moto X 2014 Pure Edition xt1095. I captured the OTA ZIP file from my cache folder, and it is attached to this post. Size of OTA ZIP is 4.29MB. (Note that Motorola OTA updates are named for the software version from which you must apply the update, not the software version to which you are upgrading.)
This is for a stock, unrooted xt1095 running Android Lollipop 5.1.
Prerequisite:
System version: 23.16.3
Build number: LPE23.32-21.6 or LPE23.32-21.3
After update:
System version: 23.16.6
Build number: LPE23.32-21.6 or LPE23.32-21.3 (unchanged)
You should be able to adb sideload this from stock recovery if you know how. If you're rooted, you'll need to request the stock 23.16.3 firmware from Motorola, and at least flash system.img and recovery.img to get back to stock system and recovery. After you do that, you might be able to sideload the OTA zip.
Deleted, sorry.
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Flash fails (TWRP finds something incorrect with HindiIME file or somesuch). Can this be caused by me removing unneeded system apps?
EDIT: Yes it was, worked perfectly after reflashing system.img.
Thanks thenestor and Romracer worked perfectly as stated I went with twrp flash -
I just installed this update from the stock recovery and it worked flawlessly. Thanks for uploading this. My wife got it a few days ago and updated before I could grab the the zip file.
Sent from my XT1095 using Tapatalk
Flintberg said:
Flash fails (TWRP finds something incorrect with HindiIME file or somesuch). Can this be caused by me removing unneeded system apps?
EDIT: Yes it was, worked perfectly after reflashing system.img.
Click to expand...
Click to collapse
System.img? Download please
I reflashed system.img of my current version and then flashed the zip in twrp.
romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
I had a stock bootloader+recovery, so I just updated via the OTA, but now my phone won't boot! Any ideas?
I'm rooted with adaway applied, I tried flashing romracer's file but I'm stuck on the boot screen saying that my bootloader is unlocked. Is it because of adaway?
romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Thank you so much for this! I lost my stock recovery so this is a godsend.
Flintberg said:
I reflashed system.img of my current version and then flashed the zip in twrp.
Click to expand...
Click to collapse
system.img have the backup to download and can flash? Sorry my english
tbs1977 said:
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
Click to expand...
Click to collapse
I'm having the same problem! Any idea how to fix it?
Damn. That file from romracer broke my phone
seriously....i can't fix it
@romracer
not sure if i understood correctly, so is it fine to have xposed? or better remove it before?
i have gravity box, bootmanager, amplify and appops
sh33z0r said:
@romracer
not sure if i understood correctly, so is it fine to have xposed? or better remove it before?
i have gravity box, bootmanager, amplify and appops
Click to expand...
Click to collapse
If you have Xposed, you need to reflash the installer zip.
---------- Post added at 07:34 AM ---------- Previous post was at 07:29 AM ----------
supremekizzle said:
Damn. That file from romracer broke my phone
seriously....i can't fix it
Click to expand...
Click to collapse
Re-flash the system.img and try again. You can find LP-5.1 for XT1095 here. (the only thing you should be upgrading from anyway).
tbs1977 said:
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
Click to expand...
Click to collapse
macravin said:
I had a stock bootloader+recovery, so I just updated via the OTA, but now my phone won't boot! Any ideas?
Click to expand...
Click to collapse
RSchmauk said:
I'm having the same problem! Any idea how to fix it?
Click to expand...
Click to collapse
Did you have Xposed install? Reflash the install zip. Otherwise see above.
romracer said:
If you have Xposed, you need to reflash the installer zip.
---------- Post added at 07:34 AM ---------- Previous post was at 07:29 AM ----------
Re-flash the system.img and try again. You can find LP-5.1 for XT1095 here. (the only thing you should be upgrading from anyway).
Did you have Xposed install? Reflash the install zip. Otherwise see above.
Click to expand...
Click to collapse
i was rooted with xposed only, and now my phone won't turn on, stuck on the boot screen...
i have two questions,
If i reflash system.img, will that wipe anything?
is there a system.img only file that i can download, downloading 1.1 gbs on my slow connection will take 4 hours, i can't afford 4 hours without a phone....
After the ota, my phone won`t turn on, like many here. What i`m worried about is that my PC is not recognizing my phone in adb. What can I do?
I was also rooted, with stock everything else but hung on the unlocked bootloader warning screen. I'm thinking AdAway or Greenify must have modified /system since that's really the only root stuff I use. For the time being I just restored my /system backup and it's working but I'll eventually need to flash stock system.img I'm guessing. Otherwise I'm gonna end up accidentally tapping the update nag screen and screwing it up again.
I just received a notification on my 6P saying that the january security update is available. The thing is that I'm rooted with systemless root, xposed, EX Kernel and TWRP. Can I update using the update button?
With systemless I believe you should be able to.
I just posted about this too....no one got back to me. I got the same message and have more or less the same setup as you. I'm scared to reboot and update lol
Pain-N-Panic said:
I just posted about this too....no one got back to me. I got the same message and have more or less the same setup as you. I'm scared to reboot and update lol
Click to expand...
Click to collapse
No.
If you have TWRP installed you will not be able to take an OTA.
Why bother?
Just flash what you want.
Ok, so if I reboot and my phone tries to install the OTA, what happens?
I have exact the same setup and tried to let the OTA install but in TWRP it aborted because of the mismatching kernel I think (at least it said it expected the generic device name Google angler etc and in stead it found Huawei nexus 6P Dees-troy etc)
So no harm is done when you try to update other than it doesn't work
But as far as I know when using xposed there's no use for systemless root because xposed is changing system partition
This update message won't go away. Can I flash it myself through TWRP with Xposed installed?
You cannot use twrp with an OTA. You need stock recovery. Also I believe that Xposed modifies /system and that in itself would prevent the OTA with stock recovery.
dratsablive said:
You cannot use twrp with an OTA. You need stock recovery. Also I believe that Xposed modifies /system and that in itself would prevent the OTA with stock recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step 10 from this guide then re-flashed TWRP, Super Su, ElementalX and everything seems to be fine, no data loss.
Pain-N-Panic said:
Ok, so if I reboot and my phone tries to install the OTA, what happens?
Click to expand...
Click to collapse
Nothing happens. it'll just fail to flash the update. It'll reboot to twrp, attempt to flash the update, and it'll fail the flash. So it just won't flash. Then you'll just reboot the system and nothing will be changed. I think you can flash these minor changes, but if you try to flash a major update through OTA it won't work with out stock recovery because that's part of the flash I think
---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------
regenwurm16 said:
I have exact the same setup and tried to let the OTA install but in TWRP it aborted because of the mismatching kernel I think (at least it said it expected the generic device name Google angler etc and in stead it found Huawei nexus 6P Dees-troy etc)
So no harm is done when you try to update other than it doesn't work
But as far as I know when using xposed there's no use for systemless root because xposed is changing system partition
Click to expand...
Click to collapse
It does not bored because of mismatched kernel. Because I tried flashing the stock kernel and then OTA and it still did not work
kirkgbolton said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step 10 from this guide then re-flashed TWRP, Super Su, ElementalX and everything seems to be fine, no data loss.
Click to expand...
Click to collapse
This. At this time it's the only fix. I did it as well. Never flashed a factory image via fastboot before so I was a little intimidated but Heisenberg's guide is so smooth and easy to follow I did it in about 5 minutes lol. Plus it was a great learning experience for me.
Is it likely that eventually TWRP flashable zips will make this process easier? Or is there some sort of restriction with these updates for Nexus phones that will always require fastboot?
Not sure. I do know that the above method only took me about 10 minutes. Yeah it sucks you have to utilize a PC to do it but its really not that bad. Maybe in the future someone will figure out how to implement the updates via flashable zip in recovery.
I struggle with this too. I really hope that someone will find a solution to flash it via .zip (sadly I'm more a programmer than an Android-hacker, otherwise I would try my very best right now ).
Just to point it out, it looks like the article you are referring to has been updated since it was linked. I wouldn't want to wipe userdata, so I think 11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact) is what you were referring to at the time. Apologies for the resurrection.
I just used the FlashFire app to update my Nexus 6p with the February update and it worked like a charm.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
Google just released May 2016 factory images for Nexus devices.
Factory Images for Nexus Devices
Android Security Bulletin—May 2016
Anyone flashed it?
OTA zip file link?
Sent from my Nexus 5X using XDA-Developers mobile app
We probably need to wait a little bit for OTA zip.
following for ota link
new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13
miksontije said:
new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13
Click to expand...
Click to collapse
Hopefully it's a good update. Sometimes they're hit-or-miss.
mxrider97 said:
Anyone flashed it?
Click to expand...
Click to collapse
Flashed it yesterday, haven't noticed anything new. However, I also haven't noticed anything bad or broken; which is just as important.
Sent from my Nexus 5X using Tapatalk
Flashed using the factory images and nothing is broken. It did trigger a Google Camera update and it has been improved a bit more. Faster startup and snappier response when changing between portrait and landscape mode. Battery life stayed the same.
waiting for ota zip :good:
I updated using fastboot. Rooted and everything is working fine. Even Android Pay with the latest SuperSU.
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Just installed! You have any advice about a compatible kernel?
Andr006 said:
Just installed! You have any advice about a compatible kernel?
Click to expand...
Click to collapse
I like EX Kernel. It has not been update with the new patches but will still work well.
---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------
chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
I update all the images with fastboot then just use WugFresh to root and add TWRP.
65coupei6 said:
I update all the images with fastboot then just use WugFresh to root and add TWRP.
Click to expand...
Click to collapse
This worked in the end, thanks for your help tip!
chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
if you boot using stock kernel (boot.img) android will replace whatever recovery you have flashed with stock recovery.
to prevent this from happening, PRIOR to first boot after flashing update, flash twrp in fastboot, scroll down in fastboot menu and boot into recovery/twrp, and apply supersu update.zip
after that you'll be rooted again and boot.img will no longer try and replace your recovery with stock recovery.
OTA posted:
http://forum.xda-developers.com/showpost.php?p=66781159&postcount=124
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.
I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?
+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)
+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?
GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good: