Related
I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left
I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.
Pro4TLZZ said:
I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.
Click to expand...
Click to collapse
What was corrupt? How did you fix it?
keeganjk said:
What was corrupt? How did you fix it?
Click to expand...
Click to collapse
Something in the partition, so I didn't restore that
Pro4TLZZ said:
Something in the partition, so I didn't restore that
Click to expand...
Click to collapse
Which partition? I just wiped my device and reinstalled FreedomOS.
keeganjk said:
Which partition? I just wiped my device and reinstalled FreedomOS.
Click to expand...
Click to collapse
Userdata partition
Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
OK.
Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
keeganjk said:
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
Click to expand...
Click to collapse
I'm sorry I can't help you more
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
I just wiped and reinstalled OxygenOS http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.10/. Once I reconfigure all my settings, files, etc, I'm going to see if it works.
dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
What's the difference between TWRP and bluspark TWRP?
dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
I can't restore; I deleted all my backups in an attempt to free up space.
I think I found the solution!
1. Go to Wipe in TWRP, swipe to factory reset
2. Download:
OnePlus Recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/OP5_recovery.img
OxygenOS: http://oxygenos.oneplus.net.s3.amaz...3_OTA_015_all_1708252353_e6d7756780064352.zip
3. Rename recovery image as recovery.img, boot phone into fastboot, plug into computer, run these commands on the computer:
fastboot devices
fastboot flash recovery recovery.img
fastboot boot recovery.img
4. Open recovery on phone
5. Select Forgot Password, will wipe all leftover files in SD Card.
6. Boot back into recovery, select reload, select Install over ADB or Install Over USB or something similar and plug phone into computer.
7. Run 'adb sideload oxygen-os-filename' without quotes on computer.
8. Let it install OxygenOS, it may appear to be frozen at some points; it probobaly isn't, so don't shut it off or unplus USB.
9. Download Bluspark TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=26601&task=get
9. Reboot into fastboot, plug into computer and run these commands on the computer:
fastboot devices
fastboot flash recovery bluspark-twrp-filename-location.img
fastboot boot bluspark-twrp-filename-location.img
10. Success (hopefully)
Oh. Wait. Now it has the same error when I try to make a backup. (I feel like it might be from installing https://forum.xda-developers.com/android/software-hacking/kali-nethunter-magisk-t3676681, but they say it's unrelated). Doors anyone know why this is happening again?
the solution to this was to boot to your previous rom that u have made nandroid backup with and then setting up the same password/pin in settings > security. When you then boot into twrp it will ask you for the pin/password to decrypt your data partition and then you can flash the nandroid backup(you have to have the same password there). here it is obvious that you are trying to flash data partition that uses different encryption password (in case of stock rom there is non) and this obviously wont happen.
maybe another solution would be to connect externally usb and unmounting data partition and then restoring from usb...
I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?
Need4Sneed said:
I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?
Click to expand...
Click to collapse
For me flashing normal oxygenos with magisk 16 and formatting data and trying to make it boot with the new flash and then rebooting into recovery and restoring made it work. I guess it has to do with the right filesystem having to be made first.
hi guys,
i've read all the thread in XDA related to ERROR 255, can't find anything to solve my problem trying to backup on TWRP ending with this error 255.?
I'm not using any parallel apps, not using Apps Locker, don't have any folder 999 (searched using Root Browser).
I've tried deleting all fingerprint, face unlock and screenlock as well.
No joy.
I'm using latest TWRP 3.2.2-1, OOS 5.1.7, Rooted.
Appreciate any help or sharing experience.
Good day!
Our country just received the Oxygen OS 5.0.1 update.
How can I install it with an unlocked bootloader?
I was going to relock it but I found out that if I did, my data will be gone.
The only difference in the set-up of my phone from a stock OP5 is the unlocked bootloader.
Flash through stock recovery
Hitman478™ said:
Flash through stock recovery
Click to expand...
Click to collapse
I haven't done this kind of thing yet.
If I do this, will my data be wiped out or not?
What about using the OTA notification ?
quick05 said:
What about using the OTA notification ?
Click to expand...
Click to collapse
What do you mean?
I tried to update my phone using the normal way but after downloading and tried to install it, it failed because my bootloader is unlocked.
I just made a backup of data using codeworkx recovery. Copied the backup (Along with the files on userdata I wanted to keep) to my PC.
Wiped all and formatted data. Then installed Oreo and copied back the files and data backup from the pc to the phone and restored data with codeworkx recovery again.
Then flashed magisk 15.2 and rebooted.
Everything working fine now.
shriekyphantom said:
Good day!
Our country just received the Oxygen OS 5.0.1 update.
How can I install it with an unlocked bootloader?
I was going to relock it but I found out that if I did, my data will be gone.
The only difference in the set-up of my phone from a stock OP5 is the unlocked bootloader.
Click to expand...
Click to collapse
I managed to flash Nougat without locking my bootloader. But I also had to Format the Data partition to make it work. I used Titanium Backup to backup the data of the Apps and Myapplist to make a list of the apps. After installing Oreo I only needed to spent 1 hour to restoring the app data.
pleomaxell said:
I managed to flash Nougat without locking my bootloader. But I also had to Format the Data partition to make it work. I used Titanium Backup to backup the data of the Apps and Myapplist to make a list of the apps. After installing Oreo I only needed to spent 1 hour to restoring the app data.
Click to expand...
Click to collapse
Hello, I'm interested in the same thing.. I have oxygen osv4.5.x received notice for is 5.0.1 and want to install. I have an unlocked bootloader and am also rooted w/magisk. I want to keep my unlocked bootloader and root after upgrading. I also want to do a "clean" install.
Can anyone provide detail instructions, including best back up method of data and links to any files needed (twrp, magisk, etc) thanks
jmoricone said:
Hello, I'm interested in the same thing.. I have oxygen osv4.5.x received notice for is 5.0.1 and want to install. I have an unlocked bootloader and am also rooted w/magisk. I want to keep my unlocked bootloader and root after upgrading. I also want to do a "clean" install.
Can anyone provide detail instructions, including best back up method of data and links to any files needed (twrp, magisk, etc) thanks
Click to expand...
Click to collapse
This is what I did:
Downloaded OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5. zip, twrp-3.2.1-0-universal-codeworkx-cheeseburger.img and Magisk-v15.3.zip.
Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP.
Rebooted to TWRP again to make sure that my TWRP was updated.
Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
This deleted my Internal Storage so I had to backup everything beforehand.
Then used advanced wipe to wipe Cache and Dalvik.
Mounted the internal storage by using the Mount option from TWRP main menu.
I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
Copied the OnePlus full update and Magisk zip file.
Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots.
Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
Booted into TWRP and flashed Magisk.
I am now on Oreo and I hate the way Ambient Display looks right now.
pleomaxell said:
This is what I did:
Downloaded OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5. zip, twrp-3.2.1-0-universal-codeworkx-cheeseburger.img and Magisk-v15.3.zip.
Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP.
Rebooted to TWRP again to make sure that my TWRP was updated.
Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
This deleted my Internal Storage so I had to backup everything beforehand.
Then used advanced wipe to wipe Cache and Dalvik.
Mounted the internal storage by using the Mount option from TWRP main menu.
I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
Copied the OnePlus full update and Magisk zip file.
Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots.
Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
Booted into TWRP and flashed Magisk.
I am now on Oreo and I hate the way Ambient Display looks right now.
Click to expand...
Click to collapse
Thank you... I like everything about my current build..should I wait to upgrade... Any other issues with Oreo?
jmoricone said:
Thank you... I like everything about my current build..should I wait to upgrade... Any other issues with Oreo?
Click to expand...
Click to collapse
I honestly dont see a big difference yet, but only had it for two days. Feels a bit snappier, my signal a bit stronger, and probably an improvement with battery life. I had issues upgrading but then again I flashed the wrong version of magisk. I think the most important thing is the latest android security update.
SysAdmNj said:
I honestly dont see a big difference yet, but only had it for two days. Feels a bit snappier, my signal a bit stronger, and probably an improvement with battery life. I had issues upgrading but then again I flashed the wrong version of magisk. I think the most important thing is the latest android security update.
Click to expand...
Click to collapse
Hey, thanks.. I will update later today. I see you provided which version of twrp (twrp-3.2.1-0-universal-codeworkx-cheeseburger.img). But what is the difference between the version you noted and the one I found (twrp-3.2.1-0-oreo-8.0-codeworkx-cheeseburger.img)
I want to make sure I have the correct version.
Thanks again
jmoricone said:
Hey, thanks.. I will update later today. I see you provided which version of twrp (twrp-3.2.1-0-universal-codeworkx-cheeseburger.img). But what is the difference between the version you noted and the one I found (twrp-3.2.1-0-oreo-8.0-codeworkx-cheeseburger.img)
I want to make sure I have the correct version.
Thanks again
Click to expand...
Click to collapse
You can ask that question on the TWRP thread. May be they can answer it correctly. I guessed that twrp-3.2.1-0-universal-codeworkx-cheeseburger.img was for both Nougat and Oreo and that is why I used it. So, if you want to be sure you should ask that on a TWRP thread.
pleomaxell said:
This is what I did:
Downloaded OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5. zip, twrp-3.2.1-0-universal-codeworkx-cheeseburger.img and Magisk-v15.3.zip.
Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP.
Rebooted to TWRP again to make sure that my TWRP was updated.
Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
This deleted my Internal Storage so I had to backup everything beforehand.
Then used advanced wipe to wipe Cache and Dalvik.
Mounted the internal storage by using the Mount option from TWRP main menu.
I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
Copied the OnePlus full update and Magisk zip file.
Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots.
Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
Booted into TWRP and flashed Magisk.
I am now on Oreo and I hate the way Ambient Display looks right now.
Click to expand...
Click to collapse
Hello, I was reviewing the process and just downloaded everything onto my computer and transferred onto my phone but have a few questions regarding some of the steps.
* Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP
** Can I update TWRP via the official app and is that version of TWRP okay to use over the "twrp-3.2.1-0-universal-codeworkx-cheeseburger.img"
* Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes' / This deleted my Internal Storage so I had to backup everything beforehand.
** How, what and where did you back up your data? Because later you mentioned "deleted my Internal Storage". I am guessing that because the OP5 does not have an external SD card everything is wiped and the new OS 5.0.1 needs to be saved onto a computer and then re-transferred back onto the phone. I am also guessing that the backup will need to be saved onto a computer as after wiping the phone it would also delete that file too, correct?
* Mounted the internal storage by using the Mount option from TWRP main menu.
** I am assuming that this option after the data wipe is self explanatory?
* I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
** This is what makes be believe all the files should be on a computer. How did you reboot and when you did, does it go directly / back to TWRP?
* Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots. / Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
** I am guessing here that once OS v8 is installed the TWRP img is no longer on the phone. I would need to transfer the TWRP back onto the phone then re-flash? Could I just install the TWRP official app and flash that way?
Thanks
jmoricone said:
Hello, I was reviewing the process and just downloaded everything onto my computer and transferred onto my phone but have a few questions regarding some of the steps.
* Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP
** Can I update TWRP via the official app and is that version of TWRP okay to use over the "twrp-3.2.1-0-universal-codeworkx-cheeseburger.img"
* Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes' / This deleted my Internal Storage so I had to backup everything beforehand.
** How, what and where did you back up your data? Because later you mentioned "deleted my Internal Storage". I am guessing that because the OP5 does not have an external SD card everything is wiped and the new OS 5.0.1 needs to be saved onto a computer and then re-transferred back onto the phone. I am also guessing that the backup will need to be saved onto a computer as after wiping the phone it would also delete that file too, correct?
* Mounted the internal storage by using the Mount option from TWRP main menu.
** I am assuming that this option after the data wipe is self explanatory?
* I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
** This is what makes be believe all the files should be on a computer. How did you reboot and when you did, does it go directly / back to TWRP?
* Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots. / Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
** I am guessing here that once OS v8 is installed the TWRP img is no longer on the phone. I would need to transfer the TWRP back onto the phone then re-flash? Could I just install the TWRP official app and flash that way?
Thanks
Click to expand...
Click to collapse
You have to flash TWRP by going to fastboot mode .
If you are rooted only then the TWRP app works
Aarju said:
You have to flash TWRP by going to fastboot mode .
If you are rooted only then the TWRP app works
Click to expand...
Click to collapse
Yes I am currently rooted. Once I flash the new OS will I still have root access to use the TWRP official app? Is that why after flashing new OS you need to flash TWRP via fastboot?
What about the backing up? I also have full titanium, thanks.
jmoricone said:
Yes I am currently rooted. Once I flash the new OS will I still have root access to use the TWRP official app? Is that why after flashing new OS you need to flash TWRP via fastboot?
What about the backing up? I also have full titanium, thanks.
Click to expand...
Click to collapse
After flashing the new rom you will be flashed stock recovery and you have to flash it through fastboot and flash magisk again.
Aarju said:
After flashing the new rom you will be flashed stock recovery and you have to flash it through fastboot and flash magisk again.
Click to expand...
Click to collapse
Hello, I followed the following instructions:
4. Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
6. Then used advanced wipe to wipe Cache and Dalvik.
7. Mounted the internal storage by using the Mount option from TWRP main menu.
8. I (also) was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
9. Copied the OnePlus full update and Magisk zip file.
I went to install the update w/in twrp and now I get an error message:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/oneplus5oxygen_23_OTA_028.....
What happened? Anyone please help...
jmoricone said:
Hello, I followed the following instructions:
4. Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
6. Then used advanced wipe to wipe Cache and Dalvik.
7. Mounted the internal storage by using the Mount option from TWRP main menu.
8. I (also) was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
9. Copied the OnePlus full update and Magisk zip file.
I went to install the update w/in twrp and now I get an error message:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/oneplus5oxygen_23_OTA_028.....
What happened? Anyone please help...
Click to expand...
Click to collapse
Wipe data and then copy the rom full zip flash it boot it to the starting screen then boot to recovery and then flash magisk ,you will see no errors.
Hello, I followed the following instructions:
4. Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
6. Then used advanced wipe to wipe Cache and Dalvik.
7. Mounted the internal storage by using the Mount option from TWRP main menu.
8. I (also) was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
9. Copied the OnePlus full update and Magisk zip file.
I went to install the update w/in twrp and now I get an error message:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/oneplus5oxygen_23_OTA_028.....
What happened? Anyone please help...
I received the following tip
"Wipe data and then copy the rom full zip flash it boot it to the starting screen then boot to recovery and then flash magisk ,you will see no errors."
But this makes no sense to me.
I have formatted my phone / wiped data / have the full rom & magisk on my "/sdcard" / went to install zip via TWRP, selected the rom and received the error message.
I decided to just go and upgrade via OTA and that failed. My phone has rebooted back to stock
what am i doing wrong?
Hey guys, I was trying to flash a ROM. TWRP was unable to wipe data. It showed error "unable to mount data". So I reformatted the data partition to exFat from ext4. After that, I was able to wipe data.
Then I flashed Carbon ROM. Everything went fine but when I booted I got Encryption unsuccessful message with an option to reset the phone. I clicked reset phone, then I was booted to recovery. I tried wiping data but it doesn't work. It gives errors which you can see in the images attached.
So, can the problem be fixed using the MiFlash tool and flashing stock rom? Or do I need to manually format data partition first?
Thanks!
Nevermind, I was able to boot into twrp and then I reformatted the data partition to ext4. Then I reflashed this rom and it seems to boot fine now.
GizmoFreak said:
Nevermind, I was able to boot into twrp and then I reformatted the data partition to ext4. Then I reflashed this rom and it seems to boot fine now.
Click to expand...
Click to collapse
How did you reformatted the data partition. ? Would you please share the process .
Soham Biswas said:
How did you reformatted the data partition. ? Would you please share the process .
Click to expand...
Click to collapse
Sure, in TWRP go to Wipe > advanced wipe > select data > change or repair file system > change file system > select your preferred format.
GizmoFreak said:
Nevermind, I was able to boot into twrp and then I reformatted the data partition to ext4. Then I reflashed this rom and it seems to boot fine now.
Click to expand...
Click to collapse
Thank you so much. Was really frustrated with this encryption deal. Worked like a charm. Cheers :good:
Hello Guys Recently i decided to update my OP5 which was on rooted nougat for a year and some how after countless wipes, bootloops, rom flashes and data mounting errors in twrp, was able to flash OOS 5.0 instead of the OOS 5.1.4 , coz flashing 5.1.4 directly from OOS 4.1.5 ,resulted in "error 7" everytime
Device status is unlocked boot loader, decrypted and rooted with magisk. But after this when i check with TWRP(3.2.3) ,i found that its unable to mount data partion again and cannot flash upadte on it or do anything else in twrp, tried to mount the data partion but that resulted in loosing OS again and had to repeat the whole process to Install OOS 5.0 .
Any Idea how i can update my phone further to 5.1.4 or beyond that?
Akarsh Adithya.K said:
Hello Guys Recently i decided to update my OP5 which was on rooted nougat for a year and some how after countless wipes, bootloops, rom flashes and data mounting errors in twrp, was able to flash OOS 5.0 instead of the OOS 5.1.4 , coz flashing 5.1.4 directly from OOS 4.1.5 ,resulted in "error 7" everytime
Device status is unlocked boot loader, decrypted and rooted with magisk. But after this when i check with TWRP(3.2.3) ,i found that its unable to mount data partion again and cannot flash upadte on it or do anything else in twrp, tried to mount the data partion but that resulted in loosing OS again and had to repeat the whole process to Install OOS 5.0 .
Any Idea how i can update my phone further to 5.1.4 or beyond that?
Click to expand...
Click to collapse
Hello, do you read this similar thread already https://forum.xda-developers.com/oneplus-5/help/oneplus5-ota-update-4-1-15-to-5-0-1-5-1-t3859695 ?
strongst said:
Hello, do you read this similar thread already https://forum.xda-developers.com/oneplus-5/help/oneplus5-ota-update-4-1-15-to-5-0-1-5-1-t3859695 ?
Click to expand...
Click to collapse
Yeah, i checked the thread, but mine is a bit different, coz mine is rooted and has TWRP recovery, and it took me many bootloops and flashs to figure out ,that i have to flash every single version of OOS, for example 4.1 to 5.0 and then, 5.0 to 5.0.4 and then 5.0.4 to 5.1 and on.
You get the point. But now i cant update after 5.0 , as TWRP throws this "unable to mount storage" error and my internal storage doesnt even show up in install section
Akarsh Adithya.K said:
Yeah, i checked the thread, but mine is a bit different, coz mine is rooted and has TWRP recovery, and it took me many bootloops and flashs to figure out ,that i have to flash every single version of OOS, for example 4.1 to 5.0 and then, 5.0 to 5.0.4 and then 5.0.4 to 5.1 and on.
You get the point. But now i cant update after 5.0 , as TWRP throws this "unable to mount storage" error and my internal storage doesnt even show up in install section
Click to expand...
Click to collapse
What twrp(link) do you have?
Did you format internal storage or not?
Don't bother with root until you have undated your os. Updating with twrp is also possible and I did it a lot of times.
strongst said:
What twrp(link) do you have?
Did you format internal storage or not?
Don't bother with root until you have undated your os. Updating with twrp is also possible and I did it a lot of times.
Click to expand...
Click to collapse
Its twrp 3.2.3 and yeah before installing rom , i did a full wipe of dalvik, data, system, internal storage and then did a data format too
Akarsh Adithya.K said:
Its twrp 3.2.3 and yeah before installing rom , i did a full wipe of dalvik, data, system, internal storage and then did a data format too
Click to expand...
Click to collapse
Please link the twrp file you're running. Als also you aware that twrp won't stick if you flash full oos rom?
strongst said:
Please link the twrp file you're running. Als also you aware that twrp won't stick if you flash full oos rom?
Click to expand...
Click to collapse
"https://dl.twrp.me/cheeseburger/twrp-3.2.3-0-cheeseburger.img.html"
Yeah i m aware of it and i flashed twrp back every time i finish flashing full OOS
Akarsh Adithya.K said:
"https://dl.twrp.me/cheeseburger/twrp-3.2.3-0-cheeseburger.img.html"
Yeah i m aware of it and i flashed twrp back every time i finish flashing full OOS
Click to expand...
Click to collapse
Please use the latest blu spark recovery which needs to be installed for the vendor partition from 5.1.4 https://forum.xda-developers.com/devdb/project/dl/?id=30332 or codeworks recovery. If you decrypt internal storage and did not flash no verity zip to stay decrypted, after first boot oos will encrypt interval storage.
strongst said:
Please use the latest blu spark recovery which needs to be installed for the vendor partition from 5.1.4 https://forum.xda-developers.com/devdb/project/dl/?id=30332 or codeworks recovery. If you decrypt internal storage and did not flash no verity zip to stay decrypted, after first boot oos will encrypt interval storage.
Click to expand...
Click to collapse
Its Decrypted , but do i have flash no verity zip, again after flashing twrp img
Akarsh Adithya.K said:
Its Decrypted , but do i have flash no verity zip, again after flashing twrp img
Click to expand...
Click to collapse
If you want to stay decrypted: yes
But first update your twrp, check if data partition is accessible, otherwise format internal storage - easiest way.
strongst said:
If you want to stay decrypted: yes
But first update your twrp, check if data partition is accessible, otherwise format internal storage - easiest way.
Click to expand...
Click to collapse
Thanks man strongst, it worked.
Changing recovery to blu spark twrp made all the difference, now i m on OOS 5.1.4
Akarsh Adithya.K said:
Thanks man strongst, it worked.
Changing recovery to blu spark twrp made all the difference, now i m on OOS 5.1.4
Click to expand...
Click to collapse
To help others mark this thread as [SOLVED] in the the title :good:
strongst said:
To help others mark this thread as [SOLVED] in the the title :good:
Click to expand...
Click to collapse
Yeah And one last question,
I tried ti update it to 5.1.5, using same process, and it throws boot loop, is there any other specifc order to flashing magisk and no verity, Or do i have to use other version of verity.
currently the one i m using is no verity v2
Akarsh Adithya.K said:
Yeah And one last question,
I tried ti update it to 5.1.5, using same process, and it throws boot loop, is there any other specifc order to flashing magisk and no verity, Or do i have to use other version of verity.
currently the one i m using is no verity v2
Click to expand...
Click to collapse
Flash full rom Update 5.1.4, then 5.1.5 then
Just make sure that vendor partition is mounted correctly within twrp, before flashing no verity v2 and after then magisk.
Now you can reboot the first time. If it won't help, you should format internal storage again when you have copied files into it like the rom zip. This can cause a bootloop sometimes.
strongst said:
Flash full rom Update 5.1.4, then 5.1.5 then
Just make sure that vendor partition is mounted correctly within twrp, before flashing no verity v2 and after then magisk.
Now you can reboot the first time. If it won't help, you should format internal storage again when you have copied files into it like the rom zip. This can cause a bootloop sometimes.
Click to expand...
Click to collapse
Again , thank you soo much man .
Turns out enabling that vendor portion after flash rom for no verity and magisk will cause no trouble
and now i m on OOS 5.1.5!!(uninstalling Magisk before flashing new update was important to).
Now that
how do i mark this thread as Solved.
Just updated to Oreo December patch. Is it true no-verity-opt-encrypt-5.1 is no longer needed before Magisk for rooting? I vaguely recall reading something like it.
Also, is factory wipe after TWRP before Magisk really needed?
I wish I wrote down the process from the last update. Angry at myself for forgetting.
goodjuju said:
Just updated to Oreo December patch. Is it true no-verity-opt-encrypt-5.1 is no longer needed before Magisk for rooting? I vaguely recall reading something like it.
Also, is factory wipe after TWRP before Magisk really needed?
I wish I wrote down the process from the last update. Angry at myself for forgetting.
Click to expand...
Click to collapse
Depends on if you want your data partition encrypted or not.
By default the device is encrypted or will encrypt data after flashing fastboot firmware. If you want the partition to be decrypted format data after installing TWRP and flash Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip after that. Boot your device, reboot to TWRP and flash latest magisk (18).
Normally Magisk itself should prevent the re-encryption but in my case that didn't happen.
A factory reset is not necessary but formatting data will erase your internal storage.
Wolfcity said:
Depends on if you want your data partition encrypted or not.
By default the device is encrypted or will encrypt data after flashing fastboot firmware. If you want the partition to be decrypted format data after installing TWRP and flash Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip after that. Boot your device, reboot to TWRP and flash latest magisk (18).
Normally Magisk itself should prevent the re-encryption but in my case that didn't happen.
A factory reset is not necessary but formatting data will erase your internal storage.
Click to expand...
Click to collapse
Thanks Wolfcity. I will leave the partition encrypted. I am writing down a step by step OTA process including my personal tweaks this time! No more relying on my memory and posting silly questions.