Hi there.
I'm trying to do port CWM for Xperia J for a locked bootloader.
Everything works except restoring backup /system:
Code:
Checking MD5 sums...
boot.img: OK
cache.ext4.dup: OK
data.ext4.dup: OK
system.ext4.dup: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2012-12-29.00.19.49//system.ext4.dup
Restoring system...
Creating filesystem with parameters:
Size: 681574400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6944
Inode size: 256
Journal blocks: 2600
Label:
Blocks: 166400
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/41664 inodes and 5415/166400 blocks
Unable to copy file ./app/AccessoryKeyDispatcher.apk
system
app
AccessoryKeyDispatcher.apk
Error while restoring /system!
Then the phone will not start. I need reflash fw (recovery doesn't work then because it is on /system partition - locked bl)
Related
hello,
Question on this post, I have no access to answer
http://forum.xda-developers.com/showthread.php?t=1081239
Thanks, good work to unpack the .img file.
I have a problem
repacking factoryfs_custom.img only 10,2*Mio (10678552 octets)
Code:
[email protected]:/home/max/ext4_utils# mkdir tempdir; mount -o loop output.img tempdir
[email protected]:/home/max/ext4_utils# ./mkuserimg.sh -s /some/directory/with/files ./factoryfs_custom.img ext4 ./temp 512M
in mkuserimg.sh PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
./make_ext4fs -s -l 512M -a ./temp ./factoryfs_custom.img /some/directory/with/files
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 10/32768 inodes and 4205/131072 blocks
[email protected]:/home/max/ext4_utils# ls -l factoryfs_custom.img
-rw-r--r-- 1 root root 10678552 2011-05-28 09:57 factoryfs_custom.img
[email protected]:/home/max/ext4_utils#
what is the problem?
sorry for my bad English
Thanks
Can we move my question in the original post?
http://forum.xda-developers.com/showthread.php?t=1081239
Thank
max30 said:
Can we move my question in the original post?
http://forum.xda-developers.com/showthread.php?t=1081239
Thank
Click to expand...
Click to collapse
It remains for me to write the six missing messages to be able to ask my question in the right place
max30 said:
It remains for me to write the six missing messages to be able to ask my question in the right place
Click to expand...
Click to collapse
I can go post in the right place now
Hi Folks,
I have tried everything...... But I can't get my BRICKED device back to life! Pleae help, the person who will FIX this wil be donated $20,- for his help, because i've tried everything that I know.
The problem is:
I have a TF101 and it's BRICKED
It has ClockworkMod Recovery v6.0.1.3 installed, TWRP is also recognized at last time I was live and kickin in ROM MANAGER, but YES I was stupid and flashed ClockworkMod Recovery v6.0.1.3. Now I can't get /sdcard/ mounted. ADB drivers can not be installed even in APX modus windows 8,7, and XP are all saying UNKNOWN DEVICE.
When I try to format /system the log says:
Formating /system ...
Done.
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
LabeL:
Blocks: 131072
Block groups: 4
Reserved block gorup size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Done.
I:Can't format unknown volume: /sdcard
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
I can't push a rom to anywhere with ADB
Please help me!!!! You'll earn $ 20,- when I get my device fixed with TWRP running and a good ROM.
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Erik Stroot said:
Hi Folks,
I have tried everything...... But I can't get my BRICKED device back to life! Pleae help, the person who will FIX this wil be donated $20,- for his help, because i've tried everything that I know.
The problem is:
I have a TF101 and it's BRICKED
It has ClockworkMod Recovery v6.0.1.3 installed, TWRP is also recognized at last time I was live and kickin in ROM MANAGER, but YES I was stupid and flashed ClockworkMod Recovery v6.0.1.3. Now I can't get /sdcard/ mounted. ADB drivers can not be installed even in APX modus windows 8,7, and XP are all saying UNKNOWN DEVICE.
When I try to format /system the log says:
Formating /system ...
Done.
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
LabeL:
Blocks: 131072
Block groups: 4
Reserved block gorup size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Done.
I:Can't format unknown volume: /sdcard
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
I can't push a rom to anywhere with ADB
Please help me!!!! You'll earn $ 20,- when I get my device fixed with TWRP running and a good ROM.
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
This is the TF201 forums
flumpster said:
This is the TF201 forums
Click to expand...
Click to collapse
I have moved this thread to the right forum!
Thanks for telling me!
Hi guys, I Have a Xperia P LT22i Black and I'm here because I can't restore my backups that I always used, but now is useless. I'm on same kernel (Sony stock), same FW (6.2.A.1.100) and can't backup anymore, always give me error while restoring those 2. Here is last_log from /cache/recovery.
Backing up .android_secure...
.
com.trust5.odp-1.asec
com.quoord.tapatalkxda.activity-1.a
com.loudtalks-1.asec
com.whatsapp.wallpaper-1.asec
com.music.download-1.asec
com.facebook.orca-1.asec
me.pou.app-2.asec
com.kiloo.subwaysurf-2.asec
com.davidamado.MetalGearOuterHeaven
Backing up cache...
.
lost+found
dalvik-cache
recovery
last_log
log
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
chmod: /sdcard/clockworkmod/blobs/02c/§☻‼/♀~|♫: No such file or directory
chmod: /sdcard/clockworkmod/blobs/235/∟/☺>☼>♣~: No such file or directory
Backup complete!
Checking MD5 sums...
boot.img: OK
cache.ext4.dup: OK
data.ext4.dup: OK
system.ext4.dup: OK
.android_secure.vfat.dup: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2013-06-30.03.16.22//data.ex
t4.dup
Restoring data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Discard failed
Unable to copy file ./backup/processed
data
user
0
idd
etc
bluetooth_bdaddr
wlan_macaddr
light_themes
GNB_DEBUG.txt
backup
processed
Error while restoring /data!
Click to expand...
Click to collapse
Can someone answer that? Thank you!!
I had a similar problem with twrp recently. I had to completely reflash my rom. I ended up totally deleting the whole twrp folder
And after re trying making and restoring a new backup all worked.
I could only assume corrupted data in that folder caused the issue
Sent from my 4.2.2 Xperia S via Tapatalk
Reflashing d entire rom is d only way ............
so as i did so
Yeah, I had to start all over, some told me to change the format of the backup, but when I press to change the format, it stuck and i have to force reboot the phone. Can't change the format, anyone know how to reinstall CWM or delete CWM? So I can install it fresh again?
Hi all!
I have a tablet device Digma CITI 7507 4g, and have a task to put custom application to firmware to "priv-apps'.
So, what have i done:
1. Taken stock FW from manufacturer site.
2. Inside archive i found .pac file, i unpack that file with Spreatrum ResearchDownload tool
3. After unpack i found several files including some img's, and system.img too.
4. So, file system.img already in raw format and i can mount in to the folder
5. I copied all the content of a mounted folder to the system_new folder, and appended here my apk.
6. After that i packed system_new folder to the system_new.img with the make_ext4fs tool
7. Flashing firmware with new system_new.img through Spreatrum ResearchDownload tool
8. After that device is stuck on first screen with "Powered by Android" that'all ((((
9. Re-flashing with stock image becomes device alive
Info about image files:
file system.img (stock)
system.img: Linux rev 1.0 ext4 filesystem data, UUID=da594c53-9beb-f85c-85c5-cedf76546f7a, volume name "system" (extents) (large files)
file system_new.img (custom)
system_new.img: Linux rev 1.0 ext4 filesystem data, UUID=da594c53-9beb-f85c-85c5-cedf76546f7a, volume name "system" (extents) (large files)
dumpe2fs system.img (Stock)
dumpe2fs 1.42.13 (17-May-2015)
Filesystem volume name: system
Last mounted on: ...
Filesystem UUID: da594c53-9beb-f85c-85c5-cedf76546f7a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 129280
Block count: 516604
Reserved block count: 0
Free blocks: 17026
Free inodes: 126892
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 127
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8080
Inode blocks per group: 505
Last mount time: Tue Jul 3 12:25:29 2018
Last write time: Tue Jul 3 17:23:26 2018
Mount count: 8
Maximum mount count: -1
Last checked: Thu Jan 1 05:00:00 1970
Check interval: 0 (<none>)
Lifetime writes: 30 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
Journal features: (none)
Journal size: 31M
Journal length: 8071
Journal sequence: 0x00000018
Journal start: 0
Click to expand...
Click to collapse
dumpe2fs system_new.img (Custom)
dumpe2fs 1.42.13 (17-May-2015)
Filesystem volume name: system
Last mounted on: <not available>
Filesystem UUID: da594c53-9beb-f85c-85c5-cedf76546f7a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 131376
Block count: 524800
Reserved block count: 0
Free blocks: 24913
Free inodes: 128988
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 135
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 7728
Inode blocks per group: 483
Last mount time: n/a
Last write time: Thu Jan 1 05:00:00 1970
Mount count: 0
Maximum mount count: -1
Last checked: Thu Jan 1 05:00:00 1970
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
Journal features: (none)
Journal size: 32M
Journal length: 8200
Journal sequence: 0x00000001
Journal start: 0
Click to expand...
Click to collapse
I need to build correct system image with which device could boot or may be i can put my apk in another place? Please, any help will be nice!
me too.
my problem also is it.
I don't know who can help me
---------- Post added at 04:30 PM ---------- Previous post was at 04:29 PM ----------
If you have answer.I hope you can share with me
// Update (Original problem described in the bottom of the post)
So I have actually tried a lot of different things, in the end I wiped the encrypted storage and everything else using TWRP however I have another bizarre problem - whatever ROM I flash it doesn't boot, there is only black screen.
Trying to repair the '/data' filesystem or change it from ext4 to ext2 and back in TWRP gives an error:
Code:
Failed to mount '/data' (Operation not supported on transport endpoint)
Unable to mount storage
Trying to 'Repair or Change File System' in TWRP for 'Internal storage' gives an error (maybe because its really '/data/media' folder? - https://twrp.me/faq/datamedia.html):
Code:
Invalid partition selection
Code:
'/data' (partition) = 'userdata' in parted = whole internal storage
'/data/media' (folder, virtual parittion?) = sdcard = user files in internal storage
It looks like after every system boot, filesystem change or repair, '/data' (internal storage?) gets unmounted and can't be mounted back. I used 'parted' and `adb shell` to recreate `/data` partition manually (called `userdata` in parittion table) but it didn't help:
Code:
adb push parted /
chmod 755 parted
adb shell
cd /dev
/parted block/mmcblk0
unit b
p
rm 50
mkpart primary 5570568192 62537055743
name 50 userdata
mke2fs -t ext4 /dev/block/mmcblk0p50
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
3481600 inodes, 13907833 blocks
695391 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
425 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
My partition table looks like this, I don't know what to make of it:
Code:
Number Start End Size File system Name Flags
1 67.1MB 155MB 88.1MB fat16 modem
2 201MB 201MB 1024B fsc
3 201MB 201MB 8192B ssd
4 201MB 202MB 524kB sbl1
5 202MB 202MB 524kB sbl1bak
6 202MB 203MB 524kB rpm
7 203MB 203MB 524kB rpmbak
8 203MB 206MB 2097kB tz
9 206MB 208MB 2097kB tzbak
10 208MB 208MB 262kB devcfg
11 208MB 208MB 262kB devcfgbak
12 208MB 225MB 16.8MB ext4 dsp
13 225MB 227MB 1573kB modemst1
14 227MB 228MB 1573kB modemst2
15 268MB 268MB 32.8kB DDR
16 268MB 270MB 1573kB fsg
17 270MB 270MB 16.4kB sec
18 336MB 347MB 11.5MB splash
19 403MB 404MB 1049kB aboot
20 404MB 405MB 1049kB abootbak
21 405MB 472MB 67.1MB boot
22 472MB 539MB 67.1MB recovery
23 539MB 540MB 1049kB devinfo
24 540MB 3761MB 3221MB ext2 system
25 3825MB 4094MB 268MB ext4 cache
26 4094MB 4127MB 33.6MB ext4 persist
27 4127MB 4128MB 1049kB misc
28 4128MB 4129MB 524kB keystore
29 4129MB 4129MB 32.8kB config
30 4129MB 4397MB 268MB oem
31 4429MB 4429MB 32.8kB limits
32 4496MB 4497MB 524kB mota
33 4497MB 4498MB 1049kB dip
34 4498MB 4531MB 33.6MB mdtp
35 4531MB 4532MB 524kB syscfg
36 4532MB 4536MB 4194kB mcfg
37 4563MB 4564MB 131kB lksecapp
38 4564MB 4564MB 131kB lksecappbak
39 4564MB 4564MB 262kB cmnlib
40 4564MB 4564MB 262kB cmnlibbak
41 4564MB 4564MB 262kB cmnlib64
42 4564MB 4565MB 262kB cmnlib64bak
43 4565MB 4565MB 262kB keymaster
44 4565MB 4565MB 262kB keymasterbak
45 4631MB 4631MB 262kB apdp
46 4631MB 4631MB 262kB msadp
47 4631MB 4631MB 8192B dpo
48 4631MB 4698MB 67.1MB logdump
49 4698MB 5571MB 872MB ext2 cust
50 5571MB 62.5GB 57.0GB ext4 userdata
I am confused because it should be more than enough.
Summary: I can flash ROMs and other things, they install without errors but to do that I have to first use TWRP's 'Format Data' each time and Reboot to Recovery. After that '/data' can be mounted properly in TWRP. Every time I try to do anything with the partition under TWRP it "dismounts" and can't be mounted back, if I try to boot the installed ROM (clean, any) instead, I end up with a Black Screen which rebooted to recovery again prevents '/data' from being mounted (until another 'Format Data').
I have also tried older versions of TWRP (to no avail) and newest OrangeFox recovery (touch doesn't work, presumably due to the original problem).
// ORIGINAL PROBLEM
I really need your help guys, will be grateful for any assistance.
My `XIaomi Redmi 5 Plus` was accidentally flooded. I disassembled it completely, checked the parts, soaked and cleaned with 99% isopropyl alcohol, then waited for it to dry completely.
I have also replaced screen into this: https://allegro.pl/oferta/wyswietlacz-ekran-lcd-ramka-xiaomi-redmi-5-plus-8501826695?snapshot=MjAyMi0wMS0yMVQwMjoxNjo1Ny40NDRaO2J1eWVyOzUyNDA1ZTkzODY3MTkzYTRlYTVlOGZkYjM3OGIwZDJjOTQ0NGI4MmZiM2Y1MmQ4MGMzYjZlNGU4ODdkNzA1MjU=
I have `lineage-15.1-20180526-UNOFFICIAL-vince` ROM installed since 2018: https://forum.xda-developers.com/t/...al-lineageos-15-1-updated-26-05-2018.3780298/ (I am not sure if this is the correct version, I can provide the file if necessary)
Also TWRP and Magisk
My Android is encrypted and incompatible with TWRP decryption since day one (its a bug apparently).
Everything works except touch on Android (pre-boot auth screen), to my astonishment touch works under TWRP), I also have adb access.
Dirty and clean flashing different ROMs and kernels didn't fix the issue.
For future reference I fixed this issue with Black Screen by flashing the newest MIUI firmware (not ROM), it appears that firmware partition had to be corrupted or my firmware was too old.
Here is the file: https://xiaomifirmwareupdater.com/miui/vince/stable/V11.0.2.0.OEGMIXM/
As for the issue with inability to mount storage ('/data') partition:
- As stated earlier it doesn't work in any version of TWRP at the moment
- I tried OrangeFox Recovery - touch not working.
- I tried Pitch Black Recovery and it mounts correctly: https://pitchblackrecovery.com/vince/
You see even if I was able to correctly boot my ROM I still had to mount '/data' because it turned out that trying to encrypt back my phone I was experiencing the issue described here: https://forum.xda-developers.com/t/encrypting-just-reboots-the-phone.3405513/, caused by "Orig filesystem overlaps crypto footer region. Cannot encrypt in place." error.
It needs 16 kb of free space so I had to use 'resize2fs' which didn't work in TWRP with the parittion being unmountable.
`Pitch Black` (PERP) uses slightly newer 'resize2fs' (and entire suite including it) version (TWRP: resize2fs 1.42.9 (28-Dec-2013), PERP: resize2fs 1.43.3 (04-Sep-2016)), so I imagine this is what allowed me to move forward.
Installing `Pitch Black` has also fixed a long standing issue with broken encoding in 'adb shell' btw.
I backed everything up and tried to use the tool above:
Code:
vince:/ # resize2fs /dev/block/mmcblk0p50 57G
resize2fs 1.43.3 (04-Sep-2016)
The containing partition (or device) is only 13907833 (4k) blocks.
You requested a new size of 14942208 blocks.
Now I had more info:
Code:
4 k (kb) = 4 * 1024 b = 4096 b
partition has: 13907833 blocks = 4096 b * 13907833 = 56966483968 b
we need 16 kb of free space: 16 * 1024 b = 16384 b
new size is: 56966483968 b - 16384 b = 56966467584 b
in blocks: 56966467584 b / 4096 b = 13907829 blocks
Resizing threw:
Code:
resize2fs 1.43.3 (04-Sep-2016)
Please run 'e2fsck -f /dev/block/mmcblk0p50' first.
So I ran:
Code:
1|vince:/ # e2fsck -f /dev/block/mmcblk0p50
e2fsck 1.43.3 (04-Sep-2016)
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? y
yes
Inode 1368088 was part of the orphaned inode list. FIXED.
Inode 2121750 was part of the orphaned inode list. FIXED.
Inode 2121751 was part of the orphaned inode list. FIXED.
Inode 2121754 was part of the orphaned inode list. FIXED.
Inode 2121755 was part of the orphaned inode list. FIXED.
Inode 2121756 was part of the orphaned inode list. FIXED.
Inode 2121757 was part of the orphaned inode list. FIXED.
Inode 2121768 was part of the orphaned inode list. FIXED.
Inode 2121769 was part of the orphaned inode list. FIXED.
Inode 2121802 was part of the orphaned inode list. FIXED.
Inode 2121803 was part of the orphaned inode list. FIXED.
Inode 2121828 was part of the orphaned inode list. FIXED.
Inode 2121829 was part of the orphaned inode list. FIXED.
Inode 2121889 was part of the orphaned inode list. FIXED.
Inode 2121890 was part of the orphaned inode list. FIXED.
Inode 2121892 was part of the orphaned inode list. FIXED.
Inode 2121940 was part of the orphaned inode list. FIXED.
Inode 2121941 was part of the orphaned inode list. FIXED.
Inode 2121943 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p50: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p50: 20071/3481600 files (2.9% non-contiguous), 2729092/13907833 blocks
After that the resize was successful:
Code:
1|vince:/ # resize2fs /dev/block/mmcblk0p50 13907829
resize2fs 1.43.3 (04-Sep-2016)
Resizing the filesystem on /dev/block/mmcblk0p50 to 13907829 (4k) blocks.
The filesystem on /dev/block/mmcblk0p50 is now 13907829 (4k) blocks long.
After that the encryption was successful, so 16 kb is all you need indeed (for the record I probably caused this issue by manually recreating '/data' parittion from the terminal).
Next was the problem with battery life decreased by 75% (it entirely discharged in 8 hours).
At first I used aggressive profiles and Naptime on top of it (I measure iwith Accubattery). Slow charging over USB was actually draining the battery instead of replenishing it.
It turns out that there must be a Bug in crDroid 7.13 (Android 11) because as soon as I disabled (ironically) battery management for all apps and battery saver (even with Naptime enabled) it dropped drastically.
Code:
Settings > Battery > Manage Apps Automatically > Off
Now I found out that speaker doesn't work...
..and the battery is still being drained way too fast.