Dumping/splitting image failed. Aborting... - X Style (Pure) Q&A, Help & Troubleshooting

Any attempt on my XT1575 with the latest OTA to install a kernel or systemless root patch, gives me this error which makes my device unbootable until I flash a valid boot.img again. What gives?

Bootloader unlocked?

Related

Error when trying to flash stock ROM and lock bootloader

Currently I have installed latest official nightly LineageOS 14.1 on my device. I want to return to stock ROM and lock bootloader. Previously, before bootloader unlocking, I had 6.0.1 stock, version with january security updates (probably).
I have downloaded latest stock 6.0.1 MPD24.107-52 ( https://github.com/motoxplay/stock ).
Unfortunately, I got an error when tried to flash it:
HTML:
$ fastboot flash partition gpt.bin
it returns:
HTML:
(bootloader) Preflash validation failed
same with recovery.img
To lock bootloader I have to flash all stock files.
Any ideas? Thanks
skip it. You cant flash same bootloader and same gpt.bin again.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
NOTE: You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin). At this point you can either continue the flash and NOT lock the bootloader at the end, or stop until you can find the most current image. Moto used to be quite willing to hand these out when they were requested, so if you have a very new firmware installed you may not find one that you can use to relock with on the Internet. Part of the requirements to lock the bootloader is you must successfully flash the partition table (gpt.bin) in order to complete the lock process, if you can't then the bootloader lock process cannot be finished.
Click to expand...
Click to collapse
so i have to wait for the official nougat flashable file.
bump
any workaround?

Bootloader relocked, root lost after 93-4 TWRP patch install - expected behavior?

After installing the 93-4 patch for TWRP, the bootloader got relocked, and the phone got unrooted too. But the TWRP was there from the recovery mode. So I re-rooted the phone by reinstalling no-verity and magisk. Did not bother to unlock the bootloader through. Is this expected?
Umm... What?!?! The bootloader could not have possibly been locked in this process, TWRP does not really have that capability, and if it was then your device would not boot since it has an unsigned recovery and you would get a security check failure.
If you are really worried about this, what the output of "fastboot getvar all"?

moto g4 wont boot

hi now I no you prob see this title and think oh another 1 but hear me out as I cant find any thing the same as the issue I'm having.
so I followed a rooting guide unlocked bootloader installed twrp all good installed supersu phone wont boot reinstalled twrp systemless installed supersu still nothing I have followed every guide I can find phone will only boot into twrp or bootloader I have flashed custom and stock roms however I do keep getting
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.071s
PS C:\Program Files (x86)\Minimal ADB and Fastboot>
I have tried every way I can find still nothing when I try to boot it freezes on the screen saying my phone is unlocked and cant be trusted I'm now lost don't no were to go from here I did not back any thing up as the first thread I read don't say bout it and iv neva had any problems with any of my other phones or games consoles I no games consoles are different any help would be amazing
Most likely the flashing wasn’t complete or corrupted or the stock ROM wasn’t the correct one (Remember to be safe you’d have to flash the original ROM when you bought the phone) that being said. My suggestion you should try flashing TWRP again and boot into TWRP. Then flash stock ROM which will overwrite the current config. Not guaranteed, but it’s worth a shot.
Good luck.
Sent from my iPhone 7 Plus from Tapatalk
Sorry to sound dumb flash it through twrps? I can get twrps to boot but thats it iv flashed through bootloader putting all commands in separate but when i tried to boot it came up with no command with the andriod dude with a red triangle above him but i can flash and boot twrps after this
1) If you're rooting on stock Motorola Nougat ROMs, you need a custom kernel - attempting to root on the stock Motorola hudsoncm kernel usually results in a boot failure or bootloop as you've found. https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 for a useful guide, you can root with either magisk or SuperSU.
2)That security downgrade error suggests you're attempting to flash stock firmware older than the firmware matching your device's bootloader. If you need newer firmware, you could look into this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You'll need to flash this firmware via fastboot/the bootloader.
3) Try first of all booting into TWRP, copy a custom kernel to your device via a computer and USB cable, and then flash the custom kernel. See if that gets your device booting. If not, you may have to re-flash the stock firmware to get your device booting again (or use a backup, if you had one).
echo92 said:
1) If you're rooting on stock Motorola Nougat ROMs, you need a custom kernel - attempting to root on the stock Motorola hudsoncm kernel usually results in a boot failure or bootloop as you've found. https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 for a useful guide, you can root with either magisk or SuperSU.
2)That security downgrade error suggests you're attempting to flash stock firmware older than the firmware matching your device's bootloader. If you need newer firmware, you could look into this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You'll need to flash this firmware via fastboot/the bootloader.
3) Try first of all booting into TWRP, copy a custom kernel to your device via a computer and USB cable, and then flash the custom kernel. See if that gets your device booting. If not, you may have to re-flash the stock firmware to get your device booting again (or use a backup, if you had one).
Click to expand...
Click to collapse
If xt1625 amazon not having understood flash RSD firmware ATHENE_NPJS25.93-14-13 (instead ATHENE_AMZ_NPJ25.93-14.7) is there any way to restore the phone's load ?
bootloder lock, oem lock, "we have detected an attempt to flash unauthorized sw on your device"
hlpain said:
If xt1625 amazon not having understood flash RSD firmware ATHENE_NPJS25.93-14-13 (instead ATHENE_AMZ_NPJ25.93-14.7) is there any way to restore the phone's load ?
bootloder lock, oem lock, "we have detected an attempt to flash unauthorized sw on your device"
Click to expand...
Click to collapse
Have you tried to flash this firmware: https://androidfilehost.com/?fid=817906626617956922 That should be the AMZ NPJ25.93-14.7 US firmware (for XT1625 and XT1644)
tried, error gpt bootloader, all firmware below 14-13 not installed, AMZ NPJ25.93-14-13 I did not find it or it does not exist.
hlpain said:
tried, error gpt bootloader, all firmware below 14-13 not installed, AMZ NPJ25.93-14-13 I did not find it or it does not exist.
Click to expand...
Click to collapse
Unfortunately you'd have to wait for a newer firmware, the NPJS25.93-14-13, NPJS25.93-14-15 and NPJS25.93-14-18 firmwares are for retail devices. Amazon devices are on a different firmware and as you've partially flashed the Dec 2017 firmware, you'd likely need AMZ NPJ25.93-14.7-3 or NPJ25.93-14.7-5 (Feb 2018 update), however neither AMZ build appears to be available at the moment.
If you're desperate for a working device, your best bet may be to talk to Amazon or Motorola support, or if your bootloader was previously unlocked, you could try to unlock your bootloader and flash a custom ROM.
I will wait for a new firmware amz

how to relock bootloader unlocked by official tool

since i have unlocked bootloader by official tool i can not root it and i cannot install any recovery
please help me so i can relock bootloader of my phone
i have tried maximum methods to relock bootloader of my phone but i am unsuccesful
can someone please help me so i can relock bootloader of my phone
uhm i unlocked my bootloader via official tool, and i already installed twrp and magisk
What is the process that you apply because I am facing issue.whenever I tried to install twrp recovery it says something about target report size does not reach and partition error
twrp not installing
now i am facing issue with this
unknown partition 'recoveryC:\Users\sankalp\Desktop\asus max pro m2\unlock\twrp-3.3.1-0-X01BD.img'
error: cannot determine image filename for
https://forum.xda-developers.com/max-pro-m2/development/recovery-twrp-3-2-3-x-t3885935/page10
Unlock 1st
After relock etc
Use original recovery wipe data case
Than boot to bootloder
Boot to twrp recovery
Wipe data
Install twrp
Flash rom?
https://forum.xda-developers.com/max-pro-m2/development/recovery-twrp-3-2-3-x-t3885935/page10
Unlock 1st
Flash orio file .. stock orio not pie

BAH-W09 boot loop after Magisk patched boot.img

My friend give me a Huawei Mediapad with lastest stock rom EMUI 5.1.3 and Android 7.0 installed. I want to root it with Magisk. After successful unlock bootloader, flash twrp, than I tried to flash Magisk 25.2 under twrp. The flash process output some permission denied error with /data/... path, but return success result. After reboot, it enter the boot loop. Then, I boot to recovery and try to uninstall Magisk, but not success. I need to recover it by flash the original boot.img from fastboot to make it boot again. Next, I tried to patch the boot.img under Magisk Manager. This time, I got the patched boot.img and flash it again in fastboot mode. It's the same result. All the patched boot.img by using differnt patch options are not boot successfully. Any procedures to make root successul on this rom?

Categories

Resources