Hello everyone! I am in dire need of help.
So I recently decided to acquire a regular Motorola G7 because I had heard its battery is fantastic. This far, I have been loving it.
But silly me decided I wanted to explore OEM boot unlocking to eventually root the device. After successfully completing theses tasks, I installed the TWRP recovery. Sadly, something (must have) went wrong because when I tried to reboot, the phone went into hard brick. Completely unresponsive, holding both power and vol. down button for 2+ minutes did nothing. I basically have exhausted every Internet recommendations thus far and nothing has been fruitful.
I have been able to get the Qualcomm Port 9008 (COM3) to show up in device manager when I hold power and vol. down. Also, the program QPST also recognizes a phone in Sahara download mode (although I have no idea what it means nor what to do with that, if anything).
So here I am, asking for your help. I have read somewhere that a blankflash zip file could allow me to restore my phone but alas, I wasn't able to find any nor would I know what to do with it.
I would greatly appreciate any help.
Regards,
Afireblood.
I have managed to find a way to potentially salvage my bricked phone, using QIFL tool to flash a stock rom. However, to do so I need some files (which are specific to the Moto G7 - any other would not do). They are:
programmer (firehose?).mbn
rawprogram.xml
patch.xml
I tried contacting Motorola directly to get those file but they basically told me to get lost.
If anyone has any clue where I could find that (except everywhere on Google - it hasn't been helpful), I would very much appreciate it!
Hi,
This post here is for a G4 model, but perhaps it can help you.
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Seems like you need Motorola RSD, and blankflash file.
crs77 said:
Hi,
This post here is for a G4 model, but perhaps it can help you.
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Seems like you need Motorola RSD, and blankflash file.
Click to expand...
Click to collapse
Hey criss77, thanks for your reply.
That indeed seems to be exactly what I need. I tried everything I could find and it doesn't work. I will need the specific Moto G7 blankflash.zip from Motorola, but I doubt they'll ever willingly release that.
I will try anyway and see if I can find a way.
Cheers!
afireblood said:
Hey criss77, thanks for your reply.
That indeed seems to be exactly what I need. I tried everything I could find and it doesn't work. I will need the specific Moto G7 blankflash.zip from Motorola, but I doubt they'll ever willingly release that.
I will try anyway and see if I can find a way.
Cheers!
Click to expand...
Click to collapse
Contacted Motorola, spoke with a few of their agents for an hour or so before they told me they wouldn't help because the warranty was voided when the bootloader was unlocked. I mean I know it would be but for ****'s sake, can't they just give me the files so I can repair the phone? I know they have them. How were older phones blankflash.zip files made public then?
Any luck finding a blankflash.zip file for the moto g7?
I am in the same boat.
Hi. I messed up my device after a faulty Magisk update. Hard bricked and unresponsive.
Hi folks! I've been working on various attempts to resolve this hardbricked G7 issue. Among them, using a Loader.img file flashed onto an SD card to boot into a bootloader, as well as attempting to create our own blankflash file. Here is a link to a post in another thread that provides everything I've attempted so far, and the files/links for anyone who wants to see if they are smarter/more successful than I at fixing our phones:
https://forum.xda-developers.com/showpost.php?p=79875059&postcount=27
If anyone manages to fix this, or sees an error in what I've attempted so far, let me know! Kthxbai
TerrestrialHost said:
If anyone manages to fix this, or sees an error in what I've attempted so far, let me know! Kthxbai
Click to expand...
Click to collapse
I managed to create a working blank flash for my XT1962-5 (RETEU) and posted my results in this thread.
I have a good working image but does anyone know how to force the g7 in to qd mode please with a working rom can't get it to work from recovery just bounces back to stock rom
Qld cable or open up back to short out test point after unhooking battery ribbon
https://www.ebay.com/i/163334124024...Uu1Gl8r2wR8ooz-w6O4F73SftBRGWRbwaAnECEALw_wcB
I need to re-format my phone somehow
I have a g7 amz variety river. i had the bootloader unlocked and the system rooted with twrp and Magisk. and then somehow all of my partitions vanished. it stays in fastboot mode when its on and i get the following results when I attempt to flash it...
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.172s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (7419 KB) OKAY [ 0.430s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash modem_a NON-HLOS.bin
(bootloader) is-logical:modem_a: not found
Sending 'modem_a' (65900 KB) OKAY [ 2.279s]
Writing 'modem_a' (bootloader) Invalid partition name modem_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash fsg_a fsg.mbn
(bootloader) is-logical:fsg_a: not found
Sending 'fsg_a' (11612 KB) OKAY [ 0.564s]
Writing 'fsg_a' (bootloader) Invalid partition name fsg_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst1
Erasing 'modemst1' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst2
Erasing 'modemst2' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash dsp_a adspso.bin
(bootloader) is-logical:dsp_a: not found
Sending 'dsp_a' (16384 KB) OKAY [ 0.718s]
Writing 'dsp_a' (bootloader) Invalid partition name dsp_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash logo_a logo.bin
(bootloader) is-logical:logo_a: not found
Sending 'logo_a' (2115 KB) OKAY [ 0.251s]
Writing 'logo_a' (bootloader) Invalid partition name logo_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot_a boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 1.307s]
Writing 'boot_a' (bootloader) Invalid partition name boot_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash dtbo_a dtbo.img
(bootloader) is-logical:dtbo_a: not found
Sending 'dtbo_a' (564 KB) OKAY [ 0.188s]
Writing 'dtbo_a' (bootloader) Invalid partition name dtbo_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system_a system.img_sparsechunk.0
(bootloader) is-logical:system_a: not found
Sending 'system_a' (261765 KB) OKAY [ 8.479s]
Writing 'system_a' (bootloader) Invalid partition name system_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system_a system.img_sparsechunk.1
(bootloader) is-logical:system_a: not found
Sending 'system_a' (257944 KB) OKAY [ 8.380s]
Writing 'system_a' (bootloader) Invalid partition name system_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system_a system.img_sparsechunk.2
(bootloader) is-logical:system_a: not found
Sending 'system_a' (262141 KB) OKAY [ 8.528s]
Writing 'system_a' (bootloader) Invalid partition name system_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system_a system.img_sparsechunk.3
(bootloader) is-logical:system_a: not found
Sending 'system_a' (243601 KB) OKAY [ 7.722s]
Writing 'system_a' (bootloader) Invalid partition name system_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system_a system.img_sparsechunk.4
(bootloader) is-logical:system_a: not found
Sending 'system_a' (258140 KB)
Please any help would be greatly appreciated!!!!
mattmsr82 said:
I have a g7 amz variety river. i had the bootloader unlocked and the system rooted with twrp and Magisk. and then somehow all of my partitions vanished. it stays in fastboot mode when its on and i get the following results when I attempt to flash it...
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.172s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (7419 KB) OKAY [ 0.430s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash modem_a NON-HLOS.bin
(bootloader) is-logical:modem_a: not found
Sending 'modem_a' (65900 KB) OKAY [ 2.279s]
Writing 'modem_a' (bootloader) Invalid partition name modem_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash fsg_a fsg.mbn
(bootloader) is-logical:fsg_a: not found
Sending 'fsg_a' (11612 KB) OKAY [ 0.564s]
Writing 'fsg_a' (bootloader) Invalid partition name fsg_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst1
Erasing 'modemst1' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst2
Erasing 'modemst2' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash dsp_a adspso.bin
(bootloader) is-logical:dsp_a: not found
Sending 'dsp_a' (16384 KB) OKAY [ 0.718s]
Writing 'dsp_a' (bootloader) Invalid partition name dsp_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash logo_a logo.bin
(bootloader) is-logical:logo_a: not found
Sending 'logo_a' (2115 KB) OKAY [ 0.251s]
Writing 'logo_a' (bootloader) Invalid partition name logo_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot_a boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 1.307s]
Writing 'boot_a' (bootloader) Invalid partition name boot_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash dtbo_a dtbo.img
(bootloader) is-logical:dtbo_a: not found
Sending 'dtbo_a' (564 KB) OKAY [ 0.188s]
Writing 'dtbo_a' (bootloader) Invalid partition name dtbo_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system_a system.img_sparsechunk.0
(bootloader) is-logical:system_a: not found
Sending 'system_a' (261765 KB) OKAY [ 8.479s]
Writing 'system_a' (bootloader) Invalid partition name system_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system_a system.img_sparsechunk.1
(bootloader) is-logical:system_a: not found
Sending 'system_a' (257944 KB) OKAY [ 8.380s]
Writing 'system_a' (bootloader) Invalid partition name system_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system_a system.img_sparsechunk.2
(bootloader) is-logical:system_a: not found
Sending 'system_a' (262141 KB) OKAY [ 8.528s]
Writing 'system_a' (bootloader) Invalid partition name system_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system_a system.img_sparsechunk.3
(bootloader) is-logical:system_a: not found
Sending 'system_a' (243601 KB) OKAY [ 7.722s]
Writing 'system_a' (bootloader) Invalid partition name system_a
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system_a system.img_sparsechunk.4
(bootloader) is-logical:system_a: not found
Sending 'system_a' (258140 KB)
Please any help would be greatly appreciated!!!!
Click to expand...
Click to collapse
Well you're not really telling the whole story here. you were just using your phone and randomly it decided to reboot into bootloader mode and all of your partitions randomly deleted themselves? This was obviously caused by something. What did you try to flash?
Phalanx7621 said:
Well you're not really telling the whole story here. you were just using your phone and randomly it decided to reboot into bootloader mode and all of your partitions randomly deleted themselves? This was obviously caused by something. What did you try to flash?
Click to expand...
Click to collapse
I was rebooting after installing lineage os successfully, at least at first
Sent from my Samsung SM-G973U1 using XDA Labs
mattmsr82 said:
I was rebooting after installing lineage os successfully, at least at first
Sent from my Samsung SM-G973U1 using XDA Labs
Click to expand...
Click to collapse
Says your bootloader is locked. You can't have LineageOS and a locked bootloader. It also can't spontaneously just lock itself.
Download the amazon firmware here and flash with fastboot.
Make sure you flash 29.114-134-4 or you will brick your device. If you have flash errors with a locked bootloader it's usually because the firmware used is older or because fastboot is older. I think the recent fastboot is v29 downloaded here.
Flashing commands:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
If it still says invalid partition names then I believe they were erased at some point.
ptn107 said:
Says your bootloader is locked. You can't have LineageOS and a locked bootloader. It also can't spontaneously just lock itself.
Download the amazon firmware here and flash with fastboot.
Make sure you flash 29.114-134-4 or you will brick your device. If you have flash errors with a locked bootloader it's usually because the firmware used is older or because fastboot is older. I think the recent fastboot is v29 downloaded here.
Flashing commands:
If it still says invalid partition names then I believe they were erased at some point.
Click to expand...
Click to collapse
Thanks! I'll try it later on today
Sent from my Samsung SM-G973U1 using XDA Labs
ptn107 said:
Says your bootloader is locked. You can't have LineageOS and a locked bootloader. It also can't spontaneously just lock itself.
Download the amazon firmware here and flash with fastboot.
Make sure you flash 29.114-134-4 or you will brick your device. If you have flash errors with a locked bootloader it's usually because the firmware used is older or because fastboot is older. I think the recent fastboot is v29 downloaded here.
Flashing commands:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
If it still says invalid partition names then I believe they were erased at some point.
Click to expand...
Click to collapse
I tried it a few times got the same errors as before. my bootloader was unlocked before it bricked. when i saw the oem lock I tried the fastboot bootloader unlock command again and it said the oem lock feature was dissabled. so...
mattmsr82 said:
I tried it a few times got the same errors as before. my bootloader was unlocked before it bricked. when i saw the oem lock I tried the fastboot bootloader unlock command again and it said the oem lock feature was dissabled. so...
Click to expand...
Click to collapse
You need a blankflash
ptn107 said:
You need a blankflash
Click to expand...
Click to collapse
I can never get the blankflash to work. Just says waiting for device
Sent from my Samsung SM-G973U1 using XDA Labs
I would like to ask a question and also give some discovery as well. I payed imeigurus to unlock my moto g7 power from metro. the bootloader was locked and they remotely connected in motorola factory mode to do the unlock. The only item they had me check was usb debuging and they did there thing. After this I checked and usb debugging was turned off. I went in to bootloader and flashed the retail rom for xt1955-5 retus. Then when I boot up and check software channel it says retla1st. It all works but what the hell. Thought I'd let people know so they could flash there devices to retail and this could also be put in to an appropriate thrread. But, retla1st why???? Anybody want to take a guess at that one. Also back to the topic at hand, blankflash is available and that might get you back up and running if you can get to edl mode. fastboot oem config bootmode I think.
gigawatt said:
I would like to ask a question and also give some discovery as well. I payed imeigurus to unlock my moto g7 power from metro. the bootloader was locked and they remotely connected in motorola factory mode to do the unlock. The only item they had me check was usb debuging and they did there thing. After this I checked and usb debugging was turned off. I went in to bootloader and flashed the retail rom for xt1955-5 retus. Then when I boot up and check software channel it says retla1st. It all works but what the hell. Thought I'd let people know so they could flash there devices to retail and this could also be put in to an appropriate thrread. But, retla1st why???? Anybody want to take a guess at that one. Also back to the topic at hand, blankflash is available and that might get you back up and running if you can get to edl mode. fastboot oem config bootmode I think.
Click to expand...
Click to collapse
Its saying that it's in AP fastboot flash mode secure ?
Sent from my Samsung SM-G973U1 using XDA Labs
When following the official guide if an error occurs when running 'fastboot flash' commands then try using a USB hub.
Also in the case of failures such as:
FAILED (remote: 'No such partition.')
Run the following commands:
fastboot getvar current-slot
current-slot: _a
Use the resulting current slot value as follows:
fastboot flash boot_a out/target/product/pioneer/boot.img
fastboot flash system_a out/target/product/pioneer/system.img
When flashing I had to flash the following:
boot.img
system.img
vendor.img
userdata.img
I have tried updating drivers from windows update but trying to flash anything does nothing I'm using mediatek drivers Other commands fail and gives this error FAILED (Write to device failed (Too many links))
C:\Users\me\Downloads\platform-tools_r31.0.3-windows\platform-tools>fastboot flashing unlock FAILED (Status read failed (Too many links)) fastboot: error: Command failed C:\Users\me\Downloads\platform-tools_r31.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img Rewriting vbmeta struct at offset: 0 Sending 'vbmeta' (11520 KB) FAILED (Write to device failed (no link)) fastboot: error: Command failed C:\Users\me\Downloads\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot magisk_patched-23000_AxlJS.img fastboot: error: boot partition is smaller than boot image
I'm trying to follow this guide to root my device with magisk https://forum.xda-developers.com/t/...0015685-series-root-and-cfw-linux-os.4195577/
Check my comments in the stackexchange post I made for more information
https://android.stackexchange.com/q...ash-anything-with-fastboot-on-onn-100015685-e
I have tried fastbootd from the recovery menu and the bootloader fastboot but none of the commands in the guide worked I could unlock flashing but nothing else
I'm trying to recover my phone which will not boot. (It's a T-Mobile version, but I've unlocked the bootloader and carrier already.)
Trying to flash some partitions using fastboot gives me this:
Code:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
But running `fastboot oem unlock_critical` or `fastboot oem unlock` just says it's unlocked:
Code:
FAILED (remote: ' Device already : unlocked!')
Where do I even go from here?
i have a motorola moto c how do i unlock the bootloader the fastboot oeam get_unlock_data command says its unknown command
Presumably that's a typo in your quote?
You should quote exactly what happened so people can help.
There are two different errors, local or remote.
Code:
C:\>fastboot stupidcmd
fastboot: usage: unknown command stupidcmd
C:\>fastboot oem stupidcmd
(bootloader) 'stupidcmd' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote: '')
fastboot: error: Command failed
Have you tried fastboot oem help?
To answer your question, I believe that Motorola in general has stopped supporting fastboot unlocking on the less expensive models.
delete
Renate said:
Presumably that's a typo in your quote?
You should quote exactly what happened so people can help.
There are two different errors, local or remote.
Code:
C:\>fastboot stupidcmd
fastboot: usage: unknown command stupidcmd
C:\>fastboot oem stupidcmd
(bootloader) 'stupidcmd' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote: '')
fastboot: error: Command failed
Have you tried fastboot oem help?
To answer your question, I believe that Motorola in general has stopped supporting fastboot unlocking on the less expensive models.
Click to expand...
Click to collapse
i did try fastboot oem help but it didnt help and its not the typo and the error is remote