I've had the opo for about two weeks now & have flashed a couple of different on my device looking for a daily driver. I'm having issues taking screenshot. Idk if this is new because I haven't tried until this morning to take a screenshot on my device. I constantly get an error stating "can't take screenshot due to limited storage space, or it isn't allowed by the app or your organization." Has anyone else experienced this error with cyanogenmod or Android lollipop in general?
Att.Fan1982 said:
I've had the opo for about two weeks now & have flashed a couple of different on my device looking for a daily driver. I'm having issues taking screenshot. Idk if this is new because I haven't tried until this morning to take a screenshot on my device. I constantly get an error stating "can't take screenshot due to limited storage space, or it isn't allowed by the app or your organization." Has anyone else experienced this error with cyanogenmod or Android lollipop in general?
Click to expand...
Click to collapse
Nopes.
Try clearing cache/dalvik cache via recovery.
I hope your internal memory is not full.
Try to take the screenshot using any third party app. Also try hardware buttons method.
If still it doesn't works out for you, provide us your ROM information, like it's build date and try to find out the users who are on same nightly and whether they are facing same issue or not.
I hope this helps you
Mr hOaX said:
Nopes.
Try clearing cache/dalvik cache via recovery.
I hope your internal memory is not full.
Try to take the screenshot using any third party app. Also try hardware buttons method.
If still it doesn't works out for you, provide us your ROM information, like it's build date and try to find out the users who are on same nightly and whether they are facing same issue or not.
I hope this helps you
Click to expand...
Click to collapse
None of the above methods solved the problem. I've experienced this same issue on a few different roms(blisspop v2.1, cyanide 8.0, sabermod 3/23/15 build).
Att.Fan1982 said:
None of the above methods solved the problem. I've experienced this same issue on a few different roms(blisspop v2.1, cyanide 8.0, sabermod 3/23/15 build).
Click to expand...
Click to collapse
Flash back to kitkat than
I am on CyanideL 8.0, no such issues.
I was on BlissPop 2.1, no such issues.
If you face same issue on KitKat, then there is some hardware issue
Mr hOaX said:
Flash back to kitkat than
I am on CyanideL 8.0, no such issues.
I was on BlissPop 2.1, no such issues.
If you face same issue on KitKat, then there is some hardware issue
Click to expand...
Click to collapse
Thanks, I'm restoring my stock root backup now in twrp recovery & will post my results if this solved the issue or not
Edit: No luck on the stock root screenshot either, guess I'll just have to live with the fact I can't take a screenshot on my device, at least until a definitive solution is found
Okay, latest update..........I did a factory restore + unroot using bacon root toolkit then re-rooted my device using the same toolkit & restored my nandroid of my last rom and................................................................................................................................................great news screenshots are working now! :good:
Mr hOaX said:
Nopes.
Try clearing cache/dalvik cache via recovery.
I hope your internal memory is not full.
Try to take the screenshot using any third party app. Also try hardware buttons method.
If still it doesn't works out for you, provide us your ROM information, like it's build date and try to find out the users who are on same nightly and whether they are facing same issue or not.
I hope this helps you
Click to expand...
Click to collapse
Even I am facing the same problem after updating CM12 latest version yesterday. Please help
I had this tonight on COS 12.1. A reboot cleared it for now.
I am having the same problem but got fed up searching a fix , I felt a waste of time searching for it too afterall how many times do we use that feature. i downloaded a third party app for the same & its working like a charm. Problem solved
Screenshot Issue
I am facing the same problem
---------- Post added at 08:21 PM ---------- Previous post was at 07:59 PM ----------
hey guys,
You gotta follow these steps to get your screenshots up and running.
1. Open file manages
2. Look for PICTURES folder.
3. Rename it to PICTURES2 or something
That's It.... Screenshots up and running....
Now Why is that ? Thats becausethe folder PICTURES is actually supposed to be Pictures. When you try to capture a screenshot, the screenshot app looks for a folder called Pictures but since it doesn't exist, it tries to create it. But File Manager doesn't differentiate between Pictures and PICTURES. Hence the error. When you do the rename and capture a screenshot you can actually see a folder called Pictures created. Now you can move the data from PICTURES2 to Pictures(Only the important one and without deleting anyexisting content in Pictures). It is safe to delete the PICTURES2 folder after this.
For now, screenshots work after renaming pictures to pictures 2 but I am unable to delete my pictures 2 now. There is a file name screenshot inside(not image). Any suggestions how to delete this?
Thank you.
saqlainsyed007 said:
I am facing the same problem
---------- Post added at 08:21 PM ---------- Previous post was at 07:59 PM ----------
hey guys,
You gotta follow these steps to get your screenshots up and running.
1. Open file manages
2. Look for PICTURES folder.
3. Rename it to PICTURES2 or something
That's It.... Screenshots up and running....
Now Why is that ? Thats becausethe folder PICTURES is actually supposed to be Pictures. When you try to capture a screenshot, the screenshot app looks for a folder called Pictures but since it doesn't exist, it tries to create it. But File Manager doesn't differentiate between Pictures and PICTURES. Hence the error. When you do the rename and capture a screenshot you can actually see a folder called Pictures created. Now you can move the data from PICTURES2 to Pictures(Only the important one and without deleting anyexisting content in Pictures). It is safe to delete the PICTURES2 folder after this.
Click to expand...
Click to collapse
Hi Guys,
Seems the internal memory permission has been jumbled up and you need to fire the following command to restore the same. Connect with adb while booted in recovery and run the following commands to correct the permissions. After that your problem might get solved:
Code:
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ';'
find /data/media/ -type f -exec chmod 664 {} ';'
Thanks
Related
Should be working fine but it's thoroughly untested so expect errors at some point.
It's for cyanogenmod installations where /custpack is mounted to /system/app, if there is a request i'll make a version that mounts /custpack to /custpack but for now this is it.
I take no responsibility for what this will do to your phone, it's entirely possible that it will kill your phone and even cause a rift in the space time continuum which will kill us all.
Anyway, here it is, flashable via fastboot as usual, if it goes to stable i'll make an installer for it to install via CWM.
For those not comfortable with flashing via fastboot or who don't have access to a computer at this time, use flash_image via terminal, it should work fine.
Latest version:
cwm_touch_cocktail_6.0.2.7-testing-V2.img
MD5: feb35010a527de42c6c68d6987b939e1
Old versions (kept but not recommended):
cwm_touch_cocktail_6.0.2.7-testing.img
MD5: da314f6eb6429bc3530539d8a0e9e20a
Changelog:
2013-01-09
* Fixed buttons, you can now scroll, select and go back using the buttons.
* Fixed backup, /custpack is now linked to /system/app, this should also make it compatible with older roms. (Remember, this is still testing)
* Added mountpoint for /sd-ext to fix nandroid backups for A2SD/S2E/Links2SD installed apps.
* Fixed some glitches and updated kernel code.
2013-01-08
* initial release
Just flashed it to my mobile and thus far it looks promising. Currently I am not planning to change my rom yet so I haven't confirmed if it is able to flash a rom I only saw it boot.
A little thing I noticed though.
When CWM boots and you are in the main menu the menu fills around 80% of the screen. But when you go to another menu lets say flash something from SDCard it only fills up 50% of the screen and you have to scroll a lot to reach the bottom.
Also the buttons are not working at all?
When you press some of the buttons it starts doing weird stuff..
It seems like the volume buttons and the power button work currectly but the buttons at the bottom of the screen are weird.
Hylix said:
Just flashed it to my mobile and thus far it looks promising. Currently I am not planning to change my rom yet so I haven't confirmed if it is able to flash a rom I only saw it boot.
A little thing I noticed though.
When CWM boots and you are in the main menu the menu fills around 80% of the screen. But when you go to another menu lets say flash something from SDCard it only fills up 50% of the screen and you have to scroll a lot to reach the bottom.
Also the buttons are not working at all?
When you press some of the buttons it starts doing weird stuff..
It seems like the volume buttons and the power button work currectly but the buttons at the bottom of the screen are weird.
Click to expand...
Click to collapse
I had completely forgotten about the bottom buttons TBH, i'll fix that in a future version.
Regarding the screen space, it's not much i can do about that ATM but i'll keep it in mind when and if it gets to stable.
Awesome looking good so far
Really cool. Just point and I'll help test.
Downloading and testing.
With this we can backup and restore CM/PA/PAC roms right?
Mrwargod said:
Downloading and testing.
With this we can backup and restore CM/PA/PAC roms right?
Click to expand...
Click to collapse
If you mount /system/app in mounts and storage it should work just fine.
I'm probably going to write a script and put it in the place of the nandroid/nanddump/nandwrite files so /system/app is mounted before the backup/restore is written.
Just added some stuff to it, partitioning sdcard and support for sd-ext (and swap).
Should work well with an init.d script and s2e for those interested in larger storage for apps.
(simple script to mount /dev/mmcblk1p2 to /sd-ext would work)
tumaini418 said:
Really cool. Just point and I'll help test.
Click to expand...
Click to collapse
Would be great it you have the opportunity.
When i use key test section, its dont back main screen and i need unplug battery.
You did great job thanks a lot...
master' said:
When i use key test section, its dont back main screen and i need unplug battery.
You did great job thanks a lot...
Click to expand...
Click to collapse
You are welcome.
Jinxxed said:
If you mount /system/app in mounts and storage it should work just fine.
I'm probably going to write a script and put it in the place of the nandroid/nanddump/nandwrite files so /system/app is mounted before the backup/restore is written.
Just added some stuff to it, partitioning sdcard and support for sd-ext (and swap).
Should work well with an init.d script and s2e for those interested in larger storage for apps.
(simple script to mount /dev/mmcblk1p2 to /sd-ext would work)
Click to expand...
Click to collapse
Yes, having that automated would be great. If i could backup/restore/install zip's all in one CWM that would be awssome and render it definitivelly daily usable. And way easyer for me to test more roms without the concern in loosing my previous rom.
Mrwargod said:
Yes, having that automated would be great. If i could backup/restore/install zip's all in one CWM that would be awssome and render it definitivelly daily usable. And way easyer for me to test more roms without the concern in loosing my previous rom.
Click to expand...
Click to collapse
Should work fine now, to check if it is, analyze the content of your /sdcard/clockworkmod folder.
Already on it to try the latest version of PAC.
I'll feed you on how it went.
---------- Post added at 11:39 AM ---------- Previous post was at 11:18 AM ----------
The link is dead Jinxxed, or is it still uploading?
Mrwargod said:
Already on it to try the latest version of PAC.
I'll feed you on how it went.
---------- Post added at 11:39 AM ---------- Previous post was at 11:18 AM ----------
The link is dead Jinxxed, or is it still uploading?
Click to expand...
Click to collapse
I mistyped the link. :silly: It's fixed now.
Sorry about that.
Yeah, i had already figured out the correct link anyway.
Thanks, testing!
Wipe battery stats is missing in advanced menu.
Backup / Restore - Not working properly - Some of my apps got lost in restore, namedelly all the gapps, some launchers (holoHD), some file explorers (root file explorer), google account, . . .
Flash zip - ROM flashed ok but gapps didn't flashed, neither did an aditional mod.
But it's really looking really good. And the hardware buttons are fixed.
Keep up the good work.
Mrwargod said:
Wipe battery stats is missing in advanced menu.
Backup / Restore - Not working properly - Some of my apps got lost in restore, namedelly all the gapps, some launchers (holoHD), some file explorers (root file explorer), google account, . . .
Flash zip - ROM flashed ok but gapps didn't flashed, neither did an aditional mod.
But it's really looking really good. And the hardware buttons are fixed.
Keep up the good work.
Click to expand...
Click to collapse
Thank you.
It's a weird result since that means that the backup has problems with both /data and /system/app (i assume since google account and launchers not installed via CWM are stored on /data). It really should be all or nothing, one would think...
There is a problem with mounting /system/app for some reason, that's why gapps isn't installed properly, i'll look into it.
It should be easy enough to fix though, expect a new version within the next couple of days.
Will post the same post here as in Benetnath his PAC rom cause maybe it has something to do with CWM?
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Just ran against a problem with doing the PAC update.
All my gapps seem to be broken and some apps crash on start up.
I had the first PAC rom running and flashed the newest over it while clearing my cache (tried flashing the gapps after this but still didn't fix it)
After this I did a complete reset and flashed it and now it seems to work.
Don't know if its the ROM or if its the new touch CWM which is still in testing..
NOTE: It seems like other people succeeded in flashing the updated rom over the previous rom.
I am not the only one with this problem and it seems like there are other people who have the same problem with the other CWM so ignore this all
trying to flash image in terminal in phone. i keep getting "error scanning partitionsfailed with error: -1
??????????
anyone?
nevermind i went ahead and did it the way i know how.
2nd Edit: just did a backup and restore. Seems to have worked fine.
I couldn't mount usb though.
Great work man. Between you and Benetnath we should be cooking with gas soon.
Thanks jinxxed.
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
THIS IS ONLY FOR THE GALAXY SIII
***MY FIX***
BACKUP ANYTHING IMPORTANT JUST IN CASE
Download this zip https://dl.dropboxusercontent.com/u/91693945/CameraFiles-signed.zip
Flash using Recovery
Wipe Cache & Dalvik (optional)
Fix Permissions
Reboot into Android
Start the camera app and cross your fingers
***MY FIX (Old Way)***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Appreciate the guide, hope it helps someone down the road. I'm in the camp that has no issues going back and forth between AOSP 4.3 or TW. I'll add this Rootz link as well which provides some additional information and might be making its way into roms via Github. Seems like as good an opportunity to spread the wealth.
Zophone i5 v8?
dwibbles33 said:
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
***MY FIX***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Click to expand...
Click to collapse
I am facing the same problem on my iphone clone - zophone i5 v8. These models do not have a "cameradata" folder in /system. Do you have a fix for these MTK phones?
shailendrachimade said:
I am facing the same problem on my iphone clone - zophone i5 v8. These models do not have a "cameradata" folder in /system. Do you have a fix for these MTK phones?
Click to expand...
Click to collapse
Me too had problem with camera, but it seems like i got fixed it finally... I have a Cubot One MTK6589 with Miui rom. The steps are:
1. http://d-h.st/BKA download this file and flash it. It will install jb camera for your mobile.
2. check it
3. if it works delete the old camera app with titanium backup because if u run the old bad camera app the problem will come back and u have to flash again.
4. install some good camera app like camera awesome because for me the jb camera doesn't detected my front camera.
I hope this will help you!
Will Try
papp-david said:
Me too had problem with camera, but it seems like i got fixed it finally... I have a Cubot One MTK6589 with Miui rom. The steps are:
1. http://d-h.st/BKA download this file and flash it. It will install jb camera for your mobile.
2. check it
3. if it works delete the old camera app with titanium backup because if u run the old bad camera app the problem will come back and u have to flash again.
4. install some good camera app like camera awesome because for me the jb camera doesn't detected my front camera.
I hope this will help you!
Click to expand...
Click to collapse
Let me try..thanks!
---------- Post added at 05:33 PM ---------- Previous post was at 04:58 PM ----------
shailendrachimade said:
Let me try..thanks!
Click to expand...
Click to collapse
I flashed successfully...but I do not see any camera app installed? I can see the Galary app. Even tried deleting original camera app by Titanium, still same issue.
Thank you. I also had this problem with any aosp ROM but the fix stopped working for me with the kk ROMs did you have the same problem?
Uou need to patch the shared objects using your stock tom files
Sent from my SM-N9006 using xda app-developers app
remzej said:
Uou need to patch the shared objects using your stock tom files
Sent from my SM-N9006 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.. Bit could you explain a little more?
evertking said:
Thanks for the reply.. Bit could you explain a little more?
Click to expand...
Click to collapse
shailendrachimade said:
Let me try..thanks!
---------- Post added at 05:33 PM ---------- Previous post was at 04:58 PM ----------
I flashed successfully...but I do not see any camera app installed? I can see the Galary app. Even tried deleting original camera app by Titanium, still same issue.
Click to expand...
Click to collapse
dwibbles33 said:
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
THIS IS ONLY FOR THE GALAXY SIII
***MY FIX***
BACKUP ANYTHING IMPORTANT JUST IN CASE
Download this zip https://www.dropbox.com/s/bt1ucpgb9xfmjbi/CameraFiles-signed.zip
Flash using Recovery
Wipe Cache & Dalvik (optional)
Fix Permissions
Reboot into Android
Start the camera app and cross your fingers
***MY FIX (Old Way)***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Click to expand...
Click to collapse
The file is not available on dropbox for download , i am using AOKP on SG3 and the camera stops working if i open through whatsapp or any other app and when i go back to the camera it gives that error
Try the One+ One or AOSP modded cameras in the Apps and Themes section. One+ One camera is awesome!
Ahmadqatei said:
The file is not available on dropbox for download , i am using AOKP on SG3 and the camera stops working if i open through whatsapp or any other app and when i go back to the camera it gives that error
Click to expand...
Click to collapse
Link fixed, sorry I don't really keep up with this anymore, my bad
fix front camera
work for my mtk device
edit builtprop, open the editor and change or add
hw.cameras=1
ro.camera.dcim=1
explanation
# hw cameras
hw.cameras = 2 (1 only for the Front, 2 for the Front & Back)
# camera DCIM dir. 0: sd only; 1: nand only; 2, sd first
ro.camera.dcim = 1
This is likely to occur due to the use of internal memory is converted into ROM
while the external sdcard memory is converted into internal
hopefully work
:cyclops:
Just sharing:
flashing didn't work, used servicely and added camera service to hitlist.
can i use it on galaxy core
Ive factory reset several times now, I've reflashed the android l preview image several times, and flashed two 5.0 roms over it even, and i even tried a multiboot with cm11. My device can't take pictures, video, basically anything to do with the camera doesnt work. Pictures seem to take, but don't save. Video or any panorama crashes the camera, and the error logs show something about permission denied to the files they are trying to create. How can i fix this?
Did you copy all your data back to the phone via recovery?
Usually for L, you run
su
restorecon -FR /data/media/0
...which is mentioned in his sticky lots of times.
But If you copied all sdcard data back to your phone via recovery, there's a different approach
rootSU said:
Did you copy all your data back to the phone via recovery?
Usually for L, you run
su
restorecon -FR /data/media/0
...which is mentioned in his sticky lots of times.
But If you copied all sdcard data back to your phone via recovery, there's a different approach
Click to expand...
Click to collapse
I tried that one, it did nothing and camera still acted up. I've tried every app on the store. Nothing seems to be allowed to write to DCIM, even though I can create files with a normal file manager just fine.
rootSU said:
Did you copy all your data back to the phone via recovery?
Usually for L, you run
su
restorecon -FR /data/media/0
...which is mentioned in his sticky lots of times.
But If you copied all sdcard data back to your phone via recovery, there's a different approach
Click to expand...
Click to collapse
I just tried creating a file inside the camera folder inside DCIM and permission was denied. How could I fix that?
dreamwave said:
I tried that one, it did nothing and camera still acted up. I've tried every app on the store. Nothing seems to be allowed to write to DCIM, even though I can create files with a normal file manager just fine.
Click to expand...
Click to collapse
Using a root explorer, go to /data/media/0/Download and set all the permissions to read, write and execute.
Then hopefully you can download stuff.
Please check that. If that works, I'll let you know the next step
rootSU said:
Using a root explorer, go to /data/media/0/Download and set all the permissions to read, write and execute.
Then hopefully you can download stuff.
Please check that. If that works, I'll let you know the next step
Click to expand...
Click to collapse
I can already download stuff. Is it a common problem with L for this to happen? I've looked it up and found little to nothing.
rootSU said:
Using a root explorer, go to /data/media/0/Download and set all the permissions to read, write and execute.
Then hopefully you can download stuff.
Please check that. If that works, I'll let you know the next step
Click to expand...
Click to collapse
I realize I just went full retard thanks to looking in the camera for permission. I had earlier set permissions with chmod from recovery for the DCIM directory to 777, but not the Camera directory within. Thanks for helping, though!
dreamwave said:
I realize I just went full retard thanks to looking in the camera for permission. I had earlier set permissions with chmod from recovery for the DCIM directory to 777, but not the Camera directory within. Thanks for helping, though!
Click to expand...
Click to collapse
One problem I have consistently had however is that my launcher and default camera app are never remembered. How can I fix this?
dreamwave said:
I can already download stuff. Is it a common problem with L for this to happen? I've looked it up and found little to nothing.
Click to expand...
Click to collapse
No it's uncommon. I've only sewn it for people using recovery or adb to push and pull sdcard folders.
Download and flash this zip via recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=2849968&d=1405300107
and it seems that for any kind of panorama or photosphere it still crashes
they crash with an event trace of java.lang.NullPointerException: attempt to invoke virtual method 'void java.io.FileWriter.close()' on a null object reference
at
com.google.android.apps.lightcycle.panoramamodule.stopcapture(panoramamodule.java:802
etc
etc
etc
Its permissions, we know that. Please flash the fix I posted before anything else.
rootSU said:
Its permissions, we know that. Please flash the fix I posted before anything else.
Click to expand...
Click to collapse
Ok, so pushing it to the sd with adb won't break even more permissions?
dreamwave said:
Ok, so pushing it to the sd with adb won't break even more permissions?
Click to expand...
Click to collapse
Why would you need to do that? You can download it direct to your phone.
rootSU said:
Why would you need to do that? You can download it direct to your phone.
Click to expand...
Click to collapse
ok, I flashed it and my phone is rebooting
dreamwave said:
ok, I flashed it and my phone is rebooting
Click to expand...
Click to collapse
Cross your fingers.
rootSU said:
Why would you need to do that? You can download it direct to your phone.
Click to expand...
Click to collapse
thanks so much, that fixed it completely!
dreamwave said:
thanks so much, that fixed it completely!
Click to expand...
Click to collapse
No problem.
The adb (or TWRP MTP) only seems to break permissions if you're pushing folders. Pishing individual files should be fine.
rootSU said:
Cross your fingers.
Click to expand...
Click to collapse
is this problem new to android l or has it been around a while? I'll also admit I do a lot of adb push/pull/commands and such, and for a lot of the time need to because I only have a wired connection with my computer at school, is there a way to avoid this problem in the future?
dreamwave said:
is this problem new to android l or has it been around a while? I'll also admit I do a lot of adb push/pull/commands and such, and for a lot of the time need to because I only have a wired connection with my computer at school, is there a way to avoid this problem in the future?
Click to expand...
Click to collapse
Its not related to L at all. Files should be fine to push. Its just folders I think that cause the issue.
I am not a big Android tech, but my work in IT teached me some basic knowledge.
But this thing I have leaves me blinded, and I haven't had this ever before on any phone (and wasn't an issue before either).
Whenever I install Lollipop at this point (Cataclysm mostly) Im facing issues with files.
A lot of them just dont show, not even the ROM file I just used.
Gallery (Photo in L) pictures untill a certain date cant be found, but are showing (with errors when opening), a Wallpaper folder just completely vanishes with L, files in Download folder..
What is this? Storage file change? Format? I dont get it.
And as soon as I flash back KitKat, all files are back.
I even deleted the faulty pictures in L, but are showing again in KK.
Is it the kernel I flash right after the Lollipop ROM?
Does L install in a different partition like thing? lol
Happily using KitKat (ART) btw, no L for me so no biggy.
But I am really really wondering, if I ever decide to go Lollipop.
Here you go man. This will explain it to you. If the terminal commands don't work for you, just move the files manually.
/sdcard problems after upgrading Android
Woody said:
Here you go man. This will explain it to you. If the terminal commands don't work for you, just move the files manually.
/sdcard problems after upgrading Android
Click to expand...
Click to collapse
Different file locations used in Lollipop obviously.
If I'd ever to switch to Lollipop and I wouldn't get an answer here, I'd completely wipe the internal storage and start from scratch again, pretty sure that would solve it.
But this might aswell do the trick..
Thanks.
I'll keep that thread saved somewhere.
justiiin said:
Different file locations used in Lollipop obviously.
If I'd ever to switch to Lollipop and I wouldn't get an answer here, I'd completely wipe the internal storage and start from scratch again, pretty sure that would solve it.
But this might aswell do the trick..
Thanks.
I'll keep that thread saved somewhere.
Click to expand...
Click to collapse
The file location is the same in KitKat and Lollipop. The reason it has issues is unknown right now.
Hi all,
I recently bought a CAT S41 and I'm wondering how to root it. The only other XDA post about this phone and rooting that I can find just has one person saying that kingoroot and one-click root did not work for him.
Things that I can figure -
1. I hear that kingoroot does not work after android 5.1 (yet they say it does on their website ? )
2. OEM Unlocking is available in the developer options and allows you to switch it to on ( Allows bootloader to be unlocked)
3. CAT isn't going to help this root be accomplished
I'm trying to look at other phones that are comparable and trying to find a route that I can root this phone. My end game for this is to get a root tutorial onto XDA that can be easily followed. I have asked the admins for a CAT S41 section also. The S41 comes with Android Nougat and a close to stock ROM. The only real difference is that it comes with a battery share app that can be very useful.
Thanks in advance for any input.
If you find anything, i would be interrested !
A root for this phone would be amazing. The stock ROM seems to have some bugs.
Hi!
I don`t own a CAT S41 but I`m planning to purchase one.
Found these online, so can anyone confirm the instructions work please.
ADB: http://neopodapsi.com/how-to-install-adb-and-fastboot-for-cat-s41/
TWRP: http://neopodapsi.com/how-to-install-twrp-custom-recovery-on-cat-s41/
ROOT: http://neopodapsi.com/how-to-root-cat-s41/
Thank You!
I will pay $50 to anyone that can root this device and can show the way for others to do the same. Message me if youre going to work in it
Thanks
I have this phone. Working fine till yesterday. Latest system update has my phone rebooting randomly.
I am trying to reach manufacturer to get a roll back to previous system.
Please disable auto update in your phones by now or you may find the same issue.
By the way the links provided by k.a.b.0 lead no nowhere but silly commercial surveys that then will redirect you to broken mediafire links.
Regards
perchera said:
I have this phone. Working fine till yesterday. Latest system update has my phone rebooting randomly.
I am trying to reach manufacturer to get a roll back to previous system.
Please disable auto update in your phones by now or you may find the same issue.
By the way the links provided by k.a.b.0 lead no nowhere but silly commercial surveys that then will redirect you to broken mediafire links.
Regards
Click to expand...
Click to collapse
Hei,
I had exactly the same experience and I tried EVERY single suggestion on-line to reboot in safe/recovery mode to fix the problem..
Then I chatted with the CAT support and I just found out that the problem is thier last update released !!!!!
actually it doesn't accept the SD card. So just remove the SD card and press the power button ...it should work fine.
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
...they also say that they are now aware of this problem and they are trying to fix it ...
So the trick should be to not use the SD card until the next update is released
evelix said:
Hei,
I had exactly the same experience and I tried EVERY single suggestion on-line to reboot in safe/recovery mode to fix the problem..
Then I chatted with the CAT support and I just found out that the problem is thier last update released !!!!!
actually it doesn't accept the SD card. So just remove the SD card and press the power button ...it should work fine.
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
...they also say that they are now aware of this problem and they are trying to fix it ...
So the trick should be to not use the SD card until the next update is released
Click to expand...
Click to collapse
Yes, me too have this problem..After till previus days have system update, and after upgrading I have reboot loop...First I have no idea what happening...I was try in recovery, wipe, system fctoring in recovery mode (yes, Im lost all my app and data), but still me boot loop making...And after all I was find, it external SD card was problem...Il try all sd card (Kingston, San Disk, Samsung, itd) was always problem with reboot loop... After all I was eject external card and was all in right. Can sameone telll Caterpillar (Bullit Group) for this very great problem. I really need external card with great capacity (128 GB) becao se i need it for my job...
perchera said:
I have this phone. Working fine till yesterday. Latest system update has my phone rebooting randomly.
I am trying to reach manufacturer to get a roll back to previous system.
Please disable auto update in your phones by now or you may find the same issue.
By the way the links provided by k.a.b.0 lead no nowhere but silly commercial surveys that then will redirect you to broken mediafire links.
Regards
Click to expand...
Click to collapse
Hey me too! It's a **** eh?
Contacting Cat support tomorrow fully expect to have to ship it to them.
Yes, it's the SD card as the Cat support confirmed by email. They introduced a bug in the latest update, they're aware of that and trying to fix it.
They also told me to see on a daily basis if there's a new update. Until then we will have to leave the SD card out - works fine, only a bit restricted (I'm doing a lot of data intensive stuff usually).
Hi ! since this topic is not only for root anymore, I post here.
Does anyone else have audio issues ? When I listen music, sometimes there are bugs, loops, music is jerky... it often goes in the day, but not always.
The bug occurs on differents music players (deezer, black player, soundcloud, ...) and more often when the screen is off.
Is this for all S41 or is it only me ?
TankiFrench said:
Hi ! since this topic is not only for root anymore, I post here.
Does anyone else have audio issues ? When I listen music, sometimes there are bugs, loops, music is jerky... it often goes in the day, but not always.
The bug occurs on differents music players (deezer, black player, soundcloud, ...) and more often when the screen is off.
Is this for all S41 or is it only me ?
Click to expand...
Click to collapse
Almost one year old question, but you are not alone. Even ring tones and notifications have this problem on my phone.
eazrael said:
Almost one year old question, but you are not alone. Even ring tones and notifications have this problem on my phone.
Click to expand...
Click to collapse
Actually I don't have this issue anymore. Try to see if your frimware is up to date.
bortski said:
I will pay $50 to anyone that can root this device and can show the way for others to do the same. Message me if youre going to work in it
Thanks
Click to expand...
Click to collapse
Add a 50$ from me as well.
Cannot find anything on unlocking bootloader or a twrp or a root software/apk for the device.
DISCLAIMER:
I just shared these steps in hope that it will help some of you achieve root on Cat S41. I am not, in any way, encouraging you to run these commands. YOU chose to follow the steps I have provided to the best of my knowledge. If you damage, soft-brick, hard-brick, or blow up an entire city because you did these steps and point your finger at me, I will laugh at you, make fun of you for not reading this disclaimer, and I will NOT take responsibility for stuff that you did.
I have not tried this on a Cat S41 so please let me know if it works. So I think it's like this:
EDIT: Oh yeah, I forgot that we can't even unlock bootloader. And the command in step 6 doesn't work without running su first. Which requires root and we can't get that in the first place. If you can figure out a workaround, that would, I'm sure, be appreciated by all of us here.
Install all the required drivers for Cat S41 on your PC.
Download ADB and Fastboot tools.
Open ADB.exe and connect your phone to your PC via USB cable.
Type adb devices to verify that your phone is recognized. Allow PC to connect to your phone by clicking allow on the prompt on your phone.
Type adb shell
Then we need to pull boot.img so I think you have to do dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Now the boot.img should be copied to the internal storage of your Cat S41.
Install Magisk Manager/App on your phone.
Select Install -> Select an image to patch. Choose the boot.img.
Wait for it to finish the patch.
Copy the patched boot.img to the ADB folder on your PC.
In the ADB window on your PC, type exit to leave ADB shell.
Now type adb reboot fastboot
Once your phone has rebooted to fastboot, type fastboot flash boot boot.img
Alternatively, you could also type fastboot flash boot and then drag the patched boot.img into the command prompt window.
I hope this works. Try this at your own risk. If it actually works (I doubt it will), I don't want to $100. Keep it or donate it to someone else. Or give it to whoever can make a custom rom or TWRP for this device.