Related
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.
I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?
I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data
prospektus said:
I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data
Click to expand...
Click to collapse
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?
thrustaxehandle said:
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?
Click to expand...
Click to collapse
yes.. delete internal memory. rom board. format data.
thrustaxehandle said:
I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?
Click to expand...
Click to collapse
You need to upgrade to a higher version for twrp. 3.2.2
prospektus said:
yes.. delete internal memory. rom board. format data.
Click to expand...
Click to collapse
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
esiv129 said:
You need to upgrade to a higher version for twrp. 3.2.2
Click to expand...
Click to collapse
I'm already using TWRP version 3.2.3
thrustaxehandle said:
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
I'm already using TWRP version 3.2.3
Click to expand...
Click to collapse
try again unlock
prospektus said:
try again unlock
Click to expand...
Click to collapse
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.
thrustaxehandle said:
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.
Click to expand...
Click to collapse
When you get the mount error, come to the home page and get to the mount. speak enable all options enable all options. speak restart recovery restart recovery. make format data
Not sure if the link is forbidden? I can't tell you sorry. https://www.youtube.com/watch?v=dzrWkjOfndA&t=501s
I have read replies and everyone is sharing his bit of suggestions, here are mine
1. boot redwolf as FASTBOOT BOOT recovery.img - (if you arent already)
2. change file type of /data partition to-from (xFat to ext4) and wipe all partitions (internal storage can be skipped)
3. instead of linage15.1 same package, try downloading some other custom rom, i recomend DotOS2.5 or Crdroid4.6.2
4. uncheck enforce md5 bla bla while flashing zip.
i hope you will succeed
So I've been running Oreo Omnirom and I'm looking at moving to Android Pie. I have never installed any of the OnePlus Beta's or any other Pie based ROM.
I am currently running TWRP version twrp-3.2.3-0-20180822-codeworkx-dumpling and from the date code, it looks like to could be a little old. When I jump into TWRP, I get errors that no vendor partition is found.. I have always ignored this as I was on Oreo and didn't need/care about a vendor partition. This also led me to believe that the version of TWRP I am using support the vendor partition.
Is there an easy way to create and format the vendor partition? Is my TWRP version too old? I tried running twrp-3.1.1-x_blu_spark_v8.55-op5_op5t as recommended in another thread (even tho it's older) and I had to re-flash TWRP via fastboot because that IMG file no worky...
I am trying to avoid formatting my data since my phone has a larger drive than my computer. If someone could point me in the right direction, it would be very much appreciated.
Flashing twrp-3.1.1-x_blu_spark_v8.55-op5_op5t or twrp-3.2.3-0-20190311-codeworkx-dumpling.img (both TWRPs for PIE) wont boot to recovery. Both boot to a blank screen with the notification LED turned blue. I assume that this is because I am still on Oreo firmwares... Seems like I have a chicken and egg sort of situation going on here....
Flashed OxygenOS_5.1.4 full OTA. /vendor partition was not created, but I only booted until I reached the lockscreen at which point told me that my password was incorrect. Do I need to remove my lockscreen password in Omni and try again?
crakerjac said:
Flashed OxygenOS_5.1.4 full OTA. /vendor partition was not created, but I only booted until I reached the lockscreen at which point told me that my password was incorrect. Do I need to remove my lockscreen password in Omni and try again?
Click to expand...
Click to collapse
Remove your security before flashing anything and then try 5.1.4 full OOS zip. If that works, great. OTA up to latest, or as far as it will allow and then use the full zip files available in the forum to get onto latest Pie. You'll need to fastboot flash latest Pie TWRP (codeworkx) when you get up to date.
If you run into security problems you might have to try a clean flash, or even format. Make sure you are in front of your PC before beginning and backup everything.
Still having no luck here.
Here is what I have done to try and get TWRP to recognize a /vendor partition:
Formatted Data
Side loaded OnePlus5TOxygen_43_OTA_037 in TWRP
Flashed OTA_037
Booted OxygenOS and completed setup
Rebooted to bootloader
Flashed twrp-3.2.3-0-20180822-codeworkx-dumpling
Rebooted to TWRP recovery
At this point I am STILL getting 'Failed to mount '/vendor' (invalid argument)'.
WTF am I doing wrong? How to I create a /vendor partition?
crakerjac said:
Still having no luck here.
Here is what I have done to try and get TWRP to recognize a /vendor partition:
Formatted Data
Side loaded OnePlus5TOxygen_43_OTA_037 in TWRP
Flashed OTA_037
Booted OxygenOS and completed setup
Rebooted to bootloader
Flashed twrp-3.2.3-0-20180822-codeworkx-dumpling
Rebooted to TWRP recovery
At this point I am STILL getting 'Failed to mount '/vendor' (invalid argument)'.
WTF am I doing wrong? How to I create a /vendor partition?
Click to expand...
Click to collapse
hi, may be this will help you, see post #2 from this thread:
"..... (because 5.1.4 creates the vendor partition and 5.1.5 fills ot)"
https://forum.xda-developers.com/oneplus-5t/help/solved-twrp-error-7-vendor-partition-t3846181
My thought process was that if 5.1.4 creates the /vendor partition, then TWRP should still be able to recognize it and mount that partition... I'm not sure if I care if it's full or empty at this point... I fear that I will download another 1.6GB of data just to find that the update wont happen because /vendor cannot be found... Unless I am completely wrong...
Well dang... I was wrong. Flashing 5.1.5 patched the /vendor partition and removed the error in TWRP.
Thanks for the help guys.
Mods please close (solved).
Hello.
Tried flashing older stock rom via TWRP.
TWRP installed fine, worked fine, flashed vbmeta, still everything worked.
Downloaded ROM, put it into the sd card, went into twrp, formatted data, rebooted into twrp again, wiped Dalvik/ART cache, cache, system, vendor and internal memory, tried flashing, gave error 7, with "mkdir folder file not existing or whatever". In twrp i went into terminal, made a directory /cache/recovery, tried flashing, worked. Wiped dalvik and when i tried to reboot, the backlight turns on for a split moment and then it turns off.
Recovery does the same, and fastboot lights up the screen with the image of fastboot but it turns off. Plugging it with the usb makes it so it repeatedly turn on backlight and off again.
What does this mean? Device dead? Any help?
Thank you.
Maybe try flashing a custom rom
With what tools if I may ask? Any advice you can give me?
Fastboot doesn't stay on like it should, the screen just flashes the fastboot picture and it restarts again. Recovery does the same.
Try following bliss rom guide with installation of twrp
Trying to do anything with ADB tools just gives me a "< waiting for any device >".
I'm sure there's other ways of flashing twrp
VirusWar said:
Hello.
Tried flashing older stock rom via TWRP.
TWRP installed fine, worked fine, flashed vbmeta, still everything worked.
Downloaded ROM, put it into the sd card, went into twrp, formatted data, rebooted into twrp again, wiped Dalvik/ART cache, cache, system, vendor and internal memory, tried flashing, gave error 7, with "mkdir folder file not existing or whatever". In twrp i went into terminal, made a directory /cache/recovery, tried flashing, worked. Wiped dalvik and when i tried to reboot, the backlight turns on for a split moment and then it turns off.
Recovery does the same, and fastboot lights up the screen with the image of fastboot but it turns off. Plugging it with the usb makes it so it repeatedly turn on backlight and off again.
What does this mean? Device dead? Any help?
Thank you.
Click to expand...
Click to collapse
i think it's dead
-when the twrp gave you the error you should log it
-you should format data after flashing a rom ,not before (and only few roms require it)
your only option is flash VBMETA then TWRP again and see if it work
use the unofficial twrp : (3.3.10)
https://forum.xda-developers.com/re...ecovery-unofficial-twrp-xiaomi-redmi-t3997267
You should have formatted data partition after flashing the rom(not manually create those folders). You would be okay.
Any solution?
Hello all.
The phone had an older unofficial LOS build installed (lineage-17.1-20200808-UNOFFICIAL-ginkgo.zip) but Bluetooth wasn't working.
I tried to install "lineage-17.1-20210927-nightly-ginkgo-signed.zip" via TWRP: I formatted DATA, then did a standard wipe, then installed via zip file on physical 64GB SD Card. But after rebooting I see the LOS animation for about 3.5 minutes then the phone reboots back to TWRP.
I installed official MUI (miui_GINKGOGlobal_V12.0.6.0.QCOMIXM_cfcf7038bd_10.0.zip) just to see if it will work and it booted without problems (and BT is working).
I tried LOS again, still doesn't work. I tried wiping EVERYTHING, including system, still the same. I tried with the LineageOS recovery - still the same but this time when it gets me back to recovery I get a message saying it failed and asking to try format DATA. I agree and let it do the format but still the same result.
I don't know what else to do and I need a phone because mine is broken!
Any advice?
C4lculated said:
Hello all.
The phone had an older unofficial LOS build installed (lineage-17.1-20200808-UNOFFICIAL-ginkgo.zip) but Bluetooth wasn't working.
I tried to install "lineage-17.1-20210927-nightly-ginkgo-signed.zip" via TWRP: I formatted DATA, then did a standard wipe, then installed via zip file on physical 64GB SD Card. But after rebooting I see the LOS animation for about 3.5 minutes then the phone reboots back to TWRP.
I installed official MUI (miui_GINKGOGlobal_V12.0.6.0.QCOMIXM_cfcf7038bd_10.0.zip) just to see if it will work and it booted without problems (and BT is working).
I tried LOS again, still doesn't work. I tried wiping EVERYTHING, including system, still the same. I tried with the LineageOS recovery - still the same but this time when it gets me back to recovery I get a message saying it failed and asking to try format DATA. I agree and let it do the format but still the same result.
I don't know what else to do and I need a phone because mine is broken!
Any advice?
Click to expand...
Click to collapse
do a clean flash and don't forget DFE