Ever since I updated to DK28 (loong time ago) I noticed that my device become unrooted, and the USB is not recognized (already tried different cables, different PC, different OS) none of the OS even recognize that there is a device inserted to the PC eventhough on Epic, the USB menu appeared. Searching at the device manager and no new device recognized at all.
I tried to use Epic's stock recovery to flash any kind of ROM: stock ROM full, stock ROM update, but always give me errors: status 2 error and or verification failed.
My Epic is still working, however, I cannot do anything with it anymore. Cannot root, cannot update, etc, etc.
I need more advice on alternative solutions that I can use.
TIA
Have you tried the update.zip samsung had posted for the "mac users"? That could update yu to EB13, no root.
Do a search on the forum, I know you can find it.
Sent from my Epic 4G powered by midNIGHT 4.2 ext4 / OC Froyo Kernel @ 1.2Ghz EB13
Hi all,
A couple of days ago, Google Hangout appeared to crash on my Nexus 4 and afterwards the Camera would not work.
Eventually I got the error message "Cannot connect to Camera".
I was on AOKP :: jb-mr1 :: Milestone 1 + franco r143.
After a few reboots, the camera worked briefly but then stopped completely.
I subsequently tried flashing franco r155, restoring a backup of milestone 1 and then eventually restoring my original stock 4.2.2 image.
None of these worked.
I have seen posts relating to firmware files in /data/cfw but these don't appear to exist on my nexus 4 and why weren't these restored with my stock image if required?
(Have checked via adb etc).
Has anyone got a fix for this specific to the nexus 4?
Any pointers gratefully received or I will be on the phone to Google for replacement.
Thanks all.
Hi. I'm having wifi issues with my Nexus. It started after flashing MIUI. I was using TWRP to flash, it took a while for the google logo to disappear and to get to the Xiaomi bootlogo. After it finally booted, the wifi was stuck to "turning on", but never ultimately firing up(couldn't get it to turn on nor off, even having turning it off). I've also noticed that I have the same EXACT issue with CyanogenMod. I completely returned to stock, i've relocked the bootloader and everything. I tried CM installer today and i'm rooted again with CM, but still I have the same exact issues as before. I don't have these issues with some other roms such as stock, official Omnirom and such, i wouldn't think it would be exactly a hardware issue, since it works just fine with certain roms. Would anyone have an idea why my phone is having this issue? It wasn't always this way. Specifically, I haven't been having issues with 4.4 roms. Does anyone think it could be something related to bootloader, or something?
Juanito216 said:
Hi. I'm having wifi issues with my Nexus. It started after flashing MIUI. I was using TWRP to flash, it took a while for the google logo to disappear and to get to the Xiaomi bootlogo. After it finally booted, the wifi was stuck to "turning on", but never ultimately firing up(couldn't get it to turn on nor off, even having turning it off). I've also noticed that I have the same EXACT issue with CyanogenMod. I completely returned to stock, i've relocked the bootloader and everything. I tried CM installer today and i'm rooted again with CM, but still I have the same exact issues as before. I don't have these issues with some other roms such as stock, official Omnirom and such, i wouldn't think it would be exactly a hardware issue, since it works just fine with certain roms. Would anyone have an idea why my phone is having this issue? It wasn't always this way. Specifically, I haven't been having issues with 4.4 roms. Does anyone think it could be something related to bootloader, or something?
Click to expand...
Click to collapse
i have a similar problem... i rooted my nexus and flashed a custom rom (PACman) when it boots wifi is disabled, also bluetooth doesnt work neither any sounds, no music, no speaker, nothing, so i flashed Paranoid android (both based on 4.3) and i had the same problem
so then i flashed stock, everything ok, then CrDroid (based en 4.4) everything ok, then OmniRom (Based on 4.4) everything ok too...
i posted it here and got no replies, hope someone could help
Yes, right now I'm running an unofficial CM 11, and no issues. I wonder if something needs to be downgraded, in order for things to be okay again. I would still like the option to be able to run 4.2/4.3 based roms. Maybe I could try flashing to stock 4.2 or 4.3, then reroot, and test my results
Sent from my Nexus 4 using Tapatalk
What radio/baseband version are you using?
Hi, I'm using AOKP last nightly builds and since 2013-10-18 Wi-Fi started to stuck, settings ui errors and other problems. So I just tried franko kernel with official AOKP releases and Wi-Fi now is working fine. But i've faced skype problems). After 4 minutes it hangs and i need to restart my phone.
Hi guys , I've got a problem with my Nexus 4. Basically whenever I try to copy over my pictures using the standard MTP method It'll crash and say my device isn't responding or not compatible to transfer with my PC. When I first got my phone it was all fine but recently it's given me these problems. Even if I use the PTP method still crashes. I'm running Kitkat 4.4.2 with Franco's Kernel and everything else is stock.
Any solutions?
Thanks
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?