I keep having an issue when returning to Stock/official Rom from Mokee100 on my NX611j
everytime I try, stock camera never works (I get a black screen when I try to launch).
I lost my original nandroid backup and am therefore helpless.
I get the black screen on 2.38, 2.45 and 2.49 rom versions.
Any pointers please?
I solved it by installing Stock firmware version 2.06.
That seemed to bring my camera back.
Related
Hey,
In the past couple of days, I've flashed a new ROM and flashed a new radio along with it. Since then, I've not been able to make a proper call. The quality of the call just breaks up constantly, it's basically impossible to hear what the other person is saying.
I flashed the ROM to VillainROM 10.3 final.
I flashed the radio to "hero-radio-63.18.55.06PU_6.35.15.14" but due to being on Orange UK, my phone locked so I flashed to a previous radio "-hero-radio-63.18.55.06PU_6.35.15.11". I cant help but think this may play a part in the problem?
Thanks
Jamie
Yeah sounds like the radio is the problem, you need to revert back to the original radio you had. Did you create a nandroid backup??
If you didnt id suggest searching google for an orange radio, or perhanps revert back to the stock rom which may include the orginal radio, dont update to the latest stock rom though as you may not be able to root again.
Yeah sounds like the radio is the problem, you need to revert back to the original radio you had. Did you create a nandroid backup??
If you didnt id suggest searching google for an orange radio, or perhanps revert back to the stock rom which may include the orginal radio, dont update to the latest stock rom though as you may not be able to root again.
my question is that i am flashing an old firmware
in order to have an old camera firmware version.
But my fw still remains the same ZDFF02.
Ani ideas how can i go back to ZDFE02?
bump
I'm interested in this too.
tried the same by flashing older firmware and writing back the old firmware but strangely it didnt happened.
any reason for downgrading?
bala_gamer said:
tried the same by flashing older firmware and writing back the old firmware but strangely it didnt happened.
any reason for downgrading?
Click to expand...
Click to collapse
Yeah bro
With newer fw my camera on CM10 isn't working, always shows " can't connect to camera".
With stock based roms it works perfectly.
Hello everybody,
I installed the latest aopk (from 19.11.) for Medipad.
Everything works good but now, the Display sometimes flicker when the Pad is in Landscapemode.
I tried some other Settings of the DPI but it doesnt work.
Can someone help? Thx.
Had that too, didn't find a solution, ended up going back to stock firmware.
Thx.
I have Recover my Backup and work with 4.0.4.
I also have Problems with Adobe Flash on 4.1.2, so i will wait for a later Rom-Version.
My current configuration:
STOCK JB 4.1.2
AT&T
Screen Rotation selected
Things I have tried:
Gyroscope calibration (result: ball stuck in the middle)
Leveling Applications from Play Store (result: looks like it calibrated but did nothing ultimately)
Used *#0*# - Sensors (result: All sensors passed except image test)
I view my phone horizontal and the screen rotates to landscape as expected. I rotate my phone to normal position and the screen is still displaying landscape. It should be portrait. HELP!!!!!!!
Redownload and reinstall the firmware to insure it was not a corrupted download or bad write.
I forgot to mention that prior to updating to official JB, I installed CM10 JB 4.2.2 and screen rotation didn't work at all. So I restored to stock and it still was broken. It was working prior to installing CM10 JB 4.2.2. I came to the conclusion that it had to be CM10's version that messed up my settings with screen rotation. I restored to stock 2.3.6 and tried everything possible. I restored CWM backup image of working image prior to install of CM10. Still having the same issue. Last night, I updated to official JB 4.1.2 via Kies and thought that they may fix it. I was wrong....
studacris said:
Redownload and reinstall the firmware to insure it was not a corrupted download or bad write.
Click to expand...
Click to collapse
You've flashed several kernels at this point
Pretty much ruling out software issues (unless you've restored an app that's getting funky or something weird)
Kinda sounds like a hardware malfunction to me
jtrinh said:
I forgot to mention that prior to updating to official JB, I installed CM10 JB 4.2.2 and screen rotation didn't work at all. So I restored to stock and it still was broken. It was working prior to installing CM10 JB 4.2.2. I came to the conclusion that it had to be CM10's version that messed up my settings with screen rotation. I restored to stock 2.3.6 and tried everything possible. I restored CWM backup image of working image prior to install of CM10. Still having the same issue. Last night, I updated to official JB 4.1.2 via Kies and thought that they may fix it. I was wrong....
Click to expand...
Click to collapse
You are NOT alone. CM 10.1 broke auto-rotate on a LOT of phones. I'm currently flashing CM 10.1 from 4/22/13, since that version worked correctly, to see if that will help.
I read about another phone having the same problem a while back, and they had some weird, contorted way of fixing the problem that, of course, could not be done to the Note.
P.S. I have also tried installing CM 10.1 from 5/02/13. No joy.
I hope installing the new Stock 4.1.2 between CM versions didn't yak the phone forever.
I give up. Hopefully, someone will come up with a flashable .ZIP file that can fix this mess.
I'm currently running SR Remix KitKat and I'm tired of the bugs so I want to go back to 4.3. I've tried simply doing a full wipe and factory reset then installing SR 4.3 v3.1 but it just loops the boot animation endlessly. I've tried using both TWRP and Philz Touch recovery. After restoring my 4.4.2 backup all is working but I'm back to square one. Before I set about using Odin to flash back to 4.1.2 I would like to make sure I'm not wasting my time
UPDATE:
So I decided to try odining back to 4.1.2 and after unlocking with casual everything was working until I tried updating to SR Remix 3.1. This doesn't make sense because that's where I was when first updating to SR Remix. I have one last thought. When first updating to MJ9 I started with the "Beans Official" release. Maybe I'll try that before giving up.
UPDATE 2:
Well that's very strange, I used the Beanstown official stock release then installed SR and got it working. I wonder what's missing from Sophisticated ROM that is keeping it from working.