Database Info

[Q] Phone won't boot

Hi,
Just recently changed my phone from Desire to Desire S. I rooted and S-Off'ed using Revolutionary. Everything was fine for the last day. Phone is still new so wanted to run the battery down till flat then recharge fully to calibrate it.
Turned my phone on this morning and it just stays at the white HTC logo screen. Tried to boot into 4ext recovery and it start loading up. It then reads system 0 cache 0 and the recovery crashes.
Tried to use factory reset option from bootloader and it freezes. Had to pull battery.
Tried to wipe everything using Fastboot commander. Fails erasing cache, sytem, etc.
What do I do now?
It was working fine yesterday even rebooted it a couple of times and it was fine. But can't get it to do anything this morning.
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Please help.
Thanks

What I would do is to go to HBOOT and flash new Clockworkmod (or any other recovery tool) from the Android Flasher.
Android Flasher: http://forum.xda-developers.com/showthread.php?t=794638
CWM: http://downloads.saga-lbc-mod.de/recovery-images/PG88IMG-RECOVERYIMG-3.2.0.0.zip
Just connect the phone to PC via USB and start Android Flasher (while in HBOOT). Click recovery and choose unzipped recovery.img (from the PG88IMG file). If your new recovery is working just mount USB storage (in recovery), put some ROM there and install zip from sdcard.
I guess you can try to fix this differently, but this is the fastest method if you don't know what exactly is wrong.

Thanks for the quick reply.
It didn't work. Android Flasher crashes. Just says not responding.
Any other ideas?

I also get these errors in recovery:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Is my eMMC dead? Don't understand what its all about.
Is it fixable?
Thanks

abhi63 said:
I also get these errors in recovery:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Is my eMMC dead? Don't understand what its all about.
Is it fixable?
Thanks
Click to expand...
Click to collapse
Seriously, a quick look in the general's section will land you to the correct guide about it:
[GUIDE] Possible FIX for the infamous eMMC problem..
Note: I INTENTIONALLY did not link the guide so YOU will be searching for it.
Check the guide on my sig first.

I did follow all the instructions in the guide. Can't even get adb to recognise my device.
Fastboot freezes whenever I use any commands.
Can't flash anything.

I have been through a similar prblem recently. Ensure you're in recovery to utilise the adb shell (this flummoxed me for hrs lol)
If it's emmc related try the following to verify whether the chip is defective.
Ensure you are in recovery when utilising the adb shell (this took me hrs to work out as my device wasn't listed!) I was in fastboot ot Hboot mode.
To be sure that you really are effected by the emmc issue (and not other partition corruption issues that show similar symptoms) you have to look at the kernel messages when booted to clockworkmod recovery. Do to this boot the phone into recovery and then (in and adb shell) issue the following command:
Code:
cat /proc/kmsg | grep mmc0
or
Code:
dmesg | grep mmc0
If you see output like (not necessarily in this order) :
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
then you are effected by this issue.
Basically the emmc chip does not initialize any more after the first attempt to access it in write mode.
Based on our current knowledge this is a hardware issue and can not be cured.
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
You need adb setup for this, use one of the stickys to get started with adb
1, start up adb and type these in.
Code:
adb reboot recovery
2, after the device starts up in recovery, enter this
Code:
adb shell
3, and then this, your serial number should come up after mmc0:0001
Code:
cat /proc/kmsg | grep 'mmc0:0001'
It looks like M4G2DE 2.10 GiB is the bad one, judging from what the #G2root devs say, but lets see what our side is.
Thanks
And unfortunaly I got the bad one too, rooted with gfree, this is what I got
<6>[ 8.328460] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

Thanks for the reply.
I just gave up in the end and got a replacement from Orange.
Thanks

[Q] Failed to mount /efs (Invalide argument) and not Start

Hi
My N8000 not start. ODIN flash well (no errors) but Rom not start from logo.
I flash a Custom Recovery on Odin I made full wipes and install or restore Roms, but they not start.
After Odin if I go to Stock Recovery I have:
E: Failed to mount /efs (Invalid argument)
Applied the csc-code : unknown
Can't open /efs/log/boot_cause.
On Custom Recovery can't mount /efs also.
May be I must flash a Pit File? But where is it?
Thank You

ValenteL said:
Hi
My N8000 not start. ODIN flash well (no errors) but Rom not start from logo.
I flash a Custom Recovery on Odin I made full wipes and install or restore Roms, but they not start.
After Odin if I go to Stock Recovery I have:
E: Failed to mount /efs (Invalid argument)
Applied the csc-code : unknown
Can't open /efs/log/boot_cause.
On Custom Recovery can't mount /efs also.
May be I must flash a Pit File? But where is it?
Thank You
Click to expand...
Click to collapse
did you backup EFS if so restore .
PIT are on sammobile but wrong PIT - brick ,
jje

JJEgan said:
did you backup EFS if so restore .
PIT are on sammobile but wrong PIT - brick ,
jje
Click to expand...
Click to collapse
Thanks
I have a backup but the Note not start. How can I restore it by Odin/Pc?
EDIT: I have efs backups format .tar.gz Can I flash this on Odin?

Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal

ValenteL said:
Thanks
I have a backup but the Note not start. How can I restore it by Odin/Pc?
EDIT: I have efs backups format .tar.gz Can I flash this on Odin?
Click to expand...
Click to collapse
You need Help?
Sent from my GT-N8000 using XDA Premium HD app

Thanks by Your Help:
BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
Click to expand...
Click to collapse
I have CWM and all on PC. I can flash on Odin and on Recovery. But I don't understood, I must flash the original ICS XWALG9 from SamMobile by Odin? You mean this?
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
Odin back to ICS to work....
Click to expand...
Click to collapse
After ...mount system I dont understood "Odin back to ICS"
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar
Reboot and everthing should be back to normal
Click to expand...
Click to collapse
This attach "factorymode" is the ON to replace the OFF?
Thank You

Good, it started, I have the Yellow text... now I continue...
Thank You
EDIT: Solved. Thank You BaDaB!ng505, from Your great help.
Not necessary to go to ICS.
mke2fs works well.
Edited factorymode whit Root Explorer and changed inside to ON.
Restored my /efs. All normal now.
Thank You

for the poeple who need the stock ICS 4.0.4
http://www.hotfile.com/dl/165813833/f958ae4/N8000XXALGA_N8000OXXALG5_PHN.zip.html
P.S. if all Poeple who recover his System, Will post Some Useful links here, he had used .
So I Can I make a good guide for the users with the same problems .
i fill tonight more links,mk now Go to my work .
Rongogo
Sent from my GT-N8000 using XDA Premium HD app

Rongogo said:
for the poeple who need the stock ICS 4.0.4
http://www.hotfile.com/dl/165813833/f958ae4/N8000XXALGA_N8000OXXALG5_PHN.zip.html
Click to expand...
Click to collapse
I have already a ICS 4.0.4 whit csc TPH from Portugal.
Thank You

How i made my 8000 work again...
Hello everyone,
i hope i canhelp. I also installed 5.0 Collective and everything worked....until the first reboot. It did not start again so i installed ICS from samfirmware and had that efs-problem and yellow text. (using TWRP 2.4.4)
I first rooted the device installed busybox (make sure to open and let install busybox)
i also installed Android Terminal (both, busybox and android from google play)
i had an efs-backup ((efs-18Marxxx.tar.gz) wich i extracted once on device then copied it to pc and extracted it again with 7zip.
So finally i had the folder again, i copied backto device extSdCard.
i opened android terminal and followed BaDas Steps (in collective thread...dont remember the post number just search pls.)
I started es file explorer gave it root in settings and copied the efs folder to / (root)
i set the rights for efs same as folder factory and renamed the file 000000000.something inside efs folder to Aaa000000000.something.
i am not sure if the last step is needed, but lately my device worksjust fine.
pls excuse any mistakes in text, if u have questions just shoot, good luck and dont worry as long as u can get into flashmode ur device can be fixed. peace
Robert

BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
Odin back to ICS to work....
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar
Reboot and everthing should be back to normal
Click to expand...
Click to collapse
Will this method work to restore a Galaxy S3's efs files with the proper 4.0.4 image? Stuck in Factory mode and the efs folder is empty.

n8000 getting ready for v6 to flash...
hello,
will flash the collective v6 by badab!ng now, will report hopefully within the next hour.
Robert
...it works just fine with me, even after reboot..

I can confirm Collective Edition v6 Dark Side works on N8000, no more efs issus

BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar
Reboot and everthing should be back to normal
Click to expand...
Click to collapse
Dear Sir,
I think my EFS is corrupted cuz when i go to service mode, i get something which reads SPEECHver: FR FR FR when I bought my phone in the usa from tomobile. Cannot read sim card. Its a note2, i don't even know how to view or where to view my efs but i am assuming it is efs corruption, imei shows up everything looks ok except not recognizing the sim. Restored and everything, will this bring me back to original efs if i install the original factory rom?
Actually how do i view my efs details cuz right now i cannot use my phone everything else looks fine except cannot read sim. Will your method work with on a tmobile t889?
Thanks.

I am having the same efs issue
HI,
I am having the same efs issue when doing a factory wipe. My Tmobile Galaxy Note 2 is stuck in a bootloop and I have flashed the current Samsung firmware from their firmware site and it changed nothing. After I flashed it and the bootloop started I booted into the stock recovery and did a factory reset. That is when I got "E: Failed to mount /efs (invalid argument). I think one problem is I am a noob, the other is I didn't get CWM installed on my phone prior to all this. I do believe it all stimmed from me downloading and running Swapper on my phone. Everything seemed fine with it until I ran that and rebooted. To make matters worse, I failed (again noob here) to back up anything. Is there any hope for my Note 2?

You do know that this is the Note 10.1 forum don't you?
What did you flash?

thanks god I see your solution but...if I didn't install CWM...and android sdk...is there any other way to save my phone? THANKS!!
BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal
Click to expand...
Click to collapse

Fix it finally
THANK YOU ><!
BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal
Click to expand...
Click to collapse

BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal
Click to expand...
Click to collapse
thank you sooooooo much!!
my s4 kept getting stuck on the samsung boot logo, i tried everything..flashing stock rom,pit files you name it. I was about to give up, untill i found this after hours upon hours of searching. Took me a couple of tries, but in the end my s4 was back up and running.
thanks so much!

aRbMama said:
thanks god I see your solution but...if I didn't install CWM...and android sdk...is there any other way to save my phone? THANKS!!
Click to expand...
Click to collapse
Dunno if CWM is necessary, but Android SDK is. Besides, It is going to help you to diagnose and repair many other problems.
Sent from my GT-N8000

[Q] Bootloader gone, only adb, not fastboot

Hi XDA-D,
I kinda helped my tf300t over the edge. I wanted to flash the new stock rom for troubleshooting purposes. I wanted to boot into Recovery but it froze the machine. Because I had fastboot options I pushed a the newest recovery (v6.0.2.3) and all seemed well untill I rebooted. Whatever I do The device boots into Recovery. It doesn't try to load the Rom and doesn't respond to "power vol down/up)
Recovery does start but with errors:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_log
and can't mount any directory (no /system, /cache, /data, /sdcard, etc)
Fast boot doesn't respond any more (keeps waiting for devices and doesn't list the tablet)
Adb recognises the tablet:
Code:
adb status-window
<-[2J<-[2HAndroid Debug Bridge
State unknown
adb devices
111111111111111111 Recovery
I think the boodloader is corrupt and the device defaults to recovery but the directories are gone, making sure that I can't install via fastboot or micro sd. Is there a way to restore this tablet with adb but without fastboot?

RVexx said:
Hi XDA-D,
I kinda helped my tf300t over the edge. I wanted to flash the new stock rom for troubleshooting purposes. I wanted to boot into Recovery but it froze the machine. Because I had fastboot options I pushed a the newest recovery (v6.0.2.3) and all seemed well untill I rebooted. Whatever I do The device boots into Recovery. It doesn't try to load the Rom and doesn't respond to "power vol down/up)
Recovery does start but with errors:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_log
and can't mount any directory (no /system, /cache, /data, /sdcard, etc)
Fast boot doesn't respond any more (keeps waiting for devices and doesn't list the tablet)
Adb recognises the tablet:
Code:
adb status-window
<-[2J<-[2HAndroid Debug Bridge
State unknown
adb devices
111111111111111111 Recovery
I think the boodloader is corrupt and the device defaults to recovery but the directories are gone, making sure that I can't install via fastboot or micro sd. Is there a way to restore this tablet with adb but without fastboot?
Click to expand...
Click to collapse
Hmm that doesnt sound good, CWM really sucks i refuse to use it lol. Does it have a terminal you enter? and have you been able to adb push anything to the tablet?
im thinking if you can adb push twrp to the device and open a adb shell you could try dd if=*path-to-twrp* of=/dev/block/mmcblk0p4
I havnt used the above in your situation so not sure if it will work, hopefully someone else can help. Goodluck mate

JoinTheRealms said:
Hmm that doesnt sound good, CWM really sucks i refuse to use it lol. Does it have a terminal you enter? and have you been able to adb push anything to the tablet?
*
im thinking if you can adb push twrp to the device and open a adb shell you could try dd if=*path-to-twrp* of=/dev/block/mmcblk0p4
*
I havnt used the above in your situation so not sure if it will work, hopefully someone else can help. Goodluck mate
Click to expand...
Click to collapse
*
Haven't tried to push a different recovery because I'm afraid I'll break the last thing that works. I think I can get a remote shell via adb. I was hoping there is a way to push a new kernel and boot but my knowledge is lacking.

RVexx said:
*
Haven't tried to push a different recovery because I'm afraid I'll break the last thing that works. I think I can get a remote shell via adb. I was hoping there is a way to push a new kernel and boot but my knowledge is lacking.
Click to expand...
Click to collapse
Id wait for someone elses input, i dont wanna mess with your adb lol. Im not sure about the above method since adb push would need access to sdcard, dd might work if you already have twrp on the device, again if you can access adb shell and dd works you might have a few things that could work, but even if you have a bricked device its not the end of the world. Asus might repair it, if not and your willing motherboards for these devices seem quite cheap, and if so you will have access to nvflash so something like wont happen again.

JoinTheRealms said:
Id wait for someone elses input, i dont wanna mess with your adb lol. Im not sure about the above method since adb push would need access to sdcard, dd might work if you already have twrp on the device, again if you can access adb shell and dd works you might have a few things that could work, but even if you have a bricked device its not the end of the world. Asus might repair it, if not and your willing motherboards for these devices seem quite cheap, and if so you will have access to nvflash so something like wont happen again.
Click to expand...
Click to collapse
Anyhow, thanks for thinking with me
I'll wait for someone who absolutely loves CWM

[Q] Accidentally Wiped /system, Can't Flash ROM

I was going to install a superuser.zip file to root my M4 but when I went to wipe the /cache the /system get wiped as well. I can boot into either CWM or TWRP and have full fastboot/adb, but when I try to boot into Android it just brings me back to the bootloader. When I try to install a stock ROM it just says it's flashing it but hangs at a certain point, I even had it run overnight and it still didn't install. When I try to flash a custom ROM suh as Cyanogenmod it either completes the flashing in about 2 seconds or greets me with an error. RUU and FUU don't seem to work. I'm 100% out of ideas now, and I'm open to anything to try.

legofan623 said:
I was going to install a superuser.zip file to root my M4 but when I went to wipe the /cache the /system get wiped as well. I can boot into either CWM or TWRP and have full fastboot/adb, but when I try to boot into Android it just brings me back to the bootloader. When I try to install a stock ROM it just says it's flashing it but hangs at a certain point, I even had it run overnight and it still didn't install. When I try to flash a custom ROM suh as Cyanogenmod it either completes the flashing in about 2 seconds or greets me with an error. RUU and FUU don't seem to work. I'm 100% out of ideas now, and I'm open to anything to try.
Click to expand...
Click to collapse
Andyt95 said:
Download Magio R4
reboot into recovery, type in cmd
Code:
adb devices
adb shell
mount data
exit
adb push /path/to/magioR4.zip /data/
[I](you should reboot here, in which case you'll
need to type[/I] "mount data" [I]again after adb shell,
but it's not really essential and should work anyway)[/I]
adb shell
mount /data /sdcard [I](creates a virtual sdcard)[/I]
flash your ROM in recovery just like you would normally (select .zip from sdcard) and boot up
run rumrunner, it should work, giving you S-OFF which will let you flash absolutely anything. If it doesn't, let me know and I'll come up with a workaround.
Click to expand...
Click to collapse
should work

Andyt95 said:
should work
Click to expand...
Click to collapse
Well first:
~ # ←[6nmount data
mount data
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
But instead I just used a USB OTG and flash drive so no big deal
And then Magio popped up with its installer and I went through that and then hit "reboot" to be greeted with the bootloader, so I hit "reboot" in the bootloader, but it still brings me back to the bootloader immediately after a black screen, so I thought "Oops, needed to flash the boot.img", so boot.img was then flashed. Now the green HTC logo is sitting there and isn't doing anything, probably frozen.

Code:
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
means /data is already mounted

I actually got it up and running from a nandroid restore, I tried it once before but the restore didnt finish so I thought it wouldnt work. Thanks for helping me out anyway though!

adb sideload does not finish

I was following this tutorial wiki.lineageos.org/devices/walleye/install and I am stuck with sideloading Lineage
I run `adb sideload lineage-17.1-20201013-nightly-walleye-signed.zip` while phone shows "Starting ADB sideload feature" then comes "Installing zip file '/sideload/package.zip'" and then I can see the progress bar below moving, but nothing more, no percentage or more textes or whatever. And it does that now for multiple hours.
Before when I tried it, it stopped completely and the progress bar was frozen.
So I guess something is not working here?! I use Lineage from here, 20201013 download.lineageos.org/walleye

I even cannot push the zip to /sdcard
$ adb push lineage-17.1-20201013-nightly-walleye-signed.zip /sdcard
adb: error: failed to copy 'lineage-17.1-20201013-nightly-walleye-signed.zip' to '/sdcard/lineage-17.1-20201013-nightly-walleye-signed.zip': no response: Success
Click to expand...
Click to collapse

Maybe you can use twrp

armuttaqin said:
Maybe you can use twrp
Click to expand...
Click to collapse
In a way Iam using TWRP, like in the tutorial. So I start the adb sideloading within twrp, how else could i use it? So how can I put the zip onto the phone to use twrp install?

and when I did the format data wipe, I got the errors
failed to mount '/system' (invalid argument)
failed to mount '/vendor' (invalid argument)
Click to expand...
Click to collapse

ok I managed to install from OTG usb I again got the error about /vendor, and also "warning no OS installed" before I rebooted, but then I booted into LOS and it seems to work now....

Hi, just wondering if you have any specifics regarding the steps you followed for OTG USB install? I'm new here and I seem to be having a very similar issue with a newer version of the walleye build