Database Develop

Help - Stuck in Bootloop

The point in which everything took a turn for the worst was while trying to update firmware via SD update method. At which point it just stayed on android boot screen.
Recovery was broken at this point
I successfully flashed an older CWM version, but that was useless for reflashing the latest Asus firmware.
I tried flashing stock recovery again and it appeared to succeed, but now when I try to boot to recovery, it just goes back to bootloop.
I'm trying to flash the US version now via fastboot I get bootloop again and I'm getting weird errors every time I try regarding filesize. (See below)
I tried flashing CROMbi as well and it went through the install process successfully, but that resulted in bootloop as well.
Tried flashing Asus US firmware again without success,
Kind of pissed that this all started when following the instructions on the Asus site to upgrade to their latest firmware via SD card.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system
asusus.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.457s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
OKAY [ 86.837s]
writing 'system'...
OKAY [ 17.080s]
sending sparse 'system' (415060 KB)...
OKAY [ 57.305s]
writing 'system'...
OKAY [ 11.353s]
finished. total time: 174.042s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.021s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.

The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk

berndblb said:
The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
The attempted SD update was done with custom recovery as I couldn't get stock recovery to work after the initial SD update with stock recovery.
Thanks for the info. I'll update.

gorilla p said:
Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.
Click to expand...
Click to collapse
That error message means that your internal sdcard is no t available to format. Erasing all partitions is a dangerous thing to do.
The only way you will get back to normal is to try and flash the stock asus rom now as that will recreate everything. I recommend you start with the 4.2.2 one - need to flash it over fastboot - I can't see anything else working as you have erased it all.....
Also you used 0x0b05 which is the code for the last generation of transformers..... You don't need it for the TF701 but not sure if that has caused additional grief now. Probably not but you never know .....

Yeah IO'm getting the same issue that I was having before. I tried both the 4.3 and 4.2 boot.img and the recommended recovery.img file. Each time I ran
fasboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.121s]
booting...
OKAY [ 0.032s]
finished. total time: 1.157s
booting from downloaded boot.img (on tablet)
Then it goes to boot into the image and...bootloop.
C:\Program Files (x86)\Minimal ADB and Fastboot\asus>fastboot flash system asus4
22.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.515s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
OKAY [ 86.861s]
writing 'system'...
OKAY [ 17.098s]
sending sparse 'system' (338700 KB)...
OKAY [ 46.823s]
writing 'system'...
OKAY [ 9.280s]
finished. total time: 161.586s
Bootloop...
Could the inability to flash or boot from stock recovery have anything to do with the CWM recovery protection?

Well after those attempts it's totally shot.
Now I can't even get to fastboot. Every reboot results in "Unrecoverable bootloader error..."
Files RMA. Returned.
Moral of story. Don't do anything on a Tegra device without previous documentation that doesn't have NVFlash available.

Can't access custom recovery :(

I've tried to install CM11 on xperia V (rooted) with T4.3_PhilZCWM_6.0.4.7_LB_v1.7 but I got error 7 and when reboot my device dont boot I tired to going to costume recovery but can't do it (broken recovery) so I can't install recovery flash-able .zip file again. and can't find *.img file in it!
How I can get stock or costume recovery file as .img for use flash in fastboot? or Can I flash custom recovery .zip file via fastboot?
and tried: fastboot flash recovery T4.3_PhilZCWM_6.0.4.7_LB_v1.7.zip
Get:
sending 'recovery' (3201 KB)...
(bootloader) USB download speed was 16392kB/s
OKAY [ 0.218s]
writing 'recovery'...
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
thank you for help

Answer is:
Sony phones doesn't have separate recovery partition. Its recovery is incorporated to the boot.img, which contains also the kernel.
Custom kernels normally comes with the recovery. You only need to "fastboot flash boot boot.img"
source: http://forum.xda-developers.com/member.php?u=4023029
So: extract boot.img from CM11.zip file and fastboot flash boot.img and recovery will accessible

[ROM] MM M1D63X ext 4 Rooted + Frankenlenok Kernel

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, thermonuclear war,
* or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if you point
* the finger at me for messing up your device, I will laugh at you.
*/
I've made a very fast rom, without a lot of stupid apk and with ext4 system for modifing /system.
You must say thanks to other people, I'm only a stupid "aggregator"....
But thanks also to @Cameo164, after his experience i've made a more little system.img, changing the partions size.
- Download my rom, unzip
http://www.mediafire.com/file/ke5h46vy86o23tl/DF0.1.zip
- Reboot into fastboot
- Install this Recovery (you'll find also here: http://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166 )
fastboot flash recovery path/to/twrp-3.0.0.img
- Reboot into recovery and Make a backup of your Rom/data/system with this recovery!!!! It's very important!
- Wipe cache and data via recovery, reboot into bootloader
- Install my boot.img
fastboot flash boot boot.img
- Go to this thred ( http://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166 ) and follow the steps 4-15 and then come back here
- Then:
fastboot flash system systemimageresized.img
- Reboot recovery and install supersu: Wear-SuperSU-v2.67.zip (you'll find in my zip)
- Restart system and wait..........
- Don't care for the google play error on your smartwatch, if you have
- Enable adb debug under dev options on your watch, you can also enable before paring, pushing the hardware button for about 2 seconds
- Pair with your phone
- Install busybox (you'll find in my zip)
adb install busybox.apk
- Install advanced settings for wear http://forum.xda-developers.com/android/apps-games/advanced-settings-t3341722
adb install com.sssemil.advancedsettings.apk
It's very usefull for change the screensaver brightness and other things
- Install Kernel Auditor http://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122
adb install KernelAudiutor4Wear.apk
For enable/disable cores and other things
- on your smartwatch if you have issue, reboot and clear data to google.play. framework (with advanced settings), reboot again
This rom is without a lot of things (like lg wathfaces, tutorial.apk and other things that i don't remeber, i'm sorry).
I use other watchfaces (with facer, this is mine: https://www.facer.io/watchface/hLzCJbTR3Z?draft=true )
Don't ask for add apks, or other things, thank you!
I suggest disable with advanced settings under apps also Bug report sender com.google...wearable.bugreportsender
Remember:
Don't change kernel or rom because you'll corrupt the new ext4 partition and you'll lose your data.
In any case before make a backup,
So, when you'll change rom/kernel you must install again the right kernel and the right rom.
If you have adb error ($ADB_VENDOR_KEYS is not set; try 'adb kill-server'), from recovery:
On your pc search adbkey.pub
cd user/.android
adb push adbkey.pub /data/misc/adb/adb_keys
You must say thanks to:
For stock Image thanks to @intersectRaven and also @vt0r http://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
For This great Kernel thanks to @dirtyhank http://forum.xda-developers.com/g-watch-r/development/kernel-frankenlenok-t3342054 (look at the last page)
windroid toolkit http://forum.xda-developers.com/showthread.php?t=2499926
@Chainfire
@suleymanovemil8
@Xmaster24
@Grarak
@dirtyhank
@Cameo164

Changelog
I've uploaded my things.

Hi, thanks for your work, but for me restoring your system in twrp fails. It show's me an "ERROR: 255" close to the end. I re-downloaded the backup files, so that I can be sure that the files aren't damaged, but still no luck. I'm using the twrp.img you provided and did it like you described.
And btw. When I'm right, it should be called "adb push" not "adb pull".

http://forum.xda-developers.com/showthread.php?t=2236620&page=48
Did you format your system, cache and data?
Did you mount system in recovery?
Or try installing before leedroid rom.
Yes... is push! I'm sorry!

dettofatto said:
http://forum.xda-developers.com/showthread.php?t=2236620&page=48
Did you format your system, cache and data?
Or try installing before leedroid rom.
Click to expand...
Click to collapse
Yes I did. But it's not important if I did it, because TWRP does it before restoring anyways.
What difference would it make if install leedroid rom before restoring, when TWRP formats /system before restoring your backup ?

If you read the link that I've posted you'll see that the issue is in some files on your phone (probably).
Leedroid use ext4, mm only f2fs (I don't remember name exactly) on system. So, probably, if you install leedroid rom, you'll format your system partition to ext4.

dettofatto said:
If you read the link that I've posted you'll see that the issue is in some files on your phone (probably).
Leedroid use ext4, mm only f2fs (I don't remember name exactly) on system. So, probably, if you install leedroid rom, you'll format your system partition to ext4.
Click to expand...
Click to collapse
To have ext4 I don't need to install a non-mm rom like leedroid's. I can just format /system to ext4 in TWRP.
Yes I have read it. The file that causes problems is "/system/usr/icu/icudt55l.dat". I removed it from the backup file and pushed the new file to the watch. And now the restoring works. But I ended up with a bootloop (tried with SuperSu flashed & without SuperSu). I don't know if it's because I removed the file or if it has any other reason.
Thanks for trying to help me.

Did you wait about 5 mins? Because the first time is very long!
Try also with several reboot!
Which boot animation you see?
After I'll see that file!!
But I don't understand... in your log which error is it?
Did you correct permission? In any case you can't remove I file from backup and restore.
Because if you format system and data you don't have any files, restoring stops for an error rewriting your files?
I've restored full m1d63x stock and then I've checked my backup and steps and I didn't find any stop...

dettofatto said:
Did you wait about 5 mins? Because the first time is very long!
Try also with several reboot!
Which boot animation you see?
After I'll see that file!!
But I don't understand... in your log which error is it?
Did you correct permission? In any case you can't remove I file from backup and restore.
Because if you format system and data you don't have any files, restoring stops for an error rewriting your files?
I've restored full m1d63x stock and then I've checked my backup and steps and I didn't find any stop...
Click to expand...
Click to collapse
Yeah I waited 30 minutes, rebooted, waited another 30 minutes and again, again...
The bootanimation I see on watch is in the attachments but because the watch screen is too small there's only "ndroi" instead of "android" visible. And there's that darker font shadow, like a fade-out animation which is going through continuously.
I know that I can't just delete one file, but with that file I can't even restore the backup.
Then I get this error :
Code:
tar_extract_all(): calling th_get_pathname()
tar_extract_all(): calling tar_extract_file(t, "/system//usr/icu/")
item name: '/usr/icu/'
dir
==> extracting: /system//usr/icu/ (mode 40755, directory)
==> setting perms: /system//usr/icu/ (mode 40755, uid 0, gid 0)
Restoring SELinux context u:object_r:system_file:s0 to file /system//usr/icu/
tar_extract_all(): calling th_get_pathname()
tar_extract_all(): calling tar_extract_file(t, "/system//usr/icu/icudt55l.dat")
item name: '/usr/icu/icudt55l.dat'
reg
==> tar_extract_regfile(t=0xb56a9300, realname="/system//usr/icu/icudt55l.dat")
==> extracting: /system//usr/icu/icudt55l.dat (file size 23068784 bytes)
FAILED RESTORE OF FILE i: /system//usr/icu/icudt55l.dat
I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/411KPFX0122123/DF/system.ext4.win'
Fehler während der Wiederherstellung. *should be "Error during restore process" in english
Prozess extractTarFork() endete mit FEHLER: 255 *should be "Prozess extractTarFork() ends with ERROR:255" in english
I:Failed to reset capabilities of /system/bin/run-as binary.
Can you send me the file icudt55l.dat from your running watch and then I can try replacing the file in the backup?

I'll send you icudt55l.da after, when I come back at home. But is very strange...
Anyone has this issue?

icudt55l.dat rw-r-r-
http://www.mediafire.com/file/kjge1s3ox561s5g/icudt55l.dat

dettofatto said:
icudt55l.dat rw-r-r-
http://www.mediafire.com/file/kjge1s3ox561s5g/icudt55l.dat
Click to expand...
Click to collapse
I tried everything I'm able to do : First pasting your new icudt55l.dat file into the backup, just gives me the same error as before. Then I tried restoring the backup without the icudt55l.dat file and push the file with adb push to /system/usr/icu, just gives me a "no space left on device error" and at last I tried to extract the system.ext4.win file on the watch with adb shell instead of twrp, this gives me a "no space left on device" error too, but it seams that I does it anyways. But still stuck on bootanimation. I just can't get this rom to work on my watch :|

After I'll try tu upload another backup...

Ok i've created a system.img_sparsechunk1 flashable via fastboot
Backup everything.
Then download: http://www.mediafire.com/file/d3yo1opb4i7j7at/system.img_sparsechunk1
Reboot into bootloader and:
fastboot erase system
fastboot erase data
fastboot erase cache
fastboot flash system system.img_sparsechunk1
Flash also (I don't know if is necessary for you, but you must use mine boot.img) boot.img http://www.mediafire.com/file/w11byay60nwy5xb/boot.img
fastboot flash boot boot.img
Reboot into recovery and
Wipe data, davlink and cache
Reboot
How I've obtained this system.img_sparsechunk1?
I've extracted my system.img with: dd if=/dev/block/mmcblk0p19 of=/sdcard/system.img
but when i reflashed via fastboot I had an error because was bigger than system partition.
So i've compressed with SparseConverter v1.0.1 http://forum.xda-developers.com/showthread.php?t=2749797
to correct size: sparseconverter /compress system.img .\ 2684354560
and I've obtained the righht system.img
I hope...
In any case i've reflashed on mine and is ok

Thanks a lot for your hard work but my watch still refuses to flash the system -.-
Code:
fastboot.exe flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.288s]
sending sparse 'system' 1/2 (252175 KB)...
OKAY [ 8.280s]
writing 'system' 1/2...
FAILED (remote: size too large)
finished. total time: 8.651s
I have tried it with the latest fastboot version for windows and linux too, but both fail on "size too large". I have even downloaded SparseConverter myself, decompressed the "system.img_sparsechunk1" to "system.img" and then compressed it back into two 100MB and one 61MB sparsechunk files. Still fastboot gives me the "size too large" error.
I can flash the stock "M1D63X_system.img" successfully and it boots too.

I have this
Code:
D:\Hack\Android\LG\extracted>fastboot flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.375s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.551s]
writing 'system'...
OKAY [ 81.913s]
sending sparse 'system' (15336 KB)...
OKAY [ 0.632s]
writing 'system'...
OKAY [ 31.335s]
finished. total time: 122.806s
try with this fastboot http://www.mediafire.com/file/rbz0qqlbb0hty9r/fastboot.exe

dettofatto said:
I have this
Code:
D:\Hack\Android\LG\extracted>fastboot flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.375s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.551s]
writing 'system'...
OKAY [ 81.913s]
sending sparse 'system' (15336 KB)...
OKAY [ 0.632s]
writing 'system'...
OKAY [ 31.335s]
finished. total time: 122.806s
try with this fastboot http://www.mediafire.com/file/rbz0qqlbb0hty9r/fastboot.exe
Click to expand...
Click to collapse
I tried your fastboot version, but it happens the same :
Code:
fastboot.exe flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.300s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.332s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 8.711s

Ok... I don't have any idea for this.
I'm uploading another backup, and another system.img extracted (this is more big, because is uncompressed)

dettofatto said:
Ok... I don't have any idea for this.
I'm uploading another backup, and another system.img extracted (this is more big, because is uncompressed)
Click to expand...
Click to collapse
I don't have any ideas too, I would be very good if anyone else could try your rom and tell if installing and booting works. Then we would know if it's my watch's or my' fault or the rom's fault.

System uncompressed extracted: http://www.mediafire.com/file/g481ae7m3ayrjmb/systemuncompressed.zip
New Backup from System:
http://www.mediafire.com/file/4jc5a31xe2insc6/TWRP.7z
May be is my rom

[GUIDE] Backup your System partition using dd

Assalamu alaikum people,
I have seen many people complain that stock ROM is ruined or XYZ feature is missing or OTA has broken down their devices. It is safer to just backup your stock ROM before playing around. Some say that twrp backup is not working. So, we can use a fail-safe method that definitely works. I personally tested on my device. And since you are backing up your own system partition, it will definitely work for you too.
To do this, you need to have a rooted device. It is just one line of code. You can run it in terminal emulator app for android or you can connect your phone to PC.
Note:This command works with Honor 9 lite. For non-Honor devices, you must do "cat /proc/mounts" and understand the results to modify your code.
Steps to be taken
1. If you connect it to your PC, you need to do "adb shell". If you don't know what adb shell means, you better download Terminal emulator on your Honor phone and open it.
2. Then type "su" without the inverted commas inside terminal app or your adb shell. It will ask for root permissions. Grant it.
3.Paste the following code
Code:
dd if=/dev/block/platform/hi_mci.0/by-name/system of=/storage/emulated/0/system.img
The code will take some time and then display a result that it has succeeded and the bytes copied. Your system is backed up to your internal storage with the file name system.img. Now you can play around and if anything goes wrong, you can simply re-write your system.img and everything will be fine. Enjoy!!!

@aveemashfaq
Assalamu alaikum return to you.
have we a chance with this procedure to save "userdata" ? i think, it's encrypted.
your code work, i have now system.img, doing other test's with other rom's, reflash this system.img and this work ! nice way if not twrp installed !

JamesBott said:
@aveemashfaq
Assalamu alaikum return to you.
have we a chance with this procedure to save "userdata" ? i think, it's encrypted.
your code work, i have now system.img, doing other test's with other rom's, reflash this system.img and this work ! nice way if not twrp installed !
Click to expand...
Click to collapse
You can save everything byte by byte... But that dont helps to decrypt it... I suggest to save everything from /sdcard to the external sd and after that wipe data, deactivate encryption and let the system recreate data unencrypted. Don't forget to save hw_init before...

@Darkest-Dark
i need not decrypted. i mean : if i make "dd if= .../userdata of= .../userdata.img "can i flash stock.system and flash this userdata.img AND phone WORK
with my userdata ! if encrypted or decrypted : that's no important. important is working ?

JamesBott said:
@Darkest-Dark
i need not decrypted. i mean : if i make "dd if= .../userdata of= .../userdata.img "can i flash stock.system and flash this userdata.img AND phone WORK
with my userdata ! if encrypted or decrypted : that's no important. important is working ?
Click to expand...
Click to collapse
I don't understand why you would like to save data partition because there isn't any important... To save data of apps you could use titanium backup...
Here is what you wanna have:
Code:
dd if=/dev/block/platform/hi_mci.0/by-name/userdata of=/youwanttosave/userdata.img

Hey,
If you want to save userdata, it is not /something/userdata but it is /something/data. It is a good idea to backup all partitions before you start. I have accidentally formatted my /data partition using twrp and now the stock system will not boot at all. That is because stock data partition is in f2fs format and twrp reformatted it to ext4 format. I am not telling not to install twrp. I am just warning you that don't format data partition using twrp.
And also, remember that you cannot execute this code unless you have root access. And to get root access, you have to install twrp in the first place.
So, the code is
Code:
dd if=/dev/block/platform/hi_mci.0/by-name/data of=/storage/emulated/0/userdata.img
It will save your data in the internal storage with the name userdata.img

aveemashfaq said:
Hey,
If you want to save userdata, it is not /something/userdata but it is /something/data. It is a good idea to backup all partitions before you start. I have accidentally formatted my /data partition using twrp and now the stock system will not boot at all. That is because stock data partition is in f2fs format and twrp reformatted it to ext4 format. I am not telling not to install twrp. I am just warning you that don't format data partition using twrp.
And also, remember that you cannot execute this code unless you have root access. And to get root access, you have to install twrp in the first place.
So, the code is
Code:
dd if=/dev/block/platform/hi_mci.0/by-name/data of=/storage/emulated/0/userdata.img
It will save your data in the internal storage with the name userdata.img
Click to expand...
Click to collapse
There is no data image at all. It's called userdata.
You can "erase" userdata by using fastboot or tell twrp to run rm - rf instead of format data Partition.

Hi,
i did tests. dd system work.
dd if=/dev/block/platform/hi_mci.0/by-name/userdata | gzip > /mnt/media_rw/8457-1CE9/dd-backup/stock-userdata.img
49274880+0 records in
49274880+0 records out
25228738560 bytes transferred in 824.913 secs
now flash system.img (developer-rom)
don't work by me
boot to bootloader
flash backup-system.img "ok"
flash backup-stock-userdata.img "fail"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 857477578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 385622474 is not a multiple of the block size 4096
fastboot: ../libsparse/sparse.c:144: write_all_blocks: Assertion `pad >= 0' failed.
Abgebrochen (Speicherabzug geschrieben)
in principle can work if solve "gzip or what here break"
now i have info, that new twrp is available and i "must" test this
if this twrp work then i open new thread
this backup with dd is in principle a simle way (thank's to @aveemashfaq for your thread here) :good:
i think if new twrp working - this info is more important (my opinion) :angel:

JamesBott said:
Hi,
i did tests. dd system work.
dd if=/dev/block/platform/hi_mci.0/by-name/userdata | gzip > /mnt/media_rw/8457-1CE9/dd-backup/stock-userdata.img
49274880+0 records in
49274880+0 records out
25228738560 bytes transferred in 824.913 secs
now flash system.img (developer-rom)
don't work by me
boot to bootloader
flash backup-system.img "ok"
flash backup-stock-userdata.img "fail"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 857477578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 385622474 is not a multiple of the block size 4096
fastboot: ../libsparse/sparse.c:144: write_all_blocks: Assertion `pad >= 0' failed.
Abgebrochen (Speicherabzug geschrieben)
in principle can work if solve "gzip or what here break"
now i have info, that new twrp is available and i "must" test this
if this twrp work then i open new thread
this backup with dd is in principle a simle way (thank's to @aveemashfaq for your thread here) :good:
i think if new twrp working - this info is more important (my opinion) :angel:
Click to expand...
Click to collapse
I asked why you would like to save it... Its an f2fs partition not ext4... Its not quite easy...
Fastboot can handle it since Merge of 02/18... Isnt in honor9...
Even TWRP cant handle is safety...

JamesBott said:
Hi,
i did tests. dd system work.
dd if=/dev/block/platform/hi_mci.0/by-name/userdata | gzip > /mnt/media_rw/8457-1CE9/dd-backup/stock-userdata.img
49274880+0 records in
49274880+0 records out
25228738560 bytes transferred in 824.913 secs
now flash system.img (developer-rom)
don't work by me
boot to bootloader
flash backup-system.img "ok"
flash backup-stock-userdata.img "fail"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 857477578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 385622474 is not a multiple of the block size 4096
fastboot: ../libsparse/sparse.c:144: write_all_blocks: Assertion `pad >= 0' failed.
Abgebrochen (Speicherabzug geschrieben)
in principle can work if solve "gzip or what here break"
now i have info, that new twrp is available and i "must" test this
if this twrp work then i open new thread
this backup with dd is in principle a simle way (thank's to @aveemashfaq for your thread here) :good:
i think if new twrp working - this info is more important (my opinion) :angel:
Click to expand...
Click to collapse
Two things for you. First you should not compress them in gzip. It is only dd if=original_file of=destination.img. You have added |gzip in the middle which ruins things for you.
Second point. You can install images using twrp. I can confirm it works. fastboot flash does not work unless it is sparse image. so, you can restore using twrp.

aveemashfaq said:
I have accidentally formatted my /data partition using twrp and now the stock system will not boot at all. That is because stock data partition is in f2fs format and twrp reformatted it to ext4 format. I am not telling not to install twrp. I am just warning you that don't format data partition using twrp.
Click to expand...
Click to collapse
Hi @aveemashfaq just red this post, like you i formatted my data partition and now my Honor 9 lite LLD-L31 C432 is in a bootloop ( data partition is formatted as f2fs not ext4).
I've tried restoring a backup, restoring with HuRupdater and flashing a custom ROM but it's still bootlooping.
Could you tell me how you got it fixed.
Edit: I found this thread by you:
https://forum.xda-developers.com/9-lite/how-to/guide-unbrick-device-recover-bootloop-t3772563
and i'm trying it out.

stuck on twrp recovery wont boot

i have on vivo xl4
i followed this and well it rebooted but i got a error
fastboot flash boot boot.img (this is i used)
fastboot flash system system.img (this is ROM, like kitkat, or lolipop)
fastboot flash userdata userdata.img (this can be optional, it means full reset)
fastboot flash recovery recovery.img ( if on twrp , dont flash this thing if not cause problems)
dm-verity error
error was system is corrupted vol up for e10 vol down to restart
when i flashed sys img it all sparse and said okay should i not flash recovery??
i have a updated factory img i can try
to repeat - sys img it all sparse and said writing system okay for all of it