I am having a strange problem. Last time I used this installer is when I tested the beta 2.0 installer + multirom combination (when I said that I had to use PA-GApss folder for the installer to recognize the .gapps-config file). That time I flashed it in a secondary Kitkat ROM. Now I am running SimpleAOSP-Lollipop only (primary).
Yesterday I noticed that I can't delete the PA-GApps folder & files. It seems to be related with permission errors, but the permissions & owner are the same as all the other folders! I tried multiple file managers, full wipe and clean install of another ROM, tried to delete it from terminal/adb (with root permissions), tried to chmod, nothing. My only option is to format the storage (haven't done that yet).
Has anyone else had this problem? Is it even related with PA-GApps installer?
-rw-rw---- root sdcard_r 420451139 2014-11-22 00:55 pa_gapps-stock-4.4.4-20141121-signed.zip -rw-rw---- root sdcard_r 27337 2014-12-09 20:58 pa_gapps_debug_info.tar.gz -rw-rw---- root sdcard_r 3174 2014-12-09 20:58 pa_gapps_log.txt
I second that. I was like 'wtf is going on?' So I tried flashing the factory image yet the problem persisted. Thanks for shading some light on this matter.PROBLEM: When you copy/create files/folders in the scdard while in TWRP, you can't delete them in android.
VERSION: MultiROM TWRP 18.104.22.168 (2014-11-15) (latest)
Can anyone else reproduce this bug? If so, we should notify the TWRP developers.
I was also completely puzzled. So, can anyone else reproduce that? When I find the time, I should check with other twrp versions too. Can anyone do it in non multirom or 22.214.171.124 versions?I second that. I was like 'wtf is going on?' So I tried flashing the factory image yet the problem persisted. Thanks for shading some light on this matter.
I was annoyed by the fact that the newly announced MTP feature wasn't working on our devices, and I managed to find a way to fix it. The necessary changes are due to the init.rc file.
This is the changed code:
# Always start adbd on userdebug and eng builds # In recovery, always run adbd as root. on property:ro.debuggable=1 write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 18D1 [B]write /sys/class/android_usb/android0/idProduct 4EE2[/B] [B]write /sys/class/android_usb/android0/functions mtp,adb[/B] #write /sys/class/android_usb/android0/enable 1 write /sys/class/android_usb/android0/iManufacturer $ro.product.manufacturer write /sys/class/android_usb/android0/iProduct $ro.product.model write /sys/class/android_usb/android0/iSerial $ro.serialno [B]write /sys/module/rmnet_usb/parameters/rmnet_data_init 1[/B] #start adbd setprop service.adb.root 1
Now MTP and adb are working correctly (YMMV). Tested on both Windows Pro 8.1. x64 and Xubuntu 14.04.
I have attached two modified files, a plain 2.8.10 twrp and a multirom one. I zipped them because of XDA upload restrictions. Please test them and report back if it works for you.
DISCLAIMER! As always, it is not my fault if you obliterate your device! /DISCLAIMER!
I will try to contact the TWRP devs to find out how and where to do a proper pull request.
Is your fix taken to TWRP 126.96.36.199 on Nexus 4?
The 188.8.131.52 recovery has an incorrect (small) screen resolution so it's shown really small in the Nexus 4 screen...184.108.40.206 image is already available for download for Mako. What's the difference between 220.127.116.11 and 18.104.22.168?