Ok people I need help I'm soft brick I can get into recovery and fastboot but If install a ROM it doesn't pass ASUS Screen and it gets a reboot loop just there
any idea?
I downloading right now asus default firmware to try to put it on SD hope that works cus I don't need a 500$ paperweight
maxrdlf95 said:
Ok people I need help I'm soft brick I can get into recovery and fastboot but If install a ROM it doesn't pass ASUS Screen and it gets a reboot loop just there
any idea?
I downloading right now asus default firmware to try to put it on SD hope that works cus I don't need a 500$ paperweight
Click to expand...
Click to collapse
How did you soft brick your device??
buhohitr said:
How did you soft brick your device??
Click to expand...
Click to collapse
Making stuff
Flashing via fastboot doesn't revive my tablet Now I flashing putting the original Update on the SD card with the original recovery..
Flashing for SD Didn't work either I Fixed my tablet .. mmm let's say it's an advanced thing
Code:
~ # tune2fs -l /dev/block/mmcblk0p2 | grep features
tune2fs -l /dev/block/mmcblk0p2 | grep features
Filesystem features: has_journal resize_inode filetype needs_recovery exten
t sparse_super large_file
~ # e2fsck -f /dev/block/mmcblk0p2
e2fsck -f /dev/block/mmcblk0p2
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p2: 16/27392 files (6.3% non-contiguous), 3650/109568 blocks
~ # tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p2
tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p2
tune2fs 1.41.12 (17-May-2010)
Setting maximal mount count to 1
Setting interval between checks to 86400 seconds
Setting reserved blocks percentage to 0% (0 blocks)
~ # e2fsck -f /dev/block/mmcblk0p2
e2fsck -f /dev/block/mmcblk0p2
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p2: 16/27392 files (6.3% non-contiguous), 1938/109568 blocks
~ # tune2fs -l /dev/block/mmcblk0p2 | grep features
tune2fs -l /dev/block/mmcblk0p2 | grep features
Filesystem features: resize_inode filetype extent sparse_super large_file
~ # e2fsck -f /dev/block/mmcblk0p8
e2fsck -f /dev/block/mmcblk0p8
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 1646715 has zero dtime. Fix<y>? y
y
yes
Deleted inode 1647157 has zero dtime. Fix<y>? yes
Pass 2: Checking directory structure
Entry 'dontpanic' in / (2) has deleted/unused inode 221185. Clear<y>? y
y
yes
Entry 'misc' in / (2) has deleted/unused inode 778241. Clear<y>? yes
Entry 'local' in / (2) has deleted/unused inode 892929. Clear<y>? y
y
yes
Pass 3: Checking directory connectivity
Unconnected directory inode 1400833 (/???)
Connect to /lost+found<y>? yes
Pass 4: Checking reference counts
Inode 2 ref count is 26, should be 24. Fix<y>? y
y
yes
Unattached inode 1237006
Connect to /lost+found<y>? yes
Inode 1237006 ref count is 2, should be 1. Fix<y>? y
y
yes
Inode 1400833 ref count is 3, should be 2. Fix<y>? yes
Unattached inode 1630913
Connect to /lost+found<y>? y
y
yes
Inode 1630913 ref count is 2, should be 1. Fix<y>? yes
Unattached inode 1631458
Connect to /lost+found<y>? y
y
yes
Inode 1631458 ref count is 2, should be 1. Fix<y>? yes
Unattached inode 1655157
Connect to /lost+found<y>? y
y
yes
Inode 1655157 ref count is 2, should be 1. Fix<y>? yes
Unattached inode 1655166
Connect to /lost+found<y>? y
y
yes
Inode 1655166 ref count is 2, should be 1. Fix<y>? yes
Pass 5: Checking group summary information
Block bitmap differences: +(3520--3559) -(831232--831394) -1248476 -1248519 +12
48522 -2826956 -(2827309--2827316) -2828801 -2828805 -(2829826--2829827) +(28298
50--2829853) +2829855 +3133955 +(3134982--3134983) -(6523708--6523717) -6548656
+6548787 -(6624192--6624247) -6636288 +(6636296--6636297) +6636304
Fix<y>? y
y
yes
Free blocks count wrong for group #0 (31180, counted=31109).
Fix<y>? yes
Free blocks count wrong for group #25 (3596, counted=3759).
Fix<y>? y
y
yes
Free blocks count wrong for group #27 (30714, counted=30715).
Fix<y>? yes
Free blocks count wrong for group #38 (32213, counted=32214).
Fix<y>? y
y
yes
Free blocks count wrong for group #86 (25562, counted=25569).
Fix<y>? yes
Free blocks count wrong for group #95 (23279, counted=23289).
Fix<y>? y
y
yes
Free blocks count wrong for group #109 (32252, counted=32254).
Fix<y>? yes
Free blocks count wrong for group #171 (32254, counted=32253).
Fix<y>? y
y
yes
Free blocks count wrong for group #199 (23041, counted=23051).
Fix<y>? yes
Free blocks count wrong for group #202 (26244, counted=26298).
Fix<y>? y
y
yes
Free blocks count wrong (4374231, counted=4374407).
Fix<y>? yes
Inode bitmap differences: +1237006 +1631458 -1646715 -1647157 +1655157 +1655166
Fix<y>? y
y
yes
Free inodes count wrong for group #27 (8191, counted=8192).
Fix<y>? yes
Directories count wrong for group #27 (1, counted=0).
Fix<y>? y
y
yes
Free inodes count wrong for group #95 (8179, counted=8192).
Fix<y>? yes
Directories count wrong for group #95 (11, counted=0).
Fix<y>? y
y
yes
Free inodes count wrong for group #109 (8190, counted=8192).
Fix<y>? yes
Directories count wrong for group #109 (2, counted=0).
Fix<y>? y
y
yes
Free inodes count wrong for group #151 (8175, counted=8174).
Fix<y>? yes
Free inodes count wrong for group #171 (8192, counted=8191).
Fix<y>? y
y
yes
Directories count wrong for group #171 (0, counted=1).
Fix<y>? yes
Free inodes count wrong for group #199 (6581, counted=6580).
Fix<y>? y
y
yes
Free inodes count wrong for group #201 (6796, counted=6798).
Fix<y>? yes
Free inodes count wrong for group #202 (7800, counted=7798).
Fix<y>? y
y
yes
Free inodes count wrong (1796954, counted=1796967).
Fix<y>? yes
/dev/block/mmcblk0p8: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p8: 13465/1810432 files (4.2% non-contiguous), 2856689/7231096
blocks
~ # tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p8
tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p8
tune2fs 1.41.12 (17-May-2010)
Setting maximal mount count to 1
Setting interval between checks to 86400 seconds
Setting reserved blocks percentage to 0% (0 blocks)
~ # e2fsck -f /dev/block/mmcblk0p8
e2fsck -f /dev/block/mmcblk0p8
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p8: 13465/1810432 files (4.2% non-contiguous), 2856689/7231096
blocks
~ # tune2fs -l /dev/block/mmcblk0p8 | grep features
tune2fs -l /dev/block/mmcblk0p8 | grep features
Filesystem features: resize_inode filetype extent sparse_super large_file
~ # exit
exit
C:\Program Files (x86)\Android\android-sdk\platform-tools>
what were you doing which caused the brick. have you tried to push a new rom via adb, can you get into recovery. if you can get into recovery, wipe your entire phone then push a new rom via adb, it is possible to get corroptions putting the sd card in ur computer transfring a rom them putting the sd back in your tablet, bypass all that and us adb
Sent from my ASUS Transformer Pad TF700T using Xparent Blue Tapatalk 2
Are you on the right bootloader for the ROM you are trying to flash?
pals0007 said:
what were you doing which caused the brick. have you tried to push a new rom via adb, can you get into recovery. if you can get into recovery, wipe your entire phone then push a new rom via adb, it is possible to get corroptions putting the sd card in ur computer transfring a rom them putting the sd back in your tablet, bypass all that and us adb
Sent from my ASUS Transformer Pad TF700T using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
It was a journaling thing man this shouldn't happen to a normal user I think
maxrdlf95 said:
It was a journaling thing man this shouldn't happen to a normal user I think
Click to expand...
Click to collapse
Trying to flash Data2SD by any chance eh!
Sent from a tablet optimized by CleanROM 2.3
Thats OK said:
Trying to flash Data2SD by any chance eh!
Sent from a tablet optimized by CleanROM 2.3
Click to expand...
Click to collapse
It wasn't Data2SD I was disabling Journaling on the Original Tablet partition.. hehe
I was trying to get 4.4.2 (Omnirom / CM11.1) on my Xoom.
The only problem I facing is TWRP is asking for password or else it will have problem mounting to cache.
This lead to cannot wipe cache and cannot wipe cache\dalvik.
I search the forum up and down and people comment that the partition is corrupt that TWRP trying to recover it.
So my question is how can I repair or recreate the partition.
What tool should I use?
Even if it is using adb shell, what kind of program I need to push into the phone.
Hope someone can help me out.
I did try to play around like 5 hours.
At first TWRP complaint that cannot mount /cache
Then I try use CWM recovery to wipe cache and dalvik. Then only install TWRP (without big part). Again I wipe cache and dalvik.
Then when I install TWRP (with big part) and no longer complaint cannot mount cache.
But it keep showing update partition details.
When I try to wipe data it will be unsuccessful.
Hope experience people can guide me. Really want to see my motorola xoom (everest) to be on kit kat.
kblade29m said:
I was trying to get 4.4.2 (Omnirom / CM11.1) on my Xoom.
The only problem I facing is TWRP is asking for password or else it will have problem mounting to cache.
This lead to cannot wipe cache and cannot wipe cache\dalvik.
I search the forum up and down and people comment that the partition is corrupt that TWRP trying to recover it.
So my question is how can I repair or recreate the partition.
What tool should I use?
Even if it is using adb shell, what kind of program I need to push into the phone.
Hope someone can help me out.
I did try to play around like 5 hours.
At first TWRP complaint that cannot mount /cache
Then I try use CWM recovery to wipe cache and dalvik. Then only install TWRP (without big part). Again I wipe cache and dalvik.
Then when I install TWRP (with big part) and no longer complaint cannot mount cache.
But it keep showing update partition details.
When I try to wipe data it will be unsuccessful.
Hope experience people can guide me. Really want to see my motorola xoom (everest) to be on kit kat.
Click to expand...
Click to collapse
hello...
same problem on my xoom Wingray
if i find a fix i posted here
Good luck
ankorez said:
hello...
same problem on my xoom Wingray
if i find a fix i posted here
Good luck
Click to expand...
Click to collapse
Same here too... wingray also
As far as I can tell, you didn't follow the directions. Re-start the BigPart process from the beginning, and when TWRP asks you for a password, just ignore that and press the Home icon at the top. Tap the Wipe tab, and there will be two options, Advanced and Format Data, along with the slider at the bottom for a Factory Reset. Tap the Format Data tab, type yes when prompted, and hit enter/return. Then follow the rest of the steps in the BigPart process.
And, please, if you're going to BigPart, just pretend CWM doesn't exist, because all it's going to do is mess things up for you.
Thanks webeougher. I revisit the steps and this time successfully to make it work.
http://forum.xda-developers.com/showthread.php?t=2506997
Step 1 - Preparation
Format MicroSD to Fat32 and copied the following files
- R.A.H._TWRPv2.6.3_BigPart_selinux.zip
- cm-11-20140216-UNOFFICIAL-1501+0100-everest.zip
- pa_gapps-modular-full-4.4.2-20131230-signed.zip
Step 2 - Flash Recovery to TWRP
- Has Android SDK
- Extract R.A.H._TWRPv2.6.3.zip to get recovery.img
- Set Xoom to Fastboot mode by press vol down before dual core logo appeared.
- In command line, type fastboot flash recovery recovery.img
Step 3 - Boot into Recovery
- Set Xoom to Recovery mode by press vol down after dual core logo appeared for 3 seconds.
- Notice at this step you will not have problem mounting to /cache partition.
Step 4 - Create BigPart
Refer to http://forum.xda-developers.com/showthread.php?t=2506997
Go through step by step.
- Use Install to flash R.A.H._TWRPv2.6.3_BigPart_selinux.zip (No Reboot)
- Home - Wipe - Advanced Wipe -> Wipe Dalvik Cache, System, Cache, Data, Internal Storage. Exclude sdcard. (No Reboot)
- Home - Reboot - Recovery -> Don't Install SuperSU (Rebooted into Recovery)
- Home - Wipe - Format Data - Type yes (No Reboot)
- Home - Wipe - Advanced Wipe -> Wipe system and cache (No Reboot)
- Home - Reboot - Recovery -> Don't Install SuperSu (Rebooted into Recovery)
- Home - Mount - Check System and Uncheck System (Just testing only. No Reboot)
Step 5 - Install Rom and Gapps
- Home - Install - cm-11-20140216-UNOFFICIAL-1501+0100-everest.zip and pa_gapps-modular-full-4.4.2-20131230-signed.zip
- Swipe to Flash
- Wipe Dalvik and Cache
- Home - Mount - Reboot - System
- Give 5 - 10 minutes for the installation to complete. Not a boot loop. Just take longer time to finish installation.
Enjoy the CM11 (4.4.2) on Xoom
Troubleshooting:
Just incase if you have problem with partition (Step 3), where you notice TWRP already have with partition
- Flash Clockworkmod Recovery
- Remove SDcard
- Reboot into CWM recovery
- Mount and Storage - Format system, cache, data
- Advanced - Fix Permission
- Flash TWRP Recovery (Back to step 2)
kblade29m said:
Thanks webeougher. I revisit the steps and this time successfully to make it work.
http://forum.xda-developers.com/showthread.php?t=2506997
Step 1 - Preparation
...
Step 2 - Flash Recovery to TWRP
...
Step 3 - Boot into Recovery
...
Step 4 - Create BigPart
...
Step 5 - Install Rom and Gapps
...
Troubleshooting:
Just incase if you have problem with partition (Step 3), where you notice TWRP already have with partition
- Flash Clockworkmod Recovery
- Remove SDcard
- Reboot into CWM recovery
- Mount and Storage - Format system, cache, data
- Advanced - Fix Permission
- Flash TWRP Recovery (Back to step 2)
Click to expand...
Click to collapse
There is almost the same problem with my "UMTS_Everest". I tried to follow all these instructions (includin the "troubleshooting part". But I'm not able to flash another recovery anymore with fastboot nor with TRWP (CWM e.g.) :crying:
I tried also everything, but there is (has never been) no /data-partition anymore and it says "unable to mount /cache" all the time in TWRP
There is no /data-partition visible to mount in TRWP.
Try again. Hope you still can enter fastboot mode.
If you use adb and fastboot, I sure you can get it work.
If you using Windows, make sure usb installed with right driver.
Make device in fastboot mode.
Power + Vol down (hold before motorola logo appear).
Screen will show some text related to fastboot.
When you type "fastboot devices" you able to see your device.
fastboot flash recovery clockwork-recovery.img
fastboot reboot
If you can enter clockworkmod recovery u can format all the mount. To enter recovery.
Power + Vol down (hold after Motorola logo appear for 3 second). When recovery text appeared press Vol up.
Sent from my Nexus 4 using xda app-developers app
kblade29m said:
fastboot flash recovery clockwork-recovery.img
fastboot reboot
Click to expand...
Click to collapse
fastboot flash recovery fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
or fastboot flash recovery recovery-clockwork-touch-6.0.3.2-everest.img
sending 'recovery' (5270 KB)...
OKAY [ 0.511s]
writing 'recovery'...
OKAY [ 0.523s]
finished. total time: 1.034s
status done!
Still TWRP
peterkling said:
fastboot flash recovery fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
or fastboot flash recovery recovery-clockwork-touch-6.0.3.2-everest.img
sending 'recovery' (5270 KB)...
OKAY [ 0.511s]
writing 'recovery'...
OKAY [ 0.523s]
finished. total time: 1.034s
status done!
Still TWRP
Click to expand...
Click to collapse
Hello,
Ihave the same issue.
You have fixed it ?
How I fixed mine
Hi,
I had the same Problem some weeks ago. After trying to install a newer custom Rom which did not boot I neither was able to wipe dalvik nore had a System Partition anymore.
With big help from HDwally I was able to fix it. The first Thing I did was to install a stock Rom.
For this you have to install the Motorola USB Driver
https://motorola-global-portal-de.custhelp.com/app/answers/detail/a_id/91819
and RSD lite.
http://www.chip.de/downloads/RSD-Lite_49139659.html
You might find a suitable stock Rom here:
http://forum.xda-developers.com/showthread.php?t=1049485
After I installed this my Xoom worked fine again. But I installed a crm after that again following these instructions and I was able to install a custom Rom again.
http://forum.xda-developers.com/showthread.php?t=2506997
I hope you will be able to fix your xoom.
Good luck..
Alexander
onlyage said:
Hi,
I had the same Problem some weeks ago. After trying to install a newer custom Rom which did not boot I neither was able to wipe dalvik nore had a System Partition anymore.
With big help from HDwally I was able to fix it. The first Thing I did was to install a stock Rom.
For this you have to install the Motorola USB Driver
https://motorola-global-portal-de.custhelp.com/app/answers/detail/a_id/91819
and RSD lite.
http://www.chip.de/downloads/RSD-Lite_49139659.html
You might find a suitable stock Rom here:
http://forum.xda-developers.com/showthread.php?t=1049485
After I installed this my Xoom worked fine again. But I installed a crm after that again following these instructions and I was able to install a custom Rom again.
http://forum.xda-developers.com/showthread.php?t=2506997
I hope you will be able to fix your xoom.
Good luck..
Alexander
Click to expand...
Click to collapse
Hello,
thank you, but don't work for me.
is there another solution ?
I still have not solved my problem, there's really no way to fix my xoom
If anyone is still looking, this article explains really well:
http://www.djsmobiles.com/2014/02/h...epartition-upgrade-on-your-motorola-xoom.html
Fuuuq! Did the BigPart partition and forgot to back up my current ROM, so when I attempt to reinstall I don't see my .zip plus when I reboot. I get the OS not installed.
Mz600 / Vzw / CDMA+Wifi
Got mine to work
I know this is a dead thread, but just in case someone comes here looking for help...
I tried all the directions, and couldn't get stuff to mount. always fails. I finally got it. Not sure why this worked...
Flashed TWRP through fastboot.
Then flashed recovery-Tiamat-R4c-100611-1150-cwm.img
formatted each partition and then mounted them
then flashed the R.A.H._TWRPv2.6.3_BigPart_selinux.zip
Then rebooted recovery
Then in TWRP it actually let me format each individual partition one at a time.
Then it let me flash Omni
Not sure why TWRP (regardless of version) would not let me mount. Only CW would. anyways, hope this helps.
stingray (verzion xoom) information
I had trouble getting my cache to mount. kept giving me an error of E:Unable to mount /cache/. After beating my head for about 5-7 hours. I found the post quoted below. I used TWRP recovery and adb sideloaded R.A.H._TWRPv2.6.3_BigPart_selinux.zip b/c I couldn't figure out how to mount the SDCARD to just drag and drop the file in my windows Operating System.
Still nothing. Then I followed the post below under STEP 4 VERY CAREFULLY where it instructed me to format the ENTIRE INTERNAL STORAGE ONLY. Did that, installed R.A.H._TWRPv2.6.3_BigPart_selinux.zip and the cache error went away. Followed the REST of step 4 and FINALLY CM11 ON MY WORE OUT MOTOROLA XOOM VERIZON (STINGRAY) TABLET! GOD SPEED AND HAPPY NEW YEARS!! :good::good:
kblade29m said:
Thanks webeougher. I revisit the steps and this time successfully to make it work.
http://forum.xda-developers.com/showthread.php?t=2506997
Step 1 - Preparation
Format MicroSD to Fat32 and copied the following files
- R.A.H._TWRPv2.6.3_BigPart_selinux.zip
- cm-11-20140216-UNOFFICIAL-1501+0100-everest.zip
- pa_gapps-modular-full-4.4.2-20131230-signed.zip
Step 2 - Flash Recovery to TWRP
- Has Android SDK
- Extract R.A.H._TWRPv2.6.3.zip to get recovery.img
- Set Xoom to Fastboot mode by press vol down before dual core logo appeared.
- In command line, type fastboot flash recovery recovery.img
Step 3 - Boot into Recovery
- Set Xoom to Recovery mode by press vol down after dual core logo appeared for 3 seconds.
- Notice at this step you will not have problem mounting to /cache partition.
Step 4 - Create BigPart
Refer to http://forum.xda-developers.com/showthread.php?t=2506997
Go through step by step.
- Use Install to flash R.A.H._TWRPv2.6.3_BigPart_selinux.zip (No Reboot)
- Home - Wipe - Advanced Wipe -> Wipe Dalvik Cache, System, Cache, Data, Internal Storage. Exclude sdcard. (No Reboot)
- Home - Reboot - Recovery -> Don't Install SuperSU (Rebooted into Recovery)
- Home - Wipe - Format Data - Type yes (No Reboot)
- Home - Wipe - Advanced Wipe -> Wipe system and cache (No Reboot)
- Home - Reboot - Recovery -> Don't Install SuperSu (Rebooted into Recovery)
- Home - Mount - Check System and Uncheck System (Just testing only. No Reboot)
Step 5 - Install Rom and Gapps
- Home - Install - cm-11-20140216-UNOFFICIAL-1501+0100-everest.zip and pa_gapps-modular-full-4.4.2-20131230-signed.zip
- Swipe to Flash
- Wipe Dalvik and Cache
- Home - Mount - Reboot - System
- Give 5 - 10 minutes for the installation to complete. Not a boot loop. Just take longer time to finish installation.
Enjoy the CM11 (4.4.2) on Xoom
Troubleshooting:
Just incase if you have problem with partition (Step 3), where you notice TWRP already have with partition
- Flash Clockworkmod Recovery
- Remove SDcard
- Reboot into CWM recovery
- Mount and Storage - Format system, cache, data
- Advanced - Fix Permission
- Flash TWRP Recovery (Back to step 2)
Click to expand...
Click to collapse
I believe I flashed a 4.1.2 boot.img file a modified rooted version and possibly also reset before a proper flashing in twrp 2.8.6.0. could be one or the other. Both.
No go on any of the suggested fixes.
I'm experiencing same issues.
Specifically, I am unable to mount /data & /cache partitions in TWRP v2.8.6.0 Bigpart Recovery.
I am unable to recover them both through the repair function and Change File System function in TWRP.
Tried all configurations of file system type and sequence of changing the file system types of system, ,data, cache.
The error that appears after attempting to change file system of data, system,cache, all of them is as follows
ERROR: sbin/e2fsk -p /dev/block/mmcblk1p10 process ended with ERROR=8
unable to repair '/data'.
error repairing file system.
I can successfully erase system, boot, userdata, recovery partitions and flash any .img to according partitions with fastboot commands (i.e. fastboot erase cache fastboot flash recovery recovery.img) Although this does not successfully flash anything. Fastboot says it does but recovery remains the same as well as the boot animation which im assuming is in the boot.img file.
I believe im looking for the next viable option which is to rebuild the systems internal data? I dont know via fastboot?
Can anyone help? Could someone explain how to what actually is missing here?
I was successful with e2fsck through adb on my userdata partition and using an alternate superblock. But not I am unsuccessful with it on my cache. These are the only two partions that I am unable to mount in TWRP. I am not even sure if fixing these is proper. I attempted to go in on the /dev/block/platform/sdhci-tegra.3/mmcblkop9 and 10 which are damaged as well I learned when I attempted repair on TWRP on cache.
Code:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6ne2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
by-name/cache
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
by-name/cache
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
by-name/cache
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n e2fsck -b /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b /dev/block/platform/sdhci-tegra.3/by-name/cache
Invalid non-numeric argument to -b ("/dev/block/platform/sdhci-tegra.3/by-name/c
ache")
~ # ←[6n e2fsck -p 32768 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -p 32768 /dev/block/platform/sdhci-tegra.3/by-name/cache
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # ←[6n e2fsvk -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsvk -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
/sbin/sh: e2fsvk: not found
~ # ←[6n e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
by-name/cache
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n e2fsck -b 8193 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -b 8193 /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
by-name/cache
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6nmke2fs -n /dev/block/platform/sdhci-tegra.3/by-name/cache
mke2fs -n /dev/block/platform/sdhci-tegra.3/by-name/cache
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32768 inodes, 131072 blocks
6553 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=134217728
4 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
~ # ←[6ne2fsck -p /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck -p /dev/block/platform/sdhci-tegra.3/by-name/cache
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform
/sdhci-tegra.3/by-name/cache
/dev/block/platform/sdhci-tegra.3/by-name/cache:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6ne2fsck -p /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -p /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform
/sdhci-tegra.3/mmcblk0p9
/dev/block/platform/sdhci-tegra.3/mmcblk0p9:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6nmke2fs -n /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs -n /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32768 inodes, 131072 blocks
6553 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=134217728
4 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
~ # ←[6ne2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
mmcblk0p9
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6ne2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
mmcblk0p9
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6ne2fsck -b 32768 /dev/block/platform/sdhci-tegra.3
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Is a directory while trying to open /dev/block/platform/sdhci-tegra.3
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6nmke2fs -n /dev/block/platform/sdhci-tegra.3
mke2fs -n /dev/block/platform/sdhci-tegra.3
mke2fs 1.41.14 (22-Dec-2010)
/dev/block/platform/sdhci-tegra.3 is not a block special device.
Proceed anyway? (y,n) y
y
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
~ # ←[6ne2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p8
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p8
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/sdhci-tegra.3/mmcblk0p8: clean, 11/16384 files, 2089/65536 b
locks
~ # ←[6ne2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
mmcblk0p9
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6ne2fsck -n 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -n 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # ←[6ne2fsck -b /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b /dev/block/platform/sdhci-tegra.3/mmcblk0p9
Invalid non-numeric argument to -b ("/dev/block/platform/sdhci-tegra.3/mmcblk0p9
")
~ # ←[6ne2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b 32768 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
mmcblk0p9
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6nmke2fs -n /dev/block/platform/sdhci-tegra.3
mke2fs -n /dev/block/platform/sdhci-tegra.3
mke2fs 1.41.14 (22-Dec-2010)
/dev/block/platform/sdhci-tegra.3 is not a block special device.
Proceed anyway? (y,n) y
y
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
~ # ←[6nmke2fs -n /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs -n /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32768 inodes, 131072 blocks
6553 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=134217728
4 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
~ # ←[6nmke2fs -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs: invalid block size - 98304
~ # ←[6nmke2fs -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
mke2fs: invalid block size - 98304
~ # ←[6ne2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck -b 98304 /dev/block/platform/sdhci-tegra.3/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/block/platform/sdhci-tegra.3/
mmcblk0p9
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n
---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------
MZ604 US WIFI Can someone pull and send me the partitions files in dev/block/platform/sdhci-tegra.3? Will replacing and overwriting all my mmcblk0, mmcblko9p1, mmcblk0p10, ect. repair the issue of not being able to mount /data & /cache? or would just someone pulling files form this folder in the picture be sufficent. I say this because if i understand correctly the /userdata and /cache are the culprits, that is the root of the damage. Not sure if im making sense but I hope someone has some advice.
Here is a list of all the partitions on MZ604 Motorola Xoom. I obtained a few list using different commands. Take a look.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Owner>cd c:\adb\adb
c:\adb\adb>adb shell
~ # ←[6nls -l \dev\block\platform\sdchi-tegra.3\by-name
ls -l \dev\block\platform\sdchi-tegra.3\by-name
devblockplatformsdchi-tegra.3by-name: No such file or directory
~ # ←[6nls -l \dev\block
ls -l \dev\block
devblock: No such file or directory
~ # ←[6nls \dev\block
ls \dev\block
devblock: No such file or directory
~ # ←[6nls -al \dev\block
ls -al \dev\block
devblock: No such file or directory
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 98304 zram0
253 1 98304 zram1
179 0 31162368 mmcblk0
179 1 3072 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 12288 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 1048576 mmcblk0p8
259 1 524288 mmcblk0p9
259 2 29525504 mmcblk0p10
~ # ←[6ncat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
~ # ←[6ncat /proc/mtd
cat /proc/mtd
dev: size erasesize name
~ # ←[6nls -l /dev/block
ls -l /dev/block
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- root root 7, 0 1970-01-02 14:15 loop0
brw------- root root 7, 1 1970-01-02 14:15 loop1
brw------- root root 7, 2 1970-01-02 14:15 loop2
brw------- root root 7, 3 1970-01-02 14:15 loop3
brw------- root root 7, 4 1970-01-02 14:15 loop4
brw------- root root 7, 5 1970-01-02 14:15 loop5
brw------- root root 7, 6 1970-01-02 14:15 loop6
brw------- root root 7, 7 1970-01-02 14:15 loop7
brw------- root root 179, 0 1970-01-02 14:15 mmcblk0
brw------- root root 179, 1 1970-01-02 14:15 mmcblk0p1
brw------- root root 259, 2 1970-01-02 14:15 mmcblk0p10
brw------- root root 179, 2 1970-01-02 14:15 mmcblk0p2
brw------- root root 179, 3 1970-01-02 14:15 mmcblk0p3
brw------- root root 179, 4 1970-01-02 14:15 mmcblk0p4
brw------- root root 179, 5 1970-01-02 14:15 mmcblk0p5
brw------- root root 179, 6 1970-01-02 14:15 mmcblk0p6
brw------- root root 179, 7 1970-01-02 14:15 mmcblk0p7
brw------- root root 259, 0 1970-01-02 14:15 mmcblk0p8
brw------- root root 259, 1 1970-01-02 14:15 mmcblk0p9
drwxr-xr-x root root 1970-01-02 14:15 platform
brw------- root root 253, 0 1970-01-02 14:15 zram0
brw------- root root 253, 1 1970-01-02 14:15 zram1
~ # ←[6n
c:\adb\adb>
No list told me exactly which partition was my /data and/cache but as you can see when I run the "Repair" function on my Data and Cache in TWRP 2.8.6.0, the log returns an error to which file it is attempting to repair respectively.
Repairing Data using e2fsk . . .
E: /sbin/e2fsk -p /dev/block/mmcblk0p10 process ended with ERROR=8
E: Unable to repair '/data' .
E: Error repairing file system.
E: Unable to mount '/data/' .
So from there I wanted to rebuild them due to the fact that they are indeed corrupt. Since I was unsuccessful using the "Change File System" function and "Format" function in TWRP 2.8.6.0 as well as unsuccessful using "fastboot format userdata' command in Fastboot I decided to use a command in ADB, mke2fs -T ext4 /dev/block/mmcblk0p9 and mke2fs -T ext4 /dev/block/mmcblk0p10. Here is the terminal showing these commands. . .
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Owner>cd c:\adb\adb
c:\adb\adb>adb shell
~ # ←[6nmke2fs -T ext4 /dev/block/mmcblk0p9
mke2fs -T ext4 /dev/block/mmcblk0p9
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32768 inodes, 131072 blocks
6553 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=134217728
4 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # ←[6nmke2fs -T ext4 /dev/block/mmcblk0p10
mke2fs -T ext4 /dev/block/mmcblk0p10
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1847776 inodes, 7381376 blocks
369068 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
226 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # ←[6nmount /dev/block/mmcblk0p9
mount /dev/block/mmcblk0p9
mount: mounting /dev/block/mmcblk0p9 on /cache failed: Invalid argument
~ # ←[6nmount /data
mount /data
mount: mounting /dev/block/mmcblk0p10 on /data failed: Invalid argument
~ # ←[6nmount /dev/block/mmcblk0p9
mount /dev/block/mmcblk0p9
mount: mounting /dev/block/mmcblk0p9 on /cache failed: Invalid argument
~ # ←[6nmount /data/media
mount /data/media
mount: can't find /data/media in /etc/fstab
~ # ←[6nreboot
reboot
c:\adb\adb>
Indeed neither of them are able to mount. Am I mistaken when i read these logs it says that these "done" but they do not appear to be as the 0's imply.
Still no fix yet
Is it a probable solution to use the sdcard as a mounting point for these partitions ( /data, /cache)? I cant fully understand it yet but Ive seen some people somehow do this with internal memory and stuff with these specific partitons.
Follow https://stackoverflow.com/questions...ack-and-flash-system-img-ext4-file-using-odin
a) Modifying
With
Code:
simg2img system.img.ext4 system.img
, you will get a raw image file named system.img
With
Code:
mkdir system
, create directory to mount system.img
With
Code:
sudo mount -t ext4 -o loop system.img system/
you will get all files of system.img in system folder
example: edit init.rc
With
Code:
ls -l system/init.rc
note permissions: 750
With
Code:
sudo chmod 777 system/init.rc
give write permissions
With
Code:
sudo echo "#MODIFICATION " >> system/init.rc
done some modification in init.rc
With
Code:
sudo chmod 750 init.rc
reset init.rc to the noted permissions
b) Calculate system sector size (Example)
With
Code:
tune2fs -l system.img | grep "Block size\|Block count"
you will get block size and count
With
Code:
echo $((1553064 * 4096))
multiply both results. I got 6361350144
c) Packing (Example)
With
Code:
sudo make_ext4fs -s -l 6361350144 -a system system_new.img sys/
you will get system_new.img “Android Sparse Image” that has all changes
With
Code:
sudo umount system
unmount the system directory
With
Code:
rm -fr system
delete the system directory
If you have a system.img file not system.img.ext4, maybe it's ext4 type just rename and delete ext4 after ".img" then follow the instructions. You may want to edit or delete but stumble on permissions, just type
Code:
sudo nautilus
and you can do it with nautilus explorer as it is root explorer.
this method is wrong
Could not build the correct package
Specifically, you can compare tune2fs -l system.img
Like this
```
Filesystem volume name: system
Last mounted on: /home/xs/tools/roms/SM-G892A_ATT/images/system
Filesystem UUID: 4c64e17e-22c3-54ec-bc54-14deddbf5036
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: journal_data_ordered user_xattr acl discard
Filesystem state: clean
Errors behavior: Panic
Filesystem OS type: Linux
Inode count: 289152
Block count: 1156446
Reserved block count: 0
Free blocks: 81485
Free inodes: 281937
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8032
Inode blocks per group: 502
Flex block group size: 16
Filesystem created: Wed Dec 31 23:00:00 2008
Last mount time: Sun Jul 17 18:00:08 2022
Last write time: Sun Jul 17 18:12:50 2022
Mount count: 2
Maximum mount count: 36
Last checked: Wed Dec 31 23:00:00 2008
Check interval: 15552000 (6 months)
Next check after: Mon Jun 29 23:00:00 2009
Lifetime writes: 69 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 0b0112c3-9689-5f54-ab9d-304e9f9e0ec7
Journal backup: inode blocks
```
xs23933 said:
this method is wrong
Could not build the correct package
Specifically, you can compare tune2fs -l system.img
Like this
```
Filesystem volume name: system
Last mounted on: /home/xs/tools/roms/SM-G892A_ATT/images/system
Filesystem UUID: 4c64e17e-22c3-54ec-bc54-14deddbf5036
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: journal_data_ordered user_xattr acl discard
Filesystem state: clean
Errors behavior: Panic
Filesystem OS type: Linux
Inode count: 289152
Block count: 1156446
Reserved block count: 0
Free blocks: 81485
Free inodes: 281937
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8032
Inode blocks per group: 502
Flex block group size: 16
Filesystem created: Wed Dec 31 23:00:00 2008
Last mount time: Sun Jul 17 18:00:08 2022
Last write time: Sun Jul 17 18:12:50 2022
Mount count: 2
Maximum mount count: 36
Last checked: Wed Dec 31 23:00:00 2008
Check interval: 15552000 (6 months)
Next check after: Mon Jun 29 23:00:00 2009
Lifetime writes: 69 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 0b0112c3-9689-5f54-ab9d-304e9f9e0ec7
Journal backup: inode blocks
```
Click to expand...
Click to collapse
Use tune2fs -l system.img to view system.img.
found the original system.img
Default mount options: journal_data_ordered user_xattr acl discard
Errors behavior: Panic
Unpack (do nothing) the repacked system_new.img
Default mount options: user_xattr acl
Errors behavior: Continue
What's going on here?
Can make "Default mount options: user_xattr acl" packaged as "Default mount options: journal_data_ordered user_xattr acl discard"
?
You are missing the fs_config and file_context files when calling the make_ext4fs binary. Anyone know how to generate those on the fly?
how do get a system.img from a super.img file?