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!
Related
I seem to be unable to flash any recovery images using
Code:
fastboot flash recovery IMG
. When I put the tablet into fastboot mode, attach it to the computer using a microusb adapter and run the command, I get the following error:
Code:
sending 'recovery' (9158 KB)...
FAILED (data transfer failure (Protocol error))
finished. total time: 0.057s
If I repeat the command, any number of times, I get another error:
Code:
sending 'RECOVERY' (9158 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
I've tried this with TWRP MultiROM and ClockworkMod Recovery. Why do I get this error? How can I troubleshoot/solve this in order to flash recovery images?
Device: (original) Google Nexus 7 16GB WIFI
Android Version: 4.3 (stock)
Kernel Version: 3.1.10-g1e8b3d8
PC Software: Ubuntu 13.04 with android-tools-fastboot 4.2.2+git20130218-3ubuntu3~raring
The full steps I took to unlock bootloader and attempt flashing the recovery (from a factory reset):
Put the device into developer mode by tapping the 'Build number' in 'Settings->About tablet' several times.
Enabled USB debugging in 'Settings->Developer options'.
Connected the USB cable to a laptop running Ubuntu 13.04 with android-tools-adb and android-tools-fastboot installed.
Ran
Code:
adb devices
which showed the device
Code:
adb reboot bootloader
>> rebooted into the fastboot bootloader
Code:
sudo fastboot devices
>> showed the device
Code:
sudo fastboot oem unlock
>> bootloader successfully unlocked
Code:
sudo fastboot continue
>> booted the device
Repeated the steps to enable developer mode and USB debugging
Downloaded kernel_kexec_430.zip, multirom_v12_n7-signed.zip, TWRP_multirom_n7_20130727.img to the current folder (and verified the md5sums)
Copied TWRP_multirom_n7_20130727.img to recovery.img
Copied kernel_kexec_430.zip, multirom_v12_n7-signed.zip, recovery.img to Nexus 7/Internal Storage root directory using nautilus
Ran
Code:
adb reboot bootloader
which put the device into fastboot mode
Ran
Code:
sudo fastboot flash recovery recovery.img
, which failed
Code:
flashboot flash bootloader [URL="http://d-h.st/QFd"]bootloader-grouper-4.23.img[/URL]
Running:
Code:
flashboot flash bootloader bootloader-grouper-4.23.img
has the same problem:
Code:
sending 'bootloader' (2100 KB)...
FAILED (data transfer failure (Protocol error))
finished. total time: 81.438s
lazyteq said:
Running:
Code:
flashboot flash bootloader bootloader-grouper-4.23.img
has the same problem:
Code:
sending 'bootloader' (2100 KB)...
FAILED (data transfer failure (Protocol error))
finished. total time: 81.438s
Click to expand...
Click to collapse
change usb cable and try different ports...
It seems this is a problem with the usb cable and usb ports. Fastboot seems very flaky and intemittently works on different USB ports.
Now for a story about how I softbricked and eventually unbricked the tablet.
By changing around USB ports on my laptop, I eventually managed to flash TWRP recovery. In the process of messing around, I managed to delete the os from the tablet, so I tried to reinstall the stock os.
I ran the flash-all script and it started to install. Unfortunately, fastboot decided to fail once it had erased the partitions and was starting to re-flash them. So I was left with a tablet with no os, no recovery and only a bootloader that wouldn't communicate properly with fastboot on my laptop!
I decided to try a different computer. The only one I had available was a very old Windows XP desktop with 256MB RAM and USB 1.0 ports (!). I managed to download the Android SDK on this incredibly slow machine and also installed device drivers using the Nexus 7 toolkit. I couldn't get fastboot to work for ages but eventually, after plugging the tablet out and in and repeating the
Code:
fastboot devices
command, I managed to get the device to show up.
I then managed to reflash TWRP onto the recovery partition. Fastboot was still very dodgy but seemed a bit more reliable at sending the data across than it had been on my laptop. Once I had flashed TWRP, I put the latest Cyanogenmod ROM onto a usb stick, connected it via OTG and managed to install it.
So now I have a working tablet with TWRP and Cyanogenmod and I finally have proper root permissions including the ability to use usb-otg which was one of the main reasons for rooting in the first place. I'm going to give MultiROM a miss because I really don't trust fastboot / my usb cable / my usb ports to properly flash images.
Username invalid said:
Code:
flashboot flash bootloader [URL="http://d-h.st/QFd"]bootloader-grouper-4.23.img[/URL]
Click to expand...
Click to collapse
I there, I am not at all a novice to Android but I have only owned two Nexus devices. The other two devices that I have had and modded were the Vzw Galaxy s4 and s3. I've been modding for quite a while now and am quite familiar with Android software modifying and using adb. That being said quick semi topic related question: How do I know what Bootloader my Nexus 7 has already? I just sent it in to repair at Asus and got it back compeletely wiped running stock (sent it in unlocked running Rootbox). I have previously flashed to the most recent bootloader, but I'm not sure if it still has it. I don't know what all they did to it.
Is there a way to find out exactly what bootloader it is running? Maybe there is an adb shell command I can run to find out or something?
I have searched but I couldn't find a definitive answer. And I didn't want to start a whole new thread just to ask this simple question.
Thanks for your time.
nicholi2789 said:
I there, I am not at all a novice to Android but I have only owned two Nexus devices. The other two devices that I have had and modded were the Vzw Galaxy s4 and s3. I've been modding for quite a while now and am quite familiar with Android software modifying and using adb. That being said quick semi topic related question: How do I know what Bootloader my Nexus 7 has already? I just sent it in to repair at Asus and got it back compeletely wiped running stock (sent it in unlocked running Rootbox). I have previously flashed to the most recent bootloader, but I'm not sure if it still has it. I don't know what all they did to it.
Is there a way to find out exactly what bootloader it is running? Maybe there is an adb shell command I can run to find out or something?
I have searched but I couldn't find a definitive answer. And I didn't want to start a whole new thread just to ask this simple question.
Thanks for your time.
Click to expand...
Click to collapse
{
"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"
}
Or you can use
Code:
fastboot getvar all
Version 4.23 is the latest released with Android 4.3.
Username invalid said:
Or you can use [Code ]fastboot getvar all[/CODE]
Version 4.23 is the latest released with Android 4.3.
Click to expand...
Click to collapse
Haha wow. Now I really feel like a noob. I guess I probably should have noticed that.
Thanks
I had the same problem and then realized I was using 3.0 usb port.
Plugged cable into 2.0 port and it suddendly worked.
I have the same error:
Code:
FAILED (command write failed (Protocol error))
In my case my phone was connected through USB HUB so i connected it to PC and everything starts working.
Did not work
sending 'recovery' (12396 KB)...
OKAY [ 0.409s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.458s
I see this also when my USB cable was too long.
I also just used a shorter cable and it worked
Hi folks,
I just received my Essential Phone, purchased through amazon. As you recall, the Essential Phone was rumored to have an unlocked bootloader. This was confirmed by @essential confirming that it will, in a tweet.
However, this is not what I'm experiencing with the phone.
After powering it up and playing around a bit, I enabled USB debugging and linked it to my computer, where I have the latest (as of today) android platform tools installed. I rebooted to fastboot and tried to issue "fastboot oem unlock", as I did with my previous phone, a nexus 6p. However, it seems "oem" is no longer a valid subcommand of fastboot; it has been renamed to "flashing unlock", along with some other new-to-me commands:
Code:
$ fastboot --help
usage: fastboot [ <option> ] <command>
commands:
.....
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
The "flashing unlock" command looks interesting. Let's try that:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.003s
Hmmm... I don't like the look of that. Well, let's see what "get_unlock_ability" says:
Code:
$ fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.000s]
finished. total time: 0.000s
Ok, that looks bad too. Let's try those other new commands and see if we can get anywhere...
Code:
$ fastboot flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.002s
Nope.
Code:
$ fastboot flashing get_unlock_bootloader_nonce
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Double nope.
Well that's not encouraging. I don't claim to be any sort of expert in regards to unlocking phones, but I can't find any other methods using these tools, and Essential's docs aren't any help. I've contact their phone support but haven't heard back after about an hour. (They use some ridiculous system where you schedule a callback... Not happy.)
So, I'm feeling pretty upset. Let's be clear here:
Essential said this:
{
"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"
}
But shipped a product with this:
Code:
$ fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.000s]
finished. total time: 0.000s
Did you turn on the allow unlocking toggle in developer options?
tw1tch175 said:
Did you turn on the allow unlocking toggle in developer options?
Click to expand...
Click to collapse
Thanks, that did the trick
xMopx said:
Thanks, that did the trick
Click to expand...
Click to collapse
So ...wich are the right steps and command d to unlock the bootloader?
thx
mastercut said:
So ...wich are the right steps and command d to unlock the bootloader?
thx
Click to expand...
Click to collapse
1) Check the box next to OEM Unlockable.
2) Then reboot your phone to fastboot
3) In a command prompt within the adb folder: type -> fastboot flashing unlock
4) Use the volume button to click yes when prompted.
Cheers
frhoward said:
1) Check the box next to OEM Unlockable.
2) Then reboot your phone to fastboot
3) In a command prompt within the adb folder: type -> fastboot flashing unlock
4) Use the volume button to click yes when prompted.
Cheers
Click to expand...
Click to collapse
I've tried all of these steps and once I get to the fastboot flashing unlock step my cmd prompt just hangs at waiting for device and I never get the option for "Yes." Instead I have Start, Recovery, Power off, etc.
What am I doing wrong?
DenverDroid said:
I've tried all of these steps and once I get to the fastboot flashing unlock step my cmd prompt just hangs at waiting for device and I never get the option for "Yes." Instead I have Start, Recovery, Power off, etc.
What am I doing wrong?
Click to expand...
Click to collapse
First in fastboot type "fastboot devices" if a string of numbers answers it is ok otherwise you need fastboot driver ....have you cheked?
Hi guys, I have an issue with unlocking the bootloader. fastboot devices returns the device ID, but flashing unlock gives me failed, unknown command error. I cannot get it working. Any ideas?
/edit: changing PC's helped
Essential Phone stuck in Start up screen with Locked Bootloader
My Essential Phone is frozen at boot up screen while trying to Update the latest Android P Beta 3 ... I restarted the phone on promoting to do so after downloading the update and now I'm here stuck with boot up screen.
Boot loader: Locked
Please let me know if there is a way around this to get it back up !!
Pleaseeeee....
Thanks in advance!!
[email protected] said:
My Essential Phone is frozen at boot up screen while trying to Update the latest Android P Beta 3 ... I restarted the phone on promoting to do so after downloading the update and now I'm here stuck with boot up screen.
Boot loader: Locked
Please let me know if there is a way around this to get it back up !!
Pleaseeeee....
Thanks in advance!!
Click to expand...
Click to collapse
If you've already waited for some time to pass, i would let it go dead, then plugin and allow it to power up on its own. I've only had limited success with this though. Other options are goto into recovery mode and factory reset.
wrecklesswun said:
If you've already waited for some time to pass, i would let it go dead, then plugin and allow it to power up on its own. I've only had limited success with this though. Other options are goto into recovery mode and factory reset.
Click to expand...
Click to collapse
Yeah, I had such instances too in the past. But no luck this time...
My OEM locking is not switched on and I'm unable to sideload the OTA or Rest the phone to factory.
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
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
1. Download F10 abl.img
2. Reboot to fastboot and flash F10 abl
adb reboot fastboot
fastboot flash abl abl.img
3.. Reboot fastboot reboot and you can use dual SIM.
Worked like a charm!
I am running OOS13 KB2003 converted from T-Mobile
I got:
FAILED (remote: 'Flashing is not allowed for Critical Partitions.')
running
Code:
fastboot flash abl abl.img
I tried to run
Code:
fastboot flashing unlock_critical
But got :
FAILED (remote: ' Device already : unlocked!')
Is there a work around?
Thanks in advance!
Stylishly said:
I am running OOS13 KB2003 converted from T-Mobile
I got:
FAILED (remote: 'Flashing is not allowed for Critical Partitions.')
running
Code:
fastboot flash abl abl.img
I tried to run
Code:
fastboot flashing unlock_critical
But got :
FAILED (remote: ' Device already : unlocked!')
Is there a work around?
Thanks in advance!
Click to expand...
Click to collapse
As far as i remember, you need to be in fastbootd to flash critical partitions.
{
"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"
}
Code:
fastboot reboot fastboot
fastboot flash abl abl.img
Does this require bootloader unlock? Would someone be able to provide more step by step confirmation on this? Also what does the updated abl.img do in order to enable dual-sim?
raven911 said:
Also what does the updated abl.img do in order to enable dual-sim?
Click to expand...
Click to collapse
It's taken from OOS13 F.10 beta release, where sim-lock is not present.
C:\adb>fastboot flash abl abl.img
target reported max download size of 268435456 bytes
sending 'abl' (220 KB)...
OKAY [ 0.009s]
writing 'abl'...
FAILED (remote: No such file or directory)
finished. total time: 0.014s
try on op 8t t mobile original firmware kb2007_11_F46 not working on it
Can you flash this in custom recovery like Orange Fox?
amine tenes said:
C:\adb>fastboot flash abl abl.img
target reported max download size of 268435456 bytes
sending 'abl' (220 KB)...
OKAY [ 0.009s]
writing 'abl'...
FAILED (remote: No such file or directory)
finished. total time: 0.014s
try on op 8t t mobile original firmware kb2007_11_F46 not working on it
Click to expand...
Click to collapse
You forgot to reboot to fastbootd.
Code:
fastboot reboot fastboot
kevinco1 said:
Can you flash this in custom recovery like Orange Fox?
Click to expand...
Click to collapse
As far as i remember in recovery you can flash .img to boot or recovery partition directly.
So you'll have to pack in update.zip where in script it will be specified which partition should abl.img be flashed to.
Excellent! Thanks Jookean !
Now my (originally) TMo 8T has been converted to a dual SIM KB2003 that works better (in the US) than my old (dual IMEI) KB2003 that I hard bricked (in FastbootD) trying to get an A12 OTA working right.
I rarely got 5G indicated on my Euro original, but now mostly 4G and low-ish signal strength issues are history! No longer being tied to T-Mobile's software updates and being able to have 5G options on my device from Verizon and Tmobile was my goal.
My eBay bargain Pixel 6 Pro will have to wait a while longer. I prefer flat screens and lighter devices. Guessing Oneplus anticipated fumbling of Android 14 may entice me to switch. Wish it had two physical SIM slots.