[KERNEL][UNOFFICIAL BUILDS][JB/KK][Vx.43v76]DorimanX Test builds

Search This thread

Troubadour666

Inactive Recognized Contributor
Aug 3, 2012
3,140
7,035
43.7031 - 7.2661
Hi,

8.44v004 always save my "life" to run the best Spirit 2nd rom i have (with mali v2 :p ) , when i stuck on any Lollipop 1rst rom runing its own kernel or with Apolo beta5 from @pedestre , i can swap kernel easily .
@dorimanx power kernel still daving device from bootloop or any other trouble (except brick)

just a little report for dualbooters ;)
 

Twiq

Senior Member
I believe many of XDA users believe the developers uses tarot or runes to solve the problems on apps, kernel or roms [emoji12] [emoji12] [emoji12] [emoji12]


Hi @cybernetus
after a long while.. i never encountered any problems whatsoever with your last build.. until now..
to keep it short, a friend of mine bought a secondhand i9100..
before i tinker with it, it was running MIUI 4.1.2, not sure what version, don't care :D

so i wiped the whole thing (manually formatted /cache /system /data /preload), and flashed what i always recommend for i9100 users : latest Slimsaber 4.4.4, slimrom slim gapps and your kernel 10.44v008, weird.. it bootlooped..
then i went back from wiping the whole thing, and flash again everything, except your kernel, but then it booted..

i got curious, reflashed your kernel and took some logs (4 logs from 4 bootloop cycles) :
here it is :


Code:
1st log :
--------- beginning of /dev/log/main

I/installd( 2118): installd firing up

I/DEBUG   ( 2110): debuggerd: Nov  4 2014 21:51:02

--------- beginning of /dev/log/system

I/Vold    ( 2107): Vold 2.1 (the revenge) firing up

D/Vold    ( 2107): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 2107): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 2107): Volume usbdisk0 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 2107): Volume sdcard0 state changing 0 (No-Media) -> 2 (Pending)

D/DirectVolume( 2107): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 1, PARTN 1
Code:
2nd log :
--------- beginning of /dev/log/main

I/installd( 2035): installd firing up

I/DEBUG   ( 2027): debuggerd: Nov  4 2014 21:51:02

--------- beginning of /dev/log/system

I/Vold    ( 2024): Vold 2.1 (the revenge) firing up

D/Vold    ( 2024): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 2024): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 2024): Volume usbdisk0 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 2024): Volume sdcard0 state changing 0 (No-Media) -> 2 (Pending)

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 1, PARTN 1

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 2, PARTN 2

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 3, PARTN 3

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 4, PARTN 4

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 5, PARTN 5

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 6, PARTN 6

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 7, PARTN 7

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 0, PARTN 8

E/DirectVolume( 2024): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p8' has a different major than its disk!

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 1, PARTN 9

E/DirectVolume( 2024): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p9' has a different major than its disk!

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 2, PARTN 10

E/DirectVolume( 2024): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p10' has a different major than its disk!

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 3, PARTN 11

E/DirectVolume( 2024): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p11' has a different major than its disk!

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 4, PARTN 12

E/DirectVolume( 2024): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p12' has a different major than its disk!

D/Vold    ( 2024): Volume sdcard0 state changing 2 (Pending) -> 1 (Idle-Unmounted)

D/Vold    ( 2024): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending)

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 9, PARTN 1

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 10, PARTN 2

D/DirectVolume( 2024): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 11, PARTN 3

D/Vold    ( 2024): Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Unmounted)

I/Netd    ( 2026): Netd 1.0 starting

W/InterfaceController( 2026): Error (undefined symbol: net_iface_send_command_fini) while searching for the interface command fini function
Code:
3rd Log :
--------- beginning of /dev/log/main

I/installd( 2070): installd firing up

I/DEBUG   ( 2064): debuggerd: Nov  4 2014 21:51:02

--------- beginning of /dev/log/system

I/Vold    ( 2060): Vold 2.1 (the revenge) firing up

D/Vold    ( 2060): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 2060): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 2060): Volume usbdisk0 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 2060): Volume sdcard0 state changing 0 (No-Media) -> 2 (Pending)

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 1, PARTN 1

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 2, PARTN 2

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 3, PARTN 3

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 4, PARTN 4

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 5, PARTN 5

I/Netd    ( 2062): Netd 1.0 starting

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 6, PARTN 6

W/InterfaceController( 2062): Error (undefined symbol: net_iface_send_command_fini) while searching for the interface command fini function

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 7, PARTN 7

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 0, PARTN 8

E/DirectVolume( 2060): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p8' has a different major than its disk!

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 1, PARTN 9

E/DirectVolume( 2060): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p9' has a different major than its disk!

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 2, PARTN 10

E/DirectVolume( 2060): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p10' has a different major than its disk!

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 3, PARTN 11

E/DirectVolume( 2060): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p11' has a different major than its disk!

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 4, PARTN 12

E/DirectVolume( 2060): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p12' has a different major than its disk!

D/Vold    ( 2060): Volume sdcard0 state changing 2 (Pending) -> 1 (Idle-Unmounted)

D/Vold    ( 2060): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending)

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 9, PARTN 1

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 10, PARTN 2

D/DirectVolume( 2060): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 11, PARTN 3

D/Vold    ( 2060): Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Unmounted)
Code:
4th log :
--------- beginning of /dev/log/system

I/Vold    ( 1536): Vold 2.1 (the revenge) firing up

D/Vold    ( 1536): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 1536): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 1536): Volume usbdisk0 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold    ( 1536): Volume sdcard0 state changing 0 (No-Media) -> 2 (Pending)

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 1, PARTN 1

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 2, PARTN 2

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 3, PARTN 3

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 4, PARTN 4

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 5, PARTN 5

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 6, PARTN 6

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 7, PARTN 7

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 0, PARTN 8

E/DirectVolume( 1536): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p8' has a different major than its disk!

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 1, PARTN 9

E/DirectVolume( 1536): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p9' has a different major than its disk!

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 2, PARTN 10

E/DirectVolume( 1536): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p10' has a different major than its disk!

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 3, PARTN 11

E/DirectVolume( 1536): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p11' has a different major than its disk!

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 4, PARTN 12

E/DirectVolume( 1536): Partition '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p12' has a different major than its disk!

D/Vold    ( 1536): Volume sdcard0 state changing 2 (Pending) -> 1 (Idle-Unmounted)

D/Vold    ( 1536): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending)

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 9, PARTN 1

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 10, PARTN 2

D/DirectVolume( 1536): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 11, PARTN 3

D/Vold    ( 1536): Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Unmounted)

--------- beginning of /dev/log/main

I/ARMAssembler( 1974): generated scanline__00000077:03545405_00000A01_00000000 [ 37 ipp] (58 ins) at [0xb61e21f0:0xb61e22d8] in 0 ns

I/ARMAssembler( 1974): generated scanline__00000077:03545405_00000A08_00000000 [ 37 ipp] (59 ins) at [0xb61e22e0:0xb61e23cc] in 0 ns

I/ARMAssembler( 1974): generated scanline__00000077:03545405_00000000_00000000 [ 36 ipp] (50 ins) at [0xb61e23d0:0xb61e2498] in 0 ns

D/DirectVolume( 1536): Checking for bad partition major number

D/DirectVolume( 1536): Checking for bad partition major number

D/DirectVolume( 1536): Checking for bad partition major number

I/Vold    ( 1536): /dev/block/vold/179:9 being considered for volume sdcard1

D/Vold    ( 1536): Volume sdcard1 state changing 1 (Idle-Unmounted) -> 3 (Checking)

D/Vold    ( 1536): Trying to get filesystem type for /dev/block/vold/179:9 

D/Vold    ( 1536): Found vfat filesystem on /dev/block/vold/179:9

I/fsck_msdos( 1536): ** /dev/block/vold/179:9

I/fsck_msdos( 1536): ** Phase 1 - Read FAT (compare skipped)

I/fsck_msdos( 1536): Attempting to allocate 5114 KB for FAT

I/fsck_msdos( 1536): ** Phase 2 - Check Cluster Chains

I/fsck_msdos( 1536): ** Phase 3 - Checking Directories

I/fsck_msdos( 1536): ** Phase 4 - Checking for Lost Files

I/fsck_msdos( 1536): 10496 files, 3970816 free (496352 clusters)

I/Vold    ( 1536): Filesystem check completed OK

D/Vold    ( 1536): blkid identified as /dev/block/vold/179:9: UUID="552A-5660" TYPE="vfat" 

D/Vold    ( 1536): Volume sdcard1 state changing 3 (Checking) -> 4 (Mounted)

D/DirectVolume( 1536): Checking for bad partition major number

D/DirectVolume( 1536): Found bad partition

E/DirectVolume( 1536): Fixing major number from 179 to 259 for partition 11

I/Vold    ( 1536): /dev/block/vold/259:3 being considered for volume sdcard0

D/Vold    ( 1536): Volume sdcard0 state changing 1 (Idle-Unmounted) -> 3 (Checking)

D/Vold    ( 1536): Trying to get filesystem type for /dev/block/vold/259:3 

I/fsck_msdos( 1536): ** /dev/block/vold/259:3

I/fsck_msdos( 1536): ** Phase 1 - Read and Compare FATs

I/fsck_msdos( 1536): Attempting to allocate 1473 KB for FAT

D/Vold    ( 1536): Found vfat filesystem on /dev/block/vold/259:3

I/fsck_msdos( 1536): Attempting to allocate 1473 KB for FAT

I/fsck_msdos( 1536): ** Phase 2 - Check Cluster Chains

I/fsck_msdos( 1536): ** Phase 3 - Checking Directories

I/fsck_msdos( 1536): ** Phase 4 - Checking for Lost Files

I/fsck_msdos( 1536): 5450 files, 1873056 free (58533 clusters)

I/Vold    ( 1536): Filesystem check completed OK

D/Vold    ( 1536): blkid identified as /dev/block/vold/259:3: UUID="277D-07D4" TYPE="vfat" 

D/Vold    ( 1536): Volume sdcard0 state changing 3 (Checking) -> 4 (Mounted)

D/Vold    ( 1536): Volume sdcard0 state changing 4 (Mounted) -> 5 (Unmounting)

I/Vold    ( 1536): /mnt/secure/asec sucessfully unmounted

I/Vold    ( 1536): /storage/sdcard0 sucessfully unmounted

I/Vold    ( 1536): /storage/sdcard0 sucessfully unmounted

I/Vold    ( 1536): /storage/sdcard0 unmounted successfully

D/Vold    ( 1536): Volume sdcard0 state changing 5 (Unmounting) -> 1 (Idle-Unmounted)

D/DirectVolume( 1536): Checking for bad partition major number

D/DirectVolume( 1536): Found bad partition

E/DirectVolume( 1536): Fixing major number from 179 to 259 for partition 11

I/Vold    ( 1536): /dev/block/vold/259:3 being considered for volume sdcard0

D/Vold    ( 1536): Volume sdcard0 state changing 1 (Idle-Unmounted) -> 3 (Checking)

D/Vold    ( 1536): Trying to get filesystem type for /dev/block/vold/259:3 

D/Vold    ( 1536): Found vfat filesystem on /dev/block/vold/259:3

I/fsck_msdos( 1536): ** /dev/block/vold/259:3

I/fsck_msdos( 1536): ** Phase 1 - Read and Compare FATs

I/fsck_msdos( 1536): Attempting to allocate 1473 KB for FAT

I/fsck_msdos( 1536): Attempting to allocate 1473 KB for FAT

I/fsck_msdos( 1536): ** Phase 2 - Check Cluster Chains

I/fsck_msdos( 1536): ** Phase 3 - Checking Directories

I/fsck_msdos( 1536): ** Phase 4 - Checking for Lost Files

I/fsck_msdos( 1536): Next free cluster in FSInfo block (7) not free

I/fsck_msdos( 1536): FIXED

I/fsck_msdos( 1536): 5451 files, 1872896 free (58528 clusters)

I/Vold    ( 1536): Filesystem check completed OK

D/Vold    ( 1536): blkid identified as /dev/block/vold/259:3: UUID="277D-07D4" TYPE="vfat" 

D/Vold    ( 1536): Volume sdcard0 state changing 3 (Checking) -> 4 (Mounted)

D/Vold    ( 1536): Volume sdcard0 state changing 4 (Mounted) -> 5 (Unmounting)

I/Vold    ( 1536): /mnt/secure/asec sucessfully unmounted

I/Vold    ( 1536): /storage/sdcard0 sucessfully unmounted

I/Vold    ( 1536): /storage/sdcard0 sucessfully unmounted

I/Vold    ( 1536): /storage/sdcard0 unmounted successfully

D/Vold    ( 1536): Volume sdcard0 state changing 5 (Unmounting) -> 1 (Idle-Unmounted)

D/DirectVolume( 1536): Checking for bad partition major number

D/DirectVolume( 1536): Found bad partition

E/DirectVolume( 1536): Fixing major number from 179 to 259 for partition 11

I/Vold    ( 1536): /dev/block/vold/259:3 being considered for volume sdcard0

D/Vold    ( 1536): Volume sdcard0 state changing 1 (Idle-Unmounted) -> 3 (Checking)

D/Vold    ( 1536): Trying to get filesystem type for /dev/block/vold/259:3 

D/Vold    ( 1536): Found vfat filesystem on /dev/block/vold/259:3

I/fsck_msdos( 1536): ** /dev/block/vold/259:3

I/fsck_msdos( 1536): ** Phase 1 - Read and Compare FATs

I/fsck_msdos( 1536): Attempting to allocate 1473 KB for FAT

I/fsck_msdos( 1536): Attempting to allocate 1473 KB for FAT

I/fsck_msdos( 1536): ** Phase 2 - Check Cluster Chains

I/fsck_msdos( 1536): ** Phase 3 - Checking Directories

I/fsck_msdos( 1536): /clockworkmod/.recovery_version starts with free cluster

I/fsck_msdos( 1536): FIXED

I/fsck_msdos( 1536): ** Phase 4 - Checking for Lost Files

I/fsck_msdos( 1536): Lost cluster chain at cluster 182

I/fsck_msdos( 1536): 1 Cluster(s) lost

I/fsck_msdos( 1536): FIXED

I/fsck_msdos( 1536): No LOST.DIR directory

I/fsck_msdos( 1536): FIXED

I/fsck_msdos( 1536): Free space in FSInfo block (71767) not correct (71762)

I/fsck_msdos( 1536): FIXED

I/fsck_msdos( 1536): Next free cluster in FSInfo block (181) not free

I/fsck_msdos( 1536): FIXED

I/fsck_msdos( 1536): FIXED

I/fsck_msdos( 1536): Attempting to allocate 1473 KB for FAT

I/fsck_msdos( 1536): 5370 files, 2296416 free (71763 clusters)

I/fsck_msdos( 1536): ***** FILE SYSTEM WAS MODIFIED *****

I/fsck_msdos( 1536): fsck_msdos terminated by exit(4)

W/Vold    ( 1536): Filesystem modified - rechecking (pass 2)

D/Vold    ( 1536): blkid identified as /dev/block/vold/259:3: UUID="277D-07D4" TYPE="vfat" 

D/Vold    ( 1536): Volume sdcard0 state changing 3 (Checking) -> 4 (Mounted)

D/Vold    ( 1536): Volume sdcard0 state changing 4 (Mounted) -> 5 (Unmounting)

I/Vold    ( 1536): /mnt/secure/asec sucessfully unmounted

I/Vold    ( 1536): /storage/sdcard0 sucessfully unmounted

I/Vold    ( 1536): /storage/sdcard0 sucessfully unmounted

I/Vold    ( 1536): /storage/sdcard0 unmounted successfully

D/Vold    ( 1536): Volume sdcard0 state changing 5 (Unmounting) -> 1 (Idle-Unmounted)

D/Vold    ( 1536): Volume sdcard1 state changing 4 (Mounted) -> 5 (Unmounting)

I/Vold    ( 1536): /storage/sdcard1 sucessfully unmounted

I/Vold    ( 1536): /storage/sdcard1 sucessfully unmounted

I/Vold    ( 1536): /storage/sdcard1 unmounted successfully

D/Vold    ( 1536): Volume sdcard1 state changing 5 (Unmounting) -> 1 (Idle-Unmounted)

if you have some time please look at it.. from what i see, the previous owner might have repartitioned the device..
orrrrr, the internal partitions were dirty, however fixing them doesn't solve anything..

for now i will use the stock slimsaber kernel, until i found a solution that is.. please tell me what you think of those logs

thanks in advance
 
Last edited:

Twiq

Senior Member
Mui is not supported :)

Sent from my LG-D805 using Tapatalk

No, i ditched miui, it doesn't run on latest slimsaber and v008 combo, it bootlooped..

But on stock slimsaber kernel it booted and runs fine..
-I've wiped clean all partitions except /efs and /boot
-fixpartitionscript from recovery completed without errors
Any suggestions?
Cc: @Troubadour666 @rkoby13
 
Last edited:

Computoncio

Senior Member
May 29, 2012
1,315
3,569
Três Corações - MG - Brasil
No, i ditched miui, it doesn't run on latest slimsaber and v008 combo, it bootlooped..

But on stock slimsaber kernel it booted and runs fine..
-I've wiped clean all partitions except /efs and /boot
-fixpartitionscript from recovery completed without errors
Any suggestions?
Cc: @Troubadour666 @rkoby13

I had that issue once, i fixed it using pit file, to repartition the fs and flashed stock rom.
After that i just rooted and installed slimsaber and Dorimanx kernel and it booted fine.

Didn't found why it didn't boot with dorimanx kernel and it booted with SlimSaber kernel.

The only thing i leaned was if it doesn't boot, start from the beginning ;)

Hope you fix it [emoji106]

Phone: LG G2 D805
Kernel: Dorimanx kernel v9.9.6 D802
1st ROM : Pardus HD RoM™ Sensation Black v3.2
2nd ROM : Waiting for custom recovery ;)
MODS: Still searching
 

m1trand1r

Senior Member
Mar 6, 2011
12,403
9,586
You don't wanna know.....
I believe many of XDA users believe the developers uses tarot or runes to solve the problems on apps, kernel or roms [emoji12] [emoji12] [emoji12] [emoji12]

Sent from my LG-D805 using Tapatalk
Yeah...devs became prophets :D...lol
No, i ditched miui, it doesn't run on latest slimsaber and v008 combo, it bootlooped..

But on stock slimsaber kernel it booted and runs fine..
-I've wiped clean all partitions except /efs and /boot
-fixpartitionscript from recovery completed without errors
Any suggestions?
Cc: @Troubadour666 @rkoby13
rkoby13 is dead bro...[emoji14]
but other than what @Computoncio suggested I have no clue....sorry....G3 gives me a lot of work lately....afterall we have xposed for LP so you might think what I did....hehe....I love this beast man!!!
Good luck to you my friend :)
Will upload log when i can, went back to cm12 for a bit.
Also the problem occurs only when flashing Pa gapps, without it no problem, will try some other gapps before uploading the logs.
Use Slim Minimal gapps package and you'll be fine:)
PA gapps give us issues on G3 too so.....i'm using normal Slim gapps package ;)

Blissed from my LG-G3/d-855/16Gb/Titanium Black
 

Twiq

Senior Member
I had that issue once, i fixed it using pit file, to repartition the fs and flashed stock rom.
After that i just rooted and installed slimsaber and Dorimanx kernel and it booted fine.

Didn't found why it didn't boot with dorimanx kernel and it booted with SlimSaber kernel.

The only thing i leaned was if it doesn't boot, start from the beginning ;)

Hope you fix it [emoji106]

That.. I haven't tried :D
Thanks for the tip.. It's good to see you posting again bro, how are you?





Yeah...devs became prophets :D...lol

rkoby13 is dead bro...[emoji14]
but other than what @Computoncio suggested I have no clue....sorry....G3 gives me a lot of work lately....afterall we have xposed for LP so you might think what I did....hehe....I love this beast man!!!
Good luck to you my friend :)

Hahaha, those dots looks familiar :D
No wonder, i had trouble mentioning you.. Had to edit posts several of times..
 

j1gga84

Senior Member
Jun 21, 2012
4,620
2,730
Bremen
www.android-hilfe.de
Although development came to an end I think it is never too late for bug reports ;)

Since a few days I have the problem that screen freezes after coming from Deep Sleep..
I see the lockscreen but I cannot do anything and have to reboot with holding power button for 5 seconds..
What could be the problem and how can I provide logs? Would the ANR file help?

Concerning a new device I will wait until april and I think I will choose between Note 4 and the upcoming LG G4 (will be similar to the Note line :fingers-crossed: )

regards
 

BlackRainX

Senior Member
Aug 13, 2010
360
66
25
Šaľa
www.facebook.com
my phone dropped on screen and its dead. so let me collect some money and i will buy S II again (really i dont have a lot of money.)
The bugs with wifi? on v008, i had none.
 
Last edited:

pSyCh¤_O_O

Senior Member
Hey!!! Hows all my friends doing??...miss the good old Dorimanx days :sniff:

Hope you're all well and flashing away merrily [emoji12]

Gave my old S2 some fresh air the other day by flashing some lolli on it [emoji3] [emoji6]... Slim of course...

I'm in OnePlus forums now....

All the beat to all Cybercompumanx team and all [emoji12]


Best wishes

Chris
 

LiL_Assassin

Senior Member
Feb 19, 2012
1,266
663
I know this is extremely off topic. My old s2 finally hit the end of its life and now using an iPhone. I know I know... But it's only temporary. Would it be worth getting a one plus one now. Or waiting for the one plus two??

Sent from my SM-T110 using XDA Free mobile app
 
  • Like
Reactions: pSyCh¤_O_O

m1trand1r

Senior Member
Mar 6, 2011
12,403
9,586
You don't wanna know.....
Hey!!! Hows all my friends doing??...miss the good old Dorimanx days :sniff:

Hope you're all well and flashing away merrily [emoji12]

Gave my old S2 some fresh air the other day by flashing some lolli on it [emoji3] [emoji6]... Slim of course...

I'm in OnePlus forums now....

All the beat to all Cybercompumanx team and all [emoji12]


Best wishes

Chris

Hey bud:) Have fun with your bacon....i'm at LG G3 fora now....my S-2 I dead and partialy sold:)
So...c'ya around

I know this is extremely off topic. My old s2 finally hit the end of its life and now using an iPhone. I know I know... But it's only temporary. Would it be worth getting a one plus one now. Or waiting for the one plus two??

Sent from my SM-T110 using XDA Free mobile app

Well...it depens on what you really want. I've chosen what you see in my sig....I couldn't be more satisfied with anything else right now if I look around what OEMs have to offer....although I have 2Gb(ram)/16gb storage model....i'm happy with my 32gb class 10 sdcard in my external slot....on top of all that....Camera is a beast on Stock rom...which i'm currently running due to the fact that I have had severe chrash yesterday on ROM im my main sig....it's still not what it could be imo and it's CM Inc.....:)

>LG-G3<>d-855<>16Gb<>Titanium Black<
 

Top Liked Posts

  • There are no posts matching your filters.
  • 155
    Hey guys!
    So from observations by @rkoby13 and myself, there seems to be a demand for regular builds of DorimanX's kernel!
    This thread will serve as a place for logs, reports, and discussion relating to these unofficial builds by me.
    Currently the plan is to compile v9 builds, whenever @dorimanx adds major updates or significant modifications to his source, however this may, and probably will, result in UNSTABLE AND EXPERIMENTAL RELEASES
    Disclaimer:
    Dori tests highly experimental commits prerelease, and if your device is damaged, wiped, or in any way negatively affected by these releases it's not the fault of Dorimanx, or me. In flashing these releases you accept full responsibility for any consequences of its use.

    In this op, I'll have a log of which builds are most stable and which ones have bugs reported or major issues in code, and builds with extreme issues will be removed.
    As x.39 was just released, the first build will be uploaded after the next major addition to the kernel sources, and every major change after that.
    If there is a commit that I have not considered major but is important to you, either reply to the thread or pm me with a link to the commit, and I'll probably update the build to include it. In future, I may also build v8 kernels until their end of life, if many people show a desire for this :)
    Finally, just a reminder not to post logs or reports/discuss these builds in any other thread, thanks :)
    I'll also soon be adding my new and improved stweaks settings guide, nearly everything is covered now.
    Source: http://github.com/dorimanx/dorimanx-SG2-I9100-Kernel
    http://github.com/dorimanx/initramfs3
    if anyone has a domain they'd like to offer to mirror I'd be glad (hint hint)
    dorimanx has decided to help out with building sometimes, and he'll post here! and apparently no one reads whole op, is this big enough?

    latest build by cybernetus :) http://www.dorimanx.ataliba.net
    aaaaaand computoncio has a fileserver too now!
    http://dorimanx.casoncia.org
    79
    Great News!

    Are you ready???

    Hyper Drive Online!
    We are jumping to 4.4.y galaxy system!!! :highfive:

    new 3 kernels uploaded to my BETA storage! before release!

    we need to test the support and see if any problems!

    So all goes like this:
    All kernels support 4.4.y ROMS!

    8.x support = STOCK, 4.1.y, 4.2.y, 4.3.y, 4.4.y maliv1(STOCK) maliv2 all the rest!
    9.x support = 4.1.y, 4.2.y, 4.3.y, 4.4.y maliv2 only!

    10.x support = 4.3.y, 4.4.y maliv3 only!

    mali = video driver (for new users that dont care to look for answers)

    This is BETA v48!

    Kernel has same commits as V47 + maliv3 branch now 10.43 version :)

    Initramfs > https://github.com/dorimanx/initramfs3/commit/d2408d668240fa0fa11f0650a96650c39de6a39c

    Big thanks to @fusionjack for init scripts and hacked sql for 4.4.2 :)

    have fun testing!

    (dont forget! you cant install 4.4.y ROM from my kernel recovery!)
    so if you want to install ROM as SEC you will have to replace META-INF forlder
    with one that i will attach here!

    it's simple changing the way perms added to ROM for selinux! we dont have it, so it's not important.

    Open ROM zip. push the META-INF from my zip inside, and save all back.

    Install as SEC or PRI ROM.

    this is for fusionjack 4.4.2 build!!!!

    other roms may have other things in install script! so it's possible to compare if something missing from ORIGINAL fusionjack folder.

    all changes are HERE:
    META-INF\com\google\android\updater-script

    i have added the ORIGINAL script for compare / revert.
    76
    soooo :) seems to be that we are close to awesome kernel version!

    i need to sit and add support for 4.4.x android and rename maliv3 branch.

    i am very busy at my job, end of year is coming and our customers very happy to spend all remaining budget on cool stuff that they not always need :)

    so i have high pressure OC for my brain to make all done for all!

    and XDA is one more customer for me :)

    so please report if any bad things happen, and kernel is this problem, and not some app that went crazy :)

    happy new coming year for all!
    62
    News Update!

    I have FOUND and fixed:

    *Fixed RO bug with 4.4.y ROMS
    *Fixed parse error in SAMMY builds (need to test)
    *Fixed not sticking theme, root access, timezone, lang, and other system stuff
    after BOOT! :laugh::highfive:
    This was HUGE bug that i was looking to solve half a year now! and finally its GONE!

    *Fixed init perms on folders.
    *Added all new updates from main line.

    Uploaded V53 all branches to my BETA Storage! :)

    Merry Christmas! every one!

    when i have found the BUGS i was LIKE!

    HHHHHAAAAAA!!!!


    Warhammer-40-000-Space-Marine-Only-War-Thunder-Hammer-Trailer_7.jpg


    EXERMINATE! DELETE!


    Warhammer-40-000-Space-Marine-Only-War-Thunder-Hammer-Trailer_3.jpg



    Kernels > https://github.com/dorimanx/Doriman...mmit/288e53a3675cad94a0bdb085e49299310b3397cd

    Initramfs > https://github.com/dorimanx/initramfs3/commit/ea5a8d10e324f3d7a357ecf46989d7a35c4ddaea

    Have fun testing! :)

    DEBUG!
    first boot with V53 will be:
    ~ # dmesg | grep property
    dmesg | grep property
    <6>sec-battery sec-battery: sec_bat_set_property: cable was changed(4)
    <11>init: skipping insecure property file persist.sys.themePackageName (uid=0 gid=1001 nlink=1 mode=100770)
    <11>init: skipping insecure property file persist.sys.usb.config (uid=0 gid=1001 nlink=1 mode=100770)
    <11>init: skipping insecure property file persist.sys.ui.hw (uid=0 gid=1001 nlink=1 mode=100770)
    <11>init: skipping insecure property file persist.sys.camera-sound (uid=0 gid=1001 nlink=1 mode=100770)
    <11>init: skipping insecure property file persist.sys.root_access (uid=0 gid=1001 nlink=1 mode=100770)
    <11>init: skipping insecure property file persist.sys.themeId (uid=0 gid=1001 nlink=1 mode=100770)
    ~ #

    SEC BOOT and any others!

    ~ # dmesg | grep property
    dmesg | grep property
    <6>sec-battery sec-battery: sec_bat_set_property: cable was changed(4)
    ~ #

    ~ #

    ~ # dmesg | grep property
    dmesg | grep property
    <6>sec-battery sec-battery: sec_bat_set_property: cable was changed(4)
    ~ #

    ~ # dmesg | grep property
    dmesg | grep property
    <6>sec-battery sec-battery: sec_bat_set_property: cable was changed(4)

    PEACE! Yee!
    56
    hi to fearless beta testers.

    i want to address the sg2 nation :)

    its my birthday today, and i have enoth $ to buy new device.

    So as i wished i will buy new sg4 i9505 device next week.

    my device will be converted to nice and simple phone, (with my kernel) and passed to my wife. so i will keep updating kernel from main line, and keep adding good stuff i will see.

    so Sg4 nation will get "new" dev to boost the fun :)

    so all who want to join me, dont wait :)

    any way sg4 is great but very different, so its will take some time for me to learn, and start from 0.

    i will release stable release for all.

    and in case of recovery code from gm will be open, i will do all i can to update recovery.

    happy new year my friends :)

    Sent from my GT-I9100