Database Info

Why does my almost finished build terminate with no reason or error?

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

[Q] Switching from CM10 to CleanRom v5

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.

[Q] Repack system.img for P5100 Tab 2?

All,
I am hacking my way through some ROM development - trying to learn how it all works.
I have been trying to get started modifying the system.img from the Stock ICS 4.0.4 ROM for the GT-P5100, following this guide
All good - and I have done my mods to the files (actually all i have done is added an APK) to reduce the variables if something goes wrong.
When I try to "repack" using:
Code:
./mkuserimg.sh -s /some/directory/with/files ./factoryfs_custom.img ext4 ./temp 512M
I get
Code:
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
error: do_inode_allocate_extents: Failed to allocate 2925 blocks
I am guessing this is because of the block size? So the question is what should this be for the Tab 2 10.1 P5100?

Have you tried using a larger value for the temp size?
Posted from my Fascinate using XDA Premium

MultipleMonomials said:
Have you tried using a larger value for the temp size?
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
I honestly am not really sure what the value does - so no... any suggestions for a value? Or suck it and see?
What impact does it have on the final image?

patonar said:
I honestly am not really sure what the value does - so no... any suggestions for a value? Or suck it and see?
What impact does it have on the final image?
Click to expand...
Click to collapse
OK - so i bit the bullet, change the size to 1024M and repacked the FS, tar'd the file, and flashed using ODIN.
Worked a dream
I think I am going to write a guide on the basics, as there is so much info out there - but not many sources for beginners pulling it all together.

Go for it! More information is never a bad thing!
Posted from my Galaxy Tab with CM10

OPO Wont load !

Need Help: OPO will reboot after boot animation, when on CM set language page( Initial Setup page)
How do I re install 38R again ?
I have access to CM recovery & Fastboot by pressing Power & Volume keys.
Device not rooted.

ashishk2 said:
Need Help: OPO will reboot after boot animation, when on CM set language page( Initial Setup page)
How do I re install 38R again ?
I have access to CM recovery & Fastboot by pressing Power & Volume keys.
Click to expand...
Click to collapse
I have the same exact issue. I restored all the same images and still the same thing. Trying something different now. You need to download the factory image from the bottom of this page : https://cyngn.com/products/oneplusone/

LaNsLyDe said:
I have the same exact issue. I restored all the same images and still the same thing. Trying something different now. You need to download the factory image from the bottom of this page : https://cyngn.com/products/oneplusone/
Click to expand...
Click to collapse
Hope it works bud ! So need the phone back and running.
Keep me posted

Will do, do you know where the thread went for the 38R flashable zip?
also when you download the fastboot zip extract it into where you have fastbooto n your pc and do these commands. will most likely wipe data and you can replace the recovery it flashed with a custom one:
Start the fastboot tool and run the following in the command line (that means, windows+r, type cmd, press enter), in sequence:
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
---------- Post added at 12:17 PM ---------- Previous post was at 12:01 PM ----------
ashishk2 said:
Hope it works bud ! So need the phone back and running.
Keep me posted
Click to expand...
Click to collapse
i found the fix!
Do this it worked for me :
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
After a helpful session with +Ricardo Cerqueira of +Cyanogen Inc., here's a fix. While your phone is booted to TWRP, run these commands on your computer:
adb shell
make_ext4fs /dev/block/mmcblk0p15
A similar fix appeared earlier on the XDA Developers forum, but this single command is easier, runs faster, and doesn't require any downloads.
Here's the output of the command:
make_ext4fs /dev/block/mmcblk0p15
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
Once everything is over, the OnePlus One should be restored without any data loss. We still don't know what causes the partition to get corrupted in the first place, but at least we all now know what to do if it does.

LaNsLyDe said:
---------- Post added at 12:17 PM ---------- Previous post was at 12:01 PM ----------
[/COLOR]
i found the fix!
Do this it worked for me :
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
After a helpful session with +Ricardo Cerqueira of +Cyanogen Inc., here's a fix. While your phone is booted to TWRP, run these commands on your computer:
adb shell
make_ext4fs /dev/block/mmcblk0p15
A similar fix appeared earlier on the XDA Developers forum, but this single command is easier, runs faster, and doesn't require any downloads.
Here's the output of the command:
make_ext4fs /dev/block/mmcblk0p15
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
Once everything is over, the OnePlus One should be restored without any data loss. We still don't know what causes the partition to get corrupted in the first place, but at least we all now know what to do if it does.
Click to expand...
Click to collapse
I'm not rooted or custom recovery ! What do I do ?

Thread closed ! "corrupt persist.img"
Thank you 
 @justinblaine23 for posting the link.
 @markbencze for proving detailed instruction for the fix.
 @other who posted solutions.
The issues for caused bcoz of corrupt persist.img. If anyone faces the same issue reboot after boot animation or 0Mb in recovery kindly following the instruction on this link
Caution: Dont press and hold the power button to rest the phone, this caused the error on my OPO.

How to fix brocken or missing efs partition [SOLUTION]

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