Page 1 of 14 12311 ... LastLast
Results 1 to 10 of 134
Like Tree2Likes

Thread: [L-ROM]Tenchi's CyanogenMod 12 ROM Lollipop Android 5.0 for ADAM [WIP]

  1. #1
    Resident
    Join Date
    May 2011
    Posts
    803
    Thanks
    15
    Thanked 531 Times in 203 Posts

    [L-ROM]Tenchi's CyanogenMod 12.1 ROM Lollipop Android 5.1.1 for ADAM[WIP][2015-07-07]

    This is a build of the latest Android CyanogenMod 12.1 ROM Lollipop 5.1.1 ROM. This includes USB fixes from ri9000 and NVOMX, screen capture, and HDMI patches from timduru. Not too many changes yet, but thought the button customization, close all apps, network adb features were most useful.

    For more info go here: CyanogenMod | Android Community Operating System

    For now it is a nvflash release as there are some issues with building zip file.

    Currently overclocked to 1.5GHz, to edit PixelQi settings, clock speed, sleep mode and other settings edit /system/etc/adam_preboot.sh

    Install Instructions for Windows NVFLASH package

    1. Download from links below the ROM, any updated boot.img if needed, no google apps download available yet.
    2. Extract nvflash ROM zip file.
    3. To increase system size if installing full Google Apps package just rename the file android_fastboot_full.cfg to android_fastboot_full-650MB-system.cfg and
    rename android_fastboot_full-800MB-system.cfg to android_fastboot_full.cfg (cm12.1 has default 924mb system so no need to rename anything).
    4. Connect Adam via usb to computer.
    5. Set Adam to nvflash recovery mode by holding Volume - and power on.
    6. Goto driver manager in Windows and you should see some APX device, and right click on update the driver for this device.
    7. Set Browse driver to Drivers/Driver32-bit/ and install.
    8. run "fbs.bat" to just install ROM and wait till it finished flashing or run "download.bat" to completely format your Adam internal storage and install complete ROM with ClockWorkMod Recovery and a 650 Meg system partition by default.
    9. Reboot Adam while holding Volume + to go into ClockWorkMod recovery.
    10. Wipe data/factory reset. (This will wipe all data from your internal sdcard and the cache).
    11. Install Google apps.zip and SuperSU to root if needed.
    12. Skip to step 16 if you don't need to flash an updated boot.img
    13. Reboot while holding volume - to go into nvflash recovery again.
    14. Copy downloaded boot.img into your nvflash directory or extract boot.img from ROM.zip (if no updated boot image is available).
    15. Run "flashboot.bat boot.img" in command line.
    16. Restart after it is finished flashing and you will boot into your new Kitkat ROM.
    17. The only way I could get any android 5.1 rom booting without any surfaceflinger crashes was to use "adb pull /system/lib/egl egl" then "adb push egl /system/lib/egl" then it will boot everytime thereafter, must be an issue with built img file or something.

    How to install ROM and Google Apps zips from ClockworkMod

    1. Download the zip and ADB and USB drivers ZIP in download section.
    2. Follow "How to install ADB driver" instructions below.
    3. Make sure you have an alternate keyboard pre-installed before installing Google Apps otherwise you will get force closes of AOSP keyboard all the time.
    4. Power on Adam in recovery mode by holding Volume + and toggling power switch.
    5. On PC in command prompt type 'cd "adb directory"'
    6. If you want to install to micro sdcard refer to link for setup details: Booting from sdcard much faster! and Type 'adb shell setprop sdboot 1'.
    7. Type 'adb shell mount -a' ignore the errors (try again if you don't see any error message).
    8. If installing new ROM type adb shell rm -rf /system/* to remove previous ROM files and do Wipe Data/Factory Reset.
    9. Type 'adb push file.zip /external_sd/' (should see files being transferred to microsd).
    10. On Adam use volume keys or middle 2 soft touch keys to navigate up and down to "Install zip".
    11. Press top soft key button to enter selection.
    12. Navigate and enter to /storage/external_sd.
    13. Navigate and enter to your file.zip file.
    14. Navigate and enter to Yes to install, should be no errors.
    15. Reboot your Adam once the transfer is complete.

    How to install ADB driver

    1. Extract the ADB zip with archive utility like WinZip or WinRAR.
    2. Run UniversalAdbDriverSetup6.msi.
    3. Connect Adam to computer via USB.
    4. Right click on "My Computer" in File Explorer.
    5. Click on "Device Manager".
    6. Should see "Notion" with exclamation mark.
    7. Right click on "Notion" and select "Update Driver Software".
    8. Select "Browse my computer for driver software".
    9. Select "Let me pick from a list of device drivers on my computer".
    10. Select "Android Device" and press Next.
    11. Select "Asus Transformer ADB Interface" and press Next.
    12. Ignore Update Driver Warning and press Yes.
    13. Should now see Android Device\Asus Transformer ADB Interface in devices.

    How to obtain adam logs to report problems

    1. Follow instructions above on How to install ADB driver.
    2. Connect Adam to computer via USB.
    3. Power on Adam with ROM you are having problems with to capture log and do what you did you get the problem.
    4. Launch Windows command prompt and type cd "path to platform-tools".
    5. Type "adb wait-for-device pull /data/aplog".
    6. If you get remote object '/data/aplog/ does not exist' goto step 8.
    7. Type "adb pull /data/dmsg".
    8. Goto step 13 if step 5 and 7 were successful.
    9. Type "adb shell".
    10. Type "cd /data".
    11. Type "logcat -d > aplog".
    12. Type "dmesg > dmsg".
    13. Type "cat /proc/kmsg > kmsg &".
    14. Press CTRL-C to exit shell.
    15. Type "adb pull /data/aplog".
    16. Type "adb pull /data/dmsg".
    17. Type "adb pull /data/kmsg".
    18. You should now have 3 files in your platform-tools directory, aplog, dmsg, and kmsg.
    19. Launch Web browser and goto Pastebin.com - #1 paste tool since 2002!.
    20. Open aplog in wordpad and copy and paste all text to web page and submit.
    21. Create a new message in this thread and paste the URL from pastebin.com of your newly submitted log.
    22. Repeat 19-20 for dmsg and kmsg.

    Download links:

    download 2015-04-03 boot img (better waking)

    CyanogenMod 12.1 ROM Lollipop for ADAM:
    5.1.1:
    download 2015-07-07 CWM ZIP (with micro sdcard install option)

    download 2015-04-25 NVFLASH

    5.1:
    download 2015-04-01 NVFLASH

    CyanogenMod 12 ROM Lollipop for ADAM:

    Disable button bar patch:

    download

    5.0.2:
    download 2015-01-28 NVFLASH

    download 2014-12-31 NVFLASH

    5.0.1:
    download 2014-12-08 NVFLASH

    SuperSU for root access:
    download

    ClockworkMod 6.0.4.7 Recovery with nvflash (run "flashrecovery.bat recovery.img" in command line):
    download CWM with battery indicator from Borkata and working USB thanks to ri9000

    ADB with USB drivers (usb_driver folder contains older version which will work with ClockworkMod although you need to allow unsigned drivers to install) download

    Open Google Apps download (mini is largest package that can be installed)

    Source download links:

    CyanogenMod 12.x ROM: download

    Device tree and kernel source: download

    Vendor tree: download

    Tested and working:

    [2015-07-07]
    -CWM ZIP with micro sdcard install option
    -Camera app should be working although picture may be inverted

    [2015-04-01]
    -SOD fix and HW video acceleration should work now in Android 5.1

    [2015-01-28]
    -USB Audio working
    -cpu overclock disabled because of SOD
    -SOD fix, wake with Back button

    [2014-12-31]
    -Android 5.0.2
    -hwcomposer hdmi fix
    -PowerHAL for cpu boost on touch and 1GHz battery saving mode
    -mic fix
    -cpu clock reduced to 1.5GHz and voltages decreased for better battery life
    -camera shouldn't prevent sleeping now
    -wake using volume buttons in addition to back button
    -vpn working now

    [2014-12-08]
    -HW Accelerated video
    -Screen capture
    -lp2 mode sleep disabled by default now to allow for stable usb connection can be re-enabled in /system/etc/adam_preboot.sh if you choose better sleep power usage over usb and comment out keepawake line (only works for some adams)
    -Pixel Qi toggle app
    -Camera app partially working in picture mode (although still can't snap a picture, other third party camera apps may work)
    -Wifi
    -Bluetooth A2DP
    -HDMI (if you get alot of freezing, you can disable by renaming /system/lib/hw/hwcomposer.tegra.so to hwcomposer.tegra.so.x
    -GPS should be working

    Not working:
    -sometimes touch screen doesn't respond, just slide power switch and then press side back button
    -sometimes shutdown/reboot/deep sleep may hang
    -Compass
    -3g

    Credits
    Borkata for making such an excellent kernel and CM ports and help with problems

    ri9000 for usb fixes

    timduru for NVOMX, screen capture fixes and HDMI fix

    CyanogenMod ROM developers for providing Android ROM
    Last edited by tenchi; 07-08-2015 at 01:11 PM. Reason: ROM Update, Open Google Apps
    tartutic07 likes this.

  2. The Following 11 Users Say Thank You to tenchi For This Useful Post:

    abufrejoval (02-14-2015), fantaze (01-08-2015), gib72 (12-16-2014), katletz (04-28-2015), mikus (12-09-2014), Prema (04-11-2015), ri9000 (12-09-2014), tartutic07 (12-10-2014), vt220 (03-13-2015), ZenOgeek (01-03-2015), ZilcH (12-14-2014)

  3. #2
    Regular
    Join Date
    Jul 2013
    Location
    Australia
    Posts
    398
    Thanks
    110
    Thanked 25 Times in 19 Posts
    rom installs nicely..
    ptp,adb access is great but mtp,adb is not working for some reason?

  4. #3
    Member
    Join Date
    Aug 2011
    Posts
    78
    Thanks
    16
    Thanked 4 Times in 4 Posts

    Unhappy stuck in APX

    Although probably not related to this ROM I'm posting here as it happened while flashing.
    My Adamis now stuck in APX mode it seems. Having it hooked up to my Win 8.1 x64 and after installing the provided driver i end up with this console log:

    Code:
    D:\nvflash>nvflash.exe --bct harmony_a02_12Mhz_H5PS1G8
    3EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct --setbct --bl bootloader.bin --c
    onfigfile android_fastboot_full.cfg --odmdata 0xbc0c0011 --create --go
    Nvflash started
    rcm version 0X20001
    System Information:
       chip name: t20
       chip id: 0x20 major: 1 minor: 3
       chip sku: 0x8
       chip uid: 0x171411c042a05097
       macrovision: disabled
       hdcp: enabled
       sbk burned: false
       dk burned: false
       boot device: nand
       operating mode: 3
       device config strap: 0
       device config fuse: 0
       sdram config strap: 0
    
    sending file: harmony_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-
    TP.bct
    - 4080/4080 bytes sent
    harmony_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct sent su
    ccessfully
    odm data: 0xbc0c0011
    downloading bootloader -- load address: 0x108000 entry point: 0x108000
    sending file: bootloader.bin
    | 941356/941356 bytes sent
    bootloader.bin sent successfully
    waiting for bootloader to initialize
    bootloader downloaded successfully
    setting device: 1 0
    creating partition: BCT
    creating partition: PT
    creating partition: EBT
    creating partition: NVC
    creating partition: MBT
    creating partition: MSC
    creating partition: SOS
    creating partition: LNX
    creating partition: APP
    creating partition: CAC
    Formatting partition 2 BCT please wait.. done!
    Formatting partition 3 PT please wait.. done!
    Formatting partition 4 EBT please wait.. done!
    Formatting partition 5 NVC please wait.. done!
    Formatting partition 6 MBT please wait.. done!
    Formatting partition 7 MSC please wait.. done!
    Formatting partition 8 SOS please wait.. done!
    Formatting partition 9 LNX please wait.. done!
    Formatting partition 10 APP please wait.. done!
    Formatting partition 11 CAC please wait.. done!
    done!
    sending file: bootloader.bin
    | 941356/941356 bytes sent
    bootloader.bin sent successfully
    sending file: microboot.bin
    \ 95888/95888 bytes sent
    microboot.bin sent successfully
    sending file: mbtdata.img
    - 1024/1024 bytes sent
    mbtdata.img sent successfully
    sending file: recovery.img
    | 3858432/3858432 bytes sent
    recovery.img sent successfully
    sending file: boot.img
    - 3182592/3182592 bytes sent
    boot.img sent successfully
    sending file: system.img
    / 3670016/129258624 bytes sentdata send failed NvError 0x120002
    command failure: create failed (bad data)
    
    Press enter to continue:
    I managed to get a few bytes further using an older KatKiss nvflash and the original Eden package but none managed to finish and the tablet won't do anything now. It used to work OK with the former CM11 on it

    Edit 1:
    Using another USB (3.0 this time) port finished with the Eden nvflash at least!

    Edit 2:
    Managed to succesfully nvflash this package now. Just to be sure first tried CM9 Beta AIO to resize partitions if needed somehow. Wiping caches in CWM recovery tells me it's unable to format /data and the log shows a warning about too many symbolic links there. boot animation is running for a couple of seconds now.
    Last edited by vendetta1987; 12-09-2014 at 02:37 PM. Reason: success?

  5. #4
    Regular
    Join Date
    Jul 2013
    Location
    Australia
    Posts
    398
    Thanks
    110
    Thanked 25 Times in 19 Posts
    looking at your original log : bad usb lead/port?, corrupt system.img?
    make sure you flash correct "cwm"

  6. #5
    Member
    Join Date
    Aug 2011
    Posts
    78
    Thanks
    16
    Thanked 4 Times in 4 Posts
    I flashed the linked CWM 6.0.4.7 of Borkata and yours before trying to wipe and factory reset. As mentioned it skips the /data partition because of too many symbolic links according to the log. The ROM keeps stuck in the boot animation even after 20+ min and wiping caches several times. Maybe ADB logs will help which i could get today evening. Just have to look up the commands around here.

  7. #6
    Regular
    Join Date
    Jul 2013
    Location
    Australia
    Posts
    398
    Thanks
    110
    Thanked 25 Times in 19 Posts
    instead of wiping/factory reset,
    in cwm, mounts & storage,
    format /data, format /cache, format /system,
    then install..

  8. #7
    Member
    Join Date
    Aug 2011
    Posts
    78
    Thanks
    16
    Thanked 4 Times in 4 Posts
    As said before, formating /data results in an error where the log is showing
    Formatting /data...
    E:format_volume: make_ext4fs failed on /dev/block/mmcblk0p2
    Error formatting /data!
    I: Skipping execution of extendedcommand, file not found...
    mtd: successfully wrote block at 0
    I: Set boot command ""
    mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Too many symbolic links encountered
    mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Too many symbolic links encountered
    Formatting /data...
    Need size of filesystem
    E:format_volume: make_ext4fs failed on /dev/block/mmcblk0p2
    Error formatting /data!
    mtd: successfully wrote block at 0
    I:Set boot command ""
    I:Can't partition non mmcblk device: /devices/platform/sdhci-tegra.3/mmc_host/mmc1
    also /data can't be mounted. the device is still stuck in the boot animation even after another nvflash. please have a look at the attached logs here.

    I already tried other CWM Recovery versions (6.0.4.7 + special partition version from KK + BorkataTenchiRi9000) with no avail.

    Edit 1:
    I managed to make it boot! Since the log output pointed to some kind of partition table problem i remembered CWM was able to repartition the SD card. I did so and set it to 7648MB for data. after some more nvflashing, partitioning and wiping the tablet now boots up. i immediately get a warning about low system disk space which occurs for 7648MB as well as 4096MB. also while updating/optimizing all apps during startup the ROM crashes to the boot animation frequently. so far it still continued after rebooting with the number of apps decreasing. after transfering the posted gapps however it already took several reboots without settling until now.

    Edit 2:
    the linked gapps won't work with my partition of 7,5GB at least. after some more reboots i formated /system again. the rom boots up, just the initial setup crashed repeatedly. is it possible to have at least a minimal gapps package (any?) installed with these partitions?
    another thing that happens with this ROM is CWM giving a warning on exit about superuser not working and asks if it shall fix it. this doesn't seem to have any effect as it pops up again next time.
    Last edited by vendetta1987; 12-10-2014 at 02:34 PM. Reason: progress

  9. #8
    Resident
    Join Date
    May 2011
    Posts
    803
    Thanks
    15
    Thanked 531 Times in 203 Posts
    Quote Originally Posted by vendetta1987 View Post
    Edit 2:
    the linked gapps won't work with my partition of 7,5GB at least. after some more reboots i formated /system again. the rom boots up, just the initial setup crashed repeatedly. is it possible to have at least a minimal gapps package (any?) installed with these partitions?
    another thing that happens with this ROM is CWM giving a warning on exit about superuser not working and asks if it shall fix it. this doesn't seem to have any effect as it pops up again next time.
    Any chance you can post /data/aplog for latest run and maybe I can fix? Also you can just delete app directories from /system/app/ for the ones you don't need.
    Last edited by tenchi; 12-10-2014 at 03:18 PM.

  10. #9
    Member
    Join Date
    Aug 2011
    Posts
    78
    Thanks
    16
    Thanked 4 Times in 4 Posts
    These logs were obtained after booting and crashing to the boot animation once, during "upgrading android app x/y". it's a fresh install without further gapps but just some settings changed.

    aplog
    dmsg
    kmsg

  11. #10
    Resident
    Join Date
    May 2011
    Posts
    803
    Thanks
    15
    Thanked 531 Times in 203 Posts
    Quote Originally Posted by vendetta1987 View Post
    These logs were obtained after booting and crashing to the boot animation once, during "upgrading android app x/y". it's a fresh install without further gapps but just some settings changed.

    aplog
    dmsg
    kmsg
    I am not sure what could be wrong, but what settings did you change? Maybe try formatting /data and /cache again.

Page 1 of 14 12311 ... LastLast

Remove Ads

Similar Threads

  1. Replies: 130
    Last Post: 12-19-2017, 07:59 AM
  2. Replies: 37
    Last Post: 07-04-2015, 12:04 PM
  3. Replies: 77
    Last Post: 02-06-2015, 07:14 PM
  4. Lollipop (ADAM)
    By ZenOgeek in forum Adam ROM Development
    Replies: 0
    Last Post: 11-09-2014, 08:37 AM
  5. Hdmi and Cyanogenmod 7.1 (android 2.3.5)
    By manuel100 in forum Folio ROM Development
    Replies: 5
    Last Post: 10-30-2011, 02:41 PM

Search tags for this page

android last kmsg in recovery

,
cant partition non mmcblk device flashimg rom
,
cyanogenmod 12 lollipop system.img rockchip 3126
,
cyanogenmod lollipop 5.0 expressi437 zip file
,
cyanogenmod lollipop 5.0 rom tablet
,
download caynogemode bootcm12
,
hdmi? on cyanogenmod 12.1??
,

s650 cyanogen mod

,
sim not loaded and not nv subscription
,
wip beta cyanogen mode 12 for i9301
Click on a term to search for related topics.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •