OTA to OOS 4.0 and adb sideload won't work - OnePlus 3 Questions & Answers

Hello Guys!
I was kinda hyped when I saw on Dec 31st that there's a new Softwareupdate available. Although I have a rooted device with a custom recovery (latest TWRP), previous OTAs always worked well. So I downloaded the OTA, and tapped "install" when it was finished. But this time it rebooted into recovery mode, and TWRP just did nothing. So, assuming it was because of the rooted device, I completely unrooted it and flashed the stock recovery and tried it again. This time there was actually smth. but an error saying "Update failed" appeared. Kinda pissed I downloaded the OTA update to my PC and tried to do it via adb sideload, same error "Installation failed" on the phone and cmd said
Code:
error: protocol fault (no status)
.
After that I copied the .zip to my phone, flashed TWRP again made a nandroid backup, wiped dalvik, chache & CO (no factory reset) and installed the zip. Again: Error. I don't remember the exact code, but it was smth. with "error reading zip" or so, but the file isn't damaged.
So I have the question: What am I doing wrong? Do I have to lock OEM again?
I am looking forward to your answers.
Sincerely, Firnien
PS: I updated adb to the latest version as well and tried, still not working

You should try this : https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Start with flashin twrp -28 then follow step by step.

Nobody07 said:
You should try this : https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Start with flashin twrp -28 then follow step by step.
Click to expand...
Click to collapse
Thanks, I'll try it

Related

Boot loop after 4.4.2 update and Clockworkmod install

Stuck in a bootloop. Here's my story.
Updated to 4.4.2 earlier today.
Tried to root my Nexus 7 later after the update. Here's what I did:
rebooted into bootloader with adb (adb reboot-bootloader)
unlocked the bootloader with fastboot (fastboot oem unlock)
flashed clockworkmod using fastboot (this is the file i downloaded and flashed: -http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-flo.img)
rebooted into recovery
selected "install zip>choose zip from sdcard" (trying to install supersu.zip file that I had loaded onto the internal memory)
Here's where I ran into trouble. After selecting "choose zip" nothing happens, and a message shows up on botton of the screen that says "E: Can't mount /sdcard"
So I can't install anything from clockworkmod.
I rebooted into bootloader, tried to re-flash using fastboot - "device not found"
I tried to reboot the device into android - bootloop animation
I tried wiping data, cache, factory reset, dalvik chache, etc from recovery - still getting bootloop animation
Any ideas?
Ok, I wiped/deleted sdcard data from clockworkmod and I managed to get it to boot.
That's deadly but I still don't have root, which was the point of this in the first place. Anyone know where I went wrong?
Strange. I did pretty much the exact same procedure and it worked for me.
Sent from my Nexus 10 using xda app-developers app
So, I flashed TWRP.
Tried installing SuperSu from there. This worked slightly better than Clockworkmod Recovery, it at least could read the internal storage, and allowed me to select the supersu.zip file. But I get the following error when I try to install it:
E: Unable to open zip file
Error flashing zip 'sdcard/Download/UPDATE-SuperSU-v1.80.zip
Not sure what's happening here.... May have to do with the 4.4.2 update? Maybe I'll try flashing the 4.4.2 factory image and then retrying the above steps.
I also did pretty much the same. I had a new Nexus 7 2013. The very first thing I did was to update to 4.4.2 through OTA before I went to rooting procedures:
Unlock bootloader (data was wiped because of it)
Flash TWRP
Flash superuser.zip file through TWRP
Everything worked fine.

C1905 - "Error mounting /data"

Hey folks,
I've just unlocked my bootloader and flashed the newest PhilZ Recovery. I've been following THIS tutorial.
Fastboot didn't encounter any issues, so I thought everything went fine. But after flashing the recovery image, my phone got stuck while booting. The Sony logo shows up, the screen turns black and that's where it gets stuck.
Trying to erase userdata, factory reset etc didn't help. While resetting it shows up the following message
Code:
"Error mounting/formatting /data"
So I tried to mount it manually in the recovery, but it shows the same error. Seems like a permission problem?!
Since I don't have a ROM on my SD-card yet I tried to install one via fastboot.
Code:
fastboot update ArchiDroid_V3.0.1.1-nicki.zip
But..
Code:
Archive does not contain 'android-info.txt'
Archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Now I'm stuck. I don't think installing a new ROM will work if I can't even mount /data. So first thing is to fix this and then I'll be able to install a new ROM. Am I right?
By the way : fastboot has no problem detecting my device, but adb can't find it?! D:
I appreciate any kind of help! Thanks in advice!
Gruß aus Deutschland,
furi ;D
furiify said:
Hey folks,
I've just unlocked my bootloader and flashed the newest PhilZ Recovery. I've been following THIS tutorial.
Fastboot didn't encounter any issues, so I thought everything went fine. But after flashing the recovery image, my phone got stuck while booting. The Sony logo shows up, the screen turns black and that's where it gets stuck.
Trying to erase userdata, factory reset etc didn't help. While resetting it shows up the following message
Code:
"Error mounting/formatting /data"
So I tried to mount it manually in the recovery, but it shows the same error. Seems like a permission problem?!
Since I don't have a ROM on my SD-card yet I tried to install one via fastboot.
Code:
fastboot update ArchiDroid_V3.0.1.1-nicki.zip
But..
Code:
Archive does not contain 'android-info.txt'
Archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Now I'm stuck. I don't think installing a new ROM will work if I can't even mount /data. So first thing is to fix this and then I'll be able to install a new ROM. Am I right?
By the way : fastboot has no problem detecting my device, but adb can't find it?! D:
I appreciate any kind of help! Thanks in advice!
Gruß aus Deutschland,
furi ;D
Click to expand...
Click to collapse
have you try to flash any rom except that? because when i try to flash archidroid i've same problem like you can't mount but when i try to install any rom like cm my device can mount normally.
Nicklas Van Dam said:
have you try to flash any rom except that? because when i try to flash archidroid i've same problem like you can't mount but when i try to install any rom like cm my device can mount normally.
Click to expand...
Click to collapse
I did. Tried 3 different ROMs and everyone gave me the same outcome.
But it seems like I fixed it by returning to stock using FlashTool and a stock ROM. I went all over again and now it's installing the ROM. I hope it's working now.
E: Yup, it's working fine now. But thanks anyway!

Install from Sideload error

Hi,
I tried to unroot my oneplus 3 with
the guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock method from the oneplus forum
Everything works fine till the install from the sideload mode.
I get the error cannot read ota.zip (downloaded the newest oxigenos 4.0.2 file from the official Oneplus Site
I thought maybe the zip is corrupt, but i tried 3 other OTA from Oneplus with the same result.
im' currious in the zip the file system.patch.dat is size 0 and crc32 is also 00000000. Is this normal or should this be different?
I just checked whats happens when i unpack everything from the zip to my computer and then zip it again (i know this will not work but at least something happened), i got following message:
loading: ota.zip * daemon not running. starting it now on port 5037*
*daemen startet successfully *
Total xfer:0.00x
Any suggestions what may the problem could be?
Meitlibei said:
Hi,
I tried to unroot my oneplus 3 with
the guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock method from the oneplus forum
Everything works fine till the install from the sideload mode.
I get the error cannot read ota.zip (downloaded the newest oxigenos 4.0.2 file from the official Oneplus Site
I thought maybe the zip is corrupt, but i tried 3 other OTA from Oneplus with the same result.
im' currious in the zip the file system.patch.dat is size 0 and crc32 is also 00000000. Is this normal or should this be different?
I just checked whats happens when i unpack everything from the zip to my computer and then zip it again (i know this will not work but at least something happened), i got following message:
loading: ota.zip * daemon not running. starting it now on port 5037*
*daemen startet successfully *
Total xfer:0.00x
Any suggestions what may the problem could be?
Click to expand...
Click to collapse
I couldn't get nougat to sideload. I pushed it to internal storage, then used 'upgrade from internal'.
You need to wipe and reset system settings in stock recovery. Then all should work fine.
This is the problem with the adb drivers installed on the PC or MAC OS. I had the exact same problem. tried every adb software available on the net , but nothing worked. So I factory reseted Windows OS and installed adb drivers. Voila sideload started working as expected. The every same file which was giving error.
Please do not reset Windows. The issue is not with Windows, but your device. You need to have stock recovery installed. Reboot to recovery. Select English. Select Wipe Data and Cache, then choose Reset System Settings. Reboot to recovery again and side load. This has always worked for me. There is no need to reset Windows, just simply reset your internal storage/partitions to factory specs.

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.

Stuck in bootloader after attempting Oct update

Im stuck!!
I was rooted with Magisk on crosshatch QP1A.190711.020.C3, Sep 2019.
I just tried option #4 keep data and am getting the below (also attached pic) after getting to fastbootd screen during flash:
sending product FAILED (Write to device failed (Invalid argument))
When I try to reboot, it only boots to bootloader. I then tried wiping data same thing. I then tried reverting to the previous .C3 Sep 2019 firmare and again, same thing.
Im currently on slot B and as far as im aware, I havent done anything to slot A. However, in the bootloader screen at the bottom, I see:
Enter reason: no valid slot to boot
Before I try flashing anything else, Id like to try to boot to Slot A and see if I can at least have a usable phone for work tomorrow. Is it possible to boot to slot A from the bootloader screen?
If not, what else can I do?
Thanks in advance!!!!
JJT211 said:
Im stuck!!
I was rooted with Magisk on crosshatch QP1A.190711.020.C3, Sep 2019.
I just tried option #4 keep data and am getting the below (also attached pic) after getting to fastbootd screen during flash:
sending product FAILED (Write to device failed (Invalid argument))
When I try to reboot, it only boots to bootloader. I then tried wiping data same thing. I then tried reverting to the previous .C3 Sep 2019 firmare and again, same thing.
Im currently on slot B and as far as im aware, I havent done anything to slot A. However, in the bootloader screen at the bottom, I see:
Enter reason: no valid slot to boot
Before I try flashing anything else, Id like to try to boot to Slot A and see if I can at least have a usable phone for work tomorrow. Is it possible to boot to slot A from the bootloader screen?
If not, what else can I do?
Thanks in advance!!!!
Click to expand...
Click to collapse
Did you try to use the latest SDK https://developer.android.com/studio/releases/platform-tools.html/
saxmydix said:
Did you try to use the latest SDK https://developer.android.com/studio/releases/platform-tools.html/
Click to expand...
Click to collapse
Yup, im on 29.0.4
So I found the command to switch to slot A
fastboot set_active a
Still stuck in bootloader mode.
Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.
OK I did the regular flash-all as you said and got error. At this point, the CLI says press "any key to exit"
I then exited, selected recovery - apply ADB update - opened CLI - adb devices (saw my serial #) and then entered "adb sideload image-crosshatch-qp1a.191005.007.zip"
And now after im getting:
verifying update package....
E: footer is wrong
Update package verification took .2 s (result 1)
E: signature verifcation failure
E: error: 21
Install from ADB completed with status 2
Installation aborted
EDIT: Im an idiot, I tried to sideload the factory image. Im sideloading the OTA now. Looks like its working. Standby
Donric13 said:
Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.
Click to expand...
Click to collapse
It worked AND I kept all my data! Suweeet! Damn you saved my ass, I wouldve been ****ed tomorrow at work. Thanks again!
How many hours did it take you to figure that out??
JJT211 said:
It worked AND I kept all my data! Suweeet! Damn you saved my ass, I wouldve been ****ed tomorrow at work. Thanks again!
How many hours did it take you to figure that out??
Click to expand...
Click to collapse
Tried several ways to get into recovery (fastboot.d) to sideload the ota after the i/o error... After a hour i got the trick (3. try to begin with flash-all.sh...). Somehow i always got trouble with system space when monthly update is downloaded automatically and can't get applied because i am rooted... Somehow it seems saver to install the full ota with sideload than the flash-all.sh procedure... Glad it also worked on your side.
Donric13 said:
Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.
Click to expand...
Click to collapse
Which file do i sideload? I tried crosshatch-qp1a.191005.007-factory-2989a08d.zip. It failed with same error as guy above. I then tried to adb sideload image-crosshatch-qp1a.191005.007.zip and i got the same error? which file am I supposed to sideload?
EDIT:Never mind. I found the file. downloading and flashing hopefully it works!

Categories

Resources