Database Users

Findings after unlocking bootloader

So as far as I know, I am one of the first people to have the bootloader unlocked on the Chinese Mate 9.
I have some unfortunate findings. Mainly, you cannot flash large files over fastboot. Here's what happens:
target reported max download size of 471859200 bytes
sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.869s
We can flash small files, can flash recovery, etc. So we need someone to make TWRP in order to do anything with the unlocked BL. Since there's no source out for the Mate 9, I'm worried about that, but hopefully @raimondomartire can get it done!

Update: I've built a preliminary TWRP, but I don't understand TWRP well, and the mount points are incorrect. However, I believe we will have a working TWRP very soon.

Solid info. Thanks. Once more developers start hopping on, I'm sure we'll get to this faster especially after the fact that you managed to already get the bootloader unlock.

Ahh, progress. Almost there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Good job !!!!

Congrats
أرسلت من HUAWEI NXT-L29 بإستخدام تاباتلك

duraaraa said:
I have some unfortunate findings. Mainly, you cannot flash large files over fastboot. Here's what happens:
target reported max download size of 471859200 bytes
sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.869s
Click to expand...
Click to collapse
I don't think, that it can stop xda community
http://forum.xda-developers.com/showthread.php?t=2749797

Job well done!

5[Strogino] said:
I don't think, that it can stop xda community
http://forum.xda-developers.com/showthread.php?t=2749797
Click to expand...
Click to collapse
Thank you for the idea. Unfortunately, when I tried this tool, it required that the image size is a multiple of 4096 bytes. So I appended null bytes to the end until it was a multiple, split, and flashed all the files, but it doesn't boot.

An update. I hate TWRP mounting /system, /data, /cache, and so on. The only one that doesn't mount is 3rdmodem (I can't even find it in the filesystem.) The data partition and /sdcard partition seem to be encrypted. USB doesn't work (yet)
When I try to flash supersu, the phone crashes and reboots just after the message that it's trying to do a systemless install and creating space...
I tried flashing the zip from Huawei's google services download. That flash worked.
I can't flash any regular huawei updates without a lot of work, so I haven't made an honest effort at unpacking the update.app's partitions and making them into flashable zip files.
So we're kind of stuck unfortunately, with not very much we can do, despite the bootloader being unlocked.
That's all I've got for you all for now.

How do you do to unlock the bootloader once you got the code

playa77176 said:
How do you do to unlock the bootloader once you got the code
Click to expand...
Click to collapse
If you don't know how to do it you might be better off not doing it because there is some risk involved with it at this point.
If you want to try anyway turn off the phone and plug in a USB cable while holding volume down key.
Then run the command on your computer
fastboot oem unlock CODE
Replace code with your code.

Update. I just figured out how to flash a rom via fastboot. Going to try flashing European newest rom on Chinese mate momentarily.

Update: The error I mentioned in my previous post (sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
)
This error doesn't occur if I'm flashing the Chinese firmware. Only if I flash the European firmware.
Something is not quite right. I'm download other version of Euro firmware to check.

Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.

duraaraa said:
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
Click to expand...
Click to collapse
Maybe you need an updated fastboot files?

It's possible to unlock With srktool ?

playa77176 said:
It's possible to unlock With srktool ?
Click to expand...
Click to collapse
I think it's best you stick to the regular fastboot commands. SRKTool is for the older Mate, so it might want to flash an incompatible TWRP or something like that.

gm007 said:
Maybe you need an updated fastboot files?
Click to expand...
Click to collapse
I've tried every version of fastboot I can find, on every platform. That's not the issue. I'm going to try and find a way though!

duraaraa said:
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
Click to expand...
Click to collapse
The problem is that fastboot does not allow flash very big files.
Solution is to divide file on chunks.
Unfortunately, i don'y have Mate 9.
Try this:
Code:
fastboot -S 256M system path_to_system.img
p.s. You should use actual fastboot version (SDK version)

[guide] root le x626

First, Unlock Bootloader
Install TWRP for Le X626
Download Magisk or SuperSU
Put Magisk or SuperSU in internal storage
Reboot to TWRP
Install from zip
Choose Magisk (Recommended) or SuperSU
Reboot
source : tickernel.tk

Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.

How to install TWRP for x626 according to the site the OP recommends.
From the same website, only without the adlinks. No guarantees from me, if you go through the instructions from the OP you will end up getting the same information.
– Make sure your Bootloader is Unlocked, if you don’t know how to Unlock the Bootloader then please go to here and Unlock the Bootloader of your Device.
– Download the Latest TWRP Recovery Image from https://dbr.ee/TKKC
– Reboot into Fastboot/Bootloader Mode.
– Run The Following Command from a Command Prompt in the Same Folder in which you downloaded the TWRP Recovery Image (Change twrp le x626.img to recovery.img):
fastboot flash recovery recovery.img
fastboot boot recovery.img
Click to expand...
Click to collapse

onlytanmoy said:
Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.
Click to expand...
Click to collapse
I can't, because it's have different chipset

okay, thanks for your response and clarification...cheers to that.

Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>

tomfoley said:
Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>
Click to expand...
Click to collapse
Unlock bootloader first
What rom do u use?

Hi Tickernel, and thank you for replying
I unlocked the bootloader as per Step 1 above and that completed successfully.
Moving on to Step 2 I got the recovery image following your links which led me to 'twrp le x626.img' (20MB), which I renamed to recovery.img.
There are two commands to execute in step 2, the first went ok, the second did not succeed
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse

Please see screenshot...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse

tomfoley said:
Please see screenshot...
Click to expand...
Click to collapse
Have u tried boot to recovery?
Press vol up + power

Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??

tomfoley said:
Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??
Click to expand...
Click to collapse
After you flash the twrp, then boot into recovery by pressing vol up + power
You don't need update.zip

Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.

tomfoley said:
Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.
Click to expand...
Click to collapse
I'm not suggesting to erase all your data, i'm just suggesting after you flash the twrp but don't straight go to recovery then press vol up + power. That's it

Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'

tomfoley said:
Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'
Click to expand...
Click to collapse
Command 'fastboot boot recovery.img' is going boot to twrp. If you fail to do that, then just press vol up + power

Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !

tomfoley said:
Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !
Click to expand...
Click to collapse
Yeah, you're welcome

Don't suppose kingroot or similar works? I'm very lazy lol

I also have this problem were it fails in "fastboot boot recovery.img" but not in commanding "fastboot flash recovery recovery.img"
what to do?? :crying:
thanks for the help

P8 Lite ALE-L21 - Bootloop with INSANE problem to solve

Hello,
I have a small problem with my old phone. After ~3 months ago of the last use I decided to launch P8 Lite. Yesterday I just wanted to flash LineageOS on it. Unfortunately, everytime that I'm trying to launch this phone, it welcomes me with just a red lightning symbol and with an animation of huawei logo.
Some details about my phone:
- P8 Lite has an unlocked bootloader
- Command "fastboot oem get-bootinfo" sends "(bootloader) unlocked" message.
Okay, let's go.
At first - I've downloaded stock ROM. I've exported cust, recovery, boot, and system (.img) files with HuaweiUpdateExtractor from update.app.
Unfortunately, when I've tried to flash boot and recovery, fastboot sends unpleasant output in the console.
HTML:
$ ./fastboot flash boot BOOT.img
Sending 'boot' (22672 KB) OKAY [ 0.590s]
Writing 'boot' FAILED (remote: 'flash writeprim vrl failure')
fastboot: error: Command failed
It doesn't look good.
Corrupted flash memory isn't the option too, because when I've tried to flash modded BOOT and RECOVERY files from xda - fastboot passed me with flashing.
Trying to flash CUST and SYSTEM's .img files goes well.
Let's try the other way. Let's check if "./fastboot erase data" is working.
HTML:
$ ./fastboot erase data
Erasing 'data' FAILED (remote: 'Command notallowed')
fastboot: error: Command failed
It doesn't work too.
If the stock recovery can't be flashed to my phone, how about flashing the other recovery, like TWRP?
HTML:
$ ./fastboot flash recovery twrp/RECOVERY.img
Sending 'recovery' (36166 KB) OKAY [ 0.940s]
Writing 'recovery' OKAY [ 0.634s]
Finished. Total time: 1.622s
Well, It works! But, I think that P8 Lite doesn't want to work with me aswell.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The errors shown on the bottom side of the screen can be different - depending on the img file that I've flashed as recovery.
Well, so let's try to boot TWRP manually using "fastboot boot" command
HTML:
$ ./fastboot boot twrp/RECOVERY.img
Sending 'boot.img' (36166 KB) OKAY [ 0.941s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Maybe let's try to check if I have unlocked bootloader for sure.
Let's try to relock my bootloader... nah
HTML:
$ ./fastboot oem lock
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
===
$ ./fastboot oem relock
FAILED (remote: 'data parse fail')
fastboot: error: Command failed
So... self-factory reset from sdcard is the only way?
Unluckily, this option isn't available too. I've removed all files from my SD Card, I've created "dload" folder and I've put update.app file in it.
Interestingly, when I'm holding VOL+, VOL- and POWER button at once during the launch - phone moves to the Huawei's eRecovery screen.
As long as "clear cache" option is possible to do, "wipe data & factory reset" option is undoable. Trying that option shows red, exclamation mark and "Operation was unsuccesful" label on the screen.
Moreover, huawei corrupted my SD Card. How? I don't know, but on every phone that I'm trying to mount this SD Card - they doesn't detect it
At this moment I don't have any ideas. I'm determined to repair this P8 Lite, but the question is - what should I do? I need help for 3 questions:
1. What steps should I do to unbrick my phone?
2. Is there any way to pass over "Command not allowed" message in he fastboot, so I could do anything?
3. How can I turn back my SD Card to work?
Here is the list of commands that returns "Command not allowed" message to me:
HTML:
./fastboot boot
./fastboot oem - in some cases
./fastboot erase
./fastboot flashing unlock
Thanks for every help!

UP

Try to uncompress a update.app folder and flash erecovery, there is a tool to transfer update.app onto .IMG on xda

yzena said:
Try to uncompress a update.app folder and flash erecovery, there is a tool to transfer update.app onto .IMG on xda
Click to expand...
Click to collapse
I did that arleady. I've exported 4 files (which I've mentioned above) with HuaweiUpdateExtractor. Trying to flash CUST and SYSTEM images passes, but when I'm trying to flash BOOT and RECOVERY - Fastboot is stopping me with an output that I mentioned above aswell ("flash writeprim vrl failure" problem).

Bump

Refresh

Still looking for answers!

Refresh!

Refresh

Refresh!

(SOLVED) (HardBrick) only fastboot and erecovery Huawei P Smart

Hi, I have a Huawei P Smart FIG-LX1 C33 with unlocked bootloader and frp unlocked
Reason why it was hard bricked its because i use this emui 9 (https://forum.xda-developers.com/hu...nt/service-firmware-emui-9-1-pe-c432-t3936692) (works) but i downgraded do my c33 emui8 official in dload
and now its bricked :crying:
In adb can flash system,cust and recovery but cannot flash kernal.
kernal: C:\platform-tools>fastboot flash kernal C:\Users\João\Desktop\KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernal' (24576 KB)...
OKAY [ 0.642s]
writing 'kernal'...
FAILED (remote: Command not allowed)
finished. total time: 0.655s
If anyone can help me i apreciate

Hi, if you need to flash kernel you need to use this command: fastboot flash boot C:\Users\João\Desktop\KERNEL.img

0ckysaurus said:
Hi, if you need to flash kernel you need to use this command: fastboot flash boot C:\Users\João\Desktop\KERNEL.img
Click to expand...
Click to collapse
Hi thank you for rresponding
But cannot flash anyway
C:\platform-tools>fastboot flash boot C:\Users\João\Desktop\KERNEL.img
target reported max download size of 471859200 bytes
sending 'boot' (24576 KB)...
OKAY [ 0.643s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.670s

Where did you find that kernel.img file ?
joaomoreira1001 said:
Hi thank you for rresponding
But cannot flash anyway
C:\platform-tools>fastboot flash boot C:\Users\João\Desktop\KERNEL.img
target reported max download size of 471859200 bytes
sending 'boot' (24576 KB)...
OKAY [ 0.643s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.670s
Click to expand...
Click to collapse

0ckysaurus said:
Where did you find that kernel.img file ?
Click to expand...
Click to collapse
in update.app

Try to extract boot.img from update.app

0ckysaurus said:
Try to extract boot.img from update.app
Click to expand...
Click to collapse
Does not have boot.img https://imgur.com/a/EPEohBf

Weird sorry I'm unable to help you with this problem.

0ckysaurus said:
Weird sorry I'm unable to help you with this problem.
Click to expand...
Click to collapse
ok no problem thank you anyway

Please try fastboot flash kernel C:\Users\João\Desktop\KERNEL.img

0ckysaurus said:
Please try fastboot flash kernel C:\Users\João\Desktop\KERNEL.img
Click to expand...
Click to collapse
WTF now can flash AHAH C:\platform-tools>fastboot flash kernel C:\Users\João\Desktop\KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.638s]
writing 'kernel'...
OKAY [ 0.539s]
finished. total time: 1.180s
but it is in bootloop

try to flash emui 9 and then use this guide: https://forum.xda-developers.com/ho...de-downgrade-stable-emui-9-0-to-emui-t3921557

I flashed the emui 9 rom again
Thank you for telling me to do something I had already done
thanks m8

You need to download this firmware FIG-LX1C33B140. Because its rollback firmware to android 8.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

0ckysaurus said:
You need to download this firmware FIG-LX1C33B140. Because its rollback firmware to android 8.0
Click to expand...
Click to collapse
flash in dload?

download firmware finder from play store and try the e-recovery method
joaomoreira1001 said:
flash in dload?
Click to expand...
Click to collapse

0ckysaurus said:
You need to download this firmware FIG-LX1C33B140. Because its rollback firmware to android 8.0
Click to expand...
Click to collapse
in build name says unknown

0ckysaurus said:
download firmware finder from play store and try the e-recovery method
Click to expand...
Click to collapse
in erecovery says "Starting wifi failed"

joaomoreira1001 said:
Hi, I have a Huawei P Smart FIG-LX1 C33 with unlocked bootloader and frp unlocked
Reason why it was hard bricked its because i use this emui 9 (https://forum.xda-developers.com/hu...nt/service-firmware-emui-9-1-pe-c432-t3936692) (works) but i downgraded do my c33 emui8 official in dload
and now its bricked :crying:
In adb can flash system,cust and recovery but cannot flash kernal.
kernal: C:\platform-tools>fastboot flash kernal C:\Users\João\Desktop\KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernal' (24576 KB)...
OKAY [ 0.642s]
writing 'kernal'...
FAILED (remote: Command not allowed)
finished. total time: 0.655s
If anyone can help me i apreciate
Click to expand...
Click to collapse
After flashing in DLOAD
Boot into erecovery and wipe data/factory reset

Livi-Tech said:
After flashing in DLOAD
Boot into erecovery and wipe data/factory reset
Click to expand...
Click to collapse
Thanks

How to unlock a Moto G7 xt1962-6

I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?

rsshilli said:
I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/

Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rsshilli said:
Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
Click to expand...
Click to collapse
It seems that your USB debugging or OEM unlock toggle was un-ticked.
Do you have recovery available to format/reset device?
RSDLite doesn't work with your model?

Negative
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .

rsshilli said:
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .
Click to expand...
Click to collapse
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!

Well, that's weird
Huh. I tried LMSA tonight again just for fun and it worked fine this time. It found the image, downloaded it, and reflashed the phone to factory settings. Yay! I'm back in. I tried it many times before. I know my firmware updated on the phone a few days before this happened. I guess I just needed to wait for a bit. Thank you everybody.
Ryan

WoKoschekk said:
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!
Click to expand...
Click to collapse
For next time, how does one find the exact firmware needed? I could never figure that out.

rsshilli said:
For next time, how does one find the exact firmware needed? I could never figure that out.
Click to expand...
Click to collapse
Code:
fastboot getvar all