Hi ,
Need some help here, after shutting down my Pixel-C, the Pixel-C now wont accept Charge and when power adapter is plugged in , it only show Google Wording and later screen turn off.,with plugged condition, tapping the back light bar will not light up .
When Power source is plugged in ,While holding the Power Key + Vol Down or Vol UP, the device will turn ON with respective menu
1. Front recovery Menu(POwer+ Down Vol)
Shown the Drop down list of Reboot, reboot to recovery, turn off , USB recovery modem, Fast boot mode
selecting to "reboot to recovery " menu item will reboot to see Google Splash screen and Unit shutdown (Lightbar indicator will not show anything).
selecting "Switch off device option- Screen turn off , rear lightbar when tapped is showing One segment of red bar
selecting to fast boot mode will go to fastboot mode with screen prompt "waiting for fastboot command"
2. Fast boot ( Power + Up Vol ).
selecting to fast boot mode will go to fastboot mode with screen prompt "waiting for fastboot command"
The Pixel-C when in fastboot mode is recognizable by PC, i have installed the bootloader interface, "fastboot devices" command is working to list the connected device.
As my device is bootloader locked. I can not use "fastboot flashing unlock" (throw errors) and "fastboot boot recovery.img" (hopefully to boot to recovery menu to conduct factory reset).
THe pixel-c is not able to go to recovery mode, no chance to enable ADB interface , that is to say i cant do cache wipe,factory reset....
Anotherthing that i logged with "fastboot getvar all"
There is a field is indicating battery voltage @ ZERO I think this is the real issue, it may not be real of battery @zero unless there is broken traces.
Code:
C:\download\phones\platform-tools>fastboot boot recovery.img
creating boot image...
creating boot image - 13518848 bytes
Sending 'boot.img' (13202 KB) OKAY [ 0.335s]
Booting FAILED (remote: 'image verification failed')
fastboot: error: Command failed
C:\download\phones\platform-tools>fastboot flashing unlock
FAILED (remote: 'Enable OEM unlock is not set')
fastboot: error: Command failed
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< fastboot fastboot getvar all >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
C:\download\phones\platform-tools>fastboot getvar all > c:\download\pixelCInfo.txt
(bootloader) version: 0.3
(bootloader) version-bootloader: Google_Smaug.7900.139.0
(bootloader) version-baseband: N/A
(bootloader) product: dragon
(bootloader) secure: yes
(bootloader) max-download-size: 0x10000000
(bootloader) partition-type:boot: ext4
(bootloader) partition-type:kernel-a: ext4
(bootloader) partition-type:kernel-b: ext4
(bootloader) partition-type:recovery: ext4
(bootloader) partition-type:kernel: ext4
(bootloader) partition-type:system: ext4
(bootloader) partition-type:system-a: ext4
(bootloader) partition-type:vendor: ext4
(bootloader) partition-type:vendor-a: ext4
(bootloader) partition-type:cache: ext4
(bootloader) partition-type:data: ext4
(bootloader) partition-type:userdata: ext4
(bootloader) partition-type:metadata: ext4
(bootloader) partition-type:lnx: ext4
(bootloader) partition-type:misc: ext4
(bootloader) partition-type:persistent: ext4
(bootloader) partition-type:system-b: ext4
(bootloader) partition-type:vendor-b: ext4
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-size:kernel-a: 0x2000000
(bootloader) partition-size:kernel-b: 0x2000000
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-size:kernel: 0x2000000
(bootloader) partition-size:system: 0xe0000000
(bootloader) partition-size:system-a: 0xe0000000
(bootloader) partition-size:vendor: 0x13000000
(bootloader) partition-size:vendor-a: 0x13000000
(bootloader) partition-size:cache: 0x19000000
(bootloader) partition-size:data: 0x62ef00000
(bootloader) partition-size:userdata: 0x62ef00000
(bootloader) partition-size:metadata: 0x4000000
(bootloader) partition-size:lnx: 0x2000000
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-size:persistent: 0x80000
(bootloader) partition-size:chromeos: 0x747c00000
(bootloader) partition-size:mbr: 0x200
(bootloader) partition-size:gpt: 0x4200
(bootloader) partition-size:RO_SECTION: 0x3f0000
(bootloader) partition-size:RO_VPD: 0x10000
(bootloader) partition-size:RW_SECTION_A: 0x580000
(bootloader) partition-size:RW_SECTION_B: 0x580000
(bootloader) partition-size:bootloader: 0x1000000
(bootloader) unlocked: no
(bootloader) off-mode-charge: 1
(bootloader) battery-voltage: 0 mV
(bootloader) variant:
(bootloader) battery-soc-ok: no
(bootloader) Bdev-size:mmc: 31268536320
(bootloader) Bdev-size:flash: 16777216
(bootloader) Gbb-flags: 0x0
(bootloader) Oem-version:RO: RO: ID NOT FOUND
(bootloader) Oem-version:RW_A: RW A: ID NOT FOUND
(bootloader) Oem-version:RW_B: Google_Smaug.7900.139.0
all: Done!
Finished. Total time: 0.514s
Other Info.
1.Adapter is working correctly which is validated OK with charging of another 2 pixel 3/4 phones.
2.: Bootloader locked, per factory out condition, Developer mode is ON but OEM Unlock is NOT SET , only use Google OTA updates to the latest.
3.This is my use only device that i have never unlocked since purchased
4. WIthout Plugged in, the device will not ON.
5. The device wont accept charges, Battery reset method recommended by Google " Holding Vol rockers( Up+Down ) +Power" while plugged in , remove adapter USB-C male plug and release the 3 buttons ,wait for 30 sec and charge..NO GO ..
I've got the exact same problem, any luck? I'm going to try replacing the battery I think
Related
Hi all,
Sorry if this thread is in the wrong area.
I have in my possession a Nexus 5X which is stuck in a boot loop. I don't think it's a case of the power button being held down because the phone behaves differently depending on whether I hold the power button down or not.
I can boot into bootloader/fastboot mode which is locked. I have the standard options to Start/Restart bootloader/Recovery mode/Power off. If I try to get into recovery mode from here, the phone enters "download mode" for a short amount of time. After that, the bootloop begins again and I can only get the phone back to bootloader at best.
If I try to use the comment fastboot oem unlock I will get the message (remote: oem unlock is not allowed). I believe this is because don't have USB debugging/developer options enabled. I can't turn the phone on to enable this.
I have tried using Nexus Root Toolkit to unlock the bootloader (using the Flash Stock + Unroot and Soft-Bricked/Bootloop option) and everything seems to run fine until it restarts the phone. This triggers the boot loop again and the Nexus Root Toolkit hangs "waiting for phone..." after previously having been able to detect it.
I've tried using WinDroid Toolkit v3.1 also to unlock the bootloader without success.
Quite simply, is it possible to unlock the bootloader while the phone is in this state? I know this is a common problem with these phones but I'm not convinced this can't be fixed at home yet!
Thanks in advance for any help.
Some extra info:
fastboot getvar all
(bootloader) product: bullhead
(bootloader) off-mode-charge: 1
(bootloader) max-download-size: 0x20000000
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4017mV
(bootloader) version-hardware: rev_1.0
(bootloader) version-baseband: M8994F-2.6.36.2.20
(bootloader) version-bootloader: BHZ11h
(bootloader) variant: bullhead LGH791 32GB
(bootloader) serialno: (hide)
(bootloader) kernel: lk
(bootloader) secure-boot: yes
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0xa80000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x65a3fb800
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x6000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:vendor: 0xf800000
(bootloader) unlocked: no
Seems u are having problems with bootloader, have u tried flash stock bootloader image via fastboot and then proceed with OEM unlock?
imor said:
Seems u are having problems with bootloader, have u tried flash stock bootloader image via fastboot and then proceed with OEM unlock?
Click to expand...
Click to collapse
No, I haven't tried that. I'll give it a go later. Assumed I couldn't flash anything with a locked bootloader.
HTC 10 boot loop problem no download no recovery mode. try all keys.
C:\adb>htc_fa stboot oem get_identifier_token
... FAILunknown command
FAILED (remote: unknown command)
Try to flash recovery error (remote: cannot flash this partition in s-on state)
information in fastboot
C:\adb>fastboot devices
FA667BN03252 fastboot
C:\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x60e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA667BN03252
all:
finished. total time: 0.356s
sharrymz said:
HTC 10 boot loop problem no download no recovery mode. try all keys.
C:\adb>htc_fa stboot oem get_identifier_token
... FAILunknown command
FAILED (remote: unknown command)
Try to flash recovery error (remote: cannot flash this partition in s-on state)
information in fastboot
C:\adb>fastboot devices
FA667BN03252 fastboot
C:\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x60e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA667BN03252
all:
finished. total time: 0.356s
Click to expand...
Click to collapse
Hold power and vol down for 30 seconds or so. If that doesbt boot into bootloader mode you probably have a brick. You need to give more info on what you have done to get into this state?
yldlj said:
Hold power and vol down for 30 seconds or so. If that doesbt boot into bootloader mode you probably have a brick. You need to give more info on what you have done to get into this state?
Click to expand...
Click to collapse
He already said he tried all keys, but it would be awesome as you suggest to give a summary of what he did
darkriff said:
He already said he tried all keys, but it would be awesome as you suggest to give a summary of what he did
Click to expand...
Click to collapse
Well to me all keys doesnt mean vol down and power. All keys to me means vol up, down and power.
I try it many time Hold power and vol down for 30 seconds still same
its a emmc problem i read it
sharrymz said:
I try it many time Hold power and vol down for 30 seconds still same
its an emmc problem i read it
Click to expand...
Click to collapse
Mine also has the same problem. But not after a software update. It came out from nowhere...
During the last week, the phone was always giving the notification that suggests me to use the supplied cable and charger when I charge it. But It was always gone after a few attempts...
Now, my phone has no battery. When I put the charger, It automatically enters the bootloop (without pressing the power key). No recovery no download mode...
I searched some pages online and try some tricks (like battery re-calibration), but no chance...
I couldn't find a real solution to this.
Unforutanely, I don't have the warranty.
Any suggestions?
Thanks.
I have the exact the same problem
Did someone achieved to get the device recognized as fastboot device on PC?. Going on advanced reboot and rebooting into the bootloader or with "adb reboot bootloader" it goes into bootloader/fastboot mode, when plugged into pc, it appears at fastboot in device manager but not in "fastboot devices" neither on "adb devices". Tried the same on linux, maybe we can unlock the bootloader while in fastboot, because we may run "fastboot get var all" and print and unlock code, example of the code:
fastboot getvar all
Code:
[COLOR="red"]*code taken from a amazon fire tablet*[/COLOR]
(bootloader) partition-type:LOGO: unknown
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: unknown
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-size:EXPDB: 1160000
(bootloader) partition-type:EXPDB: unknown
(bootloader) partition-size:DKB: 100000
(bootloader) partition-type:DKB: unknown
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) off-mode-charge: 1
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: FORD
(bootloader) version: 0.5
(bootloader) unlock_status: false
(bootloader) unlock_version: 1
(bootloader) [COLOR="Red"]unlock_code: 0x32c5657dd83d5139[/COLOR]
(bootloader) prod: 1
all: Done!!
try yourself. Or ask help from @ggow
Thats why im posting here, my device in bootloader mode isnt recognized in any of my pc's.. Even in linux or Windows.
ADB Fastboot and USB Drivers Installer:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Root Guide:
https://forum.xda-developers.com/realme-3/how-to/rooting-guide-realme-3-t3927028
Warning:
https://forum.xda-developers.com/re...me-3-users-t3930142/post79525847#post79525847
Soft Brick/Infinite Boot loop Recovery Guide:
https://forum.xda-developers.com/realme-3/how-to/realme-3-recover-soft-brick-boot-loop-t3920401
Important Files for this Phone:
https://forum.xda-developers.com/realme-3/how-to/files-partition-dump-realme-3-t3931069
Fix Magisk Lagging issue:
https://forum.xda-developers.com/android/development/magisk-lagging-issue-fix-t4012863
Kernel Sources Link:
https://forum.xda-developers.com/realme-3/how-to/realme-3-kernel-sources-link-t3920396
Flashing GSI:
https://forum.xda-developers.com/realme-3/how-to/flasing-gsi-realme-3-t3944026
Installing TWRP:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
Access Linux commands in TWRP:
https://forum.xda-developers.com/android/general/complete-linux-environment-setup-twrp-t4013271
Access files using adb from pc in TWRP:
https://forum.xda-developers.com/android/general/tool-adb-overlay-t3921133
Bootloader Unlock Guide:
https://forum.xda-developers.com/realme-3/how-to/guide-bootloader-unlock-guide-realme-3-t3999463
How I got the partitions from this phone:
https://forum.xda-developers.com/showpost.php?p=79793878&postcount=53
--------------------------------------------------------
How to recover this phone from hard brick(You have to do this before hard bricking your device ):
Note: This process is not tested yet, and probably will cause hard brick, but if this process is successful, then you will never hard brick your device again as you will be able to recover from any future hard brick.
The idea is, we can use miracle tool to recover realme U1 from hard brick phone, if we can flash preloaders from realme U1 into realme 3, I think this phone will also support recovery from hardbrick
1. You will have to flash the realme U1 preloaders into this phones preloader partition using fastboot:
https://mega.nz/folder/TVtXGK4R#szJzw48J8_k8PvH5u0y-nA
2. Whenever you are hard bricked, you can use miracle tool to recover:
https://mega.nz/file/T64CwapZ#MBAWc2PbQwlirPsev83vfxjfBQKPY8M0rIKkpP_bzz8
--------------------------------------------------------
Infinite Bootloop:
press power + vol up till blank screen, then leave the buttons quickly
now press power + vol down to boot to fastboot
----------------------------------------------------
Disable Software Update:
In lucky patcher, disable these packages:
Software Update Interface
Software Updates
System Upgrade Services
Update Service
.
-----------------------------------------------
Display and control device from pc:
https://github.com/Genymobile/scrcpy
----------------------------------------------
Fastboot Environment variable:
Code:
fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) variant:
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x80000
(bootloader) hw-revision: ca00
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4309mV
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:otp: 2b00000
(bootloader) partition-type:otp: raw data
(bootloader) partition-size:userdata: 5727fbe00
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1b000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 123000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:vendor: 53000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:odm: 10000000
(bootloader) partition-type:odm: ext4
(bootloader) partition-size:tee2: c00000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:dtbo: 1000000
(bootloader) partition-type:dtbo: raw data
(bootloader) partition-size:logo: 1000000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:boot: 2000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 500000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 500000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:opporeserve3: 4000000
(bootloader) partition-type:opporeserve3: raw data
(bootloader) partition-size:nvram: 4000000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:gz2: 1000000
(bootloader) partition-type:gz2: raw data
(bootloader) partition-size:gz1: 1000000
(bootloader) partition-type:gz1: raw data
(bootloader) partition-size:cam_vpu3: f00000
(bootloader) partition-type:cam_vpu3: raw data
(bootloader) partition-size:cam_vpu2: f00000
(bootloader) partition-type:cam_vpu2: raw data
(bootloader) partition-size:cam_vpu1: f00000
(bootloader) partition-type:cam_vpu1: raw data
(bootloader) partition-size:sspm_2: 100000
(bootloader) partition-type:sspm_2: raw data
(bootloader) partition-size:sspm_1: 100000
(bootloader) partition-type:sspm_1: raw data
(bootloader) partition-size:scp2: 600000
(bootloader) partition-type:scp2: raw data
(bootloader) partition-size:scp1: 600000
(bootloader) partition-type:scp1: raw data
(bootloader) partition-size:spmfw: 100000
(bootloader) partition-type:spmfw: raw data
(bootloader) partition-size:md1img: 6400000
(bootloader) partition-type:md1img: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:sec1: 200000
(bootloader) partition-type:sec1: raw data
(bootloader) partition-size:persist: 3000000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:seccfg: 800000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect2: 878000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: 800000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 4000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:nvcfg: 2000000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:expdb: 1400000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:oppo_custom: 100000
(bootloader) partition-type:oppo_custom: raw data
(bootloader) partition-size:opporeserve2: 4000000
(bootloader) partition-type:opporeserve2: raw data
(bootloader) partition-size:opporeserve1: 800000
(bootloader) partition-type:opporeserve1: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:recovery: 4000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot_para: 100000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:preloader: 80000
(bootloader) partition-type:preloader: raw data
(bootloader) serialno: FEGUFIK7IR8SAITC
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: oppo6771_18601
(bootloader) slot-count: 0
(bootloader) version-baseband: MOLY.LR12A.R2.PIE.RM.PR1.TC16.SP.V1.P4
(bootloader) version-bootloader: oppo6771_18601-a78000c-20190302181824-2
(bootloader) version-preloader:
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.402s
------------------------------------------------------
Boot to recovery from fastboot:
fastboot oem reboot-recovery
-----------------------------------------------------
Patch android with smali patcher:
https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
-----------------------------------------------------
Fastboot commands:
Fastboot commands:
0x%X
getvar version
signature
flash:
erase:
continue
directing the bootloader to boot into os, also used when in bootloop,
reboot
reboot-bootloader
product
prints the product id, example for realme u1, it will print OPPO6771_18611
secure
unlocked
warranty
off mode charge status is out of boundary
download: max-download-size
Shows max size of partition that can be used for flashing
Fastboot OEM commands: (add fastboot at start of each command)
oem p2u
fastboot oem p2u on and fastboot oem p2u off, these enable or disable the redirection of Linux kernel messages to the UART.
oem reboot-recovery
reboots to recovery
oem off-mode-charge
Next, there’s the fastboot oem off-mode-charge (enable|disable) command. This command determines whether or not your device will automatically turn on when a power source is detected.
oem unlock
unlocks the bootloader (similar to oem unlock in developers option)
oem lock
locks the bootloader
oem key
oem lks
check bootloader lock or unlocked
flashing unlock
Allow flashing in partition
flashing lock
locks flashing in partition
flashing get_unlock_ability
checks whether oem is unlocked or locked
oem scp_status
oem scp_log_thru_ap_uart
oem mrdump
Maybe same as ramdump, dump ram data contents to sd card
https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
---------------------------------------------------------------------------
Modes:
Downlaod or meta mode:
first power off
volup+vol down+connect the usb
or
first power off
connect your phone to pc and then press all buttons on phone together
REcovery mode:
(you can go, adb reboot recovery, or by fastboot boot recovery.img )any key combination, if fastboot flash is locked (or wait for sometime in bootloop, it will boot itself) (flash asop A/B version, it will boot to recovery), maybe also vol up+vol down + power
Fastboot mode: (to get out of fastboot, press power for sometime)
(will not work, if fastboot flash is locked )
vol down+power
To power off when stuck:
power + vol up
stuck in boot:
power+vol up (till the phone doesn't switch off)
Force power off:
power+ vol up
-------------------------------------
I am currently not doing any development for this phone, so I will not be replying to any of the realme 3 thread, I kindly request you to search all my threads for answer rather than asking questions.
I hope this will help someone who would like to develop something for this phone.
Hi, I've done something real wrong with this phone.
In the past I've rooted the phone and installed lineageOS. Everithing was working fine till 2 days ago I've did a factory reset from the menu, at reboot I had only TWRP.
I've then dowloaded the stock image and installed it from twrp.
After reboot screen was black, and is still black today :-(
If I long press power button and volume up I can see the device from adb.
I can also reboot (using adb, because I can't interact with phone buttons) in fastboot mode using adb.
This is the output of get var all command:
```
➜ platform-tools ./fastboot getvar all
< waiting for any device >
(bootloader) crc:1
(bootloader) anti:1
(bootloader) DP:0x0
(bootloader) token:9ovLp3D0s7vjKK+0oXEzy14Ujpk=
(bootloader) board_version:1.4.0
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3922
(bootloader) version-baseband:`���
(bootloader) version-bootloader:`���
(bootloader) variant:MSM UFS
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xD247FB000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x140000000
(bootloader) wcnss:1
(bootloader) serial:f9fcad2c
(bootloader) product:sagit
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.002s
➜ platform-tools
```
I've tried a lot of different commands, but I don't know if the phone is bricked or still working, for example I've downloaded the latest lineage os from here: https://download.lineageos.org/sagit, then tried:
`/fastboot flashall lineage-18.1-20210923-nightly-sagit-signed.zip`
But the command is stuck with the blinking cursor. I've also tried different usb ports on this pc, I've tried from windows and from linux without luck.
I've to throw away this phone? there's some hope?
Thank you