Hey Guys,
I installed an RRO theme and it caused my system ui to crash everytime it boots up ("Unfortunately, System UI has stopped"). Can't really go past "ok". So I booted into twrp, wiped system, data, cache, and dalvik, then proceeded to flash my rom again. I noticed that while the phone was booting, my optimization window was still themed. Once it fully booted up, I got the same system ui crash message due to the overlay still being present. I've tried wiping everything numerous times but to no avail. Am I doing something wrong? I thought wiping /system would get rid of everything. Any help would be greatly appreciated!
[UPDATE]
Nevermind, I got it.
Just in case anyone was wondering, I basically mounted vendor, then went into the vendor folder where all the overlays were located. I proceeded to delete them all, which fixed my problem. I thought that folder was located in /system/vendor/overlay but it was located in the top most /vendor folder for me.
Hi, I have the same problem. Could you elaborate or how you mounted vendor and then went into the vendor folder to delete the overlays?
I'm using TWRP but I don't know how to mount vendor. I went into "mount" to check the vendor box and then rebooted but it just went back to the "unfortunately, System UI has stopped" loop.
X_Fact0r said:
Hi, I have the same problem. Could you elaborate or how you mounted vendor and then went into the vendor folder to delete the overlays?
I'm using TWRP but I don't know how to mount vendor. I went into "mount" to check the vendor box and then rebooted but it just went back to the "unfortunately, System UI has stopped" loop.
Click to expand...
Click to collapse
Even easier - just fastboot flash vendor image
X_Fact0r said:
Hi, I have the same problem. Could you elaborate or how you mounted vendor and then went into the vendor folder to delete the overlays?
I'm using TWRP but I don't know how to mount vendor. I went into "mount" to check the vendor box and then rebooted but it just went back to the "unfortunately, System UI has stopped" loop.
Click to expand...
Click to collapse
You don't reboot after mounting vendor.
After you mount go to the file explorer in twrp and search there.
Sent from my Nexus 6P using Tapatalk
if you have a file manager, go into the root directory and delete the Vender folder and boot into recovery and wipe system...
I have the same issue like you except when I try to delete in the file manger I get a error=1.
This is what I did
1. Boot twrp
2. Mount --> Mount vendor
3. Advanced --> File Manager
4. Root directory --> Vendor --> Overlay
5. Delete & Reboot
System ui is not working
Hi I'm having that problem right now. I tried flashing android n using twrp and when it booted it up, I get a "system ui is not working." When I tried to boot into recovery, I noticed that twrp is no where to be found. Please help, this is my daily driver and I have no spare phone. As of right now I'm trying to fix it using a root toolkit but no luck. My bootloader is unlock.
Kentran5397 said:
Hi I'm having that problem right now. I tried flashing android n using twrp and when it booted it up, I get a "system ui is not working." When I tried to boot into recovery, I noticed that twrp is no where to be found. Please help, this is my daily driver and I have no spare phone. As of right now I'm trying to fix it using a root toolkit but no luck. My bootloader is unlock.
Click to expand...
Click to collapse
Use fastboot to flash the newest version of TWRP. it supposedly works with encryption
Sent from my Nexus 6P using Tapatalk
Related
Hi, today i wanted to do a factory reset and clean install my phone
im using TWRP 2.3.3.3
after factory reset in the wipe menu, at the end i see a line E:/error opening '/data/lost+found'
basically i know what does lost+found folder does in linux, but i forgot whether i have seen such error line before when i do factory resets.
in the file manager of TWRP i then see /media and /lost+found in the /data partition. when pressing into /lost+found, TWRP cannot open it
after this, wiping /system will also give me the same message at the end even it is "Done", as well as cache and dalvik, etc
then i go on flash rom, gapps, kernel, after 1 or 2 boots i go back to recovery and wipe cache, there are no such line anymore
however there is now TWO /lost+found folder in my /data partition
is this a normal behaviour? i didnt pay attention but are there 2 lost+found folders in /data partition for everyone else too?
i have backed up my sdcard and is ready for a /data wipe, any advice is appreciated. thanks in advance!
update: well really hasnt seen it anywhere tried very hard searching on google
maybe just **** happens sometime as i rushed updating the su binary together with restoring android ID in titanium backup altogether without carefully rebooting etc.
factory reset, formating every partition for N times didnt help. returned to completely stock (unlocked bootloader ofcourse), flash twrp 2.3.3.3 clean and no more that line anymore after factory reset. hell gonna start my sdcard restore now...
Miasmic said:
update: well really hasnt seen it anywhere tried very hard searching on google
maybe just **** happens sometime as i rushed updating the su binary together with restoring android ID in titanium backup altogether without carefully rebooting etc.
factory reset, formating every partition for N times didnt help. returned to completely stock (unlocked bootloader ofcourse), flash twrp 2.3.3.3 clean and no more that line anymore after factory reset. hell gonna start my sdcard restore now...
Click to expand...
Click to collapse
I was researching google for this same exact error message, when I came across your thread. I doubt you are still having this issue, but I wanted to reply with the solution in case anyone else comes across this post. I was able to solve this error message by installing a new ROM. It doesn't matter which one you install, any will do. Then open your file manager of choice, of course one which can go up to root level. Browse to /data, and then you should notice that you do not have a lost+found folder. However, you should see a lost+found file, all the way at the bottom. I renamed this file to lost+foundOLD, and then created a new folder called lost+found. Next, reboot into recovery and once again wipe both caches, system and factory reset. You should no longer get the lost+found error. Make sure to fix permissions as well to make sure.
just had this issue and was solved by dropping back to twrp 2.4.x.x and doing data format.
misspost
mitchallica said:
I was researching google for this same exact error message, when I came across your thread. I doubt you are still having this issue, but I wanted to reply with the solution in case anyone else comes across this post. I was able to solve this error message by installing a new ROM. It doesn't matter which one you install, any will do. Then open your file manager of choice, of course one which can go up to root level. Browse to /data, and then you should notice that you do not have a lost+found folder. However, you should see a lost+found file, all the way at the bottom. I renamed this file to lost+foundOLD, and then created a new folder called lost+found. Next, reboot into recovery and once again wipe both caches, system and factory reset. You should no longer get the lost+found error. Make sure to fix permissions as well to make sure.
Click to expand...
Click to collapse
No his error and mine are different. We have two lost+found dir and no file. If i delete them and make new lost+found folder. It automatically makes 2.
I am having this same problem. I just did a restore to my last backup, but it in TWRP it says mentions the error over and over again. I looked in /data and I found about 10 files called lost+found, but I do not have any folders. Any suggestions?
Full Format data worked for me
NVijapura said:
I am having this same problem. I just did a restore to my last backup, but it in TWRP it says mentions the error over and over again. I looked in /data and I found about 10 files called lost+found, but I do not have any folders. Any suggestions?
Click to expand...
Click to collapse
I just encountered this problem after updating a CM nightly and it bricked my phone. Restoring from a nandroid backup would ultimately fail and I was getting all kinds of weird problems (stuck in boot loop, graphics appearing garbled, etc). After looking closer at the logs during restore, I noticed E:/error opening '/data/lost+found' appearing several times, an then it would indicate 'done' and restart but would end up with the same problems.
Even after doing a factory reset, I had no luck in restoring my phone. So I did a factory reset again and installed a CM stable release thinking maybe my ROM / backup was messed up but noticed the same E:/error opening '/data/lost+found' message. However, this time around I managed to get booted far enough where I could connect via USB and backup files from my internal memory to my computer.
At this point I booted into recovery (TWRP 2.5.0.0) and did a full wipe including internal SD using the Format Data option, whereupon I was able to install the CM stable release without issue - no more lost+found error! I then upgraded to the nightly version of my backup and restored with success. Long and stressful night...
szurheal said:
I just encountered this problem after updating a CM nightly and it bricked my phone. Restoring from a nandroid backup would ultimately fail and I was getting all kinds of weird problems (stuck in boot loop, graphics appearing garbled, etc). After looking closer at the logs during restore, I noticed E:/error opening '/data/lost+found' appearing several times, an then it would indicate 'done' and restart but would end up with the same problems.
Even after doing a factory reset, I had no luck in restoring my phone. So I did a factory reset again and installed a CM stable release thinking maybe my ROM / backup was messed up but noticed the same E:/error opening '/data/lost+found' message. However, this time around I managed to get booted far enough where I could connect via USB and backup files from my internal memory to my computer.
At this point I booted into recovery (TWRP 2.5.0.0) and did a full wipe including internal SD using the Format Data option, whereupon I was able to install the CM stable release without issue - no more lost+found error! I then upgraded to the nightly version of my backup and restored with success. Long and stressful night...
Click to expand...
Click to collapse
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
scwied17 said:
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
Click to expand...
Click to collapse
That worked perfectly. Thanks!!!
scwied17 said:
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
Click to expand...
Click to collapse
Worked perfect for me. Very easy to miss that simple "Format Data" button in TWRP. Simply type 'yes' and problem solved.
I think I got this error when I flashed SlimKAT 4.4 over on my P880 and I had the USB cable plugged in and the partitions mounted (as I had just transferred the install.zip to my phone)
leijonasisu said:
Worked perfect for me. Very easy to miss that simple "Format Data" button in TWRP. Simply type 'yes' and problem solved.
I think I got this error when I flashed SlimKAT 4.4 over on my P880 and I had the USB cable plugged in and the partitions mounted (as I had just transferred the install.zip to my phone)
Click to expand...
Click to collapse
Can i get some help please. I cant format data via TWRP, it says "E: unable to wipe data, unknow fle system, auto, unable to format to remove encryption". I did not put any encryption. What to do?
Earlier today I (stupidly) misclicked on an update that LG was trying to send out. Once clicked, the phone rebooted to TWRP and sat there for a while. i then tried to restore an old backup I had, but it was unable to mount system. I also cannot click the box for system in the mount part of TWRP, and the permissions cant be fixed because of being unable to mount the system. Is there any way i can push the system or something?
falconfan101 said:
Earlier today I (stupidly) misclicked on an update that LG was trying to send out. Once clicked, the phone rebooted to TWRP and sat there for a while. i then tried to restore an old backup I had, but it was unable to mount system. I also cannot click the box for system in the mount part of TWRP, and the permissions cant be fixed because of being unable to mount the system. Is there any way i can push the system or something?
Click to expand...
Click to collapse
I did the same thing. Could use any help.
falconfan101 said:
Earlier today I (stupidly) misclicked on an update that LG was trying to send out. Once clicked, the phone rebooted to TWRP and sat there for a while. i then tried to restore an old backup I had, but it was unable to mount system. I also cannot click the box for system in the mount part of TWRP, and the permissions cant be fixed because of being unable to mount the system. Is there any way i can push the system or something?
Click to expand...
Click to collapse
Both your guys best bet is to flash stock ROM through download mode... I keep those files on my computer ..lol I actually delete all backup files when I find q stable ROM just so I can have the space
@dmkern
Hi
I'm having this very weird issue with my phone (A2017G). I unlocked BL, installed TWRP, updated to TWRP 3.0.3-1, formatted data, factory reset, install A2017G_Nougat_Bootloader+ModemFix, factory reset again, install LineageOS and then boot. The device booted fine.
I noticed root wasn't built-in so I flashed SuperSU V2.65. After a reboot, my phone won't let me boot into the system anymore. I get asked for a password. Whatever password I enter, it says "Decryption Unsuccesful. The password is correct, but data is corrupt". When I reboot to TWRP and format data and then factory reset, nothing changes. I keep getting the prompt before system boots. Even re-flashing the bootstack and lineageOS doesn't help. I know flashing anything else will brick my phone, so I refrained from doing that.
What am I doing wrong here?
Note that TWRP reads both my internal storage and my SDcard. However, internal storage contains only the folder "TWRP". When I go up a level, I can see the normal folders like "boot", "cache", "data", "dev" and so on. In the "backup" menu, DATA also shows as "0MB"
File system says "f2fs". Do I repair/change it?
Thanks
Ah,
I have/had the same error. Looks like this needs to be changed to ext4.
CU
Joerg
Controllerboy said:
Hi
I'm having this very weird issue with my phone (A2017G). I unlocked BL, installed TWRP, updated to TWRP 3.0.3-1, formatted data, factory reset, install A2017G_Nougat_Bootloader+ModemFix, factory reset again, install LineageOS and then boot. The device booted fine.
I noticed root wasn't built-in so I flashed SuperSU V2.65. After a reboot, my phone won't let me boot into the system anymore. I get asked for a password. Whatever password I enter, it says "Decryption Unsuccesful. The password is correct, but data is corrupt". When I reboot to TWRP and format data and then factory reset, nothing changes. I keep getting the prompt before system boots. Even re-flashing the bootstack and lineageOS doesn't help. I know flashing anything else will brick my phone, so I refrained from doing that.
What am I doing wrong here?
Note that TWRP reads both my internal storage and my SDcard. However, internal storage contains only the folder "TWRP". When I go up a level, I can see the normal folders like "boot", "cache", "data", "dev" and so on. In the "backup" menu, DATA also shows as "0MB"
File system says "f2fs". Do I repair/change it?
Thanks
Click to expand...
Click to collapse
I would say the answer lies with issues between f2fs and SuperSU
https://www.xda-developers.com/xda-...upersu-has-trouble-with-f2fs-data-partitions/
Sent from my SM-P600 using XDA-Developers Legacy app
And you flash the wrong SuperSU, the one needed is either v.2.79 or v.2.79-R3. try booting back to TWRP and clean Flash Lineage again and flash either one of the SuperSu I Mention before.
I have the same after install unofficial lineage 14.1 'decryption unsuccessful'
On TWRP 3.0.3-1 I go in 'wipe', then 'advanced wipe' and select 'Data', press 'Repair or Change File System' and then 'Change File System' to EXT4
That's work fine on my 2017G
For root
download.lineageos.org/extras
The arm64 zip
After install with TWRP go in deployment options and activated it!
Lineage is running with root
Thanks, everyone. That worked. I was quite worried for a while, I really don't want tot RMA the device a second time due tot me messing things up.
Where do I find the options in Twrp for deployment
jdg007 said:
Where do I find the options in Twrp for deployment
Click to expand...
Click to collapse
Twrp have no deployment option, what won't you to do.
joergwrage said:
Ah,
I have/had the same error. Looks like this needs to be changed to ext4.
CU
Joerg
Click to expand...
Click to collapse
Probably it is caused by a known bug in the f2fs implementation in the kernel. Only @Unjustified Dev can solve it. Some people who already was using f2fs with TWRP 3.0.4 and LineageOS 13.1 are not having those issues and they were able to dirty flash the new LOS 14.1.
Updating to TWRP 3.0.3-1 is very recommended. TWRP 3.0.2 has some problems when flashing zips. SuperSU is one of them.
i Also need help guys :/ my auto rotate isnt working. neither is mu auto brightness :/
crazynitro said:
i Also need help guys :/ my auto rotate isnt working. neither is mu auto brightness :/
Click to expand...
Click to collapse
I have the same
Hi
I unlocked the bootloader and installed TWRP as described in the tutorials here. I then also flashed SuperSU. Afterwards I booted into stock Android and it worked. I wanted to do a factory reset so that after reinitializing I could install all my apps automatically. I went into TWRP --> Wipe --> Slide to Wipe. After rebooting it asked me for the pincode to decrypt. Since that didn't work I wiped everything except the SD Card and flashed lineage. Since then, my G6 keeps booting into TWRP. I even tried AquariOS (randomls chosen ROM) and I have the same results. I checked into "backup" in TWRP and the system partition is about 1GB. I then wiped it, and it went down to almost 0 I think. I then reflashed lineage and it was again at almost 1GB. So as it seems it is writing something. I then went into "mount" and system was not selected. I checked it and "mount system partition as read only", rebooted into the system, and it booted into TWRP again, system was unchecked under mount, but the read-only option was still checked. tried the same without the read-only option, same result. So now my G6 keeps mounting into TWRP instead of the ROM.
Any ideas what I can do?
Format data in recovery, don't wipe. It will disable encryption. Flash stock 14a again and see if you can get it to boot
I fixed it, somehow TWRP was messed up. I redownloaded it and reflashed it and then it worked
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?