Hi,
I just got OnePlus 3, it is brand new but the guy who owned it has TWRP installed, I received notification that OnePlus3Oxygen_16_1706101914 System update was available, downloaded it and it wont install.
Once it starts installing it goes back to TWRP reboot page after the restart saying Android is updating. Then once I restart it is says the Update is available again. I tried to download the zip file through xda and selected it through TWRP not it says :
E:unknow command [log]
Updater process ended with ERROR 7
Error installing zip file' /sdcard/TWRP/
OnePlus3Oxygen_16_OTA_054_all_1706101914_1ab24f4be6e74def.zip.
I wiped cache/dalvik, re-downloaded the zip file and it still did not work.
Havent done this for awhile and have no idea what to do.
Thank you very much in advance.
I would recommend flashing TWRP again and then trying to install the update.
Personally I use Blu_spark TWRP as it has always worked on my end. When on the install section of TWRP there should be a button to install images. Install the img file to the recovery section, reboot back to the recovery and then try install the file.
Another way of flashing TWRP is via PC using ADB.
File here:
https://forum.xda-developers.com/devdb/project/dl/?id=25294
---------- Post added at 02:53 AM ---------- Previous post was at 02:52 AM ----------
Also, make sure you are downloading the FULL zip, not the OTA zip. full zip should be 1.3-1.4GB. Download the full zip here if you haven't got it.) http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.1.6/
You cannot flash ota from twrp. But if your bandwidth is limited, what you can do, is to flash stock recovery, then update with ota, then flash back twrp
Thank you very much for your responses. Sorry for the delay had no internet access.
Downloaded both files, TWRP and Oxygen zip, still the same error 7. Installed the drivers successfully. Have no idea what else to do.
When I am in TWRP, I go down to the folder and select the zip that I downloaded from oneplus site but it doesnt say install it says flash.
FriendWithin said:
I would recommend flashing TWRP again and then trying to install the update.
Personally I use Blu_spark TWRP as it has always worked on my end. When on the install section of TWRP there should be a button to install images. Install the img file to the recovery section, reboot back to the recovery and then try install the file.
Another way of flashing TWRP is via PC using ADB.
File here:
https://forum.xda-developers.com/devdb/project/dl/?id=25294
---------- Post added at 02:53 AM ---------- Previous post was at 02:52 AM ----------
Also, make sure you are downloading the FULL zip, not the OTA zip. full zip should be 1.3-1.4GB. Download the full zip here if you haven't got it.) http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.1.6/
Click to expand...
Click to collapse
Thank you very much all, finally was able to flash everything.
Appreciate all your help.
Related
Im looking for preferably the latest TWRP in Tar format so I can load it with Odin. I currently have CWM but would rather have TWRP.
I tried GooManager but keep getting the "webpage not found error". I tried Recovery Tools but didn't have success.I tried ROM Manager but it
keeps loading CWM. Still noobish so flashing with terminal emulator is foreign territory. Please help.
Barb3r said:
Im looking for preferably the latest TWRP in Tar format so I can load it with Odin. I currently have CWM but would rather have TWRP.
I tried GooManager but keep getting the "webpage not found error". I tried Recovery Tools but didn't have success.I tried ROM Manager but it
keeps loading CWM. Still noobish so flashing with terminal emulator is foreign territory. Please help.
Click to expand...
Click to collapse
Here are the download links for the d2att recoveries straight from TWRP's site.
FYI, GooManager installs TWRP and ROM Manager installs CWM. Also, the latest official TWRP recovery won't flash 4.4 ROMs, CWM on the other hand can.
Here's the link to the Unofficial TWRP 2.6.3.1 which supports 4.4 ROMs. It's a zip file that can only be flashed through a recovery though.
Thanks for the reply and information. For some reason I just like TWRP and coupled with the fact that I am stuck makes me want it more.
Whenever i download the tar file under that link, it extracts to a img file. What am I doing wrong?
Edit: Got it working, I used flashify from play store and flashed latest TWRP image file in less than 5 seconds.
On to the next adventure.
Barb3r said:
Thanks for the reply and information. For some reason I just like TWRP and coupled with the fact that I am stuck makes me want it more.
Whenever i download the tar file under that link, it extracts to a img file. What am I doing wrong?
Edit: Got it working, I used flashify from play store and flashed latest TWRP image file in less than 5 seconds.
On to the next adventure.
Click to expand...
Click to collapse
Your welcome, I'm glad that everything worked out for you.
Also, you're not supposed to extract the tar file, it's meant to be flashed though Odin. The img file is meant to be installed via the terminal emulator.
I rooted my G Pad 8.3 and I heard that you could install a custom recovery (TWRP) through the Flashify app. But I really wasn't sure... Can somebody just guide me through... I have flashify installed on my G Pad and I am also rooted.
Download the 2.6.3.0 img from twrp website, then download the 2.6.3.2 zip from here http://forum.xda-developers.com/showthread.php?t=2551499 , Use Flashifyed to install the 2.6.3.0 img, then when its done you will want to reboot directly into twrp, now you will want to flash 2.6.3.2 from inside the twrp recovery and then reboot. Thats how I did it and it worked on the first shot.
Download twrp 2.6.3.1, making sure that you choose the file that matches your software version of your tablet.
The file will be named twrp.txt, navigate to the file using a file browser and change the file name to twrp.img
Now open flashify and choose recovery image.
Then select choose file.
Use flashifys file Explorer and navigate to twrp.img and click on it, just follow the instructions in flashify and you should be good to go.
Once flashed, you can download the twrp 2.6.3.2 zip and flash it from your new recovery
Edit ** I chose 2.6.3.1 because I don't see a link for 2.6.3.0 on my xda app. If you can see a link for 2.6.3.0 then you should use that one first.
Sent from my LG-V500 using XDA Premium HD app
Thanks it worked ;P
I used twrp.zip and just flashed it as a zip with flashify (NOT as a recovery, which asks for an img).
Sent from my LG-V500 using xda app-developers app
LeighR said:
I used twrp.zip and just flashed it as a zip with flashify (NOT as a recovery, which asks for an img).
Sent from my LG-V500 using xda app-developers app
Click to expand...
Click to collapse
I did the same with no problems at all
Thanks guys this worked and was fast!
error
LeighR said:
I used twrp.zip and just flashed it as a zip with flashify (NOT as a recovery, which asks for an img).
Sent from my LG-V500 using xda app-developers app
Click to expand...
Click to collapse
Doesnt let me flash img as a zip says find zip extention and says flashfy says i have 2.7.0.1 installed but doesnt boot to recovery says on lg screen secure booting error cause boot certification verify and stays there.Im on 4.4.2 v500d does that make a difference?
---------- Post added at 03:57 PM ---------- Previous post was at 03:37 PM ----------
brewer15650 said:
Download the 2.6.3.0 img from twrp website, then download the 2.6.3.2 zip from here http://forum.xda-developers.com/showthread.php?t=2551499 , Use Flashifyed to install the 2.6.3.0 img, then when its done you will want to reboot directly into twrp, now you will want to flash 2.6.3.2 from inside the twrp recovery and then reboot. Thats how I did it and it worked on the first shot.
Click to expand...
Click to collapse
do you install as zip or img cause zip tells me its not a zip file
Guys I have a question. Just recently rooted my LS990 running 5.0 everything is stock including stock recovery. Want to use Flashify to install Twrp. Do I need to have a custom recovery already installed? When I'm about to install it gives me the options for either CWM recovery or Twrp. I'm not sure if is asking me if any of these are my current recovery.
samuelmoya23 said:
Guys I have a question. Just recently rooted my LS990 running 5.0 everything is stock including stock recovery. Want to use Flashify to install Twrp. Do I need to have a custom recovery already installed? When I'm about to install it gives me the options for either CWM recovery or Twrp. I'm not sure if is asking me if any of these are my current recovery.
Click to expand...
Click to collapse
You don't need it prior, but select the one you wish to install. You do need root of course...
Thanks
---------- Post added 25th March 2015 at 12:12 AM ---------- Previous post was 24th March 2015 at 11:57 PM ----------
Nope. Didn't work. I guess I'm going to have to get off my lazy behind and use adb.
hello everyone, hope you all have a nice day...
i'm no on NON-ROOTED stock OxygenOS 3.5.2, yesterday OTA update to 3.5.3 appeared on my phone and i downloaded it, i have TWRP recovery, then in rebooted to TWRP to install the update, after thtat, phone reboots again and said Update failed, if i go to system update now,it wants to download a 1.3GB file instead of former 80mb file! can i update using the 80mb OTA file instead of downloading a 1.3gb file ?
OTA wont work with TWRP Recovery. You need to revert back to stock recovery to use OTA.
And If you use full ROM ZIP, it will break your TWRP recovery.
ansaziz777 said:
OTA wont work with TWRP Recovery. You need to revert back to stock recovery to use OTA.
And If you use full ROM ZIP, it will break your TWRP recovery.
Click to expand...
Click to collapse
It worked for me with TWRP. But I did something different. If you turn on "show hidden files" in any supported File Manager you'd notice a folder named ".OnePLusH2Ota" that's where the downloaded update files are stored as a zip. So all you have to do is download the update file and Move it to the Root directory from the update folder. Then boot into TWRP and flash the zip and it will work.. Hope that helped
**REMEMBER THE TWRP I USED WAS NOT THE OFFICIAL TWRP. IT WAS A CUSTOM VERSION OF TWRP**
ansaziz777 said:
OTA wont work with TWRP Recovery. You need to revert back to stock recovery to use OTA.
And If you use full ROM ZIP, it will break your TWRP recovery.
Click to expand...
Click to collapse
I was able to download and then flash the update .zip with the modified TWRP, didn't break that version of TWRP.
So I was running stock 4.0.0 with twrp recovery just fine, and go to update via ota the 4.0.1. Now this failed, and so I decided I might as well clean install. After installation now, regardless of rom (even lineageos based) I cannot boot out of twrp. Every reboot leads back to twrp. I can access fastboot, but thats it. I've tried reflashing twrp also
Edit: This is ridiculous. Literally everything looks perfect but it refuses to boot. Tried every rom I can, even tried different recoveries and ****ing nothing. I can't find any rhyme or reason to this nonsense.
Shayded said:
So I was running stock 4.0.0 with twrp recovery just fine, and go to update via ota the 4.0.1. Now this failed, and so I decided I might as well clean install. After installation now, regardless of rom (even lineageos based) I cannot boot out of twrp. Every reboot leads back to twrp. I can access fastboot, but thats it. I've tried reflashing twrp also
Edit: This is ridiculous. Literally everything looks perfect but it refuses to boot. Tried every rom I can, even tried different recoveries and ****ing nothing. I can't find any rhyme or reason to this nonsense.
Click to expand...
Click to collapse
I'll tell you exactly the same as the last one...
First of all... YOU can NEVER try to install an official update having a custom recovery (like TWRP) installed in your device. Previously, you should have changed to stock recovery.
Having said that, you have to make the following....
1. If you have already the full room into internal memory, reboot into recovery. If not, copy the full rom to a pendrive an connect it by OTG.
2. Restart in recovery mode and click on wipe and then, advance wipe and select... davilk, cache, data and system partitions. then, slide the bar.
3. When it finish, go back to the main menu and click on install. Select the full rom from internal storage (or OTG) and install it.
4. When it finishs, you have two options from here...
4.1. First option. Try to install TWRP recovery before rebooting, because the rom will have installed stock recovery. After flashing twrp, theoretically you should get twrp installed but sometimes it fails. So, It is possible it is blocked when you try to reboot system and you can see a warming saying "there is not rom installed". Don't panic, turn off your phone from power bottom and restart the device. You will see the room installed but not the twrp. In this case, you will have to install TWRP from sideload and then, Supersu from recovery.
4.2. Second option. When the rom instalation has a finished, reboot system to check the rom is installed correctly. Then, restart again your device to fastboot mode and install recovery twrp from sideload. Finally, you can install Supersu from recovery.
This is all! Never settle!
Flash stock recovery? Does it boot?
I have the exact same problem and in stuck in a pickle
---------- Post added at 08:15 AM ---------- Previous post was at 08:12 AM ----------
Crazyhat said:
I'll tell you exactly the same as the last one...
First of all... YOU can NEVER try to install an official update having a custom recovery (like TWRP) installed in your device. Previously, you should have changed to stock recovery.
Having said that, you have to make the following....
1. If you have already the full room into internal memory, reboot into recovery. If not, copy the full rom to a pendrive an connect it by OTG.
2. Restart in recovery mode and click on wipe and then, advance wipe and select... davilk, cache, data and system partitions. then, slide the bar.
3. When it finish, go back to the main menu and click on install. Select the full rom from internal storage (or OTG) and install it.
4. When it finishs, you have two options from here...
4.1. First option. Try to install TWRP recovery before rebooting, because the rom will have installed stock recovery. After flashing twrp, theoretically you should get twrp installed but sometimes it fails. So, It is possible it is blocked when you try to reboot system and you can see a warming saying "there is not rom installed". Don't panic, turn off your phone from power bottom and restart the device. You will see the room installed but not the twrp. In this case, you will have to install TWRP from sideload and then, Supersu from recovery.
4.2. Second option. When the rom instalation has a finished, reboot system to check the rom is installed correctly. Then, restart again your device to fastboot mode and install recovery twrp from sideload. Finally, you can install Supersu from recovery.
This is all! Never settle!
Click to expand...
Click to collapse
Here is the problem tho, I can flash Roms but when I attempte to boot into said ROM it just goes straight back to recovery.
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
Puddi_Puddin said:
Flash stock recovery? Does it boot?
Click to expand...
Click to collapse
Tried that too through adb but didn't work for some reason, I forget. Either I messed up or the phone didn't allow it
urvianoob said:
I have the exact same problem and in stuck in a pickle
---------- Post added at 08:15 AM ---------- Previous post was at 08:12 AM ----------
Here is the problem tho, I can flash Roms but when I attempte to boot into said ROM it just goes straight back to recovery.
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
Tried that too through adb but didn't work for some reason, I forget. Either I messed up or the phone didn't allow it
Click to expand...
Click to collapse
You don't do that with adb but with Fastboot
Boot into fastboot > fastboot flash recovery-file name.img
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Hi
Puddi_Puddin said:
You don't do that with adb but with Fastboot
Boot into fastboot > fastboot flash recovery-file name.img
Click to expand...
Click to collapse
Yeah that is what I meant to say lol, I found something in another article on the same problem that worked for a guy, gonna try it soon
---------- Post added at 08:31 AM ---------- Previous post was at 08:22 AM ----------
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
OK I get all of it so basically I flash stock recovery from fast boot, boot into the new stock recovery via fast boot, then flash ROM and I'm done?
OTA works ONLY if you are on stock recovery, rom, kernel.
I suggest to format data in recovery (this will wipe ALL in youre phone),
flash modified recovery (.22, .23. 28 by eng.stk),
flash FULL rom,
flash SuperSU 2.79 stable, if you want root,
flash recovery,
reboot to recovery,
reboot to rom.
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
Where can I get the stock recovery download?
something like that happen to me when i try to go back from N to MM oxygen, i managed to fixed it by installing the stock recovery then install the 3.26 plus the 3.26 "modem" (if i didnt install this one, my touch screen wouldnt work) after that it just works, then i updated to 3.28
i havent install twrp and do the root for now because dont have time to tinker yet, but i can just do than whenever i have the time
I think ---- and my solution
I think some script is created as we click update...It's running on boot up and causing this problem...
I had this problem yesterday and it took me a lot of time to get my device to working...
SOLUTION: first backup the data(it backsup apps and such) from twrp and other files which are important for you...copy it to a PC.
follow the second step in this thread(it will wipe everything)
It's not allowing me to post link...It's the mega unbrick guide from Oneplus3 forums
It will take you to older version and then flash full zip(nougat build) from modded twrp..restore the backup..don't update until someone finds a solution...I did that and I'm waiting for a solution to continue...
hope it helps
This is how I solved mine.
1) Go back to stock recovery v2
2) adb sideload oos, flash magisk then flash systemless supersu.
Try this guys, found a way how to flash 36mb OTA file with latest modified TWRP by eng.stk here https://forum.xda-developers.com/devdb/project/dl/?id=22429
1. Download and dirty flash the full 4.0 zip https://drive.google.com/file/d/0BzS3nWITUqU_Sk5yQkRqWkhFY3c/view
2. Flash 4.0.1 OTA (36mb) https://drive.google.com/file/d/0B6FY-XKZtgn4R2d2Rk8xd3AzWVE/view?usp=drivesdk
3. Flash SuperSU
4. Reboot
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
eko_cahyono said:
Try this guys, found a way how to flash 36mb OTA file with latest modified TWRP by eng.stk here https://forum.xda-developers.com/devdb/project/dl/?id=22429
1. Download and dirty flash the full 4.0 zip https://drive.google.com/file/d/0BzS3nWITUqU_Sk5yQkRqWkhFY3c/view
2. Flash 4.0.1 OTA (36mb) https://drive.google.com/file/d/0B6FY-XKZtgn4R2d2Rk8xd3AzWVE/view?usp=drivesdk
3. Flash SuperSU
4. Reboot
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did it work for you? For me it keeps booting back to TWRP
---------- Post added at 03:45 AM ---------- Previous post was at 03:17 AM ----------
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
Where did you get new stock recovery? link please
paul369741 said:
Did it work for you? For me it keeps booting back to TWRP
---------- Post added at 03:45 AM ---------- Previous post was at 03:17 AM ----------
Where did you get new stock recovery? link please
Click to expand...
Click to collapse
Yes It works
You can grab the stock recovery in the OP3 toolkit here on xda
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Flash through fastboot, then flash/sideload a full stock zip. After that your phone should be back in working order and you can flash TWRP back.
Goodluck!
qyrus said:
You can grab the stock recovery in the OP3 toolkit here on xda
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Flash through fastboot, then flash/sideload a full stock zip. After that your phone should be back in working order and you can flash TWRP back.
Goodluck!
Click to expand...
Click to collapse
If my phone is rooted, flashing through fastboot the stock recovery will remove root?
I was following the guide at:
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I started with a Pixel XL 7.2, unlocked, magisk, etc. I uninstalled magisk, updated all OTA updates, and then began the thread above.
I followed 6 - Extract boot.img from Fcatory Image and fastboot boot.img
The continued with 7 - Root with Magisk
booted to twrp, flashed twrp, no issues.
Rebooted to recovery, flashed elementalX kernel 3.04, and added magisk v16.3
No errors
Rebooted phone, and upon boot, got a message:
"there's an internal problem with your device"
From what I've read, that is not really an issue and has something to do with some things not matching, so, an update to magisk in the future will resolve it. So no big deal.
However, I don't see magisk manager, and have no root.
I reboot back to recovery, uninstall magisk manager, and reboot phone.
Still get the internal problem message, but no big deal.
I reboot back to recovery, and try flashing magisk again.
Still no manager, still no root (from root checker).
I try installing the magisk manager app directly, but, the APK cannot install, and just gives a generic error message of "app not installed".
Reboot to recovery, uninstall magisk again, wipe cache. Reboot, still same internal problem message.
Try to flash magisk 16.0 instead, repeat the above, and still no root, and can't install APK.
So, just kind of stuck at this point. Phone tells me that elementalx installed without an issue though, so, just seems like magisk is the last step. Any help is greatly appreciated. Thank you.
The message you get upon boot is from the kernel, nothing to do with magisk. not that it matters, it doesnt affect anything.
According to EX thread and EX's official websites "How to install" guide, you are supposed to install magisk first. Thats how i do it.
what you need to do is......
Reflash the stock factory boot img and let it boot.
Reboot to bootloader flash or boot twrp, and install magisk.
Reboot let it boot all the way.
Then reboot to bootloader flash/boot twrp and install EX.
Reboot.
---------- Post added at 07:14 PM ---------- Previous post was at 07:12 PM ----------
Double post, sorry, butt.......
https://elementalx.org/how-to-install/
Read part one step three.
"3. Root your device (optional)
If you would like root access to your device, install SuperSU or Magisk. This should be done before installing ElementalX. Other root methods are NOT recommended. Root access will give you full control over your device and allow you to change kernel settings and tweak your device. To install SuperSU or Magisk, download to your device, reboot to recovery and install the zip you downloaded. Make sure you reboot into your system after the installation process completes. Ensure that root is correctly installed and working.
At this step, I usually make a backup of the stock rooted kernel. Now that you are rooted, you can do this very easily in EX Kernel Manager by selecting Tools->Kernel backup. This will save the boot.img."
Thank you for the help, will try it when I get a chance. The guide that I was following said for elementalx, flash kernel first. For exnoshadez, to do magisk first, for other kernels, do kernel first. I had read that some kernels need to go first, while others magisk needed to go first, and since that guide was specifically oreo, I thought kernel was first. But, thanks! Will try going back to factory boot image and progressing through.
So, I flashed back to stock boot.img, booted twrp, flashed twrp, and flashed magisk. But, Magisk still did not show up. I tried installing the magisk manager apk, but still get "App not installed" when trying that. At least the "there's an internal problem with your device" message went away.
Any other ideas on what to check when flashing, or why it's not "taking"?
Thanks again for the help.
Found out the problem:
Had to do:
adb uninstall com.topjohnwu.magisk
The key here was that I was upgrading from 7.2 to 8.1, and in the uninstall of magisk, I guess it left some remnant behind which prevented it from installing the new version.
The way I discovered this was trying to use adb to install the magisk manager apk, and that gave me the error:
adb: failed to install MagiskManager-v5.7.0.apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.topjohnwu.magisk signatures do not match the previously installed version; ignoring!]
Then, I simply uninstalled it, then flashed using twrp again, and it worked fine.