Database Develop

[Q] 5.1 ZIP decrypt, no wipe

Is it possible that there will be no wipe update 5.1 ZIP with no encryption? Works like OTA.
I'd like to update from 5.0.1 (no force encryption) to 5.1 without loosing my data. The best for me is zip for TWRP

Well if backup everything in twrp to an external flash drive then it shouldn't be an issue. I know people have side loaded the OTA via ADB but it hasn't been working for everyone. You obviously can't take a normal OTA if you are rooted so you could try that. Alternatively I would download Parcel if you have root and backup all of your apps and data for each one that you don't want to lose then transfer it to an external drive so you don't lose it when flashing the updated images. From here you can install 5.1 and then simply restore all of your missing apps and data using Parcel. It works really well and much better than TiBu for restoring data in apps. I use both TiBu and Parcel for different things. The above is only if you can't find any alternative ways to get it loaded in TWRP

There's a stock based ROM in dev forum. Flash that followed immediately (without booting) a kernel with no force encryption such as elementalx and you'll be good.
Or just fastboot flash a system image followed by immediately boot into recovery, flash kernel and SuperSU

rootSU said:
Or just fastboot flash a system image followed by immediately boot into recovery, flash kernel and SuperSU
Click to expand...
Click to collapse
So what if we wanted to, coming from encrypted, decrypt without a wipe?

drinfernoo said:
So what if we wanted to, coming from encrypted, decrypt without a wipe?
Click to expand...
Click to collapse
nope. your internal storage meeds to be reformatted. save on a computer anything you would need.

[OP3T] From stock to Nougat then flash TWRP & root

Hi all,
What happens if you take a stock 3T, upgrade it all the way to Nougat the normal way, then proceed to unlock the bootloader, flash TWRP and supersu?
Does the TWRP 3.0.3.0 build have an issue with decrypting and mouting the sdcard? Is that even a problem in the sense of waiting until a fixed version of TWRP is released? The point is to just flash supersu for the moment. No other need to access that partition from recovery, is there? Or does it directly impact my ability to upgrade TWRP in the future?
And another question: would decrypting the phone after the stock to Nougat update, and only then flashing TWRP&root be of any use? Is this even possible at the moment? I can hold on without encryption until there's a proper version of TWRP, kernel sources are released etc.
I don't seem to find any info on these scenarios. Has anyone tried any of this?
Thank you!

Good questions.
Does the TWRP 3.0.3.0 build have an issue with decrypting and mouting the sdcard?
Click to expand...
Click to collapse
I can confirm 3.0.3.0 has problems with decrypting and mounting sdcard. A new version of TWRP should fix this.
No other need to access that partition from recovery, is there?
Click to expand...
Click to collapse
Well, the need to access partition from recovery depends. You won't be able to flash anything from TWRP. I could sideload different recoveries without decrypting but had to decrypt (with the format userdata command from cmd prompt) to revert to 3.5.4 from TWRP. In the end I mostly downgraded due to bluetooth issues.

I am having the same decryption issue... TWRP shows 0MB as the storage
What should be done now..?

you can get past encryption by formating data in twrp, though that deletes all your data, back ups and everything, but with that you have the phone completely rooted and then you can download or transfer data via mtp to storage, flash super su and verity.

Amar97 said:
you can get past encryption by formating data in twrp, though that deletes all your data, back ups and everything, but with that you have the phone completely rooted and then you can download or transfer data via mtp to storage, flash super su and verity.
Click to expand...
Click to collapse
Did that already but did not work.. Even tried the setting up of pattern method.. that too did not work...
Also force decrypted with Toolkit but still the same

just to make sure. flash twrp via fastboot( I flashed the 3.0.2.0 version) then when booting to twrp you get get the screen where it asks you for a password, skip that , just swipe to continue then go to wipe, then format data, type "yes" to confirm, the at the next booting it shouldn't​ ask you for the password anymore. That did it for me. Maybe you should try adb sideload to flash verity.img and supersu

Amar97 said:
just to make sure. flash twrp via fastboot( I flashed the 3.0.2.0 version) then when booting to twrp you get get the screen where it asks you for a password, skip that , just swipe to continue then go to wipe, then format data, type "yes" to confirm, the at the next booting it shouldn't​ ask you for the password anymore. That did it for me. Maybe you should try adb sideload to flash verity.img and supersu
Click to expand...
Click to collapse
why not use 3.0.3.0?

Solnir said:
why not use 3.0.3.0?
Click to expand...
Click to collapse
Don't really know, probably tried solving the problem by trying with the older version and then didn't feel like upgrading to the newer 3.0 after fixing the problem.

Can not install anything custom anymore, dm-verity gets triggered

Hello,
I have always been on root but somehow something changed.
Since I tried to flash the newest stable stock (5.0.1), nothing works anymore.
No matter if I flash dm-verity disabler, supersu or magisk, dm-verity gets triggered everytime and my phone just says "decryption unsuccessfull" and won't boot.
I've tried everything to fix this, including: different versions of supersu/magisk, reflashing TWRP recovery, even going completely back to stock, locking the bootloader and everything.
Also I read somewhere that you can flash dm-verity disabler and wipe data to completely remove the encryption, but TWRP showed an error message, something like "failed to wipe, cannot mount /data".
In the end I got stuck with no ROM and I couldn't even access stock recovery anymore because it had the weird password bug, so I had to use the unbrick tool to get it working again.
Can someone tell me what I'm doing wrong?
I have always been on root since the early Nexus 5 days, but now I feel really stupid because I must be missing something obvious, so thank you in advance for any help.
Cheers

What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?

If by chance you are trying to flash OpenBeta 21, I have yet to avoid my data getting encrpyted when trying to flash. And personally, I must have been doing something incorrect ever since I got the phone, because almost every time I've flashed a stock OxygenOS ROM I have triggered encrpytion. In my situation it never seemed to matter if I flashed Magisk, SuperSU, a custom kernel, or even just a modified boot.img along with the disable encryption file... I don't know the steps you're taking, but what I do is this: once I get the "Encryption Unsuccessful" message when trying to boot, I just reboot to fastboot and type "fastboot format userdata". And since flashing stock OxygenOS usually overwrites TWRP with the stock recovery despite my best efforts to avoid it, I tend to go ahead and flash TWRP while I'm booted into fastboot. After, I boot into TWRP; at which point encryption has been removed, yet the total amount of storage available to me is less than 30GB (I have the 128GB model.) You have to go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data. That restores my device back to 111GB free of 113GB. I then transfer over and flash Magisk and whatever other mods I wanted. After that my device is no longer encrypted and works just how I want it to. Hope that helps with your issue.

What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?
Click to expand...
Click to collapse
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data.
Click to expand...
Click to collapse
When I tried to do that, it just told me "cannot mount /data" and wipe failed...

kaeptn1 said:
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're not using Blu Spark 8.61 TWRP, then I suggest you install it and try again.
If all else fails, do as @lordcheeto03 suggested and format userdata in fastboot - but note that this will completely wipe your data, including internal storage. Then install TWRP, then flash 5.0.1 and anything else you want.
Sent from my OnePlus3T using XDA Labs

kaeptn1 said:
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're getting the encryption unsuccessful error, I don't think you format data in that manner, you gotta use fastboot and fastboot format userdata to remove encryption THEN boot into TWRP to do that.

OnePlus 3T Pie Update Failed to Install

I am trying to install the latest Pie Update, but unable to do so, tried local upgrade/install from internal storage, recovery mode, and ADB Sideload, every time same error "Installation failed", I wiped data, erase everything, reset and wipe cache as well, no success. My device is not rooted, it is reset to Oreo Oxygen OS 5.02. Please help

mnaceem said:
I am trying to install the latest Pie Update, but unable to do so, tried local upgrade/install from internal storage, recovery mode, and ADB Sideload, every time same error "Installation failed", I wiped data, erase everything, reset and wipe cache as well, no success. My device is not rooted, it is reset to Oreo Oxygen OS 5.02. Please help
Click to expand...
Click to collapse
maybe a bad/corrupted download

Same issue here, I am unable to update my phone
Sent from my [device_name] using XDA-Developers Legacy app

I just got the same error too.
I also got a warning while i boot back to the old version.
System update failed
Update failed, tap to enter repair mode to try again.

guys, i had the same issue too.
Download the full rom via xda link, installation failed. Same goes for the OTA.
However, I managed to update to stock PIE.
My bootloader was unlocked when using stock OREO.
So what I did was, I RE-LOCKED the bootloader, and reboot the OP3T. (BE WARNED,IT RESET THE WHOLE PHONE)
After fresh installation, i was able to update to PIE via OTA. (Should work with local upgrade too)
So for my case, that helps.

vinoxflame said:
maybe a bad/corrupted download
Click to expand...
Click to collapse
NOPE no bad/corrupted download...
---------- Post added at 09:01 AM ---------- Previous post was at 08:52 AM ----------
Well I was upgraded to the pie with locked bootloader and after that, I had flashed official twrp and magisk but I flashed oreo rom to check if this problem is there when the bootloader is unlocked well yes the one plus detects that your bootloader is unlocked and doesn't deliver the ota so what you can do is click on download upgrade read carefully bro DOWNLOAD not INSTALL just DOWNLOAD it and then you will find it in .ota directory in File Manager now what you have to do is backup your all data via your prefered backup method from which you can restore things after the update I am going to give you a spoiler all data will be corrupted when you will flash the update file via twrp that's why the one plus package updater doesn't update and says installation failed... The pie update will be successfully installed but you have to factory reset your phone to use it that's why I told You to take a backup and after this restore your data...
***I have experienced all this by downgrading and then again upgrading with an unlocked bootloader so I would be honored if you thank me***

I was on stock Pie. I was facing some battery drain issue so I decided to install Oreo official stock which was already downloaded last month. I installed it through local upgrade and rom is still in internal memory. Now I am stuck in Recovery. It tries to boot but every time after few minutes it comes back to recovery. Please help me. It installs Oreo through recovery but unable to boot.
I think Pie can be installed through sideload but I could not find exact links for installation through sideload. Or if there is any option to copy Pie Rom in my internal memory to try installing back latest rom.
If anyone could help me It will be highly appreciated. My bootloader is still locked.

accidentally deleted all the system files on twrp without making back up[RealmeX2pro]

i accidentally deleted the whole system and every other files on the device and i haven't made a backup i can only get twrp working and had tried to install various ozip files from twrp which ended up with error 7.

If you still have twrp just install the stock rom then get back to stock recovery and wipe data to format the rest of the storage and you will be back to stock.

acyg said:
If you still have twrp just install the stock rom then get back to stock recovery and wipe data to format the rest of the storage and you will be back to stock.
Click to expand...
Click to collapse
Tried installing that already but it shows up error 7 msg
Also converted the ozip to zip and changed the file to remove device names
Still doesn’t work

Did you use the chinese twrp from this thread:
https://forum.xda-developers.com/realme-x2-pro/how-to/guide-unlocking-bootloader-to-getting-t4010189
I was able to install the stock ozip just fine with it.

acyg said:
Did you use the chinese twrp from this thread:
https://forum.xda-developers.com/realme-x2-pro/how-to/guide-unlocking-bootloader-to-getting-t4010189
I was able to install the stock ozip just fine with it.
Click to expand...
Click to collapse
Worked finally
But itried locking bootloader and it caused a bootloop and now i cannot access bootloader and the device isn’t showing up in fastboot.

Why would you try to re lock the bootloader while you were trying to unbrick it. I think you seriously need to read more about what can brick the phone and plan out each step if it isn't already too late.

Locked bootloader
Stuck in the same situation at the moment, if you find a way to unbrick please let us know.