Develop Bugs

Nook Touch kernel hacking

So i have downloaded the nook touch kernel source and have gotten it to build using the gossamer defconfig. (as described somewhere by jesusfreke)
then as a test i enabled ext4 support and recompiled
then converted my system partition to ext4 while booted into noogie on the sdcard.
i also edited the init.rc to mount /system as ext4 and enable adb over usb support
and it seems like it works as shown in the code below.
Code:
[email protected]: nook_touch$ adb shell cat /proc/version
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #3 PREEMPT Tue Oct 4 14:37:59 CDT 2011
[email protected]: nook_touch$ adb shell cat /proc/mounts
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext4 ro,barrier=1,data=writeback 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
so where do i go from here? how do i start forward porting the kernel to .32 or .35 or do i even need to do that? in general what needs to change to get a cyanogenmod compatible kernel?
also how can we get a serial or UART output from the nook touch. I have been testing some cm builds from the nook color but it doesnt boot far enough for abd to give any output. ive looked at the back of the board but there doesnt seem to be any blatantly obvious serial port connections on it like the nook color has.
ps. uImage and uRamdisk are attached for reference. i try them if you want. but backup yours first!

Help this guy and include a Bitcoin address and I'll send you a coin

This the config you used?
--*removed*--
Edit: nvm, figured it out, and ty!
I ended up in a serious bootloop trying my compiled kernel and I got to test my recovery image in a new setting, it worked

ros87 said:
This the config you used?
omap3621_gossamer_defconfig
Click to expand...
Click to collapse
omap3621_gossamer_evt1c_defconfig

texasice said:
also how can we get a serial or UART output from the nook touch. I have been testing some cm builds from the nook color but it doesnt boot far enough for abd to give any output. ive looked at the back of the board but there doesnt seem to be any blatantly obvious serial port connections on it like the nook color has.
Click to expand...
Click to collapse
Can't find the link but someone thought there was serial pins under/near the sd card. Here is back of NT http://www.zdnet.com/photos/crackin...6244759?seq=32&tag=photo-frame;get-photo-roto
GL with this. I need to get GPS signals into my NT so subscribed

BTW, the memory is sadly only 256MB, not 512 as written in that article,
the K4X2G323PC-8G part number is mentioned here www .samsung .com /global/business/semiconductor/support/brochures/downloads/memory/SamsungPSG_july2010_final.pdf on page 10 as
2Gb MDDR 64Mx32 K4X2G323PC-8G(1) 90-FBGA 1.8V
That explains why the device reports MemTotal: 233024 kB in /proc/meminfo :-(

texasice said:
so where do i go from here? how do i start forward porting the kernel to .32 or .35 or do i even need to do that? in general what needs to change to get a cyanogenmod compatible kernel?
Click to expand...
Click to collapse
Hi,
nice to see that someone tries to get CM to the N2E.
I'm not really familiar with the process of porting CM, but I think the next step would be trying to build a working kernel from the Nook Color CM kernel sources.
It looks like most are in the /arch/arm/configs directory where a lot of definitions for the gossamer-board are missing.
Whats also missing is the touchscreen-driver drivers/input/touchscreen/zforce.c (and the according headers/configs), and the GPU/Epaper-driver (i think it is in drivers/video/omap3ep/, headers and configs have to be added too).
A good way to see what differences between the two kernels exist, is to get the version 1.1 original source for the nookcolor (Kernel version 2.6.29, same as the N2E kernel) and make a diff. http://images.barnesandnoble.com/PResources/download/Nook/source-code/nookcolor_1.1.tgz
At least thats what I will try, as soon as I find some time and get my nook.

CM should be possible. As the nook color and nook touch shares the similar hardware (at least same CPU board).
But at least we need some developer to build ClockworkMod for Nook Touch so we can copy the CM build to the device.
The bad side of the CM build is... we can't use the default Nook application anymore (unless we are going to modify the CM framework).
I guess Nook Touch is just a Android device running the "Nook" launcher, which the device should only run default book software. I wonder if it's possible to put a Nook Touch default reading software shortcut to "Go Launcher"?
mali100 said:
Hi,
nice to see that someone tries to get CM to the N2E.
I'm not really familiar with the process of porting CM, but I think the next step would be trying to build a working kernel from the Nook Color CM kernel sources.
It looks like most are in the /arch/arm/configs directory where a lot of definitions for the gossamer-board are missing.
Whats also missing is the touchscreen-driver drivers/input/touchscreen/zforce.c (and the according headers/configs), and the GPU/Epaper-driver (i think it is in drivers/video/omap3ep/, headers and configs have to be added too).
A good way to see what differences between the two kernels exist, is to get the version 1.1 original source for the nookcolor (Kernel version 2.6.29, same as the N2E kernel) and make a diff. http://images.barnesandnoble.com/PResources/download/Nook/source-code/nookcolor_1.1.tgz
At least thats what I will try, as soon as I find some time and get my nook.
Click to expand...
Click to collapse

winstonma said:
CM should be possible. As the nook color and nook touch shares the similar hardware (at least same CPU board).
Click to expand...
Click to collapse
I described in my last post what hardware is different, and what has to be changed in the kernel. But now I think we could also try the standard Nook-Touch kernel, but we have to put all the userland files in place.
But at least we need some developer to build ClockworkMod for Nook Touch so we can copy the CM build to the device.
Click to expand...
Click to collapse
CWM-Recovery would be nice, but isn't necessary for CM. We could start with a bootable SD like it was done with CM for the Nook Color.
I guess Nook Touch is just a Android device running the "Nook" launcher, which the device should only run default book software. I wonder if it's possible to put a Nook Touch default reading software shortcut to "Go Launcher"?
Click to expand...
Click to collapse
Take a look at XorZones work http://forum.xda-developers.com/showthread.php?t=1289894

As we have the full source of Nook Touch, is it possible to get Nook Touch as Official CM port?
I have the gut feeling to follow the Nook Color: Full Update Guide and install CM. So I believe it's nice to have ClockworkMod Recovery on Nook Touch.
By the way this is the Nook Touch 1.1 Source from B&N.
I am still waiting for my Nook Touch. It'll arrive 2 weeks later.
To be honest I don't need the B&N service. I just treat this device as e-ink Android Tablet. So I really enthusiastic to make CM port as official.
Is it possible to join as a team and work together?

Is it only me thinking that undervolting this overpowered ebook, would make us get that extra inch in battery life we all (I) want?
I'll look into making this kernel overclockable when I have a bit of free time.
If someone looks into it before I do better

Now, before we go on about kernel hacking, can someone actually provide a fully working kernel compiled from sources?
I spent a few hours on it (1.1.0 sources) tonight and this is how far I got:
dmesg:
http://pastebin.com/VUv74LFV
logcat:
http://pastebin.com/cGpkAz3n
Basically it's running and I can access it, but I have some trouble with the SGX (no graphics)
This is omap3621_gossamer_evt1_defconfig btw.

Wikipedia tells me NST uses an OMAP3611, there's very little diference between the two (OMAP3621) but something must screw up the output.
http://en.wikipedia.org/wiki/Texas_Instruments_OMAP#OMAP_3
---------- Post added at 01:25 AM ---------- Previous post was at 01:19 AM ----------
Allthough our NST works at 800mhz, so maybe wiki is wrong.
Here it's reported as an OMAP3621 so forget what I said.
http://forum.xda-developers.com/showthread.php?t=1251209

eded333 said:
Wikipedia tells me NST uses an OMAP3611, there's very little diference between the two (OMAP3621) but something must screw up the output.
Click to expand...
Click to collapse
NST uses Omap3621 as I can tell you from my opened NST laying in front of me
If you need more proof:
http://www.techrepublic.com/photos/...34&tag=thumbnail-view-selector;get-photo-roto
Most likely the gossamer evt1 config is the wrong one, but the edp1 (epson digital paper) config doesn't compile at all..
Weekend and GF-time is coming up so I won't be continuing this until Sunday evening.
---------- Post added at 01:36 AM ---------- Previous post was at 01:32 AM ----------
Anyway, it's close as everything is running, including Dalvik
Will figure it out next week

f*****g wiki, they must allways have something wrong.
Good work! It'll be done when it's done but didn't expect to see so much progress in so little time

ros87 said:
Now, before we go on about kernel hacking, can someone actually provide a fully working kernel compiled from sources?
I spent a few hours on it (1.1.0 sources) tonight and this is how far I got:
dmesg:
http://pastebin.com/VUv74LFV
logcat:
http://pastebin.com/cGpkAz3n
Basically it's running and I can access it, but I have some trouble with the SGX (no graphics)
This is omap3621_gossamer_evt1_defconfig btw.
Click to expand...
Click to collapse
Hi,
building from the 1.1 source with the omap3621_gossamer_evt1_defconfig configuration works great for me. The kernel runs perfectly, no problems with the display, touchscreen or wifi. Can't notice a difference between the stock and self-built-kernel.
I used arm-eabi-4.4.0 to build it.

Great! Which means we can build CM and get official build-bot.
But back to the point. But it'll be great if we can load the new Android ROM into our device.
So back to the basic question. Should we build recovery like CWM?
Sent from my Liquid using Tapatalk

winstonma said:
Great! Which means we can build CM and get official build-bot.
Click to expand...
Click to collapse
No it doesn't! Thats just the kernel. Getting CM running is a much harder task.
So back to the basic question. Should we build recovery like CWM?
Click to expand...
Click to collapse
If you can build CWM for the N2E than please do it. I tried, but had no success.

mali100 said:
No it doesn't! Thats just the kernel. Getting CM running is a much harder task.
Click to expand...
Click to collapse
I agree that CM would be tougher than building a kernel. But there are guides. Teaching us how to grab a built CM, swap the kernel, and it boots. So we can try that. But still, we need the recovery to "install" our build.
If you can build CWM for the N2E than please do it. I tried, but had no success.
Click to expand...
Click to collapse
I know it's not easy. But we have no choice but to get this step done if we need full access (like installing custom ROM). I will start trying once I grab my N2E.

mali100 said:
Hi,
building from the 1.1 source with the omap3621_gossamer_evt1_defconfig configuration works great for me. The kernel runs perfectly, no problems with the display, touchscreen or wifi. Can't notice a difference between the stock and self-built-kernel.
I used arm-eabi-4.4.0 to build it.
Click to expand...
Click to collapse
Hi
That post got outdated quite quickly as I managed to figure it out the day after posting it.
There was no problem with my build, but there's something really important missing in the Kernel sources, kernel modules for the PowerVR graphics.
So yes, you can build that config and push the kernel to a working NST and it will work as expected, but as we don't have the source code for the modules there's a limit to what we can actually do.
From my experience there only so much you can change in the Kernel before having to recompile the modules..
To be continued..

[HOWTO] Build CM10 For The I957

First things first: THANK YOU to all those involved in the coding of this, especially the msm8660-common kernel that so many folks have put so much effort into, and Mr. Cyanogen for the device tree, etc etc. NONE of this would be possible without your efforts. I stand on the shoulders of giants in providing these instructions, the code is NOT mine, I'm just documenting this so you all can help contribute. Kindest regards to everyone who has contributed to make this possible. Your work has enabled the community to beat the vendor to the punch, yet again!
DISCLAIMER: This contains information on working with very early code as well as hacking together a completely unsupported Frankenstein build with some proprietary samsung binaries from another device (ATT Note) and I will warn you: If you aren't willing to risk bricking your device, don't even think about this. Also, I'm not so much a coder as I am a QA engineer, so I know enough to be dangerous, but I couldn't code C++ get myself out of a virtual crashing airplane if I had to. I also might not be able to help you out of a sticky situation, so... have fun at your own risk! But do have fun
Looking for binaries? See post #2
That said, it's honestly not likely any of this will brick your tab, if you know what you're doing, but... early software always carries danger, and using binaries from a similar yet different device can do who knows what.
Also of note: you should probably back up your EFS partition if you're going to hose with the radios to get cellular data working... hasn't been an issue for me, but... corrupt EFS partition = no more cellular data for you. ever.
Cyanogen has added initial support for the i957 to the CM10 repository, and it's looking good so far! But, there are no nightly builds yet, probably because Cyanogen would like to do some more work on it before handing out binary packages... Or maybe he hasn't figured out how to get things quite functional yet. I considered releasing a binary package for you to toy with, but then realized that would defeat the purpose of helping along the development of an official Cyanogen i957 (p5att) release, and lock you into something I already built from "pre-alpha" code. It's best to check out the latest source tree and do your own build, then you can easily test and contribute your modifications, should you find any.
So with that, here's some instructions on how to build CM10 for your SGH-I957 ("p5att") device from source code. This will also ensure time is spent doing development work, not hand-holding the faint of heart (sorry, sue me!)
These instructions assume you've successfully built Cyanogenmod for a supported device and understand the basics of getting things going. If not, start with that first, then come back to this. I'm also assuming you've got the android tools that you get from any build of cyanogen (like mkbootimg) in your path for some of the "optional" steps, which is of course elementary...
I'm also going to assume you know what to do with the resulting zip... You know... backup, factory reset, wipe system, flashy the zippy...
I really recommend doing the boot image modifications after the build, without ADB on boot, if something goes wrong, you'll have no way of knowing whats going on. If you get the boot image modified properly as detailed below, you will be able to ADB to the device as soon as the second boot logo disappears. Also, there's probably a cleaner way (like changing something somewhere to invoke one of the other case statements in init.qcom.usb.rc), but I didn't have any luck with that. Feel free to school me! :laugh:
EDIT: If you don't feel like hacking the boot image, just flash the one attached (ps: none of the zips below are TWRP/CWM flashable, just zipped up files.. dd if=bootimagefilename of=/dev/block/mmcblk0p8 from a root shell to flash the boot partition on the i957)
I've attached the initlogo.rle file to this post so you don't have to fish it out of the ramdisk embedded in the stock boot image. Adding initlogo.rle to the ramdisk gives you confirmation the kernel is bootstrapping, and it's disappearance indicates ADB is now available. Also, use a linux box for ADB! silly wabbit, windoze is for kids.
According to comments in system.prop, the cyanogenmod boot animation is disabled because the framebuffer is "weird". Strangely, it sometimes displays for me, one in 10 boots maybe. Weird!
Here goes.
----
Initialize Repo:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
Sync Repo:
repo sync -j6
... Coffee Break!
Breakfast for p5att:
. build/envsetup.sh && breakfast cm_p5att-userdebug
Modify device/samsung/p5att/BoardConfig.mk to clean up a few things:
Comment out:
#BOARD_SDCARD_DEVICE_PRIMARY := /dev/block/mmcblk1p1
#BOARD_SDCARD_DEVICE_SECONDARY := /dev/block/mmcblk0p28
#BOARD_SDEXT_DEVICE := /dev/block/mmcblk1p2
Add above these lines:
BOARD_HAS_SDCARD_INTERNAL := true
Modify device/samsung/p5att/device-proprietary-files.txt:
Comment out all the entries, because they aren't really needed and probably dont work with jellybean. Worry about this later, blah blah.
Modify device/samsung/msm8660-common/common-proprietary-files.txt:
Comment out all the WiFi stuff, that is, like:
# Wi-Fi
# etc/wifi/bcm4330_apsta.bin
#etc/wifi/wl
#etc/wifi/nvram_net.txt
#etc/wifi/wpa_supplicant.conf
#etc/wifi/bcm4330_p2p.bin
#etc/wifi/bcm4330_sta.bin
#etc/wifi/bcm4330_mfg.bin
#etc/wifi/nvram_mfg.txt
To get WiFi working later, you need /system/etc/wifi/* from your honeycomb image. Go save them to /sdcard/wifi or something like that now, so you can just copy them over after CM10 boots
Edit: attached the files
Extract proprietary files from i717 Note CM10 image, since I have no idea where else to get these files, and they work:
from device/samsung/p5att, run ./extract-files.sh <path to an extracted CM10 i717 nightly .zip>
... The path you provide should contain the "system" folder.. IE the root of the extracted nightly zipfile.
I had used the 0831 nightly with luck here.
Get prebuilts:
run vendor/cm/get-prebuilts
Do the build:
from the system directory of your CM10 source tree run:
. build/envsetup.sh && brunch p5att
Go find something or someone to do, this is going to take a while...
You'll end up with a .zip file to flash.
After you flash, you'll need to, manually:
1) Copy back the /system/etc/wifi/* files (wifi firmware/tools, the note ones dont seem to work).
2) Install a Skyrocket ICS AT&T radio if you want cellular data, the honeycomb radio doesn't seem to work with CM10. UCLF6 works for me, although it's slower to acquire LTE than the official samsung HC image... but it works great once it finds a cell, and HSPA comes up pretty fast.
3) Consider doing the stuff below to enable early ADB and add back the second samsung logo, for debugging purposes, if you care...
----
Things you might want to do after the build, start by unzipping the resulting .zip pacakge...
Edit: I attached a the resulting boot.img to this post so you don't have to do all this if you so desire. Bonus: working i957 JB kernel binary for whatever else you might want to do with it..
Remove the assert for platform type if your TWRP recovery, like mine, thinks it's a i717 Note:
Edit META-INF/com/google/android/updater-script, remove the assert lines (first two lines of that file)
Do some handy ramdisk hacks:
First, unpack the boot image. From the root of what you unzipped:
mkdir boot
unpackbootimg -i boot.img -o boot
cd boot
Then Unpack the initial ramdisk:
mkdir rd
cd rd
zcat ../boot.img-ramdisk.gz | cpio -id
Edit init.qcom.usb.rc to enable early adb:
Search for "on property:sys.usb.config=mtp", you'll find: (line 340, for me)
on property:sys.usb.config=mtp
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 04E8
write /sys/class/android_usb/android0/idProduct 6860
write /sys/class/android_usb/android0/f_acm/acm_transports tty
write /sys/class/android_usb/android0/functions mtp,acm
write /sys/class/android_usb/android0/enable 1
setprop sys.usb.state $sys.usb.config
Make this section like:
on property:sys.usb.config=mtp
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 04E8
write /sys/class/android_usb/android0/idProduct 6860
write /sys/class/android_usb/android0/f_acm/acm_transports tty
write /sys/class/android_usb/android0/functions mtp,acm,adb
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state $sys.usb.config
Add the glowing samsung initlogo:
Copy initlogo.rle from the root of a stock ramdisk to the root of this ramdisk
... So you'll get the second samsung logo, so you know the kernel is bootstrapping... if you care.
Turn off ro.secure:
Edit default.prop in the root of the ramdisk and change:
ro.secure=1
to
ro.secure=0
Repack the ramdisk:
find . | cpio -o -H newc | gzip > ../boot.img-ramdisk.gz
(you may want to save the original, if you care)
Make the new boot.img:
cd .. (ie get back to the directory with the files listed in the next line)
rm ../boot.img
mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --cmdline "console=ttyHSL0,115200,n8 androidboot.hardware=qcom" --base 48000000 --ramdiskaddr 49400000 --pagesize 2048 -o ../boot.img
Repack the flashable zip:
cd .. (ie get back to where you unzipped the original flashable .zip)
rm -rf boot (remove the extracted boot.img and ramdisk under it, save it somewhere if you care)
(also remove the original .zip from here if you extracted it in the cwd)
zip -r ../somezipname.zip .
Then flash somezipname.zip or whatever you called it..
(Remember you'll need to put the Honeycomb files from /system/etc/wifi into /system/etc/wifi of the running image after you boot if you want wifi
(And flash a Skyrocket ATT radio if you want cellular data!)

WARNING: FOR SAMSUNG SGH-I957 NORTH AMERICAN DEVICES ONLY
GT-SERIES (IE: GT-7320, etc) ARE NOT SUITABLE FOR THIS RELEASE
UPDATE ZIP DOES _NOT_ CHECK YOUR PRODUCT CODE, WILL HAPPILY EAT OTHER DEVICES
THIS IS A TEST RELEASE FOR EXPERIENCED ANDROID HACKERS
SOME FEATURES MAY NOT BE USABLE OR WORK AS INTENDED
BOOTLOOP ISSUE? USE TWRP 2.1.4: https://www.dropbox.com/s/u07zrx808a5ae2z/i957_twrp_recovery.img.tar
Latest Flashable .ZIP, update 7: http://droid.arm.ee/957/cm10_p5att_nrvate_testrelease7.zip
Use TWRP, factory reset and wipe /system if you are coming from another ROM. Don't forget to install google apps http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
Update 2
* h264 hardware decode fixes for youtube HQ and other hardware-decode enabled apps (vidc/yamato firmware update)
* camera fixes from kunals.shah -- thanks!! (camera library in system/lib/hw)
* wifi address fix - get MAC from EFS, no more random address (insert proper path to .nvmac.info in dhd.ko kernel module)
* move /mnt/secure to internal sdcard to fix asec apps (asec folder linked to /sdcard/.asec)
* disable adb on early boot -- fix mtp maybe? (change to init scripts in ramdisk)
* remove a couple of (probably) harmless references to sdcard1 in init scripts
* update vold.fstab with the correct partition for the sdcard (26), not sure if anything even uses that, but...
Update 3
* Kernel Lovins ->
--- Picked up slew of bugfixes from msm8660-common cyanogenmod jellybean kernel tree -- up to and including 09/13/2012 commits.
--- Enabled CONFIG_USB_ANDROID_SAMSUNG_MTP and CONFIG_SPI_QUP kernel options to match SHV-140 ICS samsung kernel config
--- Disabled CONFIG_XVMALLOC and CONFIG_ZRAM kernel options, also to match up to SHV-140 ICS samsung kernel config
--- Now compiled with newest Sourcery cross-compiler
--- Modified dhd.ko (Broadcom WiFi kernel module) -- you can now create file /data/.ranmac if you want your MAC address randomized on each reboot (ignores MAC on EFS partition, random generation expanded to 5 bytes)
* symlink for light sensor (/dev/i2c11 -> /dev/i2c-11) -- Doesn't fix auto brightness, but at least things that access the light sensor via the standard API will get values back now, FWTW.
* RIL stuff from SHV-140S (korean Tab 8.9 LTE) -- An attempt to resolve SIM_NOT_READY error -> Files replaced:
/system/lib/libril-qcril-hook-oem.so
/system/lib/libsecril-client.so
/system/lib/libreference-ril.so
/system/lib/libril.so
/system/lib/libril-qc-qmi-1.so
/system/bin/qmuxd
/system/bin/qmiproxy
/system/bin/netmgrd
* Update /system/etc/wifi stuff -- newer broadcom firmware images, wpa_supplicant.conf with p2p parameters
* Reenable early ADB since it appears MTP issues likely related to lack of CONFIG_USB_ANDROID_SAMSUNG_MTP kernel option -- Maybe someone who uses MTP can tell me whats up now?
Update 4
* Fix A2DP bitrate (48000 -> 44100 in /system/etc/audio_policy.conf)
* More invasive ASEC fix that might actually fix this jellybean nonsense (modified vold to use /data/secure locations, create /data/secure directory tree in init.emmc.rc)
* Revert SHV-140 RIL change, back to Note CM10 RIL libraries
Update 5
* Android 4.1.2 - Complete rebuild from CM10 tree retrieved on October 12th. Includes ASEC hack as in update4.
* SGH-i957 Radio Information Libraries (RIL) from official Telus ICS image - Thanks Dan!
Update 6
* Rebuilt from CM10 source code retrieved Nov 10 2012. ASEC hack applied.
* Update to latest msm8660-common kernel. Kernel unmodified (ie: no overclocking).
Update 7
* Rebuilt from CM10 source code retrieved Dec 20 2012. ASEC hack applied.
* Update to latest msm8660-common kernel. Kernel unmodified (ie: no overclocking).

Fantastic!
Are you saying everything seems to work pretty well except the 4G radio? (No guarantees, at my own risk, etc. etc. I know, I won't blame you)
If so, I'm going to try this right away. I don't have a data plan for my SIM, and haven't used the 4G yet. (Got a free upgrade from the wifi version after some shipping trouble with the vendor.)
The Galaxy Tab has been kind of a letdown when I have JB on my Galaxy Nexus and Kindle Fire both, and the "upgrade" is a bit disappointing since I checked on custom ROMs *before* I ordered, but the AT&T version is further behind.
Thanks for your hard work! I'll let you know what happens.

YellowRex said:
Fantastic!
Are you saying everything seems to work pretty well except the 4G radio? (No guarantees, at my own risk, etc. etc. I know, I won't blame you)
Thanks for your hard work! I'll let you know what happens.
Click to expand...
Click to collapse
I haven't had time to try "everything", but the stuff that I use on a regular basis is mostly functional. There's quirks, but... It's usable!
For example, one thing I just found out.. the Adreno (qualcomm MSM graphics) drivers aren't production-build.. There's no such thing available -- The current drivers available from qualcomm are "early sample" binaries for jellybean bringup testing, which is what this is... So, I've seen the random screen flicker, etc. Remember there are only a few devices with tested jellybean images, and most of them are google devices... And the i957 will probably never see an official JB release.
https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources
This release contains an early sample of the user-mode driver binaries for Qualcomm's Adreno 2xx GPU on Google Android 4.1 Jelly Bean. It has been tested with the CAF release M8960AAAAANLGD105210.1 and supports any Adreno 2xx GPU on Android 4.1 Jelly Bean. This release is intended only for developers that work on Jelly Bean bring-up work. It is an early release sample which will be replaced by a new driver binary in the future.
Click to expand...
Click to collapse
I'm sure there's plenty of little quirks you can find if you "twiddle all the knobs and flip all the switches" -- But it's certainly testable, and way closer to the "usable" end of the spectrum than the "barely functions" end.
Cheers!

PRE-ALFA CM10 Build
You did a great job nrvate !!. you inspired me to get ICS/JB on my SGH-i957. I did try your method and seems everything (3G, SMS, GPS, Bluetooth, Camera etc..) works except wifi. I am surprised that Voice calling is also working in this build !!! I will update you once I fix wifi issue. and also provide CWM/TWRP/ODIN flashable build if time permits.
Cheers !!
-KS

Its so exciting to see some real pregress.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

Ditto. This is really good news. Thanks.

Cheers, y'all!
Only thing I had to do to get wifi working was stuff the original stuff (from honeycomb) in /system/etc/wifi.
first thing I'd do is make sure the dhd module is getting loaded.. dmesg will print your kernel log that'll show problems with loading that module.. also, try rmmod dhd and insmod dhd, see what happens.
If the DHD module doesn't report symbol errors or some nasty like that, make sure it's loading the firmware -- That'll probably leave an error in dmesg also if it's broke.
also check logcat for wifi-related nastiness
If you can find a specific problem post it and I'll try to help reproduce/solve.
Also working on hacking together a build of ICS based on what's been done with JB, but no idea how that's going to turn out yet. It'd be nice to have as a daily until qualcomm releases production-grade adreno graphics drivers (and, the CM9 ICS tree is now "final", might as well build it!)
update: due to needing the "late model" msm8660-common kernel for proper i957 device support, the later qualcomm (JB) graphics drivers are required too.. drat! however, looks like I'll still be able to hack together a build of CM9 based on the current "final" ics branch using the JB kernel and beta qualcomm graphics. got 'er booted, working out the kinks now. I'll start another thread for that when it's done

i wish i knew half as much as you do, keep up the good work!

orlandoxpolice said:
i wish i knew half as much as you do, keep up the good work!
Click to expand...
Click to collapse
Thanks! Learning as I go with half this.. It's just bits, try one way, get dirt.. try another way, get bacon!
Some of this is so touchy.. ie kernel versions vs adreno drivers, blah blah.. seeing what the SHV-140 kernel does.. it boots CM9, now to see if it'll play nice with video decoders. might forget CM9, i <3 jelly beans anyways!

nrvate said:
Thanks! Learning as I go with half this.. It's just bits, try one way, get dirt.. try another way, get bacon!
Some of this is so touchy.. ie kernel versions vs adreno drivers, blah blah.. seeing what the SHV-140 kernel does.. it boots CM9, now to see if it'll play nice with video decoders. might forget CM9, i <3 jelly beans anyways!
Click to expand...
Click to collapse
Solid work/mashery my friend. This indeed great news. I am currently waiting for my zip file to spit out, do a few mods and then give it a flash when I complete those things.
As far as the adreno drivers have you checked the site for them? I recall reading about them on another msm8660 device and perhaps may pertain to this project as well. The screen flicker has a few work arounds based on other devices that may relate to this device as well. Either to get rid of the flicker entirely or at least minimize them. Worth trying (here are a few I have seen work on some devices.. dev options, disable HW overlay, another is adjusting the debug.mdpcomp.maxlayer value in build.prop from 3 to 2, another is to set the min CPU freq to 486mhz).. last but not least, this was posted on cyanogenmod review, and can be cherry picked if not merged already: http://review.cyanogenmod.com/#/c/22782/ and may work. As far as getting LTE to light up in a more prompt manner, it may be worth exploring different modems (I see you are using UCLF6 from the i717 note), there are many others from the i717 leaks (ie. UCLF5, UCLE2/3, etc etc) and also of course any other Skyrocket ICS+ modems, as well as i717m (canadian, rogers modems such as XLA2 (gingerbread but worked on the i717 note in the US) and various others. If you cannot located them I will post links when I have more time. This is a great start, and I will help out when I have time to contribute to this project (I have a few on my plate plus a full time job so sometimes having the time is a difficult venture). In any case, great start and I can see this will progress very well in due time. Congrats and thanks for your contribution to the base of this, as this progresses and we work to manage these small issues, we will have something even solid
Regards,
th3g1z

th3g1z said:
Solid work/mashery my friend. This indeed great news. I am currently waiting for my zip file to spit out, do a few mods and then give it a flash when I complete those things.
As far as the adreno drivers have you checked the site for them? I recall reading about them on another msm8660 device and perhaps may pertain to this project as well. The screen flicker has a few work arounds based on other devices that may relate to this device as well. Either to get rid of the flicker entirely or at least minimize them. Worth trying (here are a few I have seen work on some devices.. dev options, disable HW overlay, another is adjusting the debug.mdpcomp.maxlayer value in build.prop from 3 to 2, another is to set the min CPU freq to 486mhz).. last but not least, this was posted on cyanogenmod review, and can be cherry picked if not merged already: http://review.cyanogenmod.com/#/c/22782/ and may work. As far as getting LTE to light up in a more prompt manner, it may be worth exploring different modems (I see you are using UCLF6 from the i717 note), there are many others from the i717 leaks (ie. UCLF5, UCLE2/3, etc etc) and also of course any other Skyrocket ICS+ modems, as well as i717m (canadian, rogers modems such as XLA2 (gingerbread but worked on the i717 note in the US) and various others. If you cannot located them I will post links when I have more time. This is a great start, and I will help out when I have time to contribute to this project (I have a few on my plate plus a full time job so sometimes having the time is a difficult venture). In any case, great start and I can see this will progress very well in due time. Congrats and thanks for your contribution to the base of this, as this progresses and we work to manage these small issues, we will have something even solid
Regards,
th3g1z
Click to expand...
Click to collapse
Thanks for the input! The flicker, as is, is really minor. It only really seems to happen, for me atleast, in the main launcher window and sometimes when scrolling in maps. It's intermittent, actually. I will have a look at that change you linked, nice catch!
Qualcomm's dev site is linked in post #4, hopefully they will post the final drivers soon. Do they have another site that would receive them faster, or with incremental builds? I really wish OEMs would share engineering builds more openly with the community, but I guess I'm just used to being on an engineering team, lol. I've been spoiled with working for a few of the larger OEMs and getting all the cool toys first...hehe.
I tried a few of the note ICS radios, got nothing at all from them besides errors in logcat -b radio, wouldn't bring up the SIM.
All the skyrocket radios seem to work to varying degrees.
Also, it may be more of the RIL -- The UCLF6 skyrocket modem works very nicely on the stock honeycomb image, insta-LTE and everything.
I have not tried any of the non-ATT radios... wasn't sure how that'd work out. I'll give some of the non-ATT radios a go, why not! Besides Skyrocket or Note, any other similar devices? Only thing I can think of is the SGS II LTE HD (SGH-i757) but not much is available for that device as AT&T punted it for the S III (747) and it never got popular.. If you want the HD screen, you get a S-III, which came out about a month later, which is just why ATT punted it all together.
I hear you on the job. I've got an interview lined up for a better one, too! Man, I'm hoping that works out!

nrvate said:
Thanks for the input! The flicker, as is, is really minor. It only really seems to happen, for me atleast, in the main launcher window and sometimes when scrolling in maps. It's intermittent, actually. I will have a look at that change you linked, nice catch!
Qualcomm's dev site is linked in post #4, hopefully they will post the final drivers soon. Do they have another site that would receive them faster, or with incremental builds? I really wish OEMs would share engineering builds more openly with the community, but I guess I'm just used to being on an engineering team, lol. I've been spoiled with working for a few of the larger OEMs and getting all the cool toys first...hehe.
I tried a few of the note ICS radios, got nothing at all from them besides errors in logcat -b radio, wouldn't bring up the SIM.
All the skyrocket radios seem to work to varying degrees.
Also, it may be more of the RIL -- The UCLF6 skyrocket modem works very nicely on the stock honeycomb image, insta-LTE and everything.
I have not tried any of the non-ATT radios... wasn't sure how that'd work out. I'll give some of the non-ATT radios a go, why not! Besides Skyrocket or Note, any other similar devices? Only thing I can think of is the SGS II LTE HD (SGH-i757) but not much is available for that device as AT&T punted it for the S III (747) and it never got popular.. If you want the HD screen, you get a S-III, which came out about a month later, which is just why ATT punted it all together.
I hear you on the job. I've got an interview lined up for a better one, too! Man, I'm hoping that works out!
Click to expand...
Click to collapse
I hear you on OEM not releasing the drivers in a timely fashion, and it is frustrating when you have sources for it as "leaks" .. pertaining to your question I did see a link to update drivers but in my 5 min search (short on time atm, work early in the morning), I didn't find it yet, but I will look a bit deeper and hopefully can find it. I recall it related to CM10 and addressing said drivers for a particular device or devices. I will see what I can find tomorrow, and hope that it pertains.
No harm in trying a few other modems, I would look at the i717/i717m (m is the canadian model, same device though and the modems from rogers work with the i717 as well as the skyrocket).. and obviously the skyrocket various modems which it seems you have tried at least a few of. They vary so much and your location has a lot to do with it. Some work better in certain areas, and others in other areas as I'm sure you know already. Worst case, even after trying a few you can always go back to UCLF6. I found it a bit odd that the rogers modems worked with ATT but hey I'm not complaining about that one I believe you are correct, however, pertaining to the RIL as being the issue, not so much the modem's themselves. (no telling though without trial/error)
I'm not sure the i747 modems would work or not, but, it will not hurt to try, as you can return to UCLF6 if it is a dead end. the i757 I have yet to even see, so I can't comment on that in particular.
I'd like to chat a bit more when we both have some time, not sure if you get on IRC (freenode network) at all but if you do look me up, same handle as here on XDA. It would be easier to chat that way.
I have more to say but having to be away in about 4 hours, I will have to get back to you. Good luck w/ the interview bud.
Take care, we'll catch up soon.
~th3g1z

th3g1z said:
I hear you on OEM not releasing the drivers in a timely fashion, and it is frustrating when you have sources for it as "leaks" .. pertaining to your question I did see a link to update drivers but in my 5 min search (short on time atm, work early in the morning), I didn't find it yet, but I will look a bit deeper and hopefully can find it. I recall it related to CM10 and addressing said drivers for a particular device or devices. I will see what I can find tomorrow, and hope that it pertains.
No harm in trying a few other modems, I would look at the i717/i717m (m is the canadian model, same device though and the modems from rogers work with the i717 as well as the skyrocket).. and obviously the skyrocket various modems which it seems you have tried at least a few of. They vary so much and your location has a lot to do with it. Some work better in certain areas, and others in other areas as I'm sure you know already. Worst case, even after trying a few you can always go back to UCLF6. I found it a bit odd that the rogers modems worked with ATT but hey I'm not complaining about that one I believe you are correct, however, pertaining to the RIL as being the issue, not so much the modem's themselves. (no telling though without trial/error)
I'm not sure the i747 modems would work or not, but, it will not hurt to try, as you can return to UCLF6 if it is a dead end. the i757 I have yet to even see, so I can't comment on that in particular.
I'd like to chat a bit more when we both have some time, not sure if you get on IRC (freenode network) at all but if you do look me up, same handle as here on XDA. It would be easier to chat that way.
I have more to say but having to be away in about 4 hours, I will have to get back to you. Good luck w/ the interview bud.
Take care, we'll catch up soon.
~th3g1z
Click to expand...
Click to collapse
I'll hit you up on IRC at some point for sure
So I sort of figured it out... Found how to get the radio to play nice, still don't know why... The kernel! Went back to the 3.0.8 kernel as provided by samsung for the SHV-140 (replaced zImage in boot.img, reflashed mmcblk0p8) and BAM. Nice quick 4G. Nothing in /system changed (so a bunch of other stuff broke) but the radio sure got happy.
Not sure what the difference is, quite yet... Should be an interesting needle in the hackstack for sure.

Is the package manager a problem with this the same as cm9?
Sent from my SGH-I727 using xda premium

orlandoxpolice said:
Is the package manager a problem with this the same as cm9?
Click to expand...
Click to collapse
yes, the issue actually originated with jellybean -- since there's no device tree in the cm9 repo for the p5att, i jammed the cm10 p5att device tree into cm9 source to make it happen. the device tree includes the init scripts, so the problem actually originated from cm10, lol.
same fix works.. mount tmpfs on /mnt/secure (in addition to /tmp/asec) and use wide-open (777) permissions.

nrvate said:
same fix works.. mount tmpfs on /mnt/secure (in addition to /tmp/asec) and use wide-open (777) permissions.
Click to expand...
Click to collapse
Heh! Is it just me or does that feel a little less than 'secure'? :silly:

i feel like a english lit major walking into an advanced calculus class with this jargon

This is how the sausage gets made.

Speaking of making sausage, I'm starting to think this is stable enough to share a binary build...
1) Camera is borked. I'm at a bit of a loss to figure it out, maybe I'll try again next week -- Suggestions very welcome, I'd like to get this working for video chat ala skype / gtalk.
2) MTP is borked. Again, at a bit of a loss, I suppose I'd care if I used it... Silly MTP.
3) New kernel fixes radio issues (mostly) - I've had it completely refuse to come up, showing no signal, fixed by rebooting the tablet. Goes right to LTE, but defaults to HSPA only. Change to LTE / GSM / WCDMA in mobile network settings -> network mode.
4) /mnt/asec / /mnt/secure issue (play store install problems) resolved.
5) FC in Settings -> Storage resolved by removing sdcard1 (which will never exist) from the build config
6) Boot animation is disabled due to framebuffer problems (supposedly) -- i know the spinny thing is cool, but you'll have to live with a black screen. Strangely, it comes up on some boots. lol.
7) Qualcomm graphics drivers are still the pre-release version. They seem to work pretty nice though. Haven't seen any of the flickering since some mdp changes in the kernel.
8) Video codecs aren't as screwed up as they are in the ICS build I did -- IE youtube works for all the videos I tried and bsplayer for android nicely plays my favorite x264 720P tv shows (win! gotta keep myself entertained at work some how...)
9) overclocked kernel HACK WARNING for you purists -- Modifed the kernel slightly, it now recognizes all MSM8660's as having the higher binned speed (1.66 vs 1.50 ghz) -- I didn't touch the frequency tables or anything, since it made more sense to just recognize the parts as 1.66ghz parts. Also, removed the logic that limited single-core mode to 1.2ghz (why?!). Gabe put out a OC kernel and most people reported stability at 1.7+ ghz, so... 1.66 seemed good. Hasn't borked for me. If you want stock speeds bad enough or run into problems.. http://d-h.st/8mB
Usual procedure, TWRP.. factory reset, wipe system, flash zip, receive bacon.
Bacon: http://d-h.st/Klu
I've been using this as my daily the past few days, and unless it starts behaving badly for some reason, it's probably going to be my daily for the foreseeable future. Really want to get the cams working, though!
Please share other issues. There has to be something else horribly broken I haven't noticed.
Usual "may make zombies run out of your tablet" warning applies to this test software.
Enjoy!

[EXPLOIT][HOW-TO] BypassLKM: bypass module signature verification on TW 4.3

I got this idea after reading about CVE-2013-6282 and seeing the source for it.
As we all know, anyone with MF3+ bootloaders on ATT/VZW cannot load custom kernels/recoveries. Hashcode saved the day with Safestrap, which allowed users to run custom ROMs using stock, signed boot.imgs (initramfs/kernel). Unfortunately booting a custom kernel is still not possible due to BL restrictions.
With this latest root exploit, it is possible to overwrite kernel memory and thus remove some of the restrictions of the stock kernel. Most important is the ability to insert kernel modules not signed by Samsung, specifically kexec. This module can allow one to load any custom kernel regardless of BL restrictions. Before you ask, I have never compiled nor worked with kexec!
I'm going to go over the process just for completeness, you can skip this section if you want. It's mostly for devs:
With 4.3, when you insert one of the included modules (ie, /system/lib/modules), you will see the following in dmesg:
Code:
<4>[ 2003.009063] TIMA: lkmauth--launch the tzapp to check kernel module; module len is 3224
<4>[ 2003.009124] TIMA: lkmauth -- hdr before kreq is : e3003000
<4>[ 2003.009155] TIMA: lkmauth--send cmd (tima_lkm) cmdlen(304:320), rsplen(264:320) id 0x00050000, req (0xE511C000), rsp(0xE511C140), module_start_addr(0xE3003000) module_len 3224
<4>[ 2003.012237] TIMA: lkmauth--verification succeeded.
Though I'm not intimately familiar with the workings of lkmauth, it's obvious it's querying the trustzone (TZ) to verify the module. If we now change one insignificant byte in the module, you get:
Code:
<4>[ 2301.298980] TIMA: lkmauth--launch the tzapp to check kernel module; module len is 3224
<4>[ 2301.299011] TIMA: lkmauth -- hdr before kreq is : e300c000
<4>[ 2301.299041] TIMA: lkmauth--send cmd (tima_lkm) cmdlen(304:320), rsplen(264:320) id 0x00050000, req (0xE511C000), rsp(0xE511C140), module_start_addr(0xE300C000) module_len 3224
<3>[ 2301.301391] TIMA: lkmauth--verification failed -1
<4>[ 2301.301544] TIMA: MSG=lkm_modified; result (TIMA_RESULT=MSG=lkm_modified;)
We can use these messages to narrow down the code in the kernel. I'm using ATT MK2 as the example here:
kernel/module.c
Code:
/* parse result */
if (krsp->ret == 0) {
pr_warn("TIMA: lkmauth--[B]verification succeeded[/B].\n");
ret = 0; /* ret should already be 0 before the assignment. */
} else {
pr_err("TIMA: lkmauth--[B]verification failed[/B] %d\n", krsp->ret);
ret = -1;
....
If we unpack boot.img, then decompress the zImage, we can find this code in the binary. Fire up IDA and set the base address to 0xC0008000. You should be able to resolve the above string reference to:
Code:
ROM:C00B9C20 44 11 98 E5 LDR R1, [R8,#0x144]
ROM:C00B9C24 00 00 51 E3 CMP R1, #0
[B][COLOR="Red"]ROM:C00B9C28 02 00 00 1A BNE loc_C00B9C38[/COLOR][/B]
ROM:C00B9C2C 54 01 9F E5 LDR R0, =a4TimaLkmauthVe ; "<4>TIMA: lkmauth--verification succeede"...
ROM:C00B9C30 CA 57 1D EB BL sub_C080FB60
ROM:C00B9C34 3C 00 00 EA B loc_C00B9D2C
That BNE is the target for our patch. So bypasslkm will basically overwrite that test with a NOP instruction thus forcing the authentication to succeed.
I tested inserting a modified stock module and one I compiled. Btw, if you wanna use the modules from the kernel source tree, be sure to add
-fno-pic to CFLAGS_MODULE in the Makefile.
-------------------------------------------------------------------------------------------------------------
Usage:
bypasslkm is run alone, and patches the kernel in memory. It does NOT make any changes to the filesystem, and a reboot will require re-executing the patch. Please note the patch will remain in memory until you run 'bypasslkm -r' OR reboot. THIS CAN LEAVE YOUR OS IN A VULNERABLE STATE TO MALWARE. Ideally, you would run the patch, insert your module, then run the patch with -r.
Typical usage:
adb push bypasslkm /data/local/tmp
cd /data/local/tmp
chmod 755 bypasslkm
./bypasslkm
insmod <modulename.ko>
./bypasslkm -r
Supported stock kernels: ATT MK2, VZW MK2, VZW MJ7
CREDITS
fi01 - awesome source for the CVE!
CUBE - getroot source!
djrbliss - thanks for the makefile =P
DOWNLOAD:
Get the latest from my git: https://github.com/jeboo/bypasslkm

Reserved!

Very nice work. Wish I had a MF3 device so I could try it.

Thank you @jeboo. I'll see what I can do with this
Sent from my XT926 using Tapatalk

Nice job man!
Sent from my SM-N900V using Tapatalk

Hashcode said:
Thank you @jeboo. I'll see what I can do with this
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
it will help to crack the bootloader note 3?

This also works on the I545 with MI1 kernel...
This is directed at @Hashcode and @jeboo:
Guys, I just tried this on my I545 running the MI1 kernel, and it works. I am running Hyperdrive RLS 10.2 with the ATT compatibility pack (using AT&T service) -- but as you know, I am still stuck on the stock Verizon MI1 kernel. You should know that I flashed Hyperdrive over the stock ROM -- that's the only way (at the time) I could get it onto AT&T service here in the US.
My immediate question is how will this allow me to completely replace the stock kernel with something like the Infamous 4.6 OC kernel? I am just getting into this phase of development, so I am not as up on this as you guys are. I know every time I flash the Infamous kernel, the flash in SS seems to work -- but the phone always reboots to the stock 3.0.4 verizon kernel.
Of course, I had another thought, too -- I wonder if it is possible to use this to allow us to insert a module that does something similar to the Motorola Trust Zone unlock? Just another item for your consideration...
Here is a screen capture of me running bypasslkm:
=============================================
130|[email protected]:/data/local/tmp # ./bypasslkm
BypassLKM patch by Jeboo
usage: -r will restore kernel to original
Big thanks to fi01 & CUBE for their awesome CVE-2013-6282 exploit source!
ro.build.product=jflteatt
ro.build.displayid=JDQ39.I545VRUAME7
Patching kernel @ 0xC00B9C28: unsigned modules can now be inserted.
Done.
[email protected]:/data/local/tmp # ./bypasslkm -r
BypassLKM patch by Jeboo
usage: -r will restore kernel to original
Big thanks to fi01 & CUBE for their awesome CVE-2013-6282 exploit source!
ro.build.product=jflteatt
ro.build.displayid=JDQ39.I545VRUAME7
Patching kernel @ 0xC00B9C28: restoring original value.
Done.
[email protected]:/data/local/tmp #

I have an AMDL S4 so I'm already running AOSP ROM's, so I've never really paid attention to the problems which the newer S4's face.
Does the OP have a patch that allows the newer S4's to run AOSP now also?
Sorry if it's a stupid question.

Not quite yet...
CZ Eddie said:
I have an AMDL S4 so I'm already running AOSP ROM's, so I've never really paid attention to the problems which the newer S4's face.
Does the OP have a patch that allows the newer S4's to run AOSP now also?
Sorry if it's a stupid question.
Click to expand...
Click to collapse
Not quite yet -- but this is looking extremely promising!!

CZ Eddie said:
I have an AMDL S4 so I'm already running AOSP ROM's, so I've never really paid attention to the problems which the newer S4's face.
Does the OP have a patch that allows the newer S4's to run AOSP now also?
Sorry if it's a stupid question.
Click to expand...
Click to collapse
OP has an exploit that lets us load unsigned kernel modules. This means we can try to load up a kexec module, which would then load in a kernel over the stock one. So possibly, if it can be implemented.
budding_developer said:
This is directed at @Hashcode and @jeboo:
Guys, I just tried this on my I545 running the MI1 kernel, and it works. I am running Hyperdrive RLS 10.2 with the ATT compatibility pack (using AT&T service) -- but as you know, I am still stuck on the stock Verizon MI1 kernel. You should know that I flashed Hyperdrive over the stock ROM -- that's the only way (at the time) I could get it onto AT&T service here in the US.
My immediate question is how will this allow me to completely replace the stock kernel with something like the Infamous 4.6 OC kernel? I am just getting into this phase of development, so I am not as up on this as you guys are. I know every time I flash the Infamous kernel, the flash in SS seems to work -- but the phone always reboots to the stock 3.0.4 verizon kernel.
Of course, I had another thought, too -- I wonder if it is possible to use this to allow us to insert a module that does something similar to the Motorola Trust Zone unlock? Just another item for your consideration...
Click to expand...
Click to collapse
SS does not actually flash kernels, which is why it reboots to stock. The way this will allow you to run a different kernel is by loading in an unsigned kexec module and loading the new kernel over the stock one using that module. As for the Trust Zone unlock, someone with more real dev knowledge than me will have to look into that.

budding_developer said:
This is directed at @Hashcode and @jeboo:
Guys, I just tried this on my I545 running the MI1 kernel, and it works. I am running Hyperdrive RLS 10.2 with the ATT compatibility pack (using AT&T service) -- but as you know, I am still stuck on the stock Verizon MI1 kernel. You should know that I flashed Hyperdrive over the stock ROM -- that's the only way (at the time) I could get it onto AT&T service here in the US.
My immediate question is how will this allow me to completely replace the stock kernel with something like the Infamous 4.6 OC kernel? I am just getting into this phase of development, so I am not as up on this as you guys are. I know every time I flash the Infamous kernel, the flash in SS seems to work -- but the phone always reboots to the stock 3.0.4 verizon kernel.
Of course, I had another thought, too -- I wonder if it is possible to use this to allow us to insert a module that does something similar to the Motorola Trust Zone unlock? Just another item for your consideration...
Click to expand...
Click to collapse
Careful running this on unsupported kernels..I didn't add any sanity checking.

jeboo said:
Careful running this on unsupported kernels..I didn't add any sanity checking.
Click to expand...
Click to collapse
Didn't figure you did at this early stage... I am well equipped with everything I need to restore (short of JTAG, of course)... thanks for the warning, though!

I know it's early but are there any Modules handy for testing
SAFESTRAPPED ATT MK2 I337 S4

jball said:
I know it's early but are there any Modules handy for testing
SAFESTRAPPED ATT MK2 I337 S4
Click to expand...
Click to collapse
Too early, give it a week or so.. it's a long process being that no one is doing it full time...
Then again it's Christmas time, so maybe a few weeks..

tommydrum said:
Too early, give it a week or so.. it's a long process being that no one is doing it full time...
Then again it's Christmas time, so maybe a few weeks..
Click to expand...
Click to collapse
I've done some reading on it and trust me I do know it's not an easy thing for you and me.i don't put in development hours as I'm not a developer.i just want to Contribute anything I can even if it's just my phone.if you asked my wife I live and breath XDA .Thank you all for the Hard work your doing an awesome job
SAFESTRAPPED ATT MK2 I337 S4

jball said:
I've done some reading on it and trust me I do know it's not an easy thing for you and me.i don't put in development hours as I'm not a developer.i just want to Contribute anything I can even if it's just my phone.if you asked my wife I live and breath XDA .Thank you all for the Hard work your doing an awesome job
SAFESTRAPPED ATT MK2 I337 S4
Click to expand...
Click to collapse
I'd be willing to contribute my phone too .. even more since there's work around to odin bricked phone back on mk2

tommydrum said:
I'd be willing to contribute my phone too .. even more since there's work around to odin bricked phone back on mk2
Click to expand...
Click to collapse
What work around are you refering too? I thought there was no way to odin to MK2.
Sent from my GT-I9505 using XDA Premium 4 mobile app

cerobles1 said:
What work around are you refering too? I thought there was no way to odin to MK2.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Let's not clutter this thread.Look it up please

i don't mean to be a noob but will this work on mf3?

Ask in another thread please..and we don't know, but there's a good chance yes..
Again..please only developers post on this thread!! Keep it clean!!

[Preview] CyanogenMod 12.1 [Unofficial]

Hello! I haven't posted much here in the Nitro forums, but I got my p930 a couple years ago.
After loaning it out for a bit, I recently got it back, and decided to get Lollipop running on it (jumping straight to 5.1) :victory:
I've had experience porting newer versions of Android with another device (HTC Aria), but I can't say I'm extremely good at it.
I have most stuff working, but I might not be able to get everything working on my own.
Also I'm not very good at making a thread look good, so please excuse everything below being hard to read
It is based on miroslav's open source device trees and 3.4 kernel from github.com/NitroKK, but with the extra stuff removed to make it more like "stock" CM.
Bugs & things that currently don't work are:
- Camera
- Phone radio
- GPS
- Bluetooth is a bit sketchy
- MHL (aka HDMI out)
- SELinux enforcing mode
- Screen does not turn on sometimes - this is really hard to reproduce, so I'm not completely sure why... It doesn't happen too often though
- Probably more
I am releasing this as a "preview" because of the camera, phone, and GPS being broken. Once those are fixed, the preview tag will be dropped
GPS should be pretty easy to fix, but might need the phone stuff working first. Camera and phone I'm not really sure where to go next..
Notes:
LG SU640 support: miroslav's compatibility patch linked in his CM11 thread should work fine.
If it doesn't, let me know (with a log if possible) and I'll see what I can do...
If your recovery asks to fix or install root when rebooting, just hit no - it's outdated and doesn't know the correct place to look for root anymore.
If you need to use root, you'll need to enable development settings by repeatedly tapping Build number in About phone, then turn on Root access in Developer options.
I recommend changing the launcher's app drawer mode to paged, as the effect when scrolling fast on the vertical drawer runs very slow on this device (and not great on newer devices either).
There is only about 90MB free on the /system partition, so Google Apps packages will have to be somewhat light-weight to fit in that.
I have linked to the one I use below, but if you use your own, make sure it's smaller than 90MB after extracting, not just as a zip.
Because of the quality improvements on Lollipop's UI, the performance is a bit worse than KitKat.
A flag can be enabled to give a much better framerate and general responsiveness etc, but at the cost of stability.
Just add this line to build.prop then reboot:
Code:
persist.hwc.mdpcomp.enable=true
It runs much better, but causes really bad screen glitches in some places (and maybe other stuff like the screen not turning on more often).
In the future I would like to fix it, but for now I'm leaving it off by default.
If anyone would like to help fix things, full source on everything I have changed is at the following GitHub organization:
https://github.com/NitroCM
Pull requests, Issues, whatever are welcome, and I can add people to it upon request (as long as I can trust you )
On to the downloads! Pick whichever mirror works best for you.
20150809 - 9bc4906aaa21caa36217d9186bb2bb36
Google Drive: https://goo.gl/sMHQYz
MediaFire: http://www.mediafire.com/download/bcjbs0jpnj1jrpd/cm-12.1-20150809-UNOFFICIAL-p930.zip
Mega: https://goo.gl/e4Q16q
xda dev-db: http://forum.xda-developers.com/devdb/project/dl/?id=13902
Google Apps: https://goo.gl/YxlfU0 or https://goo.gl/Mw9uPt
XDA:DevDB Information
CyanogenMod 12.1 (unofficial), ROM for the LG Nitro HD
Contributors
WinSuk, miroslav_mm
Source Code: https://github.com/NitroCM
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-08-10
Last Updated 2015-08-16

Holy sweet buttery jesus. you did it.

Thanks for doing this. Finally some some extra life to this device. Unfortunately I get boot-loops when flashing this ROM, but that seems associate with partition sizes on this devices and miroslav's CM11 kernel (mine are the smaller size). I probably have to factory flash the right ICS kdz to fix it. Not sure yet what to do to get the right sizes, but I still appreciate your effort so at least there is a way forward. Keep up the good work!

miji2 said:
Thanks for doing this. Finally some some extra life to this device. Unfortunately I get boot-loops when flashing this ROM, but that seems associate with partition sizes on this devices and miroslav's CM11 kernel (mine are the smaller size). I probably have to factory flash the right ICS kdz to fix it. Not sure yet what to do to get the right sizes, but I still appreciate your effort so at least there is a way forward. Keep up the good work!
Click to expand...
Click to collapse
Hmm... I'm not completely sure which bootloader I have installed, but I think it's the gingerbread one (v10).
Does the boot animation show up? (Cid with a pulsing circle behind him)
If so, the system partition is definitely mounting correctly, and you probably just need to wait longer (the first boot takes a long time).
If not (it's stuck on the LG logo or keeps rebooting to the LG logo), does miro's CM11 ROM work for you? (if you have tried it)

WinSuk said:
Hmm... I'm not completely sure which bootloader I have installed, but I think it's the gingerbread one (v10).
Does the boot animation show up? (Cid with a pulsing circle behind him)
If so, the system partition is definitely mounting correctly, and you probably just need to wait longer (the first boot takes a long time).
If not (it's stuck on the LG logo or keeps rebooting to the LG logo), does miro's CM11 ROM work for you? (if you have tried it)
Click to expand...
Click to collapse
So the device would only show the LG logo then reboot, vibrate, and repeat. It behaved same with miroslav's CM11 but it was just fine flashing and running stock CM11.
my partition sizes were:
Code:
Filesystem Size Used Free Blksize
/dev 371.2M 136.0K 371.1M 4096
/sys/fs/cgroup 371.2M 12.0K 371.2M 4096
/mnt/asec 371.2M 0.0K 371.2M 4096
/mnt/obb 371.2M 0.0K 371.2M 4096
/mnt/fuse 371.2M 0.0K 371.2M 4096
/system 503.9M 352.6M 151.4M 4096
/cache 315.0M 5.2M 309.7M 4096
/data 2.2G 113.9M 2.0G 4096
/persist 7.9M 4.1M 3.8M 4096
/mpt 15.5M 1.1M 14.4M 1024
/tombstones 72.0M 4.1M 67.9M 4096
/firmware 64.0M 22.8M 41.2M 16384
/modem 199.8M 27.3M 172.5M 4096
Here's what I did to fix:
a) debrick with ICS kdz http://forum.xda-developers.com/showthread.php?t=2044645
b) rooted with http://forum.xda-developers.com/showthread.php?t=1886460
b) unlock bootloader with http://forum.xda-developers.com/showthread.php?t=2598278
c) flash recovery (TWRP) then this ROM
and now my partition sizes are:
Code:
Filesystem Size Used Free Blksize
/dev 383.8M 36.0K 383.7M 4096
/sys/fs/cgroup 383.8M 12.0K 383.8M 4096
/mnt/asec 383.8M 0.0K 383.8M 4096
/mnt/obb 383.8M 0.0K 383.8M 4096
/system 495.5M 402.6M 92.9M 4096
/cache 134.0M 4.3M 129.7M 4096
/data 2.2G 245.1M 1.9G 4096
/persist 7.9M 4.6M 3.3M 4096
/mpt 15.8M 1.4M 14.4M 1024
/tombstones 71.9M 4.0M 67.9M 4096
/firmware 64.0M 22.8M 41.2M 16384
/modem 199.8M 27.7M 172.0M 4096
And now your ROM as well as miroslav's CM11 install without a hitch and work great. Lots of work, but well worth it. Thanks for giving me a reason to go through all that

miji2 said:
and now my partition sizes are:
Code:
Filesystem Size Used Free Blksize
/dev 383.8M 36.0K 383.7M 4096
/sys/fs/cgroup 383.8M 12.0K 383.8M 4096
/mnt/asec 383.8M 0.0K 383.8M 4096
/mnt/obb 383.8M 0.0K 383.8M 4096
/system 495.5M 402.6M 92.9M 4096
/cache 134.0M 4.3M 129.7M 4096
/data 2.2G 245.1M 1.9G 4096
/persist 7.9M 4.6M 3.3M 4096
/mpt 15.8M 1.4M 14.4M 1024
/tombstones 71.9M 4.0M 67.9M 4096
/firmware 64.0M 22.8M 41.2M 16384
/modem 199.8M 27.7M 172.0M 4096
And now your ROM as well as miroslav's CM11 install without a hitch and work great. Lots of work, but well worth it. Thanks for giving me a reason to go through all that
Click to expand...
Click to collapse
I see, cool
I don't remember at all what I did, but my partition sizes are indeed the same as what you have now.

sweet..
any updates yet ? am dying to try out new updates :sly:

Loo Ney said:
sweet..
any updates yet ? am dying to try out new updates :sly:
Click to expand...
Click to collapse
Not really The radio is really stubborn.
Bluetooth is better, but still crashes sometimes. Camera is closer to working, but still doesn't.
I haven't been working on it until just a couple weeks ago, so maybe I'll figure something out soon (maybe )

WinSuk said:
Not really The radio is really stubborn.
Bluetooth is better, but still crashes sometimes. Camera is closer to working, but still doesn't.
I haven't been working on it until just a couple weeks ago, so maybe I'll figure something out soon (maybe )
Click to expand...
Click to collapse
GREAT bro..keep up the good work, i will be waiting for an update :good::good:

Update?

thinhx2 said:
Update?
Click to expand...
Click to collapse
I wasn't able to figure anything out except for bluetooth working slightly better as stated in a previous post - anything further would require someone who better knows how things work.
Also, my p930 is currently being used daily by a family member, so I can't try any changes out on it (I wasn't working on it at all before that though).
This will probably forever be a "hey look it boots and you can see stuff" demo

WinSuk said:
I wasn't able to figure anything out except for bluetooth working slightly better as stated in a previous post - anything further would require someone who better knows how things work.
Also, my p930 is currently being used daily by a family member, so I can't try any changes out on it (I wasn't working on it at all before that though).
This will probably forever be a "hey look it boots and you can see stuff" demo
Click to expand...
Click to collapse
Thank for work. And bro can make cm13 or aosp 6.0? My friend use this devicem he can test. Thank bro reply

Lets get Marshmallow running on this device
Maybe if we get Marshmallow on this device, things will be easier to be fixed.

YU5510A P3 Hardware Variant - Discuss

This is the yureka plus model ordered from snapdeal. Box mfg date is aug 2016. It comes with stock lollipop and VoLTE enabled out of the box.
Hardware sticker behind the battery says P3
Here is the partition size as per adb:
adb devices
adb shell
cat /proc/partitions
[email protected]:/ # cat /proc/partitions
major minor #blocks name
0 15392768 mmcblk0
1 1 mmcblk0p1
2 8 mmcblk0p2
3 512 mmcblk0p3
4 512 mmcblk0p4
5 512 mmcblk0p5
6 512 mmcblk0p6
7 512 mmcblk0p7
8 512 mmcblk0p8
9 512 mmcblk0p9
10 512 mmcblk0p10
11 1024 mmcblk0p11
12 20480 mmcblk0p12
13 1536 mmcblk0p13
14 1536 mmcblk0p14
15 262144 mmcblk0p15
16 32768 mmcblk0p16
17 1024 mmcblk0p17
18 512 mmcblk0p18
19 512 mmcblk0p19
20 131072 mmcblk0p20
21 1024 mmcblk0p21
22 32 mmcblk0p22
23 1536 mmcblk0p23
24 16 mmcblk0p24
25 4096 mmcblk0p25
26 4096 mmcblk0p26
27 32768 mmcblk0p27
28 32768 mmcblk0p28
29 2621440 mmcblk0p29
30 65536 mmcblk0p30
31 12148719 mmcblk0p31
32 4096 mmcblk0rpmb
Today I went to the service centre to have them change the OS to cyanogenmod but after waiting for two hours, the guy came out of his cabin and showed me the P3 sticker and said it was non compatible with cyanogenmod. He said this device didn't have fastboot mode and instead something else was present in the volume up config.
Around half of the people in this service centre had brought their yureka plus to the store because it was getting too hot and battery wasn't lasting through the day. One particular guy brought his yureka plus with burned display. According to him, the camera app and flash had started up automatically while it was in his pocket turning it hot and by the time he realized something warm in his pocket, parts of display pixels had already gone dead black.
Those yureka users who had come for battery issues were sent back saying it was a faulty battery issue - change battery. Some users had bought it from flipkart and were unable to replace it. I bought mine from snapdeal last week and as I was filing a return request on the website, I found that it was only eligible for a "replacement" policy.
About a month or two ago, I had wondered why so many people were selling their 2-6 month old yureka plus on olx and now I know the reason. The YU company has put a faulty device on sale and too many people have ended up buying it after watching some youtube review videos(although sharmaji technical had clearly instructed "just don't buy yureka plus" which I ignored) when they should have read the forums for genuine issues.
The new P3 device is pending:
1) rooting
(achieved !! see next post)
2) replacing kernel to solve battery and heating issue
(Partly achieved using root and bypassing kernel through apps)
3) custom rom to a) fix lagging issues and b) many features which are considered basic on 2016 absent in this stock rom
Kindly post more info on P3 in this thread to help us understand the issue.

UPDATE:
I have managed to root this device. I did this using the PC version of kingoroot. Kinguser did not work on my phone as you guys suggested and I also tried different versions of kinguser but failed.
Steps to root P3:
1) Download kingoroot PC software from their official site and complete installation
2) On phone > Enable developer mode > Turn on USB debugging
3) Start kingoroot on PC > Connect phone to pc
4) Disable your anti-virus for 15 mins (this is very important; else you won't achieve root)
5) Follow kingoroot instructions and click next when asked > it will download some very nasty exploit scripts which anti-virus don't like.
6) It will finally show root achieved
Now, on phone remove both kingoroot apps(kingoroot and its version of superuser). And install superSU from play store.
Now, download link2sd app from play store and delete many useless Google apps from /system partition.
STEPS TO CONTROL BATTERY DRAIN AND HEATING ISSUES:
This phone comes with a faulty stock kernel which controls the CPU speed. After gaining root, download kernel adiutor from play store. The stock kernel has the minimum frequency set at 960mhz by default. So it runs above 960mhz even at idle mode.
Hence, the reason for drain and hot phone.
Using kernel adiutor, change minimum frequency to 200mhz for both big and small set of 4 CPUs. In the max side, set it to 800mhz in both sets - yes, we are under clocking this chip as 615 chip gets too hot if run constantly above 1ghz. Set the governor to ondemand option. And enable on boot option so that it can set these settings every time phone boots. Also hide notifications if you want.
Now, download DS battery saver from play store. The stock kernel is stupid so it won't send your phone to deep sleep and kernel adiutor won't either. But DS will send phone to deep sleep as soon as you hit sleep button.

hi if u want Yureka full working with p1 version software .in exchange of Yureka plus p3 then u can contact me .[