Related
Hey all,
I have an S4 i337m model. I've installed a custom ROM that is essentially a rooted stock ROM (I do not remember the exact build/version of the ROM). I realize having this info would be useful, but at the moment, I cannot access this info.
While running this ROM, everything was fine. Last week Friday, I attempted to install FoxHound 1.6. Had to play around with the installation options, but I got FoxHound to work. However, I need to get back on my old ROM as I needed some files that were deleted during the FoxHound install. So I wiped my phone, and restored my nandroid backup of my rooted stock ROM. again, everything was fine. No issues.
Here is where the problem is; after restoring my rooted stock ROM, I could boot into the phone and access the files needed. However, when I reboot/shut down phone, upon restarting/powering up, my phone is stuck at the 'Samsung Galaxy S4' logo right after power on. So, I boot into recovery (the latest version of TWRP) and I navigate to 'file manager' to take a look at my storage/files. And this is where I believe the issue to be; I see virtually no files at all. I can see many folders/partitions, but there are virtually no files anywhere (i.e. the system and data partitions are empty). I am assuming this is the reason why my phone doesn't boot past the Samsung Galaxy S4 logo. Now, when this happens, I wipe my phone again and restore my working nandroid backup. Everything works fine. I can get back into Android without issues. Until I reboot/power off my phone. Then this happens all over again.
I believe I may have damaged(?) the partition(s). When I installed FoxHound, I also installed an option during installation titled 'EXT4'. I know linux uses ext2/3/4 partition tables. Did I damage my storage/partition by installing EXT4 from FoxHound? Do I need to repartition my phone via Odin PIT file or something similar? Am I totally wrong with my analysis? Any help/advise/insight would be very welcomed.
Thanks
Additional info
Baseband: I337MVLUAMG1
Build number: JDQ39.I337MVLUAMG1
ROM: Rooted stock ROM 4.2.2 (with some bloatware removed)
While my phone was in the it's 'logo stuck' state, I entered into TWRP and selected the Wipe option, then Format Data. I must select 'Format Data' in order for my phone to work on it's next boot. Manually formatting System, Data, etc... will not allow my phone to boot up at next boot. And, my phone will only work on the next boot. If I power off/restart phone, it will get stuck at the logo again. So my phone is only good for 1 boot up after a wipe.
And, after I restore a working backup and boot into the phone, everything works until next power down/reboot. Once I power down/reboot phone, I must go into recovery since it will not boot into Android. When I get into TWRP, I see that my Internal Storage has 0MB free and I am unable to see any files. I can see folders/partitions, but there is nothing in any folder/partition. My external SD card shows nothing as well. My external SD card however is unaffected as all the data is still there once I get into Android and look around.
Also, I just restored a backup I had before I was having this issue. After restoring and rebooting, the same thing happens. I get stuck at the 'Samsung Galaxy S4' logo.
So I'm guessing there is some partition troubles here. Maybe I'm wrong, but I'm scratching my head as to the cause of this problem.
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
jd1639 said:
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
Click to expand...
Click to collapse
I thought the same thing. I'm downloading the stock ROM now and will give it a try.
One other thing I noticed during my last restore/fix attempt... After I perform a wipe -> Format Data (from TWRP), I notice that it reverts to my rooted stock ROM without me restoring anything. So, after I do a full wipe/format, and reboot my phone immediately after the full wipe/format, my phone will boot into the rooted stock ROM. I thought that wiping/formatting via TWRP totally cleans the internal storage of all data. So how can I be booting into any ROM after a wipe?
Unless I'm mistaken in my thinking and the full wipe/format option in TWRP just reverts back to the stock ROM I had installed prior to installing further custom ROMs?
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Do not format data in twrp.
jd1639 said:
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Click to expand...
Click to collapse
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
xBeerdroiDx said:
Do not format data in twrp.
Click to expand...
Click to collapse
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Talabis said:
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Click to expand...
Click to collapse
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
jd1639 said:
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
Click to expand...
Click to collapse
Is TWRP 2.5.0.0 ok to use?
Ok... It's really starting to look like my partition table has been damaged. Every time I flash a new ROM or restore a nandroid backup successfully, and then restart my phone, I get stuck at the S4 logo. Upon starting recovery, my internal storage reads 0MB free. It seems like my partition table is becoming corrupt after a reboot, or it has already been corrupted.
I tried flashing the stock ROM for my phone (I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar is the one I used), but that didn't help at all. After installing this stock ROM, and I go into stock recovery, I get an error: E:failed to mount /data (invalid argument).
This really is looking like a partition problem. Is there some way to re-partition my phone? I remember a PIT file was used to partition my old Galaxy S i9000. Is there a PIT file for the S4 i337m?
I would also like to try CWM but I am having a hard time finding a ODIN flashable version.
I wouldn't mess with a pit file and I haven't seen one anyway. It's sounding more and more like your memory is bad. I'd keep it stock and see if you can get an exchange on the phone under warranty.
Further investigation has lead me to the culprit... sorta. It's my /data partition that is screwing everything up. If I format /data and then reboot, I can get into my phone. But if I reboot again, then my /data partition becomes corrupt and my phone hangs at the S4 logo. And then if I go into recovery, I can see that my internal storage is at 0MB free.
However, after formatting/restoring /data partition and rebooting into android successfully, everything works fine. If I reboot from this point and enter recovery, I am still able to see my /data partition and files. At this point, everything seems to be fine. Once I reboot out of recovery and let the phone boot into Android, I get stuck at the S4 logo and my /data partition screws up/becomes corrupt. It looks like my /data partition is only becoming corrupt after the 1st successful boot into Android. If I enter recovery after the 1st successful android load, I am still able to see all files and partitions. It is only trying to load android after the 1st boot that my /data partition becomes corrupt. Very strange...
So, I can always boot into my phone as long as I format my /data partition prior to loading Android. Anyone experience this before? Any ideas? I realize my memory may be damaged, but I'm leaving that as a last resort possibility since my phone was working fine up until I started installing FoxHound with the EXT4 option as well as installing 1 or 2 of the kernel's FoxHound provides. Namely Adam kernel is the one I tried.
All good... I think/hope
Well, I think I got the problem solved. After toying with this thing all day. It seems like TWRP 2.6 was the problem in some sense. Looks like TWRP 2.6 does not format the /data partition correctly. I had to get restore/install a working ROM, boot into my phone and install ClockworkMod Recovery via ROM Manager. I then used CWM to format /data. Once I did this, and loaded back into my phone, and went through the setup process since /data was formatted, everything was working fine. I just rebooted 5 times and shut down twice and my phone booted back up into android without issue.
So as one user in this thread had mentioned, formatting /data with TWRP 2.6 was the problem.
Hope this helps others avoid a similar issue.
Thanks everyone for all the help. It pointed me in the right direction.
Glad you got it fixed.
I'll be giving these steps a try, having somewhat of the same problem!
i've been having this exact same problem but with TWRP 2.5.0.2 since July. Its been driving me insane and I have not been able to find any one else having this issue until now. I think i might finally try CWM instead as a last measure before I finally give up!
Try TWRP 2.6.3.1 version. It works pretty well even though it's unofficial http://forum.xda-developers.com/showthread.php?t=2262996
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Sorry ppl, need some spoon feeding. I have searched but to not avail.
I unlocked my 6p, flash TWRP and installed chroma rom + despairs kernel. All was fine in TWRP
But when I boot into the TWRP after installing my apps, it says password to decrypt and I skip that but allowing it to mod system files. Tried to install zip but internal storage shows 0mb. Can't seem to find my files in SD card folder
My phone is still encrypted.
Never experienced such issues with my nexus 6. Any help?
Chroma works perfectly
Make sure you have the latest version of TWRP for the 6p. Initially it only worked if you decrypted, but a few weeks ago a newer version was released that does not require decryption and will see your files.
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
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?
I did the exact same method as mentioned in this [site](https://samarv-121.github.io/twrp-3.2.3-RMX1801/), but TWRP isn't reading the microSD slot. It gives 0 MB as the size of microSD and I can't select it. Also, it seems to me that TWRP starts from the beginning every time I boot to recovery as I'm getting the 'Allow modifications to system partition' in every boot. I tried wiping the data twice, which removed the internal storage data encryption, but when I booted back to TWRP, it showed it as 0 MB. I've also flashed TWRP several times, but to no avail. One thing that I noticed was that when I flashed TWRP the first time, it showed success, but when booting to recovery, it had stock recovery. I flashed TWRP again and that issue was fixed.
My microSD is FAT32 format, and its contents aren't encrypted. I'm able to read the contents of it on PC and in my phone, but not in recovery. However, when in TWRP, it shows that my SD card is vfat format. I can't wipe it, repair it or change the filetype, as its showing an error.
Can someone please help me out? I'll provide whatever resources are needed. But please tell a detailed way on how to get them. Thank you in advance!