adb backup fails when shared storage is enabled - Xperia Z5 Compact Q&A, Help & Troubleshooting

On my Sony Xperia Z5 Compact, when trying to make the adb backup with shared option enabled it displays forever the message "Shared storage" on the screen for more than an hour. Finally I cancelled it because I guessed out it was wrong. This is a fragment of adb logcat:
----------------------------------------------------
1402 3109 V BackupManagerService: Requesting full backup: apks=true obb=true shared=true all=true system=false pkgs=[Ljava.lang.String;@874481f
[...]
1402 22074 D BackupManagerService: Binding to full backup agent : com.android.sharedstoragebackup
1402 22074 D BackupManagerService: awaiting agent for ApplicationInfo{c76bf85 com.android.sharedstoragebackup}
1402 1412 D BackupManagerService: agentConnected pkg=com.android.sharedstoragebackup [email protected]
1402 22074 I BackupManagerService: got agent [email protected]
1402 22074 I BackupRestoreController: Getting widget state for user: 0
1402 23361 D BackupManagerService: Calling doFullBackup() on com.android.sharedstoragebackup
22075 22086 I SharedStorageAgent: Backing up 1 shared volumes
22075 22086 I FullBackup: Unrecognized domain shared/0
22075 22075 I Process : Sending signal. PID: 22075 SIG: 9

Related

not using google voice?

When I dial a call all that happens is it places the call through verizon and not google voice any one else have this issue?, The guy at the store ran the ota before I was even handed the phone...
*Update 1 (4:13 pm): google voice seems to crash when rebooting =\
*Update 2 (4:23 pm): ADB Logcat output with grep on voice
Code:
[email protected]:~/Desktop/****/SDK/android-sdk-linux_86/tools$ cat adb.log | grep voice
W/PackageManager( 74): Unknown permission com.google.android.permission.SEND_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.permission.RECEIVE_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.apps.googlevoice.REMOTE_INTENT in package com.google.android.apps.googlevoice
D/HtcCdmaPhoneApp( 111): voice privacy setting=1
D/HtcCdmaPhoneApp( 111): voice privacy status=-1
I/ActivityManager( 74): Start proc com.android.voicedialer for broadcast com.android.voicedialer/.VoiceDialerReceiver: pid=336 uid=10042 gids={3002}
D/VoiceDialerReceiver( 336): onReceive Intent { action=android.intent.action.BOOT_COMPLETED comp={com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver} }
D/RecognizerEngine( 336): deleteCachedGrammarFiles /data/data/com.android.voicedialer/files/openentries.txt
D/GooglePartnerSetup( 341): voicesearch client id: ms-android-verizon
I/ActivityManager( 74): Start proc com.google.android.apps.googlevoice for broadcast com.google.android.apps.googlevoice/.BootUpReceiver: pid=348 uid=10049 gids={3003}
E/dalvikvm( 348): Could not find method android.content.Context.getApplicationInfo, referenced from method com.google.android.apps.googlevoice.BootUpReceiver.onReceive
W/dalvikvm( 348): VFY: rejected Lcom/google/android/apps/googlevoice/BootUpReceiver;.onReceive (Landroid/content/Context;Landroid/content/Intent;)V
W/dalvikvm( 348): Verifier rejected class Lcom/google/android/apps/googlevoice/BootUpReceiver;
W/dalvikvm( 348): Class init failed in newInstance call (Lcom/google/android/apps/googlevoice/BootUpReceiver;)
E/AndroidRuntime( 348): java.lang.VerifyError: com.google.android.apps.googlevoice.BootUpReceiver
I/ActivityManager( 74): Process com.google.android.apps.googlevoice (pid 348) has died.
-Chr1831
Yes it started crashing here after the MR2
Snakehn said:
Yes it started crashing here after the MR2
Click to expand...
Click to collapse
I can confirm this on my end as well. After the first OTA update there was no issue, but MR2 screwed with it. I found I can launch the application after the initial boot crash, but haven't confirmed that it is working as it should on my phone.
I get GV FC's on startup but then again I only use it for voicemail and its working pretty good.
I got version 2.5 to work just not 3.0 hopefully the (htc) update on the 22end will address this bug
Still some issues for me. It FCs on boot. All though most functionality is there..
When I call out things are strange, contact pics don't work and the outgoing number is not the dialed number its the GV "bridge" number.
Both of the above issues do not exist on my moto droid.
I wish it was fixed.

[GUIDE][ULTIMATE][Noobs-friendly]How to fix bugs and bootloop on a ported roms

I Think this Guide going to help u lot
With this guide i think u will make a stable rom
So lets Start
1.)For fixing Bootloop when porting rom
Replace :
Code:
/system/lib/libandroid_runtime.so
/system/lib/libandroid_servers.so
/system/lib/libmedia_jni.so
*Repack boot.image
2.)Showing black screen after boot
Replace:
Code:
/system/lib/libMali.so
3.)Fixing Sensors
Replace:
Code:
/system/bin/akmd*
/system/lib/libsensors.so
/system/lib/libms3c_yamaha.so
/system/etc/firmware (folder)
/system/bin/servicemanager
4.)Fixing Bluetooth\Wifi not turning On\Off
Replace:
Code:
/system\lib\module\mtk_stp_wmt
5.) Fixing RadioFM
Replace:
Code:
\system\bin\fmradio
\system\etc\firmware\mt6620_patch_e3_hdr.bin
\system\etc\firmware\mt6620_patch_e6_hdr.bin
\system\etc\firmware\WMT.CFG
\system\lib\modules\mtk_fm_drv.ko
\system\lib\libfmcust.so
6.) Fixing Bluetooth
Replace:
Code:
/system/bin/bd_prov
/system/bin/uim*
/system/bin/hcid
/system/bin/bluetooth*
/system/bin/hciattach
/system/bin/sdptool
/system/xbin/hciconfig
/system/bin/brcm_patchram_plus
/system/lib/libbluetooth_mtk.so
/system/lib/libbluetoothem_mtk.so
7.) Fixing Wifi
Replace:
Code:
Wifi :
/system/bin/netcfg
/system/bin/dhcpcd
/system/bin/ifconfig
/system/bin/hostap
/system/bin/hostapd
/system/bin/hostapd_bin
/system/bin/pcscd
/system/bin/wlan*
/system/bin/wpa*
/system/bin/netd -> Fix wifi hotspot
/system/lib/libhardwarelegacy.so -> Fix wifi /system/lib/modules/mtk_stp_wmt.ko/system/lib/modules/mtk_wmt_wifi.ko
/system/etc/wifi (folder)
/system/etc/firmware (folder)
8.) Fixing Camera
Replace :
Code:
system/lib/libfeatureio.so - camera not working
/system/etc/media_profiles.xml
/system/lib/libcamera.so
/system/lib/liboemcamera.so
\system\lib\hw\camera.default.so
\system\lib\libcamera_client.so
\system\lib\libcameracustom.so
\system\lib\libcamer aprofile.so
\system\lib\libcameraservice.so
\system\lib\libmhal.so
\system\lib\libmhalcontent.s o
\system\lib\libmhaldrv.so
\system\lib\libmhalmdp.so
\system\lib\libmhalpipe.so
\system\lib\libmhalscenario.so
\system\lib\libmhalutility.so
\system\etc\permission\android.hardware.camera.front.xml
\system\lib\libOmx*.so -fix camcoder
\system\lib\libfeatureo.so -fix cam focus
# camera not working or force close or any other problem
copy all libs starting with /libcam*.so
#Camera showing wrong model in pic property?
Change model in build.prop
Still not working? Replace following file from STOCK to PORT
system/lib/libexif.so
9.)Fixing SD card/memory
Replace:
Code:
/system/bin/vold
\system\etc\vold.fstab -> edit file for swap internal and external
\system\etc\vold.fstab.nand
10.)Fixing Storage Not mounting
Replace:
Code:
Decompile framework-res.apk using apktool or apk multitool and replace following file from STOCK framework-res.apk to PORT framework-res.apk
/res/xml/storage_list.xml
11.) Fixing GPS
Replace:
Code:
\system\xbin\libmnlp
/system/etc/gps.conf
12.) Fixing Touch Screen(Haptic)
Replace :
Code:
/system/usr
/system/usr\keylayout\Generic.kl ->fix HomeKey
13.) Fixing Sim1/2 (RIL)
Replace:
Code:
\system\etc\firmware\modem.img
\system\etc\permission (RIL)
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
14.) Fixing Audio/Sound
Relace:
Code:
\system\lib\libaudio* .so
15.) Fixing Network / 3G Network
Replace:
Code:
/ system / etc / agps_profiles_conf
/ system / etc / APNs-conf
/ system / etc / epo-conf
/ system / etc / spn-conf
/ system / etc / virtual-spn-conf-by-efspn
/ system / etc / virtual-spn-conf-by-IMSI
16.)Fixing Pixalation in video
Replace:
Code:
Replace following file from STOCK to PORT or Port to ur Ported rom
system/lib/libvcodecdrv.so
---------------------------------------------------------------
Note Some file will not be there so dont worry jst skip it
And last thing Dont forget to Press Thanks If this helped .......................:good:​
Reserved
Thank you @adityaupreti ... i need this badly.... I will try to fix the bugs in my port ROM using this guide bro.....whenever i hav time......Thanks A lot bro
Please elaborate for bootloop.
as you said replace these files from port system folder & repack your boot image.
what changes it will make to boot image ?
will this work for 32 bit or 64 bit ?
---------- Post added at 09:48 AM ---------- Previous post was at 09:07 AM ----------
what if stuck at boot animation ?
rajlko said:
Please elaborate for bootloop.
as you said replace these files from port system folder & repack your boot image.
what changes it will make to boot image ?
will this work for 32 bit or 64 bit ?
---------- Post added at 09:48 AM ---------- Previous post was at 09:07 AM ----------
what if stuck at boot animation ?
Click to expand...
Click to collapse
rajlko said:
Please elaborate for bootloop.
as you said replace these files from port system folder & repack your boot image.
what changes it will make to boot image ?
will this work for 32 bit or 64 bit ?
---------- Post added at 09:48 AM ---------- Previous post was at 09:07 AM ----------
what if stuck at boot animation ?
Click to expand...
Click to collapse
whats ur phone model and what is the model of phone ur porting?
brownstyle said:
whats ur phone model and what is the model of phone ur porting?
Click to expand...
Click to collapse
ze550kl, 5.0.2 ( https://www.asus.com/in/Phone/ZenFone-2-Laser-ZE550KL/HelpDesk_Download/ 1.16.40.763) & YU Lettuce 12.0 version. (https://download.cyanogenmod.org/get/jenkins/124086/cm-12-20150901-SNAPSHOT-YNG4NAO254-lettuce.zip)
adityaupreti said:
Click to expand...
Click to collapse
Dear,
Please provide a solution, your solution does not work & it s still in bootloop, you have replied with
rajlko said:
ze550kl, 5.0.2 ( https://www.asus.com/in/Phone/ZenFone-2-Laser-ZE550KL/HelpDesk_Download/ 1.16.40.763) & YU Lettuce 12.0 version. (https://download.cyanogenmod.org/get/jenkins/124086/cm-12-20150901-SNAPSHOT-YNG4NAO254-lettuce.zip)
Click to expand...
Click to collapse
i think huawei honor 4x is a better option
brownstyle said:
i think huawei honor 4x is a better option
Click to expand...
Click to collapse
4x have 5.1 but base rom is 5.0.2.
rajlko said:
Dear,
Please provide a solution, your solution does not work & it s still in bootloop, you have replied with
Click to expand...
Click to collapse
It will not work coz ur porting a marshmallow or lollipop based ROM
Use any other guide of porting and then come to my threadto fix bugs
rajlko said:
ze550kl, 5.0.2 ( https://www.asus.com/in/Phone/ZenFone-2-Laser-ZE550KL/HelpDesk_Download/ 1.16.40.763) & YU Lettuce 12.0 version. (https://download.cyanogenmod.org/get/jenkins/124086/cm-12-20150901-SNAPSHOT-YNG4NAO254-lettuce.zip)
Click to expand...
Click to collapse
thanx for providing this link but when i try to flash it says E:footer is wrong installation aborted.we have the same device asus ze550kl..wat could have been the problem?
brownstyle said:
thanx for providing this link but when i try to flash it says E:footer is wrong installation aborted.we have the same device asus ze550kl..wat could have been the problem?
Click to expand...
Click to collapse
asus signature verification process is totally different. , I have provided both link so that any one may try to port it.
both having same version android, same cpu, same gpu.
rajlko said:
asus signature verification process is totally different. , I have provided both link so that any one may try to port it.
both having same version android, same cpu, same gpu.
Click to expand...
Click to collapse
is there any way to bypass that verification process?any other workaround?
what are the lib files for bluetooth in Marshmallow for Qualcomm devices ? I have found libbluetooth_jni.so but replacing it didn't fix the issue. What other files do I have to replace?
Great Work
Thanks for this guide
ROBERT CM said:
Great Work
Thanks for this guide
Click to expand...
Click to collapse
Ur welcome
Hi adi bro.
I have cm 12.1 ROM but in camera video recording is not working can u tell me how to fix it??
Man trying get wifi on this port to the s6 i found some files which i moved then bingo wifi turned on scanning put password in now its saying Failed to obtain IP address any tips some the files just arnt there. I got 920p S6
Jimmy1life said:
Man trying get wifi on this port to the s6 i found some files which i moved then bingo wifi turned on scanning put password in now its saying Failed to obtain IP address any tips some the files just arnt there. I got 920p S6
Click to expand...
Click to collapse
Always when i had that problem, i had to go to system/etc/dhcpcd and change the permission of dhcpcd-run-hooks so that "Owner", "Group" and "Others" can execute. Also in build.prop you can change ro.secure.storage=true to false (if it's not already). This is usaly for not saving the password but worth a try.
And by the way if someone has more knowledgement than me:
I'm on the Note Edge and therefor does no exist a CM 13 version. I have read somewhere you can do it also with a sammy rom as base. So i took a S7 edge rom and a Note edge rom, both 6.0.1. I get it to flash and boot but endless boot. I pulled the prev_dump.log to get the errors but all i can see is this
Code:
01-01 00:11:15.899 17542 17542 I boot_progress_system_run: 680900
01-01 00:11:15.999 17542 17542 W SystemConfig: [COLOR="red"]Got exception parsing permissions[/COLOR].
01-01 00:11:15.999 17542 17542 W SystemConfig: [COLOR="red"]org.xmlpull.v1.XmlPullParserException: No start tag found[/COLOR]
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemConfig.readPermissionsFromXml(SystemConfig.java:275)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemConfig.readPermissions(SystemConfig.java:197)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemConfig.(SystemConfig.java:157)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemConfig.getInstance(SystemConfig.java:110)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.pm.PackagePrefetcher.prefetchPermissions(PackagePrefetcher.java:251)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemServer.run(SystemServer.java:420)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemServer.main(SystemServer.java:363)
01-01 00:11:15.999 17542 17542 W SystemConfig: at java.lang.reflect.Method.invoke(Native Method)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
01-01 00:11:16.059 17542 17630 W ResourceType: Failure getting entry for 0x7f020020 (t=1 e=32) (error -75)
01-01 00:11:16.059 17542 17630 D PackagePrefetcher: put: /system/app/ANTRadioService
01-01 00:11:16.089 702 866 E BootAnimationLoader: [email protected] : ####Clear Cover is closed####
01-01 00:11:16.099 17542 17542 D AndroidRuntime: Shutting down VM
01-01 00:11:16.099 17542 17542 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
01-01 00:11:16.099 17542 17542 E AndroidRuntime:[COLOR="red"] java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "TZ_CCM_register_default" referenced by "/system/lib/libandroid_servers.so"...[/COLOR]
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at java.lang.Runtime.loadLibrary(Runtime.java:372)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1076)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:463)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:363)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
01-01 00:11:16.119 17542 17629 D PackagePrefetcher: put: /system/app/AllShareCastPlayer
01-01 00:11:16.149 17542 17542 E android.os.Debug: ro.product_ship = true
01-01 00:11:16.149 17542 17542 E android.os.Debug: ro.debug_level = 0x4f4c
01-01 00:11:16.149 17542 17542 E android.os.Debug: sys.mobilecare.preload = false
01-01 00:11:16.149 17542 17542 E AndroidRuntime: Error reporting crash
01-01 00:11:16.149 17542 17542 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke interface method 'void android.app.IActivityManager.handleApplicationCrash(android.os.IBinder, android.app.ApplicationErrorReport$CrashInfo)' on a null object reference
01-01 00:11:16.149 17542 17542 E AndroidRuntime: at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:96)
01-01 00:11:16.149 17542 17542 E AndroidRuntime: at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
01-01 00:11:16.149 17542 17542 E AndroidRuntime: at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
01-01 00:11:16.149 17542 17542 I Process : Sending signal. PID: 17542 SIG: 9
01-01 00:11:16.179 702 866 E BootAnimationLoader: [email protected] : ####Clear Cover is closed####
01-01 00:11:16.209 16339 16339 [COLOR="Red"]E Zygote : Exit zygote because system server (17542) has terminated[/COLOR]
But i don't know how to solve it.
Or is it kernel related because of selinux (i use stock Note edge)?
Code:
[ 537.872906] init: Warning! Service gatekeeperd needs a SELinux domain defined; please fix!
[ 537.873485] init: Warning! Service gpu_snapshotd needs a SELinux domain defined; please fix!
[ 537.873938] init: Warning! Service thermal-engine needs a SELinux domain defined; please fix!
[ 537.874395] init: Warning! Service imsqmidaemon needs a SELinux domain defined; please fix!
[ 537.874892] init: Warning! Service mdm_helper needs a SELinux domain defined; please fix!
[ 537.875353] init: Warning! Service mdm_helper_proxy needs a SELinux domain defined; please fix!
[ 537.886664] init: cannot execve('/system/bin/mdm_helper_proxy'): Permission denied
[ 537.887518] init: cannot execve('/system/bin/mdm_helper'): Permission denied
[ 537.887717] init: property_set("ro.service.mdm_helper_restarted", "true") failed
[ 537.888674] init: setgid failed: Invalid argument
[ 537.890330] init: cannot execve('/system/vendor/bin/thermal-engine'): Permission denied
[ 537.891130] init: cannot execve('/system/bin/gpu_snapshotd'): Permission denied
[ 537.891871] init: cannot execve('/system/bin/gatekeeperd'): Permission denied
Or is it completly nonsens?
Thank you.
prev_dump.log

[Root] Use your phone as a BOOTABLE CDROM

CD Switcher requires [root].
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are into IT or cautious or ever had a drive die, you know that sometimes you can't trust a hard drive. Need to resize a partition but can't do it while the system is running? Want a clean virus scan? We all need a good boot disk sometimes and now you can carry a bunch on your phone !
Like DriveDroid and similar products, this uses the gadget driver in the Linux kernel. This updated version should work on more devices and custom ROMs, but has had very little testing. It's Alpha-ware and I'll add more features later.
Install CD Switcher APK (yes, I wrote it) from here:
https://drive.google.com/file/d/1ZdSYIhs7pq8IrOZ4NBX4dzPSYP5tdeIh/view?usp=drivesdk
Now tap on any ISO file. It can be inside an email or on the web and it will download it. (Unfortunately, this is how it works with the OOS file manager, meaning it makes an extra copy, so using FX, pictured, is recommended). The system will ask how to open it. Select CD switcher and 'Always' and grant root when it asks.
The DriveDroid APK doesn't work on stock OOS. I've booted many CDs with this tool. You can change CDs with just a tap. Have fun with your 128GB!
EDIT: New version using better methods doesn't rely on OOS init.
Sweet! I have always wanted to be able to do this but I have not been able to ever get drivedroid to work! I can't wait to try it out and not have to carry around more than my phone and a usb cable
knightrider64 said:
Sweet! I have always wanted to be able to do this but I have not been able to ever get drivedroid to work! I can't wait to try it out and not have to carry around more than my phone and a usb cable
Click to expand...
Click to collapse
I've heard drivedroid works with other kernels but the UI is a nightmare so I would still rather use this. Let me know if you have any issues with it.
Sent from my ONEPLUS A3000 using Tapatalk
Great app, works fine. But how do you umount the iso?
Any chance to get vhd's to work? I have an external hard drive that boots CDs and vhd's. Would be great to have it all on my phone :good:
thomas_pieps said:
Great app, works fine. But how do you umount the iso?
Click to expand...
Click to collapse
You can't. Not really any need to since it mounts read only. You can unplug it at any time.
Sent from my ONEPLUS A3000 using Tapatalk
domsch1988 said:
Any chance to get vhd's to work? I have an external hard drive that boots CDs and vhd's. Would be great to have it all on my phone :good:
Click to expand...
Click to collapse
You could do a raw disk image such as created by "dd" (and name it with an ISO extension even though it isn't), but I'd have to do more work to enable write access. All the work is done by the kernel which wants a raw disk image.
Sent from my ONEPLUS A3000 using Tapatalk
Can whatever it writes to the system be unwritten? Would I be able to take and OTA update after using this if I removed it and the ISO files?
stevenswall said:
Can whatever it writes to the system be unwritten? Would I be able to take and OTA update after using this if I removed it and the ISO files?
Click to expand...
Click to collapse
No! Full OTA only. Its not about the changes made. Your /system partition is on an ext4 filesystem which is journalled. Every write changes metadata and the journal. Incremental OTAs generally will change data block by block, and there is no telling what blocks it will change. The ISO files and APK aren't on the system partition and won't affect anything.
There is an older version of this that doesn't write to the system partition at all, but you have to set the ISO with the cable unplugged and then plug in your USB. The moment you change USB in any way, such as turning on MTP, the oneplus init scripts will revert the configuration back to the default USB drivers. Turning the USB drivers ISO into a symlink is what lets it survive MTP being turned on and is minimally invasive and revertable, but it still modfies blocks in the filesystem. If you want the older/safe one I can put up the link, just know that MTP and this can't be on at once with the old one since OnePlus has a bug that keeps turning off MTP (same thing that reverts the ISO).
I'm actually pretty sure it will be safe, but I personally wouldn't chance it and am recommending against it. The best bet would be to make a Magisk module, but I'm planning on replacing Magisk with something of my own, so I can't really spend time on such a solution. Since you've already rooted, using full OTAs over incremental is generally the method most people use anyway and will be totally safe. A system update will set your ISO back to USB drivers, just set your new ISO with the app again and it will be fine.
Sent from my ONEPLUS A3000 using Tapatalk
Thanks! Why not publish it as open source on github and put it on F-Droid?
Is it possible to have a windows 10 iso to boot in uefi mode with this tool?
installed the app but can't see it in app drawer can't open it!
my mistake.
i tested it and it works but without boot option. can u enable the option to write on the image? not read only?
and i tried to mount a windows installation iso and it doesnt work properly. i want to connect the phone to usb and boot from it to install
windows and other operating systems... and use disk tools etc
what can i\u do? thanks!!!
How can I use this on AOSPA Because you say it only works with the OnePlus File Manager. I got the apk for that but I cant install it because it conflicts with the current file explorer from AOSPA built in, I cant remove it with System App Uninstaller. Any solutions?
lindahl85 said:
Is it possible to have a windows 10 iso to boot in uefi mode with this tool?
Click to expand...
Click to collapse
Yes
DJArielLB said:
my mistake.
i tested it and it works but without boot option. can u enable the option to write on the image? not read only?
and i tried to mount a windows installation iso and it doesnt work properly. i want to connect the phone to usb and boot from it to install
windows and other operating systems... and use disk tools etc
what can i\u do? thanks!!!
Click to expand...
Click to collapse
An ISO is read only. It can't be written to. I have mounted a Windows install ISO just fine. What was the error?
R3dRacer said:
How can I use this on AOSPA Because you say it only works with the OnePlus File Manager. I got the apk for that but I cant install it because it conflicts with the current file explorer from AOSPA built in, I cant remove it with System App Uninstaller. Any solutions?
Click to expand...
Click to collapse
Actually, it only worked on OnePlus phones because it needed the USB setup used on OnePlus.
Somehow this thread got unmarked and I missed all the responded. Sorry! The good news is that I have a new Alpha version that should work on non-OnePlus devices and ROM's. This one doesn't touch the system partition either.
https://drive.google.com/file/d/1ZdSYIhs7pq8IrOZ4NBX4dzPSYP5tdeIh/view?usp=drivesdk
j03x2 said:
Thanks! Why not publish it as open source on github and put it on F-Droid?
Click to expand...
Click to collapse
Source is on my Github
Wait so how do I use this? I selected to open the ISO with the app, and I granted root, and it said iso location, etc.
I plugged it into my PC via USB but I'm not seeing a bootable option...
Edit now I see a usb item but it tells me grub incorrect filesystem or something
I'm trying an Ubuntu iso
NateDev said:
Wait so how do I use this? I selected to open the ISO with the app, and I granted root, and it said iso location, etc.
I plugged it into my PC via USB but I'm not seeing a bootable option...
Edit now I see a usb item but it tells me grub incorrect filesystem or something
I'm trying an Ubuntu iso
Click to expand...
Click to collapse
If you got to rub that it's actually booting off of the phone. It's up to the iso manufacturer to make sure that you can boot off a USB CD-ROM. So the phone is working, it's something in the iso that's messed up. Try a different ISO image
It doesn't seem to work on OOS beta 25 - app opens, reads something, tries to change usb mode (I can hear disconnect and connect sounds on Windows), returns to MTP and then closes itself.
Is this because of system being beta or custom kernel?
Code:
04-24 18:22:07.049 5923 9743 I ActivityManager: START u0 {act=android.intent.action.VIEW dat=content://pl.solidexplorer2.files/storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso typ=application/x-iso9660-image flg=0x10000001 cmp=systems.eddon.android.cdromswitcher/.MainActivity (has extras)} from uid 10091 pid 11517
04-24 18:22:07.065 560 560 E ANDR-PERF-MPCTL: hint lookup failed
04-24 18:22:07.067 5923 9743 E ANDR-PERF-JNI: com_qualcomm_qtiperformance_native_perf_io_prefetch_start
04-24 18:22:07.079 5923 9743 E ANDR-PERF-JNI: gIOPHAl initialized
04-24 18:22:07.079 5923 9743 E ANDR-PERF-JNI: gIOPHAl calling iopstart
04-24 18:22:07.079 559 559 E ANDR-IOP: IOP HAL: Received pkg_name = systems.eddon.android.cdromswitcher pid = -1
04-24 18:22:07.094 5923 6352 D RestartProcessManager: Duration is too short, ignore : 861 in pl.solidexplorer2
04-24 18:22:07.097 560 560 E ANDR-PERF-MPCTL: hint lookup failed
04-24 18:22:07.097 5923 6352 D RestartProcessManager: Update Total Launch Times :systems.eddon.android.cdromswitcher
04-24 18:22:07.097 5923 6352 D RestartProcessManager: updateSelf : systems.eddon.android.cdromswitcher, size : 13
04-24 18:22:07.098 5923 6352 D RestartProcessManager: Increase Total Launch Time : systems.eddon.android.cdromswitcher, times : 6, index : 12
04-24 18:22:07.098 5923 6352 D RestartProcessManager: Last Running Package : systems.eddon.android.cdromswitcher , start time 1524586927097
04-24 18:22:07.132 11826 12327 D TextDisplay: URL: /storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso
04-24 18:22:07.132 11826 12327 D TextDisplay: Using scheme content
04-24 18:22:07.133 11826 12327 D TextDisplay: Using filename: /storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso
04-24 18:22:07.133 11826 12327 I writeToSystem: Starting root commands
04-24 18:22:07.137 11826 12327 I suwait : Aquiring root!
04-24 18:22:07.162 468 12330 D Magisk : su: request from client: 22
04-24 18:22:07.162 468 12330 D Magisk : su: request from uid=[10176] (#1)
04-24 18:22:07.163 468 12330 D Magisk : su_db: query policy=[2]
04-24 18:22:07.164 468 12330 D Magisk : su: waiting child: [12331]
04-24 18:22:07.164 12331 12331 D Magisk : su: child process started
04-24 18:22:07.166 12331 12331 D Magisk : su: argc=[3]
04-24 18:22:07.166 12331 12331 D Magisk : su: argv[0]=[su]
04-24 18:22:07.166 12331 12331 D Magisk : su: argv[1]=[-]
04-24 18:22:07.166 12331 12331 D Magisk : su: argv[2]=[root]
04-24 18:22:07.166 12331 12331 D Magisk : su: pts_slave=[]
04-24 18:22:07.167 12331 12331 D Magisk : su: use namespace of pid=[12328]
04-24 18:22:07.186 11517 11535 D OpenGLRenderer: endAllActiveAnimators on 0xbb759b00 (SEGridView) with handle 0xd1a199a0
04-24 18:22:07.200 6682 6682 I GoogleInputMethod: onFinishInput() : Dummy InputConnection bound
04-24 18:22:07.200 6682 6682 I GoogleInputMethod: onStartInput() : Dummy InputConnection bound
04-24 18:22:07.204 5923 6361 I ActivityManager: Displayed systems.eddon.android.cdromswitcher/.MainActivity: +99ms
04-24 18:22:07.394 12332 12332 W ADebug : Failed to get property persist.sys.media.traces
04-24 18:22:07.405 12332 12332 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
04-24 18:22:07.580 12189 12262 I NetworkController.MobileSignalController(2): showDisableIcon:false
04-24 18:22:07.798 5923 6541 I SettingsState: [PERSIST START]
04-24 18:22:07.850 5923 7879 I OpenGLRenderer: Initialized EGL, version 1.4
04-24 18:22:07.850 5923 7879 D OpenGLRenderer: Swap behavior 2
04-24 18:22:08.069 12332 12332 D AndroidRuntime: Calling main entry com.android.commands.am.Am
04-24 18:22:08.099 12332 12332 D AndroidRuntime: Shutting down VM
04-24 18:22:08.138 11826 12327 I suwait : I am root
04-24 18:22:08.138 11826 12327 D powrite-send: cat /sys/class/android_usb/android0/functions
04-24 18:22:08.158 5923 6524 D DebugKeepScreenOn: Acquiring screen wakelock due to Window{a0aa7c u0 Toast}
04-24 18:22:08.340 11826 12327 I powrite#: mtp,mass_storage,hid
04-24 18:22:08.340 11826 12327 D powrite-send: echo 0 >/sys/class/android_usb/android0/enable
04-24 18:22:08.441 7726 12141 E MtpServer: request read returned -1, errno: 5
04-24 18:22:09.077 560 625 E ANDR-PERF-OPTSHANDLER: perf_lock_rel: updated /sys/class/scsi_host/host0/../../../clkscale_enable with 1
04-24 18:22:09.077 560 625 E ANDR-PERF-OPTSHANDLER: return value 2
04-24 18:22:09.541 11826 12327 D powrite-send: echo '/storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso' >/sys/class/android_usb/android0/f_mass_storage/lun/file
04-24 18:22:09.743 11826 12327 D powrite-send: cat /sys/class/android_usb/android0/f_mass_storage/lun/file
04-24 18:22:09.945 11826 12327 D powrite-send: echo 1 >/sys/class/android_usb/android0/enable
04-24 18:22:10.123 5923 5923 W WindowManager: removeWindowToken: Attempted to remove non-existing token: [email protected]
04-24 18:22:10.146 6665 6665 D HeadsetPhoneState: Enter onSignalStrengthsChanged
04-24 18:22:10.146 11826 12327 I writeToSystem: All DONE! SUCCESS!
04-24 18:22:10.146 6665 6665 D HeadsetPhoneState: Exit onSignalStrengthsChanged
04-24 18:22:10.150 5923 6549 V UsbDeviceManager: USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=22690, ACTION=change, USB_STATE=DISCONNECTED, DEVPATH=/devices/virtual/android_usb/android0}
04-24 18:22:10.151 12189 12262 I NetworkController.MobileSignalController(1): showDisableIcon:false
04-24 18:22:10.238 5923 6549 V UsbDeviceManager: USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=22691, ACTION=change, USB_STATE=CONNECTED, DEVPATH=/devices/virtual/android_usb/android0}
04-24 18:22:10.240 5923 6359 D UsbDeviceManager: broadcasting Intent { act=android.hardware.usb.action.USB_STATE flg=0x31000000 (has extras) } extras: Bundle[{host_connected=false, connected=true, unlocked=false, config_changed=false, mtp=true, configured=false}]
04-24 18:22:10.263 7726 7726 W libc : Unable to set property "sys.usb.ffs.mtp.ready" to "1": error code: 0x18
04-24 18:22:10.264 5923 9743 I UsbDeviceManager: isUsbDataUnlocked: 0
04-24 18:22:10.310 5923 6549 V UsbDeviceManager: USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=22692, ACTION=change, USB_STATE=CONFIGURED, DEVPATH=/devices/virtual/android_usb/android0}
04-24 18:22:10.311 5923 6359 D UsbDeviceManager: broadcasting Intent { act=android.hardware.usb.action.USB_STATE flg=0x31000000 (has extras) } extras: Bundle[{host_connected=false, connected=true, unlocked=false, config_changed=false, mtp=true, configured=true}]
04-24 18:22:10.338 7726 7726 D MtpService: starting MTP server in MTP mode
04-24 18:22:10.534 5923 6524 D DebugKeepScreenOn: Releasing screen wakelock, obscured by Window{e3dd695 u0 systems.eddon.android.cdromswitcher/systems.eddon.android.cdromswitcher.MainActivity}
04-24 18:22:10.581 14627 14735 I PlayCommon: [373] com.google.android.play.b.h.e(263): Preparing logs for uploading
04-24 18:22:10.582 14627 14735 I PlayCommon: [373] com.google.android.play.b.h.e(267): No file ready to send
04-24 18:22:12.194 5923 6352 D RestartProcessManager: increase duration : 5090 for systems.eddon.android.cdromswitcher
04-24 18:22:12.196 560 560 E ANDR-PERF-MPCTL: hint lookup failed
04-24 18:22:12.196 5923 6352 D RestartProcessManager: Update Total Launch Times :pl.solidexplorer2
04-24 18:22:12.196 5923 6352 D RestartProcessManager: updateSelf : pl.solidexplorer2, size : 13
04-24 18:22:12.196 5923 6352 D RestartProcessManager: Increase Total Launch Time : pl.solidexplorer2, times : 14, index : 12
04-24 18:22:12.196 5923 6352 D RestartProcessManager: Last Running Package : pl.solidexplorer2 , start time 1524586932196

[Porting] CANNOT LINK EXECUTABLE < /system/bin/ file>: cannot locate symbol < ... >

[Porting] CANNOT LINK EXECUTABLE < /system/bin/ file>: cannot locate symbol < ... >
Hi.
I encountered a problem while trying to port AOSP Extended v. 4.1 (Android 7.1.2, kernel 3.10.65+, MTK 6753) on my device (VOYO Q101, 2GB/32GB, kernel 3.10.65+, MTK 6753).
After successfully started the booting process (after one week of research, and a stupid line in /system/build.prop: ro.setupwizard.enterprise_mode=1 which caused stucking at logo), I have managed to get a logcat via adb. LOG (it's 8MB)
It is booting.. and booting... forever. It is not stucked, nor bootlooping. It is just booting (the "Google dots" animations running forever).
I have attached the log. There are a lot of CANNOT LINK EXECUTABLE <....> cannot locate symbol < ... > referenced by <...> and also a lot of:
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Write 56 bytes to slot 0, CCCI_H(0x0)(0x38)(0x801D000F)(0x0)
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Read 128 bytes from FS device
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Read 128 bytes from slot 0, CCCI_H(0x0)(0x80)(0x801E000E)(0x0)
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): CMPT File name:Z:/NVRAM/NVD_DATA/ULMH_000 opid_map:0x00000013 Flag:0x00000100 Offset:34 Whence:-229154332 Length:16384
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): O: [1010103F282D2C35](0x00000100): (7 1)
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): F: 1: 1906 0
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): C: 1: 0
[What I did]
- just copying the kernel from stock ROM (tried also: stock kernel + stock ueventd.rc +/- stock fstab): all caused bootloop or even stucked at logo. Just kernel change works good (at least till the actual stage) .
- compared with old .rc files. No replaces needed (in my opinion)
- From system/build.prop file I have DELETED all lines from ADDITIONAL_BUILD_PROPERTIES section (especially ro.setupwizard.enterprise_mode=1) - which took me 4 DAYS !!! to understand why it was stucked at logo .
- tried with and without patching with init.d (from porting ROM's website)
- tried to put the stock binaries mentioned in errors <CANNOT LINK ...> (/system/bin/mtk_agpsd, xlog) - not booting at all (it even stucks at logo...). Should I try with stock linker.so lib(64) ? But I think it will not boot at all (It really can't).
I hope for your help . Thanks!
up

Camera hal3 test app not working

Hi all,
hardware/qcom/camera/QCamera2/HAL3/test command line test app is not working. Please check below logs and give any suggestions.
CAF details.
LA.UM.7.6.2.r1-06900-89xx.0.xml
chipset - msm8953_64
I/ServiceManager( 3396): Waiting for service display.qservice...
( 3396): uid=0(root) ./hal3-test-app identical 2 lines
I/ServiceManager( 3396): Waiting for service display.qservice...
E/QCamera3HWI( 3396): getBinder: invalid binder object
I/QCamera ( 3396): <HAL><INFO> openCamera: 723: [KPI Perf]: X PROFILE_OPEN_CAMERA camera id 0, rc: 0
I/QCamera ( 3396): <HAL><INFO> initialize: 945: E :mCameraId = 0 mState = 1
I/QCamera ( 3396): <HAL><INFO> initialize: 978: X
Invalid gralloc handle (at 0xb019a708): ver(12/12) ints(4/25) fds(2/2) magic(----/gmsm)
/DisplayMetaData( 3396): validateAndMap: Private handle is invalid - handle:0xb019a708
/QCamera ( 3396): <HAL><ERROR> registerBuffer: 1140: Buffer 0xb01a72bc couldn't be registered -12
E/QCamera ( 3396): <HAL><ERROR> request: 3647: On-the-fly buffer registration failed -12
E/QCamera ( 3396): <HAL><ERROR> processCaptureRequest: 4739: Fail to request on picture channel
I/mm-camera( 844): <CPP >< INFO> 359: cpp_hardware_set_clock: Set clock 200000000 BW avg 235526384 BW inst
( 3396): Snapshot Process Capture Request Sent
Thanks,
pradeep
I have the same problem in msm8917(camera.msm8937.so), samsung device, but here the camera get a lot of time to open, you know the solution?
thanks for attention

Categories

Resources