Hello !!
I installed Link2SD on my Acer liquid E (running LiquidNext 1.9.2).
linked 5 apps.
But after rebooting, Titanium autmoatically crashes, as well as other apps!!
I could not understand what the problem is !
could you please help me ?
Logcat attached
Firstly, I would actually like to thank you on taking the efforts on getting a logcat...
Loads of members nowadays think that their problem is our problem, and hence don't put in efforts in even explaining...
On the other hand, you actually did a good thing :thumbup::good:
Even though I'm not too knowledgeable on such technical stuff, I did go through your logcat (for the simple reason that you took efforts in attaching it in the first place)...
I've (hopefully) identified the problem areas:
Code:
I/Vold ( 284): Vold 2.1 (the revenge) firing up
D/Vold ( 284): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 284): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 284): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
W/Vold ( 284): Ignoring unknown switch 'MSM72K_UDC'
.
.
.
.
I/Installer( 347): connecting...
E/PackageManager( 347): Package com.keramidas.TitaniumBackup has mismatched uid: 0 on disk, 10042 in settings
I/PackageManager( 347): Linking native library dir for /data/app/com.keramidas.TitaniumBackup-1.apk
I/PackageManager( 347): Time to scan packages: 7.069 seconds
W/PackageManager( 347): Unknown permission com.android.vending.permission.UPDATE_MARKET_FAILURE in package com.android.vending.updater
W/PackageManager( 347): Unknown permission android.permission.ADD_SYSTEM_SERVICE in package com.android.phone
W/PackageManager( 347): Unknown permission android.permission.READ_EXTERNAL_STORAGE in package com.cyanogenmod.cmparts
W/PackageManager( 347): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.browser (protectionLevel=2 flags=0x9be45)
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.READ_GMAIL in package com.google.android.talk
W/PackageManager( 347): Unknown permission android.permission.READ_OWNER_DATA in package com.android.setupwizard
W/PackageManager( 347): Unknown permission android.permission.WRITE_OWNER_DATA in package com.android.setupwizard
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.WRITE_GMAIL in package com.android.settings
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.READ_GMAIL in package com.android.settings
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.READ_GMAIL in package com.google.android.apps.uploader
W/PackageManager( 347): Unknown permission com.google.android.voicesearch.SHORTCUTS_ACCESS in package com.google.android.googlequicksearchbox
W/PackageManager( 347): Unknown permission android.permission.READ_EXTERNAL_STORAGE in package com.android.vending
W/PackageManager( 347): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.vending (protectionLevel=2 flags=0xabec5)
W/PackageManager( 347): Unknown permission android.permission.SEND_SMS_NO_CONFIRMATION in package com.android.vending
W/PackageManager( 347): Not granting permission android.permission.STATUS_BAR to package com.android.vending (protectionLevel=3 flags=0xabec5)
W/PackageManager( 347): Not granting permission android.permission.PACKAGE_USAGE_STATS to package com.android.vending (protectionLevel=2 flags=0xabec5)
W/PackageManager( 347): Unknown permission android.permission.PACKAGE_VERIFICATION_AGENT in package com.android.vending
W/PackageManager( 347): Unknown permission com.google.android.verifier.permission.UPDATE_VERIFIER in package com.android.vending
W/PackageManager( 347): Not granting permission android.permission.INSTALL_PACKAGES to package com.chelpus.lackypatch (protectionLevel=3 flags=0xbe46)
W/PackageManager( 347): Not granting permission android.permission.DELETE_PACKAGES to package com.chelpus.lackypatch (protectionLevel=3 flags=0xbe46)
W/PackageManager( 347): Not granting permission android.permission.CLEAR_APP_USER_DATA to package com.chelpus.lackypatch (protectionLevel=2 flags=0xbe46)
W/PackageManager( 347): Unknown permission android.permission.READ_OWNER_DATA in package com.android.email
W/PackageManager( 347): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x8be45)
(I've put in dots .... to just state that there isn't any error there)
From what I've seen, I believe that your partition (since you are using link2sd) isn't formatted properly (or mounted)...and titanium was linked to your partition (am I right?)
Do your system apps also force close?
There's an error with the status bar...
And ya, because of that logcat, I hope we see more of such members in the future :beer:
I agree. I am thinking that your partitions are not set up correctly. IIRC from when I used Link2Sd, you had to have 1-Fat32 for normal stuff and 1-Fat32 for the apps to link too. In older versions it was Fat32, Ext2/3 and the Swap.
When you installed Link2Sd, and it checked for partitions, did it throw any errors? Does your ROM support Link2SD? I'll look around at it some more but A.cid asked for some help.
Thank you both guys for replying in such a kind way: i appreciate!
I am running this MOD: LiquidNext (latest version 1.9.2)
forum thread about the rom here
It seems to be possible to run link2SD on the above ROM.
Other apps crash as well, but I honestly can't recall whether they were system apps or not.
I have now resetted everything:
I have wiped everything, both internal and external memories (8GB SDcard).
I have formatted the sd card from the CWM Recovery (touch): EXT3 1024 MB, Swap: 0 MB, FAT32 remaining space.
I have flashed the same rom again, and haven't yet installed link2sd and Titanium.
so far everything is running smoothly, but I want to understand what's wrong when I install link2sd!
I have been running it smoothly in the past on the same ROM => then something mysterious happened
hope you guys are better than me and can find the culprit !!
Corrupt partition. Removing the link2sd script from init.d will be a temporary fix. You need to reformat your ext partition!
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________
shaaan said:
Corrupt partition. Removing the link2sd script from init.d will be a temporary fix. You need to reformat your ext partition!
Click to expand...
Click to collapse
already done !!
thanks though
Hey, I know that this isn't your device but there may be somethings in this trhead that will help you troubleshoot, like kernel modules and proper partition setup. This was my first Android device so you might see a post or two in there from me way back when.
[GUIDE] Link2SD on milestone XT 720
Woodrube said:
Hey, I know that this isn't your device but there may be somethings in this trhead that will help you troubleshoot, like kernel modules and proper partition setup. This was my first Android device so you might see a post or two in there from me way back when.
[GUIDE] Link2SD on milestone XT 720
Click to expand...
Click to collapse
Thank you but that was not of much help !!
I still haven't managed to get Link2SD to work correctly!!
help me please
Some of you may be familiar with my trials with my T699. To make a long story short, (see that story here http://forum.xda-developers.com/showthread.php?t=2528444) (thanks gee one!)
I was attempting to put CM on my Relay and I ended up hard bricking it.
I can now boot but I need a SD card installed to do it.
Recently I was playing around with adb and was running logcat which dumped a whole mess of wonderful information.
The line I thought was important was the following -
I/rmt_storage( 125): No EBR found
It is my guess that I messed up (corrupted) the EBR and that is why I am dependent on the external SD card.
My question is, does anyone know how to restore the EBR to working condition? I have tried to use odin to put the stock
image on but I think it is just over-writing the image on the SD card. If it can be done using adb that would be very great too since
it appears to be working well.
Oh, and the other thing I noticed, if I do not put the SD card, with image, into the slot I just boot into QHSUSB-DLOAD mode.
Which means much but is not useful at this time.
Thanks all,
Lou
I have added the first 25 lines of the logcat -
--------- beginning of /dev/log/main
I/rmt_storage( 125): Target is APQ8064: 1074445686
I/rmt_storage( 125): No EBR found
I/rmt_storage( 125): Error (-1) parsing MBR partitions
I/rmt_storage( 125): Registering modemst1: 0x4a /boot/modem_fs1
I/rmt_storage( 125): Registering modemst2: 0x4b /boot/modem_fs2
I/rmt_storage( 125): Registering fsg: 0x58 /boot/modem_fsg
I/rmt_storage( 125): Registering ssd: 0x5d ssd
I/rmt_storage( 125): 4 GPT partitions found
D/ICD ( 183): icd .02 runs
E/DataRouter( 186): Main entered
E/DataRouter( 186): switchUser
E/DataRouter( 186): monitor_usb_thread
E/DataRouter( 186): server_init
E/DataRouter( 186): Opening of the usb select file failed fd is -1 & errno is 2
E/DataRouter( 186): Opening of the usb select file failed fd is -1 & errno is 2
E/DataRouter( 186): Initialise USB and start the thread
E/DataRouter( 186): dr_usb_init
E/DataRouter( 186): USB Interface is open with 0x9
E/DataRouter( 186): USB interface is now configured for usb_fd = 0x9
E/DataRouter( 186): THREAD LAUNCH
E/DataRouter( 186): monitor_data_of_usb
E/DataRouter( 186): USB monitor thread launched, usb_fd= 0x9
E/DataRouter( 186): init_cur_sock
E/DataRouter( 186): Before the usb select
I/DEBUG ( 182): debuggerd: Mar 16 2013 22:15:51
*** UPDATE ***
I found another interesting line in line in the logcat ...
W/PackageManager( 674): Library not found: /system/framework/com.qualcomm.location.quipslib.jar
More on de-bricking
I have been continuing my hunt on how to permanently de-brick my T699. The following thread does not leave me with
much hope . I know it is for Evita on the HTC One but I see similar behaviour when I hook my T699 to linux.
http://forum.xda-developers.com/showthread.php?t=1966850&page=40
If anyone can comment on this it is greatly appreciated.
All of a sudden, on Stock + Root TF700T, WiFi won't turn on. I highly doubt that this is related to my WiFi router ... the WiFi won't even enable on the tablet, and I can't even see a MAC address in About Tablet section.
I also did some digging and have some additional detail, but I cannot find a solution.
logcat:
Code:
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '43 softap fwreload wlan0 STA' failed with '400 43 Softap operation failed (No such file or directory)'
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2767): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2767): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2767): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2767): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 3ms+3ms, total 57ms
D/AsusBrightnessManager( 489): br transform : 35 -> 13
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '46 softap fwreload wlan0 STA' failed with '400 46 Softap operation failed (No such file or directory)'
E/WifiStateMachine( 489): Failed 6 times to start supplicant, unload driver
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '48 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 48 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2792): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2792): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2792): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2792): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 2ms+1ms, total 22ms
W/NvCpuClient( 489): Failed to bind to service
D/AsusBrightnessManager( 489): br transform : 35 -> 13
E/WifiHW ( 489): Supplicant not running, cannot connect
W/NvCpuClient( 489): Failed to bind to service
Also, output from netcfg:
Code:
[email protected]:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
dummy0 DOWN 0.0.0.0/0 0x00000082 76:ad:93:6b:c9:b7
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
And here is output of my wpa_supplicant.conf:
Code:
[email protected]:/ # cat /etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
And I searched the entire filesystem for "nl80211" and found nothing.
Does anyone have suggestions on where to go next? Did my driver somehow get deleted, or am I just not looking for the right thing?
Thanks.
I will use this question in the future as an example of how to ask for support properly. Unfortunately I don't have a solution for you, but you could check the files in your /data/misc/wifi, maybe you can find something unusual. Your MAC address should come from some file on the FAT filesystem on /dev/block/mmcblk0p5 - I'd recommend making an image of it as a backup and then analyze the image.
_that said:
I will use this question in the future as an example of how to ask for support properly.
Click to expand...
Click to collapse
I provide Enterprise-level support to software devs working in the Cloud and particularly on CentOS/RHEL Linux servers. This is why I know how to ask for help properly.
Well, since I can't find much, and there aren't any definitive answers here, my next thoughts are:
1) Something is seriously jacked up on the filesystem, possibly corrupted driver, possibly something worse. Hopefully, this is the case, because a software problem is possible to fix.
2) The WiFi radio is permanently damaged, or "burnt out".
In the hopes that it's something more like software, I'm going to reimage. I just need to decide what ROM to use. Not having network connectivity will make the prep for this a bit more challenging, but I can work through it using a MicroSD card.
If it's #2, well then I suppose I will have wasted my time reimaging and will be on the market for a new tablet ... and I need to get on that right away because I need to travel soon. Any suggestions are welcome ... I'd like a 9" or 10" tablet and it must have an HDMI out (micro preferred) and be able to handle 1080p video.
Thanks.
[SOLVED]
I am having a heckuva time even doing what I described above.
-I had never unlocked the bootloader before, so when I tried the ASUS unlock util v8, it gave error "INSTALL_FAILED_SHARED_USER_INCOMPATIBLE"
-I tried the ASUS unlock tool v7, and was finally able to install it but when I run and select Unlock I get an error that there is no network connection (FFS that's what I'm trying to resolve!)
-I can't get into recovery, I just get the Android guy with "ERROR!" when I enter fastboot and select "RCK".
My only option is to go back to Stock. So, I tried this:
http://forum.xda-developers.com/showthread.php?t=1833212
The steps in that post result in the same Android guy with the "ERROR!" screen ... not a very helpful error msg.
So, I tried this, and used the stock firmware from ASUS. (NOTE: I downloaded "ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)" directly from ASUS after I read their notes on where to check for which one you need ([Settings]-->[About tablet]-->Build number).):
http://www.transformerforums.com/fo...e-firmware-tf700-tf701-tf300-tf101-tf201.html
From that post ^^ I did Method B: Flash from MicroSD. I extracted the .zip I downloaded from ASUS, and renamed the new zip EP201_768_SDUPDATE.zip per the GUIDE linked above.
I put in my MicroSD, went back into fastboot, and selected "RCK". It was at this point that I began typing the above. Total time to get to this point was about 90 minutes!
-----
FINALLY, for the first time, I saw a progress bar under the Android guy, and he had gears turning in his belly.
*INSERT SIGH OF RELIEF HERE*
As I was typing out all the above, progress bars were moving, and a few reboots happened. I expected that I would be fully back on Stock ROM, and that my data would have been wiped. I never ran a data wipe, I just assumed the ASUS installer would do that by default.
Well, it didn't wipe data. But, what it did do: restore all my device drivers!! After about 10 minutes, and 2-3 reboots, Android loaded with my existing desktop and settings, and the WiFi connected right away!!
So, this fixed it. I documented the above so anyone (even me, months from now) having a similar problem might be able to use these steps.
WOO HOO!
lost root
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.
CaptainRewind said:
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.
Click to expand...
Click to collapse
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
sbdags said:
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Click to expand...
Click to collapse
Yep, I had to do that anyway because I wanted to do a full Titanium Backup first. Still, I'm moving to CM now.
I encountered this weird case that
after creating a symlink in 3c toolbox, external storage is cannot be detected in MTP mode in windows. Only phone storage was detects. 2 drives vs 1 now.
I tested that the micro SD card is detectable with
a usb card reader
TWRP mode
and internally by Android.
Only it is missing from MTP.
Anyone has encountered this before?:crying::crying:
07-29 10:17:37.871 D/MtpService(4913): Adding MTP storage 0x10001 at /storage/emulated/0
07-29 10:17:37.871 E/MtpServerJNI(4913): server is null in add_storage
07-29 10:17:37.871 D/MtpService(4913): Adding MTP storage 0xe550001 at /storage/9C33-6BBD
07-29 10:17:37.871 E/MtpServerJNI(4913): server is null in add_storage
07-29 10:17:37.871 E/MtpServerJNI(4913): server is null in run
07-29 10:17:37.871 E/MtpServerJNI(4913): server is null in cleanup
07-29 10:17:37.881 V/MtpMediaDBManager(17347): inside Thread updateFilesTable
07-29 10:17:37.881 E/MtpServerJNI(4913): server is null in send_object_removed
07-29 10:17:37.901 E/ (17347): mtp_get_storage_ids_mtp_handle : START !!
I encountered this weird case that
after creating a symlink in 3c toolbox, external storage is cannot be detected in MTP mode in windows. Only phone storage was detects. 2 drives vs 1 now.
I tested that the micro SD card is detectable with
a usb card reader
TWRP mode
and internally by Android.
Only it is missing from MTP.
Anyone has encountered this before?
To add some debug onformation from logcat:
07-29 10:17:37.871 D/MtpService(4913): Adding MTP storage 0x10001 at /storage/emulated/0
07-29 10:17:37.871 E/MtpServerJNI(4913): server is null in add_storage
07-29 10:17:37.871 D/MtpService(4913): Adding MTP storage 0xe550001 at /storage/9C33-6BBD
07-29 10:17:37.871 E/MtpServerJNI(4913): server is null in add_storage
07-29 10:17:37.871 E/MtpServerJNI(4913): server is null in run
07-29 10:17:37.871 E/MtpServerJNI(4913): server is null in cleanup
07-29 10:17:37.881 V/MtpMediaDBManager(17347): inside Thread updateFilesTable
07-29 10:17:37.881 E/MtpServerJNI(4913): server is null in send_object_removed
07-29 10:17:37.901 E/ (17347): mtp_get_storage_ids_mtp_handle : START !!