Database Users

Wiley Fox Swift2+ Bootloader Unlock

It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead

I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.

Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.

Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.

thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable

I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.

SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll

Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip

"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553

Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?

got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)

Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?

bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery

Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now

bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .

I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|

When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.

My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse

bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.

After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818

Can't downgrade back to Nougat.

I want to downgrade back to the last version of the sprint nougat firmware. I want to use the phone as my daily driver again, I cannot afford to have any surprise bugs that a beta oreo might bring.
1 - I am using a mac that is currently updated to macOs High Sierra 10.13.3
2 - I have the latest android platform tools downloaded released in december
3 - I have no problems executing ./adb devices or ./adb reboot bootloader commands
4 - I have no problems executing ./fastboot devices or ./fastboot flashing unlock/./fastboot flashing lock commands
5 - I cannot how ever execute the ./flashall.sh command when I do it returns the message permission denied.
The phone is currently on the latest oreo beta build, I have tried every firmware that has been listed on essentials dev page. Each time I try ./flashall.sh I get permission denied. I have reached out to essential for the guide to downgrading but when you have an actual problem their response time seems to increase 10 fold.
6 - To upgrade to the beta I used the side load method, I put the phone in to recovery mode and select the apply update from adb. In the terminal I would run ./adb flash update.zip.(I changed the firmware name to update.zip)
7 - Can the apply update from adb method work to downgrade to an earlier firmware, I want to try but I dont want to risk bricking the phone. Then I will have a titanium and ceramic paper weight for my desk .

swagglepuff said:
I want to downgrade back to the last version of the sprint nougat firmware. I want to use the phone as my daily driver again, I cannot afford to have any surprise bugs that a beta oreo might bring.
1 - I am using a mac that is currently updated to macOs High Sierra 10.13.3
2 - I have the latest android platform tools downloaded released in december
3 - I have no problems executing ./adb devices or ./adb reboot bootloader commands
4 - I have no problems executing ./fastboot devices or ./fastboot flashing unlock/./fastboot flashing lock commands
5 - I cannot how ever execute the ./flashall.sh command when I do it returns the message permission denied.
The phone is currently on the latest oreo beta build, I have tried every firmware that has been listed on essentials dev page. Each time I try ./flashall.sh I get permission denied. I have reached out to essential for the guide to downgrading but when you have an actual problem their response time seems to increase 10 fold.
6 - To upgrade to the beta I used the side load method, I put the phone in to recovery mode and select the apply update from adb. In the terminal I would run ./adb flash update.zip.(I changed the firmware name to update.zip)
7 - Can the apply update from adb method work to downgrade to an earlier firmware, I want to try but I dont want to risk bricking the phone. Then I will have a titanium and ceramic paper weight for my desk .
Click to expand...
Click to collapse
You need to unlock the boot loader.
You will need to go into developer mode and check the oem unlock.
In fast boot you need to unlock and unlock_critical.
They you should be able to revert.

tech_head said:
You need to unlock the boot loader.
You will need to go into developer mode and check the oem unlock.
In fast boot you need to unlock and unlock_critical.
They you should be able to revert.
Click to expand...
Click to collapse
Awesome, no where in essentials guide does it ever mention unlock_critical, all it says it to use fastboot flashing unlock. Even then it still says permission denied. After I unlock the bootloader i will go back to the fastboot menu and the run ./fastboot flashing unlock_critical or is it ./fastboot unlock_critical

tech_head said:
You need to unlock the boot loader.
You will need to go into developer mode and check the oem unlock.
In fast boot you need to unlock and unlock_critical.
They you should be able to revert.
Click to expand...
Click to collapse
Here is my exact steps of what I just did.
open terminal set directory to required folder
./adb devices- recognizes phone and shows model number
./adb reboot bootloader- executes no problem now in fastboot mode
./fastboot devices- recognizes device and show model number
./fastboot flashing unlock-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up and get back to the fastboot screen.
./fastboot flashing unlock_critical-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up again, get back to the fastboot screen
./flashall.sh-permission denied
In the fastboot menu on the phone it says status is unlocked. Up next the spectacular smashing on a essential phone with a hammer!!!!!!!!!!!!!!!!

swagglepuff said:
Here is my exact steps of what I just did.
open terminal set directory to required folder
./adb devices- recognizes phone and shows model number
./adb reboot bootloader- executes no problem now in fastboot mode
./fastboot devices- recognizes device and show model number
./fastboot flashing unlock-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up and get back to the fastboot screen.
./fastboot flashing unlock_critical-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up again, get back to the fastboot screen
./flashall.sh-permission denied
In the fastboot menu on the phone it says status is unlocked. Up next the spectacular smashing on a essential phone with a hammer!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Do you have the script file set to execute?
Sent from my PH-1 using XDA Labs

avd said:
Do you have the script file set to execute?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
That was my next question.
chmod +x flash-all.sh

fastboot

Hi essential phone owners, I'm hoping you are willing to help me out.. Anyway, i used adb reboot bootloader for fastboot access after I enabled OEM unlock from the developer options. The device state is LOCKED. I then typed fastboot devices and received no permissions (verify udev rules). Does that mean I'm stuck on stock?

dirtyreturn said:
Hi essential phone owners, I'm hoping you are willing to help me out.. Anyway, i used adb reboot bootloader for fastboot access after I enabled OEM unlock from the developer options. The device state is LOCKED. I then typed fastboot devices and received no permissions (verify udev rules). Does that mean I'm stuck on stock?
Click to expand...
Click to collapse
What type of computer?
Hopefully, not using cable that came with the phone. Don't use it for flashing.
What are you trying to do?

tech_head said:
What type of computer?
Hopefully, not using cable that came with the phone. Don't use it for flashing.
What are you trying to do?
Click to expand...
Click to collapse
Thanks for your questions. I am using Ubuntu 18 I believe. I have a nexus 6p also, and adb/fastboot commands worked just fine with that phone. What i would like to do successfully is to unlock the bootloader and critical partition, flash twrp, and finally be able to flash AICP/Magisk.
Edit- from computer to phone I am using the extra type C USB cable that came with the 6p. And I must note that the essential is found using command adb devices. And command adb reboot bootloader gets me to the point of fastboot.

Ubuntu ?
sudo fastboot devices

I'm using Linux Mint, so basically Ubuntu. I created a file under /etc/udev/rules.d and put this line in it:
SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", MODE="0666", GROUP="plugdev"
(My login ID is in the plugdev group.)
I'm able to execute adb and fastboot without needing sudo.

[Moto G6 Plus] developer option OEM unclock is disabeld (gray, not switchable enable)

Hi,
I have had a MotoG6 plus from a friend, but after upgrade it from 8.0 to 9.0 begans problems. The phone goes on crash and restart many time during usage of lots of Apps. I Tried a factory reset + reinstall alot of app, but nothing changed. The phone crash as well with same frequency. I decide to broke it and i tried to install a LineageOS16_9Pie. Unfortunatly during the Custom install, even if i followed a guide, unloking the bootloader, i really broke it, the bootloader and recovery partition. I have started the image of TWRP via fastboot to obtained a motoG6plus working (even without a proper bootloader) with LineageOS16_9Pie. To do it i've got the code from motorola site, to unlock the G6plus, after eneable USB debug + OEM Unlock from OS. With theLineageOS i have unlocked and locked oem many times using the OS without any problems . I have used the LineageOS for a week, after that, It started agan the same crashs i had with the stock rom 9.
I decided to reinstall the 8.0 version Evert , to remove the boot errors and because with the 8.0 was stable. After i installed the stock rom 8.0 evert i cant' unlock oem again . Into the developer option, the option "OEM unclock" is gray , disabeld not switchable . Even if i tried to unclock again from fastboot command , it say that i have to switch and anable "OEM Unlock" from the OS but i can't.
Is there a way to unclock byassing the OS or re-enable that option?

Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')

WoKoschekk said:
Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')
Click to expand...
Click to collapse
Thanks WoKoschekk, but i surely ' loaded a wrong rom, because the Moto G6plus don't have Wifi and connectivity via SIMs working, so I can't download any app. I am going to try to copy an app via apk on the SD. The good news is that the bootloader initial stop has disapeared, (but i still do not have any recovery)

Nothing to do with "install app unknown" o similar (sorry, my phone is in Italian). Even if i do have the apk terminal emulator, i Can't install because of the few app in list that i can unable to install unknown sources. In this list there isn't "File manager" .. i still have the error of parsing the package

If you downgrade from Pie to Oreo you will lost all connections. To get them back you must flash a Pie version of any Rom.
First of all flash the right and latest firmware.

I Would like to reburn another rom, but i can't because the option "Unlock OEM" is in "gray" not switchable, so for be is a bit hard. I am stuck..
Thanks anyway for your interest. I appreciated it.

Reggians said:
I Would like to reburn another rom, but i can't because the option "Unlock OEM" is in "gray" not switchable, so for be is a bit hard. I am stuck..
Thanks anyway for your interest. I appreciated it.
Click to expand...
Click to collapse
Flash the latest Magisk.zip to enable OEM unlock option.

WoKoschekk said:
Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')
Click to expand...
Click to collapse
Hi
I finally copy a term.apk and installed with success ! (i have no root permissions on the device)
when i give
Code:
evert_n:/ $ su
the answer is:
Code:
/system/bin/sh: su: not found
127|evert_n:/
if send the command with #
Code:
:/ $ # service call oem_lock 1 s16 allowed
i get null
Code:
127|evert_n:/
if i send the command without # (probably it is the cli after su level) like this
Code:
:/ $ service call oem_lock 1 s16 allowed
the answer is
Code:
service: Service oem_lock does not exist

WoKoschekk said:
Flash the latest Magisk.zip to enable OEM unlock option.
Click to expand...
Click to collapse
I have installed Magistik7.3.4.apk via filesystem but, i don't have connectivity and i can't install it via TWRP because i have the device locked so i can't even try to load TWRP via fastboot , so Magistik is not fully working unfortunatly..

Are you able to start the device in fastboot mode?
What is the error message when booting in TWRP?
For the "service oem_lock" command you need super user rights...

if you haven't solved it yet, use this to enable internet connection to your phone and you will be able to unlock the bootloader
https://github.com/Genymobile/gnirehtet

Has anyone solved this? Do I need to wait the 7 days to unlock it again?
I saw a thread where someone said they skipped the 7 days by changing the date of the device and rebooting, but that didn't work for me.

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.