Related
Hi
ADB sideload fails at 47%, error in package.zip
The phone is in bootlop. I can't find signed MM images. The bootloader is locked. Any suggestions????
zaver said:
Hi
ADB sideload fails at 47%, error in package.zip
The phone is in bootlop. I can't find signed MM images. The bootloader is locked. Any suggestions????
Click to expand...
Click to collapse
Is your phone rooted? Because the same thing happened to me, but with the Nougat OTA update, not the ADB. I tried to unroot, but It kept failing, until I flashed from scratch the Marshmallow (with ADB).
Then I went through the OTA update again and it worked!
Maybe if you install the MM again, the Nougat may work =)
The phone is stock. I tried flashing MM with adb sideload, but I get "signature verification failed"
I also tried flashing in fastboot, but I can't without signed firmware files.
Have you extract the MM firmware files? I have successfully downgrade to MM my reteu Z play.
-=MoRpH=- said:
Have you extract the MM firmware files? I have successfully downgrade to MM my reteu Z play.
Click to expand...
Click to collapse
I have downloaded this:
https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
if i use fastboot flash:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Output:
.....
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
......
.....
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
.......
....
Invalid signed image is for every partition action.
First flash this commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
than restart the bootloader!
Now flash:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
after that make a wipe in the stock recovery. That works for me yesterday.
{Edit} Is your Bootloader unlocked? And what channel is it? (RETEU?)
Fisrt set of commands goes through OK
For the second set I get "Invalid signed image"
My bootloader is unfortunately locked.
I got the msg that the signature failed also. But the flash finished. Just flash all commands straightforward.
Gesendet von meinem XT1635-02 mit Tapatalk
I did wipe/factory reset in recovery.
Now it starts up MOTO scren, the followed by by an ""Android (like in recovery)" and text "Erasing..."
And it loops.
That's because a broken update. I had the same after trying to root. The only way for me was the downgrade to MM and update till nougat again.
Would you write me a pm with the errors you got at the downgrade process?
Gesendet von meinem XT1635-02 mit Tapatalk
zaver said:
I did wipe/factory reset in recovery.
Now it starts up MOTO scren, the followed by by an ""Android (like in recovery)" and text "Erasing..."
And it loops.
Click to expand...
Click to collapse
is your software status official or modified?
if its modified flash this by fastboot method
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
check which ur device is and download latest stock firmware... everything will be just fine..
if it fails do report us we all are here to help you
edit: ur bootloader is locked... ur in trouble my son....
unlock it then flash firmware files...it should work out
Sagar_1401 said:
unlock it then flash firmware files...it should work out
Click to expand...
Click to collapse
You are aware that unlocking erases all data and voids warranty?
Without unlocking you may try starting with
fastboot oem lock start
ending with
fastboot oem lock
(Only from memory, don't know what needs to be integrated, should do no harm if it fails, just refuse changes - but have no experience with this)
tag68 said:
You are aware that unlocking erases all data and voids warranty?
Without unlocking you may try starting with
fastboot oem lock start
ending with
fastboot oem lock
(Only from memory, don't know what needs to be integrated, should do no harm if it fails, just refuse changes - but have no experience with this)
Click to expand...
Click to collapse
he anyways need to loose all his data... he has messed up already.. what could he do now?
Maybe the data is lost, but the warranty isn't. At least by now.
Edit: I mean, it may be that the action makes sense. But it is not your decision and you should mention the drawbacks. He may not be aware that the data is lost, and there may be actions avoiding the data loss (may be needed to wait weeks or months to get the right nougat firmware). He may not be aware that warranty will be void, and it may also be an option to use the warranty and give it Lenovo. It is not your decision. Giving hints is fine, but always tell the negative part/alternative ways. You do suggestions, not a guide. The user has to decide himself, otherwise he has some right to get angry if something does not work fine.
Just my 2 cents: He needs a open bootloader to downgrade. If not, he have to wait for an full Android 7 Firmware File what is newer or exact Version of the flashed bootloader; what he flashed already i think. The big Question is: why the update stops. Where do you get the file?
Gesendet von meinem Lenovo TAB 2 A10-70F mit Tapatalk
I cannot unlock bootloader, you need to modify a setting when the phone is running in developer options.
I don't care about the data and I already have the bootloader unlock key. I need to get official signed firmware files so I can flash MM from fastboot. At least that is what I think.
Try other firmware than retail.us. You have already done
Enviado desde mi XT1635-02 mediante Tapatalk
joshua764 said:
Try other firmware than retail.us. You have already done
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
I tried reteu, retbr 6.01. I cannot flash from fastboot. I get "Invalid signed image", which to my knowledge means, that the image was not signed by motorola/google/lenovo. And I can't find official, signed images anywhere.
For me, the OTA update succeeded, worked a for a while, then at some point it rebooted, whereupon I received the same message as OP.
Using: https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
Running
Code:
fastboot flash partition gpt.bin
results in
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.072s
I assume this is because the update flashed newer firmware than what has been released by Motorola...
Attempting to sideload the .zip results in:
Code:
E: footer is wrong
EL signature verification failed
Installation aborted
So I'm left with the following choices:
1. Send the device back to Motorola for repair - won't have a phone in the meanwhile
2. Wait for Motorola to get a move on with releasing their firmware - phone unusable in the meanwhile
3. Unlock bootloader, void warranty, install LineageOS or similar, no camera until Motorola release the firmware blobs
Unless there are any other options I've missed, this is why you just cough up and go Google Nexus/Pixel gents...
Like I have said numerous times , DON'T ATTEMPT TO FLASH BACK TO MM unless you have a back up plan.
That back up plan would of course be, make sure you have the Nougat firmware for your specific device.
The phone doesn't show up in RSD Lite
But in my ADB ( $- Fastboot devices) it's showing up.
Can someone help me?
Downloaded and installed:
Device Manager
Moto USB Drivers
Moto Service (doesn't appear here too)
My brother give me this phone, and doesn't know the Gmail account he use (yeah i'm furious, he created a account just to "test" the phone, now i'm stuck in the google login screen because he wipes the phone in bootloader)
Windows 10
Motorola USB Cable
Print:
http://prntscr.com/gcrqab
What are you attempting to do?
If you are trying to flash firmware you do it through fastboot
If you are trying to log into google just create and sign in with a different account
Commands to flash via fastboot once you have downloaded the firmware are
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Note if you have more sparsechunks flash them as well in number order
If you want to play it safe and only really flash what should get the phone booting again just flash
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
Again if you have more sparsechunks flash them as well in number order
I don't know what that tool you are using is but it's not required
TheFixItMan said:
What are you attempting to do?
If you are trying to flash firmware you do it through fastboot
If you are trying to log into google just create and sign in with a different account
Commands to flash via fastboot once you have downloaded the firmware are
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Note if you have more sparsechunks flash them as well in number order
If you want to play it safe and only really flash what should get the phone booting again just flash
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
Again if you have more sparsechunks flash them as well in number order
I don't know what that tool you are using is but it's not required
Click to expand...
Click to collapse
I can do it with bootloader locked?
i"m with FRP (Factory Reset Protection) i can't pass without the gmail that he created and doesn't even remember the email.
TeuzHd said:
I can do it with bootloader locked?
Click to expand...
Click to collapse
Yes if it's original Motorola firmware
You only need to unlock bootloader for custom firmware/roms
TheFixItMan said:
What are you attempting to do?
If you are trying to flash firmware you do it through fastboot
If you are trying to log into google just create and sign in with a different account
Commands to flash via fastboot once you have downloaded the firmware are
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Note if you have more sparsechunks flash them as well in number order
If you want to play it safe and only really flash what should get the phone booting again just flash
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
Again if you have more sparsechunks flash them as well in number order
I don't know what that tool you are using is but it's not required
Click to expand...
Click to collapse
TheFixItMan said:
Yes if it's original Motorola firmware
You only need to unlock bootloader for custom firmware/roms
Click to expand...
Click to collapse
I'm getting this with everything:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
That's my ADB root folder: http://prntscr.com/gcz5ld
TeuzHd said:
I'm getting this with everything:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
That's my ADB root folder: http://prntscr.com/gcz5ld
Click to expand...
Click to collapse
from that you should be typing the following
Code:
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
The errors you are getting is because of your adb version - it should still flash
long as you get an output that looks like this at the end
Code:
sending 'logo' (460 KB)...
OKAY [ 0.099s]
writing 'logo'...
OKAY [ 0.154s]
finished. total time: 0.256s
I have encluded my adb and fastboot folder for you to use (excludes any firmware just adb and fastboot) for use on windows
Download from link below
Platform-tools
TheFixItMan said:
from that you should be typing the following
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.520s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.722s[/HTML]
i can try with another PC, should work?
Click to expand...
Click to collapse
TeuzHd said:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.520s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.722s[/HTML]
i can try with another PC, should work?
Click to expand...
Click to collapse
The firmware you are trying to flash is a lower version than what is installed - You must get firmware that is equal to or newer than the firmware on the device already else it will fail
eg you cant flash android 7.0 on a device that has a bootloader that is for 7.1
you will have to find the correct firmware for your device
note there is no harm trying the firmware because as you can see - if its wrong it will just fail the validation test and not flash
TheFixItMan said:
The firmware you are trying to flash is a lower version than what is installed - You must get firmware that is equal to or newer than the firmware on the device already else it will fail
eg you cant flash android 7.0 on a device that has a bootloader that is for 7.1
you will have to find the correct firmware for your device
note there is no harm trying the firmware because as you can see - if its wrong it will just fail the validation test and not flash
Click to expand...
Click to collapse
Reflashing the 7.1.2 version i can pass FRP? i'm trying to bypas FRP.
In the authorized warranty, they told me that they can not do any software repairs on the device until I remove the FRP, but as I said we do not know the account he used to "test" the device
try adding this to the list of fastboot commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
---------- Post added at 06:24 PM ---------- Previous post was at 06:21 PM ----------
TeuzHd said:
Reflashing the 7.1.2 version i can pass FRP? i'm trying to bypas FRP.
In the authorized warranty, they told me that they can not do any software repairs on the device until I remove the FRP, but as I said we do not know the account he used to "test" the device
Click to expand...
Click to collapse
best thing is to google
eg
https://www.progeeksblog.com/frp-bypass-apk/
Iv never had do anything with frp so no idea how to do it on this device
TheFixItMan said:
try adding this to the list of fastboot commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
---------- Post added at 06:24 PM ---------- Previous post was at 06:21 PM ----------
best thing is to google
eg
https://www.progeeksblog.com/frp-bypass-apk/
Iv never had do anything with frp so no idea how to do it on this device
Click to expand...
Click to collapse
I did this, but the APK and Share exploit's doesn't work anymore
do you mean there is a password on the device because you can bypass that easy
just goto twrp
advanced
file manager
data
system
click on each of the following files and delete
gatekeeper-password.key
gatekeeper-patten.key
locksettings.db-shm
locksettings.db-wal
other than that I can't help anymore
TheFixItMan said:
do you mean there is a password on the device because you can bypass that easy
just goto twrp
advanced
file manager
data
system
click on each of the following files and delete
gatekeeper-password.key
gatekeeper-patten.key
locksettings.db-shm
locksettings.db-wal
other than that I can't help anymore
Click to expand...
Click to collapse
can't start TWRP
1- bootload locked with ADB options OFF
to put adb options on i need to pass FRP
TeuzHd said:
can't start TWRP
1- bootload locked with ADB options OFF
to put adb options on i need to pass FRP
Click to expand...
Click to collapse
have you tried
https://www.youtube.com/watch?v=xhf9egv8-ys
uses this app
https://play.google.com/store/apps/details?id=com.wUnlockiOfficial
TheFixItMan said:
have you tried
https://www.youtube.com/watch?v=xhf9egv8-ys
uses this app
https://play.google.com/store/apps/details?id=com.wUnlockiOfficial
Click to expand...
Click to collapse
How can i install a app without pass FRP?
TeuzHd said:
How can i install a app without pass FRP?
Click to expand...
Click to collapse
Do some googling
https://youtu.be/GkmL5tUtyB0
With this tool
http://www.mediafire.com/file/yif2m8j11dx1ur8/Moto+G4+Plus+Google+Account.rar
Watch videos and Google - don't rely on me to search for thing for you
TheFixItMan said:
Do some googling
https://youtu.be/GkmL5tUtyB0
With this tool
http://www.mediafire.com/file/yif2m8j11dx1ur8/Moto+G4+Plus+Google+Account.rar
Watch videos and Google - don't rely on me to search for thing for you
Click to expand...
Click to collapse
i alredy do this, look in the thread
Hi,
Where I can download the last firmware for Moto G5 XT1676 ?
hELLO..
I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from twrp recovery and tried to install the same software again but it gave me the error at the end ..what should I know now to fix the mobile knowing that when i try to select recoverymode it tells me ersing and then takes m back to fastboot
note the first time i just opened a bat file with the software that installed the software automatically..
the bat file told me that
<bootloader> slot-count not found
<bootloader> slot suffixes not found
<bootloader>has-slot:fsg not found
hELLO..
I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from twrp recovery and tried to install the same software again but it gave me the error at the end ..what should I know now to fix the mobile knowing that when i try to select recoverymode it tells me ersing and then takes m back to fastboot
note the first time i just opened a bat file with the software that installed the software automatically..
the bat file told me that
<bootloader> slot-count not found
<bootloader> slot suffixes not found
<bootloader>has-slot:fsg not found
Click to expand...
Click to collapse
Code:
<bootloader> slot-count not found
<bootloader> slot suffixes not found
<bootloader>has-slot:fsg not found
This is a totally normal output
You either have an error elsewhere or you are trying to flash wrong firmware
If you have a working bootloader there's no need to flash gpt or bootloader parts of the firmware if you are flashing the same android version - if you are upgrading android versions you will need to flash these
The commands are
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Firmware can be download from https://mirrors.lolinet.com/firmware/moto/cedric/official/
I have a problem with flashing bootlogo via fastboot. after
Code:
fastboot flash logo logo.bin
it show me
Code:
Sending 'logo__a' (3283 KB) OKAY [ 0.088s]
Writing 'logo__a' (bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed
I supposed that there is something with a/b partitioning, but how to correct flash bootlogo?
forgottennick said:
I have a problem with flashing bootlogo via fastboot. after
Code:
fastboot flash logo logo.bin
it show me
Code:
Sending 'logo__a' (3283 KB) OKAY [ 0.088s]
Writing 'logo__a' (bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed
I supposed that there is something with a/b partitioning, but how to correct flash bootlogo?
Click to expand...
Click to collapse
Bootloader is unlocked?
Could try
Code:
fastboot flash logo_b logo.bin
If that work
Switch slots
Code:
fastboot --set-active=b
And flash other side
Code:
fastboot flash logo_a logo.bin
Then switch back
Code:
fastboot --set-active=a
Sent from my Moto E (4) using Tapatalk
Yes, bootloader unlocked/twrp/magisk, active slot A, stock 8.0
it is correctly sequence?
Code:
fastboot flash logo_b logo.bin
fastboot --set-active=b
fastboot flash logo_a logo.bin
fastboot --set-active=a
forgottennick said:
Yes, bootloader unlocked/twrp/magisk, active slot A, stock 8.0
it is correctly sequence?
Click to expand...
Click to collapse
Yes if current active is slot _a
Code:
fastboot getvar current-slot
Sent from my payton_sprout using XDA Labs
Hello kind saviour,
I accidentally deleted my build.prop file and now my phone is stuck on "the boot loader is unlocked and software integrity cannot be guaranteed..." screen at boot.
I use the AOSIP rom for OnePlus 7t,if that helps.
I do NOT want to lose any data and preferably not lose any system settings either.
Updating the ROM is OK for me. Please let me know if that is a good idea however.
The good part:
fastboot boot TWRP.img works, sdcard data de-cryption works, i can access files with MTP. Already made a backup of most important data.
I do not know which AOSIP version I have, but it's not the latest.
Doesn't work: fastboot boot magisk-patched.img (image might be too old?)
Doesn't work: fastboot reboot fastboot + fastboot boot boot.img -> Error:
*FAILED (remote: 'Download is not allowed on locked devices')
Booting from A instead of B goes into infinite booting animation.
adb commands during twrp don't work
No adb access anywhere else
I have no backup of build.prop
I have a builT.prop file and i suspect i saved it with wrong name (but I still can't access /system partition)
I had access to /system partition during first twrp boot, but accidentally mounted it as read only the first time.
After following reboots to twrp, system is always unmountable (both from slot a as well as slot b).
Even after deleting twrp folder from pc, the system partition remains unmountable:
*Failed to mount '/system_root' (Permission denied)
*Failed to mount '/vendor' (Permission denied)
bootloader is unlocked & phone is rooted with magisk.
If you could help me with a solution where i can keep my data you would make me soo happy. Having a rough time with life lately and you could be my second coming of Jesus
Thanks in advance.
Dirty flash latest aosip with TWRP or with fastboot
HueyT said:
Dirty flash latest aosip with TWRP or with fastboot
Click to expand...
Click to collapse
Thank you! I will try that later today and report back.
I tried dirty flashing the latest AOSIP update, and it made everything worse. (Maybe I was on the wrong slot??)
Now there is no fastbootD, no recovery, and neither possible to fastboot boot twrp.img!
Only thing that worked was the bootloader (fastboot).
I didn't even get the usual "the boot loader is unlocked and software integrity cannot be guaranteed..." screen.
However, i changed slot with fastboot and now I have recovery and fastbootD and can boot twrp again.
Now I'm really worried about messing up my next steps, so would be super grateful for any help you can give me. I believe we are near a solution here.
Big Questions:
Should I dirty update the rom from fastbootD or from TWRP?
Which *SLOT* do I update from?
History of how everything went wrong:
Spoiler: command line messages and responses
fastboot update OSiP-10-Gapps-hotdogb-20210621-img.zip
Code:
--------------------------------------------
Bootloader Version...: unknown
Baseband Version.....:
Serial Number........: 9de0f5c0
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error:
Setting current slot to 'b'
FAILED (remote: 'set_active command is not allowed on locked devices')
fastboot: error: Command failed
fastboot oem device-info
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
//I manually rebooted to bootloader (fastboot) here//
fastboot oem device-info
Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
(bootloader) op_abl_version: 0x31
(bootloader) cal_rebootcount: 0x31
OKAY [ 0.050s]
Finished. Total time: 0.053s
fastboot reboot fastboot
Code:
Rebooting into fastboot
OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Update: i found a solution by updating adb/fastboot .exe files,
flashing twrp-3-5-1_10-hotdog-sdcardfs.img
and dirty flashing the latest aosip image in twrp's fastboot mode
I got a "QUALCOMM CrashDump Mode" message once but it boots to aosip now. We will see if the crashdump messages appear again or not.