Develop Bugs

Camera frozen on black screen no matter what I do

I've done a lot of digging through the forum and can't find an answer, so forgive me if this is an already-answered question.
I have a T-mobile S4 with a camera stuck on the classic "updating camera firmware" error message with black screen. If I open Snapchat the front facing camera will work, but with a slight delay in projection.
Here's the thing...this has happened on two separate phones now and on both of them it happened about 48 hours after I signed into the phone with my google account. Is it possible there is some kind of malware attached to my google account?
In the newest phone I have done a clean full wipe using TWRP, then Odin-flashed a full firmware package I found here on xda (recovery, OS, modem, kernel). Cache wipe and factory reset immediately after rebooting from Odin mode. Still have problem.
Have switched out known good cameras from other phones, and the phone I'm working on was functioning perfectly until I signed into it with my account. Totally stumped here, and really need some assistance.
Phone is:
M919 logic board in I337 body
Kitkat 4.4.4
Baseband: M919UVUFNH7
Kernel: 3.4.9-6281449, [email protected] #1
Build: KTU84P.M919UVUFOK3
Security software version: MDF v1.0 release 3, VPN v1.4 release 2
If anybody's got some ideas, please let me know!

Ok, no answers yet but plenty of views, so either this is an extremely rare issue that no one knows a solution for, or it's a ridiculously stupid question that everyone knows the answer to. I'm going to try and keep a log of what I'm doing with this phone in case any other rookies need assistance in the future.
So far I've flashed three different versions of stock Kitkat onto the phone....OH3, OK3 and NH7. When I flash OK3 my build number doesn't match my baseband (baseband reads NH7)...not sure what's going on there. Also, if I flash OK3 I lose my wifi....do not have this problem with other versions of firmware. Each flash is done after a full clean wipe with TWRP.
I found a thread that mentions an almost identical camera issue being caused on an M919 that was flashed with Nottache Xposed framework for AT&T phones. The OP said they could fix the issue by wiping the framework off the phone. Since my M919 motherboard is installed in an I337 body, I'm wondering if this is something related to a compatibility issue between T-Mobile and AT&T components. Best lead I've got so far.
Two posts have mentioned a fix. One says he opened Google Edition Camera Photosphere and his problem went away. He was running a different machine than mine so I haven't tried this yet, but I'm doubtful. The other user said they have only been able to solve the cam issue by installing a stock modded kernel by @jovy23. All the links I've found to this kernel are dead now, so no dice there.
I'm gonna put my M919 motherboard into an M919 body, wipe and flash stock rom again and see if somehow that does anything.
As a side note, I started getting "SIM not inserted" errors just before I began flashing different roms, and since the initial flash I've lost my SIM completely. So now I've got no camera, no SIM card being read, and sometimes losing wifi. I need this phone for work, so this is kind of sh*tty.

You cant downgrade once youve updated to OK3. The order would have to have been NH7, OH3 then OK3. It seems like mabey its not flashing correctly. Try a different odin program 3.04 3.07 3.09 are good ones. Flash it twice, untick auto reboot and manually power off and back into download mode and flash again. Dont use adv reboot menu to boot into download or it may not flash correctly. If that doesnt work I'm not sure what else to try. Good Luck

Ok, latest update for future readers...
It seems that lordodin912 is right when he says that flashing to OK3 means you can't flash backwards to a previous baseband/build. I hadn't seen that info anywhere so I didn't know about it. I'm not sure how to go about finding this kind of info on the forum but it would have been nice to know ahead of time. Anyhow...thank you for that information lordodin.
Here's where I'm at now:
-I was originally on NH7 with the camera error and sim card error. Flashed NH7 full stock after doing a full wipe and still had problems.
-Flashed OK3 full stock after full wipe and still had the problems, and also lost wifi capabilites (as in the phone wouldn't turn on wifi at all). At this point the baseband read as NH7 but the build read as OK3. I don't know why.
-Tried flashing OH3 after that (didn't know any better) and it wouldn't take. At this point wifi capabilites returned but still no cam and not reading sim card.
-Flashed OK3 again and wifi returned but still no cam and no sim. A couple hours later I powered the phone off and then back on, and Samsung then notified me of OTA updates. This update notification hadn't appeared before I manually rebooted the phone. I took the updates and now have wifi, sim card is being read, and my camera appears to be functioning properly as well. About 20 minutes or so after the updates are applied, the sim card error returned and told me to restart the phone. I did so and now the phone is reading the sim card again.
Right now my best guess is that when I was on NH7 I had accidentally made some app and update settings changes that prevented me from receiving some of the important OTA updates connected to camera and sim functioning, and this caused incompatibility between certain parts of the firmware that had been updated and others that had not. Trying to flash OH3 failed to solve the issue because I had already flashed OK3 before that and you can't go backwards from OK3. I don't know why the initial OK3 flash failed to fix anything, but I'm guessing the flash just didn't take as well as I thought it did. Flashing OK3 twice in a row seems to have done the trick, I presume because it reset and updated everything so that all firmware was compatible with itself.
I don't know how this could have happened (I try to be very careful about what I freeze and uninstall), but it's the most likely culprit because after flashing the latest firmware manually (twice) and allowing OTA updates my phone returns to proper function. Why OK3 didn't work correctly at first is beyond me....I don't see why it should have taken a few hours or a second reboot for OK3 to begin offering updates but whatever.
I'm doubtful that the camera will continue to work after the next 48 hours, but we'll see. I'll report back in with what happens after a few days go by.

Leaving an update here as I said I would.
For two months the phone has been functioning properly. Camera, sim and wifi have all been good. About one week ago my camera started acting glitchy again and then stopped working. The problem is the same as before- upon opening camera app the screen is black with a message saying "updating camera firmware", then nothing happens. This occurred around the same time I started using google hangouts frequently...don't know if that is related to the issue or not.
Yesterday the phone began showing the error message about sim card not being read, and then today it stopped reading the card altogether.
I repeated the same procedure that seemed to fix these problems two months ago and it hasn't done the trick. Full clean wipe of phone using TWRP, then installation of Chainfire's Autoroot, then flashed OK3 stock firmware twice with battery pulls between installations. Factory reset immediately after install of stock ROM. When connecting to wifi, no OTA updates appear. Camera not functioning, sim card not being read.
Phone shows baseband and build number are matching. I have no ****ing idea what the problem is with this phone. Beyond frustrated.
Anyhow, I'll keep updates going as long as I am working with this thing, maybe it'll help someone later. Anyone knows anything that could help, feel free to chime in.

Problems with Stock ROM, Custom ROMs, and LTE radio

Gonna try my best to give as much information as I can to make it easier for anyone good enough to try and help me with this. So I have an HTC One M9, from Sprint right here in the good old US of A, and it was working fine until I got the OTA Marshmallow update. At that point, apps started crashing like crazy (even after all were updated) and the status bar at the top of the screen and navigation buttons at the bottom would randomly disappear for several seconds after pressing the volume buttons, even after wiping the cache for both the system as well as the individual apps in question.
"No problem," I thought, "I'll just root it and install a custom ROM like I have with all my Android phones in the past." So I did that and tried Android Revolution, ICE, and ViperOne (all the latest versions), and every one of them had the same issues with programs crashing, the volume buttons messing up the screen, and so on. Actually, I couldn't even get through the setup wizards for any of them because those kept crashing too, and I had to use TWRP to rename the HTCSetupWizard.apk just to get to the home screen. Once there, my home button was inoperable, and no notifications or usual buttons like WiFi, Bluetooth, etc appeared when I pulled down on the status bar (which I discovered is what Android does if you don't complete the setup wizard).
At this point, I thought, "Well, maybe it's just a problem where my phone doesn't like Marshmallow for some reason. Let me try downgrading to Lollipop and see what happens." So I got the latest Lollipop versions for each of the aforementioned Custom ROMs, and they all ran smooth as silk, which tells me it's not an issue with faulty or damaged hardware. Only problem was that mobile data wouldn't work, on either LTE or CDMA settings.
I tried changing network modes, popping my SIM card in and out and rebooting in various combinations, but none of it worked. I couldn't even get into APN settings since the phone couldn't seem to detect my SIM card and had the APN menu greyed out. I thought I might have somehow damaged the SIM card with all the time I spent screwing around with the phone, but just to see what happened, I flashed a Marshmallow ROM back onto the phone and, sure enough, LTE service was right back.
I did some more research and saw that the issue may lay in the fact that the firmware (which is currently OS version 3.41.651.4) is not usable for Lollipop OS versions, and since my phone is S-ON (and I'm really not interested in spending $25 to S-OFF it), I'm not able to downgrade the firmware or, I assume, the radio firmware (if that's something you can even do separately from the "regular" firmware. Currently version [email protected]).
At this point, I'm really not sure what to do, and could use some guidance. I feel like my options basically boil down to the following:
1)Find a way to make Marshmallow ROMs more stable, possibly by reinstalling the firmware or some other method someone here might know that I don't,
2)S-OFF my phone, downgrade my firmware to something Lollipop can work with, and try a Lollipop-era ROM (not ideal), or
3)Go back to stock and hope Sprint pushes down an update my phone can use.
After going through all that, does anyone reading this have a recommendation for which of these options would be best (and how to go about them), or possibly offer other ideas I haven't come up with during the week and a half I've been researching and trying to fix it myself? I'm not hellbent on any particular option, I just want my phone to work (all of it) without constant crashes and glitches. Thank you to anyone who read all that and is still moved to offer help!

If you can run lollipop based roms you'd be on Lollipop firmware.
If you're going to mess around with aftermarket software you need s-off. If you don't s-off then you are risking unrecoverable bricks.
Sent from my HTC One M9 using Tapatalk

Okay, so if I'm on Lollipop firmware, would it stand to reason that that's why I'm having trouble running Marshmallow ROMs, including the stock ROM from Sprint? If so, what's the best (and safest) way to update it?

Note 7 random restarts and bootloops gone!!!

Hello,
I was facing some of the problems everyone is reporting here about random restarts and bootloops even (and mostly) using stock firmwares. As many of you started to have the problems after updates my problem started when I tried to root for the first time when SuperSU was not totally working yet. These problems didn't stop even flashing everything to stock (bootloader, modem, firmware, csc) and other stock firmwares from other countries so I was thinking that my phone was faulty too.
Every reboot my phone asked me for a password that I never set, so there was nothing to put there and I always had to reboot into recovery and flash the "no-verity" script or else I would get stuck in a bootloop or the phone asking me for a decrypt password (that didn't exist).
Sometimes when the phone randomly restarted gave me the "verity encryption" error at the beginning when using the stock recovery, if using TWRP it asked me for a password after semi loading Android (since it didn't found the official recovery to show that error from it), so I always suspected that the Samsung encryption was causing all my problems. Tried everything and even made a post about it (http://forum.xda-developers.com/note-7/help/random-restarts-password-doesnt-exists-t3450678)
So I kept waiting for something that disabled the phone encryption to verify that this was the real cause of this random behaviour before going to Samsung for warranty. Finally @Tkkg1994 came up with the Hydrakernel that disables the encryption so after trying it and formating everything MY PROBLEMS ARE TOTALLY GONE.
My suspects were finally confirmed..... The Samsung encryption was causing all these sh1ty problems (at least in my phone).
So everyone that is flashing stock firmwares even going back to old ones, it seems that doing this doesn't fix anything once you got into this problem for the first time, only disabling the encryption solves it. So my recommendation would be to disable the force encryption from Samsung by using the Hydrakernel and testing again (http://forum.xda-developers.com/note-7/development/kernel-hydrakernel-v1-1-t3452433)
I would like to thank all the devs that are doing their best effort to give us a free Note 7 to enjoy. @Tkkg1994 @dr.ketan @Chainfire it is very admirable that common people like them can solve things that not even Samsung has figured them out yet.
PS: Have you guys flashed this ROM and kernel instead of stock firmwares and continue to have problems with your Note 7??? Give your feedback!!!

Interesting, keep us posted with your phone status...

nice job keeping on testing & we waiting your next result

LG G4 won't boot up- NOT BOOTLOOP

So I have a T-Mobile LG G4 that like every other G4 had the bootloop problem when I got it. I sent it to LG and they promptly fixed the issue. My current issue has nothing to do with the bootloop I believe.
Because the G4 wasn't getting the Android N update fast enough and also because I wanted to play around with Android's full potential, I decided to root the phone a little over two weeks ago. The process worked and I decided to install a custom ROM. That also worked. I have installed four or five custom ROMs built on Android 7.1 without issue, or at least without any major issue.
However last night I decided to flash Genysis ROM on Android 6.0 because I wanted to play with Xposed. I made a full Nandroid backup of the CRdroid ROM it had been running and then wiped and flashed it using TWRP. When I installed the ROM it didn't work for whatever reason, freezing up and frequently becoming unresponsive. Over about 30 minutes I managed to enable USB debugging and reboot it to recovery (why I didn't shut factory wipe it from bios I'm not sure).
Now any ROM I try to install doesn't boot up. It never gets past the OS loading screen with the ROM logo. On 6.0 ROMs it says it has optimized the apps but gets stuck on starting them. The Nandroid backup I made does the same thing, even ones I made early that day and one from several days ago.
The backups had that one app installed that shows the logcat while booting up and while I'm no expert it seems to get a loop loading the audio drivers. I don't know if that's the cause or if it's just coincidental, as I've never heard of audio drivers preventing a boot, albeit my experience is with Windows PCs.
If it would help I can attempt to take a picture of the screen while stuck, although the text moves very fast. I can access the TWRP recovery just fine but don't know how to/if you can dump logs.
Any help would be much appreciated! I can attempt to supply an information that may be needed as well.

merger3 said:
So I have a T-Mobile LG G4 that like every other G4 had the bootloop problem when I got it. I sent it to LG and they promptly fixed the issue. My current issue has nothing to do with the bootloop I believe.
Because the G4 wasn't getting the Android N update fast enough and also because I wanted to play around with Android's full potential, I decided to root the phone a little over two weeks ago. The process worked and I decided to install a custom ROM. That also worked. I have installed four or five custom ROMs built on Android 7.1 without issue, or at least without any major issue.
However last night I decided to flash Genysis ROM on Android 6.0 because I wanted to play with Xposed. I made a full Nandroid backup of the CRdroid ROM it had been running and then wiped and flashed it using TWRP. When I installed the ROM it didn't work for whatever reason, freezing up and frequently becoming unresponsive. Over about 30 minutes I managed to enable USB debugging and reboot it to recovery (why I didn't shut factory wipe it from bios I'm not sure).
Now any ROM I try to install doesn't boot up. It never gets past the OS loading screen with the ROM logo. On 6.0 ROMs it says it has optimized the apps but gets stuck on starting them. The Nandroid backup I made does the same thing, even ones I made early that day and one from several days ago.
The backups had that one app installed that shows the logcat while booting up and while I'm no expert it seems to get a loop loading the audio drivers. I don't know if that's the cause or if it's just coincidental, as I've never heard of audio drivers preventing a boot, albeit my experience is with Windows PCs.
If it would help I can attempt to take a picture of the screen while stuck, although the text moves very fast. I can access the TWRP recovery just fine but don't know how to/if you can dump logs.
Any help would be much appreciated! I can attempt to supply an information that may be needed as well.
Click to expand...
Click to collapse
why not start from 0 and flash latest KDZ with LGUP.
https://forum.xda-developers.com/tmobile-g4/development/h811-kdz-file-t3607807

For sure I'll try that. I'll let you know if it works, thanks!

Follow up- I eventually found the free time to work on this and flashing the kdz worked! I actually had to use LG Bridge as LGUP only found my device as unknown.
Thanks for the help! Back to flashing ROMs for me.

Upgrading from Lollipop to Nougat, many issues

Hi team
I recently purchased an ex Demo HTC One M9 as a cheap replacement to my broken Galaxy S7 Edge, as soon as I received it I decided to flash TWRP and a new ROM on it. I was able to unlock the bootloader via HTCDEV.com easily enough and I was able to flash TWRP onto it without issue but when it came to the ROM's I ran into many problems.
Any version of Android that is Nougat or lower would not boot, the phone would go straight to the white bootloader screen every time. Oreo and Pie ROMs were able to boot but I ran into separate issues with them, I could not make or receive phone calls as the whole phone would freeze and there was no audio in from the speaker. I was also unable to play any videos in Facebook, YouTube, Snapchat etc.
I tried every single ROM available here on XDA and ran into these issues. I stupidly also did not make a TWRP backup of my system so it was quite hard to revert back to what it came from factory, I managed to get a stock Marshmellow running thanks to a User here posting a TWRP backup so thanks.
Is anyone able to help me with upgrading to Nougat? I would really like to get the Viper ROM working if possible, is it a known issue getting stuck in the bootloader menu every time?
I've tried just updating through the OTA process in the menu but it says there is no update file available.
Cheers