I have tried following guides on going back to stock rom but getting many errors in doing that. I have also tried flashing many different roms with TWRP. I get many errors when doing that one of them is local error 7. One also tells me that it detects OEM partition now at potter. The model of this device is XT1806.
This is my attempt to get things back to stock.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.016s]
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.094s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.538s]
finished. total time: 0.695s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71925 KB)...
OKAY [ 2.068s]
writing 'modem'...
OKAY [ 1.067s]
finished. total time: 3.151s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3024 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.203s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.488s]
writing 'dsp'...
OKAY [ 0.284s]
finished. total time: 0.787s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.063s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.188s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.492s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.375s]
finished. total time: 0.867s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.614s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.484s]
finished. total time: 1.098s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (256355 KB)...
OKAY [ 7.384s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.415s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (262115 KB)...
OKAY [ 7.538s]
writing 'system'...
OKAY [ 3.399s]
finished. total time: 10.937s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (259034 KB)...
OKAY [ 7.468s]
writing 'system'...
OKAY [ 3.535s]
finished. total time: 11.019s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262013 KB)...
OKAY [ 7.507s]
writing 'system'...
OKAY [ 3.523s]
finished. total time: 11.046s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 7.517s]
writing 'system'...
OKAY [ 3.387s]
finished. total time: 10.920s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 7.492s]
writing 'system'...
OKAY [ 3.283s]
finished. total time: 10.775s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (259637 KB)...
OKAY [ 7.466s]
writing 'system'...
OKAY [ 3.293s]
finished. total time: 10.775s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (240915 KB)...
OKAY [ 6.953s]
writing 'system'...
OKAY [ 3.633s]
finished. total time: 10.617s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 7.506s]
writing 'system'...
OKAY [ 3.650s]
finished. total time: 11.155s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (233189 KB)...
OKAY [ 6.672s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 7.237s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.10
target reported max download size of 534773760 bytes
sending 'system' (65436 KB)...
OKAY [ 1.890s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.905s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (145482 KB)...
OKAY [ 4.172s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.172s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.813s]
finished. total time: 0.813s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase DDR
erasing 'DDR'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
I'll need a bit more information.
What stock ROM did you try and flash? There's stock Nougat for the xt1806 that is different that stock Nougat for the other versions (XT1800,XT1801,XT1802,etc). It seems the Stock Oreo build can be flashed to all of them with minor issues.
Also, why are you trying to flash an OTA using TWRP? That won't work.
pizzaboy192 said:
I'll need a bit more information.
What stock ROM did you try and flash? There's stock Nougat for the xt1806 that is different that stock Nougat for the other versions (XT1800,XT1801,XT1802,etc). It seems the Stock Oreo build can be flashed to all of them with minor issues.
Also, why are you trying to flash an OTA using TWRP? That won't work.
Click to expand...
Click to collapse
I figured out after that it was OTA. The point I was trying to show was that it is detecting potter on the OEM partition. All other roms like PixelExperience, Xtended Rom and Arrow all just give error 7. E1001 : Failed to update system image.
I am trying to flash stock ROM SANDERS_OPS28.65-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
briant97 said:
I figured out after that it was OTA. The point I was trying to show was that it is detecting potter on the OEM partition. All other roms like PixelExperience, Xtended Rom and Arrow all just give error 7. E1001 : Failed to update system image.
I am trying to flash stock ROM SANDERS_OPS28.65-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
Click to expand...
Click to collapse
Not sure about this but check in your root (/) and/or /vendor directory for default.prop file (/vendor might have a build.prop instead). Check to see if there's anything odd there. I once had a default.prop with entries from a long-forgotten custom ROM that was causing issues. See if potter is in any of them.
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
Not sure about this but check in your root (/) and/or /vendor directory for default.prop file (/vendor might have a build.prop instead). Check to see if there's anything odd there. I once had a default.prop with entries from a long-forgotten custom ROM that was causing issues. See if potter is in any of them.
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
default.prop
https://ghostbin.com/paste/bx9uj
build.prop
I could not find a build.prop file anywhere.
briant97 said:
default.prop
https://ghostbin.com/paste/bx9uj
build.prop
I could not find a build.prop file anywhere.
Click to expand...
Click to collapse
Every ROM has a build.prop, if I'm not mistaken, sitting in /system directory.
EDIT: Your default.prop looks good. Has sanders throughout and shows sdk25 (Nougat).
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
Every ROM has a build.prop, if I'm not mistaken, sitting in /system directory.
EDIT: Your default.prop looks good. Has sanders throughout and shows sdk25 (Nougat).
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
I cannot find a build.prop file /system only contains a lost and found directory.
I also looked through every single directory. Can someone provide me with a flashable build.prop file maybe that would help resolve.
This is oem.prop file. May need a way to resolve this file is part of the issue as well. This for sure contains potter info.
#
# OEM_BUILD_PROPERTIES
#
ro.build.version.incremental=b8ea
ro.build.version.ci=16
ro.mot.build.guid=54d0fbcff7908bd
ro.product.name=potter
ro.mot.build.oem.product=potter
ro.mot.build.customerid=retail
Also here is my recovery.log for when i tried to flash Xtended Rom
https://hastebin.com/uvejafafug.sql
briant97 said:
I cannot find a build.prop file /system only contains a lost and found directory.
I also looked through every single directory. Can someone provide me with a flashable build.prop file maybe that would help resolve.
This is oem.prop file. May need a way to resolve this file is part of the issue as well. This for sure contains potter info.
#
# OEM_BUILD_PROPERTIES
#
ro.build.version.incremental=b8ea
ro.build.version.ci=16
ro.mot.build.guid=54d0fbcff7908bd
ro.product.name=potter
ro.mot.build.oem.product=potter
ro.mot.build.customerid=retail
Also here is my recovery.log for when i tried to flash Xtended Rom
https://hastebin.com/uvejafafug.sql
Click to expand...
Click to collapse
simple just flash the correct stock image as i can see you can successfully flash bootloader of sanders
chirayu19091997 said:
simple just flash the correct stock image as i can see you can successfully flash bootloader of sanders
Click to expand...
Click to collapse
Can you please let me know how to do this correctly. As you can see above I tried to flash it via the bootloader back to stock using the commands. If I can use TWRP, where can I find a flashable stock rom. As so far nothing is working.
briant97 said:
Can you please let me know how to do this correctly. As you can see above I tried to flash it via the bootloader back to stock using the commands. If I can use TWRP, where can I find a flashable stock rom. As so far nothing is working.
Click to expand...
Click to collapse
As far as a TWRP flashable for the XT1806, this is what I used way back when. Nougat. Still on it as a primary ROM. No chance of OTAs or anything but I'm not interested in stock Oreo anyway.
https://forum.xda-developers.com/showthread.php?t=3738502
[ROM][STOCK][TWRP ZIP] Sanders Stock 7.1.1 rooted NPS26.116-61
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Here is my attempts to flash this stock file. It still wont boot to an OS. Just reboots to twrp.
Total brain freeze. I remember the rebooting into TWRP thing and there were numerous posts about it. Fix was trivial but for the life of me I can't remember.
As far as getting into the OS, have you tried manually via the bootloader screen?
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
Total brain freeze. I remember the rebooting into TWRP thing and there were numerous posts about it. Fix was trivial but for the life of me I can't remember.
As far as getting into the OS, have you tried manually via the bootloader screen?
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
How do you manually get into the OS via bootloader?
briant97 said:
How do you manually get into the OS via bootloader?
Click to expand...
Click to collapse
In TWRP, choose "reboot bootloader" and then in that, choose "start"
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
briant97 said:
Here is my attempts to flash this stock file. It still wont boot to an OS. Just reboots to twrp.
Click to expand...
Click to collapse
That 2nd shot is normal errors for that specific restore (even says so in the OP). Looks good so far, just need to get it to boot to OS
pizzaboy192 said:
In TWRP, choose "reboot bootloader" and then in that, choose "start"
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
That 2nd shot is normal errors for that specific restore (even says so in the OP). Looks good so far, just need to get it to boot to OS
Click to expand...
Click to collapse
It will not boot into the OS.
Anybody have any other ideas or thoughts. The oem partition is still the issue. Is there anyway to reflash this partition to the correct version?
I tried letting the phone boot over night as requested above but it never booted.
Hmm I made a bat file to fix this issue but can't find it
the concept is the bootloader accepts the firmware I told you can flash rom because you can flash Sanders bootloader and as seen in op
will see bat just hit me a private message me busy till 27 Nov 2018 and I can help on 27 or 28 IST
marcdw said:
Total brain freeze. I remember the rebooting into TWRP thing and there were numerous posts about it. Fix was trivial but for the life of me I can't remember.
As far as getting into the OS, have you tried manually via the bootloader screen?
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
Sent you a private message.
I think you should try QPST flashing because this method will flash stock rom while device is off or even no battery,hope this can overwrite your prev wrong rom,
glewo45 said:
I think you should try QPST flashing because this method will flash stock rom while device is off or even no battery,hope this can overwrite your prev wrong rom,
Click to expand...
Click to collapse
https://androidmtk.com/use-qpst-flash-tool
I got to step 5 here and nothing shows under ports. I have tried when phone is at bootloader and also when phone is in twrp.
Related
Hi all, I need some (or much) help I'm trying to update to the 602 version, to EMUI 3.0 or the lollipop but I really can´t figure out how, downloaded 'My Rom v3.3' according to instructions I should update to 602 I've already downloaded a CWM flashable 'http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343' tryed to flash CWM via fastboot but nothing happens when I try to go to recovery just as the latest TWRP, What I'm missing? Please help. :crying:
KV92GT said:
Hi all, I need some (or much) help I'm trying to update to the 602 version, to EMUI 3.0 or the lollipop but I really can´t figure out how, downloaded 'My Rom v3.3' according to instructions I should update to 602 I've already downloaded a CWM flashable 'http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343' tryed to flash CWM via fastboot but nothing happens when I try to go to recovery just as the latest TWRP, What I'm missing? Please help. :crying:
Click to expand...
Click to collapse
Hi! You need to flash the stock recovery, b133 or b135 unfortunately I do not have those files, there's a post pointing to stock recovery but links are dead, may be someone here could be kind enough to provide those images for us
KV92GT said:
Hi all, I need some (or much) help I'm trying to update to the 602 version, to EMUI 3.0 or the lollipop but I really can´t figure out how, downloaded 'My Rom v3.3' according to instructions I should update to 602 I've already downloaded a CWM flashable 'http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343' tryed to flash CWM via fastboot but nothing happens when I try to go to recovery just as the latest TWRP, What I'm missing? Please help. :crying:
Click to expand...
Click to collapse
I am exactly in the same situation for several weeks.....
My actual config is
My-Rom V1.2
TWRP 2.8.1.0
I want to upgrade to either My-Rom 3.3 or Stock lollipop
The main issue is that I can't do that with my actual recovery, and no other recovery works on my phone, no idea why.
The only recovery img that is working is the one I use at the moment: openrecovery-twrp-2.8.1.0.img
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery [COLOR="Green"]openrecovery-twrp-2.8.1.0.img[/COLOR]
target reported max download size of 838860800 bytes
sending 'recovery' (11896 KB)...
OKAY [ 0.463s]
writing 'recovery'...
OKAY [ 0.582s]
finished. total time: 1.047s
Here's a little peak on all recovery img files I have tried so far:
cwm.img
recovery_cwm.img
CWM-6.0.5.0.img
B609_recovery.img
recovery-clockwork-3.0.0.5-ascend.img
TWRP-2.8.7.0.img
TWRP-2.8.7.0.img
openrecovery-twrp-2.8.1.0.img
And you can see below that the flashing procedure is completely normal for all attempts
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.671s]
finished. total time: 1.130s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery_cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.461s]
writing 'recovery'...
OKAY [ 0.559s]
finished. total time: 1.023s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\CWM-6.0.5.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.570s]
finished. total time: 1.032s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\B609_recovery.img
target reported max download size of 838860800 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.634s]
writing 'recovery'...
OKAY [ 0.793s]
finished. total time: 1.430s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery-clockwork-3.0.0.5-ascend.img
target reported max download size of 838860800 bytes
sending 'recovery' (3636 KB)...
OKAY [ 0.145s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.317s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\TWRP-2.8.7.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (13182 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 0.643s]
finished. total time: 1.157s
I grabbed all those recovery img here on the P7 forums and they are apparently working for most of us.
Consider I flashed each of them at least 5 times. None of them works but the last one.
The most horrible is that I don't even know WHY ???????
I have read countless threads in this forum to unblock the situation and I am still nowhere because, if I have found a few people having the same issue, I could not found any valid solution.
If you can, please help.
Well... Here you have it
Do it at YOUR OWN RISK!
This is the STOCK RECOVERY B135 from my Huawey Ascend P7
You can flash it using flashify or go with the fastboot procedure
1. Unpack it
2. Flash it
'https://mega.nz/#!0pF0jawS!Q8NNIkYIy_k2e6abgTYvAoyT11M92HL5iG9riG3f7-k'
SiulGKT said:
Well... Here you have it
Do it at YOUR OWN RISK!
This is the STOCK RECOVERY B135 from my Huawey Ascend P7
You can flash it using flashify or go with the fastboot procedure
1. Unpack it
2. Flash it
'https://mega.nz/#!0pF0jawS!Q8NNIkYIy_k2e6abgTYvAoyT11M92HL5iG9riG3f7-k'
Click to expand...
Click to collapse
Thank you! downloading,do you recommend flashify?
KV92GT said:
Thank you! downloading,do you recommend flashify?
Click to expand...
Click to collapse
You'de welcome, yes!
SiulGKT said:
You'de welcome, yes!
Click to expand...
Click to collapse
Thank you very much SiulGKT it worked like a charm! now I will try to update to 3.3! :laugh:
Crippius said:
I am exactly in the same situation for several weeks.....
My actual config is
My-Rom V1.2
TWRP 2.8.1.0
I want to upgrade to either My-Rom 3.3 or Stock lollipop
The main issue is that I can't do that with my actual recovery, and no other recovery works on my phone, no idea why.
The only recovery img that is working is the one I use at the moment: openrecovery-twrp-2.8.1.0.img
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery [COLOR="Green"]openrecovery-twrp-2.8.1.0.img[/COLOR]
target reported max download size of 838860800 bytes
sending 'recovery' (11896 KB)...
OKAY [ 0.463s]
writing 'recovery'...
OKAY [ 0.582s]
finished. total time: 1.047s
Here's a little peak on all recovery img files I have tried so far:
cwm.img
recovery_cwm.img
CWM-6.0.5.0.img
B609_recovery.img
recovery-clockwork-3.0.0.5-ascend.img
TWRP-2.8.7.0.img
TWRP-2.8.7.0.img
openrecovery-twrp-2.8.1.0.img
And you can see below that the flashing procedure is completely normal for all attempts
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.671s]
finished. total time: 1.130s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery_cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.461s]
writing 'recovery'...
OKAY [ 0.559s]
finished. total time: 1.023s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\CWM-6.0.5.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.570s]
finished. total time: 1.032s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\B609_recovery.img
target reported max download size of 838860800 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.634s]
writing 'recovery'...
OKAY [ 0.793s]
finished. total time: 1.430s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery-clockwork-3.0.0.5-ascend.img
target reported max download size of 838860800 bytes
sending 'recovery' (3636 KB)...
OKAY [ 0.145s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.317s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\TWRP-2.8.7.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (13182 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 0.643s]
finished. total time: 1.157s
I grabbed all those recovery img here on the P7 forums and they are apparently working for most of us.
Consider I flashed each of them at least 5 times. None of them works but the last one.
The most horrible is that I don't even know WHY ???????
I have read countless threads in this forum to unblock the situation and I am still nowhere because, if I have found a few people having the same issue, I could not found any valid solution.
If you can, please help.
Click to expand...
Click to collapse
I've uploaded the b135, give it a try.
---------- Post added at 04:41 PM ---------- Previous post was at 04:36 PM ----------
KV92GT said:
Thank you very much SiulGKT it worked like a charm! now I will try to update to 3.3! :laugh:
Click to expand...
Click to collapse
Glad to see it! You're welcome! Good luck!
There's an improvement for sure, to not say a breakthrough
I am in the Huwaei recovery and it is currently installing the B609 update.app that I put in dload folder.
Crossing fingers!
A big up to you already man :good:
B135 Installed
B609 Installed
B621 installing
Thanks again @SiulGKT
SiulGKT said:
Well... Here you have it
Do it at YOUR OWN RISK!
This is the STOCK RECOVERY B135 from my Huawey Ascend P7
You can flash it using flashify or go with the fastboot procedure
1. Unpack it
2. Flash it
'https://mega.nz/#!0pF0jawS!Q8NNIkYIy_k2e6abgTYvAoyT11M92HL5iG9riG3f7-k'
Click to expand...
Click to collapse
Hello, I'm sorry but when i try to download your file, mega is asking for a key, can you give me this key?
Hope you still have it
hello i can't lock the bootloader of my nexus 6 since i received it from the technical service of motorola. before i send it to them it was closed and when i received it it was unlock and another no padlock its apear when is booting. ive traid every thing but nothing work
i can flash factory images but i cant relock it. fastboot oem lock works on my nexus 7 but not on my nexus 6
You should use the correct command, as google documents it.
But locking your bootloader is a pretty bad idea, and will prevent you from having any ability to fix anything if it fails to boot. If you cannot boot into android, you cannot enable unlock, and will be locked out for good with no recourse other then to send it in.
See this page
https://source.android.com/security/verifiedboot/verified-boot.html
Scroll down to "changing the device state" and use the given fastboot command.
i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem
alex482 said:
i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem
Click to expand...
Click to collapse
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.
istperson said:
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.
Click to expand...
Click to collapse
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly
alex482 said:
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly
Click to expand...
Click to collapse
Do other adb/fastboot commands work?
What does
Code:
fastboot devices
say?
yes its work adb devices , adb reboot, adb reboot bootloader, fastboot flash...., fastboot devices , fastboot reboot and fastboot reboot-bootloader
istperson said:
What does
Code:
fastboot devices
say?
Click to expand...
Click to collapse
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot
C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.077s
that it what it say when i tried to lock it but i also tried to flash the factory image its work but then when i try to lock it the same massage appear again
Please paste here the output of flashing the factory image.
istperson said:
Please paste here the output of flashing the factory image.
Click to expand...
Click to collapse
yes when its finish i copy and past everything here
I'd be curious what specific error it gives with the fastboot flashing lock says, as that should be the command now assuming your on MM and using up to date SDK.
C:\Program Files (x86)\platform-tools>adb devices
List of devices attached
ZX1G423BMR device
C:\Program Files (x86)\platform-tools>adb reboot bootloader
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot
C:\Program Files (x86)\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
C:\Program Files (x86)\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\Program Files (x86)\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.617s]
finished. total time: 0.617s
C:\Program Files (x86)\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.409s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.685s]
finished. total time: 1.102s
C:\Program Files (x86)\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
C:\Program Files (x86)\platform-tools>fastboot flash radio radio-shamu-d4.01-9625-05.27+fsg-9625-02.104.img
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 4.283s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.522s]
finished. total time: 5.808s
C:\Program Files (x86)\platform-tools>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\platform-tools>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (517178 KB)...
OKAY [ 20.071s]
writing 'system'...
OKAY [ 6.964s]
sending sparse 'system' (515137 KB)...
OKAY [ 20.267s]
writing 'system'...
OKAY [ 7.088s]
sending sparse 'system' (518219 KB)...
OKAY [ 20.493s]
writing 'system'...
OKAY [ 7.188s]
sending sparse 'system' (492726 KB)...
OKAY [ 19.042s]
writing 'system'...
OKAY [ 6.804s]
finished. total time: 107.938s
C:\Program Files (x86)\platform-tools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8197 KB)...
OKAY [ 0.316s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.431s
C:\Program Files (x86)\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8915 KB)...
OKAY [ 0.334s]
writing 'recovery'...
OKAY [ 0.126s]
finished. total time: 0.463s
C:\Program Files (x86)\platform-tools>fasboot flash cache cache.img
"fasboot" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
C:\Program Files (x86)\platform-tools>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.057s]
sending 'cache' (6248 KB)...
OKAY [ 0.237s]
writing 'cache'...
OKAY [ 0.137s]
finished. total time: 0.446s
C:\Program Files (x86)\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.349s]
finished. total time: 1.349s
C:\Program Files (x86)\platform-tools>fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.165s]
sending 'userdata' (138868 KB)...
OKAY [ 5.070s]
writing 'userdata'...
OKAY [ 3.001s]
finished. total time: 9.236s
C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.070s
C:\Program Files (x86)\platform-tools>fastboot reboot
rebooting...
finished. total time: -0.000s
yes im on 6.0 marshmallow and the sdk with the latest update
Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?
istperson said:
Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?
Click to expand...
Click to collapse
yes its all turn on i send to it to change the rear camera because it was factory failure
Then it too must be a hardware problem.
do you think so?
alex482 said:
do you think so?
Click to expand...
Click to collapse
It seems, you did everything right. The line "(bootloader) Please flash valid signed images firstly!" is returned by the bootloader, and the bootloader is, opposite to adb and fastboot, closed source. So no help from the source.
I googled it, and it appeared on the Moto G 2014 device.
Hi
After de-brand, and upgraded to Nougat, bootloader isn't restored to locked
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.009s
But when i flash pre-rooted boot image,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot rooted_b378_boot.img
target reported max download size of 471859200 bytes
sending 'boot' (16204 KB)...
OKAY [ 0.350s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.365s
Help me please
Hey guys, recently I hard bricked my sanders 1802 in way that everything I tried does not work.
After I flashed lineage 16.0, the fingerprint sensor and some other things were not working, then I tried downgrading it back to stock via fastboot, Sanders retail 8.1.
After that everthing went to hell. It got into bootloop. So i tried to restore it via Leonovo Moto Smart Assistant. Went back to bootloop and started showing some cache mount issues.
I tried over 10 different ROMs and every time it showed cache mout problems or ERROR 6, 7 and 1 in TWRP and sometimes kernel issues.
I've already tried flashing new kernels, tried every ERROR 6 and 7 solutions that are available online and nothing happens.
Right now I have it at the best shape possible, it has the latest TWRP installed (3.2.1 sanders r20), it does not show any cache nor kernel errors when I try to install a ROM, but it keeps giving me the ERROR 7 even when I delete the assert line on the updater-script file.
Searching the XDA foruns I found someone talking about getting a fresh start for the phone by flash the sdcard with mmcbk0.img. I'm not even sure if that's the right path to solve my problem, but I thought I give it a try since I have no idea what else to do.
I'm pretty noob on everything regarding android, just followed everything easily when it comes to tutorials.
Can someone please help me? Is the new mmcbk0.img file the right path or should I try somthing else? I talked to a "expert" guy here in my city and he said that the phone is gone and there's nothing I can do. Is it possible?
Have you tried TWRP 3.3
pradeeppk said:
Have you tried TWRP 3.3
Click to expand...
Click to collapse
It does not even install, it gives me this:
cmd: getvar: partition-type: recovery
cmd: getvar: max-download-size
cmd: download: 00471000
cmd: flash: recovery
Error: failed to load kernel!
Boot up failed
voliveira92 said:
It does not even install, it gives me this:
cmd: getvar: partition-type: recovery
cmd: getvar: max-download-size
cmd: download: 00471000
cmd: flash: recovery
Error: failed to load kernel!
Boot up failed
Click to expand...
Click to collapse
Are you using fastboot command to flash recovery, Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there. Have you any backup of your stock image?
pradeeppk said:
Are you using fastboot command to flash recovery, Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there. Have you any backup of your stock image?
Click to expand...
Click to collapse
Yes, I'm using fastboot to flash it.
I tried booting directly from twrp.3.3.1 but it gives me this error message:
cannot load 'recovery': No such file or directory
Searched for a solution and tried to rename the file to one single name (twrp.img), tried renaming the adb/fastboot folder to one single name as well and it didn't work.
And unfortunately I don't have a backup of my stock
voliveira92 said:
Yes, I'm using fastboot to flash it.
I tried booting directly from twrp.3.3.1 but it gives me this error message:
cannot load 'recovery': No such file or directory
Searched for a solution and tried to rename the file to one single name (twrp.img), tried renaming the adb/fastboot folder to one single name as well and it didn't work.
And unfortunately I don't have a backup of my stock
Click to expand...
Click to collapse
Have you missing something? i mean .img, Code is fastboot boot recovery twrp.img.
HTML:
pradeeppk said:
Have you missing something? i mean .img, Code is fastboot boot recovery twrp.img.
Click to expand...
Click to collapse
I'm pretty sure that I'm not missing anything.
I was able to flash Twrp 3.3.0 from this thread (https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-3-0-t3940378), but now it keeps giving me Error 7 and 'unable to mount system'.
Tried lineage and Havocs ROM. Tried altering the assert line again and no changes.
pradeeppk said:
Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there.
Click to expand...
Click to collapse
Wrong command format
voliveira92 said:
it gives me this error message:
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
Try the command:
Code:
fastboot boot <your_twrp_filename.img>
Run
Code:
fastboot --help
for the help on how to use fastboot.
D302Thakur said:
Wrong command format
Try the command:
Code:
fastboot boot <your_twrp_filename.img>
Run
Code:
fastboot --help
for the help on how to use fastboot.
Click to expand...
Click to collapse
I'm not having troubles with flashing or booting Twrp via fastboot, I'm having issues with Twrp or something else that is interfering and not allowing me to flash any ROM.
I've tried every TWRP I've found, 3.2.1, 3.3.0, 3.3.1, all of them gives me the ERROR 7 when I try to flash a ROM.
Looked online for the ERROR 7 solution, tried erasing the assert line from updater-script file and still no help.
The times that I flashed the ROMs via fastboot or adb the phone stays in bootloop or just freezes at the boot screen.
I don't have a backup stock file.
voliveira92 said:
I'm not having troubles with flashing or booting Twrp via fastboot, I'm having issues with Twrp or something else that is interfering and not allowing me to flash any ROM.
I've tried every TWRP I've found, 3.2.1, 3.3.0, 3.3.1, all of them gives me the ERROR 7 when I try to flash a ROM.
Looked online for the ERROR 7 solution, tried erasing the assert line from updater-script file and still no help.
The times that I flashed the ROMs via fastboot or adb the phone stays in bootloop or just freezes at the boot screen.
I don't have a backup stock file.
Click to expand...
Click to collapse
It may be a hardware issue or currupted partition, Flash stock firmware using fastboot, erase data and cache using these fastboot commands "fastboot erase userdata and fastboot erase cache"
pradeeppk said:
It may be a hardware issue or currupted partition, Flash stock firmware using fastboot, erase data and cache using these fastboot commands "fastboot erase userdata and fastboot erase cache"
Click to expand...
Click to collapse
Don't think its hardware because the only thing I did was flash lineage 16.0 (worked) and then try to go back to stock ROM. Do you have the link for stock firmware, please? I tried one but didn't work as well (SANDERS_NPSS26.116-64-2).
voliveira92 said:
Don't think its hardware because the only thing I did was flash lineage 16.0 (worked) and then try to go back to stock ROM. Do you have the link for stock firmware, please? I tried one but didn't work as well (SANDERS_NPSS26.116-64-2).
Click to expand...
Click to collapse
Those are the lines that came with error. The phone went on a bootloop after clearing the cache and userdata.
platform-tools>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (504333 KB)...
OKAY [ 11.743s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.804s
platform-tools>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (495479 KB)...
OKAY [ 11.539s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 15.942s
platform-tools>fastboot flash system system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system' (65436 KB)...
OKAY [ 1.528s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.552s
platform-tools>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (335882 KB)...
OKAY [ 7.802s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.841s
Try to fix file system using "repair or change file system" menu in twrp and set them all default. Then format data, cache and system and flash a new rom.
Here is the link to g5splus firmwares https://firmware.center/firmware/
pradeeppk said:
Try to fix file system using "repair or change file system" menu in twrp and set them all default. Then format data, cache and system and flash a new rom.
Here is the link to g5splus firmwares https://firmware.center/firmware/
Click to expand...
Click to collapse
Ok, so I repaired system file, formated data, cache and system and tried to flash from TWRP and fastboot.
On TWRP I got the same ERROR 7 as always (tried Pixel Experience and Havoc OS, as well stock firmware Sanders_NPS26.1):
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Tried again editing the assert line and the same ERROR 7 anyway.
And via fastboot (stock firmware) I got this and the phone went on bootloop after rebooting:
fastboot oem fb_mode_set
...
OKAY [ 0.004s]
finished. total time: 0.004s
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
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.073s
fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.124s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.704s]
finished. total time: 0.828s
fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.109s]
finished. total time: 0.163s
fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.419s]
finished. total time: 0.816s
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.496s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.511s]
finished. total time: 1.007s
fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.385s]
writing 'dsp'...
OKAY [ 0.286s]
finished. total time: 0.670s
fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (327830 KB)...
OKAY [ 7.627s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.669s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (524260 KB)...
OKAY [ 12.189s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.260s
fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (522314 KB)...
OKAY [ 12.161s]
writing 'system'...
OKAY [ 6.230s]
finished. total time: 18.391s
fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (522269 KB)...
OKAY [ 12.161s]
writing 'system'...
OKAY [ 7.196s]
finished. total time: 19.356s
fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (524204 KB)...
OKAY [ 12.207s]
writing 'system'...
OKAY [ 6.143s]
finished. total time: 18.349s
fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (524139 KB)...
OKAY [ 12.211s]
writing 'system'...
OKAY [ 6.929s]
finished. total time: 19.141s
fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (435100 KB)...
OKAY [ 10.111s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.502s
fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (75360 KB)...
OKAY [ 1.758s]
writing 'modem'...
OKAY [ 1.088s]
finished. total time: 2.846s
fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (2452 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 0.118s]
finished. total time: 0.178s
fastboot erase cache
erasing 'cache'...
OKAY [ 0.018s]
finished. total time: 0.018s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.334s]
finished. total time: 0.334s
fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
fastboot oem fb_mode_clear
...
OKAY [ 0.118s]
finished. total time: 0.118s
fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.131s]
finished. total time: 0.185s
I have the option of switching the system file to another format on TWRP (EXT2, EXT3, EXT4, FAT, exFAT, F2Fs), could any of those help?
voliveira92 said:
fastboot erase customize
fastboot erase clogo
Click to expand...
Click to collapse
Where did you get this firmware from ?
From what I used to flash, the was nothing like customise or clogo.
Try this stock : https://rsdsecure-cloud.motorola.co...900158&Signature=8E+n+/9YjxFXHGokrKaycy1StXI=
And this script :
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
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
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
D302Thakur said:
Where did you get this firmware from ?
From what I used to flash, the was nothing like customise or clogo.
Try this stock : https://rsdsecure-cloud.motorola.co...900158&Signature=8E+n+/9YjxFXHGokrKaycy1StXI=
And this script :
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
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
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Ok, so I tried the stock you recomended and used the codes you provided.
Here's what I got. Frozen at boot screen. Tried from -fastboot- and -minimal adb and fastboot-.
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.000s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.002s]
finished. total time: 0.002s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.002s]
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.057s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.519s]
finished. total time: 0.641s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71941 KB)...
OKAY [ 1.678s]
writing 'modem'...
OKAY [ 0.980s]
finished. total time: 2.658s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3024 KB)...
OKAY [ 0.071s]
writing 'fsg'...
OKAY [ 0.120s]
finished. total time: 0.191s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.035s]
finished. total time: 0.035s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.035s]
finished. total time: 0.035s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.382s]
writing 'dsp'...
OKAY [ 0.254s]
finished. total time: 0.637s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.051s]
writing 'logo'...
OKAY [ 0.097s]
finished. total time: 0.150s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.396s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.357s]
finished. total time: 0.754s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.490s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.452s]
finished. total time: 0.942s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.097s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.099s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (249863 KB)...
OKAY [ 5.809s]
writing 'system'...
OKAY [ 2.935s]
finished. total time: 8.744s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (260323 KB)...
OKAY [ 6.091s]
writing 'system'...
OKAY [ 3.729s]
finished. total time: 9.820s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.105s]
writing 'system'...
OKAY [ 3.309s]
finished. total time: 9.414s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 6.098s]
writing 'system'...
OKAY [ 3.106s]
finished. total time: 9.203s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.097s]
writing 'system'...
OKAY [ 2.928s]
finished. total time: 9.025s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.104s]
writing 'system'...
OKAY [ 2.986s]
finished. total time: 9.090s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (255675 KB)...
OKAY [ 5.971s]
writing 'system'...
OKAY [ 3.487s]
finished. total time: 9.459s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (242629 KB)...
OKAY [ 5.647s]
writing 'system'...
OKAY [ 2.830s]
finished. total time: 8.478s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (239745 KB)...
OKAY [ 5.575s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 6.124s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.10
target reported max download size of 534773760 bytes
sending 'system' (65436 KB)...
OKAY [ 1.518s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.520s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (135426 KB)...
OKAY [ 3.150s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.153s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.009s]
finished. total time: 0.009s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.124s]
finished. total time: 0.124s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.001s]
finished. total time: 0.001s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.002s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot
rebooting...
finished. total time: 0.001s
voliveira92 said:
fastboot flash system system.img_sparsechunk.0
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.9
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.10
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
fastboot flash oem oem.img
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
I guess, there's some problem with your system partition.
Like you said, even in TWRP system was failing to flash and here also.
Further, oem also failed here.
Rest of the output is fine and expected.
To conclude anything further, may I know your region ? Like India, Brazil,...
Or better if you know the device model, like xt1804, xt1802, etc...
D302Thakur said:
I guess, there's some problem with your system partition.
Like you said, even in TWRP system was failing to flash and here also.
Further, oem also failed here.
Rest of the output is fine and expected.
To conclude anything further, may I know your region ? Like India, Brazil,...
Or better if you know the device model, like xt1804, xt1802, etc...
Click to expand...
Click to collapse
Brazil, model XT1802
voliveira92 said:
Brazil, model XT1802
Click to expand...
Click to collapse
Can anyone please help me with this? I'm almost giving up on this device but I can't accept that there's nothing else I can try.
Hello everyone, I own a Moto g6 xt1925-4 and I decided to root the device. First thing I unlocked the bootloader, it worked (with bad key logo). Second, I flashed TWRP, which I downloaded the IMG of from the official thread here on XDA. Third, I flashed the no-verity modified image: now I think I made a mistake because I flashed a OPS image which I should suppose is Oreo but the device was already updated to PIE.
Then the troubles started. I couldn't flash magisk, so I tricked too much on the MOUNT page on TWRP, perhaps I have mounted system or storage, then I also pulled out the USB cable without safe ejection and in the end, when I rebooted the phone in Bootloader mode and pushed Start, nothing happened at all.
I thought then: I have to restore to stock. I followed the procedure on the thread here on XDA, and I should say, something happened, but strange.
Now the phone boots up, but goes in a kind of a strange bootloop, because sometimes it says the "hello moto", sometimes not, sometimes it even starts the initial configuration, but the screen flashes on and off at random, and a few centimeters of the bottom screen are black. This happened also on TWRP recovery, the bottom part of the screen appeared cut by 2/3 centimeters.
Now I surely made mistakes, but I can't get what's wrong, and most of all this in going to get me crazy. I'm near to desperation, so I pray you to help me, please!
This is the result of the stock firmware flash I tried twice. I can see a couple of "failed" and "no such files"
Microsoft Windows XP [Versione 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Programmi\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.020s]
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.090s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.250s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.461s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71577 KB)...
OKAY [ 10.255s]
writing 'modem'...
OKAY [ 0.571s]
finished. total time: 10.836s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (6780 KB)...
OKAY [ 2.464s]
writing 'fsg'...
OKAY [ 0.100s]
finished. total time: 2.564s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin': No such file or directory
C:\Programmi\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin': No such file or directory
C:\Programmi\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 3.515s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.300s]
finished. total time: 3.815s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.0
target reported max download size of 534773760 bytes
sending 'system' (259756 KB)...
OKAY [ 65.294s]
writing 'system'...
OKAY [ 2.293s]
finished. total time: 67.587s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.1
target reported max download size of 534773760 bytes
sending 'system' (253441 KB)...
OKAY [ 27.379s]
writing 'system'...
OKAY [ 1.763s]
finished. total time: 29.142s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.2
target reported max download size of 534773760 bytes
sending 'system' (254074 KB)...
OKAY [ 32.957s]
writing 'system'...
OKAY [ 1.773s]
finished. total time: 34.730s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.3
target reported max download size of 534773760 bytes
sending 'system' (260545 KB)...
OKAY [ 44.554s]
writing 'system'...
OKAY [ 1.803s]
finished. total time: 46.357s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.4
target reported max download size of 534773760 bytes
sending 'system' (259733 KB)...
OKAY [ 28.171s]
writing 'system'...
OKAY [ 1.813s]
finished. total time: 29.983s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.5
target reported max download size of 534773760 bytes
sending 'system' (246724 KB)...
OKAY [ 36.092s]
writing 'system'...
OKAY [ 1.682s]
finished. total time: 37.794s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.6
target reported max download size of 534773760 bytes
sending 'system' (246141 KB)...
OKAY [ 24.425s]
writing 'system'...
OKAY [ 1.702s]
finished. total time: 26.148s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.7
target reported max download size of 534773760 bytes
sending 'system' (262029 KB)...
OKAY [ 26.448s]
writing 'system'...
OKAY [ 1.933s]
finished. total time: 28.391s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.8
target reported max download size of 534773760 bytes
sending 'system' (262001 KB)...
OKAY [ 26.198s]
writing 'system'...
OKAY [ 1.803s]
finished. total time: 28.010s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.9
target reported max download size of 534773760 bytes
sending 'system' (25072 KB)...
OKAY [ 2.654s]
writing 'system'...
OKAY [ 0.170s]
finished. total time: 2.824s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash vendor vendor.img_sparsechu
nk.0
target reported max download size of 534773760 bytes
sending 'vendor' (260148 KB)...
OKAY [ 35.711s]
writing 'vendor'...
OKAY [ 2.023s]
finished. total time: 37.744s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash vendor vendor.img_sparsechu
nk.1
target reported max download size of 534773760 bytes
sending 'vendor' (178315 KB)...
OKAY [ 16.644s]
writing 'vendor'...
OKAY [ 1.412s]
finished. total time: 18.056s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.080s]
finished. total time: 0.080s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.010s]
finished. total time: 0.010s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2182 KB)...
OKAY [ 0.681s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.751s
C:\Programmi\Minimal ADB and Fastboot>fastboot reboot
EDIT:
Good news, at least for me. I solved by flashing the PIE STOCK ROM, despite I liked OREO the most, I find this PIE slower and less smooth but anyways, that's it, I have my phone back.
But still..... I can't get the root, but that's fine, I'm still enjoying the feel of victory... maybe I'll try, some day...