Related
Hi
I've upgraded to 2.3.3 and my camera doesnt work anymore. The screen comes black for a few seconds and then the message "Camera error. Cannot connect to camera" appears. The flashlight is also doesnt work. I have some MoDaCo firmware HTC Sense before, as I remember...
Help me to fix it, please.
Thanks
Flash newer radio.
Jack_R1 said:
Flash newer radio.
Click to expand...
Click to collapse
Could you tell me how to do it, pls? What is the last version of radio? How to check it?
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Jack_R1 said:
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Click to expand...
Click to collapse
The Baseband Version is 32.41.00.32U_5.08.00.04
What I'm thinking is could it be the problem because my Nexus had non original firmware before the GB update, and maybe I didnt make some important thing which blocking my camera now? Maybe I need to re-flash the radio with some original image? I'm totally NOOB in all these things...
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Jack_R1 said:
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Click to expand...
Click to collapse
Thanks for your advices. Just upgraded the radio to 5.12 via fastboot. The camera still not work Will try to flash to original state...
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
P0MkA said:
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
Click to expand...
Click to collapse
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
k_myk said:
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
Click to expand...
Click to collapse
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
P0MkA said:
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
Click to expand...
Click to collapse
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
k_myk said:
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
Click to expand...
Click to collapse
Yeah... backuping is a cool thing.... It is just my first experience with the Android phone... Maybe will find some kind of solution for this...
Well... Problem stays... However I've found few interesting things. As I've mentioned above, after the 2.3.3 update the camera and flashlight doesnt work enymore. But I've installed Z-DeviceTest and found that after the reboot this app (which provides the hardware test) sees the camera and flashlight! But, unfirtunately, doesnt able to test it. Moreover, if to start some torchlight widget directly after the reboot, the flashlight works!!! But it is not after the camera start... So, maybe someone will find this information useful.
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
sevensaints said:
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
Click to expand...
Click to collapse
Stupid actually. Its stay the same, not working....
found the solution!
http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91
You have go go back to stock ROM.....then camera Happy Trigger Finger!
yeah...
1. Go back to stock through HBOOT
2. Flash back ur fav ROM - mine-MIUI AU
pls click thanks
Hi all,
First of all, apologies for a very newbie question.
I have a stock N1 with terrible battery life. I have stumbled intersectRaven's mod/Kernel at: http://forum.xda-developers.com/showthread.php?t=653598
I would like to ask how I can install this on my N1, is it just a matter of downloading the right file, renaming it to update.zip and then doing what I've done to update my phone as with official updates?
What do I need to pay attention to and is there a way to revert back to the original rom/Kernel if I'm having issues with this mod or if I want to sell my phone?
Thank you in advance!
I don't think you can flash a kernel if your bootloader is locked--you didn't say
I know if you are, you need to wipe Dalvik Cache and Cache first, but that is on Amon_Ra recovery. Been rooted from day one and don't remember anything about stock recovery
There may be some unrooted kernels, not sure if any for N1
Some kernels are geared to certain roms
I would be very careful till you get 100% answer on this
First of all, sorry for the absurd title. Couldn't think of anything else.
Anyways, since the time I've got my GN, I've flashed CheckROM (GB), TeamRocket's ICS, Imilka's AOSP, Stunner and I don't remember the others. Now, as discovered, there have been tons of issues with all these repacks and what not. I am on stock GB for now, tried the official ICS, couldn't get root somehow. My question is if there is any way by which I can make my note "brand new". Like nothing ever has been done to it. I don't think just flashing the stock ROM with PC Odin does that, or does it!?
flashing a stock rom, providing its a wipe rom should set it back to factory settings
Richy99 said:
flashing a stock rom, providing its a wipe rom should set it back to factory settings
Click to expand...
Click to collapse
I flashed a stock GB ROM (wipe version) through PC Odin over the stock ICS. Rebooted like a 100 times and always getting FC messages. All my apps are crashing, gapps crashes all the time. Had to reflash the stock ROM like 5 times, working fine for now..
dr ketan has a nice how to... follow it and you should be fine...
I have heard a lot of talk about an emmc bug affecting stock Ice Cream Sandwich builds realeased by Samsung. THe general consensus seems to be that it is not safe to wipe/factory reset the stock Samsung ICS roms.
The question I have is do we know if the recent UK region ICS update (XXXLQ2) is affected by the emmc bug?
Can anyone confirm that if they factory reset after upgrading to LQ2 ICS that they bricked their phone or that it was a successfull wipe?
I can confirm that i have factory reset my phone successfullu after installing LQ2 update although my phone has problems caused by this update - random reboots, crashes to the homescreen, screen going black and buttons not responding etc. Could these problems be caused by the emmc bug?
I look forward to your replies, i know there are geniuses on this forum who can enlighten us.
We wont know if its affected until someone reports a brick.
But I would guess its still affected by the emmc bug.
As Entropy says in his PSA:
"All ICS official releases for the Samsung Galaxy Note (GT-N7000) as of late May 2012 - This includes XXLPY, ZSLPF, and DXLP9, and future kernels should be assumed affected until further notice."
So the bug is in offical releases?
SO this bug is in the official releases that you can install via kies?
Will Samsung patch this bug?
Surely they must be aware of it since the number of bricks going to the service centers must be rising astronomically. If we are aware of it how can they not be when they have tested many devices at factory?
Better hold on to gb then rushing to ics with emmc bug. Wait for awhile until some one found a solution. Or else you will stuck like me with no gb backup to revert back.
Sent from my GT-N7000 using XDA
This is a XXLQ2 Brick I Guess.
Lol thats a total facepalm. But whats the cause of his brick? I couldnt read it all cause I laughed so hard that I got tears in my eyes.
JazonX said:
This is a XXLQ2 Brick I Guess.
Click to expand...
Click to collapse
No, that brick was not caused by the LQ2 kernel; it happened because the guy had used an ancient updater script for his Rom.
http://forum.xda-developers.com/showpost.php?p=26951708&postcount=3
chasmodo said:
No, that brick was not caused by the LQ2 kernel; it happened because the guy had used an ancient updater script for his Rom.
http://forum.xda-developers.com/showpost.php?p=26951708&postcount=3
Click to expand...
Click to collapse
Yeah thats exactly what I thought. As I said, couldnt read it all.
Contrary to beliefs I have had no issues on my Indian ROM ICS.
I believe it may have something more to do with custom kernels, etc rather than Stock firmware?
I too have the LQ2 update and would also like to know if this is also affected by the brickbug i have not done a factory reset and currently have no issues with my phone. I do not intend on doing a factory reset until i know that Samsung have fixed the issue.
Well, you might aswell count on beeing affected. But if you dont need to factory reset then everytging is fine.
Belfia said:
Well, you might aswell count on beeing affected. But if you dont need to factory reset then everytging is fine.
Click to expand...
Click to collapse
Cheers just hope i don't need to factory reset before a fix is sorted. Don't really want to go about changing roms as i like tw and like to keep my phones standard.
volvo940seturbo said:
I too have the LQ2 update and would also like to know if this is also affected by the brickbug i have not done a factory reset and currently have no issues with my phone. I do not intend on doing a factory reset until i know that Samsung have fixed the issue.
Click to expand...
Click to collapse
Run the "GotBrickBug" app by Chainfire under the Themes/Apps section and see what firmware you have.
More than likely the LQ2 ROM still has the faulty MMC_CAP_ERASE code because Samsung hasn't admitted to the problem at all yet.
dbreloaded said:
......my phone has problems caused by this update - random reboots, crashes to the homescreen, screen going black and buttons not responding etc. Could these problems be caused by the emmc bug?
Click to expand...
Click to collapse
I initially update by Kies to LQ2 and had random homescreen force close, black screen,green dots on the screen, apps freezing...etc. Done a factory reset, then downgraded to GB UK, factory reset again, downloaded the LQ2 Firmware via Check FUS PC version and flashed ICS LQ2 using ODIN PC and everything is running smooth. No bugs to report after more than 1 week.
rdosti said:
Contrary to beliefs I have had no issues on my Indian ROM ICS.
I believe it may have something more to do with custom kernels, etc rather than Stock firmware?
Click to expand...
Click to collapse
I'm afraid this is not correct! Its a bug in stock ICS kernels (or other ICS based kernels that are not specifically modified) that enable the eMMC erase command.
Some custom ICS based kernels now have this command disabled. But as for now, it is considered unsafe to flash or specifically full (data) wipe from any stock ICS ROM (some ICS ROMs do a full wipe when flashed!). It is still statistically a rare event, but the only way to be 100% sure safe is to flash from a GB based kernel, such as Abyss 4.2 kernel.
Samsung is working on a "fix" for the faulty firmware in the emmc chips but what this fix will be is unknown.
It has been reported that, unrooted, on a Stock ICS ROMS (and hence stock kernel) has super-bricked after doing a factory reset.
You may be able to do a full wipe/reset/custom ICS kernel ROM and not suffer any immediate ill effects but the bug can manifest itself at a later date.
If you really want to get the bug, the best way would be to fill up your internal memory, then do a factory wipe, rinse and repeat!
GB kernels don't use the erase command, so are totally safe.
So to summarise, it is not safe to factory reset on LQ2 UK rom! Samsung have not yet issued a fix!
EDIT: Wow, its even more complicated than above lol!
See here for updates and the first sign of a fix!
http://forum.xda-developers.com/showthread.php?t=1698977&page=14
So, I'm a total newbie at android rooting but, I decided to take a shot at it a few months ago. I flashed the kernel of my Android 5.1 Note 5 to a rooted one, now, I'm about to give the phone back to T-Mobile, but I certainly want the root gone before I do that just for the sake of things going as smoothly as possible.
I didn't flash any custom roms or anything, its still the stock rom, just a rooted kernel. Would doing a simple phone reset through the normal settings put everything back to normal/unroot and get rid of that "Kernel is not seandroid, enforcing" message on boot? Or would it require just simply flashing a stock kernel back through Odin? Or something else? I really just need that damn message gone.
If need be, I have TWRP flashed as the recovery as well.
// NEVERMIND, problem solved.
how do you solved it?
I think Odin should do the trick.