Post Reply

[ROM]★★[KitKat 4.4.2][CROMi-X 7.1 b2][11.4.1.29][Jan 25]★★

OP sbdags

Announcement from sbdags: CROMi-X 7.1 BETA Released!
22nd February 2015, 03:44 AM   |  #601  
HippoMan's Avatar
Senior Member
Thanks Meter: 117
 
548 posts
Join Date:Joined: May 2009
Quote:
Originally Posted by GrouchyPunisher

HippoMan,

Which kernel did you choose? I had this same exact problem a while back, and the only thing that fixed it was using the Modified stock kernel. (I can't remember if that's the default or not, but may want to try that if you didn't choose it already.)

Aha! That did the trick. I booted up successfully now. Thank you!

In all the previous attempts, I just used the kernel which was selected by default in Aroma. It was the second one, which I think is called the "enhanced" kernel, or something like that. This time, I followed your suggestion and selected the modified stock kernel, and the OS started without any problems.

I'd like to suggest that the second kernel no longer be selected by default in Aroma.

... and thanks to sdbags for all your patience and help.

Onward!
.


---------- Post added at 09:44 PM ---------- Previous post was at 09:16 PM ----------

By the way, I tried installing ADB+Recovery+Driver.zip, but it gave me an "installation aborted" message.
However, it maybe worked anyway, because I was then able to do an "adb pull /tmp/recovery.log" from when I was running in recovery.

Here are the contents of that log file after trying to flash ADB+Recovery+Driver.zip. Note the section in red near the end of the log listing ...

Code:
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Sun Feb 22 02:38:34 2015

can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (2560 x 1600)
CWM-based Recovery v6.0.5.1
recovery filesystem table
=========================
  0 /recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS 0
  1 /boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX 0
  2 /system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP 0
  3 /cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC 0
  4 /data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA 0
  5 /metadata emmc /dev/block/platform/sdhci-tegra.3/by-name/MDA 0
  6 /misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC 0
  7 /staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP 0
  8 /storage/MicroSD auto /devices/platform/sdhci-tegra.2/mmc_host/mmc1 0
  9 /storage/SD auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1.3 0
  10 /storage/USBdisk1a auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1.2 0
  11 /storage/USBdisk1b auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1:1.0 0
  12 /storage/USBdisk1c auto /devices/platform/tegra-xhci/usb2/2-1 0
  13 /storage/USBdisk1d auto /devices/platform/tegra-xhci/usb1/1-2/1-2.1 0
  14 /storage/USBdisk1e auto /devices/platform/tegra-xhci/usb1/1-2/1-2.2 0
  15 /storage/USBdisk1f auto /devices/platform/tegra-xhci/usb1/1-2/1-2.4 0
  16 /storage/USBdisk1g auto /devices/platform/tegra-xhci/usb1/1-2/1-2:1 0
  17 /storage/USBdisk1h auto /devices/platform/tegra-xhci/usb1/1-2/1-2.3/1-2.3:1.0 0
  18 /storage/USBdisk2 auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1.1 0
  19 /tmp ramdisk ramdisk 0

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 MicroSD /storage/MicroSD 1 -
I:110 0 SD /storage/SD 0 -
I:110 0 USBdisk1a /storage/USBdisk1a 0 -
I:110 0 USBdisk1b /storage/USBdisk1b 0 -
I:110 0 USBdisk1c /storage/USBdisk1c 0 -
I:110 0 USBdisk1d /storage/USBdisk1d 0 -
I:110 0 USBdisk1e /storage/USBdisk1e 0 -
I:110 0 USBdisk1f /storage/USBdisk1f 0 -
I:110 0 USBdisk1g /storage/USBdisk1g 0 -
I:110 0 USBdisk1h /storage/USBdisk1h 0 -
I:110 0 USBdisk2 /storage/USBdisk2 0 -
I:200 0 Volumes listed.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ap.interface=wlan1
ro.cm.device=tf701t
ro.cm.display.version=11-20150105-UNOFFICIAL-tf701t
ro.cm.version=11-20150105-UNOFFICIAL-tf701t
ro.cm.releasetype=UNOFFICIAL
ro.sf.override_null_lcd_density=1
ro.com.google.clientidbase=android-google
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.cwm.enable_key_repeat=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.boot.emmc=0
ro.boot.mode=normal
ro.boot.modem=none
ro.boot.hardware=macallan
ro.boot.serialno=15C4110C61C0000000EFF8140
ro.boot.productid=mozart
ro.boot.commchip_id=0
ro.emmc=0
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=tegra
ro.build.id=KTU84Q
ro.build.csc.version=US_TF501T_V11.4.1.29
ro.build.date=Sun Jan  4 21:21:53 EST 2015
ro.build.date.utc=0
ro.build.epad.project=TF501T
ro.build.host=pershoot-ubuntu
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=root
ro.build.display.id=cm_tf701t-userdebug 4.4.4 KTU84Q a67270b42c test-keys
ro.build.product=tf701t
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.4
ro.build.version.codename=REL
ro.build.version.incremental=a67270b42c
ro.build.description=US_epad-user 4.4.2 KOT49H US_epad-11.4.1.29-20141218 release-keys
ro.build.fingerprint=asus/US_epad/K00C:4.4.2/KOT49H/US_epad-11.4.1.29-20141218:user/release-keys
ro.build.characteristics=tablet
ro.radio.noril=true
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.secure=1
ro.zygote.disable_gl_preload=true
ro.carrier=unknown
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=K00C
ro.product.board=macallan
ro.product.brand=asus
ro.product.model=K00C
ro.product.device=tf701t
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=asus
ro.baseband=unknown
ro.bootmode=normal
ro.hardware=macallan
ro.opengles.version=131072
ro.revision=0
ro.serialno=15C4110C61C0000000EFF8140
ro.bootloader=unknown
ro.debuggable=1
ro.modversion=11-20150105-UNOFFICIAL-tf701t
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
tf.enable=y
drm.service.enabled=true
net.bt.name=Android
net.change=net.bt.name
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
wifi.interface=wlan0
debug.hwui.render_dirty_regions=false
dalvik.vm.heapsize=512m
dalvik.vm.lockprof.threshold=500
dalvik.vm.heapmaxfree=8m
dalvik.vm.heapminfree=512k
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.75
persist.sys.dun.override=0
persist.sys.usb.config=mtp,adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.dalvik.multithread=false
persist.sys.root_access=1
persist.sys.recovery_update=false
persist.tegra.nvmmlite=1
persist.tegra.compositor=glcomposer
persist.logtool.gps.loglv=0
service.adb.root=1
keyguard.no_require_sim=true

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:using /data/media for /sdcard.
I:using /data/media for /sdcard/0/clockworkmod/.no_confirm.
I:using /data/media for /sdcard/0/clockworkmod/.many_confirm.

-- Installing: /sdcard/0/ADB+Recovery+Driver.zip
Finding update package...
I:Update location: /data/media/0/ADB+Recovery+Driver.zip
Opening update package...
Installing update...
Installation aborted.
I:using /data/media for /sdcard/0/clockworkmod/.last_install_path.
.
Last edited by HippoMan; 22nd February 2015 at 04:36 AM.
22nd February 2015, 05:03 AM   |  #602  
berndblb's Avatar
Recognized Contributor
Flag Los Angeles, CA
Thanks Meter: 1,222
 
3,506 posts
Join Date:Joined: Nov 2012
More
What zip is that????
You do not flash adb to the tablet.
You do not flash drivers to the tablet.
I think you tried to flash a package that is meant for installing adb on you computer
22nd February 2015, 05:53 AM   |  #603  
HippoMan's Avatar
Senior Member
Thanks Meter: 117
 
548 posts
Join Date:Joined: May 2009
Quote:
Originally Posted by berndblb

What zip is that????
You do not flash adb to the tablet.
You do not flash drivers to the tablet.
I think you tried to flash a package that is meant for installing adb on you computer

Oh, yes, you're right. sdbags suggested that I install those drivers because I was having trouble using adb in recovery mode, and I mistakenly thought they should be flashed onto the device. But now I see that they are just a bunch of Windows DLL's. They don't do me any good, anyway, because I don't use Windows at all ... only Linux.

For some reason, adb started working again for me in recovery mode. I have no idea why it wasn't working before nor why it's working now. Perhaps that "enhanced" kernel which kept me from booting into the OS was also interfering with adb in recovery mode.

In any case, everything is working fine now that I'm using the modded stock kernel.
.
26th February 2015, 01:49 PM   |  #604  
Senior Member
Thanks Meter: 15
 
294 posts
Join Date:Joined: May 2009
More
Why the orange light all the time?
Tablet has started getting quite hot when I leave it to charge overnight.
The orange power light stays on for a few minutes even after I turn it off and unplug it?
WTF?
What's causing the heat build up, does anyone have any idea???
26th February 2015, 07:33 PM   |  #605  
sbdags's Avatar
OP Recognized Contributor
Flag Kenilworth, Coventry
Thanks Meter: 14,092
 
11,940 posts
Join Date:Joined: Jun 2007
Donate to Me
More
Quote:
Originally Posted by Revhead

Tablet has started getting quite hot when I leave it to charge overnight.
The orange power light stays on for a few minutes even after I turn it off and unplug it?
WTF?
What's causing the heat build up, does anyone have any idea???

Is this docked or undocked?

My dock battery died and it did this just before it went.
26th February 2015, 10:26 PM   |  #606  
Senior Member
Thanks Meter: 15
 
294 posts
Join Date:Joined: May 2009
More
Unhappy
Quote:
Originally Posted by sbdags

Is this docked or undocked?

My dock battery died and it did this just before it went.

Docked.
Turned it off last night and left it charging.
This morning it is hot, the light is green and it has turned itself back on again?
I unplugged it, turned it off again and it cooled down straight away?
Wierd behaviour . . .
27th February 2015, 07:02 AM   |  #607  
berndblb's Avatar
Recognized Contributor
Flag Los Angeles, CA
Thanks Meter: 1,222
 
3,506 posts
Join Date:Joined: Nov 2012
More
Quote:
Originally Posted by Revhead

Docked.
Turned it off last night and left it charging.
This morning it is hot, the light is green and it has turned itself back on again?
I unplugged it, turned it off again and it cooled down straight away?
Wierd behaviour . . .

Don't let the dock charge unsupervised. sbdags' almost went up in flames before the battery died completely.
That it turns itself on when you connect it to power is normal. All Transformers do it.
27th February 2015, 08:14 PM   |  #608  
sbdags's Avatar
OP Recognized Contributor
Flag Kenilworth, Coventry
Thanks Meter: 14,092
 
11,940 posts
Join Date:Joined: Jun 2007
Donate to Me
More
Quote:
Originally Posted by Revhead

Docked.
Turned it off last night and left it charging.
This morning it is hot, the light is green and it has turned itself back on again?
I unplugged it, turned it off again and it cooled down straight away?
Wierd behaviour . . .

Yes as Bernd says this happened to mine. It got very hot and then the battery died. It then sporadically showed a working battery and the dock continued to work fine thereafter but the batter circuit was dead.

Boldnuts bought it off me from here but never got it to work either. I think he said one of the cables had burnt out when he opened it up to look at it.
28th February 2015, 11:07 AM   |  #609  
Senior Member
Flag Wetherby
Thanks Meter: 57
 
170 posts
Join Date:Joined: Jan 2012
More
Yep that's right the cable seems to have been nipped between the inner hinge mech shorting out the battery , you can get replacement,s though from here
http://www.asusparts.eu/en/partfinde...Pad/TF701T#PCB

I have changed both the docks and the tablets connecter which sorted things out for me
Sent from my K00C using XDA Premium HD app
Last edited by boldnuts; 28th February 2015 at 11:09 AM.

The Following 2 Users Say Thank You to boldnuts For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes