Hi there,
I'm getting an error - "CreateDirectory() Error!!" every time when I reset my phone. I'm not sure which program is failing and causing this error. I'm still on Tmobile US stock ROM, got my HD2 last week. I've loads of apps/games installed.
Not sure if anyone else have this problem, so just checking.. I couldn't find anything in XDA search & google search as well..
Thanks in advance
I have not heard of this issue, but the only thing I can think of is to reinstall a ROM, then install things one at a time and try it out for a while then you will see what the problem is ...
OR... think about when you first started seeing the error, around that time what app did you install last ? ...remove that one then work your way back down until you fix it/remove the error or app with the error...
hope this helps!
thanks. I'll try that. So far, it's not causing any problem, as soon as I close the message box, everything seems to work fine.
I have a tmobile s4 running wicked v2 and I am unable to get any program that can make logcats to work with my phone. I tried several and including catlog. When I run it, it keeps loading showing the loading circle and nothing comes up. I even tried Easy Android Logcat tools on my pc and I am still having problems. How can I get this to work correctly?
Hi Folks,
I've been lurking and getting great advice form this forum for many years but have finally come up with something I can't fix myself.
I was running a few custom roms but somehow when trying out a few of them I have managed to do something so that I can't flash any custom roms any more.
TWRP which gives an error 7 message (which seems to suggest that my phone no longer thinks it is a moto x play). At present I can install stock roms using ADB but that seems to be about it. I have tried to roll back using a stock rom from the motorola website (LUX_RETLA_DS_LPD23.118-6.1_cid12_lux_retla_ds) but that didn't fix it.
I also can't seem to root my current stock rom (XT1562_LUX_RETEU_6.0.1_MPD24.107-52) but am sure I was able to before i had this problem.
I can't help but think I probably should be grateful that whatever i did didn't brick my phone but I've been trying every idea I can find that over the last few months and nothing has helped. I get the idea it might be some kind of low level partition issue but that is just a desperate hunch. From time to time I've got what seem to be partition errors when try various roms to fix this but they've usually worked their way out.
Any hints or suggestions on how to rectify this would be most welcome.
N
I have a glitch with the stock ROM from Samsung SM-N910W8 Android v# 6.01 and all latest updates, there is a clitch that will kill my battery very fast and cause my phone to miss read the battery # as it usually shots off and will not last rebooting past the intro screen for Touchwhiz but says the battery % is usually between 17 -35%.
I know in any kind of power saver mode I get down to 1% like a normal phone but under battery nothing is listed that used that much power. Also other mods so far I don't get that issue.
So here is what I am looking for.
I want to install one of 2 roms. the first is Alliance ROM I have fallowed all their instructions on this page.
https://forum.xda-developers.com/no...0-1-alliancerom-n910f-18-themes-huge-t3051276
I could not install bob4 or any other bob modem either with Oden (yes the latest one 3.12 or something.) I always get a basic non helpful error and fail, however when I boot into custom recovery Philz_touch I can install the Alliance mod (AllicnceROM_v2.2_N910F) that was the latest version I found to be compatible with the Note 4 so if there is something else I can go to get a more up-to-date version that would be awesome as android I think it up to V#7 something. Anyways after I clean the partition and install it just infinitely boot loops and I have to recover my old Rom to try something else.
The other MOD I found that I liked was the Omega ROM. I was able to get it installed but the modem drivers were not present and trying to fallow the instructions and install the 2 drivers to get the modem working failed every time I tried to install them. this is the link I fallowed https://forum.xda-developers.com/note-4/snapdragon-dev/omega-rom-note-4-t2994778
Can someone please tell me how if possible to get these installed properly I did fallow all the guides and they didn't work.
I am on stock rom and rooted using the Super SU method. The only things I've flashed are the wifi fix, and edited build.prop to unlock tethering. My camera app will not open, and I get this error every single time. Doesn't work in instagram, snapchat, nothing. Anyone know what may be causing this?
Anyone? I would really like to get my camera working again
had the same problem today. restarted the phone and it worked again
ckret said:
had the same problem today. restarted the phone and it worked again
Click to expand...
Click to collapse
I've restarted several times even gone so far as to install a new OS. I'm thinking about undoing the changes just to fix this.
Try booting in Safe mode
ckret said:
Try booting in Safe mode
Click to expand...
Click to collapse
Camera still doesn't work
your cam may be disconnected from the motherboard. try claiming warranty
Wiped and installed the AOKP ROM and that fixed it.. Could've been the ROM or could've been the wipe, although I wiped several times before and it didn't fix it.
did you get the error again?
I had the same problem and I installed AOKP rom which fixed it at the beginning but after less 1 day the error back again.
now I'm on stock rom .35 (rooted with Magisk) and no camera error so far after 4 days
As far as i know, it is due to custom kernel, you may have installed that.. try flashing stock rom without any custom kernel..
Mayanknagpal.nm said:
As far as i know, it is due to custom kernel, you may have installed that.. try flashing stock rom without any custom kernel..
Click to expand...
Click to collapse
yes, I had custom kernel first time I got the error.
but then I got it also with custom rom.
now I'm on stock rom and stock kernel....but does it mean that I can never flash custom rom/kernel because of that error?
marcol87 said:
yes, I had custom kernel first time I got the error.
but then I got it also with custom rom.
now I'm on stock rom and stock kernel....but does it mean that I can never flash custom rom/kernel because of that error?
Click to expand...
Click to collapse
Custom roms do not have that error... and on stock rom you can use elementalX 2.0 , it is made for the .67.. so the camera issue is resolved.. i think this will help
I had this error on Stoneware .67 (stock based ROM) and resolved it by dirty flashing Stoneware and Magisk v.13 again.
and I had this error also on AOKP rom
I have been having this problem on the Stock ROM, non-rooted, for quite some time now. I have no idea what's causing this error. When I open it sometimes, it just throws an error. If I close it and open it again, it works as it should. It's very annoying.
I had the same thing, flashing roms didnt fix it so i flashed stock via RSD lite and everything was back to normal.
Same issue here, completely stock unrooted. This is not the first Android device I've had that's struggled to connect to the camera consistently... how hard can it be?
Can people getting this error try to disable the image stabilisation in video mode please? One of the errors I see when downloading a bug report refers to the stabilisation code and I've not had the "please restart camera" message since switching it off. Could be coincidence though as it's not like I get it every time the camera loads...
Hello ,
I tried rooting my Moto G5 using Moto G5 toolkit (flashing superSU). t
Then I flashed TWRP and Flashed the WLAN_CUSTOM
Now i get that generic warning screen of unlocked boot loader however My phone is not rooted. and I cant open camera at all , getting error as " Camera Busy - Camera unable to start. If this happens again, please power off your phone and restart."
Can someone help me fix this camera issue? or just help me to revert back as it was previously no root nothing, I guess this TOOLKIT has some bugs in it.
Any help will be appreciated as I am newbie with this android development.
the.MindHacker said:
Hello ,
I tried rooting my Moto G5 using Moto G5 toolkit (flashing superSU). t
Then I flashed TWRP and Flashed the WLAN_CUSTOM
Now i get that generic warning screen of unlocked boot loader however My phone is not rooted. and I cant open camera at all , getting error as " Camera Busy - Camera unable to start. If this happens again, please power off your phone and restart."
Can someone help me fix this camera issue? or just help me to revert back as it was previously no root nothing, I guess this TOOLKIT has some bugs in it.
Any help will be appreciated as I am newbie with this android development.
Click to expand...
Click to collapse
I had the same issue as you after using the toolkit, did you fix it?