Hey there,
had a strange happening minutes before.
was rebooting but device was in bootloop, so i flashed factory images without -w, but no success.
so i decided to go clean and added the -w, but now while flashing i get an error in fastboot:cannot generate image for userdata
i cant find the userdata.img in the factory image anymore
any ideas?
Try format data or flash old 8.1.0 image. Hade same problem today but solved My problem
Erased Userdata and was able to start from scratch
pa.pn2 said:
Erased Userdata and was able to start from scratch
Click to expand...
Click to collapse
What steps did you follow to do that please?
I just put in the command in fastboot to erase
Could you post the command you used?
arismelachrinos said:
Could you post the command you used?
Click to expand...
Click to collapse
Guess you already figured the command, but if you didn't:
fastboot erase userdata
Cheers...
Related
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
xx000xx said:
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
Click to expand...
Click to collapse
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
graphdarnell said:
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
Click to expand...
Click to collapse
I didn't see that...anyway it happened... NO WAY???!! :crying:
xx000xx said:
I didn't see that...anyway it happened... NO WAY???!! :crying:
Click to expand...
Click to collapse
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
graphdarnell said:
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
Click to expand...
Click to collapse
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
xx000xx said:
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
Click to expand...
Click to collapse
From experience, mine and others', if you get to the animation part, it means the boot partition is intact. You get into trouble when that is damaged somehow. If I were you, I would flash everything again and separately, from boot.img, to system.img, to recovery.img.
Make sure you choose the right one for your tablet. LTE for LTE and flo for flo (wifi only model) - no mix up. I did flash a wi-fi only rom on an LTE 2012 before, and it didn't brick the tablet, but I have no idea what such a mistake would do to a 2013 model.
I would use a stock-based rom like CleanRom only because so many people bricked theirs after flashing stock rom. I would try Cleanrom to make sure the tablet is functional hardware-wise first. Then, if you feel like taking the dive, go for your stock rom. Ask the author if you cannot retrieve the individual images from the zip file. Good luck.
hardest soft-bricked ever seen!!!
anybody haven't idea?
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
yosmokinman said:
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
Click to expand...
Click to collapse
because this:
http://forum.xda-developers.com/google-nexus-5/help/load-img-error-t3108648
in #4 solved
---
i did that all thing u said but not worked
---
All,
I am not a noob by any means, but when I attempted to manually flash the img files via fastboot for the latest N build from the factory images coming from the last 6.0.1 build I get stuck on the Google logo. I checked the commands and re-flashed again and the same result happened ( i did flash radios and BL ) .
I even tried to format data ( i had backed everything up ) , still no go and stuck at google logo still. I could access BL and able to access TWRP.
I got frustrated and flashed the 6.0.1 images including BL and radio via fastboot and booted up just fine. I then rooted, installed flashfire and used the OTA and Android N installed just fine.
Does anyone have any idea what could be causing this. I am currently on N, but wanted to do a clean install .
Thanks in Advance
Did you flash vendor.img?
Why don't you list the exact commands you used to flash, then people can comment.
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
sfhub said:
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
Click to expand...
Click to collapse
SlimSnoopOS said:
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have tried fastboot erase userdata and fastboot format userdata and fastboot erase cache
fastboot format cache and that never worked.
I tried that factory image before and resulted in the same, however, I will at sometime attempt to do the final of 7.1.1 once it is available sometime in December 2016 and hopefully will resolve the issue.
I will stay on DP1 right now as i find the battery extremely excellent, the Visual VM is back now, and i notice some notifications are coming through better than in 7.0. (I read an article earlier today about notifications and the pixel not coming through)
Thanks in Advance for the people that did come through so far and wanted to thank you for your input on the matter and if i don't have a pixel by December I will try this out.
Guyzzz after erase config through fastboot .... Won't get onto O.S I used xfstk , flash raw file through fastboot , all done good but while start system stucked. .. recovery stills remains
Sideload via adb done.. system stucked
Upgrade through adb to M but stucked at boot
Unlock bootloader via fastboot works installed TWRP flash custom ROM also stucked at boot
While wipping or installing shows error on TWRP...
Unable to mount Config
Help me guyzzz is this is a mother board issue ??
user531xda said:
Guyzzz after erase config through fastboot .... Won't get onto O.S I used xfstk , flash raw file through fastboot , all done good but while start system stucked. .. recovery stills remains
Sideload via adb done.. system stucked
Upgrade through adb to M but stucked at boot
Unlock bootloader via fastboot works installed TWRP flash custom ROM also stucked at boot
While wipping or installing shows error on TWRP...
Unable to mount Config
Help me guyzzz is this is a mother board issue ??
Click to expand...
Click to collapse
well this is issue with partition. if you are on twrp try to repair it with advanced wipe and repair option. use xFSTK. and then flash raw with commands not with AFT
sukhwant717 said:
well this is issue with partition. if you are on twrp try to repair it with advanced wipe and repair option. use xFSTK. and then flash raw with commands not with AFT
Click to expand...
Click to collapse
On TWRP there's no config column to select
On mount tab on TWRP I got config column but can't able to tick (select) it
I done xfstk 10 20 times and flash with fastboot commands with your thread everything seems good on PC and device but after last command fastboot reboot it reboots to system and stuck there before the setup wizard
sukhwant717 said:
well this is issue with partition. if you are on twrp try to repair it with advanced wipe and repair option. use xFSTK. and then flash raw with commands not with AFT
Click to expand...
Click to collapse
I leaved device for 1 hour nothing happens
Reboot to recovery then format data then reboot still stucked at boot logo... Update through adb sideload .. update from adb complete then reboot and after that still stuck on boot logo...
Unlock bootloader then flash TWRP and try custom rom they also stuck on boot logo
Help me m stucked and really need help
user531xda said:
Help me m stucked and really need help
Click to expand...
Click to collapse
device can not boot untill and unless config partition is formatted. there are lot of things you can try.
fastboot erase config
fastboot erase cache
fastboot erase data
fastboot erase factory
then without reboot flash raw firmware with commands
sukhwant717 said:
device can not boot untill and unless config partition is formatted. there are lot of things you can try.
fastboot erase config
fastboot erase cache
fastboot erase data
fastboot erase factory
then without reboot flash raw firmware with commands
Click to expand...
Click to collapse
Done but still same , also tried fastboot -w but not worked ... Can I use fastboot format config?? If yes then how because I think it needs partition size and partition type for the format command through fastboot
user531xda said:
Done but still same , also tried fastboot -w but not worked ... Can I use fastboot format config?? If yes then how because I think it needs partition size and partition type for the format command through fastboot
Click to expand...
Click to collapse
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
---------- Post added at 09:33 AM ---------- Previous post was at 09:33 AM ----------
user531xda said:
Done but still same , also tried fastboot -w but not worked ... Can I use fastboot format config?? If yes then how because I think it needs partition size and partition type for the format command through fastboot
Click to expand...
Click to collapse
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
sukhwant717 said:
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
---------- Post added at 09:33 AM ---------- Previous post was at 09:33 AM ----------
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
Click to expand...
Click to collapse
Thanks alot sir...really thanks it worked ..ty ty :fingers-crossed:
user531xda said:
Thanks alot sir...really thanks it worked ..ty ty :fingers-crossed:
Click to expand...
Click to collapse
glad to know that helped
sukhwant717 said:
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
---------- Post added at 09:33 AM ---------- Previous post was at 09:33 AM ----------
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
Click to expand...
Click to collapse
Hi guys.
I have the same problem. But
"fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning"
not working for me...
FAILED (remote: unknown command)
finished. total time: -0.000s
My Redmi 4x have propably broken partitions. I didn't flash global soft because his stopped... A lot of errors, problems.
I will eraseing/format cache, userdata, system, config etc.
Only TWRP 3.0.3 has working but only when i flash with fastboot and boot. When twrp are stuck, i must flash once again with fastboot...
When I am in twrp, command adb devices see my phone like "8h231h8921 recovery"
Please, help!
How can I fix this? I flashed the most current twrp for this device and now it just bootloops twrp ...
eightrac said:
How can I fix this? I flashed the most current twrp for this device and now it just bootloops twrp ...
Click to expand...
Click to collapse
Boot in fastboot mode and run
fastboot format userdata
fastboot format cache​Your data was erased by the unlock and now it needs formatting.
k23m said:
Boot in fastboot mode and run
fastboot format userdata
fastboot format cache
Your data was erased by the unlock and now it needs formatting.
Click to expand...
Click to collapse
No, twrp wasn't fully installing itself.
That being said, I flashed it back to stock and it works fine.
Thanks anyway.
This morning I've just received the February 2019 security update, I've downloaded it but when the installation starts then it fails. Any idea why this happens?
Somebody has the same issue?
Thanks
Restart, connect charger and start again when above 60%.
Sent from my Mi A2 Lite using Tapatalk
locovibe said:
Restart, connect charger and start again when above 60%.
Click to expand...
Click to collapse
I'm going to try and then I'll let you know.
Thank you very much!
locovibe said:
Restart, connect charger and start again when above 60%.
Sent from my Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
Not work for me. Since January I have this problem.
Xmata said:
Not work for me. Since January I have this problem.
Click to expand...
Click to collapse
You need to reflash whole rom with miflasher and unlock bootloader.
Some people solved the issue by stopping the download, turning on mobile data and resuming download on mobile data. Don't forget to turn off your WiFi. Try this before flashing the stock rom again and losing all your data.
Check the log and reflash touched partitions
konan82 said:
This morning I've just received the February 2019 security update, I've downloaded it but when the installation starts then it fails. Any idea why this happens?
Somebody has the same issue?
Thanks
Click to expand...
Click to collapse
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat -e update_engine
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.
yakovpol said:
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat | grep update_engine (under Linux)
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.
Click to expand...
Click to collapse
Does this format all data?
wenna.speedy said:
You need to reflash whole rom with miflasher and unlock bootloader.
Click to expand...
Click to collapse
Unlock of bootloader will format all partitions and erase all my data, right?
konan82 said:
Unlock of bootloader will format all partitions and erase all my data, right?
Click to expand...
Click to collapse
reflashing rom lock your bootloader. it will erase your data.
unlocking bootloader via adb erase your data again.
if you have rooted phone you can't use OTA
Finally i have also got feb security update after a long waiting period.
IO13 said:
if you have rooted phone you can't use OTA
Click to expand...
Click to collapse
No my phone isn't rooted. I'm still with locked bootloader
marstonpear said:
Some people solved the issue by stopping the download, turning on mobile data and resuming download on mobile data. Don't forget to turn off your WiFi. Try this before flashing the stock rom again and losing all your data.
Click to expand...
Click to collapse
I've tried to download the entire update without WiFi, using mobile data but nothing to do
IO13 said:
if you have rooted phone you can't use OTA
Click to expand...
Click to collapse
Of course you can,
read this:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
I followed the instructions and updated my phone.
I had no problems
konan82 said:
Does this format all data?
Click to expand...
Click to collapse
Of course, not.
Reflashing of boot or system partition doesn't touch you data partition.
---------- Post added at 07:21 PM ---------- Previous post was at 07:04 PM ----------
wenna.speedy said:
reflashing rom lock your bootloader. it will erase your data.
unlocking bootloader via adb erase your data again.
Click to expand...
Click to collapse
It depends how you reflash. Some scripts provided with the stock ROM do contain bootloader lock command. Some do erase data. The performing actions follow from script names. If you are not sure, open a script and check the commands inside.
In a case you have a problem with the OTA update, it is unlikely connected to your data partition. So no need in reflashing it/reflashing entire phone and loosing your data.
---------- Post added at 07:31 PM ---------- Previous post was at 07:21 PM ----------
konan82 said:
Unlock of bootloader will format all partitions and erase all my data, right?
Click to expand...
Click to collapse
There is a way to unlock bootloader on this phone without loosing data, see https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-unlock-bootloader-erasing-t3878453
You do not have to unlock bootloader if you want to flash stock ROM images.
Something interesting
I've had done something interesting recently. I'm not a "pro" user, just a normal. I couldn't install the February update through OTA, every time the install failed.
I had download from the new dump post the full rom. (Sorry i'm a new user and i can't url posting)
k4sh44 said:
Here is the zip file with all images.
But as i told already, i wasn't able to boot with fastboot command the boot.img i extracted.
Click to expand...
Click to collapse
I have saved all my datas in my phone, then in the pc unzip all the files what i downloaded and installed the new rom with this method in fastboot mode.
HoangP05 said:
These are image files that are extracted from the payload of the android P OTA:
Warning: You will erase all of your data
Code:
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img
Run the code and then factory reset in recovery, and you will have android P.
Click to expand...
Click to collapse
After that when my phone first rebooted, the most interesting thing was for me, all of my files and apps were in my phone, anything lost, and everything is working. I don't understand why, the new rom works good, and no need restoring.
Only the magisk wasn't good. With the magisk manager I had made a patched boot img file from the full rom files. Then I booted the new patched boot img with fastboot, and then the magisk is perfect too. (but in magisk everything had to reinstalling)
yakovpol said:
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat | grep update_engine (under Linux)
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.
Click to expand...
Click to collapse
Do you think a factory reset (done from the attached image) without flashing the Rom could fix the problem?
I had same problem. Something broke when I used Adaway adblocker.
Unlocking OEM with volume down button didn't work.
And than I downloaded this image http://bigota.d.miui.com/V10.0.3.0....0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz
This is January image.
All other images here are for months before. 10.0.3 is Jan, 10.0.2 is Dec and so on
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Unzipped with 7zip this image
_________________________________________
step 1: install adb and fastboot. ( On windows follow this link https://forum.xda-developers.com/sho....php?t=2588979 )
enable the developer menu on your phone (launch settings, go to system->"about phone" and press repeately on build number)
from the developer options ( launch settings, go to system->"about phone"->developer options ) enable adb and allow bootloader unlock
connect the phone to your PC and give adb permissions to your PC. here I used in cmd
Code:
adb devices
so it would ask for permission from PC
turn off the phone
reboot by pressing power + vol down
_________________________________________
Then with adb in recovery I used:
Code:
fastboot oem unlock
then i repeated step 1, becouse of factory reset with unlocking oem
Code:
fastboot getvar current-slot
if i got A i used A in next string, if B, i used B, where ? is used
Code:
fastboot flash boot_? boot.img
Code:
fastboot flash system_? system.img
Code:
fastboot oem lock
Rebooted phone and
then I updated, and everything worked as it should.
konan82 said:
Do you think a factory reset (done from the attached image) without flashing the Rom could fix the problem?
Click to expand...
Click to collapse
No, it will not: Data partition is not being checked during the update process.
What you can do:
(a) try to find out the reason why the update is failing. It is as simple as starting adb logcat during the update and watching through strings containing update_engine for "error" or "fail" words. Then you will know for sure what is wrong in your phone.
or
(b) reflash your current android version with flash_all_except_storage.bat (if you are under Windows) or flash_all_except_storage.sh (if you are under Linux) script which are part of the whole package http://bigota.d.miui.com/V10.0.3.0....0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz
Most likely you will be able to download and perform the update after this.
or
(c) wait for a few hours: Xiaomi must grant a download link for February 10.0.4.0 version at http://en.miui.com/download-354.html and then do what is in (b) option above with the newer version. You will get updated system right away. Or at your own risk use a dump of this version that someone has already provided (find the link above in the same forum).
Wish you success.