I've got a problem, my nexus 6p (unlocked, rooted, xposed installed, everything else is stock) everytime i try to open download app says that media storage process has stopped, any suggestion?
EDIT SOLVED
noooooo said:
I've got a problem, my nexus 6p (unlocked, rooted, xposed installed, everything else is stock) everytime i try to open download app says that media storage process has stopped, any suggestion?
EDIT SOLVED
Click to expand...
Click to collapse
Instead of just saying that it's solved, please explain how you solved it. That's the point of having these forums, sharing of information, you sharing your solution might benefit someone else in future.
Heisenberg said:
Instead of just saying that it's solved, please explain how you solved it. That's the point of having these forums, sharing of information, you sharing your solution might benefit someone else in future.
Click to expand...
Click to collapse
Well, i just said i solved beacouse i found out there were multiple thread for this problem, just no specific one for nexus 6p... anyway, at this link there's the whole process, it is quite well explained, so no need to repeat the whole thing
Related
Ever since the first froyo rom until now (currently running Nero 4.1), Fix Permissions in Rom Manager and ClockworkMod Recovery has been rendered useless. It simply starts for a second then ends right after, and permissions remain unfixed. Is this a problem due to lack of source from samsung or is this a bug that has not been detected by devs, either way if its solvable I think its a minor bug that should have some attention and maybe a fix.
Thank You!
I thought I had read something about having the proper busybox installed, but I have changed mine and can't seem to get it to work ether. I have also uninstalled and reinstalled RM.
No need for a think tank. There is already a solution.
Apparently the script in Clockwork is looking for a file in the wrong place. You can change the script or you can copy and move the file it's looking for. Either one will work. I am unsure if Koush has been contacted about this issue.
Check out this thread. I use the solution in post #3 and it works fine.
Also, if you feel as though someone is being rude, just ignore it and report the post. The mods act quickly as soon as something is brought to their attention.
-thanks for your suggestion...worked great.
Keslynn said:
No need for a think tank. There is already a solution.
Apparently the script in Clockwork is looking for a file in the wrong place. You can change the script or you can copy and move the file it's looking for. Either one will work. I am unsure if Koush has been contacted about this issue.
Check out this thread. I use the solution in post #3 and it works fine.
Also, if you feel as though someone is being rude, just ignore it and report the post. The mods act quickly as soon as something is brought to their attention.
Click to expand...
Click to collapse
--Thanks for keeping this thread on-point. Almost got side-tracked there with all the other posts. Follow Keslynn's attached link. The fix worked for me.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant General
I'm trying to follow these directions... but I'm not sure where to get the packages.xml file.
Can someone please show me?
jnagar said:
Thank you--if it helps, I simply copied the packages.xml file into /data/system/ in order to run fix_permissions, and then just deleted the .xml file.
A temporary fix, yes, but I was just trying to fix a specific problem with ending phone calls causing an FC (see http://forum.xda-developers.com/showthread.php?p=9943863#post9943863).
Click to expand...
Click to collapse
rogue sound files
I wonder if permissions will fix the rogue sound files in my player?
Does anyone know if the fix permissions issue is limited to Rom Manager or if all other applications doing the same thing are affected? I tried using the "Root Tools" app to fix permissions, but it looks to be doing the same thing that occurs in rom manager.
- Mat
Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.
KrossX said:
Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.
Click to expand...
Click to collapse
Sent from my GT-I9505G using Tapatalk 2
KrossX this is the second time you have posted questions in the development forum. As I stated before these are for Q&A NOT here. Please refrain from posting your questions here and READ the XDA users guide and forum rules again. There is a reason for this. I am glad your part of the community and your questions and comments are noteworthy you just need to put them in the right place. We read those threads as well! MJ
This is for Development ONLY
Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I thought that since I was aiming this more at the devs it would've been in the Dev forums. Sorry for having you move yet another thread of mine.
Didn't mean to cause a ruckus; never really got a chance to read the post by deaffob above before it was edited by the mod so no offense from whatever name-calling was done, haha.
Thanks MJHawaii; I will search for logcat and see what I can pull up.
Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4
KrossX said:
Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.
xHausx said:
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.
Click to expand...
Click to collapse
Good news and bad news.
Bad news: I am unable to run logcat; I am unable to access my device via USB ever since the root and when I tried doing the logcat steps, yet again it couldn't connect to my device.
Good news: I believe the solution to this issue (being unable to access my device via USB) may also lie in the logs along with the bluetooth issue. The reason why is because of this error message I received while trying to reinstall the USB driver (attached pic); it points to not being able to "start" a device. I think this will all eventually tie-in with some services not running correctly on my phone.
So, is there another way for me to post a log for you kind folks to review on here via my phone directly?
If I can do that via catlog app on my device, let me know what sort of log (which options) I'd need to run and post. Thanks!
Well, did a restore to stock + root. That didn't help. It changed the Baseband, Kernel, and Build versions but did nothing to fix my issues with BT and USB connectivity.
I think I am going to start researching ways to start from scratch. Like a factory reset/wipe back to first-use condition. If anyone can point me towards some reading material on how to do that safely and wisely, it would be much appreciated!
I just ended up doing a factory reset (Menu-->Settings-->Backup & Reset-->Factory Data Reset) and that resolved the issue (while wiping my phone).
Bluetooth issue is resolved; tested it just now and it works just fine again. As is the USB issue; as soon as the phone was connected to the same exact PC as before, it was recognized and showed up as a device that I could open and explore.
My Kernal/Baseband/Build versions are all back to the ones I had when I got the phone from the Google Store, so that's comforting too.
Thanks to all those who attempted to help!
Hi Guys,
I have a weird problem with my S7 Edge, everytime I launch µTorrent my phone reboots few minutes after
Can anyone help please
Thanks in advance
Logcat maybe?
But thinking logically, if its a reboot, does it have some Permission issues and is causing the device to crash?
Your asking abit of a needle in a haystack unless this is a common issue, If you can post the Logcat we can get an idea why its crashing / rebooting
dave7802 said:
Logcat maybe?
But thinking logically, if its a reboot, does it have some Permission issues and is causing the device to crash?
Your asking abit of a needle in a haystack unless this is a common issue, If you can post the Logcat we can get an idea why its crashing / rebooting
Click to expand...
Click to collapse
Thanks Dave
What's a Logcat please? please show me how to do and I will share it
The_Warchitect said:
Thanks Dave
What's a Logcat please? please show me how to do and I will share it
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1726238
Or google how to extract Logcat android
(The System Log file)
There is alot of Apps on the Play-store that will also extract this for you.
Just search google play "Logcat"
Ideally you want to capture the log straight after a boot when the crash / reboot occurred.
Will do that immediately
Here it is
I launched it again and my phone rebooted a second time log attached
I'm no expert but there's something with the install of AppCompat.
CrEaTiiOn_187 said:
I'm no expert but there's something with the install of AppCompat.
Click to expand...
Click to collapse
What's AppCompat please? is there a way to fix this?
The_Warchitect said:
What's AppCompat please? is there a way to fix this?
Click to expand...
Click to collapse
As i said i'm no expert but it seems that that is your problem. It tries to install it but it can't 'cause there's already a factory one. Don't know what it is though.
dave7802 said:
http://forum.xda-developers.com/showthread.php?t=1726238
Or google how to extract Logcat android
(The System Log file)
There is alot of Apps on the Play-store that will also extract this for you.
Just search google play "Logcat"
Ideally you want to capture the log straight after a boot when the crash / reboot occurred.
Click to expand...
Click to collapse
I just upload to logs
Can you help please
Many thanks in advance
Here is another one
Hi,
I am currently following this 'How-to' guide here: https://forum.xda-developers.com/att-s7-edge/development/howto-update-galaxy-s7-edge-firmware-to-t3541329
However, when I get to trying to Sideload 'v8 (G935AUCS4APJ4) to unreleased (G935AUCU4BQA4) update file' - it says it 'cannot read *filename*'. I've visited the troubleshooting link in the OP's post, but to no avail. Tried everything, new USB Cable, different port, different ADB drivers etc.
I'd like to say that the problem lies with the file itself, but having seen other people have success with it, means it must be a problem on my end.
Do any of you have any suggestions on how to fix this? If possible, can anyone link a new upload of it?
For reference: I own the US model, G935AUCS4APJ4 is what I am on now. I am using the Sideload method as I don't have an SD Card. Any help is appreciated.
Thanks.
NoogleGexus said:
Hi,
I am currently following this 'How-to' guide here: https://forum.xda-developers.com/att-s7-edge/development/howto-update-galaxy-s7-edge-firmware-to-t3541329
However, when I get to trying to Sideload 'v8 (G935AUCS4APJ4) to unreleased (G935AUCU4BQA4) update file' - it says it 'cannot read *filename*'. I've visited the troubleshooting link in the OP's post, but to no avail. Tried everything, new USB Cable, different port, different ADB drivers etc.
I'd like to say that the problem lies with the file itself, but having seen other people have success with it, means it must be a problem on my end.
Do any of you have any suggestions on how to fix this? If possible, can anyone link a new upload of it?
For reference: I own the US model, G935AUCS4APJ4 is what I am on now. I am using the Sideload method as I don't have an SD Card. Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
I had the exact same problem as you, which is strange because I've used ADB on the same setup (same cable, port, phone, OS, drivers, etc.) to sideload packages with no issue. It's such a hard issue to solve, as even RAM/space requirements could cause it.
Long story short, nothing fixed the problem for me either. I'd trust that your file is fine - I don't think you need to re-download it.
Sadly, I think your best option is just buying a cheap SD card. It sucks, but sideloading the package from the SD card via recovery worked perfectly for me.
As was said previously, use an SD card.
NoogleGexus said:
Hi,
I am currently following this 'How-to' guide here: https://forum.xda-developers.com/at...to-update-galaxy-s7-edge-firmware-to-t3541329
However, when I get to trying to Sideload 'v8 (G935AUCS4APJ4) to unreleased (G935AUCU4BQA4) update file' - it says it 'cannot read *filename*'. I've visited the troubleshooting link in the OP's post, but to no avail. Tried everything, new USB Cable, different port, different ADB drivers etc.
I'd like to say that the problem lies with the file itself, but having seen other people have success with it, means it must be a problem on my end.
Do any of you have any suggestions on how to fix this? If possible, can anyone link a new upload of it?
For reference: I own the US model, G935AUCS4APJ4 is what I am on now. I am using the Sideload method as I don't have an SD Card. Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
You need to place in *filemane* file you download and rename to .zip. In example if you name downloaded file update.zip you should wrote " adb sideload update.zip" w/o qotes.
Good luck.
Sent from my SAMSUNG-SM-G935A using XDA Premium HD app
I've looked around on the forum but haven't found anything concrete. I've so far only been able to find broken mirrors to supposed fixes and random chatter about the issue.
If you happen to know more about this please let me know.
Thanks
Thebluemace said:
I've looked around on the forum but haven't found anything concrete. I've so far only been able to find broken mirrors to supposed fixes and random chatter about the issue.
If you happen to know more about this please let me know.
Thanks
Click to expand...
Click to collapse
You are still having that issue? If you have already updated to the latest Rom .
You can do this for a go to root/data/system folder. and then try delete this file
* locksettings.db
It will allow you to enter the OS without a key and then you can recreate one. But it will not permanently solve the issue.
FYI : Certain Magisk mods seemingly to make this happen or happen quicker than it would without them.
tsongming said:
You are still having that issue? If you have already updated to the latest Rom .
You can do this for a go to root/data/system folder. and then try delete this file
* locksettings.db
It will allow you to enter the OS without a key and then you can recreate one. But it will not permanently solve the issue.
FYI : Certain Magisk mods seemingly to make this happen or happen quicker than it would without them.
Click to expand...
Click to collapse
I may not have been clear enough in my question, I can access my phone but after rebooting I'm not able to use my fingerprints anymore..
Thebluemace said:
I may not have been clear enough in my question, I can access my phone but after rebooting I'm not able to use my fingerprints anymore..
Click to expand...
Click to collapse
Its a bug, with the current version of the msm8996Pro base, which all Roms use
The developers are aware of the bug and it will be fixed on the next build. For now you can row back to an earlier rom that didn't have that issue or wait for the next build of the Rom you are using.