Database Users

Nvflash-based recovery based on TnT Lite 2.2.0

As always, USE AT YOUR OWN RISK. You should a fundamental understanding of how nvflash functions - if you do not, I would not recommend attempting this!
1.0.2 Link (based on TnT Lite 2.2.0): http://www.mediafire.com/?5c7is1eld6j9i6d#1
Alternative link: http://www.megaupload.com/?d=7ROU81O0
md5sum : ee3f346e602437b6a1be2336acb0b3ae
References: http://wiki.tegratab.com/index.php/Nvflash_FAQ#Entering_APX_Mode
http://forum.tegratab.com/viewtopic.php?f=6&t=8
So Why Did You Do This?
My reason for building this out was to have a newer baseline in case I needed to wipe the device using nvflash - I was just sick of seeing the TnT homescreen each time.
So What's Different in This?
- Malata bootloader with a Tegra boot image (you'll see that on bootup). Thanks to rothnic for the pic!
- Clockworkmod .08.
- Changes to ramdisk to allow adb remount to work.
- TnT Lite 2.2.0 baseline.
- NOT an update.zip. this is a compressed nvflash folder with the Windows DLL's and Linux .so's added. I have tested this on Linux only, the Windows stuff I grabbed from Malata.
So How Do I Use This?
You should have a fundamental understanding of how nvflash works, and how it could bork your system if you're not careful. I've run this several times today, but there is speculation that some devices may have a different partition structure. I'm just releasing this as an option to you, if you choose to use. But it's at your own risk!!!!!!!! Bekit has actually suggeted that you just flash things like boot and system manually (and as seen in the the tegratab link) and that might not be a bad idea. But, that would not inlude the bootloader changes.
USE AT YOUR OWN RISK, YOU HAVE BEEN WARNED
For Linux users (which is how I tested): Expand this out, open up a terminal session as root to that folder. Connect your device in APX mode. Then, run this command:
Code:
LD_LIBRARY_PATH=. ./nvflash --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --create --go
This will wipe the bootloader, kernel and system, and then reboot. It will not wipe data.
Once it reboots, you might get a UID error - if so, reboot into clockworkmod and then fix permissions. That should correct it.
EDIT: A post that might help out Windows users: http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
Again, be very very careful with this - if I'm being redundant it's because it's important to understand what you are doing.
EDIT: 1.0.1+ versions downlevel clockworkmod back to .08, and fixes the VOLD issue. Two annoyances that I felt required a new version.
----------------------------------------------------
Archives:
1.0.1 Link: no longer needed
1.0.0 Link (based of of TnT Lite 2.0.2 + performance pack): http://www.mediafire.com/?hd6aal4857h567h
md5sum: e127b529021c4479bae5c6170c73dbd9

Soooo...
Let me see if I understood.
Compared to the previous post on TegraTab adding both folders together and then runing the bat file to the bootloader I can substitute the content of the zip instead and have TnT2.0.2 with Vega x-pack?
Also I noticed that there were 2 folders for USB Drive including one x64. Do I keep on the original format outside the folders? Or leave as it is when extracted?
Thanks
PS. Dude the moment I get the "how to install " this image this is gold in my hands
Thank you sooo much for your work bro
Edit: Just noticed the lack of a nvflash bat file. Can I use the original one?

Please, help me to understand the benefits of this new bootloader and ADB mounting?

Honestly, I have no clue how to run this in Windows. It's probably similar syntax to what I posted for Linux.
I'm not sure if previous batch files would work, as the syntax is actually different, I believe. Look at the bct and cfg file, for example - those are different than what bekit used.
This is actually 95% Malata, I just replaced the system.img and boot.img files.

flipper9 said:
Please, help me to understand the benefits of this new bootloader and ADB mounting?
Click to expand...
Click to collapse
bootloader has no real benefit, other than having a different boot image.
adb remount is nice because it makes things easier if you are using ADB to make changes to /system. It's like full su acess wihout all the workarounds.

I'm having a problem on mine getting stuck in APX mode after doing the full recovery. Was trying this file you just put up and it gets stuck at;
flash.bct sent successfully
Never goes any further.
How did you ultimately unbrick yours? Anyone have an original image I can push?

cahiatt said:
I'm having a problem on mine getting stuck in APX mode after doing the full recovery. Was trying this file you just put up and it gets stuck at;
flash.bct sent successfully
Never goes any further.
How did you ultimately unbrick yours? Anyone have an original image I can push?
Click to expand...
Click to collapse
I've been using the original Bekit nvflash recovery, which is very similar to this one except it's vanilla 1.0.0 stock (mostly). His dump always worked for me -- https://www.dropbox.com/s/wrcd87u1iy31u4e/nvflash_gtablet_2010110500.zip

Have actually done both of them (but which is the proper one). They will flash correctly and the system will boot. But when I turn it off it goes into APX mode and will not turn back on again. Have to reflash again. If I turn it off it is back in APX.

I've been following along with the TnT Lite adventures. I did this and it worked fine. Thanks for making the gtablet a very usable device. I'm not sure I will keep the performance pack, but there's a tremendous difference.

cahiatt said:
Have actually done both of them (but which is the proper one). They will flash correctly and the system will boot. But when I turn it off it goes into APX mode and will not turn back on again. Have to reflash again. If I turn it off it is back in APX.
Click to expand...
Click to collapse
Try unplugging the tablet and power cycling a few times. Once you're in APX mode, the device will go back to APX mode just from doing a recovery reboot as long as the power supply remains plugged in.
I'm not 100% sure if this is what is happening in your case since it still really shouldn't happen unless you specificially request a recovery reboot, but try unplugging the tablet after the APX flash if you haven't tried that yet.

download.bat
thx69 said:
Soooo...
Let me see if I understood.
Compared to the previous post on TegraTab adding both folders together and then runing the bat file to the bootloader I can substitute the content of the zip instead and have TnT2.0.2 with Vega x-pack?
Also I noticed that there were 2 folders for USB Drive including one x64. Do I keep on the original format outside the folders? Or leave as it is when extracted?
Thanks
PS. Dude the moment I get the "how to install " this image this is gold in my hands
Thank you sooo much for your work bro
Edit: Just noticed the lack of a nvflash bat file. Can I use the original one?
Click to expand...
Click to collapse
Is this it... download.bat was inside the package ---> "nvflash.exe" --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --create --go

catttman said:
Is this it... download.bat was inside the package ---> "nvflash.exe" --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0xbb0c0011 --create --go
Click to expand...
Click to collapse
That should work, but be very very careful.....

Any noob friendly windows instructions?

Hey Roeby, please do not ever forget about us common folks who can not get nvflash working on their pooters
Even worse case, I was able to put CW on a micro sd, remap command and get back up through interrupting the boot-loop and forcing isntall of CW.
Now have a full CW back up of current TnT Lite 2.0 and the Nvidia 2.03 patch .. all 900mb of it (lot of apps).

I'm not planning to go to nvflash online, anytime soon. This was just a restore point for myself that I wanted to pass on.
Already used it, this morning - I found out that clockworkmod .12 sometimes give you that mismatch error, so I had my nvflash restore image to fix it.

roebeet said:
That should work, but be very very careful.....
Click to expand...
Click to collapse
I will report back tonite after I flash it
I like useing Nvflash ...saved me a lot
and shooting my apk,s back on with adb... fast and clean

Ok, I used windows to flash roebeet's backup. It was scary at first but then got better.
I initially blindly used the Download.bat file, just because it looked good. It finished successfully but I couldn't get the device to boot past the "Malata" screen. I couldn't get into recovery mode either. I was a little scared.
I put the device back into apx mode and then edited the Download.bat file so that it was just this...
"nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --create --go"
I removed this piece " --odmdata 0xbb0c0011" Not sure what exactly it does but it wasn't in the linux command roebeet posted.
After that it worked and everything booted up normally. I'm still testing but it is looking good.

Going to have a 1.01 version of this, soon. The VOLD issue I found affects this, as well.
EDIT: Uploaded. VOLD issue fixed, and downleveled cwm back to .08 due to the "Mismatch errors" when flashing boot.img files that are not padded.

all went well
working as told... Nice

flashed 1.01 version s
Is the Camera fixed yet

[HOWTO] Installing the unlocked bootloader and fixing broken recovery in leaked ICS

Some of us used the flash-stock-then-flash-CWM method of installing the ICS leak, but were left without a working recovery. The method below allows you to unlock the bootloader and install a custom CWM.
This method may or may not work for you. I take NO CREDIT for making this happen, I'm just writing a quick howto. Thanks to strra for making it convenient.
Typically, attempting to boot into Recovery would generate an error that recovery image was not verified (something along those lines).
Thanks for all the devs who made this possible - you guys are amazing. Donate to them if you can, they deserve it.
I TAKE NO RESPONSIBILITY IF YOU TURN YOUR A500 INTO A PAPERWEIGHT.
If you don't feel comfortable with this possibility, stop here.​
Install the A500 drivers from Acer on PC (from Acer's site).
Install and launch Android terminal app on tablet. Run the following command:
Code:
dmesg>/mnt/external_sd/dmesg.txt
Open up dmesg.txt and look for androidboot.serialno. That is your CPUID. In my case, the serial number reported by the OS, on the box, in the MicroSD slot was NOT my cpuid.
Use Vache's site to convert that number into your SBK (four long hex values).
Extract all of the required files (batch.rar and nvflash) from strra's post into c:\nvflash.
Open up a Windows command prompt (cmd.exe) and then `cd c:\nvflash`.
Launch `run.bat`, but don't enter your SBK yet.
Power down the tablet.
Use a paper clip and hold down the Reset button. Do not release it. Hold down power for 3 secs and then release it. After another second, remove the paper clip. Your Windows PC should then detect your device and install the APX driver. You should then have an APX USB device installed. If you do not have an APX USB device listed in your system tray, you cannot proceed.
Go back to the Windows command prompt and enter your SBK. Once you enter it, the process should begin. If you receive a USB write error, your SBK is incorrect.
Once the process begins, the Windows command prompt will read "Press any key when your A500 is in bootloader mode". Do not continue until the tablet is in Download Mode.
Once the tablet reads "download mode" (something along those lines), you are in bootloader mode. You can proceed and it will begin formatting the various partitions and installing the recovery.
Once the process completes, it should say PASS. You can then power off the tablet and power it back on again.
Make sure your tablet boots.
Power the tablet down and attempt to launch CWM via Power+VolDown.
PROTIP
Remount /system rw:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p3 /system

Worked perfectly! Thanks!

yaw
worker for me too... thanks to all for this work!

good write-up
also, another protip:
if you right click the title bar of the command prompt, you can go to edit>paste to copy/paste the SBK... should make things a little easier

@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
I'd like to add them to the following list of bloat that can go (another PROTIP) once you remount /system rw.
Under /system/app, rename:
3DPhotoBrowser-apk
AcerNidus-apk
Clearfi-apk
aupeo-apk

Problem with recovery
When it launches download mode, it says entering download mode in acer boot screen and it stays like that. How much time should I wait until it enters download mode? Or is that download mode? When it shows PASS message then under appears a red text saying LNX image not certified or something like that, why? Please help me. Thanks.
Now my tablet boots with a white text on it saying custom bootloader. But i don't have recovery mode.

Luescoff said:
Now my tablet boots with a white text on it saying custom bootloader. But i don't have recovery mode.
Click to expand...
Click to collapse
Install new recovery with fastboot. Boot into Android normally and connect it to PC with Android SDK (you need working adb and fastboot commands).
Check if adb sees your device:
Code:
adb devices
Boot into bootloader:
Code:
adb reboot bootloader
If you haven't been in bootloader mode before you might need to install fastboot drivers (from ACER Drivers for example).
Check if fastboot sees your device:
Code:
fastboot devices
My a500 didn't return its ID so fastboot is showing a device with "?" instead of ID. It is ok.
Install new recovery (here it is in recovery.img file, change it to yours):
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
When device will be booting just hold Volume Down like always to get into recovery.
You can also test and boot recovery.img directly from PC with fastboot:
Code:
fastboot boot recovery.img
You can test with fastboot boot command as it doesn't overwrite anything in device's flash. It downloads boot image (like recovery.img or boot.img into RAM and runs it from there).

jm77 said:
@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
I'd like to add them to the following list of bloat that can go (another PROTIP) once you remount /system rw.
Under /system/app, rename:
3DPhotoBrowser-apk
AcerNidus-apk
Clearfi-apk
aupeo-apk
Click to expand...
Click to collapse
You can also add social Jogger
Link to facebook .
and all the links to there so called book shelf apps like link to games link to media .there are 4 of them They Hog resources even if you NEVER use them.I forget all there names and im on Vachs rom he has removed them all.

@jm77: Maybe could you split the DL link (batch.rar) and add the link to the OP of the orig. thread for downloading the bootloader binary (so when I update it people get the updated version directly)?

jm77 said:
@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
.......
Click to expand...
Click to collapse
Acer hid them in flexrom/app this time around!

Thanks for the help.

yaworski said:
Install new recovery with fastboot. Boot into Android normally and connect it to PC with Android SDK (you need working adb and fastboot commands).
Check if adb sees your device:
Code:
adb devices
Boot into bootloader:
Code:
adb reboot bootloader
If you haven't been in bootloader mode before you might need to install fastboot drivers (from ACER Drivers for example).
Check if fastboot sees your device:
Code:
fastboot devices
My a500 didn't return its ID so fastboot is showing a device with "?" instead of ID. It is ok.
Install new recovery (here it is in recovery.img file, change it to yours):
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
When device will be booting just hold Volume Down like always to get into recovery.
You can also test and boot recovery.img directly from PC with fastboot:
Code:
fastboot boot recovery.img
You can test with fastboot boot command as it doesn't overwrite anything in device's flash. It downloads boot image (like recovery.img or boot.img into RAM and runs it from there).
Click to expand...
Click to collapse
Thank you, yaworski
For a mysterious reason the only way to boot in CWM recovery mode on my a500 is passing by your last command
Code:
fastboot boot recovery.img
The classical "volume-/power" method brings me to the "dead android man" with the exclamation mark... Same thing if I use the "Acer recovery" app.
In others words, the only way to open the recovery is passing by the bootloader and the fastboot commands...
Any idea for the reason of that?

So should the odmdata in the bat file be 0x300d8011 or 0xb00d8011. It has 0x300d8011, but i saw another post where it should match was EUU uses as 0xb00d8011.
Thanks.

castafiore said:
Thank you, yaworski
For a mysterious reason the only way to boot in CWM recovery mode on my a500 is passing by your last command
Code:
fastboot boot recovery.img
The classical "volume-/power" method brings me to the "dead android man" with the exclamation mark... Same thing if I use the "Acer recovery" app.
In others words, the only way to open the recovery is passing by the bootloader and the fastboot commands...
Any idea for the reason of that?
Click to expand...
Click to collapse
it's because you didn't delete recovery-from-boot.p from /system and it's reflashing stock recovery whenever you boot into android

I want to make a backup of my current EBT before I try flashing this new one. When I enter APX mode (reset button + power), I get "Acer Picasso USB Boot-recovery driver" listed in my device manager.
Then I issue the command (i blanked out most of my SBK here).
Code:
nvflash --read 4 myboot.img --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
I've tried different flags like --bct --odmdate --configuration but i always get:
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Following that, the device dissappears from my windows device manager.
I've also tried the first command from run.bat with both odmdata values
Code:
nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0xb00d8011 --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
Both of these give the error message same message.
Any ideas?
---------- Post added at 01:21 PM ---------- Previous post was at 01:11 PM ----------
Also, just tried the run.bat as is (well.. i removed the "cls" so the screen woudln't blank. Get the same error..
Code:
C:\Users\james\Downloads\bootloader>run
****************************************************************
* This will boot your A500 into bootloader mode, *
* flash patched bootloader V2, and flash Thor Recovery 1.7 *
****************************************************************
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here : http://vache-android.com/v1/index.
php?site=sbk
Enter your SBK:0x8E000006 0x9C000001 0x22000002 0xF0000002
Loading bootloader...
Nvflash started
rcm version 0X4
[COLOR="Red"]Command send failed (usb write failed)
[/COLOR] **********************************************************
* Press any key when your A500 is in bootloader mode *
**********************************************************
Press any key to continue . . .

strra said:
it's because you didn't delete recovery-from-boot.p from /system and it's reflashing stock recovery whenever you boot into android
Click to expand...
Click to collapse
Thank you, strra.
I suspected it, to be honest, since I've noticed this advice when I launched the run.bat
But, my question has been/is still now: how to remove this "recovery-from-boot.p" ?
Can it be done when in APX mode? Do the adb commands work in APX mode?

castafiore said:
Thank you, strra.
I suspected it, to be honest, since I've noticed this advice when I launched the run.bat
But, my question has been/is still now: how to remove this "recovery-from-boot.p" ?
Can it be done when in APX mode? Do the adb commands work in APX mode?
Click to expand...
Click to collapse
While in Android you need to remount your /system partition as writable and just delete the file with rm command . If you didn't replaced your boot.img yet with patched one, just use
Code:
fastboot boot boot.img
command where boot.img is patched kernel, then wait until Android is started (it will run on patched kernel from ram like with recovery).
When you run on patched kernel and you use adb shell then you will have root from the beginning. Then just use
Code:
mount -o remount,rw /system
and you can remove the file.

Thanks for your quick and clear answer, yaworski
Booting on this patched boot.img is the trick.

fastboot boot recovery.img doesnt work for me, and i'm no able to mount rw to delete the recovery-from-boot.p. what can i do now??? i'm stuck in this leak version...

querobolo said:
fastboot boot recovery.img doesnt work for me, and i'm no able to mount rw to delete the recovery-from-boot.p. what can i do now??? i'm stuck in this leak version...
Click to expand...
Click to collapse
Did you flash the patched bootloader in APX mode using nvflash? Because all above instructions work only on unlocked and patched bootloader with "secure" flag off.

ZTE Open C (US) - brand new, bootloader won't unlock, rooted terminal?

just got the device today
followed the tutorial on unlocking the bootloader using the comebuy upgrade tool and checked the box for erasing "CEFS" and upgraded the firmware.
shell is now rooted.
however, rebooting to bootloader and trying any fastboot command gets "waiting for device"; fastboot devices shows nothing.
wth???
i'm an experienced dev / user, but i'm not going to be happy if this device i just got for developing purposes is locked down to where i can't do that.
also, trying to install the FFOS_to_android.zip that's widely available also does not pass signature verification in the recovery...
anyone got any ideas how i can unlock this thing???

stayboogy said:
just got the device today
followed the tutorial on unlocking the bootloader using the comebuy upgrade tool and checked the box for erasing "CEFS" and upgraded the firmware.
shell is now rooted.
however, rebooting to bootloader and trying any fastboot command gets "waiting for device"; fastboot devices shows nothing.
wth???
i'm an experienced dev / user, but i'm not going to be happy if this device i just got for developing purposes is locked down to where i can't do that.
also, trying to install the FFOS_to_android.zip that's widely available also does not pass signature verification in the recovery...
anyone got any ideas how i can unlock this thing???
Click to expand...
Click to collapse
If you google "fastboot command gets "waiting for device"; you may find your answer, most likely driver problem, I use Linux so drivers aren't necessary for me.

vampirefo said:
If you google "fastboot command gets "waiting for device"; you may find your answer, most likely driver problem, I use Linux so drivers aren't necessary for me.
Click to expand...
Click to collapse
i got it figured out. i use both linux and windows; mainly linux. in linux fastboot was acting the same way. it's not now. still have to use sudo though...
i had to dd your recovery, then rebooted to bootloader and ran fastboot oem unlock and it was done.
i was initially very frustrated though.
since i got that figured out i've been trying to port my touchnav recovery to the device but i've been getting an error when i try to fastboot boot it.
funny you replied cause i'm curious what you're using to build your recovery. are you just using the last jb repo or something newer?

stayboogy said:
i got it figured out. i use both linux and windows; mainly linux. in linux fastboot was acting the same way. it's not now. still have to use sudo though...
i had to dd your recovery, then rebooted to bootloader and ran fastboot oem unlock and it was done.
i was initially very frustrated though.
since i got that figured out i've been trying to port my touchnav recovery to the device but i've been getting an error when i try to fastboot boot it.
funny you replied cause i'm curious what you're using to build your recovery. are you just using the last jb repo or something newer?
Click to expand...
Click to collapse
In Linux you need to make user rules if you don't want to use sudo to fastboot, my .50 recovery is a straight pull from CyanogenMod's 4.4 tree.
other recovery straight pull from CyanogenMod's 4.3 tree

Trying to unlock bootloader for oneplus6t getting error in adb

When I go into the bootloader to run the fastboot oem unlock command it gets stuck at waiting for device. I tried turning on USB debugging and it reads the phone while its booted into the OS but when going to bootloader "Waiting for device" could someone plz help me out thks. I have minimal adb and fastboot on my computer and it has worked before

Have you turned OEM unlocking on in developer options? Test for connectivity with "fastboot devices" fastboot drivers are also not installed by default on PC, might have to go searching for some more up to date drivers

Did you install all your drivers , ie.. the one for OnePlus...

Hello. I am having the same issue. When I read the general XDA rules and the guide to OnePlus Device Forums, I believe I should post here instead of creating a new topic.
I am running adb and fastboot on Fedora 33. My 6T is a T-mobile variant. I was running /e/ for a couple months. I used the MSM tool to restore to Oxygen 9. Then I upgraded to Oxygen 10 OTA. No issues there.
I enabled developer tools, and toggled OEM Unlock to ON. I am able to start in fastboot, no issues. The phone is obviously locked. I have the unlock token from when I originally unlocked to install /e/.
When I run
Bash:
sudo fastboot devices
, it returns the same number as on the phone's fastboot menue. So I believe it sees the phone.
If I run
Bash:
[sudo] adb reboot bootloader
, I get the message
Code:
error: insufficient permissions for this device. See [http://developer.android.com/tools/device.html] for more information
. (Going to that website gives a white page with bold letters Service Unavailable.
I run
Bash:
fastboot flash cust-unlock unlock_code.bin
, and it hangs with the message
Bash:
< waiting for any device >
. I'm able to Ctrl-C back to the command prompt.
If I run
Bash:
sudo fastboot flash cust-unlock unlock_code.bin
, it gives me the message
Bash:
fastboot: error: cannot load unlock_code.bin: permission denied
After searching on the web, I've seen a couple of others with this same problem. But I haven't seen anybody found a solution yet. I'm going to keep on plugging away at this. If I figure something out, I'll bring it back here.
Dan.

OK. Turns out I'm a complete dodo bird. The permission denied is from bash. chmod 755 on the token file fixed the problem. Lineage is now running nicely.

v20 H918 fastboot/twrp/bootloop brick

i have 3 lg
one of them is seen by my linux mint 20.1 desktop. this is my good stable and never touches any mods till my two better phones are running.
the other 2 i can get into fast boot, they were previously rooted & running orea/8 stock rooted
neither of those other 2 phones are recognized by my pc
i am using the adb reboot bootloader and get no joy on the 2 suborn phones.
both of the two phones refused to flash roms of any sort or type after a twrp wipe.
one of the phones is now fastboot only and nothing else ever happens and no connection to the pc is ever made
the other phone still goes into twrp most of the time,,sometimes fastboot only,,and still refuses to take any rom of any sort at all
my goal is to reflash twrp, and throw on lineage stable
BUT
not desktop connection?
someone pleas help me unbrick these two

updot
i found a way to get coms, but it is still failsauce.
.
the instructions on twrp page failed because my system could not read that far into my hard drive
.
TWRP Installation Tutorial for Linux Mint and Ubuntu users » AndroidGuru.eu
TWRP (Team Win Recovery Project) is an open-source custom recovery image for Android devices. It is a replacement for the stock recovery mode that is installed on most Android devices by the manufacturer. TWRP provides various advanced features and options that are not available in the stock...
www.androidguru.eu
.
seeing the fail sequence @ terminal feedback info i used that to go to where it WAS reading from, pasted the .img file there, then ran the commands @ that point
result was
.
[email protected]:~$ sudo fastboot flash boot /home/twrp-3.5.0_9-0-h918.img
target reported max download size of 536870912 bytes
sending 'boot' (23540 KB)...
OKAY [ 0.681s]
writing 'boot'...
FAILED (remote: unknown command)
finished. total time: 0.700s
[email protected]:~$
now i need to troubleshoot /fix why my phone is refusing to accept a flash,,even though it is correctly responding back to
sudo fastboot devices
any advice would be GREATLY appreciated.
will update as possible.if the Lord be willing.
event time stamp @ 4:30 - 2/9/21

notes :
adb sideload Full-Path-to-the-file.zip
CommandFunctionsADB Commandsadb devicesShows attached devicesadb shellTo jump from windows command prompt to android device shell:adb reboot bootloaderTo boot into bootloader modeadb reboot recoveryTo boot into recoveryadb get-serial noGet Serial Number of your connected deviceadb installTo install apps over adbadb install -rTo update the existing apps with new versionadb uninstall package_name.hereTo uninstall any apps or packages from the connected deviceadb uninstall -package_name.hereKeep the data and cache directories after uninstalling appsadb push <local> <remote>Upload a specified file from your computer to deviceadb pullDownload a specified file from your device to your computer.adb backupTake backup from your device to PCadb restoreRestore the backup to your phoneadb sideloadTo sideload apps or flashable zip file to your deviceadb logcatTake the realtime log from your phoneadb start-serverstart adb servers processesadb kill-serverstop adb server processesadb reboot fastbootreboot your device into fastboot modeadb usbshows all devices connected to your computer via a USB cable.adb devices //show devices attachedIt will display the list of all devices attached to your PC.adb connect ip_address_of_deviceconnect the IP address of your Android device to your computer.Fastboot commandsfastboot devicesShows connected devices on your PC/Laptopfastboot rebootTo reboot your devicefastboot reboot recoveryTo boot your device into recovery modefastboot oem device-infoTo check the bootloader unlock status:fastboot oem unlockIf the above command returns fall, run the following to unlock the bootloaderfastboot flashing unlockFew OEM may use this command to unlock bootloaderfastboot flashing unlock_criticalAllow flashing of bootloader related partitions too:fastboot oem device-infocheck bootloader lock/ unlock statusfastboot flash recovery [recovery.img]To flash recovery on your devicefastboot boot [boot.img]To test the recovery without permanently flashingfastboot format:ext4 userdataTo format data partitionfastboot flash boot [boot img name]flash flashable boot.img from fastboot modefastboot getvar cidTo display CID of your deviceFlashing ROM via Fastboot ROM zip packagefastboot -w
fastboot update </path/to/your/Rom.zip>
ref :
Basic ADB and Fastboot commands that you should learn to become Android Pro
Basic ADB command that you should learn to become Android Pro: Every Android developer or Android enthusiast should know some basic ADB comma
www.getdroidtips.com

thinking out loud.
everything i am seeing sais if my handset is not recognized by the desktop PC then my drivers are not correct.
problem with that statement is one of my 3 V20's does connect. correctly.
the other two are
FAILED (remote: unknown command)
as if there was no phone connected
but they are recognized under the fastboot devices, showing the connection is recognized by the PC, but not recognized by the phone.
how?
someone tell me pleas?
how do i get the 2 derpy phones to recognize the pc?

i am very much in a less then 3rd world country circumstance. (16 kbps max download speed for more then a week now) connecting to the internet is almost impossible as it is under excellent circumstances. for me to reboot into a Live os, and then set up a full NIC config before the Live freezes, glitches out or other wise kicks me in the face is almost impossible.
i am guna try to make an install. drag copy everything from the install to my os. this arch distro is built super similar to parrot os, so i might be able to make something work.
time will tell.
so far i have a failed atempt at this point
--------------------------------------------------------------------------------------------------------------------------------
[email protected]:/home/lglaf$ cd lglaf
bash: cd: lglaf: No such file or directory
[email protected]:/home/lglaf$ sudo git checkout h918-miscwrte #for the TMO V20
error: pathspec 'h918-miscwrte' did not match any file(s) known to git
--------------------------------------------------------------------------------------------------------------------------------
the lafsploit is not able to "get" from the hub. looks like files have been removed?
now how do i get what i need?
took me an hour and a half to run less than 10 cmd lines.
not to mention thes fails are forcing me to unplug a phone while in download mode.
this is not fun.
any one know where i can download the file "h918-miscwrte"
looks like it is no longer on github
[email protected]:/home/lglaf# git pull
Already up to date.
[email protected]:/home/lglaf# git checkout h918-miscwrte
error: pathspec 'h918-miscwrte' did not match any file(s) known to git
hard thing waiting.