Hello guys, I have a little problem with developing apps in my phone.
I installed Stock Android 4.1.2 v4 for my Xperia U ST25i ( http://forum.xda-developers.com/showthread.php?t=2284394 ) (I wanted to post this issue in this thread but i'm new here and I just can't... anyways, rules are rules), and i'm have some issues when I want test APK's in my phone via ADB or Eclipse-ADT.
When I click excecute ( or do adb install), the process will fail, showing me that:
Code:
[2013-07-23 16:40:48 - AWifiSignal] ------------------------------
[2013-07-23 16:40:48 - AWifiSignal] Android Launch!
[2013-07-23 16:40:48 - AWifiSignal] adb is running normally.
[2013-07-23 16:40:48 - AWifiSignal] Performing net.elsemieni.awifisignal.SplashActivity activity launch
[2013-07-23 16:40:48 - AWifiSignal] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2013-07-23 16:40:51 - AWifiSignal] WARNING: Unknown device API version!
[2013-07-23 16:40:51 - AWifiSignal] Uploading AWifiSignal.apk onto device 'YT9002B59S'
[2013-07-23 16:40:52 - AWifiSignal] Installing AWifiSignal.apk...
[2013-07-23 16:40:53 - AWifiSignal] Installation failed due to invalid APK file!
[2013-07-23 16:40:53 - AWifiSignal] Please check logcat output for more details.
[2013-07-23 16:40:53 - AWifiSignal] Launch canceled!
In simple words, doesn't install beacuse [INSTALL_FAILED_INVALID_APK] error code.
Of course, i have Debugging activated in my phone and install 3rd party applications.
By the way, Logcat gives me that
Code:
07-21 18:05:23.663: W/zipro(25492): Unable to open zip '/data/local/tmp/AWifiSignal.apk': Permission denied
07-21 18:05:23.673: W/PackageParser(25492): Unable to read AndroidManifest.xml of /data/local/tmp/AWifiSignal.apk
That's curious I can't write inside it. I searched the forums and I applied a workaroud solution (http://forum.xda-developers.com/showthread.php?p=40040546&postcount=4), to make a link from tmp to sdcard folder. It worked in this way, but ruined the phone sys after reboot ( crashes randomly, most critical app's frezzes, etc), so doesn't work.
I know that's a firmware bug, but... any ideas about this? There's another workaround to make tmp safely writable, or any way to change the folder who ADB uses to install apps remotely?
Thanks! :laugh:
Related
Ok, so i recently started programig in Eclipse and i have this error when i try to launch it on my phone:
PHP:
Android Launch!
adb is running normally.
Performing com.guzi.cuantofalta.MainActivity activity launch
Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
Uploading CuántoFalta.apk onto device 'S7500ef722d08'
Installing CuántoFalta.apk...
Installation failed due to invalid APK file!
Please check logcat output for more details.
Launch canceled!
I have been searching to fix this error but i couldnt find any.
I did a search and have found similar threads. However, people seem to have been intelligent and back up stuff or installed recovery apps before screwing around with their phones. I did not.
I have a Samsung Note3. Kit Kat 4.4.2 installed OTA once I had it up and running. I rooted it. However, the version of Kit-kat has a famous issue in that it would not allow apps to write to the SD card. I found a site with manual instructions to edit the platform.xml to overcome this issue. The site is as below:
winaero.com/blog/unlock-external-sd-card-writing-for-all-apps-in-android-4-4-kitkat/
However, something went awry after rebooting. I could not see anything on my SD card and I was unable to edit the platform.xml. A solution seemed to be to flash the ROM (using ODIN 3.07). I did this and currently have Baseband version N9005XXUENB1 and Build Number KOT49H.N9005XXUENB7
However, the still has lots of issues. I can stick in a password on wifi and connect to the network but it does not actually communicate with the internet. The H with up and down arrows appears for 3g connectivitiy but also does not work. Bluetooth does not work. Youtube has stopped working errors are common. I am unable to install any apps as cannot use play store, etc. I have pictures and mp3s on my SD card but gallery comes up empty as does music app. The only "file explorer" I seem to have is "my files" app. It comes up as empty (although it shows Total storage available for both SD memory and device storage as using 25/32 and 22/29 respectively.
I am guessing that flashing the ROM did not remedy the corrupt platform.xml in the permissions folder. I think the folder path was etc/permission/platform.xml although am not an expert with android. I was hoping someone might be able to give me a solution to fix the issue. Preferably a completely fresh and clean wipe type solution. Although as I am a "newbie" the greater the simplicity of the solution the better.
Apologies for the length of this issue!
T
laconical said:
I did a search and have found similar threads. However, people seem to have been intelligent and back up stuff or installed recovery apps before screwing around with their phones. I did not.
I have a Samsung Note3. Kit Kat 4.4.2 installed OTA once I had it up and running. I rooted it. However, the version of Kit-kat has a famous issue in that it would not allow apps to write to the SD card. I found a site with manual instructions to edit the platform.xml to overcome this issue. The site is as below:
winaero.com/blog/unlock-external-sd-card-writing-for-all-apps-in-android-4-4-kitkat/
However, something went awry after rebooting. I could not see anything on my SD card and I was unable to edit the platform.xml. A solution seemed to be to flash the ROM (using ODIN 3.07). I did this and currently have Baseband version N9005XXUENB1 and Build Number KOT49H.N9005XXUENB7
However, the still has lots of issues. I can stick in a password on wifi and connect to the network but it does not actually communicate with the internet. The H with up and down arrows appears for 3g connectivitiy but also does not work. Bluetooth does not work. Youtube has stopped working errors are common. I am unable to install any apps as cannot use play store, etc. I have pictures and mp3s on my SD card but gallery comes up empty as does music app. The only "file explorer" I seem to have is "my files" app. It comes up as empty (although it shows Total storage available for both SD memory and device storage as using 25/32 and 22/29 respectively.
I am guessing that flashing the ROM did not remedy the corrupt platform.xml in the permissions folder. I think the folder path was etc/permission/platform.xml although am not an expert with android. I was hoping someone might be able to give me a solution to fix the issue. Preferably a completely fresh and clean wipe type solution. Although as I am a "newbie" the greater the simplicity of the solution the better.
Apologies for the length of this issue!
T
Click to expand...
Click to collapse
Sounds like a bit of a pickle. Since you know that Odin is working and the firmware you have at least flashes correctly, I'd consider installing a custom recovery, backing up EFS folder (and the rom too, just in case there is some weird issue with Odin the 2nd time around) , then wipe everything - /system included. This will make your phone not be able to boot up at all because it will wipe the OS off. Then just boot directly to Download and redo the firmware flash. Something else to consider since you do have the international version, is that some of the firmwares you install might be more carrier or region specific, so there might be a better option to install. I know that there is a some slightly newer version that has NC2 in it as I was trying to fix one of these phones the other day that could not register on any network and ran across that build. Do you remember the build number of the software before you started modding?
Hello. Thanks for the reply.
I am going to ask what are probably very obvious questions but I am a little out of my depth.
1) What does installing a custom recovery involve?
2)How would I backup the EFS directory? When I had ES file explorer I would have been able to try and find it. However, as it is I do not know how to find the directory and back it up. I have connected the phone to a windows laptop and it shows up as note3 but there are no folders or files visible in either the phone or on the card.
3) What is the procedure to "wipe everything"?
I think the final part I know how to do with ODIN. Just go to download boot and load and run odin with the ROM.
I got the BTU ROM is that not for the UK? I tried looking up what NC2 was but did not really find anything the explained what it is.
Thanks again and sorry for the ignorance on my side.
Let's put the custom recovery and all that on the back burner for now.
Was your phone unlocked from the factory or did you get it from a carrier? If from a carrier, which, and is it unlocked now or you are still using it with the original carrier? This one is for Vodaphone http://www.sammobile.com/firmwares/3/?download=27401 but if you are unlocked, it should work anyway, I believe.
Thanks to the people for their replies. I managed to solve the issue as below.
As mentioned previously I had flashed using ODIN and BTU version of N9005XXUENB7. The only other thing that was then required was to enter the recovery (I think power + volume up + home and then release power once samsung name appears). I then selected wipe data/factory. A reboot later and everything was solved.
es0tericcha0s said:
Sounds like a bit of a pickle. Since you know that Odin is working and the firmware you have at least flashes correctly, I'd consider installing a custom recovery, backing up EFS folder (and the rom too, just in case there is some weird issue with Odin the 2nd time around) , then wipe everything - /system included. This will make your phone not be able to boot up at all because it will wipe the OS off. Then just boot directly to Download and redo the firmware flash. Something else to consider since you do have the international version, is that some of the firmwares you install might be more carrier or region specific, so there might be a better option to install. I know that there is a some slightly newer version that has NC2 in it as I was trying to fix one of these phones the other day that could not register on any network and ran across that build. Do you remember the build number of the software before you started modding?
Click to expand...
Click to collapse
Hi, The other day i tried to fix the Platform.xml. on my S5. i noticed sometime after that when i move files using the "My files" app, the phone would not refresh the files so that they would show up in gallery, videos etc.. I tried to undo the Media_rw by using SD Maid to find the Platform.xml and Axel to rewrite the Xml. In the platform.xml. i deleted the Media_rw and replaced the old xml with the old (original) one. I rebooted my phone. On swiping to open the screen i noticed alot of apps crashing one after the other. I when back to SD Maid and searched for Platform.xml and opened it with Axel but it said file not found.. i can not use the internet, i cant use most apps, i cant even use the Kies on my computer. I cant save anything to the storage either. I really need help. Odin is the only thing i can use. but i dont know how i can reset the xml files on my phone.. What exactly am i do to?
please
christaph3r said:
Hi, The other day i tried to fix the Platform.xml. on my S5. i noticed sometime after that when i move files using the "My files" app, the phone would not refresh the files so that they would show up in gallery, videos etc.. I tried to undo the Media_rw by using SD Maid to find the Platform.xml and Axel to rewrite the Xml. In the platform.xml. i deleted the Media_rw and replaced the old xml with the old (original) one. I rebooted my phone. On swiping to open the screen i noticed alot of apps crashing one after the other. I when back to SD Maid and searched for Platform.xml and opened it with Axel but it said file not found.. i can not use the internet, i cant use most apps, i cant even use the Kies on my computer. I cant save anything to the storage either. I really need help. Odin is the only thing i can use. but i dont know how i can reset the xml files on my phone.. What exactly am i do to?
please
Click to expand...
Click to collapse
Hey, I was wondering if you ever got a fix on this without factory reset. I am having the exact same issue.
Same boat here. Please someone help!
woahs said:
Hey, I was wondering if you ever got a fix on this without factory reset. I am having the exact same issue.
Click to expand...
Click to collapse
I am having exact same problem. After editing the platform.xml, my Note 3 is behaving the same way: no access to any storage area (including USB drive), no remote access/online access (even though WIFI and 4G appear to connect just fine), most apps fail with 'Unfortunately ... has stopped' error message, no Google Play...
I really don't want to do a factory reset, but really, does it even help? Is there a way to put the platform.xml back? Is there a way to access the phone via USB cable?
vbcomer said:
I am having exact same problem. After editing the platform.xml, my Note 3 is behaving the same way: no access to any storage area (including USB drive), no remote access/online access (even though WIFI and 4G appear to connect just fine), most apps fail with 'Unfortunately ... has stopped' error message, no Google Play...
I really don't want to do a factory reset, but really, does it even help? Is there a way to put the platform.xml back? Is there a way to access the phone via USB cable?
Click to expand...
Click to collapse
Update: I went ahead and successfully install the all-in-one file to the phone via Odin, but it still has the same issues. Can someone give a hint? thanks
FIX!!!
Hi I'm a god at searching(hence the Go)but an Noob(hence the obie) to Dev on Android but a computer techy(in other words I fix computers upgrade ETC.) Now if you followed EXACT instructions you SHOULD have the Backup copy of platform.xml. If not reply and I'll give those instructions.
So I did the same as this post did to get my issue as well but there's a SOLUTION I just found W/o getting rid of your loved files and its easy!
1. Download the ADB also included in The Android SDK by Google (approx. 3XX MB)
2. DOWNLOAD Root Explorer.APK
3. Extract ADB Dev kit( name should be roughly adt-bundle-windows-x86_64-20140702.zip)Note: I prefered it at C:\Android it avoided Name too long error
4. Open CMD Type: cd C:\<location ADB was extracted>\sdk\platform-tools(if you followed my note it will be "C:\Android\adt-bundle-windows-x86_64-20140702\sdk\platform-tools") and press enter... HINT TO COPY PASTE IN CMD RIGHT CLICK SAVES TIME!!!!
5. Install Root Explorer so you can backup your files(if any) I was unlucky having none on the phone but SD storage is ok!
To do this type ADB INSTALL <Location of Root explorer.exe> For standard windows users with default download locations it would be "C:\Users\<USER NAME>\Downloads\Root Explorer v3.1.9.apk" <COPY PASTE
6. Copy the original back to System>ETC>Permissions and overwrite
7. Factory reset!
Links?
sorry guys bt i have the same note 3 and i delete the platform.xml file .....i did a factory reset bt nothing happened ...can u help plz
Re:FIX!
But you have to set the permissions of platform.xml as 0777.Right?
Step 5 how should it works
Android Goobie said:
Hi I'm a god at searching(hence the Go)but an Noob(hence the obie) to Dev on Android but a computer techy(in other words I fix computers upgrade ETC.) Now if you followed EXACT instructions you SHOULD have the Backup copy of platform.xml. If not reply and I'll give those instructions.
So I did the same as this post did to get my issue as well but there's a SOLUTION I just found W/o getting rid of your loved files and its easy!
1. Download the ADB also included in The Android SDK by Google (approx. 3XX MB)
2. DOWNLOAD Root Explorer.APK
3. Extract ADB Dev kit( name should be roughly adt-bundle-windows-x86_64-20140702.zip)Note: I prefered it at C:\Android it avoided Name too long error
4. Open CMD Type: cd C:\<location ADB was extracted>\sdk\platform-tools(if you followed my note it will be "C:\Android\adt-bundle-windows-x86_64-20140702\sdk\platform-tools") and press enter... HINT TO COPY PASTE IN CMD RIGHT CLICK SAVES TIME!!!!
5. Install Root Explorer so you can backup your files(if any) I was unlucky having none on the phone but SD storage is ok!
To do this type ADB INSTALL <Location of Root explorer.exe> For standard windows users with default download locations it would be "C:\Users\<USER NAME>\Downloads\Root Explorer v3.1.9.apk" <COPY PASTE
6. Copy the original back to System>ETC>Permissions and overwrite
7. Factory reset!
Links?
Click to expand...
Click to collapse
Hi have next message in the install root step could you help me please
Android Debug Bridge version 1.0.31
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode) adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the followin
g format:
<serial> " " <local> " " <remote> "\n" adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only) adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-d] [-s] [--algo <algorithm name> --key <hex-encoded ke
y> --iv <hex-encoded iv>] <file>
- push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-d' means allow version code downgrade)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all]
[-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.) adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1 [parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
ABOUT THE GALAXY ALPHA CM-12.1 PROJECT
I'm working on getting CyanogenMod working on the Galaxy Alpha since October 2014. This ROM is not complete. There are still features which are not fully working and there are for sure things which need bugfixing. Please check the Known Bugs section before reporting issues.
I work on this project for FREE and putting in a lot of hours into it. A small donation would help to buy better tools to improve the development some day.
RECOVERY
To be able to install the ROM you need a recovery. I suggest to use my TWRP Recovery build. You can find it here.
BACKUP
Before installing the ROM you should create backups. The most important backup is to create one of the EFS partition and store it on safe place on your computer. If something goes wrong you need to restore this partition. It holds information about your device, like the MAC address for your wifi and information for the radio.
DOWNLOAD
You are storing very sensitive information on your phone. You always have to be careful what ROMs you flash and whom you trust. If you don't trust me then don't use my ROM or compile it from source by yourself.
The ROM will be gpg signed with my key 0xCC014E3D. You can verify the ROM with 'gpg --verify cm-12.1-20150901-UNOFFICIAL-slte-beta1.zip.asc '.
Detailed information and instruction for Windows can be found here.
Download BETA
FLASHING THE ROM
As this is a Lollipop (Android 5) based ROM you need to flash sboot (bootloader) and the modem image from one of the latest LL releases. Or install a LL ROM via the Samsung update option. You can find the latest stock ROM here. Suggested modem version is: G850FXXU2COI3 or newer
I suggest to put the ROM on a USB disk and use a USB OTG cable to flash the ROM. It is also possible to put it on the emulated sdcard and flash it from there.
GAPPS
I suggest to use Open GAPPS.
REPORTING BUGS
Give the programmer some credit for basic intelligence: if the program really
didn't work at all, they would probably have noticed. Since they haven't
noticed, it must be working for them. Therefore, either you are doing something
differently from them, or your environment is different from theirs. They need
information; providing this information is the purpose of a bug report. More
information is almost always better than less.
Click to expand...
Click to collapse
Before reporting bugs, please check the KNOWN BUGS list below and read THIS HOWTO
XDA:DevDB Information
[ROM][SM-G850F] CM-12.1 UNOFFICIAL ROM, ROM for the Samsung Galaxy Alpha
Contributors
modpunk, raymanfx, bonuzzz, kyasu
Source Code: https://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP/CWM Recovery
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 8
Beta Release Date: 2015-10-22
Created 2015-09-01
Last Updated 2015-10-26
KNOWN ISSUES
RIL: SMS broadcast subscriptions aren't working (generic failure)
MEDIA: HEVC videos don't work
INCALL: Some SLTE devices need 10-30 seconds to wake the screen on an incoming call
VOIP: Not tested (could someone please test)
CHANGELOG
2015-10-22 + BETA8
audio: Should be completely working now
ril: Fixed network operator search
2015-10-15 - BETA7
audio: More fixes to get audio fully working
audio: Fixed voice recording (camcorder should work fine now)
audio: Fixed media playback (especially over bluetooth)
camera: Fixed remaining camera issues (using LL blobs now)
Kernel: Smaller kernel image using XZ compression now
Kernel: Updated arizona sound driver
2015-10-10 - BETA6
More fixes to the audio HAL
Improved PowerHAL (VSYNC and LOW_POWER) support
This version includes the latest Security fixes for Android, see the Android Patchlevel in Settings -> About Phone.
2015-10-07 - BETA5
Fixed audio calls (wideband)
Fixed audio calls with bluetooth headset and carkit
Fixed audio recordings
This version includes the latest Security fixes for Android, details see here.
2015-10-02 - BETA4
Fixed bluetooth call playback (mics are not working yet)
Fixed two mic control in audio HAL
Fixed firmware loading on wisol devices
New sensor HAL
Improved boot time
2015-09-17 - BETA3
Added bluetooth headset support
Added support for noise suppression
Better sound quality on wideband connections
2015-09-03 - BETA2
Fixed flashing issue with TWRP
Set addtitional build information
2015-09-01 - BETA1
Initial release
FREQUENTLY ASKED QUESTIONS
"It doesn't work."
Give the programmer some credit for basic intelligence: if the program really didn't work at all, they would probably have noticed. Since they haven't noticed, it must be working for them. Therefore, either you are doing something differently from them, or your environment is different from theirs. They need information; providing this information is the purpose of a bug report. More information is almost always better than less.
Please read How to Report Bugs Effectively
My modem doesn't work, what can I do?
Did you flash the latest MODEM firmware from the latest Lollipop release? The suggested firmware is at least G850FXXU2COI3 or newer
How do I use adb/logcat go get logs from my device
You can find a good tutorial here.
I have problem with flashing. I tried with suggested TWRP. Flashing rom takes 1 second and ends with successful information
Edit. "Unable to mount /system" twrp error
miszko77 said:
I have problem with flashing. I tried with suggested TWRP. Flashing rom takes 1 second and ends with successful information
Edit. "Unable to mount /system" twrp error
Click to expand...
Click to collapse
Which TWRP version are you using?
Awesome work man. Honestly I can't flash this right now, just because, I need a fully functioning device daily so, I'll be patient
modpunk said:
Which TWRP version are you using?
Click to expand...
Click to collapse
I am using 2870. Anyway I flashed recovery with odin. May this be a problem?
miszko77 said:
I have problem with flashing. I tried with suggested TWRP. Flashing rom takes 1 second and ends with successful information
Edit. "Unable to mount /system" twrp error
Click to expand...
Click to collapse
I have same problem
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
miszko77 said:
I am using 2870. Anyway I flashed recovery with odin. May this be a problem?
Click to expand...
Click to collapse
I am using 2.8.7 also
lukrangelu said:
I have same problem
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
I am using 2.8.7 also
Click to expand...
Click to collapse
Could you connect with 'adb shell' to the recovery and run 'getenforce'. Then get me the log and avc_msg file with:
adb pull /tmp/recovery.log
adb pull /proc/avc_msg
and paste the file somewhere ...
modpunk said:
Could you connect with 'adb shell' to the recovery and run 'getenforce'. Then get me the log and avc_msg file with:
adb pull /tmp/recovery.log
adb pull /proc/avc_msg
and paste the file somewhere ...
Click to expand...
Click to collapse
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the following format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --iv <hex-encoded iv>] <file>
- push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
('--algo', '--key', and '--iv' mean the file is encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
would it be this?
Blubberor said:
Thanks a lot modpunk,
initial bug after doing wipe incl. Cache, dalv.cache and using same minimal gapps that works in kyasus cm12.1
I dont have network setting up, sim card not detected and cannot manually activate it.
Again thank you for your work,
blubberor
Click to expand...
Click to collapse
Read the bug report section in the initial post, provide logcat for system/main and also radio. This is a beta version you should at least know the basics how to get information from the device ...
lukrangelu said:
would it be this?
Click to expand...
Click to collapse
Not even close. If you want to run a beta version you should learn at least the basics for using adb.
ADB/LOGCAT HOWTO
Here you are.
getenforce
Permissive
Click to expand...
Click to collapse
miszko77 said:
Here you are.
Click to expand...
Click to collapse
The recovery reports:
Code:
You have an installed system that isn't signed with this build's key, aborting...
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
This is a pretty obvious message to me. You need to wipe system and data in order to install the ROM.
modpunk said:
You need to wipe system and data in order to install the ROM.
Click to expand...
Click to collapse
Result of wiping caches, data and system. See attachment.
I did factory reset and getting the same information.
miszko77 said:
Result of wiping caches, data and system. See attachment.
I did factory reset and getting the same information.
Click to expand...
Click to collapse
I've wiped my system partition and running into the same problem as you know. I'm investigating it now ...
modpunk said:
Read the bug report section in the initial post, provide logcat for system/main and also radio. This is a beta version you should at least know the basics how to get information from the device ...
Click to expand...
Click to collapse
Mfg
Blubberor said:
Mfg
Click to expand...
Click to collapse
Please pull /proc/avc_msg ...
modpunk said:
Please pull /proc/avc_msg ...
Click to expand...
Click to collapse
and here you go.
Thanks a lot. crossing fingers that the avc_msg.log helps you with fixing.
Tschö,
blubberor
i have created python script for copy all third party apps installed in your device and copy all the apps in your pc.
NON-ROOT script.
script uses adb shell commands for copy and reinstall apps in your device so no need of root access.
for now i only manage to test it on X00TD(Android 9.0) for now. Update me for other device/android versions.
Steps for backup apps :-
1) Download python 3 from python.org and install it in your pc.
2) Download python script files from the link below.
3) Run "windows-backup.py" if you are on Windows OS, else "linux-backup.py" for linux based OS.
Steps for reinstall apps:-
*first 2 steps are same
3) Run "install-apps.py" for install apps OS dosent effect on this script.
YouTube :- www . youtube . com / watch?v=EEoPo7Hqt3k
File Download link :- bit.ly / 2Lhqe0T (remove spaces).
I'm getting error.
Zenfone max pro m1
Android: 8.1 (stock, No root, bootloader unlocked, TWRP recovery)
PC: Windows 8.1
USB debugging enabled, USB mounted as storage
ERROR msg in screenshot
foxonfox said:
I'm getting error.
Zenfone max pro m1
Android: 8.1 (stock, No root, bootloader unlocked, TWRP recovery)
PC: Windows 8.1
USB debugging enabled, USB mounted as storage
ERROR msg in screenshot
Click to expand...
Click to collapse
Install adb in your pc first
Can you tell me why I'm getting this error?
[email protected]:~/Documents/App backup-restore$ python3 linux-backup.py
Folder Created
Fetching Packages list from device
error: no devices/emulators found
Packages are fethced
Copying Started
Total 1 Apps
b'
1 : .apk
/bin/sh: 1: Syntax error: Unterminated quoted string
Traceback (most recent call last):
File "linux-backup.py", line 47, in <module>
os.rename("base.apk",name)
FileNotFoundError: [Errno 2] No such file or directory: 'base.apk' -> '.apk'
[email protected]:~/Documents/App backup-restore$
What's wrong or what am i doing wrong?
OS 9 MSM Extended with MicroG installed (No Google)
EDIT:
got it after enabling USB DeBugging
Hey guys.
On my old SM-J730G device, some ROMs did not have the confirmation dialog for ADB certificates. This prevented me from connecting to the shell, getting logcat output, etc.
To resolve, I needed to copy the certificate to the device, install a root file manager, and copy the file to / data / misc / adb / adb_keys.
Well, I developed an application that helps in this process. Your requirements are only to have the device rooted and to have copied the adbkey.pub file to the device. The app will assist in the implementation of the same.
Download: https://play.google.com/store/apps/details?id=com.gobrito.adb_keys
Screenshots on Play Store page
Created with Flutter
NOTE: if you are in the wrong area, I ask you to move the topic to the correct area, and sorry for the inconvenience, this is my first topic.