Related
hi, here goes my problem:
i had flashed stock oreo firmware (posted here on xda) together with a magisk-patched bootloader, all done via fastboot. my bootloader is unlocked, the device drivers on my win10 pc were working back then and i was able to boot the bootable twrp img.
i also had used one magisk module, namely app systemizer. but after updating it and rebooting, something went wrong (probably fault of magisk or the module), and i can't boot into system, it always gets stuck o the M logo.
i've still got fastboot, my pc correctly detects the phone is in fastboot and connected, and the phone sees the connection too. i am able to send commands like reboot, but whenever i try to tell it to boot a boot.img from my pc (stock img, magisk patched img, or twrp img), it always either gets stuck on loading the file, or straight up says that it failed - (remote: unknown command). the same happens with commands like erase and flash.
can anyone help me get it working again?
thanks
Hey.... I experienced the same thing yesterday.
Have you got it fixed cause this thread is 10 days now.
The solution was to go to the recovery and factory reset and the phone will work. Weirdly, it still had root and magisk app worked without a hitch. I restored all the apps and started working from today morning.
None of the commands were working in Fastboot mode, cant send files or execute something. Someone here has to explain this or we have to revert it back to stock image (which will kaput the root of course) and then try the flashing and see if it will work out.
After busting my head for 6 plus hours i am back again with the phone with root. I installed 4 modules and used the latest Magisk.
Tommylee567 said:
Hey.... I experienced the same thing yesterday.
Have you got it fixed cause this thread is 10 days now.
The solution was to go to the recovery and factory reset and the phone will work. Weirdly, it still had root and magisk app worked without a hitch. I restored all the apps and started working from today morning.
None of the commands were working in Fastboot mode, cant send files or execute something. Someone here has to explain this or we have to revert it back to stock image (which will kaput the root of course) and then try the flashing and see if it will work out.
After busting my head for 6 plus hours i am back again with the phone with root. I installed 4 modules and used the latest Magisk.
Click to expand...
Click to collapse
i got it fixed the same way.. my issue was caused by a bug in the shell app systemizer module, i reported it to the dev.... still really strange that it'd render fastboot unusable
No Solution
I still didn't find a solution to the fastboot problem in Windows. but using Linux system (present i have Manjaro linux installed) had solved it as i entered the commands step by step and flashed it.
And still I am having partial letters missing in reply I get from fastboot commands.
Ex: fastboot boot boot.img i will get something like suffix-slo:not found..... etc with missing letters on the screen.
So using the fastboot flashing script for Moto phones i flashed a stock firmware and started fresh with a good ol' stock boot.img file and still the fastboot commands work here and there. After few times of rebooting it works well. Then goes back to the same problem.
I don't know what is the matter with it but I learned my lesson of backup and never am gonna miss that step out (at least I had Titanium Backup done before the first shot).
BTW, i found what was the problem in Magisk module. It froze up in the Magic Charging Switch module. So re-flashed everything and back to normal.
Rooted and Magisk running well again.
I hope there won't be any flashing necessary soon for me :laugh:
I have what seems the same problem: "fastboot boot twrp.img" fails, either hanging on downloading, or simply failing with "remote: unknown command". I am also rooted with Magisk, no modules.
The kink is that on a different PC, it works fine. As far as I can tell, same software setup: Minimal ADB and Fastboot 1.4.3 + drivers installed by Motorola Device Manager 2.5.4 on both (Win10) PCs. So I'm not inclined to factory reset.
Frustrating.
edhaswell said:
I have what seems the same problem: "fastboot boot twrp.img" fails, either hanging on downloading, or simply failing with "remote: unknown command". I am also rooted with Magisk, no modules.
The kink is that on a different PC, it works fine. As far as I can tell, same software setup: Minimal ADB and Fastboot 1.4.3 + drivers installed by Motorola Device Manager 2.5.4 on both (Win10) PCs. So I'm not inclined to factory reset.
Frustrating.
Click to expand...
Click to collapse
Do you guys now if the error occur on a AMD "Ryzen" CPU?
I have both Amd and Intel desktops and on the intel works just fine on ever try, on the amd cpu I have no sucess till now.
btotta said:
Do you guys now if the error occur on a AMD "Ryzen" CPU?
I have both Amd and Intel desktops and on the intel works just fine on ever try, on the amd cpu I have no sucess till now.
Click to expand...
Click to collapse
In my case the non-working machine is a new Ryzen build, while the one that works is an older Intel. Shouldn't matter, but hmm...
edhaswell said:
In my case the non-working machine is a new Ryzen build, while the one that works is an older Intel. Shouldn't matter, but hmm...
Click to expand...
Click to collapse
Yeah, I think the same, but the problem it's with the USB drivers on the Windows 10 for ryzen. If you run windows 7 with the USB drivers from AMD will work normally.
I have done some research about it and find some guys that manage to install the drivers from windows 7 on windows 10, but for me just broke everything and I have to format the PC.
Tommylee567 said:
I still didn't find a solution to the fastboot problem in Windows. but using Linux system (present i have Manjaro linux installed) had solved it as i entered the commands step by step and flashed it.
And still I am having partial letters missing in reply I get from fastboot commands.
Ex: fastboot boot boot.img i will get something like suffix-slo:not found..... etc with missing letters on the screen.
Click to expand...
Click to collapse
I have similar issue with the same error message.
But in my case, the issue shows up on Ubuntu Linux. It works fine on another PC with Windows 7. Both are using fastboot r28.
The issue still persists even after re-stock, I still need to use Windows 7 (for any fastboot operation). Both PCs are Intel.
I also had a lot of errors with fastboot, which used to work perfectly some time ago. I too was frustrated and was searching for it. Just as a test case, I decided to use an older version of platform tools and voila all fastboot commands ran smoothly without a single error. I was getting all kinds of errors with platform-tools_r28.0.1-windows (downloaded directly from https://developer.android.com/studio/releases/platform-tools.html). I used older version 27.0.1 and everything working perfectly. I use win 7 x64 (intel). Maybe this will help some of you, or maybe I was just lucky and fastboot version is not the issue but something else, but as long as older version is working for me, I will be using it.
Cheers.
anonyo said:
I used older version 27.0.1 and everything working perfectly. I use win 7 x64 (intel).
Cheers.
Click to expand...
Click to collapse
linux r27.0.1 doesn't work for me. I don't think any version would work for my linux pc.
Was the final fix for this to just factory reset? I'm tempted to try booting to the recovery image on my home machine first but didn't want to mess with it if there's no point.
Update: since recovery was still accessible (Lineage OS recovery), I was able to ADB sideload TWRP, which then allowed me to push a new OS.
I have had this same problem since I got the phone. Fastboot works on my ryzen desktop, doesnt work on intel laptop. both are running latest linux mint
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is going wrong here!
Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
ptn107 said:
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
Click to expand...
Click to collapse
Thanks for your reply, the file sizes are correct, I tried these from twrp download page: twrp-3.2.3-1-payton.img (29.5M) and twrp-3.2.3-0-payton.img (25.9M) - same result.
Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
gee one said:
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
Click to expand...
Click to collapse
Will give this a try tomorrow, thanks a lot!
Edit: Still no luck. Tried it with linux mint and even there the same sh!t... wtf
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Neffy27 said:
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Click to expand...
Click to collapse
Latest drivers from Motorola Device Manager are installed and phone is properly recognized in device manager (used usb 2.0, 3.0 and 3.1 ports, nothing changes, same behavior). I tried it now with mfastboot but still nope..
Are you using minimal or full sdk (by Google) platform tools?
Neffy27 said:
Are you using minimal or full sdk (by Google) platform tools?
Click to expand...
Click to collapse
Minimal, I have also a Moto G5 and I don't face this kind of problems - only with Payton.
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Neffy27 said:
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Click to expand...
Click to collapse
Unfortunately still no progress with full sdk and latest platform-tools, I'm giving up (for now).. I don't get it man, I'm not able to do anything in bootloader... for example when I try "fastboot flash partition gpt.bin" it freezes at sending OR it throws instant failed, the bootloader log menu shows that something is downloading but nothing happens... I relocked the bootloader (locking and unlocking is no problem) again and I am going to use it for a while... otherwise I will do a mistake somewhere and will brick it... Thanks for taking the time to help me haha
I'm having this same exact issue, just got this phone (XT1900-1) for my wife and she wants a custom rom, my own phone booted into twrp no problem.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Maybe try the fastboot in that link. I read through the thread and no specific reason why they suggest that version but it allowed people to flash back to stock. I used it last week to go back to stock before Lineage.
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Sorry, beyond my expertise. Maybe it's USB c port on the phone issue? Intermittently dropping the connection? Or have to tried flashing the 8.1 sick from the thread I posted? Maybe the factory ROM is messed up some how. I honestly don't know and those suggestions aren't based in any real knowledge.
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Slayer5934 said:
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Click to expand...
Click to collapse
Had exactly the same behavior like you (especially Edit 3), I tried it on a different computer from 2013 with usb 2.0 ports and it worked..
No other cable, no usb port, no adb and fastboot changes and no other drivers - just put all the stuff on a other computer and run the commands from there :good:
ptn107 said:
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Click to expand...
Click to collapse
Yeah, I'm on 1:7.0.0+r33-2 too.. I guess it has something to do with my mainboard or usb controller, weird weird weird
A different pc solved the issue.. wtf.. thank you..
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
dirktacular said:
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
Click to expand...
Click to collapse
Yeah I wish we knew the exact problem and solution but you might just be stuck trying new computers for eternity sadly..
Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
FIXED
@RomLover1999: gave the tip to reboot without a sim card, and that seemed to have fixed the problem!
seend said:
Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
Click to expand...
Click to collapse
did you tried a factory reset before updating
galardo_2 said:
did you tried a factory reset before updating
Click to expand...
Click to collapse
Nope, but just tried it and it didnt work.
Try booting without sim card
Same and via fastboot method same. Any solution? We need help its a one mi a2 more????
Unfortunately the error is not informative. I had this error when installing November update. The only way I found to see what went wrong is to check logcat during upgrade, but I think it requires root. In the end I flashed the OTA using fastboot. Still didn't get this update. Try opening shell from adb and reading logcat. I don't think anyone can help you unless we know what is 5he reason for failure
RomLover1999 said:
Try booting without sim card
Click to expand...
Click to collapse
Oh my, that worked! :highfive:
Why would something like that even work?
seend said:
Oh my, that worked! :highfive:
Why would something like that even work?
Click to expand...
Click to collapse
The november update has a bug in it that it only boots in english with a simcard inserted , other languages make the screen bug out ( at least that's what I had ) and only boot without a simcard
Worked greatly
Hey folks, just reinforcing the answer: removing the sim card before restart did the trick, the update went smooth.
Thanks @RomLover1999 and @seend
January update failed
Help! My phone is Mi A2 lite. I can't install January update. My phone is rooted and unlocked.
Thank you!
The same problem....
The same problem....anyone help?
nedjog said:
The same problem....anyone help?
Click to expand...
Click to collapse
did you unlock ? ever run TWRP/Magisk or similiar?
luminoso said:
did you unlock ? ever run TWRP/Magisk or similiar?
Click to expand...
Click to collapse
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?
nedjog said:
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?
Click to expand...
Click to collapse
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend
luminoso said:
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend
Click to expand...
Click to collapse
Ok, my phone is not rooted.
I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues
luminoso said:
I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues
Click to expand...
Click to collapse
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks
Mr.Krulez said:
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks
Click to expand...
Click to collapse
I´m assuming you have xiaomi a2? it must match codename "jasmine"
luminoso said:
I´m assuming you have xiaomi a2? it must match codename "jasmine"
Click to expand...
Click to collapse
fastboot does say that my product is jasmine
Hello!
I just got this phone today and tried to update (8.0 November security update) and keep getting the same error!
I've tried with and without sim card, tried with and without my google acc, and tried with full battery!
Do not really want to unlock/install rom again... Any ideas?
Hey guys, My phone has been bootlooping for about a few weeks now. I gave up on it thinking it was bricked, and also since i had a spare phone. Well that spare phone is no longer functional, and I need a device for work/school.
What happened was that I put the phone on the charger, and went to check on it. It was at about 60% battery life, I unplugged it, tried to unlock the screen and it crashed, went into boot loop for a while and said something along the lines as there was a problem with the OS or something?
So I tried hard resetting it via hardware buttons, and no luck. Now it just boot loops, goes from android one logo to Nokia. Stay on Nokia logo as if it's booting normally and the screen turns of and it boot loops again.
Is there anyway I could reflash the device? It's relative new so I doubt it would be a hardware issue and it was fine before?
However, and this might not be relevant, but a couple months ago i started getting modem ram dump popping up randomly on the screen, and it would restart the modem and it would be fine. Could this be the cause of my errors?
If it is a hardware issue, I'm in CA, would I be able to take it to a shop and have it fixed?
Thanks in advance!
try factory reset in recovery menu: hold power to powerdown, hold power + volume up some sec, aftet show no command with android logo on black screen, press short power + volup to show menu
k3dar7 said:
try factory reset in recovery menu: hold power to powerdown, hold power + volume up some sec, aftet show no command with android logo on black screen, press short power + volup to show menu
Click to expand...
Click to collapse
I've factory reset multiple times through recovery mode, still bootloops. Is reflashing the best option? How would I go about doing that?
zackman558 said:
I've factory reset multiple times through recovery mode, still bootloops. Is reflashing the best option? How would I go about doing that?
Click to expand...
Click to collapse
hi,you can try to update using a micro sd card or by using adb sideload command,you have to update with a new security patch that was in your phone,for example if you have june security patch then update with july patch,give a try as it might work,here you can find all the update
cristi.blidariu said:
hi,you can try to update using a micro sd card or by using adb sideload command,you have to update with a new security patch that was in your phone,for example if you have june security patch then update with july patch,give a try as it might work,here you can find all the update
Click to expand...
Click to collapse
Oh, that seems like a really solid idea! I think I had the June security Patch when these issue arised, so I should try to install July?
And that's installing it by going into recovery mode and selecting install update from SD card, correct?
cristi.blidariu said:
hi,you can try to update using a micro sd card or by using adb sideload command,you have to update with a new security patch that was in your phone,for example if you have june security patch then update with july patch,give a try as it might work,here you can find all the update
Click to expand...
Click to collapse
Hi! So I tried updating from SD using the OTA july 2019 file, and it started installing got to step 1/2 and then rebooted back to the android robot no command screen! What does this mean?
zackman558 said:
Hi! So I tried updating from SD using the OTA july 2019 file, and it started installing got to step 1/2 and then rebooted back to the android robot no command screen! What does this mean?
Click to expand...
Click to collapse
UPDATE!
I tried using june, and it wouldn't work since it's june so that made sense.
When I tried July this most recent time, it gave me the following error code:
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode : : kDownloadStateInitializationError)
E:Error in /sideload/package.zip (status 1)
Installation aborted.
What do i do now? I'm thinking of redownloading the July update and trying again
zackman558 said:
UPDATE!
I tried using june, and it wouldn't work since it's june so that made sense.
When I tried July this most recent time, it gave me the following error code:
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode : : kDownloadStateInitializationError)
E:Error in /sideload/package.zip (status 1)
Installation aborted.
What do i do now? I'm thinking of redownloading the July update and trying again
Click to expand...
Click to collapse
Try to sideload using adb sideload command
cristi.blidariu said:
Try to sideload using adb sideload command
Click to expand...
Click to collapse
I'm downloading android studio rn, how would I go about sideloading via adb? I know how to get to the adb from recovery but on the computer end what do I do. Thanks for the help so far
zackman558 said:
I'm downloading android studio rn, how would I go about sideloading via adb? I know how to get to the adb from recovery but on the computer end what do I do. Thanks for the help so far
Click to expand...
Click to collapse
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
zackman558 said:
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
Click to expand...
Click to collapse
UPDATE!
Tried to do it via adb, got it to get going. Got to 61 and then
adb: failed to read command: No error
What does this mean?
zackman558 said:
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
Click to expand...
Click to collapse
UPDATE!
Tried to do it via adb, got it to get going. Got to 61% and then
adb: failed to read command: No error
What does this mean?
zackman558 said:
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
Click to expand...
Click to collapse
Put the update file in the same folder where you have adb,then run adb sideload name of the file.zip and hit enter
zackman558 said:
UPDATE!
Tried to do it via adb, got it to get going. Got to 61% and then
adb: failed to read command: No error
What does this mean?
Click to expand...
Click to collapse
It either does this, or it fails to verify signature at 41%. Error 21
cristi.blidariu said:
Put the update file in the same folder where you have adb,then run adb sideload name of the file.zip and hit enter
Click to expand...
Click to collapse
Yes, I figured this much out but it won't complete past 61%. Recent attempts it gets to around 47%, and says signature verification failed.
Error 21
Installation aborted.
Why does this happen? Is there something wrong with the July file found on xda?
Is there a way of reflashing or something? Im confused as why it won't complete the install, only thing that i could think of is corrupted partition somehow.
zackman558 said:
Yes, I figured this much out but it won't complete past 61%. Recent attempts it gets to around 47%, and says signature verification failed.
Error 21
Installation aborted.
Why does this happen? Is there something wrong with the July file found on xda?
Is there a way of reflashing or something? Im confused as why it won't complete the install, only thing that i could think of is corrupted partition somehow.
Click to expand...
Click to collapse
I all so think that your sistem partition is corrupted,try again with August patch and see if is working,if not,then you need to take it to a service,or if is possible to unlock bootloader
cristi.blidariu said:
I all so think that your sistem partition is corrupted,try again with August patch and see if is working,if not,then you need to take it to a service,or if is possible to unlock bootloader
Click to expand...
Click to collapse
August didn't install yesterday, said something about how it needed July i think.
How would I go about unlocking bootloader? How can i check if it is already unlocked?
zackman558 said:
August didn't install yesterday, said something about how it needed July i think.
How would I go about unlocking bootloader? How can i check if it is already unlocked?
Click to expand...
Click to collapse
hi,you can all so try to downgrade aboot(bootloader) by flash an older security patch,try with december patch from 2018,as soon as you see abort error keep the phone in recovery,now download full firmware of march and try again to flash
ps/this method i have try on nokia 5,but it might all so work on nokia 7 plus i wish you best of luck
Hi All,
I'm trying to clean flash the latest May 2020 image on my P4 XL using the Flash All command in Fastboot, and it all appears to run fine until it suddenly stops at the same location with the same error (sparse 'product_b' 1/9 FAILED (remote: Partition should be flashed in fastbootd).
At that point, the flashing process stops. On the phone, it reboots back to normal and nothing was erased. Any ideas as to what may be causing this?
Thank you
Prey521 said:
Hi All,
I'm trying to clean flash the latest May 2020 image on my P4 XL using the Flash All command in Fastboot, and it all appears to run fine until it suddenly stops at the same location with the same error (sparse 'product_b' 1/9 FAILED (remote: Partition should be flashed in fastbootd).
At that point, the flashing process stops. On the phone, it reboots back to normal and nothing was erased. Any ideas as to what may be causing this?
Thank you
Click to expand...
Click to collapse
Try a different usb cable. Type C to type C causes a similar error with me while a standard one works
Make sure to update to the latest platform tools and you are using the correct image for ur phone.
gm007 said:
Make sure to update to the latest platform tools and you are using the correct image for ur phone.
Click to expand...
Click to collapse
I have the right image and was using the same tools that I had been using with no issues with my Pixel 2 XL just a few weeks ago, which are outdated by now since I hadn't updated them in a long time. Thanks, I will give that a try.
gm007 said:
Make sure to update to the latest platform tools and you are using the correct image for ur phone.
Click to expand...
Click to collapse
It was the platform tools! Updated and all is well now, thanks!