Install from Sideload error - OnePlus 3 Questions & Answers

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.

Related

Flashing Bugless Beast with ROM Manager..... help needed

I have rooted my EVO with the toast method and files. I updates my adb usb drivers and flash erecovery from my PC but when I download the file w/i RM and the DL finishes I select back up current rom and nothing happens. I did double check my root access by running the su command in a terminal and had no issues. I then DL'ed the file to me PC and transferred it to the root on the SD card, reboot into fastboot the manually into erecovery and tried to perform an update zip . Nothing is working as expected, does anyone have any ideas on things to try??? Also I am very familiar with RM as I used it all the time with my Droid.
dm5363b said:
I have rooted my EVO with the toast method and files. I updates my adb usb drivers and flash erecovery from my PC but when I download the file w/i RM and the DL finishes I select back up current rom and nothing happens. I did double check my root access by running the su command in a terminal and had no issues. I then DL'ed the file to me PC and transferred it to the root on the SD card, reboot into fastboot the manually into erecovery and tried to perform an update zip . Nothing is working as expected, does anyone have any ideas on things to try??? Also I am very familiar with RM as I used it all the time with my Droid.
Click to expand...
Click to collapse
Try just loading of Rom manager and click flash rec. All tht then try reboot into rec. May not work depending on what Rom your currently on
not sure what you mean
Are you suggesting reinstalling RM? Or are you suggesting DL'ing the Rom and flashing from RM?
Couple of things :
1) I have DL'ed the Rom from RM and began theflash process w/i the tool and nothing happens, where in the past on my droid it would go into CW recovery and flash the new Rom and all was well, but not thus far
2) I am still using the stock since UI and have flashed CW recovery via RM
3) the main thing I have noticed is the CW recovery isn't set for whatever reason
4) I did read in one of th xda threads that the boot loader was not able to be unlocked at this point

Device not detected

Hello everybody,
Here my problem :
I tried to install a custom rom, I failed. Now, my smartphone stay on the Asus logo screen. I tried to follow this - http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835 - to fix the problem, but when I connect phone and laptop, adb doesn't find the device.
If I continue and go in recovery mode (using TWRP), laptop can access the phone (I can see internal memory but not external).
And if I try the ADB sideload, there is no device again...
It's the first step, I don't see any other way to unbrick the phone...
Thanks in advance
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 be lucky your phone is recognized
Hello,
Frist, thank you for your answer. I had already tried this way but nothing. Finally, I fixed the problems (detect phone and unbrick phone).
1-In TWRP, I loaded recovery.img, boot.img and droidboot.img. Reboot in recovery mod, but I had the dead droid... so I pushed on power and volume up till I have a new screen.
2-In this part, I did a Wipe/Factory reset (useless I think), reboot in recovery mode (still dead droid). This time I selected the line "update with adb" (with an ASUS firmware). Then I had a message who told me update adb sideload. I did it and it installed the firmware. The smartphone reboot correctly.
Now, I have the same problem I had yesterday. In TWRP, my external storage isn't detected...
you use stock recovery or custom recovery, if you use stock recovery external-storage won't detected
Hello,
Thank you Bar4, I explained above how I fixed my problems. Now I'm searching a way to make TWRP (TWRP 3.0) detect my external storage to install Cyanogenmod 13.0. If it's really not possible, I would try with CWM (I have seen it in your screen).
Edit : I guess custom, TWRP. It's why I don't understand why it doesn't allow me to mount SD card or doesn't detect this same SD Card.
Mara Udé said:
Hello,
Thank you Bar4, I explained above how I fixed my problems. Now I'm searching a way to make TWRP (TWRP 3.0) detect my external storage to install Cyanogenmod 13.0. If it's really not possible, I would try with CWM (I have seen it in your screen).
Click to expand...
Click to collapse
i use twrp 3.0 too, but external sd detected. no need to put on external storage, you can flash Cm 13 through internal storage
if you want to install custom rom it's better if you make a backup first, so if happen you failed when installing new rom or maybe you don't like it (new rom) you can go back to stock rom through TWRP restore
Ok, failed again...
Try a different rom or redownload the rom it might have been a bad download.
The error message says there is no updater script in the zip meaning it can't install anything as the updater script tells what directories to install the files if I seen it correctly that is.
Sent from my ASUS_Z00AD using Tapatalk
Mara Udé said:
Ok, failed again...
Click to expand...
Click to collapse
maybe the CM 13 zip file you have download corrupted, try to re-download and re-flash it again. if still failed try another rom
( i'm using AICP Rom "based on CM 13 too") try it, it's awesome Rom ---> do clean install wipe all except internal storage and external storage
http://forum.xda-developers.com/zenfone2/development/rom-c-p-t3285951/post64645756#post64645756
http://opengapps.org/ ( select x86-6.0-nano )
Hi,
Sorry for this late answer. As I failed to install those roms (CM13, Bliss), I'm going to stop here and wait for the Marsmallow update. But I'm happy my phone isn't brik anymore.
Thank you all.

How to repair Wileyfox Swift when I can get into TWRP but not bootloader

Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.

Oneplus 3 can't boot into OxygenOS after deleting file

Hey,
I wanted to create an nandroid backup in TWRP and got error 255 in the process.
I got the log of the failed update:
cloud.directupload.net/dfZq
So i searched for a solution, and the internet said that i should remove the file wich causes backup to fail. The logs said it was '/system/app/AndroidPay'
This is a file, not a folder.
So i removed the file, keeping an backup of it, booted into TWRP and the backup still failed.
To my surprise the boot into OxygenOS fails now. It shows the Oneplus Powerd by Android logo, turns black and reboots into twrp. Recovery and Bootloader seems to work fine.
So I connected my device with my computer and tried to get the file back to '/system/app' using adb.
I tried 'adb push AndroidPay /system/app' and it seems to be transferred succesfully, however the boot into oxygenOS is still not working.
I think it can be fixed by formatting the device and flash OxygenOS new to it, but I really don't wanna do that.
General Information:
Oneplus 3
OxygenOS 3.3.4
Rooted
Xposed Installed
No custom kernal
TWRP 3.0.2-0
File wich may be broken: cloud.directupload.net/dfZs
Is there an easyer way than resetting my whole phone to get it to work ?
I'm sorry for language mistakes or maybe leaving relevant information.
Thank you for help
I've had same problem today, my solution is restore "System" part (only system) from old backup, it saved my data and OP3 works fine after that
Wipe system, then flash OOS and it should work fine. If it doesn't Im afraid you need to do a full clean install since it isn't system related then.

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.

Categories

Resources