Hey Guys,
I am very new here but have been seeing alot of helpful stuff on this massive forum. A bit about my self.
1st, i am not a developer - Just nosy and love some things you guys can do to Android Devices.. Android FTW
My name is Mike aka DJROETZ from South Africa. Will update my details as soon as i can.
The Question?
I have an unlocked and rooted Nexus 7 (2012) 3G Lollipop Update 5.1.1 ,I have been reading alot but i just cant seem to find where to put this info in to boot the device from dead and into the OS without pressing the power button. Im sure i am missing something small.
Could you guys maybe shed some light.
The Code Below i need to look for.
fastboot getvar all
(bootloader) product: herring
(bootloader) version-hardware: REV 51
(bootloader) version-baseband: I9020XXKB1
(bootloader) version-bootloader: I9020XXKA3
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
all:
finished. total time: 0.004s
and then
Code:
fastboot oem off-mode-charge 0
The Code i get when inputting fastboot getvar all
(bootloader) version-bootloader: 4.23
(bootloader) version-baseband: 1231_0.18.0_0409
(bootloader) version-hardware: PR
(bootloader) version-cdma: N/A
(bootloader) variant: tilapia
(bootloader) serialno: 015d46d95167fe07
(bootloader) product: tilapia
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: no
(bootloader) partition-size:bootloader: 0x0000000000600000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006fff00000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.250s
Please let me know what i am missing..
Your help will be much appreciated.
Actually,
Just put this in fastboot oem off-mode-charge 0
And seems to be working 100s.
After a nice long session of getting my phone to root and installing my first custom ROM, I was sad to see after booting successfully, there was no touch.
I thought, "oh well" and tried to flash back to stock. This is where I think I made a critical error. I tried flashing the stock OTA, Fastboot files, and the BACK_TO_STOCK files from the XDA thread. Nothing worked and I tried to change my slot, only to get the message "Fastboot: error: Device does not support slots." Additionally, when I try to flash-all from the fastboot files, it tells me i basically have no partitions. I do still have twrp though so all is not lost and I can boot into the bootloader.
tonafish12 said:
After a nice long session of getting my phone to root and installing my first custom ROM, I was sad to see after booting successfully, there was no touch.
I thought, "oh well" and tried to flash back to stock. This is where I think I made a critical error. I tried flashing the stock OTA, Fastboot files, and the BACK_TO_STOCK files from the XDA thread. Nothing worked and I tried to change my slot, only to get the message "Fastboot: error: Device does not support slots." Additionally, when I try to flash-all from the fastboot files, it tells me i basically have no partitions. I do still have twrp though so all is not lost and I can boot into the bootloader.
Click to expand...
Click to collapse
lol, your not totally bricked, sounds like you have a fastboot driver thats old
I had this problem too when I was trying to get TWRP + Magisk + EX kernel working.
I found that my Essential phone is pretty picky with what commands it accepts. Maybe this is due to a silent bootloader update, maybe not. A lot of commands work only if you spam them.
What Fastboot do you have?
aer0zer0 said:
lol, your not totally bricked, sounds like you have a fastboot driver thats old
Click to expand...
Click to collapse
I'm having the same issue as the OP so I grabbed the latest driver from essential (I was using an older release) but it hasn't made a difference.
Is there a known way to verify the partition structure on this device? For both slots
bavarianblessed said:
I'm having the same issue as the OP so I grabbed the latest driver from essential (I was using an older release) but it hasn't made a difference.
Is there a known way to verify the partition structure on this device? For both slots
Click to expand...
Click to collapse
You want to use the driver included in essential windows driver.exe on their website. The Google ones are a little goofy.
Can you do *fastboot --version* (that's minus minus version) and send the output?
Also try a different USB cable from the one that came with the phone, if you were using that one. Mine doesn't respond properly with that one, but a USB-A to USB-C cable from Anker that I bought works fine.
aer0zer0 said:
You want to use the driver included in essential windows driver.exe on their website. The Google ones are a little goofy.
Can you do *fastboot --version* (that's minus minus version) and send the output?
Click to expand...
Click to collapse
Yep, here is the version info. With some of the errors I was getting trying to flash it I grabbed the latest from Google
Code:
C:\ADB\PH1-Images-PPR1.181005.034>fastboot --version
fastboot version 28.0.1-4986621
Installed as C:\ADB\PH1-Images-PPR1.181005.034\fastboot.exe
dsip said:
Also try a different USB cable from the one that came with the phone, if you were using that one. Mine doesn't respond properly with that one, but a USB-A to USB-C cable from Anker that I bought works fine.
Click to expand...
Click to collapse
Yeah I've tried an Ankar and a Samsung so far. I've had better luck with another cable in the past though so going to try and find it.
EDIT
This is so odd. If I try to run this command a few times it finally takes?
Code:
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
all:
Finished. Total time: 0.000s
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
all:
Finished. Total time: 0.000s
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
(bootloader) version:0.5
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4192
(bootloader) version-baseband:2.0.c4-M2.0.3
(bootloader) version-bootloader:mata-84f7cce
(bootloader) variant:SPRINT
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1987357000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x100000000
(bootloader) has-slot:nvdef:yes
(bootloader) has-slot:dsp:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:abl:yes
(bootloader) has-slot:mdtp:yes
(bootloader) has-slot:mdtpsecapp:yes
(bootloader) has-slot:bluetooth:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:_b
(bootloader) slot-retry-count:_b:1
(bootloader) slot-unbootable:_b:no
(bootloader) slot-successful:_b:no
(bootloader) slot-retry-count:_a:7
(bootloader) slot-unbootable:_a:no
(bootloader) slot-successful:_a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:PM1#############
(bootloader) product:Mata
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
all:
Finished. Total time: 0.249s
bavarianblessed said:
Yep, here is the version info. With some of the errors I was getting trying to flash it I grabbed the latest from Google
Yeah I've tried an Ankar and a Samsung so far. I've had better luck with another cable in the past though so going to try and find it.
EDIT
This is so odd. If I try to run this command a few times it finally takes?
Click to expand...
Click to collapse
Do you have essentials windows driver executable installed?
aer0zer0 said:
Do you have essentials windows driver executable installed?
Click to expand...
Click to collapse
Yeah I have it installed. It was the cable! For real I would have thought the Samsung GS9 OEM cable would be high quality enough.
Anyway thanks for the help.
bavarianblessed said:
EDIT
This is so odd. If I try to run this command a few times it finally takes?
Code:
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
all:
Finished. Total time: 0.000s
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
all:
Finished. Total time: 0.000s
C:\ADB\PH1-Images-PPR1.181005.034>fastboot getvar all
(bootloader) version:0.5
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4192
(bootloader) version-baseband:2.0.c4-M2.0.3
(bootloader) version-bootloader:mata-84f7cce
(bootloader) variant:SPRINT
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1987357000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x100000000
(bootloader) has-slot:nvdef:yes
(bootloader) has-slot:dsp:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:abl:yes
(bootloader) has-slot:mdtp:yes
(bootloader) has-slot:mdtpsecapp:yes
(bootloader) has-slot:bluetooth:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:_b
(bootloader) slot-retry-count:_b:1
(bootloader) slot-unbootable:_b:no
(bootloader) slot-successful:_b:no
(bootloader) slot-retry-count:_a:7
(bootloader) slot-unbootable:_a:no
(bootloader) slot-successful:_a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:PM1#############
(bootloader) product:Mata
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
all:
Finished. Total time: 0.249s
Click to expand...
Click to collapse
That seems to be a normal thing with Essential devices to be honest, I've had 2 and both have been lets say slow and picky at accepting some ADB/Fastboot commands. On the OPENAM variant it was even more of a problem (no idea why), but the white OPENUS replacement I have now hasn't been too much of an issue. I've not had to specify everytime I'm in Fastboot which slot I want to flash to specifically, for example...
At least its not like we have plenty of Pie ROMs to flash over and over, so ultimately its not that much of an issue.
CamoGeko said:
EDIT
This is so odd. If I try to run this command a few times it finally takes?
That seems to be a normal thing with Essential devices to be honest, I've had 2 and both have been lets say slow and picky at accepting some ADB/Fastboot commands. On the OPENAM variant it was even more of a problem (no idea why), but the white OPENUS replacement I have now hasn't been too much of an issue. I've not had to specify everytime I'm in Fastboot which slot I want to flash to specifically, for example...
At least its not like we have plenty of Pie ROMs to flash over and over, so ultimately its not that much of an issue.
Click to expand...
Click to collapse
It just gets corrupted easily. I found formatting fixes it.either with twrp, or the verity disabler by zackptg.then flash the whole current stock firmware and start over. They got some issues internally with easy corruption it seems
CamoGeko said:
That seems to be a normal thing with Essential devices to be honest, I've had 2 and both have been lets say slow and picky at accepting some ADB/Fastboot commands. On the OPENAM variant it was even more of a problem (no idea why), but the white OPENUS replacement I have now hasn't been too much of an issue. I've not had to specify everytime I'm in Fastboot which slot I want to flash to specifically, for example...
At least its not like we have plenty of Pie ROMs to flash over and over, so ultimately its not that much of an issue.
Click to expand...
Click to collapse
Actually in my case it was just the cable. Using the known good cable that command will work every single time as well as any others I try. Mine is a white SPRINT variant.
For the record this is the cable that I'm using
Try fastboot flashing Google's Offical GSI?
MY FRIENDS, HELP ME:NOKIA 4.2 Panther - my A and b slots are gone, Nokia flash tool says current slot invalid, Adb also :
current-slot: INVALID
finished. total time: 0.002s
here is what I have:
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3946070
(bootloader) variant:QRD eMMC
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) logical-block-size:0x200
(bootloader) erase-block-size:0x200
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1ff00000
(bootloader) slot-count:2
(bootloader) current-slot:INVALID
(bootloader) slot-retry-count:b:7
(bootloader) slot-success:b:No
(bootloader) slot-active:b:No
(bootloader) slot-unbootable:b:No
(bootloader) slot-retry-count:a:0
(bootloader) slot-success:a:No
(bootloader) slot-active:a:No
(bootloader) slot-unbootable:a:Yes
(bootloader) has-slot:userdata: No
(bootloader) has-slot:demoapp: No
(bootloader) has-slot:elabel: No
(bootloader) has-slot:wt_log: No
(bootloader) has-slot:logdump: No
(bootloader) has-slot:dpo: No
(bootloader) has-slot:msadp: No
(bootloader) has-slot:apdp: No
(bootloader) has-slot:custom: Yes
(bootloader) has-slot:keymaster: Yes
(bootloader) has-slot:cmnlib64: Yes
(bootloader) has-slot:cmnlib: Yes
(bootloader) has-slot:mcfg: No
(bootloader) has-slot:syscfg: No
(bootloader) has-slot:mdtp: Yes
(bootloader) has-slot:dip: No
(bootloader) has-slot:mota: No
(bootloader) has-slot:limits: No
(bootloader) has-slotem: No
(bootloader) has-slot:config: No
(bootloader) has-slot:keystore: No
(bootloader) has-slot:misc: No
(bootloader) has-slotersist: No
(bootloader) has-slot:vendor: Yes
(bootloader) has-slot:system: Yes
(bootloader) has-slot:devinfo: No
(bootloader) has-slot:boot: Yes
(bootloader) has-slot:vbmeta: Yes
(bootloader) has-slot:dtbo: Yes
(bootloader) has-slot:aboot: Yes
(bootloader) has-sloticture: Yes
(bootloader) has-slot:splash: Yes
(bootloader) has-slot:sec: No
(bootloader) has-slot:fsg: No
(bootloader) has-slotDR: No
(bootloader) has-slot:modemst2: No
(bootloader) has-slot:modemst1: No
(bootloader) has-slot:dsp: Yes
(bootloader) has-slot:devcfg: Yes
(bootloader) has-slot:tz: Yes
(bootloader) has-slot:rpm: Yes
(bootloader) has-slot:sbl1: Yes
(bootloader) has-slot:ssd: No
(bootloader) has-slot:fsc: No
(bootloader) has-slot:modem: Yes
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x527679e00
(bootloader) partition-type:demoapp:raw
(bootloader) partition-size:demoapp: 0x4000000
(bootloader) partition-type:elabel:raw
(bootloader) partition-size:elabel: 0x500000
(bootloader) partition-type:wt_log:raw
(bootloader) partition-size:wt_log: 0x4000000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:custom_b:raw
(bootloader) partition-size:custom_b: 0x3200000
(bootloader) partition-type:custom_a:raw
(bootloader) partition-size:custom_a: 0x3200000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x100000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x100000
(bootloader) partition-type:cmnlib64_b:raw
(bootloader) partition-size:cmnlib64_b: 0x100000
(bootloader) partition-type:cmnlib64_a:raw
(bootloader) partition-size:cmnlib64_a: 0x100000
(bootloader) partition-type:cmnlib_b:raw
(bootloader) partition-size:cmnlib_b: 0x100000
(bootloader) partition-type:cmnlib_a:raw
(bootloader) partition-size:cmnlib_a: 0x100000
(bootloader) partition-type:mcfg:raw
(bootloader) partition-size:mcfg: 0x400000
(bootloader) partition-type:syscfg:raw
(bootloader) partition-size:syscfg: 0x80000
(bootloader) partition-type:mdtp_b:raw
(bootloader) partition-size:mdtp_b: 0x2000000
(bootloader) partition-type:mdtp_a:raw
(bootloader) partition-size:mdtp_a: 0x2000000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:mota:raw
(bootloader) partition-size:mota: 0x80000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-typeem:raw
(bootloader) partition-sizeem: 0x4000000
(bootloader) partition-type:config:raw
(bootloader) partition-size:config: 0x8000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-size:vendor_b: 0x28000000
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-size:vendor_a: 0x28000000
(bootloader) partition-type:system_b:raw
(bootloader) partition-size:system_b: 0xc0000000
(bootloader) partition-type:system_a:raw
(bootloader) partition-size:system_a: 0xc0000000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x100000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x4000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x4000000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b: 0x10000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a: 0x10000
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-size:dtbo_b: 0x800000
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-size:dtbo_a: 0x800000
(bootloader) partition-type:aboot_b:raw
(bootloader) partition-size:aboot_b: 0x400000
(bootloader) partition-type:aboot_a:raw
(bootloader) partition-size:aboot_a: 0x400000
(bootloader) partition-typeicture_b:raw
(bootloader) partition-sizeicture_b: 0x600000
(bootloader) partition-typeicture_a:raw
(bootloader) partition-sizeicture_a: 0x600000
(bootloader) partition-type:splash_b:raw
(bootloader) partition-size:splash_b: 0x600000
(bootloader) partition-type:splash_a:raw
(bootloader) partition-size:splash_a: 0x600000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0xa00000
(bootloader) partition-typeDR:raw
(bootloader) partition-sizeDR: 0x8000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x400000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x400000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x1000000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x1000000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x40000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x40000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x200000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x200000
(bootloader) partition-type:rpm_b:raw
(bootloader) partition-size:rpm_b: 0x80000
(bootloader) partition-type:rpm_a:raw
(bootloader) partition-size:rpm_a: 0x80000
(bootloader) partition-type:sbl1_b:raw
(bootloader) partition-size:sbl1_b: 0x80000
(bootloader) partition-type:sbl1_a:raw
(bootloader) partition-size:sbl1_a: 0x80000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0x5400000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0x5400000
(bootloader) hw-revision:10000
(bootloader) pcb_sn:4931806751002093
(bootloader) serialno:4T89571EA1932701086
(bootloader) kernel:lk
(bootloader) productanther
(bootloader) productid:4T89571EA1932701086
(bootloader) MEID:00000000000000
(bootloader) IMEI1:352900100148118
(bootloader) IMEI0:352900100148100
(bootloader) proof:1
all:
finished. total time: 0.805s
WHAT TO DO? THERE NO CHANCE TO ACTIVATE ANY SLOT AND FLASH TO ACTIVE SLOT AS SLOTS ARE INVALID. HELP PLEASE
Hello
any one can help please, I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (loop on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
-------------
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3447000
(bootloader) variant:TULIP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x12c00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5ebb79e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x100000000
(bootloader) serialno:bc13c89a
(bootloader) kernel:lk
(bootloader) product:TULIP
all:
finished. total time: 0.022s
------
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
-------
Thanks
So I cross flashed (LGUP Partition DL) F800 Pie to a US996 and it was working fine except I no longer had cell service. So I flashed(QFIL to get a good download mode, then LGUP Partition DL) back to US99620f and now I'm stuck in fastboot mode. I have a feeling that the F800 flash redid the partitions and the US996 is not happy. I've build a QFIL flat package build and I still get the same results. If I flash F800 back on it will boot just fine, but I have to use QFIL to regain download mode and I don't have root or TWRP to try other methods.
I can access Download and Recovery modes too.
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x4d000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xced000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x180000000
(bootloader) serialno:LGUS99680d946a4
(bootloader) kernel:lk
(bootloader) product:MSM8996
(bootloader) unlocked:no
Things I can do:
Recovery,Stock - yes
Download Mode - Yes
9008 Mode - yes
Wiped User/Cache "factory reset" - Yes
Boot into F800 Pie - yes
I have spent the last 12 hours trying to fix this. I am tech savvy but have never flashed a cellphone before, hence I dunno if I am doing something wrong. And apologies if my terms aren't correct. please correct me when I am wrong.
Phone is a moto G5 plus XT1681 (according to imei), one day it powered to fastboot (see image 1) and what ever I try to press, I get an error. (see image 2)
I followed and tried many guides. but especially this one
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
when I try to run the first line of the script I get the following error.
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
If I keep advancing in the code I get the same error than this guy
Bricked MOTO G5(XT1676) stucked at fastboot menu
hELLO.. I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from...
forum.xda-developers.com
the phone is detectable with command "fastboot devices"
Despite running this, the phone still stays "oem_locked" like in the images
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot oem unlock
(bootloader) feature disabled
OKAY [ 0.017s]
Finished. Total time: 0.018s
I tried also installing TWRP and I get this error (because maybe that bypasses a locked bootloader?)
"(bootloader) Preflash validation failed
FAILED (remote failure)ยจ
And here is the log for what I learned that you always ask for
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: ca31f0ad
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 423FF92E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.175s
QUESTIONS
Am I just confusing rom because of firmware or country?
is all of this because my bootloader seems locked?
do I just need to get to recovery mode first?
I just want the phone to work, don't care for the data inside.
Other people that seem to be stuck with the same problem
https://forum.xda-developers.com/t/...-question-noob-friendly.3963645/post-85232253
THANKS IN ADVANCE AND SORRY FOR THE LONG POST I WANTED TO GIVE ALL MY INFORMATION AND RESEARCH
Same problem here.