• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[DEV] CyanogenMod 11 - Android 4.4 For PRIMOU(HTC ONE V) [NOT FOR NOOBS]

doga.ozkaraca

Inactive Recognized Developer
May 10, 2013
902
2,815
0
San Francisco, CA
dogaoz.com
Hi, Mates

I opened this thread for bring 4.4 Kitkat & CM11 ROM to our HOV device :))

Here is my github for device-tree and all other stuff : https://github.com/dogaozkaraca

Download Link of TEST ROM : link removed because of someone reported me about shorte.st and mods warned me...

TEST ROM IS NOT EVEN STABLE OR USABLE .. IT DOESN'T BOOT AND SHOW SOMETHING ON SCREEN..
IF YOU'RE NOOB, NORMAL USER. I'M NOT RECOMMEND TO BROWSE OR DOWNLOAD THAT ROM AND FLASH ...

I'M NOT RESPONSIBLE OF ANY PROBLEM. I'm just trying alive HOV...

Also thanks to @bradthomas127 .. for primoc device-tree . it will help much..

For Testers or developers :

Kernel included in rom :)

Please report problem you've found.. But PLEASE DON'T WRITE only(IT STUCKED HERE ..) etc. IT DOESN'T HELP ME... I need more detail to fix that problem.. :))
YOU CAN REPORT EVERYTHING LIKE A IT STUCKED HERE. I GOT THAT LOGCAT ALSO HERE IS A DMESG AND MAYBE WE CAN CHANGE THAT CODES(in github please if you find solution, send pull request) .....

CURRENT STATUS

1- we cannot access adb .. It shows : similar like this log "' '/system/bin/sh' failed: No such file or directory (2)'" .. it cannot find symlink. maybe problem is too simple. anyway we can't solve it...
If we can get adb probably we will get bootable 4.4 kitkat rom.. because something prevents to access somefiles or wrong setted symlinks causes that. dont know . i tried to solve..

2-
a guy found the problem..

thank you so much @skinbark
as i said in op. .. problem is too easy to fix but we dont know and i missed something. :)
you found that thanks again :)


@skinbark wrote "I looked at the ramdisk on your github and there's an error in your init.primou.rc where it says mount_all fstab.primoc and it should say mount_all fstab.primou (in 2 places). The reason you're not getting adb because /system isn't getting mounted."

so i looked in fstab.primou ... and i changed primoc values and poof i got logcat and system partition working good :D

but rom looks like very very very buggy..

as you can see here :

Code:
E/cutils-trace( 1633): Error opening trace file: No such file or directory (2)
F/libc    ( 1633): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 1633 (surfaceflinger)
I/DEBUG   ( 1488): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   ( 1488): Build fingerprint: 'htc_primou/primou:4.4/KRT16M/330937:user/user-debug'
I/DEBUG   ( 1488): Revision: '2'
I/DEBUG   ( 1488): pid: 1633, tid: 1633, name: surfaceflinger  >>> /system/bin/surfaceflinger <<<
I/DEBUG   ( 1488): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
...................................
3-Hi cyanogenmod 11 4.4.2 primou
Code:
I/cm      ( 1578): ____ _   _ ____ _  _ ____ ____ ____ _  _ _  _ ____ ___ 
I/cm      ( 1579): |     _/  |__| | | |  | | __ |___ | | |/| |  | |   
I/cm      ( 1581): |___   |   |  | | | |__| |__] |___ | | |  | |__| |__/ 
I/cm      ( 1587): Welcome to Android 4.4.2 / CyanogenMod-11-20131216-UNOFFICIAL-primou


XDA:DevDB Information
CyanogenMod 11 - Android 4.4 For PRIMOU(HTC ONE V) , a ROM for the HTC One V

Contributors
doga.ozkaraca, doga.ozkaraca
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod

Version Information
Status: Testing

Created 2013-12-10
Last Updated 2014-01-05
 

doga.ozkaraca

Inactive Recognized Developer
May 10, 2013
902
2,815
0
San Francisco, CA
dogaoz.com
I don't think so. I replaced it and updater-script with the ones from CDMA PrimoKat, resulted in worse, stuck on bootloader screen o_O
this error caused by update-binary?
i checked ext4 stuff in kernel defconfig..

did i miss something to add into defconfig ??

can somebody check kernel ??

i added lots of stuff twice.. and i checked..

but still i couldnt find ...
 

bradthomas127

Senior Member
Nov 6, 2012
225
325
0
Ft. Wayne
wp-ultra.com
Have you tried these commits for vold and media provider.

https://github.com/Mustaavalkosta/a...mmit/056a90abe45c32f7e5ae0b66e45e6cb74628f4c6

https://github.com/Mustaavalkosta/a...mmit/d75e64f348afff110af90d451840ba279ae0c942

I know Mustaavalkosta reverted them but he is having problems since he did and should be adding them back. They are needed for our non updated recoveries

I'm with out Internet right now so it's kind of hard for me to help you out, but I have been working on an ion kernel and just got it to boot so maybe we will be closer to using the same repos soon.

Sent from my Nexus 5 using xda app-developers app
 

skinbark

Senior Member
Nov 25, 2013
73
87
0
Dubuque, IA
Instead of mount all using fstab in init script try mounting partitions individually. Mount system read-write so it can set a checkpoint then unmount it and mount it read only. Mount system, data and cache the way it's done in CM10.2. Then you should get adb shell.
 
Last edited:
  • Like
Reactions: doga.ozkaraca

parkourz

Senior Member
Jul 8, 2011
942
181
0
Łódź
https://github.com/TeamPrimo/androi...c700#diff-0cb3afbdabb5622bd63ffed541baffa8R19

Hey mates..

probably that commit save our HOV lol

we have symlink problem.. so that commit changed fstab file :) so maybe it can detect ext4 partitions correctly and we can boot it..
I will test that these days :D
Dang it!!! HOV development is like me during my exams: I've failed few first attempts and everything seems that I'll fail them all, but at the end I've passed them all :p