Related
I have a problem where when I clear the Dalvik Cashe, it says E: Unknown volume SD_ext... People have said on other forums that this is not a problem, but I believe it is because it only happens with ICS roms, and when this started happening, the camera and gallery also stopped working. When I launch the camera or gallery, it says "media scanning" and it immediately closes the app. Anyone have any ideas about this. I'm worrying that I've broken something and I won't be able to use an ICS Rom. So far I've tried a few ICS roms and they all have this problem, but I didn't have this problem with ICS roms before. And Gingerbread roms are fine. None of the problems above.
Did you flash this way?
- Flash CF Repack via Mobile Odin
- Stay in recovery and do the following
- Fullwipe (factory reset)
- Flash ICS ROM
- Fullwipe (factory reset) again. This is important.
- Reboot device.
If you didnt full wipe before and after flash this may of had something to do with it.
Try reflash this way especially if camera is still working on GB.
I also get that same message but no problems with camera. On MIDNOTE ics but also tried TRR 1.5 ics
It isn't a problem. All ICS roms say this. Even on the Galaxy Nexus.
I used Redpill recovery...some say nonsense, but it worked like a charm. I flashed the Midnote ROM w/Chinese leak base (which has Chainfire's kernel in it), then I was able to flash any thing else over that...AOSP, MIUI, ect...
It worked for me.
Greetings,
The camera on my Note 3 is not working for video recording (taking pics works fine). I have switched a lot of roms and kernels on it, but I noticed the camera app would not record and, instead, show me a "Warning: Recording Error" followed by a force close and, usually, a reboot.
I decided to switch back to stock Lollipop to see if this would revert it, but it didn't work.
The phone specs and other info:
SM-9005
Currently on official Lollipop from Brazil (N9005VJUGBOD5_N9005ZTOGBOD4_ZTO from sammobile)
Stock kernel
These are the things I did to try and fix this, not in order:
1- Changed kernels
2- Changed roms (always wiping everything but internals on recovery before doing so)
3- Cleaned cache
4- Cleaned camera cache
5- Tried google camera app instead of the official camera app (it did not FC, but while it said it was recording, it would never save a video file of it)
6- Did a factory reset on the stock rom
7- Updated modem and bootloader with the files on the Aryamod thread
8- Tried removing the SD card completely
9- Tried reseating the SD card
10- Tried changing to internal card in the camera app
11- Changing recording resolution options
Last custom rom I had was the Omega Rom. First Lollipop rom I installed was the official (non leaked) Poland rom, and I did not use a pit file back then (as, according to the thread this was featured it, that file was meant only for users coming from the leaked lollipop rom).
This is the log from the camera bugging out in the Omega Rom:
http://pastebin.com/TkCA2KbT
I took a second one for precaution:
http://pastebin.com/1exMLTk3
This is not a hardware problem as it worked on KK. The problem persists on the official rom I just installed. Also, the SD card has a lot of space available, as does the internal memory.
Also, not sure if this is relevant, but most kernels give me a bootloop, exception being the Omega kernel and the Darkqueen. I also *may* have flashed by accident a rom based on Cyanogen at some point, but my memory is very fuzzy on this. I think that this wouldn't matter as I wipe everything before putting a new rom in, anyway (and if I did that, the new and now correct rom I put after that wouldn't leave any traces of this accident).
I have no idea what else to do to fix this.
I have exactly the same problem. I have a ZTO Note 3 with the same problem as well, sometimes the whole android crashes after I try to record it.
The whole problem began after I installed the Omega Rom, I used CM12.1 for quite some time and the camera record correctly. I am not sure if you managed to wipe the whole thing by using the TWRP, but once I did, I found out that it was a MTO problem, which I searched about and it was nothing major.
Did you manage to fix the problem?
Maybe install latest bootloader?
Try changing the camera app video resolution back to 1080P - there's been a number of people had problems with UHD mode.
It's quite possible that BL and Modem flash will not work unless you turn the phone off and then go into DL mode for an Odin flash - rebooting into DL mode doesn't let them flash. So maybe once you went to a ROM that had the UHD issue, you haven't fully come back to stock?
Journyman16 said:
Try changing the camera app video resolution back to 1080P - there's been a number of people had problems with UHD mode.
It's quite possible that BL and Modem flash will not work unless you turn the phone off and then go into DL mode for an Odin flash - rebooting into DL mode doesn't let them flash. So maybe once you went to a ROM that had the UHD issue, you haven't fully come back to stock?
Click to expand...
Click to collapse
white7561 said:
Maybe install latest bootloader?
Click to expand...
Click to collapse
Sorry for the time taken, I flashed the Omega Rom once again using TWRP, and then I flashed the bootloader and modem recommended for such rom using Odin, but the problem still continues. And I have tried change resolutions, storage and everything possible, the problem still continues.
Funny thing is, I thought it was the back camera problem, it could take photos but it freezes during video recording. Once I tried the front camera, the same problem happens as well, it does take pictures, but it does not record.
I am getting a little desperate now, I have a feeling that the omega rom made such problem but as of yet it did not fix said problem! What should I do?
Leminur said:
Sorry for the time taken, I flashed the Omega Rom once again using TWRP, and then I flashed the bootloader and modem recommended for such rom using Odin, but the problem still continues. And I have tried change resolutions, storage and everything possible, the problem still continues.
Funny thing is, I thought it was the back camera problem, it could take photos but it freezes during video recording. Once I tried the front camera, the same problem happens as well, it does take pictures, but it does not record.
I am getting a little desperate now, I have a feeling that the omega rom made such problem but as of yet it did not fix said problem! What should I do?
Click to expand...
Click to collapse
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
---------- Post added at 04:45 AM ---------- Previous post was at 04:40 AM ----------
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
Video not recording
Do you have a link to the kernel and has anyone else tried this? I'm also having the same problem with the video recording not working and I'm not sure what to do about it.
chickenlittlesound said:
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
---------- Post added at 04:45 AM ---------- Previous post was at 04:40 AM ----------
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
Click to expand...
Click to collapse
I'm having exact same problem
I'm also having this exact same problem with my N9005 Note 3. Its running Lollipop but i don't really much about roms as i bought it used from some shop. Everything works fine both cameras take pictures but video recording doesn't work at all. Also i downloaded a screen roader app and its videos are also not recorded. When i finish recording them and go to gallery it says File Corrupted. Please anyone got fix of this problem yet?
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian
Hi everybody,
@hayder78,
I tried to do the same to fix the issue: flash with the last firmware available for my region code (XEF - N9005XXUGBOK6) using Odin 3.11.1 and the same options (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update) but I still have the issue.
@Fenrir007
Did you manage to fix the issue using the same method?
I had the same issue with a 6.0.1 ROM (MagMa-NX UX8.5) on my Note 3 N9005. Any attempt to record video merely resulted in a "recording failed" message after about a second.
I thought I had installed a recent bootloader and modem using Odin 3.11.1, but although I did it twice I had used a "Reboot to Download" restart and for some reason that does not seem to have taken properly - although I have no idea why, all the display messages said it had worked.
So I have just done a full (remove battery and then three-finger power-up) boot into Download as advised in this thread, and then sent the same BL_N9005XXSGBQA1 and CP_N9005XXUGBOJ2 files to the phone via Odin, and now video recording works fine.
So when people say clean boot into Download, they do actually mean it. Thanks folks!
Oh, and I did NOT need to tick the "clear EFS" option, which seemed a rather risky thing to try so I was avoiding it as long as I could.
Andre
I bought a ZenFone 2 Laser CN version, and in need for Google Play Store, I rooted my phone. Since then, the rear camera stopped working. The front camera is fine, but the rear camera shows only black screen, and the button to capture picture doesn't work.
Here are the steps I tried:
- Flash ROM to ZE601KL_CN_1.16.40.1338, rooted it with a pre-root system.img via adb
- Installed Google services - Google services worked - And this is where the Rear Camera stopped working.
So I thought, maybe if I install a custom ROM, the camera may start working again, so I tried:
- unlock Bootloader
- Installed TWRP - twrp-3.0.2-5-Z00T
- Installed various version of CM and RR:
RR 5.6.7; RR 5.6.8; RR 5.6.9; RR 5.7.0; RR5.8.0
CM 13.0 20161220; CM 14.1 20161225
P.S. when I install RR 5.6.7, 5.6.8, 5.6.9, & 5.7.0, the phone will auto restart at welcome screen, only with RR 5.8.0, the phone is stable, both CM versions was stable
All with the same camera issue,
Then, I decided to flash it back to stock CN to see if it will solve the camera problem,
So I flahsed my phone to:
CN_V1.16.40.1338 ，
CN_V1.15.40.825
And now its CN_1.14.40.654
Still, nothing worked to fix the rear camera black screen issue.
The original ROM installed on my phone was: UL-Z00T-CN-1.16.40.1715-user
I tried to flash CN to WW, but it will not convert, so I am stuck with stock CN rom.
I'm looking for another possible solution.
Thanks if you can help.
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?
After smashing my head against the limits of the MIUI again, i decided to say goodbye to my warranty and flash a custom rom. Via TWRP I flashed the latest (stable) version of Arrow OS based on android 10Q. Everything works perfectly aside from the popup camera, that appears to be firmly locked in place feeding live feed from inside the chassis. Thinking it was an error of that release, i tried other ROMs, both Android 9 and 10, ResurrectionRemix, Lineage. With RR the problem is the same, while with Lineage, the camera asks for a calibration: it actually pops out fully does two or three pops and then it says calibration failed. The servos are working, I've opened the chassis and found no dust at all, so I've looked for a fix online. The most common one is a flash of the stock 'persist.img' image, I've tried several times via TWRP, tried a few clean flashes (ROM+image) of different versions and nothing. Am I missing something? I don't want to get back to MIUI...
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
The problem persists.
Badis st said:
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
Click to expand...
Click to collapse
I did, but even when I tried flashing different versions of persist.img ranging from fastboot stock firmware 10 to 12, with and without backup, (clean wipe, fresh recovery) the problem was still present. I'm no expert but I'd guess the OS doesn't know how to: either tell the servos to pop the camera out (Arrow OS) or recognizing the camera working when calibrating (Lineage OS). I'm trying to dig my way to the cam app in the MIUI release and to install it in the custom ROM, but I don't think it works.