Develop Bugs

Oneplus 3 do not boot after installing OxygenOS 4.0.2

Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin

Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.

dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.

Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.

[Q] Odd Recovery Message on Stock, No Root

The phone (VZ Galaxy S8+) is not rooted and on stock ROM.
The phone is having issues during calls this past week, so I decided to take a look if it has anything to do with the install failure of the July 2018 (that was pulled) update.
I did an OTA update in July 2018, it downloaded... but the install failed.
In going to recovery, I cleared cache > turned off phone > return to recovery > it started to install the update. Then, the screen turned blue and said, "no command".
The recovery message states as follows:
#fail to open recovery_cause(NO such file or directory)
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGLE-SKU
File-Based OTA
Supported API: 3
#MANUAL MODE v.1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory}
E:[libfs_mgr]Error fetching verity device number: No such device or address
E:[libfs_mgr]Couldn't get verity device number!
lE:[libfs_mgr]Error removing device mapping: No such device or address
Successfully verified dmverity hash tree
Click to expand...
Click to collapse
What does this all mean?

Did you get a answer
sunNsnow said:
The phone (VZ Galaxy S8+) is not rooted and on stock ROM.
The phone is having issues during calls this past week, so I decided to take a look if it has anything to do with the install failure of the July 2018 (that was pulled) update.
I did an OTA update in July 2018, it downloaded... but the install failed.
In going to recovery, I cleared cache > turned off phone > return to recovery > it started to install the update. Then, the screen turned blue and said, "no command".
The recovery message states as follows:
What does this all mean?
Click to expand...
Click to collapse
Did you ever get this figured out asking because mines says the same

I got rid of the phone and replaced it with the Google version of the Pixel 2 XL.
The S8+ got too temperamental and unreliable for work.

no OTA update notification

Pixel 3a XL
I haven't been getting a notification when there is a new monthly update and checking for update button not working either. I am rooted with Magisk and have some modules installed. I have disabled the modules, unistalled the modules and neither worked. I have uninstalled Magisk and checked for update before reinstalling.
Any idea what could be blocking me from getting OTA?
Thanks

You can't take ota's if you have magisk and or a custom kernel installed
you have to restore/ flash the boot img from the factory img your currently on in fastboot on a pc or mac

I've done it many times with these directions. I recently had to factory reset my phone and since I've done that no OTAs.
http://bit.ly/2PTAXj0

Getting an OTA to take while rooted is always hit and miss. I bought this phone in May 2019 and have successfully installed an OTA update perhaps 3 times since owning it.
You are going to have to get very familiar with sideloading the updates. Here is a set of instructions that I created in my "How to Root" thread in the Pixel 3a forum.
If the normal OTA method isn't working - sideload the OTA update
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on some Android 10 images, but not all.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, while the the initial boot doesn't generally take that long there are times when may take quite a while. In extreme cases, I've seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take an regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just need to be patient and let the phone complete the process.

I updated via sideload. Thank you

Stuck in boot loop - need magisk_patched file Pixel 2 XL (QQ3A.200805.001, Aug 2020)

Dear XDA-Developers, after installing August 2020 update for my Pixel 2 XL and possibly applying incorrect Magisk bootloader version, my phone doesn't boot anymore and is constantly stuck in bootscreen animation.
What I have tried so far to no result:
- Re-flashing both May 2020 (previous working version) and August 2020 without -w flag to preserve my data that I would ideally like to recover.
- Side-loading May 2020 and August 2020 OTA versions through TWRP
- Creating and booting from Magisk-core only image as per guide called "How to Create & Boot from a Magisk Core-Only Image to Fix a Bootloop Without Custom Recovery" (since I cannot post links in here).
While unpacking and repacking Magisk-core image I noticed that "BOARD_OS_PATCH_LEVEL 2020-05" indicating that I might have had the wrong version applied to it.
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
I have also tried to make data backup using TWRP, but it fails mounting /data partition and shows that it's 0 Mb.
Any other ideas to how to save the phone without wiping all the data would be greatly appreciated.
Thank you all very much for whatever suggestions you might have to help me!

hencrow said:
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
Click to expand...
Click to collapse
Magisk doesn't touch the bootloader, only modifying the boot image. Given your description of the issue, I don't believe Magisk to be the culprit here. Based upon personal experience, flashing a stock image using flash-all.bat, whether the -w flag is present or absent, totally removes Magisk as the stock boot image overwrites the modified version created by Magisk.
It's clear though that you have an issue, but how much of it is brought about by misconceptions and incorrect knowledge is unknown and at this point irrelevant. So what do you do now? Try backing up your data using the instructions here. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.

Strephon Alkhalikoi said:
So what do you do now? Try backing up your data using the instructions URL. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.
Click to expand...
Click to collapse
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.

hencrow said:
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.
Click to expand...
Click to collapse
It may not work, and in fact it probably won't, especially if TWRP can't mount the data partition. That's why I said you should be prepared for the very real possibility that you have lost all your data. As for getting logs to diagnose the issue, the only certain way to get a catlog is to record the logcat from the device on your PC as you boot it, via USB Debugging. Something that likely will not be of much help now, given what you have tried doing to resolve the issue.
At this point, in your position I would simply cut my losses and install a factory image and let it wipe the data. Once you are back up and running, you want to get into the habit of backing up app data. There are many apps that can do this, but regardless of the app used, backing up the app data to internal storage or to a location like Mega or Dropbox will make life easier if you ever encounter this again.

An update if anybody is wondering what happened - flashing Android 11 Beta 3 brought the phone back to life with all the data intact. All versions of Android 10 haven't even reached the booting stage where adbd was started and showed no logs.

Question Nokia G10 recovery from failed Android 13 sideload update

Hello,
I have the following situation. A friend attempted an Android 13 sideload update on a Nokia G10 (TA-1334) using the package provided here: https://www.theupdatebox.com/nokia-g10-and-nokia-g20-get-android-13-update-download/ .
Unfortunately he didn't backup the phone first and as far as he told me he neither had Google sync turned on. The update failed.
Now the phone doesn't boot anymore and displays the standard message: Your device is corrupt. It can't be trusted and may not work properly.
I managed to enter recovery mode and retried the same sideload update, with the same package. The update seems to progress ok up to verifying the package, but after fails with the same result. The detailed log displayed on the phone screen is:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 216.6 s (result 0).
Installing update...
E: Package is for product ROGA|ROGA_sprout but expected ROGA_sprout
I don't have much experience with ADB, sideload updates and Android in general, but since the verification looks like passing and the failure is immediately after, my assumption is that this is simply a string mismatch with the package metadata. There is this field in the metadata file "pre-device=ROGA|ROGA_sprout", which I assume it indicates that the update fits for both types of devices ROGA and ROGA_sprout but I guess this is not interpreted correctly. I removed the "ROGA" part and left only "ROGA_sprout", but obviously the update then fails with a signature error.
So, my questions are:
1) Does somebody know where we could get another sideload update only for ROGA_sprout? Or maybe any way to "fix" the referenced update to pass the thrown error. It would be fine also with an older version of Android if possible to recover.
2) It looks possible to do a factory reset from the recovery mode, but as I mentioned, unfortunately nothing was backed up. In case there's no chance to find another sideload update that could install properly, is there any way to try saving something from the phone in the current state? AFAIK the factory reset wipes out everything.
Again, I don't have much experience with sideload updates for Android phones, so sorry if I got anything wrong above.
Thank you in advance for any advice.

dkmoore said:
Hello,
I have the following situation. A friend attempted an Android 13 sideload update on a Nokia G10 (TA-1334) using the package provided here: https://www.theupdatebox.com/nokia-g10-and-nokia-g20-get-android-13-update-download/ .
Unfortunately he didn't backup the phone first and as far as he told me he neither had Google sync turned on. The update failed.
Now the phone doesn't boot anymore and displays the standard message: Your device is corrupt. It can't be trusted and may not work properly.
I managed to enter recovery mode and retried the same sideload update, with the same package. The update seems to progress ok up to verifying the package, but after fails with the same result. The detailed log displayed on the phone screen is:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 216.6 s (result 0).
Installing update...
E: Package is for product ROGA|ROGA_sprout but expected ROGA_sprout
I don't have much experience with ADB, sideload updates and Android in general, but since the verification looks like passing and the failure is immediately after, my assumption is that this is simply a string mismatch with the package metadata. There is this field in the metadata file "pre-device=ROGA|ROGA_sprout", which I assume it indicates that the update fits for both types of devices ROGA and ROGA_sprout but I guess this is not interpreted correctly. I removed the "ROGA" part and left only "ROGA_sprout", but obviously the update then fails with a signature error.
So, my questions are:
1) Does somebody know where we could get another sideload update only for ROGA_sprout? Or maybe any way to "fix" the referenced update to pass the thrown error. It would be fine also with an older version of Android if possible to recover.
2) It looks possible to do a factory reset from the recovery mode, but as I mentioned, unfortunately nothing was backed up. In case there's no chance to find another sideload update that could install properly, is there any way to try saving something from the phone in the current state? AFAIK the factory reset wipes out everything.
Again, I don't have much experience with sideload updates for Android phones, so sorry if I got anything wrong above.
Thank you in advance for any advice.
Click to expand...
Click to collapse
You should not have done that.
Nokia does not allow sideloading on this device. Please check your PM.