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.
Related
I used the latest leaked update and flashed my droid 3 to Version 5.6.890, but now I having problem with my camera, so I decided to enter the Recovery mode and do the Data Wiping, but I found out I cannot enter the recovery mode...the screen shows AP FASTBOOT MODE and "BOOT FAILURE"...
So have I half bricked my Droid 3...? is there any way I can solve this problem and safe the Recovery Mode?
Thanks.
Read this post and this thread.
limaxray said:
Read this post and this thread.
Click to expand...
Click to collapse
Thanks for the information, I tried the method, but still failing to fix the problem, this is what the screen shows after i run the commend.
PHP:
[email protected]_solana:/# sh /etc/install-recovery.sh
sh /etc/install-recovery.sh
blk: partition "emstorage" size 12203196416 not a multiple of io_buffer_size 524
288
contents of partition "recovery" didn't match MTD:recovery:2048:ed2ac38df0bab0b2
382dc3330707ff884981f335
file "MTD:recovery:2048:ed2ac38df0bab0b2382dc3330707ff884981f335" doesn't have a
ny of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
applying patch to MTD:boot:8388608:c2c527aa31b9e529de6c6a574e4e589f1d2965d9
LoadPartitionContents called with bad filename (MTD:recovery)
blk: partition "emstorage" size 12203196416 not a multiple of io_buffer_size 524
288
contents of partition "recovery" didn't match MTD:recovery
partition read matched size 8388608 sha c2c527aa31b9e529de6c6a574e4e589f1d2965d9
543948800 bytes free on /cache (8388608 needed)
[email protected]_solana:/#
What's the output of
Code:
df /system
limaxray said:
What's the output of
Code:
df /system
Click to expand...
Click to collapse
It shows:
PHP:
Filesystem Size Used Free Blksize
/system 320M 310M 9M 1024
and I have also extract "install-recovery.sh" from the latest OTA package, and push to system/etc, now when i run the commend it shows:
PHP:
[email protected]_solana:/# sh /etc/install-recovery.sh
sh /etc/install-recovery.sh
blk: partition "emstorage" size 12203196416 not a multiple of io_buffer_size 524
288
partition read matched size 2048 sha ed2ac38df0bab0b2382dc3330707ff884981f335
EDIT: Solved, maybe after the space is freed up a little, I was able to enter the recovery mode again, and I re-flashed the OTA update again, everything is working now!
If you were able to enter recovery, then you were successful in running install-recovery.sh.
In any case, I'm glad you were able to get it to work.
Yesterday, the OTA update was pushed to my D3 by verizon. It appearred to install correctly, but I noticed issues with a couple apps. I tried to enter recovery, but it's not there! I checked /system and it is full. 0 free space. I need to reinstall the recovery. Any help would be appreciated.
UPDATE: I rooted my D3, and then pushed the recovery to the phone. I then ran the install .sh and was able to boot into recovery.
AXi0N420 said:
Yesterday, the OTA update was pushed to my D3 by verizon. It appearred to install correctly, but I noticed issues with a couple apps. I tried to enter recovery, but it's not there! I checked /system and it is full. 0 free space. I need to reinstall the recovery. Any help would be appreciated.
Click to expand...
Click to collapse
I have the same issue. Update installs (Thanks to Petes tools for bloatware recovery) but camera app is not working. Try to boot into recovery and get this message:
Code:
AP Fastboot Flash Mode (S) (Boot Failure)
0A.53
BAttery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG Version (CG:recovery)
Based on suggestions here I used Titanium Backup to backup and remove a few verizon bloatware apps and got up to 54MB free on recovery partition, but still can't boot into recovery. Tried doing an adb push of the install-recover.sh from the update to /system/etc and still can't boot into recovery. When I run sh /etc/install-recovery.sh I get this:
Code:
[email protected]_solana:/# sh /etc/install-recovery.sh
sh /etc/install-recovery.sh
blk: partition "emstorage" size 12203196416 not a multiple of io_buffer_size 524
288
contents of partition "recovery" didn't match MTD:recovery:2048:ed2ac38df0bab0b2
382dc3330707ff884981f335
file "MTD:recovery:2048:ed2ac38df0bab0b2382dc3330707ff884981f335" doesn't have a
ny of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
applying patch to MTD:boot:8388608:c2c527aa31b9e529de6c6a574e4e589f1d2965d9
LoadPartitionContents called with bad filename (MTD:recovery)
blk: partition "emstorage" size 12203196416 not a multiple of io_buffer_size 524
288
contents of partition "recovery" didn't match MTD:recovery
partition read matched size 8388608 sha c2c527aa31b9e529de6c6a574e4e589f1d2965d9
544096256 bytes free on /cache (8388608 needed)
Unknown patch file format
I do not really know where to go from here. Because I haven't yet posted ten times, I can't respond directly to the thread where they were discussing this solution. Any help would be greatly appreciated.
I pushed recovery-from-boot.p and install-recovery.sh files from an update I downloaded from another thread. I ran the .sh from terminal on the phone, and it installed the recovery partition. Did you push both files?
recovery-from-boot.p is located at /system/recovery-from-boot.p
AXi0N420 said:
I pushed recovery-from-boot.p and install-recovery.sh files from an update I downloaded from another thread. I ran the .sh from terminal on the phone, and it installed the recovery partition. Did you push both files?
recovery-from-boot.p is located at /system/recovery-from-boot.p
Click to expand...
Click to collapse
Thanks a lot! This seems to have worked. I ran the install-recovery.sh from an adb shell and am able to boot into recovery again. Now I just have to reinstall all the bloatware and run the patch again.
Hi,
I tried to flash JB from one of those http://forum.xda-developers.com/showthread.php?t=1936512 (on Windows with the motorola drivers), and since then the i does not go beyond the red M.
I can still access the fastboot, but when doing manually "fastboot flash boot boot.img", the CMD prompt shows/
> sending 'boot'
> okay
> writing 'boot'
> okay
> finished
And on the phone
> Getvar max-download-size
> Downloading ...
> Flashing boot...
and nothing else happens. I tried wiping and all but still nothing...
Does anyone have a clue?
thx
maybe duplicate of this?
Jeqar said:
Hi,
and nothing else happens. I tried wiping and all but still nothing...
Does anyone have a clue?
thx
Click to expand...
Click to collapse
I'm expieriencing a similar problem, maybe relatet? http://forum.xda-developers.com/showthread.php?p=37592790
From the recovery I flashed "81.5.31002.Retail.en.GB" that was on my sd card, but the i doesn't go further than the red M with unlocked on it...
I really don't know what else to try.
AW: Stuck in Fastboot
Try this one with RSD 6.1.4
http://sbf.droid-developers.org/smi...17.0R_USASMIICSRTGB_P042_A005_S1FF_fb.xml.zip
Sent from my XT890
I tried with "CFC_signed_customer_8.7.1I-110_IFW-31_RTGB.xml" as I was already downloading it and it worked!
Thanks a LOT !
Do you know what was the issue and what I should do to flash JB properly (now that I know how to come back to ICS...)?
AW: Stuck in Fastboot
The File i've linked is the actual 390001 GB Retail. You flashed an old one.
But about your Question.
Make sure you have the actual Moto Drivers installed! Enable USB Debugging in Developersettings and run the flashandroot.bat while you're booted into your System. After it flashed successfully boot into Recovery, flash the Root.zip and Profit. Nothing else will work and many users didn't have any issues (me included)
Just charge your battery before that and give it another go.
Sent from my XT890
just try to flash a new boot.img, worked for me
HSD-Pilot said:
while you're booted into your System.
Click to expand...
Click to collapse
But what to do if there isn't any system to be booted in? I can power up the phone but it's stucked at the red m.
Shall i just simply flash the images out ouf the zip? (since at my windows machine rsd doesn't work…)
AW: Stuck in Fastboot
Edit the bat and delete the fist 2 adb lines.
adb push root.zip
adb reboot-bootloader
Copy the RazRiRoot2.zip on your external SD and profit :thumbup:
Sent from my XT890
HSD-Pilot said:
Edit the bat and delete the fist 2 adb lines.
adb push root.zip
adb reboot-bootloader
Copy the RazRiRoot2.zip on your external SD and profit :thumbup:
Sent from my XT890
Click to expand...
Click to collapse
I did this, here is a logfile
http://pastebin.com/nn8eNuaZ
after the last step i selected reboot system now in cwm, phone reboots and stays at this "warning bootloader unlocked" message forever
This message replaced the red M after i flashed everything from http://sbf.droid-developers.org/smi/...1FF_fb.xml.zip exept system_image_signed since flashing this gave me an error:
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 687106000 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 581994448 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 475494352 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 371742672 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 266872784 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 172869584 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 67946448 is not a multiple of the block size 4096
fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
[1] 6906 abort (core dumped) fastboot flash system system_signed
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
Prerequisite
1. Unlocked Bootloader
2. TWRP Recovery or OrangeFox Recovery
3. Latest adb & fastboot files
4. Stock ROM ZIP files
5. Stock Recovery [OPTIONAL]
Custom Recovery Method:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1901_flashable_*.zip /sdcard or MTP
3. Wipe data, cache & dalvik (format data if stuck at boot animation)
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip. Your device will have Stock Recovery with Stock ROM. Finally Reboot.
Fastboot Method:
Note: Following process formats internal storage, so backup the internal storage files. If your device is in Stock ROM & somehow system partition is messed up just flash only system.
1. Download required Fastboot files
2. If downloaded 7z files, extract system.img file.
3. Enter
Code:
fastboot -w && fastboot erase system && fastboot flash recovery recovery.img && fastboot flash boot boot.img && fastboot flash vbmeta vbmeta.img && fastboot flash dtbo dtbo.img && fastboot flash system system.img && fastboot reboot
4. It takes a while to flash System partition, have patience.
5. Device reboots to system if everything is flashed successfully.
Stock Recovery Method:
1. Download Stock ROM OZIP Files & Stock Recovery
2. Copy *.ozip to sdcard or internal storage.
2. Goto fastboot & enter fastboot flash recovery recovery.img
3. Reboot to recovery, wipe (1st option). Then go back to main menu Install from storage locate the *.ozip file & install.
Can i install the A.06 zip file into my realme x china?
taolatao123 said:
Can i install the A.06 zip file into my realme x china?
Click to expand...
Click to collapse
Nope.
It looks like the CN variant is using a different key for signing (?) or verifying the boot.img.
I have tried india version boot.img and unofficial LOS16 boot.img, they all fail to boot.
Only the boot.img extracted from CN updates (ozip) can pass the verification.
Unless we get an idea how the f**king verification of boot.img is done, CN variant is pretty hard to crack.
BTW, although the failure screen shows boot/recovery is corrupted when verification fails, the verification doesn't apply to recovery at all.
You can easily install TWRP and boot into recovery.
The TWRP problem is, its model is still considered as global model (1901) not (1901CN), thus it can't apply the converted zip from CN official ozip.
If you want a flashable stock zip, you need to remove the compatible.zip (pretty common for treble rom), then remove the model checking code in update-script.
Can I install Fastboot Method files to Realme X CN (RMX1901CN)?
Is there any way to go Global rom on CN Realme X?
Can't flash system.
I am unable to flash system.img and get error
error: write_sparse_skip_chunk: don't care size 1664534048 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1134061088 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 597009952 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 75220512 is not a multiple of the block size 4096
Sending sparse 'system' 1/5 (524284 KB) error: write_sparse_skip_chunk: don't care size 1664534048 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1664534048 is not a multiple of the block size 4096
OKAY [ 11.870s]
Writing 'system' OKAY [ 0.001s]
Sending sparse 'system' 2/5 (517881 KB) error: write_sparse_skip_chunk: don't care size 1134061088 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1134061088 is not a multiple of the block size 4096
OKAY [ 11.889s]
Writing 'system' FAILED (remote: 'Error: Last flash failed : Bad Buffer Size')
fastboot: error: Command failed
Please help.
@4j17h
Is there any way to flash stock ROM but keep TWRP Recovery.
Maybe, by deleting the recovery.img from zip file???
Please add RMX1901EX_11_A.09 updated TWRP flashable zip file. Global (indian) version.?
ihr3.1416 said:
Can I install Fastboot Method files to Realme X CN (RMX1901CN)?
Is there any way to go Global rom on CN Realme X?
Click to expand...
Click to collapse
Right now there isn't any. Chinese variant users should figure out the way.
Thejayyadav said:
@4j17h
Is there any way to flash stock ROM but keep TWRP Recovery.
Maybe, by deleting the recovery.img from zip file???
Click to expand...
Click to collapse
Sure you can delete recovery.img from zip & flash but still twrp will get replaced with stock recovery once colorOS is booted.
Workaround is
Flash ROM
Flash twrp
Flash vbmeta (use ofox or reboot to fastboot)
Reboot recovery
Flash debloater (https://forum.xda-developers.com/realme-3-pro/how-to/guide-debloater-bootloader-locked-t3965506)
Wipe data or format data if you haven't done already
Reboot System
Follow these steps, don't miss any.
farhantahir said:
I am unable to flash system.img and get error
error: write_sparse_skip_chunk: don't care size 1664534048 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1134061088 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 597009952 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 75220512 is not a multiple of the block size 4096
Sending sparse 'system' 1/5 (524284 KB) error: write_sparse_skip_chunk: don't care size 1664534048 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1664534048 is not a multiple of the block size 4096
OKAY [ 11.870s]
Writing 'system' OKAY [ 0.001s]
Sending sparse 'system' 2/5 (517881 KB) error: write_sparse_skip_chunk: don't care size 1134061088 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1134061088 is not a multiple of the block size 4096
OKAY [ 11.889s]
Writing 'system' FAILED (remote: 'Error: Last flash failed : Bad Buffer Size')
fastboot: error: Command failed
Please help.
Click to expand...
Click to collapse
Try to flash System.img to System Image in recovery or else install flashable ROM.
4j17h said:
Sure you can delete recovery.img from zip & flash but still twrp will get replaced with stock recovery once colorOS is booted.
Workaround is
Flash ROM
Flash twrp
Flash vbmeta (use ofox or reboot to fastboot)
Reboot recovery
Flash debloater (https://forum.xda-developers.com/realme-3-pro/how-to/guide-debloater-bootloader-locked-t3965506)
Wipe data or format data if you haven't done already
Reboot System
Follow these steps, don't miss any.
Click to expand...
Click to collapse
Which vbmeta to flash, one i used after flashing TWRP for first time or stock??
Thejayyadav said:
Which vbmeta to flash, one i used after flashing TWRP for first time or stock??
Click to expand...
Click to collapse
Yes which is around 1kb used after flashing twrp
Stock recovery method:
Does it require unlocked bootlaoder too?
Any one please..
seebani said:
Stock recovery method:
Does it require unlocked bootlaoder too?
Any one please..
Click to expand...
Click to collapse
Yes without unlocked bootloader you can't flash any recovery from fastboot. It's in OP the very first section plus when you want to go back to stock ROM it's understood you have a unlocked bootloader through which you switched ROM
---------- Post added at 05:06 PM ---------- Previous post was at 05:05 PM ----------
@4j17h , you are a life saver! Thanks so much for this ?
4j17h said:
Try to flash System.img to System Image in recovery or else install flashable ROM.
Click to expand...
Click to collapse
hey I am facing the same issue but my phone is stuck in a bootloop and i am not able to boot into recovery mode all i can do is Go into fastboot mode
ANY SOLUTIONS ??? :crying::crying::crying:
kjdirectioner said:
hey I am facing the same issue but my phone is stuck in a bootloop and i am not able to boot into recovery mode all i can do is Go into fastboot mode
ANY SOLUTIONS ??? :crying::crying::crying:
Click to expand...
Click to collapse
Flash vbmeta & twrp
Boot into twrp
Flash ROM ZIP
Format & reboot
4j17h said:
Flash vbmeta & twrp
Boot into twrp
Flash ROM ZIP
Format & reboot
Click to expand...
Click to collapse
Ya i already did that but after flashing every time it automatically restores to its stock recovery
kjdirectioner said:
Ya i already did that but after flashing every time it automatically restores to its stock recovery
Click to expand...
Click to collapse
Flash twrp
Flash debloat zip (get it from 3 Pro guide section)
4j17h said:
Flash twrp
Flash debloat zip (get it from 3 Pro guide section)
Click to expand...
Click to collapse
Ok I'll try Thanks for the help ?
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. TWRP Recovery or OrangeFox Recovery
3. Latest adb & fastboot files
4. Stock ROM ZIP files
5. Stock Recovery [OPTIONAL]
Custom Recovery Method:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1901_flashable_*.zip /sdcard or MTP
3. Wipe data, cache & dalvik (format data if stuck at boot animation)
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip. Your device will have Stock Recovery with Stock ROM. Finally Reboot.
Fastboot Method:
Note: Following process formats internal storage, so backup the internal storage files. If your device is in Stock ROM & somehow system partition is messed up just flash only system.
1. Download required Fastboot files
2. If downloaded 7z files, extract system.img file.
3. Enter
4. It takes a while to flash System partition, have patience.
5. Device reboots to system if everything is flashed successfully.
Stock Recovery Method:
1. Download Stock ROM OZIP Files & Stock Recovery
2. Copy *.ozip to sdcard or internal storage.
2. Goto fastboot & enter fastboot flash recovery recovery.img
3. Reboot to recovery, wipe (1st option). Then go back to main menu Install from storage locate the *.ozip file & install.
Click to expand...
Click to collapse
Is the stock recovery method file for all device ? I mean i m using Indian variant can i flash it ?
---------- Post added at 12:35 PM ---------- Previous post was at 11:37 AM ----------
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. TWRP Recovery or OrangeFox Recovery
3. Latest adb & fastboot files
4. Stock ROM ZIP files
5. Stock Recovery [OPTIONAL]
Custom Recovery Method:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1901_flashable_*.zip /sdcard or MTP
3. Wipe data, cache & dalvik (format data if stuck at boot animation)
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip. Your device will have Stock Recovery with Stock ROM. Finally Reboot.
Fastboot Method:
Note: Following process formats internal storage, so backup the internal storage files. If your device is in Stock ROM & somehow system partition is messed up just flash only system.
1. Download required Fastboot files
2. If downloaded 7z files, extract system.img file.
3. Enter
4. It takes a while to flash System partition, have patience.
5. Device reboots to system if everything is flashed successfully.
Stock Recovery Method:
1. Download Stock ROM OZIP Files & Stock Recovery
2. Copy *.ozip to sdcard or internal storage.
2. Goto fastboot & enter fastboot flash recovery recovery.img
3. Reboot to recovery, wipe (1st option). Then go back to main menu Install from storage locate the *.ozip file & install.
Click to expand...
Click to collapse
After flashing using stock recovery method phone again boot to stock recovery any way to fix this ?