Database Users

[Unresolved] [Bricked?] [Fastboot] Factory images won't flash

Hey all,
A little background: I was a little late to the Lollipop scene, and seeing as my phone wasn't getting an update anytime soon, I thought I'd crack out my ol' Nexus 7 2012 Wifi-edition. This thing was running an old version of Paranoid Android and was pretty slow and unreliable, I'd assumed I'd flashed a bad kernel or made some bad configurations or something. I very promptly downloaded the Lollipop factory image, fired up fastboot and wiped the device and attempted to flash the image.
It didn't work. I then assumed the image was bad, so I figured, as I had done in the past for KitKat, I'd download an older image and just accept the OTA. Once again the image refused to flash. It got stuck at the bootloader every time, but stubborn as I am, I tried yet an older image. flashing different versions of Jellybean, I discovered that my Nexus 7 wouldn't take any bootloader version higher than 4.18, and that if the bootloader did flash, the system.img would fail.
The procedure for flashing went as follows:
Download and extract nakasi gzipped tar images
cd into the folder containing an image
Run ./flash-all.sh, manually erase partitions and flash the zip, or extract the zip archive and manually erase partitions and flash the contained images
I noticed that the script wasn't working at all, so I took to manually flashing each image myself, and discovered that the issue usually occured with system.img and bootloader-group-x.xx.img
Looking for a solution to my problem. I'm running out of images to flash, and I have no way of transferring files to the tablet. I tried loading CWM so I could flash an unofficial image to get the thing booting, but I received errors when I tried to mount the USB storage.
Any and all help would be appreciated, I'm thinking this is a flash memory issue (i.e. one or more partitions is corrupt or formatted incorrectly), and I don't have the slightest clue how to fix it. Thanks!
EDIT: Errors and the actual process output are probably relevant.
Note that I run an Arch Linux box, but also tried the equivalent procedure using my other Windows 8.1 machine, to no avail.
Using the 4.3 jwr66y image as an example, this was the full manual process:
Code:
nakasi-jwr66y $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.978s]
finished. total time: 0.978s
nakasi-jwr66y $ fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.787s]
finished. total time: 0.787s
nakasi-jwr66y $ fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.526s]
finished. total time: 2.526s
nakasi-jwr66y $ fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.027s]
finished. total time: 0.027s
nakasi-jwr66y $ fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.423s
Using the 4.1.2 image as an example, this was the full manual process:
Code:
nakasi-jzo54k $ fastboot erase boot
erasing 'boot'...
OKAY [ 1.125s]
finished. total time: 1.125s
nakasi-jzo54k $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.633s]
finished. total time: 0.633s
nakasi-jzo54k $ fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.601s]
finished. total time: 0.601s
nakasi-jzo54k $ fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.526s]
finished. total time: 2.526s
nakasi-jzo54k $ fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.027s]
finished. total time: 0.027s
nakasi-jzo54k $ fastboot flash bootloader bootloader-grouper-3.41.img
sending 'bootloader' (2092 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 9.212s]
finished. total time: 9.498s
nakasi-jzo54k $ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.808s
nakasi-jzo54k $ fastboot flash boot boot.img
sending 'boot' (4896 KB)...
OKAY [ 0.643s]
writing 'boot'...
OKAY [ 1.967s]
finished. total time: 2.610s
nakasi-jzo54k $ fastboot flash recovery recovery.img
sending 'recovery' (5240 KB)...
OKAY [ 0.699s]
writing 'recovery'...
OKAY [ 1.120s]
finished. total time: 1.819s
nakasi-jzo54k $ fastboot flash system system.img
erasing 'system'...
OKAY [ 2.608s]
sending 'system' (446268 KB)...
OKAY [ 58.787s]
writing 'system'...
FAILED (remote: (Unknown error code))
finished. total time: 63.412s
Flashing the 4.1.2 image produced another strange error where the tablet would continually output (in a loop) the phrase "Neither USP nor CAC partitions found" after the flash failed.
EDIT: I managed to successfully flash bootloader 4.23 from the KRT16S factory image, but I still can't get the system.img from any KitKat or Lollipop factory image to flash. I keep getting "FileWriteFailed" error messages. Anyone know how I can fix this?

Bumping because I'd like to fix my tablet at some point :$

Narwhal73 said:
Bumping because I'd like to fix my tablet at some point :$
Click to expand...
Click to collapse
I'm on the same situation as you, but mine initially started after trying to install an f2fs lollipop ROM. I also think it's because of some sort of partition screwup.
My tablet won't let me install a bootloader, always saying invalid state. Luckily mine seems to still work on 4.23.
It let's me install the boot and recovery images every time,but it always fails at the system image.
What also happens when trying to flash the system image is that it will sit saying sending image for ages. Then eventually it fails with the errors of either too many links or unknown error.
Only once has it actually sent the image using jwr66v and got the tablet booting again, but it wouldn't update and kept giving errors, so I'm trying again to see if I can manually update to latest.
I was told to try using Linux instead of windows, which I'll attempt this weekend. I'll let you know if it works, but am not too optimistic.
Sent from my LG-D802 using XDA Premium HD app

Got mine to work again, by just trying once again the terminal fastboot erase of all the partitions and then flash bootloader, reboot bootloader, then flash recovery, flash boot, flash system and finally flash userdata.
This is the same thing that wasn't working earlier but took on first try again after a break. So unfortunately I can't say I fixed it in a specific way, it just seems to be a case of persistence paid off.
Flashed the latest Google lollipop image.
Try to do the manual erase and flash again. Maybe it will take eventually like mine did.
Hope you come right.
Sent from my LG-D802 using XDA Premium HD app

I had issues flashing factory images to my N7 yesterday too. At first I did the flash all script. It hung just like yours did at flashing the system image. I did it again with trying to flash everything manually and it still wouldn't work. Finally, I rebooted into fastboot and opened a new terminal window and everything worked as it should.

Persistence doesn't work as a solution for me. Trying with multiple machines, many different terminal instances, and several attempts with each has lead to no results. I'm thinking that for some reason the partition scheme might be broken, though of course it could be something else . Anyone know how I can go about diagnosing the issue properly, or repartitioning this thing? I don't even care about the Google images anymore, as long as I can get a functional OS back on it.
Currently the Nexus 7 is sitting with bootloader version 4.18, and no other functional images flashed to it. I can't seem to get the official bootloader version 4.23
to flash.
(Sorry for letting the thread die, I was away on vacation)

Narwhal73 said:
Persistence doesn't work as a solution for me. Trying with multiple machines, many different terminal instances, and several attempts with each has lead to no results. I'm thinking that for some reason the partition scheme might be broken, though of course it could be something else . Anyone know how I can go about diagnosing the issue properly, or repartitioning this thing? I don't even care about the Google images anymore, as long as I can get a functional OS back on it.
Currently the Nexus 7 is sitting with bootloader version 4.18, and no other functional images flashed to it. I can't seem to get the official bootloader version 4.23
to flash.
(Sorry for letting the thread die, I was away on vacation)
Click to expand...
Click to collapse
Check the md5sum of your "Official" 4.23 bootloader if it isn't THIS:
df53028033c9eccf4fe5ba7bc198ce24
Then it is Wrong...
http://forum.xda-developers.com/showthread.php?t=2573015
http://forum.xda-developers.com/nexus-7/general/guide-nexus-7-2012-factory-image-root-t2937833
Those two post will explain in further details.
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??

sponix2ipfw said:
Check the md5sum of your "Official" 4.23 bootloader if it isn't THIS:
df53028033c9eccf4fe5ba7bc198ce24
Then it is Wrong...
http://forum.xda-developers.com/showthread.php?t=2573015
http://forum.xda-developers.com/nexus-7/general/guide-nexus-7-2012-factory-image-root-t2937833
Those two post will explain in further details.
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??
Click to expand...
Click to collapse
I'm not sure what F2FS is, so I'm pretty sure I wasn't trying to do that. I'm just trying to get an actual bootable OS back onto the tablet. Stock Lollipop is preferable to anything else right now and I'll worry about customising it again at a later date...
I was unaware that Google/ASUS fudged up the bootloader images for the last few major releases (that would explain my inability to flash 4.23 to the device), so I'll try the instructions in the threads you've pointed me to when I get a chance. Thanks!
I'll report back with any successes or failures at some point next week; I have exams to study for in the meantime...

Hi dude, you can Try to install Firmware stock 4.2.2 and after upgrade it using ota. My friend resolved same problem in this way.
Inviato dal mio Nexus 7 utilizzando Tapatalk

Okay, so I found time to try to fix this thing tonight. The bootloader from KRT16S flashed fine, so my N7 is once again running bootloader version 4.23. The issue with flashing the system.img persists however.
The error I get is:
Code:
writing 'system'...
FAILED (remote: (FileWriteFailed))
finished. total time: 93.175s
What is so frustrating about this is that a "write failed" error message isn't very descriptive. A write could fail for any number of reasons. Is there a way I can enable more verbose error output in fastboot?
The only thing that I can think of pinning this on is an improperly sized partition. Unless there is something someone else can think of, could someone point me to where I can get the stock partition layout, and how I can repartition the device?
EDIT: not sure of the relevance, but I have just noticed that as soon as fastboot begins sending the image for writing, the bootloader on the device freezes up. Like I can't scroll through the options, not see any live text on the screen. Same goes for userdata.img.
EDIT: Here's all the bootloader variables (S/N changed in this post for privacy), can someone make sense of the partitions? What's with the hexadecimal?:
Code:
$ fastboot getvar all
(bootloader) version-bootloader: 4.23
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: no
(bootloader) partition-size:bootloader: 0x0000000000600000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000727f00000
(bootloader) partition-type:userdata: ext4

sponix2ipfw said:
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??
Click to expand...
Click to collapse
Bumping this again because I'm still having issues, anyone have any ideas about how I could go about getting my N7 back to working stock? It's recognisable by Fastboot, and I can get a working ADB connection through PhilZ recovery, but apart from that I can't do anything. It's a nice tablet and I'd like to get it back to a usable state.

Moto Downgrade Utility

** View the making of moto downgrade tool at https://youtu.be/xaJKx9Vqdjc ***
Please like and subscribe to my youtube channel to encourage me to create more tools for the members of xda ! I really really appreciate it
Moto Downgrade Tool is a tool that I have quickly created to SAFELY downgrade android marshmallow to android lollipop on the XT1541 model.
You need Python 3.5 installed to run this program !!
make sure your phone is plugged into your pc and in fastboot mode when you start the tool.
INSTALL MOTO DRIVERS BEFORE USING THE TOOL !!!!
ADB and Fastboot is included in the downgrade tool.
Please comment if you have any issues ! This tool has been tested a few times by myself on my phone. , so it is guaranteed to be able to function correctly !
XDA:DevDB Information
Moto Downgrade Utility, Tool/Utility for the Moto G 2015
Contributors
therealduff1
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2016-03-02
Last Updated 2016-03-02

Keep going on Master!
Sorry for the off topic questions
I'm searching a Rom with multi window feature + floating windows apps like last Sammy's roms for XT1541 do you know any?
Currently using last Resurrection Remix from Vatsal that have multi window but not floating windows
One off topic more:
I have XT1541 European version obtained in Spain but I'm using it in Argentina and my mobile connection (4g) its very slow
I have to change the modem or something else?
Thanks a lot mate!
Enviado desde mi XT1541 mediante Tapatalk

fedez said:
Keep going on Master!
Sorry for the off topic questions
I'm searching a Rom with multi window feature + floating windows apps like last Sammy's roms for XT1541 do you know any?
Currently using last Resurrection Remix from Vatsal that have multi window but not floating windows
One off topic more:
I have XT1541 European version obtained in Spain but I'm using it in Argentina and my mobile connection (4g) its very slow
I have to change the modem or something else?
Thanks a lot mate!
Enviado desde mi XT1541 mediante Tapatalk
Click to expand...
Click to collapse
No need to be sorry for off topic questions !
About the rom , i am not to sure about finding a rom with floating windows , but i would like that aswell !
Also , about using a european device in a different location, this is probably due to different network bands. I would NOT reccomend you flash another models modem, as this could hard brick your phone .
I foyu have any other questions, dont hesitate to ask !

I want to downgrade from stock mm(not rooted) to LP, possible?

arun356y said:
I want to downgrade from stock mm(not rooted) to LP, possible?
Click to expand...
Click to collapse
Using my tool , yes ! . Remember not to accept ota tho

How are you doing the downgrade without having the bootloader unlocked???
Also, is this flashing EVERYTHING, including the bootloader and partition table, or is this just a tool to perform the "normal" downgrade of flashing a factory firmware image and skipping gpt.bin and bootloader.img?

therealduff1 said:
Using my tool , yes ! . Remember not to accept ota tho
Click to expand...
Click to collapse
not to accept ota, why? if in future I want to update then?

acejavelin said:
How are you doing the downgrade without having the bootloader unlocked???
Also, is this flashing EVERYTHING, including the bootloader and partition table, or is this just a tool to perform the "normal" downgrade of flashing a factory firmware image and skipping gpt.bin and bootloader.img?
Click to expand...
Click to collapse
This tool flashes SIGNED images, which means it does not need bootloader unlock. Also , it skips gpt.bin and bootloader.img . It is a normal downgrade, but i made this tool for people who dont want to risk bricking their phones typing the wrong command or accidentally flashing gpt.bin or bootloader.img

therealduff1 said:
This tool flashes SIGNED images, which means it does not need bootloader unlock. Also , it skips gpt.bin and bootloader.img . It is a normal downgrade, but i made this tool for people who dont want to risk bricking their phones typing the wrong command or accidentally flashing gpt.bin or bootloader.img
Click to expand...
Click to collapse
So if I use fastboot and flash a lp I just need to skip those 2 files right?

Downgrading from Rooted Stock MM
I have the XT1541 rooted on stock MM, can i downgrade to stock lollipop without bricking the phone ?
I also flashed the squid kernel r15b (latest)

BurningKoala said:
So if I use fastboot and flash a lp I just need to skip those 2 files right?
Click to expand...
Click to collapse
No need to use fastboot if you trust my programming . but yes , skip gpt.bin and bootloader.IMG and you will be fine my program automatically does that

Hello does my xt1541 need to be unlocked and rooted for this tool to work and downgrade from mm to lollipop?

Agiofws said:
Hello does my xt1541 need to be unlocked and rooted for this tool to work and downgrade from mm to lollipop?
Click to expand...
Click to collapse
No root needed !

Luigi_Manga said:
Ok then, I'll try tonight, does this work whit every rom despite the different number of sparsechunks?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Yes it should work perfectly

Didn't work, still on the crappy 6.0
Partition table has been skipped!
Bootloader has been skipped!
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.040s]
writing 'logo'...
OKAY [ 0.071s]
finished. total time: 0.114s
boot logo has been flashed
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.649s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.183s
boot.img has been flashed
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.651s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.616s
Stock lollipop recovery has now been flashed
target reported max download size of 268435456 bytes
sending 'system' (262140 KB)...
OKAY [ 10.071s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.515s
System part 1 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (262143 KB)...
OKAY [ 10.079s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.124s
System part 2 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (232632 KB)...
OKAY [ 8.988s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.060s
System part 3 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (233355 KB)...
OKAY [ 8.971s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.014s
System part 4 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (257122 KB)...
OKAY [ 9.884s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.927s
System part 5 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (236089 KB)...
OKAY [ 9.090s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.124s
System part 7 has been flashed
system partitions successfully flashed
target reported max download size of 268435456 bytes
sending 'modem' (36940 KB)...
OKAY [ 1.423s]
writing 'modem'...
OKAY [ 0.994s]
finished. total time: 2.423s
Flashed Mobile Data Connection Chip Data
erasing 'modemst1'...
OKAY [ 0.019s]
finished. total time: 0.021s
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
Old data erased
target reported max download size of 268435456 bytes
sending 'fsg' (2031 KB)...
OKAY [ 0.083s]
writing 'fsg'...
OKAY [ 0.083s]
finished. total time: 0.169s
Flashed FSG
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.021s
cache erased
erasing 'userdata'...
OKAY [ 0.199s]
finished. total time: 0.201s
userdata partition formatted
rebooting...
finished. total time: 0.006s
flash finished
***PLEASE READ BELOW***
YOU MUST NOT ACCEPT ANY OTA UPDATES ON YOUR PHONE WHILE IT IS RUNNING LOLLIPOP
OR YOU ARE RISKING A HARD BRICK DUE TO UPGRADING THE BOOTLOADER WHICH IS AT A DI
FFERENT VERSION
THAN EXPECTED
and thats all !
enjoy lollipop again!
Press any key to continue . . .
Click to expand...
Click to collapse

Sorry for the noob question but does the bootloader have to be unlocked?

BurningKoala said:
Didn't work, still on the crappy 6.0
Click to expand...
Click to collapse
Agiofws said:
Sorry for the noob question but does the bootloader have to be unlocked?
Click to expand...
Click to collapse
Downgrade using fastboot it's not possible without unlocked bootloader, that's why I think it didn't work.

coolizard said:
Downgrade using fastboot it's not possible without unlocked bootloader, that's why I think it didn't work.
Click to expand...
Click to collapse
I flashed mine using a locked bootloader

BurningKoala said:
Didn't work, still on the crappy 6.0
Click to expand...
Click to collapse
Ok right , this is a problem with the image, not my program . Are you flashing the correct image for your phone ?

therealduff1 said:
Ok right , this is a problem with the image, not my program . Are you flashing the correct image for your phone ?
Click to expand...
Click to collapse
Yes, I flashed the xt1541 vodafone EU that was on my phone (now I'm on vodafone 6.0), did you think that it's better I flash the no brand eu version?
edit: same errors with the retail eu

How unzip this firmware?

Have some trouble to flash my HTC M9+ to stock ROM
I Have the firmware: 0PK7IMG_HIAU_ML_TUHL_M60_SENSE70_MR_HTC_Europe_2.30.401.1_Radio_1.1550V70.2501.0304_HT[W.T]_release_490382_combined_signed
It has inside 10 zip's:
zip_0
zip_1
zip_2
zip_3
zip_4
zip_5
zip_6
zip_7
zip_8
zip_9
How can unzip to get the firmware? size of the firmware is 2.3 GB
Thanks

1. If you were familiar with ubuntu , decrypt RUU.zip by means of
ruuveal [options] --device DEVICE source.zip output.zip
then using "simg2img" to create system.img
2. 7zip
https://forum.xda-developers.com/on...how-to-extract-one-m9-rom-dump-image-t3062808
3. Now, you have this tool to decrypt and extract system.img from RUU.zip.
https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928

yvtc75 said:
1. If you were familiar with ubuntu , decrypt RUU.zip by means of
ruuveal [options] --device DEVICE source.zip output.zip
then using "simg2img" to create system.img
2. 7zip
https://forum.xda-developers.com/on...how-to-extract-one-m9-rom-dump-image-t3062808
3. Now, you have this tool to decrypt and extract system.img from RUU.zip.
https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928
Click to expand...
Click to collapse
Thank you very much
I have two files now: boot.img and system.img
and then:
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (9188 KB)...
OKAY [ 1.342s]
writing 'boot'...
(bootloader) HOSD CL#821792
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.215s]
finished. total time: 3.557s
C:\adb>fastboot flash system system.img
target reported max download size of 800000000 bytes
erasing 'system'...
OKAY [ 0.140s]
sending 'system' (638680 KB)...
OKAY [ 23.213s]
writing 'system'...
(bootloader) HOSD CL#821792
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 14.336s]
finished. total time: 37.690s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.000s
the device reboot but frozen in white screen with green logo HTC
What can i do?
Thanks

cejas_99 said:
Thank you very much
I have two files now: boot.img and system.img
and then:
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (9188 KB)...
OKAY [ 1.342s]
writing 'boot'...
(bootloader) HOSD CL#821792
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.215s]
finished. total time: 3.557s
C:\adb>fastboot flash system system.img
target reported max download size of 800000000 bytes
erasing 'system'...
OKAY [ 0.140s]
sending 'system' (638680 KB)...
OKAY [ 23.213s]
writing 'system'...
(bootloader) HOSD CL#821792
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 14.336s]
finished. total time: 37.690s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.000s
the device reboot but frozen in white screen with green logo HTC
What can i do?
Thanks
Click to expand...
Click to collapse
oh~ no~ Don't mess up.
If you want to flash rom, adopt this method.
https://forum.xda-developers.com/showpost.php?p=61801034&postcount=8
https://forum.xda-developers.com/on...neral/help-flashing-stock-rom-htc-m9-t3711628
To flash this on S-On, you must have your device Relocked (on S-Off you don't need to relock) and then in fastboot mode:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
If you wanna flash dump image, use the following command.
https://forum.xda-developers.com/on...c-one-m9-stock-backup-stock-recovery-t3190453
fastboot flash system system.img

cejas_99 said:
Have some trouble to flash my HTC M9+ to stock ROM
I Have the firmware: 0PK7IMG_HIAU_ML_TUHL_M60_SENSE70_MR_HTC_Europe_2.30.401.1_Radio_1.1550V70.2501.0304_HT[W.T]_release_490382_combined_signed
It has inside 10 zip's:
zip_0
zip_1
zip_2
zip_3
zip_4
zip_5
zip_6
zip_7
zip_8
zip_9
How can unzip to get the firmware? size of the firmware is 2.3 GB
Thanks
Click to expand...
Click to collapse
You will propably get an error trying to unzip these archives. It is because it is not meant to be unzipped. Try to rename the zip file to 0PK7IMG and put it on your sd card. Alternatively, you can try to flash it via adb.

[Guide] Updating your Pixel 2 to latest factory image, no wipe

Note: This is NOT A FIX FOR SOFTBRICKED DEVICES. This is simply an easy way for someone who is rooted to easily update /system to the most recent build without erasing user data.
Please note this is not a clean factory flash - this does not flash radio or bootloader, and does not wipe /data. This works regardless of whether you have a custom kernel or unlocked bootloader.
This assumes that you already know how to use ADB and fastboot.
1. Download the latest factory image for your device from HERE.
2. Unzip the archive.
3. Open the folder it was unzipped to, and you will find an archive titled "image-[device]-[build number].zip. Copy this to your ADB/fastboot folder.
4. Connect your phone and reboot to bootloader.
5. Type:
Code:
fastboot update [name of image].zip
6. Wait for the process to finish. Phone will automatically reboot into system when complete.
Congratulations, you are now on the latest factory system image. This overwrites boot, dtbo, and breaks root, so reflash kernels and Magisk as desired. Be aware that the kernel you are flashing must match the security update you flashed.
If for whatever reason you do want to wipe /data when flashing this, use:
Code:
fastboot -w update [name of image].zip
If you want to update your radio, simply pull the radio.img from the factory zip, and while in bootloader, type:
Code:
fastboot flash radio [name of radio image].img
After you flash bootloader and radio, make sure you use
Code:
fastboot reboot bootloader
to ensure you're on the new firmware.

I'm getting the following, any advice? I definitely dont want to wipe, and suspect flashing a bootloader image will do that?
:
:\adb> fastboot update image.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: XXXXXX
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0066.00'.
Update requires 'mw8998-002.0067.00.

mjondj said:
I'm getting the following, any advice? I definitely dont want to wipe, and suspect flashing a bootloader image will do that?
:
:\adb> fastboot update image.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: XXXXXX
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0066.00'.
Update requires 'mw8998-002.0067.00.
Click to expand...
Click to collapse
Sounds like you've been without OTAs for a while.
Pull the bootloader and radio images from the .021 zip. They will be right there in the same folder as image-walleye-opm1.171019.021.zip.
Copy to fastboot folder
Code:
fastboot flash bootloader bootloader-walleye-mw8998-002.0067.00.img
fastboot reboot bootloader
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot bootloader
fastboot update image-walleye-opm1.171019.021.zip

socal87 said:
Pull the bootloader image from the .021 zip. It'll be right there in the same folder as image-walleye-opm1.171019.021.zip.
Copy to fastboot folder
Code:
fastboot flash bootloader bootloader-walleye-mw8998-002.0067.00.img
fastboot reboot bootloader
fastboot update image-walleye-opm1.171019.021.zip
Click to expand...
Click to collapse
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
flashing all those won't wipe the device?

mjondj said:
Pull the bootloader image from the .021 zip. It'll be right there in the same folder as image-walleye-opm1.171019.021.zip.
Copy to fastboot folder
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
flashing all those won't wipe the device?
Click to expand...
Click to collapse
No. Flashing without the -w flag does not wipe. Refer to bottom of first post.

socal87 said:
No. Flashing without the -w flag does not wipe. Refer to bottom of first post.
Click to expand...
Click to collapse
i appreciate the help, but now i'm soft bricked (wont go past G logo) after failing on system. i was rooted w/ magisk. i suspect thats what the problem was. is there any way to avoid a wipe at this point and get back up and running?
PS C:\adb> fastboot devices
xxx fastboot
PS C:\adb> fastboot flash bootloader boot.img
target reported max download size of 536870912 bytes
sending 'bootloader' (38652 KB)...
OKAY [ 0.913s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E20000
(bootloader) Updating: abl @0255A000 sz=00065000
OKAY [ 0.918s]
finished. total time: 1.840s
PS C:\adb> fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
PS C:\adb> fastboot flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.437s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.552s]
finished. total time: 2.000s
PS C:\adb> fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
PS C:\adb> fastboot update image.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: mw8998-002.0067.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: xxx
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (32768 KB)...
OKAY [ 0.775s]
writing 'boot'...
OKAY [ 0.002s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.252s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 14.383s
PS C:\adb>
Click to expand...
Click to collapse

mjondj said:
i appreciate the help, but now i'm soft bricked (wont go past G logo) after failing on system. i was rooted w/ magisk. i suspect thats what the problem was. is there any way to avoid a wipe at this point and get back up and running?
Click to expand...
Click to collapse
A factory reset in recovery will get it up and running again and afterwards you can reroot.

gee2012 said:
A factory reset in recovery will get it up and running again and afterwards you can reroot.
Click to expand...
Click to collapse
this doesnt really help. the whole point is to not wipe

mjondj said:
this doesnt really help. the whole point is to not wipe
Click to expand...
Click to collapse
Don`t think its possible without a wipe, but good luck anyways

gee2012 said:
Don`t think its possible without a wipe, but good luck anyways
Click to expand...
Click to collapse
the title of this thread includes the words "no wipe"

mjondj said:
the title of this thread includes the words "no wipe"
Click to expand...
Click to collapse
No wipe, extenuating cirumstances not withstanding. But I have an idea.
Boot TWRP and use ADB push to send the image.zip to /tmp. Flash using TWRP, see if that works.
Also, check out Deuce's tool here.

mjondj said:
the title of this thread includes the words "no wipe"
Click to expand...
Click to collapse
We know that, but the dude he is trying to help is soft bricked probably by following op instructions which I do t k ow why we have a other thread about anyway.

dobbs3x said:
We know that, but the dude he is trying to help is soft bricked.
Click to expand...
Click to collapse
This method is not a fix for, nor does it address prexisting issues. Everyone is responsible for their own phones. I will help as much as I can but the responsibility lies on the user to be familiar with flashing as well as what to do if something goes wrong.

socal87 said:
This method is not a fix for, nor does it address prexisting issues. Everyone is responsible for their own phones. I will help as much as I can but the responsibility lies on the user to be familiar with flashing as well as what to do if something goes wrong.
Click to expand...
Click to collapse
If you post instructions and someone bricks their phone from it then they are going to come here and post about it.
We already have threads that talk about updating and there was really no need for this one anyway.

dobbs3x said:
If you post instructions and someone bricks their phone from it then they are going to come here and post about it.
We already have threads that talk about updating and there was really no need for this one anyway.
Click to expand...
Click to collapse
My instructions didn't brick his phone. And while there are threads about updating from the factory zip without wiping, this is a manual way to update /system independently. If you feel the thread is unnecessary, let an admin know, and they will decide whether to remove it.
Or, you could simply be thankful that I'm trying to help.

Will this method work for nonrooted devices?

Phil_Chambers said:
Will this method work for nonrooted devices?
Click to expand...
Click to collapse
Yes. This is functionally similar to flashing the factory zip, except you're typing the commands yourself and omitting the -w (wipe) flag.

Issue solved by using this script to flash all the imgs to both slots. up and running in one pass like nothing happened:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

I'm getting this when I try to boot the OTA .zip.
">fastboot update walleye-ota-opm1.171019.021-bb894efa.zip
archive does not contain 'android-info.txt'
error: update package 'walleye-ota-opm1.171019.021-bb894efa.zip' has no android-info.txt"
Not sure what I'm doing wrong
Edit: I had to sideload the update. But worked like a charm

Phil_Chambers said:
I'm getting this when I try to boot the OTA .zip.
">fastboot update walleye-ota-opm1.171019.021-bb894efa.zip
archive does not contain 'android-info.txt'
error: update package 'walleye-ota-opm1.171019.021-bb894efa.zip' has no android-info.txt"
Not sure what I'm doing wrong
Edit: I had to sideload the update. But worked like a charm
Click to expand...
Click to collapse
Interesting. Did you modify the zip in any way?

bootloader yellow alert

had the bootloader unlocked and ended up giving hardbrick after an update via OTA.
I managed to recover but had the alert that the bootloader was unlocked, so I wanted to block again, then by fasstboot, I made the command: fastboot flashing lock, and apois this alert began to appear.
I'm afraid to give a factory reset and give hardbrick.
image attached
https://drive.google.com/file/d/1V_UK0iGIhDO31dETqs9t83uZ_TOHHYIJ/view?usp=sharing

What device do you have and what firmware did you use to lock your device with? I'd check your ADB folder and make sure you've extracted the correct firmware. Also, that should give you an opportunity to delete any old stock ROMs - updating via OTA after flashing an old stock ROM runs a risk of hard bricking.
When you're locking your device bootloader, your device will be wiped anyway.

echo92 said:
What device do you have and what firmware did you use to lock your device with? I'd check your ADB folder and make sure you've extracted the correct firmware. Also, that should give you an opportunity to delete any old stock ROMs - updating via OTA after flashing an old stock ROM runs a risk of hard bricking.
When you're locking your device bootloader, your device will be wiped anyway.
Click to expand...
Click to collapse
I'm going to put the prints here of the device and the folder that I used to pass the mobile;
one detail that I realized is that the rom that step is at ATHENE_NPJS25.93-14-18, but on the device shows ATHENE_NPJS25.93-14-4.
https://drive.google.com/file/d/1ivZZP275zHBteiykw5hgF2elSkatCAOs/view?usp=sharing
https://drive.google.com/file/d/1znezKwp4esAJ6Q1rJFoeJtg-gmhZjAXy/view?usp=sharing
the rom was supposed to be the April 2018 patch but appears in March 2017;
I really wanted to reset the factory; but I'm afraid to brick it again

luis dambrowski said:
I'm going to put the prints here of the device and the folder that I used to pass the mobile;
one detail that I realized is that the rom that step is at ATHENE_NPJS25.93-14-18, but on the device shows ATHENE_NPJS25.93-14-4.
https://drive.google.com/file/d/1ivZZP275zHBteiykw5hgF2elSkatCAOs/view?usp=sharing
https://drive.google.com/file/d/1znezKwp4esAJ6Q1rJFoeJtg-gmhZjAXy/view?usp=sharing
the rom was supposed to be the April 2018 patch but appears in March 2017;
Click to expand...
Click to collapse
Hmm, you have the March 2017 stock ROM but the Feb/April 2018 baseband. I wonder if you've got a firmware mismatch in your ADB folder?
I'd delete all the stock ROM files from your ADB folder (except the ADB and fastboot files and your flashing scripts), then extract a fresh copy of the NPJS25.93-14-18 firmware, then copy the extracted files to your ADB folder (don't extract directly to the ADB folder if your ADB folder is on C drive, sometimes UAC can block the extraction. Extract then copy to the C drive). That way, you can be sure the firmware you're flashing is not mixed up (despite the same timestamps, have you verified the md5 checksums of the extracted files match the md5 checksums in the flashfile.xml or servicefile.xml? You can use a program like WinMD5Free to check).
When you recovered from the hard brick, did you flash a working GPT and bootloader before you attempted to lock your device?
What flashing commands are you using and what are the outputs? I'd suggest trying to flash the stock ROM again, provided you've cleaned out your ADB folder as suggested above.
Can you also post your getvar all info here please?
1)Boot your device to the bootloader, connect your device to your computer via USB.
2)Open an ADB terminal on your computer. Type 'fastboot getvar all' without quotes in the terminal. Press Enter.
3)Please post or paste the getvar all output in a text file and upload to this thread, or paste the output here. You may wish to omit your IMEI. This should give us an idea of your device health.

echo92 said:
Hmm, you have the March 2017 stock ROM but the Feb/April 2018 baseband. I wonder if you've got a firmware mismatch in your ADB folder?
I'd delete all the stock ROM files from your ADB folder (except the ADB and fastboot files and your flashing scripts), then extract a fresh copy of the NPJS25.93-14-18 firmware, then copy the extracted files to your ADB folder (don't extract directly to the ADB folder if your ADB folder is on C drive, sometimes UAC can block the extraction. Extract then copy to the C drive). That way, you can be sure the firmware you're flashing is not mixed up (despite the same timestamps, have you verified the md5 checksums of the extracted files match the md5 checksums in the flashfile.xml or servicefile.xml? You can use a program like WinMD5Free to check).
When you recovered from the hard brick, did you flash a working GPT and bootloader before you attempted to lock your device?
What flashing commands are you using and what are the outputs? I'd suggest trying to flash the stock ROM again, provided you've cleaned out your ADB folder as suggested above.
Can you also post your getvar all info here please?
1)Boot your device to the bootloader, connect your device to your computer via USB.
2)Open an ADB terminal on your computer. Type 'fastboot getvar all' without quotes in the terminal. Press Enter.
3)Please post or paste the getvar all output in a text file and upload to this thread, or paste the output here. You may wish to omit your IMEI. This should give us an idea of your device health.
Click to expand...
Click to collapse
about having incompatibility, I do not know what to do, what I did was download the rom that was supposed to be the april of 2018 and add the fastboot files and the .bat OEM lock and OEM Flash files, and run the OEM lock.bat
about the procedure of extracting the files, I believe that I have nothing mixed, I just do not understand how it does not load the right version, but I can do it if I think it's the problem

luis dambrowski said:
about having incompatibility, I do not know what to do, what I did was download the rom that was supposed to be the april of 2018 and add the fastboot files and the .bat OEM lock and OEM Flash files, and run the OEM lock.bat
about the procedure of extracting the files, I believe that I have nothing mixed, I just do not understand how it does not load the right version, but I can do it if I think it's the problem
Click to expand...
Click to collapse
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go... never mind, I had a look at my ADB folder and the same is for me
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Edit 2: can you repeat the flash without the locking commands please (the two initial OEM lock commands and the final OEM lock command)

echo92 said:
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go...
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Click to expand...
Click to collapse
a piece of the log
"
D:\Downloads\Nova pasta (2)\teste>fastboot oem lock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Not in unlocked state
OKAY [ 0.174s]
finished. total time: 0.175s
D:\Downloads\Nova pasta (2)\teste>fastboot oem lock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Not in unlocked state
OKAY [ 0.176s]
finished. total time: 0.178s
D:\Downloads\Nova pasta (2)\teste>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.137s]
finished. total time: 0.146s
D:\Downloads\Nova pasta (2)\teste>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.128s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) flash permission denied
(bootloader) will fail: flash:cmnlib
FAILED (remote failure)
finished. total time: 0.329s
D:\Downloads\Nova pasta (2)\teste>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.078s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.095s
D:\Downloads\Nova pasta (2)\teste>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 [ 1.176s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.194s
D:\Downloads\Nova pasta (2)\teste>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 1.241s]
writing 'recovery'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.254s
D:\Downloads\Nova pasta (2)\teste>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.540s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.553s
D:\Downloads\Nova pasta (2)\teste>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 3.140s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.149s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 16.071s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.079s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250846 KB)...
......
"

echo92 said:
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go...
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Edit 2: can you repeat the flash without the locking commands please (the two initial OEM lock commands and the final OEM lock command)
Click to expand...
Click to collapse
I will do now,
D:\Downloads\Nova pasta (2)\teste>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.067s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.137s]
finished. total time: 0.209s
D:\Downloads\Nova pasta (2)\teste>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) flash permission denied
(bootloader) will fail: flash:cmnlib
FAILED (remote failure)
finished. total time: 0.368s
D:\Downloads\Nova pasta (2)\teste>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.105s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.120s
D:\Downloads\Nova pasta (2)\teste>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.738s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.755s
D:\Downloads\Nova pasta (2)\teste>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.707s]
writing 'recovery'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.723s
D:\Downloads\Nova pasta (2)\teste>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.696s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.710s
D:\Downloads\Nova pasta (2)\teste>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 4.547s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.555s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...

luis dambrowski said:
I will do now,
.
Click to expand...
Click to collapse
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?

echo92 said:
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
Click to expand...
Click to collapse
I have already done the process with another cable and another port and using the commands manually, without positive results.
exactly was using the blankflash, then it was stuck on the screen with the "start" in the bootloader, after this tried to flash several roms and without result, nothing worked.
Yes I tried to make GPT / bootloader flash, (gpt and boot), but it did not work.
So I downloaded that rom that I sent the print with the adb files that should be April 2018, and the phone revived, but with the red bootlader alert unlocked, and so I was using it without problems. but I wanted to remove the alert, and tried to block the bootloader, I used the command: fastboot flashing lock, and asked to flash again from a rom, but at the moment I did not have the files and just rebooted.
So I got that yellow alert, everything works normally, but I wanted to fix this problem, so I can make updates via OTA in the future.
Sorry for the bad English.

echo92 said:
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
Click to expand...
Click to collapse
and if I do a blankflash again now and do the rom flash, would it work?

luis dambrowski said:
I have already done the process with another cable and another port and using the commands manually, without positive results.
exactly was using the blankflash, then it was stuck on the screen with the "start" in the bootloader, after this tried to flash several roms and without result, nothing worked.
Yes I tried to make GPT / bootloader flash, (gpt and boot), but it did not work.
So I downloaded that rom that I sent the print with the adb files that should be April 2018, and the phone revived, but with the red bootlader alert unlocked, and so I was using it without problems. but I wanted to remove the alert, and tried to block the bootloader, I used the command: fastboot flashing lock, and asked to flash again from a rom, but at the moment I did not have the files and just rebooted.
So I got that yellow alert, everything works normally, but I wanted to fix this problem, so I can make updates via OTA in the future.
Sorry for the bad English.
Click to expand...
Click to collapse
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)

echo92 said:
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
Click to expand...
Click to collapse
When I did the GPT / bootloader flash (gpt and boot) process, there was apparently no change.
do you suggest doing the flash with that (bootloader.img and gpt.bin) now? to remove this alert?
in fact this alert does not bother me, but I intend to remove it for future upgrade via OTA.
finally I will try to redo the process with ADB v1.4.3.

echo92 said:
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
Click to expand...
Click to collapse
I did all the procedures, separated and together, with no results.
I made a "Format Factory" for the recovery and did the rom flash again also did not work.
it is in the same way.
* should i try to update via OTA

luis dambrowski said:
I did all the procedures, separated and together, with no results.
I made a "Format Factory" for the recovery and did the rom flash again also did not work.
it is in the same way.
* should i try to update via OTA
Click to expand...
Click to collapse
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.

echo92 said:
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
Click to expand...
Click to collapse
ainda esta no firmware de março de 2017!
Tive uma ideia de desbloquear o bootloader e instalar o TWRP e colocar uma custom rom. No entanto, o código de desbloqueio não pode ser encontrado no site da motorola, mas sim o desbloqueio do bootloader.
Pois bem, o probloma aqui é o bootloader !!
Estou sem ideias de como prosseguir.
Sera que quando sair de novo update, (talvez algum) de certo o processo?

echo92 said:
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
Click to expand...
Click to collapse
good news!!! solved problem.
What did I do:
I used the command: fastboot flashing unlock
then he asked to repeat the command and then unlocked the bootloader, with the alert that was yellow turned red.
There I did the rom flash of April 2018 and it went without errors.
rom update and no bootloader alert.
echo92 thank you very much for your attention. big hug!!!