Hi,
years ago i installed the Teamsuperluminal's CM13 on my Xiaomi Mi 4c and it it worked for a long time without major issues. Lately the phone started to auto power down when the battery reached appr. 50% charge. I would hook it up to a charger and reboot it and charge it back up again. Then it was fine again, this has been going on for months now. But yesterday it auto powered down again and after reboot it showed the CM boot logo for an unusual amount of time, after that it started preparing apps for start. When it was done with that it would just immediately reboot and start over again. So it is now stuck on a preparing apps reboot loop.
What i have tried so far:
1. Wipe cache and dalvik in TWRP and reboot. Didn't help
2. Tried to reformat a partition that might be corrupted due to brown out with:
Code:
make_ext4fs /dev/block/mmcblk0p15
It shows the following error:
Code:
Creating filesystem with parameters:
Size: 131072
Block size: 4096
Blocks per group: 32768
Inodes per group: 16
Inode size: 256
Journal blocks:1024
Label:
Blocks: 32
Block groups: 1
Reserved block group size: 7
error: ext4_allocate_best_fit_partial: failed to allocate 1005 blocks, out of space?
But there are more than 2GB of free space available and mmblk0p15 is then missing from /dev/block/ , so if i run the same command again i get:
Code:
Need size of filesystem
How can i repair this or what log file might be interesting?
Related
First of all my phone is working fine, and I don't see any errors.
However when I do FS check on the data partition - mmcblk0p2
it has so many errors!
Code:
e2fsck -yv /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
DATA contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? yes
Inode 80 was part of the orphaned inode list. FIXED.
Inode 89 was part of the orphaned inode list. FIXED.
Deleted inode 91 has zero dtime. Fix? yes
Inode 105 was part of the orphaned inode list. FIXED.
Inode 5905 has imagic flag set. Clear? yes
Inode 5905 has compression flag set on filesystem without compression support. Clear? yes
Inode 5905 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 5905, i_blocks is 4294967295, should be 0. Fix? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 5905 (...) has invalid mode (0177777).
Clear? yes
Pass 5: Checking group summary information
Inode bitmap differences: -80 -89 -91 -105
Fix? yes
Free inodes count wrong for group #0 (3270, counted=3273).
Fix? yes
Free inodes count wrong (117779, counted=117782).
Fix? yes
DATA: ***** FILE SYSTEM WAS MODIFIED *****
5098 inodes used (4.15%)
385 non-contiguous files (7.6%)
6 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 5026/57
76415 blocks used (15.55%)
0 bad blocks
1 large file
4376 regular files
707 directories
0 character device files
0 block device files
3 fifos
2 links
0 symbolic links (0 fast symbolic links)
3 sockets
--------
5091 files
[check again, it is fine now]
# e2fsck -v /dev/block/mmcblk0p2
e2fsck -v /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
DATA: clean, 5098/122880 files, 76415/491520 blocks
[force check again, ensure all errors are corrected]
# e2fsck -fv /dev/block/mmcblk0p2
e2fsck -fv /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
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
5098 inodes used (4.15%)
385 non-contiguous files (7.6%)
6 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 5026/57
76415 blocks used (15.55%)
0 bad blocks
1 large file
4376 regular files
707 directories
0 character device files
0 block device files
3 fifos
2 links
0 symbolic links (0 fast symbolic links)
3 sockets
--------
5091 files
Now all errors are corrected.
After a few days of normal use, install uninstall apps.... power off and on....
The data partition has errors again during FS check....
I have been building some CM7/9 ROMs, but lately this one repo I'm compiling from never finishes the make job. It did worked once, but the rest of the times it never does. I do not do anything other than edit the init, mk, vendor files.
It always stops after making the system.img and terminates for no reason back to the terminal.
Code:
Install: out/target/product/vivo/system/app/SystemUI.apk
Finding NOTICE files: out/target/product/vivo/obj/NOTICE_FILES/hash-timestamp
Combining NOTICE files: out/target/product/vivo/obj/NOTICE.html
Installed file list: out/target/product/vivo/installed-files.txt
Target system fs image: out/target/product/vivo/obj/PACKAGING/systemimage_intermediates/system.img
in mkuserimg.sh PATH=out/host/linux-x86/bin/:/usr/lib/jvm/java-6-sun/bin:/home/kaijura/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/kaijura/android-sdk/tools:/home/kaijura/android-sdk/platform-tools:/home/kaijura/icecold/out/host/linux-x86/bin:/home/kaijura/icecold/prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin:/home/kaijura/icecold/development/emulator/qtools:/home/kaijura/icecold/prebuilt/linux-x86/toolchain/arm-eabi-4.6.3/bin:/home/kaijura/icecold/prebuilt/linux-x86/toolchain/arm-eabi-4.6.3/bin
make_ext4fs -s -l 585101312 -a system out/target/product/vivo/obj/PACKAGING/systemimage_intermediates/system.img out/target/product/vivo/system
Creating filesystem with parameters:
Size: 585101312
Block size: 4096
Blocks per group: 32768
Inodes per group: 7152
Inode size: 256
Journal blocks: 2231
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 39
Created filesystem with 1402/35760 inodes and 66573/142847 blocks
Install system fs image: out/target/product/vivo/system.img
out/target/product/vivo/system.img+out/target/product/vivo/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p total size is 266217238
[email protected]:~/icecold$
Any ideas what I can try? I have done make clean, deleted the out folder and have properly set ccache.
Code:
export USE_CCACHE=1
export CCACHE_DIR=/home/kaijura/.ccache
prebuilt/linux-x86/ccache/ccache -M 40G
make -j2
Hello, I am trying to switch from CM10 to CleanRom, but am having issues installing the ROM itself. When selecting the last next before the install process in the Aroma installer, it simply goes to the install complete screen.
I pulled the install logs off the device which I have pasted below.
Code:
AROMA INSTALLER version 2.51
(c) 2012 by amarullz xda-developers
ROM Name : CleanROM
ROM Version : 5.0
ROM Author : Scott
Device : HTC One X
Start at : Thu Nov 8 13:04:13 2012
CleanROM V
//snip//
Formatting and Optimizing File System...
Extract: /tmp/fsck.ext4
Extract: /tmp/mkfs.ext4
Extract: /tmp/tune2fs.ext4
Creating filesystem with parameters:
Size: 1744829440
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 6656
Label:
Blocks: 425983
Block groups: 13
Reserved block group size: 103
Created filesystem with 11/106496 inodes and 13971/425983 blocks
error: file_write: write: I/O error
Installer Error (Status 1)
End at : Thu Nov 8 13:04:13 2012
I can reload CM10 happily via recovery, just not CleanRom. (I also tried Viper which failed too.)
Info:
Bootloader Unlocked
HBOOT-01.09.0000
I feel I am missing something stupid here, any ideas?
Thanks,
koj1n said:
Hello, I am trying to switch from CM10 to CleanRom, but am having issues installing the ROM itself. When selecting the last next before the install process in the Aroma installer, it simply goes to the install complete screen.
I pulled the install logs off the device which I have pasted below.
Code:
AROMA INSTALLER version 2.51
(c) 2012 by amarullz xda-developers
ROM Name : CleanROM
ROM Version : 5.0
ROM Author : Scott
Device : HTC One X
Start at : Thu Nov 8 13:04:13 2012
CleanROM V
//snip//
Formatting and Optimizing File System...
Extract: /tmp/fsck.ext4
Extract: /tmp/mkfs.ext4
Extract: /tmp/tune2fs.ext4
Creating filesystem with parameters:
Size: 1744829440
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 6656
Label:
Blocks: 425983
Block groups: 13
Reserved block group size: 103
Created filesystem with 11/106496 inodes and 13971/425983 blocks
error: file_write: write: I/O error
Installer Error (Status 1)
End at : Thu Nov 8 13:04:13 2012
I can reload CM10 happily via recovery, just not CleanRom. (I also tried Viper which failed too.)
Info:
Bootloader Unlocked
HBOOT-01.09.0000
I feel I am missing something stupid here, any ideas?
Thanks,
Click to expand...
Click to collapse
Have you tried wiping everything (data, cache, dalvik, system) before running the installer?
Yep, I have wiped everything. Even tried flashing the CleanRom boot.img via fastboot, non-CM10 ROMs just seem fail to load.
Unzip on a computer and flash the cleanroms boot.IMG then flash.
Sent from my HTC One X using xda premium
curly9 said:
Unzip on a computer and flash the cleanroms boot.IMG then flash.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
He's on hboot 1.09 he doesnt need to do that
Figured it out. CleanRom 5 is incompatible with TWRP 2.3+, just downgraded and it works again.
Hello i erased my efs partition and i didnt have a back up, so after one week i found the ****in solution.
First you need a twrp recovery maybe it will work and with others but i used that.
Second you need to download coloros (version COS_2.0.1i_11.zip) : http://forum.xda-developers.com/oneplus-one/general/rom-4-4-2-coloros-2-0-36beta-t2955853
download oxygenos (version 1.0.3) : https://forums.oneplus.net/threads/update-oxygenos-1-0-3-with-the-latest-stagefright-patches.354409/
download pesist.img : http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Now we have everything.
1. Go to recovery mode.
2. Wipe factory reset.
3. Flash coloros (dont worry wont mess anything)
4. Wipe
5. Flash oxygenos (boot it and now you will have a wi-fi bluethooth and sim-card)
6. Go to recovery again.
7. Wipe
8 Go to fastboot mode
9. fastboot erase persist
10. fastboot flash persist persist.img
11. Go to recovery mode againd
12. Advanced -> terminal command -> select (right bottom corner)
13. type: su
14: type: make_ext4fs /dev/block/mmcblk0p15
You will see:
Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
And after that you are good to go.
Big thanks to all guys and their articles.
And again you will be able to flash others roms and to have wi-fi, audiofx and etc...
Took you long enough... lol
Glad you solved it my friend.
Tom 2.0
how can check memory of one plus one when phone stuck on logo i have recived many times one plus one hang on logo and customer dont no how much memory in this phone how can check plz help thnx
ahmerp said:
how can check memory of one plus one when phone stuck on logo i have recived many times one plus one hang on logo and customer dont no how much memory in this phone how can check plz help thnx
Click to expand...
Click to collapse
If the device has a white back cover, it's the 16gb version and if i'ts the sandstone black cover then it's the 64gb version, ofcourse this is only true when the owner hasn't replaced their back cover!
if user change back cover then bcz to much refurbish phone in market last night black back cover 16gb phone i recived for firmware update that is reason today i post this
ahmerp said:
if user change back cover then bcz to much refurbish phone in market last night black back cover 16gb phone i recived for firmware update that is reason today i post this
Click to expand...
Click to collapse
if it has a customer recovery built in boot into recovery and plug in the cable and see how much memory there is
fastboot format cache
waiting for device >
rasing 'cache'...
KAY [ 0.197s]
ormatting 'cache' partition...
reating 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
reated filesystem with 11/32768 inodes and 4206/131072 blocks
ending 'cache' (10432 KB)...
riting 'cache'...
KAY [ 0.624s]
inished. total time: 0.823s this is the procedure to check memory