Develop Bugs

I can't copy file from PPC to PC through Activesync

I can't copy files from PPC to PC through activesync. When I tried to copy, the conversion window of copying files popped up and it seems like its doing its job (converting and copying) and finished with no error. But when I go to the directory in my PC where the file copied to, there is nothing inside the directory. I've upgraded the activesync to version 4.1 (Build 4841) and still no luck. I tried from bluetooth and craddle connection and same result. However, I can successfully copy any file from my PC to PPC.
Does anyone had the same problem?

That's unusual.
I haven't had that problem myself, and it would be maddening if I did.
Tell me:
- Can you copy the other way around (PC to WM)?
- Is it every file, or certain types only?
- Can you try installing AS on another PC and trying the same process?

Same problem here, but with a S110. Various pc's and different version of AS tested. Some time ago it did work, but something triggered it to go wrong. Learning to live with it and copying stuff via sd-card.
Anyone a clue?

snorbaard said:
That's unusual.
I haven't had that problem myself, and it would be maddening if I did.
Tell me:
- Can you copy the other way around (PC to WM)?
- Is it every file, or certain types only?
- Can you try installing AS on another PC and trying the same process?
Click to expand...
Click to collapse
PC to WM5 works fine and it always successfully transfer the file for every type. The problem is only one way (WM to PC) through activesync.
I haven't tried to install AS on different PC yet. Will report after trial
Learning to live with it and copying stuff via sd-card.
Click to expand...
Click to collapse
In my case to upload file from WM to PC i use WiFi and connect through ftp to transfer data (Although it's inconvenient but it does the same job)
Thanks for the replies[/quote]

[Q] MIUI 1.11 & ES File Manager

I'm running MIUI XJ XPART (latest 1.11). Anyone else experiencing the following problem (it's present for last few versions, but now it's really making me mad ): using ES file manager, setting custom FTP/LAN servers and views - everything OK for some time, then opening it it reverts to default settings (view and all my FTP servers gone? ).
Could it be MIUI too agressive with RAM management or something else?

aloalotebetrazim said:
I'm running MIUI XJ XPART (latest 1.11). Anyone else experiencing the following problem (it's present for last few versions, but now it's really making me mad ): using ES file manager, setting custom FTP/LAN servers and views - everything OK for some time, then opening it it reverts to default settings (view and all my FTP servers gone? ).
Could it be MIUI too agressive with RAM management or something else?
Click to expand...
Click to collapse
if you are using FTP/LAN to transfer files from pc to mobile device via WiFi, why dont you use the built in File Explorer FTP server option? correct me if i have not understood your question.

You've understood me well
But there are some cases when I can't use it (ie firewall issues, not the same LAN etc)... and I'm curious to find out why is that happening.
ES is the only program I've encountered problems with, and it seems like a fresh install when it occurs. I've tried using Astro, but I don't like it

aloalotebetrazim said:
You've understood me well
But there are some cases when I can't use it (ie firewall issues, not the same LAN etc)... and I'm curious to find out why is that happening.
ES is the only program I've encountered problems with, and it seems like a fresh install when it occurs. I've tried using Astro, but I don't like it
Click to expand...
Click to collapse
may be you can address it in "http://forum.xda-developers.com/showthread.php?p=19434249" along with the logcat which might have some info on the issue hopefully . i believe there is app available to get the log file.
below is the command to get the log using adb from command prompt by connecting your device to the pc. you should have android-sdk.
prompt> adb logcat > log1.txt

[Q] Couldn't capture screenshot. Storage may be in use.

Verizon Galaxy Nexus.
I was running 4.0.4 IMM30B leak. The new leak/possible update came out, I decided to flash it. Saw that it was only good for updating from 4.0.2 (ICL53F), so I wiped, formatted, and reinstalled it. Re set up my phone (titanium backup, homescreens, android market updates for a few apps, the basics). Everything seemed fine, though I didn't try saving anything. Ran the update to the new 4.0.4, and everything seemed fine and dandy.
The next day, titanium backup runs (scheduled) and fails. Says not enough storage or something despite the fact that it also shows ~14GB free space...
Tried to take a screenshot of the issue, and I get a notification that it "Couldn't capture screenshot." "Couldn't save screenshot. Storage may be in use."
Curious, I tried to take a picture with the system camera app, and it doesn't seem to save pictures either. Though no error messages tell me such things.
Caching seems to work, updating apps seems to work, using 'most' apps seems to work, but saving data to the virtual SDcard has no such luck.
Assuming that it's a permissions issue, I went into CWM Recovery and did a 'fix permissions.' Though that has not fixed anything.
Various searches have shown me that others have experienced this problem, but I haven't seen anyone with a solution. Also, they seem to be experiencing it in various AOKP roms (specifically for the Transformer tablet).
Question: Anyone know what I can do to fix it?

Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium

msedek said:
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Glad to hear that there is a fix. I may end up doing this tonight... I'm hoping that a quicker, simpler fix is available (something like boot an insecure.img and change permissions of these folders via adb, or something).
Thanks for that though, as I now know that it should work.

Happening on GSM Galaxy Nexus as well. I tried a rom over milestone 5, then reinstalled milestone 5 and restored my backup, and then got this problem. Seems sdcard is not writable to at all. Gonna try out the bootloader locking stuff i guess.

I ended up using the Galaxy Nexus Toolkit (for time and automated simplicity) to wipe the device, reflash 4.0.2 (signed by Google), reroot, CWM reccovery, and restore the virtual sdcard backup saved with the toolkit.
Once the virtual sd was restored, I restored my apps (but no system apps) with titanium backup. Haven't had the time since to reupgrade to 4.0.4, but 4.0.2 seems to be working for me nicely.
I am able to screenshot, and nice things like that, but sometimes titanium backup is giving me errors about not being able to save due to insufficient space (still 14GB free). Gonna dive into that issue today.

4.0.2 works good.. What its bad about it its the lag, the ROM its laggy and also the battery life and the photo quality.. ICS now its much better than 4.0.2
Sent from my Galaxy Nexus using xda premium

No fix?
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.

Redscorpian said:
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Click to expand...
Click to collapse
Dat gravedig.
Just try reflashing your device from a stock image.

Beauenheim said:
Dat gravedig.
Just try reflashing your device from a stock image.
Click to expand...
Click to collapse
And do you think that'll be leaving it as it is?

I fixed this deleting the "pictures" folder with RootExplorer.

jwiegand said:
I fixed this deleting the "pictures" folder with RootExplorer.
Click to expand...
Click to collapse
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!

bergmanman said:
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
Click to expand...
Click to collapse
I'm on a different phone, but I fixed this issue by clearing the defaults for the program that launched pictures. In my case, I use Gallery, so in Program Info under Settings, I reset defaults and everything worked fine. I guess this is the same thing as deleting the Pictures folder since I believe it is an issue of 'releasing' the memory that remains in use by your respective program. For all future requests as to which program should be used to launch a file (or picture in this case), I never select the option that binds future requests to one specific program. Hope that helps .

My fix: re enable the media scanner!
Like many others, I have disabled the DRM and media scanner services because of the bug that caused ridiculous cpu usage (particularly on boot). Re enabling the media scanner fixed this problem right up. If you want a free and easy utility to do this, check out: "Rescan Media ROOT"
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
Disclaimer: I am not associated with the author of that app.

On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I tried all the previous solutions without success, but manually creating the Pictures/Screenshots folder worked flawlessly on my LG 4X.
Thanks TulsaDavid!

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thanks alot! Worked for me!!

Thanks, TulsaDavid!
Making screenshots folder solved it for me aswell.

Unable to take Screenshot, USB storage maybe in use
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I have tried using home+power button, turned on swipe and had difficulty in using the S PEN to make the screenshot - still doesnt work.
I also tried making a new folder but still doesnt work.
My unit is Samsung Note 8.0

/sdcard permissions broken
Just had this happen on my Nexus 5.
The cause was using adb push to copy files to /sdcard when I was booted into recovery. All the files and folders were owned by root:root. I had to reboot to recovery, adb shell, and then
Code:
chown -R media_rw:media_rw /data/media/0
It might be possible to do this while booted in android with Connectbot or something, but I didn't try that.

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thank you TulsaDavid. This helped me tremendously. You're a deity!
Sent from my SGH-T989 using Tapatalk

Help with endless nested /0/0/0/0 folders

Hi. I just switched from 1 custom 4.3 rom to a different one and i did a factory reset. However once i rebooted, i noticed that all my internal SD content had gone into 0/0/0/0 etc. i kept clicking but eventually file explorer on widows just froze.
I went into ES file explorer on my phone and saw the content was behind 400 0's!!!!
Anyone have any idea what i could do to recover that info? every time i try copying the files ES explorer either crashes or says that it had copied the files when it hadnt.
Any help would be greatly apreciated. I'm at my wits end... :crying:
Thanks

Bro you need to use a file explorer from recovery. TWRP custom recovery has a built-in file explorer. That should do the trick
Sent from my SGH-T999 using Tapatalk

aussie88 said:
Hi. I just switched from 1 custom 4.3 rom to a different one and i did a factory reset. However once i rebooted, i noticed that all my internal SD content had gone into 0/0/0/0 etc. i kept clicking but eventually file explorer on widows just froze.
I went into ES file explorer on my phone and saw the content was behind 400 0's!!!!
Anyone have any idea what i could do to recover that info? every time i try copying the files ES explorer either crashes or says that it had copied the files when it hadnt.
Any help would be greatly apreciated. I'm at my wits end... :crying:
Thanks
Click to expand...
Click to collapse
Also, you should update your recovery as the more recent versions have fixed that problem. It doesn't happen each time you flash with the new versions.

fingolfin14 said:
Also, you should update your recovery as the more recent versions have fixed that problem. It doesn't happen each time you flash with the new versions.
Click to expand...
Click to collapse
Yep I figured that out the hard way lol. Already upgraded to the latest version of CWM to prevent it from happening anymore. Now to get the files out from down there... :banghead:
Sent from my SGH-T999 using xda app-developers app

On Windoz, You could troll and copy out every 10 deep or 20 deep back to surface and then continue. That'd be better than crashing Explorer.
Dos Prompt is more rugged. You could write a batch script there.

Perseus71 said:
On Windoz, You could troll and copy out every 10 deep or 20 deep back to surface and then continue. That'd be better than crashing Explorer.
Dos Prompt is more rugged. You could write a batch script there.
Click to expand...
Click to collapse
I saw that somewhere and tried that. Doesnt seem to be having any effect. Unless im doing it wrong...
I'm plugging my phone into my computer, accessing the phone section when it comes up, going about 20 0s deep and copying it back to the root. It either crashes my windows explorer, or doesnt seem to be doing anything(i think because its already disconnected itself. i tried making a new folder and it wouldn't let). what am i doing wrong?
PS. how would i access my phones internal SD from DOS?
thanks

Try ADB FileExplorer that should not time out on Windows. I have also tried Android File Manager with success. If that does not work, I will look up other options.

Well i tried android file manager. Im not 100% sure exactly how these programs work, but either way its saying i dont have root access. I do and i also have chainfires adbd insecure app which should give me full root access, but its still not working.
I looked at ADB FileExplorer too, but i didnt really get it and it kept saying it couldnt find my phone and something about an incorrect path.

With the Android File Manager, when it accesses the Phone over ADB, it will ask for Root once. If you don't click SuperSU warning in that time, the File Manager will give this error. Please read its thread carefully. I have connected over ADBWIRELESS and this just fine.

Perseus71 said:
With the Android File Manager, when it accesses the Phone over ADB, it will ask for Root once. If you don't click SuperSU warning in that time, the File Manager will give this error. Please read its thread carefully. I have connected over ADBWIRELESS and this just fine.
Click to expand...
Click to collapse
It never asked for root on my phone. I've tried all the changes and everything else that people have recommended, but im still not having any luck. I guess im too much of a noob for all this lol :crying:

Try Re-mounting internal SD in Recovery and then connect to PC.

nope, still no luck. Its still saying no root and no supersu request is coming up. I guess im missing something....
EDIT: I seem to somehow be "losing" root every time i try to connect to the android file manager. i open an app that requires root and it says i dont have root. I have to reboot my phone to get root to work again. It's weird though, because SuperSU opens fine...

open the last "zero" folder on your computer, drag everything into a folder on your computer desktop, let everything copy (do something else in the mean time), delete your phone memory, copy everything back to your cleared phone memory card

Lieu10ant said:
open the last "zero" folder on your computer, drag everything into a folder on your computer desktop, let everything copy (do something else in the mean time), delete your phone memory, copy everything back to your cleared phone memory card
Click to expand...
Click to collapse
If only it was that easy. its behind 400 nested folders. Windows cant go that deep. it freezes and FC's after about 200.
Im giving my phone in to get my power button repaired, so i guess ill ask the software tech there if he can figure it out. But thank you Perseus for all your help last night. :good:

I also have this problem guys, how do i update my custom recovery please?

[Q] Unable to connect to PC properly after rooting

Hello,
I have had my HTC One M8 for a while now but I wasn't really happy with the soundquality while playing through my headphones, so I looked for ways to improve it. I found a few methods and finally decided to give it a try. These methods require a root so yesterday I have rooted my phone for the first time. Unfortunately I am experiencing some problems now.
The rooting process went without too much trouble. I used hasoon2000's toolkit and have TWRP version 2.7.0.2 installed as recovery and used it to install the provided SuperSU, which didn't work at first. On the forums I found a newer version and installed that one, updated it and got it to work.
Now this is where I think I messed up: I read somewhere that when rooted, you are able to delete pre-installed apps from the phone. I downloaded SD maid and deleted Kid Mode, Zoe and 7digital. When I deleted Kid Mode I got an error saying it has crashed. I tapped away the error but from this point I couldn't go back to my homescreen anymore because my launcher kept crashing (com.htc.launcher crashed). I rebooted the phone and the launcher worked again, but the phone still seemed to be buggy.
After this I tried to install the snapdragon audio+ (this was my first choice for an equalizer). I downloaded the apk and moved it to the system folder using ES file manager. I installed but when I tried to use it (through settings in google play music app) my phone would crash. I uninstalled it and tried again, but when I tried to move the apk to the system map like before, my phone would crash everytime. I then found out the file I used doesn't work for lollipop so I figured that's what caused the crashes.
My next move was to try and install viper4android. I downloaded it from the Play Store and opened it. It told me it needed an installation of BusyBox so I downloaded that too. But when I opened the BusyBox app and clicked install my phone would crash again. After some searching I found that the HTC One M8 requires BusyBox to be flashed manually so I downloaded the file but when I tried to load it onto my phone I noticed this wasn't possible anymore.
Now when I connect my phone to my PC the PC recognizes it, but when I open the map in Windows Explorer it only shows three maps; .showme, _nero_sync and Ringtones. I know there should be more as they were there before. It also shows my phone's capacity as a total of 10GB (shouldn't this be 16GB?). Also when I try to connect it with Sync Manager it gives me an error everytime I reconnect the phone; Device unavailable. Please reconnect your device [4].
I have tried to reset the phone through settings, wipe with TWRP and fix permissions with TWRP. I also tried reinstalling Sync Manager and the drivers on my PC. What I'm thinking now is I maybe have done something wrong in the ES file explorer that would make the folders unaccessible.
My phone is running stock android 5.0.1 and my PC Windows 7 64-bit.
I hope someone can help me, Thanks.
P.S: Sorry for the long post, I figured I'd give as much info as possible.

@Steef076 First update recovery to the latest one (2.8.6.0)
Second if you go and delete vital or integrated parts of the stock rom you will get a lot of bugs. Third, viper4android requires to write system and you can't write system with the stock kernel, you need an unsecured kernel or unsecure it yourself.
10GB is right since 6 is eaten by android. At this point I would just revert to a backup or install any custom rom around here. Most are close to stock and with no bloatware and come with root. You can even clean them further using a tool called ROM Cleaner. It will most likely solve all your problems

Did the deleted system apps reappear after reboot, or do they remain "uninstalled"? If the system is write protected like TempestZ states, any deleted system apps should reappear after a reboot.
Revert your nandroid to restore the system apps. And you didn't make a nandroid, you really should before making any system modifications for the very reason that it allows you to revert if you run into problems.
Another good practice, is if you don't know what effect deleting a system app will have (such as "safe to delete" lists that can sometimes be found on XDA) you should first freeze the app with Titanium Backup. If freezing doesn't cause any issues, then go ahead and delete. If you do have issues, just unfreeze the app.
Steef076 said:
Now when I connect my phone to my PC the PC recognizes it, but when I open the map in Windows Explorer it only shows three maps; .showme, _nero_sync and Ringtones. I know there should be more as they were there before. It also shows my phone's capacity as a total of 10GB (shouldn't this be 16GB?). Also when I try to connect it with Sync Manager it gives me an error everytime I reconnect the phone; Device unavailable. Please reconnect your device [4].
Click to expand...
Click to collapse
No, Windows will never show 16 GB. It only shows "internal storage" partition, or the user accessible portion of the storage. A good chunk is reserved for the OS.
Does what is shown in Windows differ from what is shown in ES if you browse to internal storage?

Thanks for the replies. @TempestZ @redpoint73
First of all I managed to update twrp to 2.8.6.0 using adb/fastboot.
To answer your question @redpoint73 the system apps I had deleted indeed reappeared after reboot. Also I didn't make a nandroid before I deleted the files, as I did not even know this was possible. Now I have made a nandroid of my stock ROM that is working decently, except for the TV app keeps crashing (I'm not opening it) and the connection to the PC is not working properly (not sure if this is ROM based?). I have noticed when the phone is in recovery I CAN see the folders through windows explorer. HTC sync manager still doesn't find it though. I am working on finding a proper stock ROM or maybe flash a custom one to see if that will fix it.
I understand now that the OS is taking up the storage space. The space windows is showing is the same as ES file manager so I guess this is fine.

HTC Sync is a hot mess. It often causes more troubles than it solves.
One thing you can try (to see if it fixes the USB connectivity) is uninstall HTC Sync and all HTC drivers. Than connect the phone. Don't let it install HTC Sync. Go to Windows Device Manager, find the device. Then pick the option to manually select the drivers, and pick the generic "Android MTP device" (or something to that effect) drivers.
This doesn't work for everyone. But it worked for me to be able to "see" the internal storage of my M8 on my home PC (Win 7). Annoyingly, it seems to vary from one PC to another. My work laptop (also Win 7) works fine with HTC Sync.

Steef076 said:
So if I understand correctly, 'version-main' is the same as 'firmware' and 'software number' (found in settings)? If so, my current firmware seems to be 4.19.114.2.
Now, what you're saying is I should do an OTA but this isn't possible because I have a custom recovery right?
Also, when I want to flash stock rom and stock recovery or do a nand don't I need the files that fit my cidnum? How would your file work for me?
Click to expand...
Click to collapse
If yours already on 4.19.114.2 then no need to do OTA as that the latest.
and my backup will bring back your device back to stock as you first bought it when restore with a full wipe.
Try to solve your problem first, only when you really need the backup then only I will upload ... let me know

ckpv5 said:
If yours already on 4.19.114.2 then no need to do OTA as that the latest.
and my backup will bring back your device back to stock as you first bought it when restore with a full wipe.
Try to solve your problem first, only when you really need the backup then only I will upload ... let me know
Click to expand...
Click to collapse
Hello, sorry for the late reply.
I have decided to give a custom ROM a try. I now have ARHD 41.0 installed and it seems this took care of my problems. All the maps are showing in windows explorer and HTC sync manager is connecting properly with my phone again. Also no more crashing apps. Your backup would still be of much use for me as I am not sure I want to stick with a custom ROM and therefore would like to have a stock ROM backup.
Thanks in advance.