Hello All,
I have a Nexus 6 (Hence the reason I'm posting in this thread) and I am not able to take screenshots after upgrading to Marshmallow 6.0. I would think to post in the thread of the current rom I'm running but I also full wiped and tried a different rom with the same result.
Every time I try and take a screen shot it says "Couldn't capture screenshot. - Can't take screenshot due to limited storage space, or it isn't allowed by the app or your organization." I would post a screenshot of what it's doing but... well... I think you get the point. I have plenty of storage space and I have dived into the various permissions settings on 6.0 but have yet to find out how to fix it.
Has anyone else had this problem across multiple roms and no luck with screenshots?
Currently running:
Chroma Oct-10-2015
Kernel:
3.10.40-Chroma-v1.01
Go to the screenshot directory and try to manually create any file there using your usual file manager/explorer.. If that fails,.it may be that the permissions are screwed which sometimes happens when you copy sdcard data back whilst in recovery.
If that sounds like your problem, there is a zip you can flash. Do NOT use "fix permissions" in recovery.
Flash this*zip*via recovery...
http://forum.xda-developers.com/attachment.php?attachmentid=2849968&d=1405300107
Located from thread: http://forum.xda-developers.com/showthread.php?t=2239421 by @osm0sis
danarama said:
Go to the screenshot directory and try to manually create any file there using your usual file manager/explorer.. If that fails,.it may be that the permissions are screwed which sometimes happens when you copy sdcard data back whilst in recovery.
If that sounds like your problem, there is a zip you can flash. Do NOT use "fix permissions" in recovery.
Flash this*zip*via recovery...
http://forum.xda-developers.com/attachment.php?attachmentid=2849968&d=1405300107
Located from thread: http://forum.xda-developers.com/showthread.php?t=2239421 by @osm0sis
Click to expand...
Click to collapse
There was a miscellaneous file on the /sdcard/pictures folder called screenshots. I couldn't access it and I couldn't create a new folder called screenshots
Es says operations failed
Sent from my Nexus 6 using Tapatalk
mkgarrod said:
There was a miscellaneous file on the /sdcard/pictures folder called screenshots. I couldn't access it and I couldn't create a new folder called screenshots
Es says operations failed
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Try this. Boot into TWRP select Advanced, File Manager go to /sdcard/pictures hit Select, chmod 755, confirm, reboot.
{
"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"
}
mkgarrod said:
There was a miscellaneous file on the /sdcard/pictures folder called screenshots. I couldn't access it and I couldn't create a new folder called screenshots
Es says operations failed
Click to expand...
Click to collapse
Witek_M said:
Try this. Boot into TWRP select Advanced, File Manager go to /sdcard/pictures hit Select, chmod 755, confirm, reboot.
Click to expand...
Click to collapse
Why are you still in ES? The problem isn't permissions, it's ownership. Use my zip as was suggested by @danarama.
The permissions zip worked,
As to why I was "still in ES?" I like to have an understanding of how everything works. May not be the quickest way to fix a problem, but it allows process of elimination on my side to see what specifically the issue is.
I appreciate the .zip and suggestions everyone! Thanks!
osm0sis said:
The problem isn't permissions, it's ownership. Use my zip as was suggested by @danarama.
Click to expand...
Click to collapse
@osm0sis, You are amazeballs!! Ran into this same inconvenience the last couple of days. Swyped a quick search, quite effortlessly arrrived here, where I can thank you for the fruits of your labour. And I do mean ALL of your work across XDA. I appreciate you much! ?
Take screenshot on your PC
Well, I think maybe you can try taking the screenshot of your Nexus 6 on computer. Just don't do it on the phone if it keeps failing. Android Manager can do this and save the picture on your PC.
is it working now?
You can try to rename pictures to pictures2 and reboot your phone, this was a quick solution on the oneplus one, if it works, but it's a dirty solution.
Related
okay, so i used Rom manager to back up my phone...now i flashed new rom and want to go back to my backup. But i cant do anything with Rom manager because i cant get it to flash the new recovery (servers are down or something). The restore files look like this inside the folder:
{
"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"
}
Is there any other app i can use to restore these to my phone?
Looks like the layout of a nandroid backup. Heres what I would try:
Extract that zip into a folder - name it whatever you want (ex Skittle)
Delete the recovery.img from that folder
Take that folder and put it into your nandroid folder on your phone's SDcard
**It'll look something like /sdcard/nandroid/SERIAL#HERE/skittle**
Reboot into recovery, select "Backup/Restore", "Nand Restore"
Select the Device-ID (serial#), then pick the Skittle folder to restore.
**Notice**
If you don't have a nandroid folder on your sdcard then just reboot into recovery and make a nandroid backup. It will create the nand/serial# folders for you. Then just throw the extracted zip into that directory.
kyouko said:
Looks like the layout of a nandroid backup. Heres what I would try:
Extract that zip into a folder - name it whatever you want (ex Skittle)
Delete the recovery.img from that folder
Take that folder and put it into your nandroid folder on your phone's SDcard
**It'll look something like /sdcard/nandroid/SERIAL#HERE/skittle**
Reboot into recovery, select "Backup/Restore", "Nand Restore"
Select the Device-ID (serial#), then pick the Skittle folder to restore.
**Notice**
If you don't have a nandroid folder on your sdcard then just reboot into recovery and make a nandroid backup. It will create the nand/serial# folders for you. Then just throw the extracted zip into that directory.
Click to expand...
Click to collapse
I did all of that and about 20 "."s into the restore i got an error: "Error : run 'nandroid-mobile.sh restore' via adb!"
Any ideas?
Thanks for helping, i messed my phone up and i go to work in 5 hours!
p.s. i just tried restoring the "dummy" backup i made, and it restored it successfully! Is my back up bad? Im so F*^#%@ if it is!
Hmm.. I know that error shows up for me when I tried doing a nand-restore with low'ish battery. Is it close to being fully charged?
Edit: ok, nvm. if the other one restored fine then you basically have two options for now:
1. Try doing the restore via command prompt/adb shell - which I can help you with
2. Waiting for rom manager (not sure what that is, never used it ) to start working
Do you have AndroidSDK and the tools (adb) installed on your computer?
kyouko said:
Hmm.. I know that error shows up for me when I tried doing a nand-restore with low'ish battery. Is it close to being fully charged?
Edit: ok, nvm. if the other one restored fine then you basically have two options for now:
1. Try doing the restore via command prompt/adb shell
2. Waiting for rom manager (not sure what that is, never used it ) to start working
Do you have AndroidSDK and the tools (adb) installed on your computer?
Click to expand...
Click to collapse
No i do not, never heard of it :/ Can you point me in the right direction please.
If you have a msn or anything, we can talk a little faster with messenger or something
You can download the Android SDK HERE
Extract the Android SDK zip to C:\
So it'll look like C:\android-sdk-windows\tools
and check your PMs - not the female kind
Hi, Can someone please dump/backup the system.img from baltic P500 or have a offical update for baltics. Thanks
Just do a backup and upload it. Thanks
No one here from Baltic States?
Hey, just show me how to do it, and I will give you.
hi, please use this guide: http://forum.xda-developers.com/showpost.php?p=8917870&postcount=12
or if you have Thunderg installed, then just do a backup and upload these files.
thanks
Hmm, could you be more specific? I just bought this Optimus One like two days ago, and I'm feeling very newb (it's my first Android).
What do I have to do, to give you that system.img and what is that system.img file?
Hi, the system.img a backup from Android /system partition is a main part of the android. But this guide we just dump that /system partition, it's the easiest way.
I'll try to help you do that:
1. Is your phone rooted?
If you haven't done that, then use Z4Root(super easy app ) and you can get it from here: http://www.upload.ee/files/997919/z4root.1.3.0.apk.html
Download that file and copy to sd card and install.
Open that installed app and root your phone
If you need help with that, then there is little how to here: http://www.worldofnubcraft.com/285/rooting-a-lg-optimus-one-android-phone
2. OK, rooting done, now we need terminal app: You'll find that from Market. Just search "Android Terminal Emulator" it's from Jack Palevich and install that.
3. Now open the Terminal Emulator and enter these commands without "" and hit enter after command, these 3 command should be it:
"su" it asks for a root privileges and you allow that
"cd /system"
"tar zcvf /sdcard/system-dump.tar.gz *" and wait when it finishes. it takes some time. It's done when you see #, it takes couple of minutes max.
4. That file is now on your phone SD card and upload that system-dump.tar.gz file to somewhere and let me know
Are you sure about that?
I'm sorry, but it's not working. It gives me an error "tar not found". Any ideas?
{
"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"
}
By the way, what you can do with that file? What it contains? I'm just a newb, and I want to know everything about Android.
EDIT:
Is it possible to do that dump with Thunderg?
Go to market and install app called "BusyBox" and download / install BusyBox with this tool. After that it will work.
yes, i forgot busybox install that and give a new try
Ok guys, I got it. Before putting it live, I would like to know one thing. Does it contains any personal data, if so, what exactly? Sorry, for being so paranoid.
hi, it won't contain any of your personal data. Personal data is stored mostly on /Data partition and we didn't dump that. Thanks
Ok, so here you have it.
Optimus_One_Baltic_ROM_dump.zip - 89.2 Mb
And it's only contains branded ROM with no changes? That's great. What program do I need to restore my ROM to the branded one, if I'm going later to change it?
i think you should look to Thunderg... it's best way to make a full backup and restore after
When I flash back to stock, of course the new updated market works. At one point I kept the stock and flashed a new kernal after updating to the current 2.2 and still the new market worked. As soon as I flash a custom ROM such as Serendipity, Fasty, Cognition, or another the market all of a sudden does not work. When I mean does not work, I only mean in the instance that it will not download large apps. I have read on flashable zips, adb shell commands, and other methods such as removing the battery but still none of this works. Is there any way to fix this problem without reverting to the old market??
It's cache size related bug, the problem here is that manufacturers put a cache partition on their devices that is smaller than googles maximum allowed app size for the market, 50MB (which was updated this year from 30mb). Reverting back to the old market will fix that issue and what I'd recommend you is to freeze MarketUpdater in TiBu (titanium backup app) so that it won't allow it to update itself back to the new market.
In case u want to use the new market, u'll have to apply the fix made by corgar - iXNyNe ,but it requires a kernel with init.d script support. If u wanna try it out here's the script, download and extract the file and then copy it in system/etc/init.d folder with a root explorer and modify the permissions of the script to 7-5-5. To do that go to system/etc/init.d folder ,mount r/w (if ur using root explorer) and long press on S95change_cache file, select permissions and make it look like in the pic below and then reboot ur phone in recovery and wipe cache ,dalvik cache and restart ur phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If all went well (u should have a cache.img file under dbdata of 54+ mb) u now can download all the apps from the new market, if it didn't then try with 7-7-7 permissions (like in the pic above only everything checked)
There are other methods , here's a post from Kyuta Syuko that sums it all up. http://forum.xda-developers.com/showpost.php?p=17850944&postcount=9050
Have u tried stopping the market and clearing all data in the all apps menu?
Sent from my SGH-I897 using xda premium
He can try that too, but that's useful when ALL downloads aren't starting/apps aren't updating. But the 30mb+ download issue ,insufficient space error, is cache related.
I can confirm (and others did as well) that the script works.
Thanks for the help but I did search like I posted. None of the options worked. But I did figure out a way around it. Just disable the VooDoo Lagfix and system lagfix. Download perfectly afterwards. Defintely beats reverting to older markets and the methods described. Although this worked for me, hopefully someone will find luck with the methods you all posted. But yeah I tried everything besides reverting to the market and enabling a script change. That was going to be my last option.
Good to hear u managed to get it work, btw could u pls check if Third Blade downloads without an error. Thx
Having found the fix'es on this site for the GPS, I am having a great deal of trouble applying it.
Using ES File Explorer I can navigate to root/etc - but I if I try to add or delete it just tells me the file can not be deleted (or added/copied/renamed or whatever I try). So how do I overcome this?
Secondly, I have to change the file permissions.
e.g.
5.Set permissions as follows
gps.conf rw- r-- r--
gps_brcm_conf.xml rwx rwx --x
Where do I go to make these changes?
Thanks.
1. I think your system partition is mounted as read-only, so you have to mount it as read/write - then changes are allowed. In Es file explorer there is such option in settigs menu.
2. To change permission using Es, put your finger on file you want to change permisions and hold a while. When 'operations' menu appers, go to option 'properties' and there is window where you can change permissions
yomek88 said:
1. I think your system partition is mounted as read-only, so you have to mount it as read/write - then changes are allowed. In Es file explorer there is such option in settigs menu.
2. To change permission using Es, put your finger on file you want to change permisions and hold a while. When 'operations' menu appers, go to option 'properties' and there is window where you can change permissions
Click to expand...
Click to collapse
1. Cant find any options that do this.
2. doing this only gives me buttons for "check checksum" and "OK", but I suspect if once I can change things in root I may get different options.
If you have rooted phone and root permiossions for Ex file explorer granted, then:
{
"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"
}
in my case it looks like this... and work well
and:
Arr yes, I see it now. But its greyed out and wont let me activate it. When I try to enable root explorer I get this message:
Warning: When 'SU Request' dialog popup, please select 'always allow' or make system 'remember' your 'allow' choice. Do you want to try this feature anyway?
It then says "sorry, test failed, this feature cannot be run on your phone"
So looking up this new problem I installed some adb software to fix my SU Request problem. But it adb software only says it only works on rooted devices and wont let me do anything..... frustrating
EDIT: I have installed GingerBreak to root it. But its been trying to do so for over an hour...
You need to be your phone rooted.
The method changed in versions 20, the best option is bin/fls converter:
http://forum.xda-developers.com/showthread.php?t=1692191
noobguy001 said:
EDIT: I have installed GingerBreak to root it. But its been trying to do so for over an hour...
Click to expand...
Click to collapse
Yes, you need to root your device for this feature, if gingerbreak didn't work the first time is not going to work at all, i had to flash from smartflash tool in N00BY0815's guide for noobs =)
ErnuB said:
Yes, you need to root your device for this feature, if gingerbreak didn't work the first time is not going to work at all, i had to flash from smartflash tool in N00BY0815's guide for noobs =)
Click to expand...
Click to collapse
Thanks, but way to complex for me. All this stuff seems to be about changing ROMs, not just unrooting the phone, which is probably why I am having trouble grasping it.
ErnuB solution unfortunately has a youtube video which isn't in English and doesn't seem to apply to my particular version of phone which is V20c with Android 2.3.4
I will keep looking.....
formatted and repaired everything in TWRP
I thought I was having problems with my USB c otg so I took it back. Now I'm getting this message just trying to copy and paste the twrp backup on my internal storage as well. When I move it with a file explorer app it fails. When I move it with the built in storage explorer it moves it but its a 0 byte file. Is it a TWRP issue or a CM13 issue or OnePlus issue?
{
"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"
}
Using the file manager in twrp I can copy and paste the file just fine. I'm on my second different USB c OTG and it's the same problem. boot.emmc.win from my TWRP backup just won't copy over and it even erases everything off my flash drive when failing to transfer. Anyone else have this issue?
I have that issue, too.
Cant find any solution
belek1979 said:
I have that issue, too.
Cant find any solution
Click to expand...
Click to collapse
Me either it's scary enough to stop me from even plugging in my otg storage completely. 1 cable OK maybe, 2 cables, now we have a serious problem and I'm not trying to lose anymore data.
It's a bug in TWRP that makes the file get created with the wrong permissions. (You don't see this if you look at the permissions in the normal place because of how mounting works on Android.) See https://github.com/TeamWin/Team-Win-Recovery-Project/issues/749 for details.
Any chance it gets fixed? That message was 5 months ago. It would be nice to be able to backup to USB otg without everything getting erased.
954wrecker said:
It would be nice to be able to backup to USB otg without everything getting erased.
Click to expand...
Click to collapse
This never leads to anything being erased, and you can easily work around it by fixing the permissions in TWRP.
When Im moving it with the built in file manager or fx explorer it erases everything off my otg flash storage. 50% of the time it erases everything the other 50% of the time it simply copies it as a 0 byte file.
954wrecker said:
When Im moving it with the built in file manager or fx explorer it erases everything off my otg flash storage.
Click to expand...
Click to collapse
That sounds like an unrelated issue.
I think it's the exact same issue I don't think it's a coincidence its always after it gets to that exact file everytime
I was just hoping I didn't have to manually change permissions in recovery, just to be safe in case I ever forgot.
In recovery > ADB I can copy that file to PC without any problems
Yeah I can do it anyplace but when booted into the phone system. It's getting fixed soon so I won't have to worry anymore.