Database Info

problem on android phone "failed to mount system invalid argument"

I heve edited the system.img.ext4 on samsung galaxy mini 2
and after i have flashed the phone i receive this error :
failed to mount system invalid argument
Flashing the system back with original phone works
What is causing this error?

grigoreee said:
I heve edited the system.img.ext4 on samsung galaxy mini 2
and after i have flashed the phone i receive this error :
failed to mount system invalid argument
Flashing the system back with original phone works
What is causing this error?
Click to expand...
Click to collapse
Well, it really depends on your edit.

I have mounted system.img.ext4 and removed some files from it then i have recreated the image and flashed to phone but i receive this error when the phone starts.

re install the firmware or install a new one....that should serve the purpose

the phone is working when i flash the original fw but i want my modded system.img.ext4
with the modified system i receive this:
Not need checksum confirmation already executed!!... (this is normal )
then:
E:failed to mount /system (invalid argument)

@grigoreee - I have the same problem like You with system...
Do You found any solution?
I think that replace boot.img from this thread:
Code:
http://forum.xda-developers.com/showthread.php?t=1719699
end's in the same way

How did u guys extract the system.img.ext4?
using dd?

I use this method:
Code:
http://forum.xda-developers.com/archive/index.php/t-1588461.html
(in mini2 system is mount with the same parameters as described above)

No solution for this error?
I still receive the same error......

grigoreee said:
No solution for this error?
I still receive the same error......
Click to expand...
Click to collapse
try to format /system partion from cwm in mount and storage

HTC Sensation: Can't install zip from SD card & WiFi "Error" stopped working.

HTC Sensation: Can't install zip from SD card & WiFi "Error" stopped working.
Hello
I recently rooted my HTC Sensation (Pyramid) Z710e using KINGORoot and it was a successful root, unlocked bootlader and got SuperUser.
Security is still on (S-ON) as I don't need or wish to turn this off.
I have tried using CWM recovery 5.8.0.9 but flashing the ROM which was MADE for the Pyramid failed, then I tried using TWRP 2.1.0 but I got the same result, and then I also tried CWM recovery 5.0.2.0 but still the same result (error below).
The problem: When I try flashing a new custom ROM after doing data wipe, cache wipe and dalvik cache wipe it gives me the following error message:
' E: Error in /sdcard/'zipname'.zip
(Status 0 )
Installation Aborted. '
All recoveries downloaded were specific to my phone (obvoiusly) so all were named with Pyramid in them (ex. "twrp-pyramid-2.1.0.img") and so were the custom ROMs, specific to the sensation.
I read something about changing the META-INF File from the new ROM zip to a working META-INF file for the Pyramid but when I tried this it didn't work either, got me an error Status 1 message if I remember correctly.
I'm currently running a downloaded zip of ICS (Ice Cream Sandwich) Android 4.0.3 which is like the OS I had before I formatted everything except SD Card. However my WiFi isn't working anymore since I flashed this downloaded ICS zip and what I mean by not working I mean that when you flip the switch to turn WiFi on it flips to On and then to Off again immediately, and in the settings menu it says there's an Error, but that's it. I tried using the Wifix manager app with the code but that didn't work at all.
Any help is greatly appreciated as to what I can do regarding why I can't install a zip successfully from recovery or as to how I can fix my WiFi problem on my Sensation.
Thanks

Hello
Please wait for the moderation team to move this thread to relevant section.
Do register an account on xda for better access and privileges.
Have a good day !

Flash the boot.img of the rom via fastboot command
The command is fastboot flash boot boot.img
And I suggest to use 4ext recovery since you are on S-ON

Still not working :/
Thank you for the reply
Ok I did what you said, I'm currently trying to get the new latest version of CM12 - Lollipop for my sensation.
And yes I'm using 4ext recovery aswell.
I flashed the boot.img file in my phone and it was a success, however after wiping cache, davlik, and data and formatting all partitions except sd card I go to flash the CM12 ROM but it's giving me a status 0 error again.
Am I missing something?
Here is the log of when I try installing the CM12 zip
"
Installing: /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
Finding update package...
I:Update location: /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
Opening update package...
Installing update...
Warning: No file_contextsminzip: Extracted 3 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 12
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such file or directory
unmount of /data failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
E:Error in /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
(Status 0)
Installation aborted.
"
Thanks

Spitfire98 said:
Thank you for the reply
Ok I did what you said, I'm currently trying to get the new latest version of CM12 - Lollipop for my sensation.
And yes I'm using 4ext recovery aswell.
I flashed the boot.img file in my phone and it was a success, however after wiping cache, davlik, and data and formatting all partitions except sd card I go to flash the CM12 ROM but it's giving me a status 0 error again.
Am I missing something?
Here is the log of when I try installing the CM12 zip
"
Installing: /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
Finding update package...
I:Update location: /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
Opening update package...
Installing update...
Warning: No file_contextsminzip: Extracted 3 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 12
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such file or directory
unmount of /data failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
E:Error in /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
(Status 0)
Installation aborted.
"
Thanks
Click to expand...
Click to collapse
did you flash the latest version of 4ext recovery?
if not take it from here
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command

Spitfire98 said:
Thank you for the reply
Ok I did what you said, I'm currently trying to get the new latest version of CM12 - Lollipop for my sensation.
And yes I'm using 4ext recovery aswell.
[]
E:Error in /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
(Status 0)
Installation aborted.
Click to expand...
Click to collapse
1.) Make sure you have at least 4ext recovery v1.0.0.6 RC2 in order to install new ROMs. Otherwise you will very likely get a status 0 error with most ROMs.
2.) I suggest to use CM11 as a daily driver, Lollipop so far has not been stable enough on the Sensation, I had different kinds of problems. Still seems to be a bit experimental to me.

WiFi + ROM (status 0) ~ Problem SOLVED!
Okay, first of all, a huge thanks to everyone that replied and took the time to help me with my problem!
The WiFi problem occurred because I had the incorrect ROM Build name even though it was like the old untampered Ice Cream Sandwich (my stock O.T.A.update ICS was 3.32.x and the one I had downloaded and flashed myself was a stock ICS to bring back my phone's old OS but it was 3.33.x).
The problem of the status 0 error was that at first I was forgetting to flash the Boot.img file in the phone, but then it was because I had version 1.0.0.5 of 4ext recovery not 1.0.0.6 (the latest) as you guys suggested. I can't believe it was that simple but it's solved atleast now and I am infact currently running the latest CM12 Lollipop on my Sensation which looks amazing but since its still unofficial it has a few small bugs.
Once again Thanks all
Happy Devving!

Emergency calls only (but valid IMEI)

Hi everyone, I'm in a particular situation. I bought an used J710MN but I forgot to check that the IMEI number that's under the battery matches with the one that appears in the software. It turns out that they didn't
BUT: Before I bought it, I made a test call and the phone was working OK. I had no problems.
After that I installed TWRP with Odin in order to root it. That's when the phone stopped working.
What I did:
I believed that the phone wasn't working because the physical IMEI is reported (I checked) so:
1. I flashed superSU and rooted the phone
2. I installed Xposed and IMEI changer and I set the IMEI of an old phone of mine, but nothing happens. In fact, although the physical IMEI is reported, the "soft IMEI" that the phone had initially was NOT reported and as I said, I tested the phone when at the moment I bought it.
Something must have changed when I installed TWRP.
Additional info:
1. I have NOT an EFS backup.
2. I currently have a VALID IMEI address (the one that I installed with IMEI changer)
3. In Settings -> About Device -> Status, I see the following:
IP Address: [shows an IP address]
Wi-Fi MAC address: [shows a valid MAC address]
Bluetooth address: Unavailable
Serial number: [shows an 11 characters length string]
4. In Settings -> About Device -> Status -> IMEI Information, I see the following:
IMEI: [shows a valid IMEI address]
IMEISV: 01
4. I can use wifi without problems
5. When I try to make an EFS backup from TWRP, I get the following:
Code:
[COLOR="Red"]Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.[/COLOR]
Updating partition details...
[COLOR="Red"]Failed to mount '/data' (Invalid argument)
Failed to mount '/cpefs' (Invalid argument)[/COLOR]
...done
[COLOR="Red"]Unable to mount storage
Failed to mount '/data' (Invalid argument)[/COLOR]
Full SELinux support is present.
[COLOR="Red"]Unable to mount /data/media/TWRP/.twrps[/COLOR]
MTP Enabled
Updating partition details...
[COLOR="Red"]Failed to mount '/data' (Invalid argument)
Failed to mount '/cpefs' (Invalid argument)[/COLOR]
...done
[COLOR="Red"]Unable to mount storage
Failed to mount '/data' (Invalid argument)[/COLOR]
Also I have a question: Could the carrier still know the physical IMEI number if the phone has a different IMEI number in software?
Thank you

I've got the same... after installing " twrp-3.1.1-0-j7xelte " on Galaxy J7 J710F/DS
well, I fixed it as far that only one ERROR is left: " Failed to mount '/cpefs' (Invalid argument) ".
for that installed " CF-Auto-Root-j7xelte-j7xeltexx-smj710f " with ODIN and then reinstall " twrp-3.1.1-0-j7xelte ".
But can't find any Info to this ERROR MESSAGE.
Acutually it is still not possible to install any ZIP with TWRP... no ROM, no SUPERSU, no MAGISK, no other RECOVERY
---------- Post added at 11:29 AM ---------- Previous post was at 11:13 AM ----------
HCFatLiveDE said:
I've got the same... after installing " twrp-3.1.1-0-j7xelte " on Galaxy J7 J710F/DS
...........
Acutually it is still not possible to install any ZIP with TWRP... no ROM, no SUPERSU, no MAGISK, no other RECOVERY
Click to expand...
Click to collapse
some more Info that might be important:
after install twrp-3.1.1-0-j7xelte (but before I wiped everything) the Stock-Rom made a ERROR MESSAGE when getting to the LockScreen (but interrupted by SIM PIN Input )
It said "device can not be started, integrity check failed" ... and that a factory reset is needed... I did it often, but always same ERROR.
Now trying to install custom ROM but twrp-3.1.1-0-j7xelte tell " Failed to mount '/cpefs' (Invalid argument) "

the little thinks
well, I have a J701F/DS .... thats why it did't work ....

Updated my Samsung J7 pro( SM-J730F) to Android 8.1 Oreo and the phone only shows emergency calls, Imei is okay, it just can't read the local network, tried searching network manually, just shows error, downgrading back to nougat still the same problem, tried patching with z3x pro tool , still the same issue, anyone to help please am desperate now.

Galaxy Note 9 Bricked?? Help!

Hi,
I hope someone can help me. I managed to get locked out of my new galaxy note 9 and decided to try to flash fresh software onto it. I have flashed phones a few times before and never had an issue.
Whilst the software was flashing in Odin it seemed to get stuck and so I used the shortcut to exit download mode and unplugged the USB from my computer thinking I could just try again. Since I have just had the phone stuck on a loop of a blue screen "installing system update", followed by "no command" and then a black screen which I have attached a picture of. I have tried all combinations of keys with no hope of entering download or recovery mode. If I hold both volume up and down as well as power button I get to the samsung loading screen but then this simply loops and goes back to what I described before if I release the buttons.
I really hope someone can help as it seems I have bricked by new phone. Sorry if this isn't the right place to post but I'm a new member here.
Cheers in advance,
John

What's on the black screen:
#Reboot Recovery Cause is [BL: Recovery mode set by key]#
E: failed to mount/cache: Invalid argument
Support SINGLE-SKU
Block based OTA
Supported API: 3
'MANUAL MODE v1.0.0#
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Can't mount /cache/recovery/last_locale

johnwick27 said:
What's on the black screen:
#Reboot Recovery Cause is [BL: Recovery mode set by key]#
E: failed to mount/cache: Invalid argument
Support SINGLE-SKU
Block based OTA
Supported API: 3
'MANUAL MODE v1.0.0#
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Can't mount /cache/recovery/last_locale
Click to expand...
Click to collapse
Can you get it to boot to a screen that says something like "encountered an issue, connect to Smart Switch"? If so, you "should" still be able to flash it via Odin or connect to Smart Switch and flash the device to recover it.
Or, you can try a USB jig made for Samsung devices, it's a tool that forces the device into download mode, they are only about $3 - $4 USD on eBay and other locations.
Or you can try the "300k resistor" trick or the "301k resistor" trick. They also can force a Samsung device into download mode, if possible, but there is no guarantee that the jig or the resistor tricks will work.
You are getting signs of life so there "should" be something that can revive the device.
You might have to send it to a shop that offers a JTAG service or replace the motherboard. The JTAG service is also not guaranteed.
Sent from my LGL84VL using Tapatalk

i have similar problem do find a solution??
I recently tried to install a custom ROM in my samsung j6+ but halfway through it my PC turned off.
Then the problem starts i decided to reboot my phone but it shows this error "No command" " #Reboot recovery cause is [[check_bootmode]RebootRecoveryWithKey]#
Block-based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E:Failed to mount / cache: Invalid argument
The error message keeps appearing for just a fraction of a second then disappear and appear again
I tried to go to recovery mode but no luck i cant get to it
I drained the battery to turn off the device then go download mode but after get to it, it also keep restarting
help me please. thank you

johnwick27 said:
What's on the black screen:
#Reboot Recovery Cause is [BL: Recovery mode set by key]#
E: failed to mount/cache: Invalid argument
Support SINGLE-SKU
Block based OTA
Supported API: 3
'MANUAL MODE v1.0.0#
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Can't mount /cache/recovery/last_locale
Click to expand...
Click to collapse
hello sir i have the same problem do you find solution?
I recently tried to install a custom ROM in my samsung j6+ but halfway through it my PC turned off.
Then the problem starts i decided to reboot my phone but it shows this error "No command" " #Reboot recovery cause is [[check_bootmode]RebootRecoveryWithKey]#
Block-based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E:Failed to mount / cache: Invalid argument
The error message keeps appearing for just a fraction of a second then disappear and appear again
I tried to go to recovery mode but no luck i cant get to it
I drained the battery to turn off the device then go download mode but after get to it, it also keep restarting
help me please. thank you

Seriously could use help flashing custom ROM to Oneplus 8t (Tmo-variant) I am at my wit's end

Ok, first off let me say thank you in advance. I had the Oneplus 7t and (Tmo) and played hell with it trying to root until I found that MSMTool and then had a hayday with it. Now I have the 8t, I have been waiting for a working TWRP because I really like TWRP and I really like Magisk. As of yesterday my stock Rom was fully rooted with TWRP, Magisk, and busybox. It had been that way for several days with no glitches or errors, so obviously bootloader unlocked, phone is carrier unlocked and got my oneplus unlock token last tuesday (5 days ago). On my 7t after trying several ROM's I settled on Havoc-OS so with my 8t I was just going to go straight to Havoc-OS even thought I might try messing around with a kernel update at some point in the near future. BUT...... somehow I have angered the Android God's and am being punished. I have been through much frustration in the past with things Android, have always been able to figure it out thanks to XDA, but today I must humble myself, finally make an account and ask for help. To the best of my recollection here is what I have done with the results.
But before that my current state is, I can boot to TWRP recovery, fastboot, bootloader, EDL and all that but I wiped partitions prior to starting the flashing process so right now I can not boot to system.
I started at techsphinx.com/smartphones/install-havoc-os/ It is a very straighforward guide. but gave error 7, which I believe is wring device error so I checked and it's the kebab havoc like it should be (I think, I'll get to that in a moment) so I look it up and everything says to get in to the file and find the update binary and update script and edit the update script, blah blah EXCEPT that in my copy of havoc-os in the called out directory I have different files. Mine are otacert and metadata. two completely different scenarios. otacert is a binary file while metadata when opened with notepad gives this text:
ota-property-files=payload_metadata.bin:1784:116801,payload.bin:1784:1262105569,payload_properties.txt:1262107411:156,care_map.pb:737:1000,metadata:69:621
ota-required-cache=0
ota-streaming-property-files=payload.bin:1784:1262105569,payload_properties.txt:1262107411:156,care_map.pb:737:1000,metadata:69:621
ota-type=AB
post-build=OnePlus/havoc_kebab/OnePlus8T:11/RQ3A.210805.001.A1/eng.kshiti.20210826.065117:userdebug/release-keys
post-build-incremental=eng.kshiti.20210826.065117
post-sdk-level=30
post-security-patch-level=2021-08-05
post-timestamp=1629960471
pre-device=OnePlus8T,OnePlus9R
I can't remember when was supposed to be remarked in the updater-script file but there is nothing like that in this file. That is all that is present in this directory, META-INF/com/google/android
Everything I try to push to the device errors out before it completes with a broken pipe error, adb sideload is similar in that it won't finish the transfer to the phone. Now anything I try to do in TWRP gives me error can't mount partition_name. I had a nandroid backup but I can't use it because partitions can't be mounted.
I wondered if it was the tmobile variant thing so I tried the msm tool for switching tmobile to universal edition first but I can't get msm tool to work in my device manager the now soft-bricked device shows up as the QS BULK device which is not the right one so I install the automatic driver installer for the qualcomm usb drivers, no effect so I follow how to install manually and windows will not let me and tells me it's likely that the driver file is corrupt or has been tampered with.
My frustration level right now is just before the part where I take a hammer to the phone and make as many small pieces as I can.
The state of my phone right now is that I can't even get it into edl mode because I can't get it to turn off. reboot to power off, holding volume up and power both leave it to when I push both volumes in the screen comes on and I am in bootloader mode. I am at a complete and utter loss.
I need my phone for work tomorrow

@Frustrated_AF,
Regarding the QualComm device driver: I've attached my notes on how I installed the MSM Tool (including the QC driver) in case it's of any help to you. (@Unbrick Instructions.zip). Just note that my phone is a KB2000.
If you can get into bootloader mode, than you can flash TWRP. Get it from https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
And once you're in TWRP you can install the Havoc rom zip file using the instructions in post #2 in the TWRP thread. Get Havoc from https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/.
Note that the Havoc thread installation instructions were written before TWRP for the 8T was available. And, yes, I've installed Havoc using TWRP so I know it works.

BillGoss said:
@Frustrated_AF,
Regarding the QualComm device driver: I've attached my notes on how I installed the MSM Tool (including the QC driver) in case it's of any help to you. (@Unbrick Instructions.zip). Just note that my phone is a KB2000.
If you can get into bootloader mode, than you can flash TWRP. Get it from https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
And once you're in TWRP you can install the Havoc rom zip file using the instructions in post #2 in the TWRP thread. Get Havoc from https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/.
Note that the Havoc thread installation instructions were written before TWRP for the 8T was available. And, yes, I've installed Havoc using TWRP so I know it works.
Click to expand...
Click to collapse
Thank you, I have one issue (at least) that I can't find anything on in your instructions... I have been unable to install the usb drivers, on 2 different laptops one old one new one running windows and one running Linux with Windows in VMWare. same thing both times. I have tried the oneplus exe file, the qualcomm auto-installer andstlil show up as QUSB_BULK_ CID...... When I try to manually install by clicking on let me choose one Windows won't allow it. Windows says the file is possibly corrupted or tampered with. So I am unable to use any of the MSMTool versions I have tried.
Any ideas on that?
Cancel that. Please forgive me if I seem panicky if I can't get my phone working by tomorrow morning there will be hell to pay at work. So in your instructions where you write:
"If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ), extract the files, then install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you extracted the CAB file and selecting that directory."
I downloaded the file (brought back memories from doing my 7t) and extracted it to a folder on my desktop oddly enough without even updating the driver my edl mode device was detected correctly.
Working on the rest I'll get back to you shortly and once again I can't even begin to express my thanks!

@BillGoss Ok hopefully this will be the last question and it might be a dumb one but I'm not wanting to screw this up any more, In post #2 paragraph 2, bullet point 1 at https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
He states "sideload/flash ROM + installer" if I sideload the ROM it's going to install it, I don't see that the installer would go onto the device??? That URL is from the RECOVERY part of it from the ROM part of it at the URL https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/ under "installation" it describes a process of altering the RO M files payload.bin and then putting the pieces back together then using ROMinstaller.exe while phone is in fastboot mode.
Could you shine any light on this for me?

Frustrated_AF said:
@BillGoss Ok hopefully this will be the last question and it might be a dumb one but I'm not wanting to screw this up any more, In post #2 paragraph 2, bullet point 1 at https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
He states "sideload/flash ROM + installer" if I sideload the ROM it's going to install it, I don't see that the installer would go onto the device??? That URL is from the RECOVERY part of it from the ROM part of it at the URL https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/ under "installation" it describes a process of altering the RO M files payload.bin and then putting the pieces back together then using ROMinstaller.exe while phone is in fastboot mode.
Could you shine any light on this for me?
Click to expand...
Click to collapse
Like I said, the Havoc thread instructions relate to the pre-TWRP method. And I've never used that method.
The TWRP instructions say to sideload the rom and installer (TWRP installer zip) because installing the Havoc rom also installs a recovery, thereby replacing TWRP. That's why you need to reinstall TWRP after installing Havoc.

@BillGoss Thank you for your patience with this. I just assumed that learning what I learned when I did my 7t would transfer right on over to this and it would be simple... Haha. So now this... sideloading ROM at 47% from my powershell window it stops and says "adb: failed to read command: No error" On my device:
Flashing A/B zip to inactive slot A
step 1/2
step 2/2
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Updating partition details...
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
...done
Devices on super may not mount until rebooting
recovery.
To flash additional zips, please reboot recovery to
switch to the updated slot.
Leaving me clueless as to what has gone wrong or what to do about it. Any ideas on this one?
Edit; It worked! I did nothing else except rebooted it and it came up fine brand new havoc-os so far nothing at all wrong. I have no idea why all the failed to mount errors and I don't think I really care all that much it works!!! I'm going to flash twrp and magisk and be done for the night with it. @BillGoss I can't thank you enough. You have saved my bacon [email protected]!

Frustrated_AF said:
@BillGoss Thank you for your patience with this. I just assumed that learning what I learned when I did my 7t would transfer right on over to this and it would be simple... Haha. So now this... sideloading ROM at 47% from my powershell window it stops and says "adb: failed to read command: No error" On my device:
Flashing A/B zip to inactive slot A
step 1/2
step 2/2
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Updating partition details...
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
...done
Devices on super may not mount until rebooting
recovery.
To flash additional zips, please reboot recovery to
switch to the updated slot.
Leaving me clueless as to what has gone wrong or what to do about it. Any ideas on this one?
Edit; It worked! I did nothing else except rebooted it and it came up fine brand new havoc-os so far nothing at all wrong. I have no idea why all the failed to mount errors and I don't think I really care all that much it works!!! I'm going to flash twrp and magisk and be done for the night with it. @BillGoss I can't thank you enough. You have saved my bacon [email protected]!
Click to expand...
Click to collapse
Glad you're ok now. Those error messages are common when installing roms because those partitions (what used to be the system partition and is now a set of virtual partitions inside the physical super (sda15) partition) don't get properly setup until you reboot.
The 8T is a virtual A/B device which makes life more complicated than the old simple partition and straight A/B partition devices.