5,599,190 Members 35,591 Now Online
XDA Developers Android and Mobile Development Forum

[KERNEL][AGNi][STOCK 4.3] 16-04-2014 AGNi pureSTOCK I605 MJ9+ (ULTRA SMOOTH)

Tip us?
 
xmxm
Old
(Last edited by xmxm; 16th April 2014 at 05:19 PM.) Reason: Found workaround
#231  
Junior Member
Thanks Meter 11
Posts: 13
Join Date: Sep 2010
Quote:
Originally Posted by psndna88 View Post
16-04-2014 Update v3.9.5
At the end of installation, I've got following error:
assert failed: getprop("ro.product.device") == "SGH-I317M" || getprop("ro.build.product") == "SGH-I317M"
Not sure if it it impacted the installation: About phone gives kernel version 3.0.101 AGNi@PSN-pureSTOCK #1 Mar-6-2014

I think that Verizon Galaxy Note 2 device code is SCH-I605 and not SCH-I317M.

UPDATE: I've manually removed assert from META-INF\com\google\android\updater-script and then it worked: about phone now shows Apr-16-2014 date for kernel.
 
psndna88
Old
#232  
psndna88's Avatar
Recognized Contributor - OP
Thanks Meter 4246
Posts: 3,149
Join Date: Dec 2011
Location: Mumbai

 
DONATE TO ME
Quote:
Originally Posted by xmxm View Post
At the end of installation, I've got following error:
assert failed: getprop("ro.product.device") == "SGH-I317M" || getprop("ro.build.product") == "SGH-I317M"
Not sure if it it impacted the installation: About phone gives kernel version 3.0.101 AGNi@PSN-pureSTOCK #1 Mar-6-2014

I think that Verizon Galaxy Note 2 device code is SCH-I605 and not SCH-I317M.
this is the assert used
Code:
assert(getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || 
       getprop("ro.product.device") == "SGH-I317M" || getprop("ro.build.product") == "SGH-I317M");
check if such values exist in ur /system/build.prop

else if u are on I605 or I317M remove the assert from the updater-script

it could also be caused by recovery problem.
AGNi Kernel
I9300, I9305, N7100, N7105, I605, P31xx, P511x


DONATE TO ME : send your donation directly by paypal to psndna88@gmail.com
The Following User Says Thank You to psndna88 For This Useful Post: [ Click to Expand ]
 
xmxm
Old
#233  
Junior Member
Thanks Meter 11
Posts: 13
Join Date: Sep 2010
Quote:
Originally Posted by psndna88 View Post
check if such values exist in ur /system/build.prop

else if u are on I605 or I317M remove the assert from the updater-script

it could also be caused by recovery problem.
Once I've removed assert completely, everything worked. My point was that the build for I605 should have SCH-I605 in assert, not SGH-I317M.

I've checked Ext2SD swap and it does not seem to work - SD Card does not appear at all. Here is the output of mount command once it is enabled in 3.9.5 build:

Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/menion.android.locus.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,errors=continue,user_xattr,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.abbyy.mobile.textgrabber.full-2 ext4 ro,dirsync,nosuid,nodev,noatime,errors=continue,user_xattr,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.abbyy.mobile.bcr-1 ext4 ro,dirsync,nosuid,nodev,noatime,errors=continue,user_xattr,barrier=1 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p13 /system f2fs ro,nosuid,nodev,relatime,background_gc=off,discard,user_xattr,inline_xattr,active_logs=2 0 0
/dev/block/mmcblk0p16 /data f2fs rw,nosuid,nodev,noatime,nodiratime,background_gc=off,discard,user_xattr,inline_xattr,active_logs=2 0 0
/dev/block/mmcblk0p12 /cache f2fs rw,nosuid,nodev,noatime,nodiratime,background_gc=off,discard,user_xattr,inline_xattr,active_logs=2 0 0
/dev/block/mmcblk0p14 /preload ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,discard 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p11 /tombstones ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p10 /firmware vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/container /mnt/shell/container sdcardfs rw,nosuid,nodev,relatime,uid=1000,gid=1000 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:49 /storage/extSdCard exfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro 0 0
tmpfs /storage/extSdCard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/mmcblk0p16 /storage/extSdCard f2fs rw,nosuid,nodev,noatime,nodiratime,background_gc=off,discard,user_xattr,inline_xattr,active_logs=2 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
If I understand correctly /dev/block/void/179:49 needs to be mounted to /mnt/shell/emulated/0 or something similar. This line (or similar) from the mount on previous version is missing:

Code:
/dev/block/vold/179:49 /mnt/shell/emulated/0 exfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro 0 0
The Following User Says Thank You to xmxm For This Useful Post: [ Click to Expand ]
 
nutpn
Old
#234  
nutpn's Avatar
Senior Member
Thanks Meter 49
Posts: 410
Join Date: Dec 2010
Location: ALABAMA
Default Agni kernel for the 4.1

Do you have an Agni kernel for the 4.1 or will this work for my 4.1. I'm still hanging on to it. Thanks

US Marines-"NO EASY DAY" Except Yesterday
Semper Fi
 
psndna88
Old
#235  
psndna88's Avatar
Recognized Contributor - OP
Thanks Meter 4246
Posts: 3,149
Join Date: Dec 2011
Location: Mumbai

 
DONATE TO ME
Quote:
Originally Posted by nutpn View Post
Do you have an Agni kernel for the 4.1 or will this work for my 4.1. I'm still hanging on to it. Thanks
not made for it.

Sent from F2FS FORMATED I9300XXUGNB6 NeatROM v7.2 + AGNi pureSTOCK v3.6 kernel
AGNi Kernel
I9300, I9305, N7100, N7105, I605, P31xx, P511x


DONATE TO ME : send your donation directly by paypal to psndna88@gmail.com
 
manbat
Old
(Last edited by manbat; Today at 04:38 AM.)
#236  
manbat's Avatar
Senior Member
Thanks Meter 162
Posts: 576
Join Date: Jun 2008
Location: Fort Worth, Texas
Thanks for the update....Just flashed. Straight forward install with no issues!!

Sent from my SCH-I605 / Galaxy Note 2 / JB 4.3 / Unlocked, Rooted, ROMed and ANGi-fied !!... using Tapatalk v 2.4.13
manbat

Samsung Galaxy Note II / Unlocked, Rooted and ROMed / JB 4.3
.........and
HTC / ReZound / S-OFF and Rooted / ICS 4.0.3 / 4.05.605.14 71ORD /....
.........and
Samsung Tab 3, 7 Tablet / Rooted / TWRP Recovery
.........and
(RETIRED) HTC / Touch Pro 2 / Mr. X Fixed Verizon MR2 ROM / WM6.5 / Sense 2.5 / Co0kies Home Tab v1.8.5 / WiMoSpeed v1.07


If I helped, please hit the "THANKS" button.
 
Shamestick
Old
#237  
Shamestick's Avatar
Senior Member
Thanks Meter 64
Posts: 357
Join Date: Oct 2012
Hey, I was just checking out partition table and I noticed that all the zram partitions were not mounted even though I have it turned on and I was wondering if that was normal or not?
Attached Thumbnails
Click image for larger version

Name:	1397976737474.jpg
Views:	0
Size:	57.0 KB
ID:	2697493  

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes