Database Users

[Q] Mission Impossible: How to let a2sd working?

Hi everybody,
I have spent several hours to try letting a2sd working and it still seems to be impossible.
I'm running the last version of CyanogenMod with the dark tremor patch installed.
I've partitioned the sd card using gparted, now I've a partition of 1024 gb ext 3 (I've tried also with different size and different file systems (2,3,4)), I've also tried with another sd card (2 gb), but nothing.
I'm always getting the same error when I try run check with a2sd:
# a2sd check
[ ] GREP: Using ROM Busybox.
[!] REBOOT: Using Darktremor Busybox.
[ ] FDISK: Using ROM Busybox.
[ ] CAT: Using ROM Busybox.
[ ] MKDIR: Using ROM Busybox.
[ ] RMDIR: Using ROM Busybox.
[ ] CHMOD: Using ROM Busybox.
[ ] MOUNT: Using ROM Busybox.
[ ] UMOUNT: Using ROM Busybox.
[ ] CP: Using ROM Busybox.
[ ] RM: Using ROM Busybox.
[ ] MV: Using ROM Busybox.
[ ] LN: Using ROM Busybox.
[ ] MORE: Using ROM Busybox.
[ ] MKNOD: Using ROM Busybox.
[ ] AWK: Using ROM Busybox.
[ ] SLEEP: Using ROM Busybox.
[ ] SYNC: Using ROM Busybox.
[ ] TEE: Using ROM Busybox.
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30)
[-] Checkpoint 1: Check for SD Card Fix and Implement.
[-] Checkpoint 2: Run Dalvik Heap Program (if exists).
[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).
[-] Checkpoint 4: Determine Mount Point.
[-] Checkpoint 5: Set Parameter Variables.
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /sd-ext
[-] Checkpoint 6: Insert CyanogenMod patch.
[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).
[-] Checkpoint 8: Resetting Dalvik Cache Partition
[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)
[-] Checkpoint 10: Checking for existence of command parameter
[-] Checkpoint 11: Check for a2sd help command
[-] Checkpoint 12: Check for a2sd check command
[ ] Starting Apps2SD Check Program.
Darktremor 2.7.5.3 Beta 4a Apps2SD Status Report
===================================================================================
Legend: [✔]=Setting is correct
[‼]=Setting is correct, but not optimal.
[✖]=Setting is incorrect and needs to be fixed or option is not available.
===================================================================================
Block Device - [✖] Not Found
- [✖] SD card cannot mount
Obviously if I run a2sd reinstall does not work.
Does anyone have any solution?
Thank you very much
Does anyone have any solutions?

Which version are you using.
Also have you tried any other SDcard as i am using CM7 N 89 with A2SD with no issues.
First try another SDCard if this fails see if you can mount the SDCard via the phone.
If you can't give me a PM and i will try and help you out the best i can.
Just noticed you said you use gparted. If you have a custom recovery use that to partition your SDCard.
Save the data first from the SDCard that is important reboot into Recovery mode then select advance if you have Version 3.x.x.x there will be partition SD card there!!!!!!!!

You can either try s2e from the market...it will make job easy..also you could try rom manager for partitions ....
Sent from my HTC Wildfire

I'm using the last one as you: CM7 89.
I've tried with 2 different sdcard and I always get the same problem when I run "a2sd check".
The phone see the sd card correctly but the application are not installed.
Are there maybe any app to check the ext partition?
Did u install the darktremor patch as I did?
Maybe if u give me your procedure I could understand where is the problem.
Thank you.
P.S.: It's normal that gps is not working on this rom?
-Giulio

Right this is how i did it.
Booted into recovery.
Did a Wipe all (Using 3.1.0.2 Recovery)
Did a Advance Partition SD
Then Took out the SDcard and put on 89 rom and a2sd flash files on.
Then Flashed 89 rom then a2sd and rebooted the phone.
i then in terminal typed the following.
SU and then accepted root access
the a2sd install then a2sd cachesd then a2sd datasd. each after each reboot.

giulio1212 said:
P.S.: It's normal that gps is not working on this rom?
-Giulio
Click to expand...
Click to collapse
GPS Works. Reflash the radio if it doesn't. Tested on #87

I've tried to install ClockworkMod 3.1.0.2 (this version)
with unrevoked3 but it doesn't work... Unrevoked just get stuck at some point while rebooting... :/
Any ideas?

All radio's unfortunately need CWM 2.x to be flashed. You can get this by installing CWM from within the ROM Manager Application.
As for installing CWM 3.1.0.2, use an old version of Unrevoked (3.14 or 3.20), they work. You should be able to find a few links by looking around a bit.

I currently have ClockWorkMod 2.5.0.7.... I'm now trying to upgraded it to be able to create the right partition of the SD....
I did not found this versions of Unrevoked for Mac OSX .... do u have it?
Thank you

Found it.... and it works.... now I've the CWM 3.1.0.2... I will try to create the sd partition as Hacktrix explained

Bad news....
I did has hacktrix explain me but still won't works
here is what I get from the shell:
# su
# a2sd install
[ ] GREP: Using ROM Busybox.
[!] REBOOT: Using Darktremor Busybox.
[ ] FDISK: Using ROM Busybox.
[ ] CAT: Using ROM Busybox.
[ ] MKDIR: Using ROM Busybox.
[ ] RMDIR: Using ROM Busybox.
[ ] CHMOD: Using ROM Busybox.
[ ] MOUNT: Using ROM Busybox.
[ ] UMOUNT: Using ROM Busybox.
[ ] CP: Using ROM Busybox.
[ ] RM: Using ROM Busybox.
[ ] MV: Using ROM Busybox.
[ ] LN: Using ROM Busybox.
[ ] MORE: Using ROM Busybox.
[ ] MKNOD: Using ROM Busybox.
[ ] AWK: Using ROM Busybox.
[ ] SLEEP: Using ROM Busybox.
[ ] SYNC: Using ROM Busybox.
[ ] TEE: Using ROM Busybox.
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30)
[-] Checkpoint 1: Check for SD Card Fix and Implement.
[-] Checkpoint 2: Run Dalvik Heap Program (if exists).
[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).
[-] Checkpoint 4: Determine Mount Point.
[-] Checkpoint 5: Set Parameter Variables.
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /sd-ext
[-] Checkpoint 6: Insert CyanogenMod patch.
[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).
[-] Checkpoint 8: Resetting Dalvik Cache Partition
[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)
[-] Checkpoint 10: Checking for existence of command parameter
[-] Checkpoint 11: Check for a2sd help command
[-] Checkpoint 12: Check for a2sd check command
[-] Checkpoint 13: Display version information.
[ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 4a
[-] Checkpoint 14: Check for filesystem support.
[-] Checkpoint 15: Mount partition.
[-] Checkpoint 16: Reset Dalvik if Flag File is present.
[-] Checkpoint 17: Mount Swap.
[-] Checkpoint 18: Display Heap Size.
[ ] Heap Size set to: 24m
[-] Checkpoint 19: Check for start parameter and launch start2sd if needed.
[ ] Launching Apps2SD Start Program with install
[ ] Starting Darktremor Apps2SD in install mode
[X] SD Card not mounted.
Cannot reinstall applications to SD card.
#
I just did it like this (same stuff with two different SDCard):
1.Installed the new CWM 3.1.0.2 with unrevoked.
2.Did a WIPE All
3.Create the partition form advance->partition SD->1024mb->swap 0mb
4.Installed CM7 N89
5.Installed Darktremor Apps2SD 2.7.5.3 Beta 4a
6.Restart the phone
7.Wait
8.Run with adb "a2sd install"
9.Unsucess
Does anyone knows which is the problem... Is driving me crazy, it's really frustrating :/

I think I've done it... but I did it only with an old 2gb microSD card...
I would like to use my 32gb microSD card....
After I've created the partition I tried to mount it inside CWM:
-With 2gb card no problem, it mounts.
-With 32gb card it gives me: error mounting/
Do you know why?
Here a screenshot of my card:
{
"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"
}
Any idea on how to create a working partition with this card?

That card might be a fake! if it works on the 2GB version and i have a 16GB sdcard to which it works on that 32gb must be a fake. I can't even find a class 8 card where did you get it from ?

I ordered on ebay, in effect I paid few $$.... but, yeah I can assure you that I fill it with 32gb....
At the end I decided to use app2sd from android, that seems to work without problems on CM7 (when I've tried on CM6 sometimes app disappeared ).

[Q] Darktremor Apps2SD Supported for HTC Wildfire 2.2.1 Stock ROM?

I have a rooted HTC Wildfire with stock ROM 2.2.1,
I have the following rooting tools installed:
+ ROM Manager 4.3
+ Clockworkmod Recovery 5.0.2
+ Root Toolbox
+ Busybox 1.19
+ Terminal Emulator
I also got a 8 GB SDcard, partitioned with CWM as follows:
+ 1024 MB as Ext3
+ 64 MB SWAP
+ Rest as FAT32
I tried to install Darktremor Apps2SD 2.7.5.3 Beta 04 but it never started and whenever I start the phone.
Here's an output result after executing commands:
>> su
$ a2sd reinstall
Code:
[ ] GREP: Using ROM Busybox.
[ ] REBOOT: Using ROM Busybox.
[ ] FDISK: Using ROM Busybox.
[ ] CAT: Using ROM Busybox.
[ ] MKDIR: Using ROM Busybox.
[ ] RMDIR: Using ROM Busybox.
[ ] CHMOD: Using ROM Busybox.
[ ] MOUNT: Using ROM Busybox.
[ ] UMOUNT: Using ROM Busybox.
[ ] CP: Using ROM Busybox.
[ ] RM: Using ROM Busybox.
[ ] MV: Using ROM Busybox.
[ ] LN: Using ROM Busybox.
[ ] MORE: Using ROM Busybox.
[ ] MKNOD: Using ROM Busybox.
[ ] AWK: Using ROM Busybox.
[ ] SLEEP: Using ROM Busybox.
[ ] SYNC: Using ROM Busybox.
[ ] TEE: Using ROM Busybox.
grep: /init.rc: Permission denied
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30)
[-] Checkpoint 1: Check for SD Card Fix and Implement.
[-] Checkpoint 2: Run Dalvik Heap Program (if exists).
[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).
[-] Checkpoint 4: Determine Mount Point.
[-] Checkpoint 5: Set Parameter Variables.
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /system/sd
[-] Checkpoint 6: Insert CyanogenMod patch.
[ ] Creating /cache/dc
mkdir: can't create directory '/cache/dc': Permission denied
chmod: /cache/dc: Permission denied
[ ] Symlinking /cache/dalvik-cache to /data/dalvik-cache
rm: can't stat '/cache/dalvik-cache': Permission denied
ln: /cache/dalvik-cache: Permission denied
[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).
[-] Checkpoint 8: Resetting Dalvik Cache Partition
[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)
[-] Checkpoint 10: Checking for existence of command parameter
[-] Checkpoint 11: Check for a2sd help command
[-] Checkpoint 12: Check for a2sd check command
[-] Checkpoint 13: Display version information.
[ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 4a
[-] Checkpoint 14: Check for filesystem support.
[-] Checkpoint 15: Mount partition.
[-] Checkpoint 16: Reset Dalvik if Flag File is present.
[-] Checkpoint 17: Mount Swap.
[-] Checkpoint 18: Display Heap Size.
[ ] Heap Size set to:
[-] Checkpoint 19: Check for start parameter and launch start2sd if needed.
[ ] Launching Apps2SD Start Program with reinstall
[X] Problem detected: Darktremor Apps2SD may not have ran
during boot. Cannot read a2sd.mountpoint.
[ ] Starting Darktremor Apps2SD in reinstall mode
[X] SD Card not mounted.
Cannot reinstall applications to SD card.
As shown, errors are:
[X] Problem detected: Darktremor Apps2SD may not have ran
during boot. Cannot read a2sd.mountpoint.
[X] SD Card not mounted.
I wonder whether Darktremor Apps2SD officially supports stock ROM for HTC Wildfire 2.2.1 or not.
Any alternatives for this method if not supported?

Nobody ever successfully moved all apps to Ext3 partition for rooted Wildfire with stock Android 2.2.1?

A ROM must support Apps2SD to enable you to use it. You can cook your own ROM with the Stock as base, and just Apps2SD enabled using the DSIXDA Kitchen.

dude google if your current rom support ext3. the log shows problem with mounting sd. if it does not, u should partition it to ext2( kinda old, but have 2. if you want 2 stay with stock. if you plan to be a cm7 fan you can even use ext4 in latest nightly). reformatt sd. reflash rom, then install a2sd.
hey i had successed in moving app to sd using dta2sd. i even moved data to sd. check my thread " deal with a2sd ".
Sent from my HTC Wildfire using XDA App

Backup TA tool for Linux

Hi !
I'm porting the TA Backup script to Linux. It advanced pretty well so backup works, but not restore for today.
I wanted to write this post on the developpement forum, but it seems I can't with less than 10 posts…
You can get my work on Github : github.com/Salamandar/Backup-TA-Linux.
Salamandar aka Félix

Top stuff! I had a look through you scripts and they're looking pretty good! A lot easier to read through than the Windows BAT files.

Thanks
I'd like to say that it'd work for OSX too, but i'm not exactly sure. I'll test it when i can.
I just updated the script, it now checks for script files. (all but busybox)
I'll add some options as help.
If you mant some other features, don't hesitate to ask. If you want some other scripts (bash for android), just ask, I'll do it if i can.

I run OSX. I'm happy to look over your scripts and test them out as best I can.

I think that expecting 'adb' to be in a particular place is not the best idea.
I have 'adb' installed, but not in "/opt/android-sdk/platform-tools/". So I modified the ADB="..." line in the script to be
Code:
ADB=`which adb`
Although this requires adb to be installed somewhere in your $PATH. A possible enhancement might be to use `which adb` with a fall-back to asking the user where adb is installed.
---------- Post added at 09:35 PM ---------- Previous post was at 09:27 PM ----------
Hmmm....
I ran the script and got the following output:
Code:
viking$ ../Backup-TA.sh
[ ------------------------------------------------------------ ]
[ Backup TA vL1.0 for Sony Xperia MIT License ]
[ ------------------------------------------------------------ ]
[ Copyright (C) 2013 DevShaft ]
[ ]
[ Permission is hereby granted, free of charge, ]
[ to any person obtaining a copy of this software ]
[ and associated documentation files (the "Software"), ]
[ to deal in the Software without restriction, ]
[ including without limitation the rights to use, ]
[ copy, modify, merge, publish, distribute, sublicense, ]
[ and/or sell copies of the Software, and to permit ]
[ persons to whom the Software is furnished to do so, ]
[ subject to the following conditions: ]
[ ]
[ The above copyright notice and this permission notice ]
[ shall be included in all copies or substantial portions ]
[ of the Software. ]
[ ]
[ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY ]
[ KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE ]
[ WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR ]
[ PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS ]
[ OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR ]
[ OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR ]
[ OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE ]
[ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ]
[ ------------------------------------------------------------ ]
Press any key to continue…
[Lots of empty lines]
[ ------------------------------------------------------------ ]
[ Backup TA vL1.0 for Sony Xperia MIT License ]
[ ------------------------------------------------------------ ]
[ Initialization ]
[ ]
[ Make sure that you have USB Debugging enabled, you do ]
[ allow your computer ADB access by accepting its RSA key ]
[ (only needed for Android 4.2.2 or higher) and grant this ]
[ ADB process root permissions through superuser. ]
[ ------------------------------------------------------------ ]
Starting adb and waiting for phone in USB Debugging Mode…
OK
Pushing Backup TA Tools… OK !
Checking for SU binary… OK : Su found at /system/xbin/su
Requesting root permissions… OK : Got Root permissions.
[Lots of empty lines]
[ ------------------------------------------------------------ ]
[ Backup TA vL1.0 for Sony Xperia MIT License ]
[ ------------------------------------------------------------ ]
[ Choose an option : ]
[ 1) Backup ]
[ 2) Restore ]
[ 3) Restore dry-run - nothing will be written on partition ]
[ 4) Convert TA.img to backup ]
[ 5) Quit ]
[ ------------------------------------------------------------ ]
scripts/utils.sh: line 37: read: 0.1: invalid timeout specification
=======================================
BACKUP
=======================================
When you continue Backup TA will perform a backup of the TA partition.
First it will look for the TA partition by its name. When it can not
be found this way it will ask you to perform an extensive search.
The extensive search will inspect many of the partitions on your device,
in the hope to find it and continue with the backup process.
scripts/utils.sh: line 37: read: 0.1: invalid timeout specification
Are you sure? [y/N] y
=======================================
Searchin TA Partition…
Partition not found by name.
scripts/utils.sh: line 37: read: 0.1: invalid timeout specification
Do you want to perform an extensive search for the TA ? [y/N] y
=======================================
Inspecting Partitions…
--- mmcblk0p1 ---
\e[KThis is a compatible TA Partition !figuration…
--- mmcblk0p2 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p3 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p4 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p5 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p6 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p7 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p8 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p9 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p10 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p11 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p12 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p13 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p14 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p15 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p18 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p19 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p20 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p21 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p22 ---
\e[KThis is not a TA Partition.entifier…
Partition found : /dev/block/mmcblk0p1
An unknown error was caught : partition is not set. Aborting…
=======================================
Backup unsuccessful
Cleaning working directory…
Removing files from Android…
Killing ADB Daemon… OK, exiting now !
If you're using ANSI colour sequences, don't. Colour is all well and good, but (as in my case) may not be totally compatible across platforms.
Now, the backup may have failed because my poor phone has had a "rough life" (Stock Sony ROM -> CM10.2 -> FreeXperia -> Stock Sony ROM) and I may have "lost" my TA partition somewhere along the line. Let me restore the backup I made and see what happens.

This is getting very strange. I've restored the original TA backup, rebooted the phone and compared the md5sum output from the original TA backup, the /dev/block/mmcblk0p1 device and the TA backup I took an hour or so ago. They all have different MD5 values. I thought that they should all be the same - after all, they are supposed to be same data.
Code:
aec2542181f6d5c0a21c1563897c9a93 ./TA-backup-2014-05-21.img
347632d7f2761996798acd7f1acc38fc ./TA-backup-2014-09-26.img
63cabee22106f26d25a34d2664ee1695 /dev/block/mmcblk0p1
When I reboot my phone after restoring the TA image, it puts up a "NFC Firmware Update in progress" message. Which is strange - as I'm not doing anything crazy to the NFC, and I'm putting the TA image back to where I got it from.
Any ideas from anyone?

There's a logging area in the TA partition, so the contents and therefore the md5 can vary.
Sent from my C6603 using Tapatalk

I never knew that. It certainly explains why the MD5s were different. Thanks for clearing that up.

Thanks a lot for sharing this work! =)
Will give a shot with my next Xperia as i already lost my TA x)

if [[ "x" == "x$partition" ]]; then
Thank's alot for the scrips, well done.
I had to make a minor fix to get it to work on my setup. The script backup.sh checks for an empty string, but that check failes for some reason (D5803_23.0.A.2.93_Nordic_1288-5411, Linux Mint 17.1 Rebecca, adb version 1.0.31).
The trick was to change
Code:
if [[ ! -z $partition ]]; then
to
Code:
if [[ "x" == "x$partition" ]]; then
I'm not saying anyone should do the same, or that the fix is any good, but I got the script running without indicating any errors and producing some kind of file.
I'm writing this just in case anyone else would have the same problem, and this might provide a clue on how to proceed. And of course to say thank you.
Cheers!

Coming back soon
Hi !
I must admit I changed my phone (OnePlus One) so i didn't work a lot on this script lately (but I found some bugs :s )
I'll work on it next week probably to finish it properly
More infos to come
Salamandar

New structure
Hi everybody,
I rewrote a big part of my script tonight. In fact all the complexity/difficulty/errors i encoutered was due to the adb communication.
So now, I simply copy a big part of the script on the phone, then call it from the computer. That means simpler code and probably an executable script from your phone's terminal if you can't use adb.
I think i'll have finished all of that by friday
The problem here is that I don't have an XPeria anymore to test this so… if someone feels like a beta-tester, just tell me (promise i'll do a safe-beta )

Backup is OP, the rest will follow
Hi !
This took me some more time than hoped, thanks to the sh*t that is adb…
Backup is OP with the new script structure. And way more stable and readable than the old structure.
I let aside the "partition detection" stuff, I don't know if it's useful. Let me know if you get the message "Partition not found by name. Extensive search is not available yet." and we'll see to add some model-specific stuff.
Hiya everybody !
Salamandar

thanks!
Just got a Z3c so will try out soon. Always good to see linux tools (and not just windows!)
Salamandar3500 said:
Hi everybody,
I rewrote a big part of my script tonight. In fact all the complexity/difficulty/errors i encoutered was due to the adb communication.
So now, I simply copy a big part of the script on the phone, then call it from the computer. That means simpler code and probably an executable script from your phone's terminal if you can't use adb.
I think i'll have finished all of that by friday
The problem here is that I don't have an XPeria anymore to test this so… if someone feels like a beta-tester, just tell me (promise i'll do a safe-beta )
Click to expand...
Click to collapse

[SOLVED][Q] Commands not properly executing

EDIT:
The problem was that i was trying to read a line from the inputreader, when there was no line, so it was waiting for a response there...
Hello,
I am currently building an app to fix a little problem that exists on some devices with the wifi-mac and bluetooth addresses constantly changing (for me it's a N4 but I read somewhere that there are other devices with that problem too)
The thing the app should do is (steps taken from another xda thread: http://forum.xda-developers.com/showpost.php?p=43164157&postcount=1 )
- Mount /persist
- create the folders wifi and bluetooth
- create a text file in each of these directories containing the addresses that should be used in future
- fix the owners and permissions of these files and directories
- execute /system/bin/conn_init as su
The app is mostly done but somehow not working at all.
Everything from generating random adresses to saving them in a temporary file seems to work fine, but as soon as I try to mount the persist directory, the app stops to react.
At first, this was the first thing done by the SU Shell class that I wrote for executing su shell commands, so I thought that might be not working, but when I let that execute echo test it returns test just fine...
The code that is used could be expressed like that (this is missing some debug info and strings that get passed, but it should technically have the same result):
Code:
try {
shell = Runtime.getRuntime().exec("su");
outputStream = new DataOutputStream(shell.getOutputStream());
inputStream = new BufferedReader(new InputStreamReader(shell.getInputStream()));
outputStream.writeBytes("mount /dev/block/mmcblk0p20 /persist");
outputStream.flush();
} catch (IOException e) {
e.printStackTrace();
}
The attached zip file contains my main activity and the before mentioned su shell.
The complete source code of the app is available via my git server: http://greensserver.redirectme.net/greenchris/WiFi-MAC-and-Bluetooth-Adress-Fix.git
Does anybody have an idea why this isn't working?
Greetings
GreenChris
Edit:
I forgot to add the logcat...
Code:
04-09 23:33:21.289 3903-3903/com.janchristiangruenhage.macfixer I/art﹕ Late-enabling -Xcheck:jni
04-09 23:33:21.791 3903-3949/com.janchristiangruenhage.macfixer D/OpenGLRenderer﹕ Render dirty regions requested: true
04-09 23:33:21.797 3903-3903/com.janchristiangruenhage.macfixer D/Atlas﹕ Validating map...
04-09 23:33:21.951 3903-3949/com.janchristiangruenhage.macfixer I/Adreno-EGL﹕ : QUALCOMM Build: 10/28/14, c33033c, Ia6306ec328
04-09 23:33:21.953 3903-3949/com.janchristiangruenhage.macfixer I/OpenGLRenderer﹕ Initialized EGL, version 1.4
04-09 23:33:21.985 3903-3949/com.janchristiangruenhage.macfixer D/OpenGLRenderer﹕ Enabling debug mode 0
04-09 23:33:22.318 3903-3903/com.janchristiangruenhage.macfixer I/Timeline﹕ Timeline: Activity_idle id: [email protected] time:14543691
04-09 23:33:31.781 3903-3919/com.janchristiangruenhage.macfixer I/art﹕ Background sticky concurrent mark sweep GC freed 11333(680KB) AllocSpace objects, 3(44KB) LOS objects, 13% free, 4MB/5MB, paused 5.706ms total 39.550ms
04-09 23:33:31.843 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ address-bytes generated
04-09 23:33:43.923 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ save .bdaddr
04-09 23:33:43.925 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ address written: .bdaddr
04-09 23:33:43.954 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ su shell started
04-09 23:33:43.955 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ added outputstream
04-09 23:33:43.957 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ added inputstreamreader
04-09 23:33:43.957 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ echo test
04-09 23:33:43.973 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ test
04-09 23:33:43.974 3903-3903/com.janchristiangruenhage.macfixer D/macfixer﹕ mount /dev/block/mmcblk0p20 /persist

I cannot install any app because I've uninstalled system guard app [rooted device]

By running logcat while attempting to re-install the guard app (com.miui.guardprovider), I see the followin error (FYI I see this error when installing any app):
Code:
[ 01-21 03:49:18.090 1462: 2549 I/ActivityManager ]
START u0 {dat=file:///storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk cmp=com.google.android.packageinstaller/com.android.packageinstaller.InstallAppProgress (has extras)} from uid 10023 on display 0
[ 01-21 03:49:18.095 1462: 2549 D/ActivityTrigger ]
ActivityTrigger activityPauseTrigger
[ 01-21 03:49:18.098 3467: 3501 I/Finsky ]
[25] com.google.android.finsky.bo.an.run(6): Stats for Executor: NotificationAssistDatabaseManager [email protected][Running, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 6]
[ 01-21 03:49:18.106 1462: 2301 I/Timeline ]
Timeline: App_transition_ready time:1710168
[ 01-21 03:49:18.120 11313:11313 W/ResourceType ]
No package identifier when getting name for resource number 0x00000000
[ 01-21 03:49:18.124 1462: 2507 W/ResourceType ]
No package identifier when getting name for resource number 0x00000000
[ 01-21 03:49:18.125 1462: 2507 W/ ]
Unable to open '/storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk': Permission denied
[ 01-21 03:49:18.125 1462: 2507 W/zipro ]
Error opening archive /storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk: I/O Error
[ 01-21 03:49:18.125 1462: 2507 D/asset ]
failed to open Zip archive '/storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk'
[ 01-21 03:49:18.129 2724: 2724 W/ContextImpl ]
Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:788 android.content.ContextWrapper.sendBroadcast:411 android.content.ContextWrapper.sendBroadcast:411 com.miui.permcenter.install.PackageVerificationRecevier.ar:-1 com.miui.permcenter.install.PackageVerificationRecevier.onReceive:-1
[ 01-21 03:49:18.135 1462: 2332 W/ActivityManager ]
cann't getContentProviderImpl: guard, cpi is null.
[ 01-21 03:49:18.135 2724: 9453 E/ActivityThread ]
Failed to find provider info for guard
[ 01-21 03:49:18.135 2724: 9453 E/PackageVerifyedRecevier ]
parseApk
java.lang.IllegalArgumentException: Unknown URI content://guard
at android.content.ContentResolver.call(ContentResolver.java:1424)
at com.miui.permcenter.install.q.doInBackground(Unknown Source)
at com.miui.permcenter.install.q.doInBackground(Unknown Source)
at android.os.AsyncTask$2.call(AsyncTask.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
[ 01-21 03:49:18.135 2724: 9453 D/PackageVerifyedRecevier ]
verify package /storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk info: null
[ 01-21 03:49:18.135 2724: 9453 D/PackageVerifyedRecevier ]
verify package /storage/emulated/0/Root_Uninstaller_Backup/Bezpečnostní prvky MIUI_null.apk finish false
[ 01-21 03:49:18.136 1462: 2507 I/com.android.server.pm.PackageManagerServiceInjector ]
MIUILOG- INSTALL_FAILED_VERIFICATION_FAILURE uid: 10023 pkg : com.google.android.packageinstaller
[ 01-21 03:49:18.138 9998: 9998 D/PackageVerificationReceiver ]
PackageVerificationReceiver onReceive:Intent { act=com.miui.global.packageinstaller.action.verifypackage flg=0x10 cmp=com.miui.global.packageinstaller/.PackageVerificationReceiver }
Would it be possible to skip resolving the content://guard link? I've already tried to go to Settings -> System apps settings -> Security -> Security scan and unchecked the "Scan before installing" button, but the error is still the same :/
Any ideas how to fix this?
Btw, I've tried to post this to the development section, but I was rejected due to the fresh account, so that's why I'm writing here.

Dirty flash the ROM means just wipe catches and dalvic catches and flash ROM zip again.